Database Users

Recoverable custom ROM installation on APAC/WWW/ASIAN ARIA

This is for our friends using the APAC/WWW/Asian HTC Aria that do not have a factory restore image from HTC to restore their phone. This is largely a repost of an the original method we used to install custom ROMs on the Aria that we used before Unrevoked's REFLASH installed clockwork recovery for us. This method borrowed a lot from Eugene373's original mytouch slide method, with uses an exploit developed by the unrevoked team.
I am reposting it here because the original thread is locked and I can no longer edit my post. I don't want to simply link to it because we want to make sure we don't do any modification that cannot be reversed. If followed, the ARIA can be backed up, modified, then recovered fully to stock. This is not an easy method for many.
Again, what this does is allow you to load clockwork recovery without installing it, backup your original, unrooted ROM and then install a custom ROM.
OS X/Linux Users: remember to preface abd commands with ./ (./adb)
I strongly suggest using Linux or OS X to do this as these operating systems have far fewer driver issues. An Ubuntu LiveCD works well, and you can use Linux without ever installing it on your PC.
PREREQUISITE #1: You must have the android sdk installed and know how to use adb.
PREREQUISITE #2: Download Clockwork_Aria_MT3GS.zip
Process:
Format the SD card supplied with the phone like this: http://forum.xda-developers.com/showpost.php?p=7029045&postcount=283 (Thanks Yoshiofthewire) in a card reader if at all possible.
Copy your new ROM zipfile to the root directory of the SDCARD. DO NOT name it update.zip. DO NOT unzip it. You must flash the zipfile later.
Copy the contents of Clockwork_Aria_MT3GS.zip to the tools directory of your SDK, along with your ROM zipfile of choice.
Power up the phone, holding down the VOL-DOWN button.
Wait about 10 seconds, until some diagnostic checking is done.
Press volume down to highlight recovery, but to do not push power to execute just yet.
Open a terminal window/command prompt and Migrate to the SDK tools directory to run the adb commands later. If you are on OS X or Linux, open the terminal window and then switch to superuser access (sudo su).
Get ready to connect the phone to the computer with the USB cable, but don't connect one end until you read the next step.
This part is difficult and it's critical, and it's inconsistent and therefore may take quite a few tries to get it right: Pushing the power button first and then approximately one second later plug in the USB cord. (Think ONE THOUSAND ONE-PLUG)
When the triangle/exclaimation over phone graphic appears, hold volume up and press power. This will bring you to stock recovery.
If this works, running adb devices command from the tools directory on the PC will list the device. If not, start from the beginning from power up. This can take a lot of tries, be patient and don't give up. Not all SD cards will work reliably.
Once devices are listed in the loop, hit CTRL-C to terminate the loop if you've started one. Hurdle one complete.
In recovery, use volume down to select Apply sdcard:update.zip and push the power button to execute (This will fail, but it's enabled write access for me.)
adb push ota.zip /sdcard/update.zip and press the enter on keyboard to execute. (No - that's not a typo)
If that pushes without error, then enter adb push update.zip /sdcard/update.zip but do NOT press enter.
In recovery, again scroll down with power down to select sdcard:update.zip but do not execute yet.
Press the power button and then watch phone to say "verifying" and then press enter IMMEDIATELY on the keyboard. If timed right, Clockwork recovery should load. If not, start back at step push ota.zip /sdcard/update.zip and repeat from there until clockwork loads.
From Clockwork Recovery, do a Nandroid backup.
From Clockwork Recovery, select install zip from sdcard, and execute, then choose zip from sdcard and execute, and then you can scroll down to your pre-rooted rom of choice and execute that to flash it. In Clockwork you can scroll with trackpad or volume buttons, and you can execute with either the power button or a trackpad button push.
To restore, follow this process again and do a nandroid restore of your original backup instead of flashing a new ROM.
Click to expand...
Click to collapse

not sure what to call this problem

Ok, so rooted (razorclaw) ics 4.0.3 tf-101.
fully charged
when powering on, stalls at the eee pad screen. (sounds like a boot loop, but it doesn't go to recovery)
Cold boots fine, works great, no random reboots (yet)
Will not boot into recovery, has ww_epad-9.2.1.11-20120221 bootloader
stalls at "booting kernel image" I assume there is no recovery installed.. Tried to get cwm onto it but I cant get apx working, it wont recognize the device at all.
I didn't root it, someone else did and I have no idea what recovery is/was on it.
I bought the tablet used, and would like to fix it.
Once recovery is installed would this boot normally.
Ive been searching on here/transformer forums for a couple weeks and have thought I found the answer multiple times. I need a push in the right direction.
Tried to fix this for a while a couple months ago when ics first launched and gave up. (did the same thing when It had honeycomb on it)
edit::
the only solution I can come up with is using NVFLASH to try to restore it. Working on this right now, hopefully this is a sbk1//not working, cant seem to get the computer to recognize the device in apx mode. (win 7)

If your TF is rooted, you may want to give the RecoveryInstaller app a go.
http://forum.xda-developers.com/showthread.php?t=1346180&highlight=recovery

I forgot to add that I have tried that (tried it again just now.. twice, just incase it happened to work but it didnt.)
following these instructions:
"click the button and the Superuser app will ask for permissions. Then the tablet reboots and to enter it you have to keep the Volume - key pressed and when it the TF writes "Booting into recovery" on the screen press Volume + once"
also tried it without holding volume buttons when it reboots.
When I run it, and click the button to install recovery, it grants superuser permissions and then reboots, sticks at the eee pad screen again and it stalls at booting recovery kernal image. Anything Im missing?

Reflash a recovery image .sos and bootloader .ebt if the recovery image doesn't work.
Download any cwm flashable recovery and extract it twice to get the recovery blob out:
put the recoveryblob on your computer somewhere.
adb push C:\Location\Of\Blob\blob.blob /sdcard/
adb devices
adb shell
su
dd if=/sdcard/blob.blob of=/dev/block/mmcblk0p4 -
reboot
--
this should fix recovery.

Thanks for breaking that down! Im going to try this once I can get adb working.
Going to try another computer now. I'm beginning to wonder if the usb cord for my tf has gone bad.

You can do it on your tf too, via terminal emulator app since you can coldboot.
Download blob somewhere on tf, download term em. and run this part:
su
dd if=/Path/to/recoveryblob of=/dev/block/mmcblk0p4 -notice path/to is where you placed on Tf's INTERNAL storage.
reboot

Ok, went through it on the terminal emulator. Everything seemed to go ok, but on rebook, it still wont enter recovery (held the vol button of course) just hangs on "booting recovery kernal image"

Is BusyBox installed?

That it is, just reinstalled 1.20.. should i use a different version perhaps?

Ro.secure set to 0?
see the guide to flashing an insecure boot.img if it isn't, this may be the problem.
if you're on a rom this isn't the issue..
Try a different version of BB I suppose

simplywinter said:
Ok, went through it on the terminal emulator. Everything seemed to go ok, but on rebook, it still wont enter recovery (held the vol button of course) just hangs on "booting recovery kernal image"
Click to expand...
Click to collapse
Suggest you try method 3 in the following post.
http://forum.xda-developers.com/showthread.php?t=1622628
It does not require rooted TF. If you do everything right but still not working, you may have a faulty device.

^^ My peri runs that method, so that didn't work. :/
I think borked hardware, try NvFlash

just did this
ls - l /system/xbin/su
getprop ro.secure
returned: 0
So it is indeed set to 0.
NVflash.. well I would do that if I could get the usb connection to the computer working.. Still trying that.
Also, kokopopz
I went through method 3 on the tf itself, unfortunately it didnt work. Still trying to get adb working to try it that way.

simplywinter said:
I went through method 3 on the tf itself, unfortunately it didnt work. Still trying to get adb working to try it that way.
Click to expand...
Click to collapse
The following guide will be useful for setting up ADB.
http://forum.xda-developers.com/showthread.php?t=1071584
For the USB driver, you can try the naked driver.
http://forum.xda-developers.com/showthread.php?t=1514942&highlight=naked
Note: I am a linux user. I set up ADB on my linux box. I did not try the above myself. I just came across them. They maybe useful to a Windows user.

Windows drivers are finicky, make sure you totally uninstall and reinstall them too. Took forever to get right on my computer.

no go with windows. I still cant seem to make this work... I have ubuntu on my laptop though. Can I even do this on Ubuntu? its 11.04

You can do this with Ubuntu no drivers required, just pick up the Nvflash wheelie for linux and get yourself a reflashed ROM.
Also you can still do this on TF. I had a very similar issue that I was able to fix by using Rayman's Blobtools (you can pickup blobunpack for windows in my bootsplash screen change guide).
Download the latest stock ROM for your device, and extract the 'blob' file out of it.
Put the blob in the same folder as blobunpack.exe, then open a command prompt and cd to the directory, then run:
Code:
blobunpack blob
After that you will see that there are now many blobs, one of them is called blob.EBT, this is your bootloader blob. What you want to do is copy that to /sdcard/ on your tf via mass storage or 'adb push blob /sdcard/' (You Have to remove the .ebt extension, it's just there as an ID, so it should just be 'blob')
Once that's there flash it through the staging partition (In terminal emulator or adb shell):
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
reboot
Then it shouldn't get stuck at the Eeepad screen anymore!
If it still does, you might have that weird problem where nothing flashed through staging partition sticks, so you'll need to run Roach2010's fix.

after trying that.. twice. It doesn't seem to stick. Roaches 2010 fix it is, searching for it right now.

If you can get adb shell access (I'm assuming yes) PERI has the fix bootloop option. Otherwise run roaches fix AFTER flashing a new recovery and EBT partition but BEFORE rebooting.

how do i run roaches fix. i Dont understand that part. I understand the rest though.

Need Help, No OS

Hi,
The N4 of my wife has big problem.
I wiped in "custom recovery" (TWRP) some stuff for return all in factory settings (this was stupid, I know)
Now, when she reboots on recovery, there is a message "No OS installed !"
How fix this, please ?
Edit: I tried with a toolkit, everything seems good, but when I boot, I have only the google screen.
Edit 2: I send with adb: image-occam-jdq39.zip, but when it failed when I try to install it.
Thanks.

https://developers.google.com/android/nexus/images#instructions

^^ negroplasty has given you the link to download the latest factory image. You can flash that to your phone no problem as long as you can boot into the bootloader (from off state, hold power + vol down)

Connect phone to pc, go to bootloader
Throw the image you want to flash to the same folder where your adb tools are
Open terminal, change directory to that folder
Then write: ./adb push EXACTNAMEOFROM.zip /sdcard/
Example of me trying to adb push Xylon
Then go to "Install" on your phone, sdcard, select the image, swipe to flash and that's it, hope this clears it.

[Q] Stuck in twrp recovery after update

Morning everÿone,
I am currently stuck in twrp recovery with a sprint lg g2. I factory reset my phone last night, and all was well. Accidentally clicked on the ota update that was showing it had downloaded. Phone rebooted into recovery. I have tried to restore from a backup I made last night after the hard reset. Phone says it was successful, I click reboot, comes right back up into recovery after the lg symbol.
I am new to android, so I am not familiar with how to use adb. I am fine with losing all the info that is on my phone, no biggie, just need the phone working again.
I have a zip saved to my phone, from when I was rooted before, which I tried to flash. It takes about 30 seconds, and then says that it failed.
Any help, pointers, directions would be amazing.
Also, have never used side loader, but have heard of people loading roms this way, to get back working.
Please and thank you

Do u have twrp or cwm
Sent from my LG-D802 using xda app-developers app

Hi! you have to follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=2451696
it worked for me

lingarajug said:
Do u have twrp or cwm
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
twrp

rienkar said:
Hi! you have to follow the instructions here:
http://forum.xda-developers.com/showthread.php?t=2451696
it worked for me
Click to expand...
Click to collapse
Great. thank you. I do not have adb access, if i go into advanced, and then terminal command, i have a list of folders, paths, something like that, that I can click on. which would I need to go to, in order to type in the command?
"Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!"

DopePedaler said:
[/COLOR]Hi everyone, I am stuck in recovery in twrp at the moment, accidentally clicked to download the OTA. When i go into advanced, and terminal command, where would I go to enter the following command?
"If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!"
Click to expand...
Click to collapse
In terminal command, there is a choice for select. I clicked that, and then I typed in the following command in terminal command:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
once this was done, i backed out, and selected reboot, power off. phone powered up, and went right back into twrp recovery...What did I do wrong?

This is from tomajo2 in another thread. That OP was stuck in CWM, but in case the fix is similar, here you go:
I have a better idea to repair this problem.
1- You have to install LG Phone drivers and Android.sdk
2- Download TWRP for LG G2 and paste it to platform-tools folder in android.sdk direction on your PC
3- Go to recovery and plug the phone to PC
4- Next, in your phone recovery CWM you have to choose install zip and install.zip from sideload. Then wait for install the drivers of phone on your PC.
5- Open console in folder platform-tools (shift + PPM) and type adb sideload nameofTWRPfile.zip
6- Then reboot phone
7- Next enter to another time to recovery (now will be TWRP recovery)
8- Enter advanced and terminal console
9- Choose select and type the second option from this site: http://forum.xda-developers.com/show....php?t=2451696
10- Reboot phone
In my case is everything ok, but you have to remember that you can't install any OTA on custom ROM !
Sorry, but my english is not so good

Thank you,
I just received and installed an OTA update today. I was stuck in twrp and this saves my butt.
I used the terminal command in TWRP menu and type in the dd code and reboot the phone. Make sure you check twice that you have typed it in correctly or you could brick your phone.
Cheers.
DopePedaler said:
Great. thank you. I do not have adb access, if i go into advanced, and then terminal command, i have a list of folders, paths, something like that, that I can click on. which would I need to go to, in order to type in the command?
"Then you should be able to successfully reboot your phone via the TWRP menu option, or via a simple reboot command in adb.
If you DONT have ADB access (because of an early build of TWRP), you can simply use TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You'll have to type that whole thing out, and be VERY careful with spaces and punctuation. One wrong letter and you could nuke your phone.
After that finishes, you can reboot and continue on your happy way!"
Click to expand...
Click to collapse

kcharng said:
Thank you,
I just received and installed an OTA update today. I was stuck in twrp and this saves my butt.
I used the terminal command in TWRP menu and type in the dd code and reboot the phone. Make sure you check twice that you have typed it in correctly or you could brick your phone.
Cheers.
Click to expand...
Click to collapse
When you are typing this in terminal command, where are you typing it at? I believe that I typed it in correctly, checked twice. Backed out, went to reboot, and power off. When comes back on, goes back into recovery.
I see at the top of terminal command, there is a line with / in it.
If you press select, it takes you to a line where you can enter in the full command, which I did before.

When I press select,in terminal command this is what is I type in, checked to make sure I am typing it in correct.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Once I type this in, I hit go, in the lower right.
Takes me back out one screen
I then go to reboot
I've tried big power off and system
Once loads back up, it goes right back to twrp recovery.
Where am I going wrong? Where it says by name in the command, do I need to change that, or does it stay by-name? I've been typing it In as by name like the command shows.

I would love to help but what you did is exactly what I did. However regarding the go button I am not so sure. Why don't you try hitting enter instead.

How do i boot this phone

i can't get into cwm after i got installation aborted on the bravo for CM7.... i already have a backup through recovery, whats the key combo to get into cmw?

jafferkhan said:
i can't get into cwm after i got installation aborted on the bravo for CM7.... i already have a backup through recovery, whats the key combo to get into cmw?
Click to expand...
Click to collapse
Can you still boot into the Android operating system itself? If you can, then you can download a terminal emulator from Google Play and use it to boot into recovery through its command line. Here's what you would need to type in, only type what is in bold:
su
(This requests superuser/root permissions for the app. When you get this, wait for a message to come up asking if you want to give it root permissions and then grant the app permissions.)
reboot recovery
This will make the phone turn off, and it will boot into recovery. If it doesn't boot into recovery, then the recovery itself is probably broken.
I'll try to get the button combo for recovery ASAP, just in case the terminal emulator method does not work.
EDIT: Here is how to boot into recovery with the button combinations:
1) turn off the phone, take off the cover, and remove the battery.
2) put the battery back in
3) hold down the volume down key. CONTINUE TO HOLD IT DOWN AS YOU THEN HOLD DOWN THE POWER BUTTON TO TURN THE PHONE ON AGAIN.
this method is to get into stock recovery, but you can try it to get into CWM. Post back what happens when you try these methods.