ClockworkMod Recovery for the Transformer Prime TF201
NEW: Repack of Koush's clockworkmod recoveries to prevent a recovery loop when using ROMS that support reboot to recovery.
These recoveries are not mine and I take no credit for them. I only made a small change to the official recoveries found here
and repacked them into update.zip files.
Here is a diff of my somewhat hacky change, but hey it works!
Code:
diff -Naur org/init.rc new/init.rc
--- org/init.rc 2012-04-02 21:18:24.875745175 +0100
+++ new/init.rc 2012-04-02 20:58:55.855745201 +0100
@@ -31,6 +31,8 @@
service ueventd /sbin/ueventd
critical
[COLOR="Green"]+service clearmisc /sbin/clear-misc.sh
+[/COLOR]
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
diff -Naur org/sbin/clear-misc.sh new/sbin/clear-misc.sh
--- org/sbin/clear-misc.sh 1970-01-01 01:00:00.000000000 +0100
+++ new/sbin/clear-misc.sh 2012-04-02 20:58:55.855745201 +0100
@@ -0,0 +1,4 @@
[COLOR="Green"]+#!/sbin/sh
+# This clears the boot flag from misc which forces
+# this device to continuously boot into recovery
+/sbin/dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13[/COLOR]
I also replaced the CWM top hat icon to avoid confusing my repacked recovery with the original version.
I am not responsible for any loss of data or any harm caused by using these recoveries especially if small kittens are involved.
IN CASE YOU FIND YOURSELF HERE AS A RESULT OF HAVING A RECOVERY LOOP OR RECOVERY DOESN'T SEEM TO BE UPDATING PLEASE USE THE COMMAND BELOW
Run the following command from your PC then reboot and any new recovery should be flashed by the bootloader and then android should boot.
Code:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Just in case you missed big red bold line, please read it before posting about recovery not updating or not being able to get out of recovery!
Download
Touch Recovery v5.8.1.8 (repacked from official with the fix above)
MD5: 0a5f77d3524fbdd01a241b02368814ae
ClockworkMod Recovery v5.8.2.0 (repacked from official with the fix above)
MD5: 351f2382907afc48d12932e019ecb193
Installation Instructions
Method 1 Flashing through CWM
Download the recovery zip file
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Once it has flashed the zip file, be sure to reboot your transformer so it complete the flashing process.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thx Roach!
Thanks for this Roach. This might be a really obvious question but I take it that the reboot to recovery option will have to be enabled by devs? I am using AOKP and the reboot to recovery option still just reboots the tablet after flashing this. Jermaine will have to enable this option in AKOP for it to work, right?
Thanks again. Btw, I am really excited to see what you and Team Eos do with your rom on the Prime
Sent from my EPAD using xda premium
Cool... thanks!!
paddycr said:
Thanks for this Roach. This might be a really obvious question but I take it that the reboot to recovery option will have to be enabled by devs? I am using AOKP and the reboot to recovery option still just reboots the tablet after flashing this. Jermaine will have to enable this option in AKOP for it to work, right?
Thanks again. Btw, I am really excited to see what you and Team Eos do with your rom on the Prime
Sent from my EPAD using xda premium
Click to expand...
Click to collapse
Yeah, Here's my commit's to enable this on EOS in case it helps. I know it already works on the TF101 so it might just need to be added to your device tree assuming the libcutils work has already been merged to the AOKP repo.
https://review.teameos.org/#/c/377/
https://review.teameos.org/#/c/378/
Thanks for putting this out. Works good. Ext-Sd would be cool but we'll let that dev try to update it. Thanks again to help us out!
Working great on Team Eos thx!
Excellent work Roach, well done. I plan on looking into trying to get SDcard (both micro and docked full size) and USB drive support up and running.
Don't hold your breath though anyone, I am extremely lazy.
Doktaphex said:
Excellent work Roach, well done. I plan on looking into trying to get SDcard (both micro and docked full size) and USB drive support up and running.
Don't hold your breath though anyone, I am extremely lazy.
Click to expand...
Click to collapse
Thanks mate.
That would be great to see more features and storage support. I'm excited for the possibilities for the Prime and what we can all do for it.
Touch updated 4/16?
Curios as to if the touch recovery was updated today, and if it does in fact let you reboot from android into recovery.. Thanks.
kizzle4 said:
Curios as to if the touch recovery was updated today, and if it does in fact let you reboot from android into recovery.. Thanks.
Click to expand...
Click to collapse
??? ????
What? Official CWM Touch is still listed as build 5.8.18 on Koush's website. Only new release is the KANG build in the OP (much appreciated by the way ), and as of right now it only works on AOSP Rom.
This seriously needs to get stickied ASAP. I hope fellow Prime owners can appreciate that the devs coming to this part of the forums are some of the very best.
I'm having a bit of a problem... I'm in CWM, which is looping back into itself, and I cannot for the life of me figure out where to enter the code that you provided in the OP. My computer installed the ADB drivers just fine, but I can't see anything in which I can enter that code. Any assistance is appreciated.
Edit: Ok, I figured out that I'm supposed to enter that in the Command Prompt window, but every time I try running the command, I get the following:
'adb' is not recognized as an internal or external command, operable program or batch file.
Any ideas?
I'm really stuck on this, guys. If there is anyone who can help me out, I would be in your debt.
ZebTheCalvinist said:
I'm having a bit of a problem... I'm in CWM, which is looping back into itself, and I cannot for the life of me figure out where to enter the code that you provided in the OP. My computer installed the ADB drivers just fine, but I can't see anything in which I can enter that code. Any assistance is appreciated.
Edit: Ok, I figured out that I'm supposed to enter that in the Command Prompt window, but every time I try running the command, I get the following:
'adb' is not recognized as an internal or external command, operable program or batch file.
Any ideas?
Click to expand...
Click to collapse
Where did you install the adb/sdk files? You need to be in that directory to run the command. In otherwords, if you have adb installed in C:\tools, you need to do this from the command prompt before running the adb commands:
Code:
cd C:\tools
jermaine151 said:
Where did you install the adb/sdk files? You need to be in that directory to run the command. In otherwords, if you have adb installed in C:\tools, you need to do this from the command prompt before running the adb commands:
Code:
cd C:\tools
Click to expand...
Click to collapse
I feel like a total idiot, but I can't find where I installed the ADB files. I have a handful of ADB files from various android projects, but I don't know where the specific drivers for the TF201 are. Is there a way to re-download and install ADB?
ZebTheCalvinist said:
I feel like a total idiot, but I can't find where I installed the ADB files. I have a handful of ADB files from various android projects, but I don't know where the specific drivers for the TF201 are. Is there a way to re-download and install ADB?
Click to expand...
Click to collapse
The drivers are installed. Adb is adb and not device specific. Do a search on your computer for adb.exe
jermaine151 said:
The drivers are installed. Adb is adb and not device specific. Do a search on your computer for adb.exe
Click to expand...
Click to collapse
Ok, I was able to get it figured out. I really appreciate the help.
kizzle4 said:
Curios as to if the touch recovery was updated today, and if it does in fact let you reboot from android into recovery.. Thanks.
Click to expand...
Click to collapse
Yes, I'm running the latest EOS nightly and the reboot to recovery function from the power menu works. I can't speak for any other rom
Sent from my Galaxy Nexus using Tapatalk 2
I'm running jermaines latest aokp build and cannot boot to recovery from directly from the rom. No biggie.
Sent from my EPAD using XDA
Related
Alright everyone,for those of you having issues to revolution on your Evo 3d and flooding the irc I figured id start this to compile everything.
Things I have noticed.
1. yes after the install your device to attempt a hands free activation,don't freak when is say checking for firmware update,it wont find anything!
2. You may have to do a battery pull after the initial flash/install. On Mine,the recovery did not install! Problem will be worked out im sure,this is a beta AND teamwin has their own recovery going on as well.
[ I have found the reason why the recovery is not installed is simply because clockwork is not support on the shooter yet.Do install a recovery use team wins recovery image and directions which can be found here: http://forum.xda-developers.com/showthread.php?t=1192077
Here is a simplistic break down on how to do this,I am not responsible for your actions!
Download the .img file found in the thread,make sure you also download the fastboot.exe and place it in the same folder as ADB for easy access. Once that is done,reboot while holding down your power + volume down button!
Fastboot menu will come up,the command you need it
fastboot flash recovery (location of file).img
For me it was fastboot flash recovery C:\Downloads\durka.img yes I renamed it durka because I dont like long names]
3. If you are having issues getting your serial number,connect it to ADB and do adb get-serialno
4. If you cannot get root,you will have to download busybox by stericson on the market. I had to manually sign into my gmail accounts so remember your passes!
[This is wrong,if you do not have root you need to have the teamwin recovery installed and you need to flash the superuser.zip file found on the forums. If you are having issues installing,make sure signature verification is unchecked,then once reboot install busybox]
All apps that I have that require root are working for me, just waiting on a deodexed rom. Even SetCPU is working,but I dont have the custom kernel installed,which could actually be easily doable now!
And I leave the thread to y'all
Well, I can probably help troubleshoot. Rooted and installed teamwin recovery first try. Doing a nandroid backup now.
I can also help people troubleshoot, I am also rooted and have teamwin recovery going!
N e 1 kno how to do this with a mac?
D3VO
Rooted and recoveried on first try. Doing my compressed NAND backup now. (I like the fact that it can be compressed...but it's slow as hell lol)
Yeah, I was a tad concerned at first about the hands-free activation notice, but everything was smooth like buttah... Thank god I remembered my passwords!
My issues:
First try: I got all the way to the part where the phone is taken to hboot and fastboot usb is selected. I was getting a red X for the driver not being installed bc I didn't have HTC Sync installed, so I cancelled revolutionary, rebooted my phone, installed htc sync on my pc, and tried again...
Now, after rebooting both my phone and the pc, I can't get past the initial "Acquiring Root" step.
help...
rtbluver said:
I can also help people troubleshoot, I am also rooted and have teamwin recovery going!
Click to expand...
Click to collapse
Successfully gained S-OFF but when I select recovery from HBOOT it sends me to htc screen. Power button then reboots phone.
tia
A few of us are stuck on --- Acquirig root ( method 3) -- Any ideas???
only issue I've found is that Titanium Backup refuses to work on my phone.
yes, I flashed the SU package found here, and also tried the Busybox installer from the market.
besides that, everything's working great, already nandroided my stock setup and my WiMax partition while waiting for the ROMs to drop!
hey guys.....im trying to fastboot thye recovery img but cant quite to get it goiung.....do the recovery img and fastboot.exe have to be placed int he same folder?....or where exactly do i put them?.....thanks fellas
tek818 said:
My issues:
First try: I got all the way to the part where the phone is taken to hboot and fastboot usb is selected. I was getting a red X for the driver not being installed bc I didn't have HTC Sync installed, so I cancelled revolutionary, rebooted my phone, installed htc sync on my pc, and tried again...
Now, after rebooting both my phone and the pc, I can't get past the initial "Acquiring Root" step.
help...
Click to expand...
Click to collapse
HTC Sync should not be installed. Install the HTC Fastboot drivers from the revolutionary wiki
reverepats said:
hey guys.....im trying to fastboot thye recovery img but cant quite to get it goiung.....do the recovery img and fastboot.exe have to be placed int he same folder?....or where exactly do i put them?.....thanks fellas
Click to expand...
Click to collapse
Yes, Fastboot, recovery and AdbWinUsbApi.dll must all be in the same folder
miguelfp1 said:
only issue I've found is that Titanium Backup refuses to work on my phone.
yes, I flashed the SU package found here, and also tried the Busybox installer from the market.
besides that, everything's working great, already nandroided my stock setup and my WiMax partition while waiting for the ROMs to drop!
Click to expand...
Click to collapse
TB works great for me. Are you sure that the su installed? is it in your app drawer? If not download it from the market and try installing that.
housry23 said:
TB works great for me. Are you sure that the su installed? is it in your app drawer? If not download it from the market and try installing that.
Click to expand...
Click to collapse
yeah, flashed it twice. other root programs work (including the Busybox installer), which stumps me... TB even worked flawlessly with the temp-root before
Did you try uninstalling then reinstalling TB?
housry23 said:
Yes, Fastboot, recovery and AdbWinUsbApi.dll must all be in the same folder
Click to expand...
Click to collapse
mines set like that but i get
Code:
C:\sdk\tools>fastboot flash_image recovery C:\Users\Tesso\Desktop\recovery-twrp-
shooter-1.img
usage: fastboot [ <option> ] <command>
CheesyNutz said:
mines set like that but i get
Code:
C:\sdk\tools>fastboot flash_image recovery C:\Users\Tesso\Desktop\recovery-twrp-
shooter-1.img
usage: fastboot [ <option> ] <command>
Click to expand...
Click to collapse
In the new sdk adb is in platform-tools folder, so here's what I did. I moved fastboot and twrp recovery to platform-tools folder, renamed the recovery image to recovery.img and pressed shift while right clicking on the platform-tools folder and choose open command prompt(or window) here. Then just type flasboot flash recovery recovery.img and press enter. Worked for me.
I see what you did...you have to type "fastboot flash recovery nameofrecoveryhere.img" and it will work. Make sure the recovery image is in the same folder as fastboot.
housry23 said:
Did you try uninstalling then reinstalling TB?
Click to expand...
Click to collapse
no go either , I'll keep trying
thanks for your help!
miguelfp1 said:
no go either , I'll keep trying
thanks for your help!
Click to expand...
Click to collapse
Did you unroot the temp root before installing Revolutionary? This might be the cause because attn1 from AlphaRev told me to unroot and factory reset to get rid of all the temp root stuff before running Revolutionary.
irock1985 said:
A few of us are stuck on --- Acquirig root ( method 3) -- Any ideas???
Click to expand...
Click to collapse
I'm stuck here also..
[RECOVERY] ClockWorkMod Official "TOUCH" recovery v5.8.1.8 [UPDATED 24/5/12]
As I seem to have come under a little fire for not stating that you need to be unlocked to install a custom recovery, I thought that I would add a little clarification.
At the time I started this thread the unlock had only just been released, and EVERYONE knew that the methods contained within this thread were only possible if you were unlocked. I apologize for my assumptions.
PLEASE NOTE, YOU MUST BE UNLOCKED TO BE ABLE TO INSTALL A CUSTOM RECOVERY AND/OR CUSTOM ROM!
I also received a little flak for not explaining the adb/fastboot processes more clearly. While I can understand that many people who come to XDA are new to the whole custom ROM kettle o' fish, it is my honest opinion that if you have not already read up about ADB and FASTBOOT and have an understanding of how to use them, you most definitely have absolutely no business whatsoever flashing a recovery or ROM at all.
I was a noob when I first arrived here at XDA, but I read and re-read as much information as possible before going anywhere near flashing custom recoveries and/or ROMs to my Desire HD.
There are plenty of great guides around for learning how to use ADB and FASTBOOT, please I implore you, before attempting to flash anything to any device you own, read these guides over and over again until you feel that you have the confidence to flash your device without the need for someone to hold your hand.
I think that about covers everything that I wanted to say other than a big thank you to Swiftks and Striatum_bdr for answering so many peoples questions in this thread.
That's all folks.
As always Peace, Dok
!!!YOU MAY WANT TO GO HERE FOR UPDATED UNOFFICIAL RECOVERIES, BOTH TOUCH AND STANDARD VERSIONS ARE AVAILABLE!!!
Huge thank you to Roach2010 for the updated recoveries.
LETS GET THE FORMALITIES OUT OF THE WAY
1. I did not build this, it is the official CWM touch recovery from the CWM website.
2. If you brick your device flashing this, I am in no way responsible.
3. If you brick your device flashing this, I am in no way responsible.
4. Please, follow all steps very carefully, especially the actual flashing step.
5. I have personally flashed this without issue.
6. THERE IS CURRENTLY NO VERSION OF CWM FOR THE PRIME THAT SUPPORTS EXTERNAL SDCARD STORAGE. USE THE INTERNAL MEMORY FOR ALL YOUR FLASHING NEEDS.
CREDIT: KOUSH FOR HIS AWESOME WORK
So, you want some lovely touch based CWM recovery on your device?
METHOD NUMBER 1: The Fastboot! - NO NEED FOR ROOT
Come right this way you fearless young chap.
http://www.clockworkmod.com/rommanager
download the tf201 touch recovery, version 5.8.1.8
Now, switch off your device, then hold volume DOWN and the power button together until your Prime shows the RCK screen.
At this point press volume down. This will take you to the options of which fastboot is one.
Switch to fastboot mode by pressing volume DOWN (It's the USB symbol, but you knew that already else you wouldn't be here) then press volume UP to select the option.
Connect your USB cable now, if you haven't already.
Next you need to open a command prompt/terminal window and cd to where you have downloaded the .img
Next type fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
Once the flash has completed (the screen will sit with a full blue bar doing nothing) you can reboot to recovery as per normal, but now you will have the wonderful touch recovery.
METHOD NUMBER 2: The blob!
CREDIT to Striatum_bdr
- download the img file
- rename it as blob file with a more simple name for example cwm_touch.blob
- open Terminal Emulator on your tablet, then:
$ su
# dd if=/"path to blobfile" of=/dev/block/mmcblk0p4 (REPLACE "path to blobfile" with the path to where you have saved the file).
You're done.
Reboot, the blob file will be flashed at boot (same as kernel).
METHOD NUMBER 3: The Terminal noob!
CREDIT to darksiiide
It is also available via ROM Manager, for a fee.
!!!HUZZAH FOR KOUSH!!!
I hope you all enjoy.
My recommendation would be to do a fresh backup of your ROM as soon as you boot into the new recovery, just in case.
AWESOME!!!
It is also available via ROM Manager, for a fee.
Sent from my Transformer Prime TF201 using Tapatalk
this won't wipe my current rom correct?
No it doesnt touch your ROM. It just changes your recovery to clockwork touch.
Sent from my Transformer Prime TF201 using Tapatalk
darksiiide said:
No it doesnt touch your ROM. It just changes your recovery to clockwork touch.
Sent from my Transformer Prime TF201 using Tapatalk
Click to expand...
Click to collapse
thank you, will report back on how it went
---------- Post added at 08:43 PM ---------- Previous post was at 08:32 PM ----------
it takes forever to start Fastboot USB download protocol
Cwm touch recovery was bricking Epic touches last month. Don't mean to spook anyone but I'm fine with the volume rocker. :beer:
No disrespect OP
Sent from my Galaxy Nexus using xda premium
Works great for me! Thanks for posting.
Sent from my Transformer Prime TF201 using Tapatalk
Question does this have theme support? Themeing the recovery not the rom?
I like the idea of them wanting more money.
Sent from my Transformer Prime TF201 using XDA Premium HD app
Touch Recovery is completely buggy on my phone, I'll wait a little for some user feedback lol...
EDIT: another method (need to be rooted)
- download the img file
- rename it as blob file with a more simple name for example cwm_touch.blob
- open Terminal Emulator on your tablet, then:
$ su
# dd if=/path/to/blobfile of=/dev/block/mmcblk0p4
You're done.
Reboot inrecovery as usual, the blob file will be flashed at boot (same as kernel), you'll ony need to reboot in recovery.
Striatum_bdr said:
Touch Recovery is completely buggy on my phone, I'll wait a little for some user feedback lol...
EDIT: another method (need to be rooted)
- download the img file
- rename it as blob file with a more simple name for example cwm_touch.blob
- open Terminal Emulator on your tablet, then:
$ su
# dd if=/path/to/blobfile of=/dev/block/mmcblk0p4
You're done.
Reboot inrecovery as usual, the blob file will be flashed at boot (same as kernel), you'll ony need to reboot in recovery.
Click to expand...
Click to collapse
I added this method to the first post, credit to you in there also. Thanks for the input dude.
Can you do this with a locked boot loader?
KiNG OMaR said:
Can you do this with a locked boot loader?
Click to expand...
Click to collapse
In a word "NO!"
Sent from my Transformer Prime TF201 using XDA Premium HD app
No problem using method 2
# 2 also worked perfect for me as well.
Had this and it worked great. I upgraded to stock v.21 firmware and lost root. Not only that, I have no recovery bootloader or fastboot anymore. It informs me that recovery kernel is not found and requires me to hard-reset the device.
Is it possible to flash this through ADB without having to be in fastboot or something?
crypted said:
Had this and it worked great. I upgraded to stock v.21 firmware and lost root. Not only that, I have no recovery bootloader or fastboot anymore. It informs me that recovery kernel is not found and requires me to hard-reset the device.
Is it possible to flash this through ADB without having to be in fastboot or something?
Click to expand...
Click to collapse
Through adb you can push the blob renamed file in the same /dev block file than in method 2 but I'm afraid you still need root to do that.. Worth to try adb remount command, and see the result. If no error message then 'adb push /path/to/blob/computer /dev/etc...'
First time I used my terminal emulator and it worked like a charm. Thanks for the guide and feedback everyone.
Sent from my Transformer Prime TF201 using XDA
Striatum_bdr said:
Touch Recovery is completely buggy on my phone, I'll wait a little for some user feedback lol...
EDIT: another method (need to be rooted)
- download the img file
- rename it as blob file with a more simple name for example cwm_touch.blob
- open Terminal Emulator on your tablet, then:
$ su
# dd if=/path/to/blobfile of=/dev/block/mmcblk0p4
You're done.
Reboot inrecovery as usual, the blob file will be flashed at boot (same as kernel), you'll ony need to reboot in recovery.
Click to expand...
Click to collapse
worked like a charm. thanks for the info.
So I dont have my nanadroid backup...thats not my concern because i can just flash the stock rom...but anyways i dont have an os installed i have twrp recovery...im tryin to adb sideload the rom.zip so i can then flash the rom. Could someone please enlighten me how to do this or a detailed tutorial ive searched but im having no luck thanks in advance!!!
2phonejones said:
So I dont have my nanadroid backup...thats not my concern because i can just flash the stock rom...but anyways i dont have an os installed i have twrp recovery...im tryin to adb sideload the rom.zip so i can then flash the rom. Could someone please enlighten me how to do this or a detailed tutorial ive searched but im having no luck thanks in advance!!!
Click to expand...
Click to collapse
If never gotten sideload to work, but you can try adb push. this is where I learned it http://forum.xda-developers.com/showthread.php?t=1667929
joshyy_rey said:
If never gotten sideload to work, but you can try adb push. this is where I learned it http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
It working as far as connecting to fastboot but when i goto recovery like the tutorial states and then goto mount and run the commands it doesnt push the file even though it says device is being read.
joshyy_rey said:
If never gotten sideload to work, but you can try adb push. this is where I learned it http://forum.xda-developers.com/showthread.php?t=1667929
Click to expand...
Click to collapse
Im using twrp btw idk if that is the issue but if so do you know how i can flash the cwm recovery or is that not possible urrghhh im so close i just have to get this adb to push the file!
if you have an OTG cable you can load from a USB stick..Just mount OTG
2phonejones said:
Im using twrp btw idk if that is the issue but if so do you know how i can flash the cwm recovery or is that not possible urrghhh im so close i just have to get this adb to push the file!
Click to expand...
Click to collapse
You can flash cwm through adb. Adb might be buggy through recovery it was at first. I'd post on the twrp thread to see if a someone has an idea
Sent from my HTC One using xda premium
I had this problem myself today and started freaking out. After a brief 15 second panic attack I realized I could side load. I have twrp and sideloaded very easily.
I used the all in on toolkit listed in the android dev section and cleanrom 1.5. I put cleanrom on my desktop and renamed it to Rom.zip. I started the aio tool which has a button for sideloading a Rom. Boot the phone into recovery and plug it into your pc. (I am assuming you have the HTC drivers installed) From TWRP click on advance and the adb sideload. Then click the side load button on the aio tool. This will attempt to reboot your phone first but since you're already there just close the command prompt that comes up. A new window will come up for you to chose the zip. Navigate to your desktop and pick the zip you put on the desktop (longer paths seem to cause issue with sideloading). Then it will push the zip to your phone. The command prompt on your pc will have a percentage progress. Once done just flash that zip like normal.
I had to reboot my phone using the volume down power button method before I could get back to twrp and the install froze once in Aroma. But I just flashed it again and it worked. Once I got it back I just put my backup back on the phone, booted back to twrp, and restored my backup.
Sorry if this seems unorganized, had two toddlers crawling all over me while. typing. Using the AIO should work
AIO found herehttp://forum.xda-developers.com/showthread.php?t=2242635
Sent from my HTC One using xda app-developers app
hi guys
i've unlocked my HTC ONE X + international!
but now i can't go further the HTC logo
i tried fastboot, flashing boot and recovering recover.img. but nothing go right.
Some questions:
Which rom did you try to flash?
What method did you use to flash it? (e.g. Hasoon's all in one tool/through recovery/sideload)
Did you make sure to flash your kernel (boot.omg) separately?
Did you perform a full wipe before flashing?
Can you enter the bootloader by holding volume-down while powering the phone on?
Can you use adb or fastboot to interact with the phone? e.g.
Code:
$ adb reboot bootloader
or
$ fastboot devices
Sent from my cellular telephone using xda premium
o_O said:
Some questions:
Which rom did you try to flash?
What method did you use to flash it? (e.g. Hasoon's all in one tool/through recovery/sideload)
Did you make sure to flash your kernel (boot.omg) separately?
Did you perform a full wipe before flashing?
Can you enter the bootloader by holding volume-down while powering the phone on?
Can you use adb or fastboot to interact with the phone? e.g.
Code:
$ adb reboot bootloader
or
$ fastboot devices
Sent from my cellular telephone using xda premium
Click to expand...
Click to collapse
after i unlocked the phone i've used fastboot to fastboot recovery.img
and that's all i did .
now i have low battery
Boot into bootloader by holding volume-down and restarting the phone (if you don't know how to do that, hold the power button until the capacitive lights flash).
Then, try flashing a recovery image. You can get twrp from the thread in the One X+ Original Android Development forum. I think you already have the platform tools (adb and fastboot).
The command to flash a recovery is:
Code:
$ fastboot flash recovery recovery.img
This is assuming your recovery filename is "recovery.img" and that it's in the same directory as your command prompt when you run the command.
Sent from my cellular telephone using xda premium
o_O said:
Boot into bootloader by holding volume-down and restarting the phone (if you don't know how to do that, hold the power button until the capacitive lights flash).
Then, try flashing a recovery image. You can get twrp from the thread in the One X+ Original Android Development forum. I think you already have the platform tools (adb and fastboot).
The command to flash a recovery is:
Code:
$ fastboot flash recovery recovery.img
This is assuming your recovery filename is "recovery.img" and that it's in the same directory as your command prompt when you run the command.
Sent from my cellular telephone using xda premium
Click to expand...
Click to collapse
thanks bro )))
but now it says there is no any zip file
is there any methods to "put custom rom inside" the phone???
tyomaus said:
thanks bro )))
but now it says there is no any zip file
is there any methods to "put custom rom inside" the phone???
Click to expand...
Click to collapse
If you've gotten the recovery installed, then you can sideload the rom onto the phone. I can give you instructions to do that with TWRP as your recovery. With your phone connected to your computer, enter the recovery from the bootloader. Choose the "Advanced" button, and then "ADB Sideload" and then swipe to start the sideload process.from your command line on your computer, you can now start the sideload process:
Code:
$ adb sideload name-of-rom-zip-file.zip
Obviously you would need to put the actual name of your rom's zip file and make sure your zip is in the correct directory to be picked up by the command. You should see the rom begin to upload to your phone, and when it's done, it will automatically flash.
I've found that sometimes sideload can take a little while to detect the phone but usually it detects it immediately. If it's taking a while, try running the following command and then do the sideload again; it might help:
Code:
$ adb kill-server
$ adb sideload name-of-rom-zip-file.zip
Don't forget that because we haven't gotten S-OFF for our device yet, we need to flash the kernel separately. Just open the rom zip file, and extract "boot.img". Then you need to enter the bootloader and flash that to your phone with this command:
Code:
$ fastboot flash boot boot.img
Hopefully that helps to sort your phone out.
thanks for help! )))
, MAN u r the best!!!! thanks a lot ! ))))
No problem! Glad to help.
o_O said:
No problem! Glad to help.
Click to expand...
Click to collapse
hi, i have one more problem (((
i've installed custom ROM, but only AOKP is working but not properly, after installing says there is no SD card ((
others stuck in loading screen.
This is because the default location of your SD card has changed from /data/media to /data/media/0. You can fix it by simply moving the contents of /data/media to /data/media/0.
Code:
$ adb remount
$ adb shell
# mv /data/media /data/0
# mkdir /data/media
# mv /data/0 /data/media/
Make sure you copy the commands exactly, including the slashes and that should have the contents of your SD card accessible again.
o_O said:
This is because the default location of your SD card has changed from /data/media to /data/media/0. You can fix it by simply moving the contents of /data/media to /data/media/0.
Code:
$ adb remount
$ adb shell
# mv /data/media /data/0
# mkdir /data/media
# mv /data/0 /data/media/
Make sure you copy the commands exactly, including the slashes and that should have the contents of your SD card accessible again.
Click to expand...
Click to collapse
thannks MAN, but it does not work (((
i tried to install OrDroid and it flies normally, however i'd like to use CM 10 4.2.2 which stuck in loading logo
maybe there is something i do wrong?!
tyomaus said:
thannks MAN, but it does not work (((
i tried to install OrDroid and it flies normally, however i'd like to use CM 10 4.2.2 which stuck in loading logo
maybe there is something i do wrong?!
Click to expand...
Click to collapse
every rom needs the correct boot.img/kernel to work. did you flash blade kernel for CM 10.1? did you wipe/factory reset your phone in recovery before you flashed CM 10?
Exactly what reaper90 said, the first thing you should check when you get a bootloop is the kernel.
A lot of other phones don't require you to flash the kernel separately, but those phones have S-OFF available to them. Since we're stuck with S-ON (for now), the boot partition is locked and can't be written to from the phone. So you have to flash the img containing the kernel + ramdisk separately. Also note that max has done three different versions of the BLADE kernel, so you need to ensure that you're grabbing the correct one.
Check max's post here: http://forum.xda-developers.com/showpost.php?p=34962464&postcount=1
Edit: Just another couple of things:
1. Like reaper90 said, doing a full wipe really helps when switching between roms. Usually you can get away without wiping if you're installing a new version of the SAME rom, but to be on the safe side I personally wipe everything when I flash a different rom.
2. If you're certain that you've done everything correctly, and it's still not working, try clearing your cache and dalvik cache from the recovery. Occasionally that can fix minor problems.
cool
reaper90 said:
every rom needs the correct boot.img/kernel to work. did you flash blade kernel for CM 10.1? did you wipe/factory reset your phone in recovery before you flashed CM 10?
Click to expand...
Click to collapse
thank you MAN!!! it's working! :good:
yourthebest
o_O said:
Exactly what reaper90 said, the first thing you should check when you get a bootloop is the kernel.
A lot of other phones don't require you to flash the kernel separately, but those phones have S-OFF available to them. Since we're stuck with S-ON (for now), the boot partition is locked and can't be written to from the phone. So you have to flash the img containing the kernel + ramdisk separately. Also note that max has done three different versions of the BLADE kernel, so you need to ensure that you're grabbing the correct one.
Check max's post here: http://forum.xda-developers.com/showpost.php?p=34962464&postcount=1
Edit: Just another couple of things:
1. Like reaper90 said, doing a full wipe really helps when switching between roms. Usually you can get away without wiping if you're installing a new version of the SAME rom, but to be on the safe side I personally wipe everything when I flash a different rom.
2. If you're certain that you've done everything correctly, and it's still not working, try clearing your cache and dalvik cache from the recovery. Occasionally that can fix minor problems.
Click to expand...
Click to collapse
nothing to say, just HUGE THANKS!!! )))
i have more questions, one of them is - how can i rollback stock ROM for my HOX+? i've bought it in UAE!
is it possible to install original ROM, if so where can i find one for my HOX+ ?
thanks in advance !
Sure, it's possible, and you have a couple of options depending on how "stock" you want to go.
If you just want to go back to a Sense rom, you can go to the One X+ Android Development forum and download any of the international roms from there. You would need to flash Elite kernel or hXORe kernel, which can also be found in that forum, and the process for flashing the rom and kernel is exactly the same as the AOKP/CM roms you already tried.
If you specifically need to get back to STOCK, then it's a little more complicated. You need to run a RUU (Rom Update Utility) for your device, which will put the original software back on your phone, but you need to remember to re-lock your bootloader before you run it, or it will fail. You can download the correct RUU for your device here (http://androidfiles.org/ruu/?developer=ENRC2B).
I would hazard a guess that you can find the right version by matching the radio version on your phone to the radio version on the RUU, along with your geographic location. You can find your phone's radio version by going to settings > about phone > baseband version. A quick explanation behind that logic is that a normal rom-flash won't touch your phone's radio, so you're likely to still have the same radio version that your phone shipped with.
WARNING, however, messing with your radio can brick your device so please please make sure you have the right one before you flash. I'm not sure which is the correct one for your device and the only RUUs I've ever flashed were way back in the early Windows Mobile days, so hopefully someone else here can give you better direction on that point.
Finally, if I were to give my opinion, you're better off taking a rom from the Android Development forum. I'm a die-hard AOSP fan, but I've flashed and played with the roms in there and our Sense devs have done a great job with the X+. The only reason I'd go back to stock is if I had to for warranty purposes.
tyomaus said:
i have more questions, one of them is - how can i rollback stock ROM for my HOX+? i've bought it in UAE!
is it possible to install original ROM, if so where can i find one for my HOX+ ?
thanks in advance !
Click to expand...
Click to collapse
As already said, I'd recommend installing a stock like custom rom, for example Android Revolution HD, it's very close to stock. You can find stock kernel/boot.img in the thread and if you want it as close to stock as possible you can just leave out all the tweaks options in aroma installer.
reaper90 & thank u BROS! )))
I kinda messed up about a month ago, I was wanting to root my HTC One so I could try some custom ROMS and experience other cool stuff
However, Me, feeling nervous decided to go the Cyanogenmod Installer route (You know this isn't gonna end well). And so I plugged in my device and everything was good and fine until It was unlocking my bootloader, it seemed to do the HTCDev one, I got the option to unlock it or lock it, and as soon as the device restarted the phone disconnected.
Some apps went missing, however I recently had a talk to a friend who said that is normal, and he recommended me to come here to get some help.
I can boot into the bootloader where you can go into fastboot and stuff, I can factory reset through the Android OS once its booted, however when I enter recovery in the bootloader, the screen goes black and a red exclamation mark shows up for about 5-10 minutes and then the device reboots into Android.
The same thing happens when I try to get Over the air updates, I can still get OTA updates, they just don't install.
So what I'm looking for is, can I relock my device and get it back to how it was before I ran Cyanogenmod installer and then maybe I can try root it manually and have more control over the situation.
I hope you guys can help me and I hope I can find a place on this forum
Thanks in advance guys!
First of all, it seems you shouldn't have started to mess with this at all...
now to fix this...
Download the latest recovery of your choice e.a. twrp. @ http://techerrata.com/browse/twrp2/m7 the normal one is the m7 i suppose? else go to the right section...
save it to your /sdcard directly or move it there. than for the eaz just rename it to twrp.img
open an terminal if installed on your device and type
su
than
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 (note command for the m7)
if you however don't have the capability to install an app because of missing gapps... which sounds like it...
install adb/fastboot on your pc with the htc drivers..
download the recovery image with your pc and rename it to twrp.img and put it at your fastboot file
turn off your device
keep holding volume down until a menu shows up
select fastboot from the menu
attach the device to your pc
open cmd and type fastboot devices (to see if you actually installed the right driver... and that it's recognizing it)
if it does
type:
fastboot flash recovery twrp.img
if that all succeeded, you can download gapps for the android version your using or flash something else with the working recovery..
goodluck!
Hawkysoft said:
First of all, it seems you shouldn't have started to mess with this at all...
now to fix this...
Download the latest recovery of your choice e.a. twrp. @ (It prevented me posting links) the normal one is the m7 i suppose? else go to the right section...
save it to your /sdcard directly or move it there. than for the eaz just rename it to twrp.img
open an terminal if installed on your device and type
su
than
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 (note command for the m7)
if you however don't have the capability to install an app because of missing gapps... which sounds like it...
install adb/fastboot on your pc with the htc drivers..
download the recovery image with your pc and rename it to twrp.img and put it at your fastboot file
turn off your device
keep holding volume down until a menu shows up
select fastboot from the menu
attach the device to your pc
open cmd and type fastboot devices (to see if you actually installed the right driver... and that it's recognizing it)
if it does
type:
fastboot flash recovery twrp.img
if that all succeeded, you can download gapps for the android version your using or flash something else with the working recovery..
goodluck!
Click to expand...
Click to collapse
Thank you! Will there be a risk in ruining my device?
And thank you once again! I definitley shouldn't have messed with this, but you gotta start somewhere right?
If I never took the risk of building my own computer then I never could have done it Its how we learn.
Anyways, I'm not sure about the terminal bit, I don't run linux and I don't have a mac? So, how would I have access to the terminal. Unless I somehow got it on my device (I don't know how to do that).
And one more question, once I've done the things you've told me to do I can just put Cyanogenmod on it?
Thanks once again
Oh, and I have got Gapps, if my Gapps you mean Google Apps, yes I have I've got Google play services, Google play, hangouts etc.
Thank you! Will there be a risk in ruining my device?
Click to expand...
Click to collapse
Further than now? i highly doubt it... unless you totally put in a wrong recovery which magically wud fk up the partitions?
And thank you once again! I definitley shouldn't have messed with this, but you gotta start somewhere right?
Click to expand...
Click to collapse
True, but babysteps mate...
Anyways, I'm not sure about the terminal bit, I don't run linux and I don't have a mac? So, how would I have access to the terminal. Unless I somehow got it on my device (I don't know how to do that).
Click to expand...
Click to collapse
Terminal should be on the phone, if not use command prompt in windows... u need to do a little research on the m7 forums which driver you need they probably have an m7 toolkit again if the one is the m7, as far as i knew it is.. than you could put the recovery.img in the folder of fastboot.exe and go there with command prompt and do what i've written before
And one more question, once I've done the things you've told me to do I can just put Cyanogenmod on it?
Click to expand...
Click to collapse
erhm ofcourse you can, however just download the rom instead of an installer...
p.s. you got gapps.. install an emulator oh... better solution... install flashify download the latest twrp and install it with that if u have proper root that is!
Hawkysoft said:
Further than now? i highly doubt it... unless you totally put in a wrong recovery which magically wud fk up the partitions?
True, but babysteps mate...
Terminal should be on the phone, if not use command prompt in windows... u need to do a little research on the m7 forums which driver you need they probably have an m7 toolkit again if the one is the m7, as far as i knew it is.. than you could put the recovery.img in the folder of fastboot.exe and go there with command prompt and do what i've written before
erhm ofcourse you can, however just download the rom instead of an installer...
p.s. you got gapps.. install an emulator oh... better solution... install flashify download the latest twrp and install it with that if u have proper root that is!
Click to expand...
Click to collapse
Thanks I don't have root, I've run rootchecker, and it says I don't have root.
And what if I do Cyanogenmod but I want to go back to HTC Sense (Doubt it though)
Will instlaling the recovery root my device? If not, how will I root it?
Oh and, how do I get fastboot and ADB?