Develop Bugs

[Q] how do i install cwm 3.0.0.5

can someone please explain it to me very detailed? i dont understand so much from the tuts i have read.

Are you rooted and s-off`d?

Blinkydamo said:
Are you rooted and s-off`d?
Click to expand...
Click to collapse
yes, i have

Put cwmod on the root of your sd card. Download terminal emulator from the market. In terminal emulator type
su
press enter
then type
flash_image recovery /sdcard/nameofrecovery.img
press enter
Replace nameofrecovery with whatever the name of the file is.
When you reboot into recovery it should be cwm 3.0.0.5 (should be amber font)
Sent from my Desire HD using XDA App

it shows file not found, even when i write the name of the file.

From the htc stock rom, you need to do it from your pc using fastboot. It won't work with terminal emulator.
Which rom are you running?
Do you have adb installed on your pc?
If you have fastboot, put the recovery.img in the tools folder of your sdk, start up your phone to the bootloader, connect your phone with the usb cable then open a command promt, navigate to the tools folder and type
fastboot flash recovery nameofrecovery.img
Press enter then type
fastboot reboot
Should take aboot 5 seconds
Sent from my Desire HD using XDA App

pwraggcan said:
From the htc stock rom, you need to do it from your pc using fastboot. It won't work with terminal emulator.
Which rom are you running?
Do you have adb installed on your pc?
If you have fastboot, put the recovery.img in the tools folder of your sdk, start up your phone to the bootloader, connect your phone with the usb cable then open a command promt, navigate to the tools folder and type
fastboot flash recovery nameofrecovery.img
Press enter then type
fastboot reboot
Should take aboot 5 seconds
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i am running revolution HD, i just tried that and it said failed <remote: not allowed>
why must it be so damn hard? damn crap

Are you eng s off?
Try using adb shell from your command prompt then use the same commands you used in terminal emulator.
Sent from my Desire HD using XDA App

pwraggcan said:
Are you eng s off?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i think so, http://forum.xda-developers.com/showthread.php?t=857537 i used that tut. is it so many different S-OFF's ?

Ok, with that s off method you can't use fastboot commands. Did you try the commands in adb shell?
Sent from my Desire HD using XDA App

pwraggcan said:
Ok, with that s off method you can't use fastboot commands. Did you try the commands in adb shell?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i dont know, maybe. but im trying this now http://forum.xda-developers.com/showthread.php?t=855403 will it be a problem that i used the other S-OFF and now this?

I don't know. First try the commands in adb shell from your pc.
Sent from my Desire HD using XDA App

pwraggcan said:
I don't know. First try the commands in adb shell from your pc.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
if you mean the commands that is written in cmd, then i have already tried it, and it failed.

In the command prompt, navigate to your sdk then type
Adb devices
Press enter
Your device's serial number should show
Then type
Adb shell
Press enter
If you get a $ type su then press enter
Then enter the same commands you used in terminal emulator
Why do you want cwm 3? It's generally only for 2.3 roms.
Sent from my Desire HD using XDA App

pwraggcan said:
In the command prompt, navigate to your sdk then type
Adb devices
Press enter
Your device's serial number should show
Then type
Adb shell
Press enter
If you get a $ type su then press enter
Then enter the same commands you used in terminal emulator
Why do you want cwm 3? It's generally only for 2.3 roms.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I just installed it now thats why i want it, but do you know how i get back to the older cwm? do i just flash it in ROM manager?

Excellent. What worked finally?
To go back to an older version use rom manager or the use same way you upgraded.
Sent from my Desire HD using XDA App

You could try this, i haven't tried it myself so don't know if it works, but read it somewhere here on xda.
Go to this path with any file manager.
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
And copy that file to another folder. Then copy the name of that recovery (2.x.x.x) and then rename your 3.0.0.5 recovery with the old recovery name and just copy the new (2.x.x.x) to this path. (Just say yes to overwriting the file).
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
Then reboot and then boot into recovery and that should have changed the cwm from old to new. The color should be orange now and not green, if still green it didn't work.
If it doesn't work just restore the old recovery .img you've copied earlier (2.x.x.x).
Regards Dousan
e: Lol you fixed it while i was typing... Nice

pwraggcan said:
Excellent. What worked finally?
To go back to an older version use rom manager or the use same way you upgraded.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
i used this and then the command worked

Cool. Glad you're sorted. Good luck with cm7.
Sent from my Desire HD using XDA App

Dousan said:
You could try this, i haven't tried it myself so don't know if it works, but read it somewhere here on xda.
Go to this path with any file manager.
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
And copy that file to another folder. Then copy the name of that recovery (2.x.x.x) and then rename your 3.0.0.5 recovery with the old recovery name and just copy the new (2.x.x.x) to this path. (Just say yes to overwriting the file).
/mnt/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries
Then reboot and then boot into recovery and that should have changed the cwm from old to new. The color should be orange now and not green, if still green it didn't work.
If it doesn't work just restore the old recovery .img you've copied earlier (2.x.x.x).
Regards Dousan
e: Lol you fixed it while i was typing... Nice
Click to expand...
Click to collapse
Hello
just tried that worked flawlessly
thank you

[BOOTANIMATION]Samsung Stock Boot Animation

Well, I did a little search for the SAMSUNG STOCK boot animation since I don't like the one in Custom and I just like the Stock one to just show off
and here it is...
I know you can found this in stock rom or img or whatever, but this one is just for convenience
I take no credit since Samsung made it, not me
How to use it?
Code:
adb remount
adb push bootanimation.zip /system/media/

Tried replacing using root explorer and didn't work. I'll try adb when I get to my PC.
Sent from my Galaxy Nexus using xda premium

spunks3 said:
Tried replacing using root explorer and didn't work. I'll try adb when I get to my PC.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Works for me...I used ES File explorer

used root explorer and it worked fine, only had to change permissions thank you

ytwytw said:
Well, I did a little search for the SAMSUNG STOCK boot animation ...
Code:
adb remount
adb push bootanimation.zip /system/media/
Click to expand...
Click to collapse
Or you can make it flashable
View attachment Samsung_bootanimation_Nexus.zip
Feel free to use this zip as template to flash other bootanimations just replace the original

Req boot animation

OK I would like to know if any one would like to help me out.
I have a boot animation (call of android)
It not the rite size and I don't have a PC to fix it. I was wondering if any one can be of service and can do it for me.
Please and thank you ^_^
Sent from my Galaxy Nexus using xda premium

Ante one
Sent from my Galaxy Nexus using xda premium

Is it the same one as in
http://forum.xda-developers.com/showthread.php?t=1364044&page=1
?
Also see mods of that one later in the same thread, here:
http://forum.xda-developers.com/showpost.php?p=26795464&postcount=275
Otherwise, get back in touch.... re-sizing's no biggie.

That the one I still see it the not to size
Sent from my Galaxy Nexus using xda premium

What do you actually see?
Maybe try deleting the bootanimation.zip on your phone directly and then re-flash:
Assuming you're on windows and the zip file bootanimation_droid_loop.zip is in your downloads directory
Code:
adb root
adb remount
adb shell
rm /system/media/bootanimation.zip
rm /data/local/bootanimation.zip
exit
adb push %userprofile%\downloads\bootanimation_droid_loop.zip /data/local/bootanimation.zip
adb reboot

I don't have a PC
Sent from my Galaxy Nexus using xda premium

Sorry... You did say that.
But what do you actually see on your screen when you boot?

galaxy nexus stuck on boot animation screen

I used rom toolbox to change the fonts of my phone.The first time it reebooted properly.But the second time i installed a font and went into reboot it wasnt starting up.The phone just stays in boot animation screen and the colors just keeps moving.It stayed like this for about 10 minutes so i removed the battery and went into recovery mode and did a factory rest but no use.I am running Jellybean 4.1.1. ANY HELP ??

Re-flash your rom.
If you aren't on a custom one or don't have a rom.zip on your phone...check my guide.
Post 3.
Fonts reside in /system/fonts/
You can probably rip them from anyone else's rom.zip and push them (as explained in post 3) if you aren't on a custom rom.
|
|
|
|
V​

I cant exactly understand what to do.
Can you show me any other steps or provide any detailed info ??

Post one to set up adb.

adb is installed but do i need to transfer any files from pc to nexus ??
if i enter into recovery how do i move the file ??

Jubakuba said:
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu). Navigate to recovery and select it with the power button.
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.
Code:
adb push NAMEOFZIP.zip /sdcard/
(Hit enter)
You may have to reboot recovery to get the file to show up. Now follow the guide above for flashing a rom to get you booting again.
---------------------------------------------------------------------
Did you install a tweak that modified only a file or two on your phone? (Find this out by opening the .zip and looking in the folders (ignore META-INF). Good news! We MAY be able to recover you completely. If this doesn't work...you'll have to follow another method.
Get your phone into fastboot (the boot-menu that allows you to select recovery/reboot/etc). Navigate to recovery and select it. Start up ADB. Pull the files that were modified out of the stock rom's .zip (using whatever tweak you were installing as reference to find what was changed) that you're on into the C:\android-sdk-windows\platform-tools folder. Now we're going to push these files onto your phone...replacing the tweaked ones and hopefully getting you booted again. Use this code, but change the values of the file name and where it should reside. This is only an example!
Code:
adb shell
(Hit Enter)
Code:
su
(Hit Enter)
Code:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
(Hit Enter)
This will mount your system so you can write to it.
Code:
exit
(Hit Enter)
This should exit shell and allow the use of adb commands again. You may need to type it a couple of times (until the #_ changes back to the platform_tools> prompt).
Code:
adb push framework-res.apk /system/framework/framework-res.apk
(Change the location and the file name(s) to the correct values. Press enter after each file that you need to replace).
***I take no responsibility for what happens to your phone due to following this guide! That being said, not only am I sure you'll be fine...but there are an endless amount of users who would be glad to help if you need it.***
Click to expand...
Click to collapse
Ok.
Give me some info here.
Are you on a custom rom?
If so...use the part before the red line.
If not...use the part after.
To use this option, however...
You'll need access to working font files.
http://forum.xda-developers.com/showthread.php?t=1667418
Bam. First rom post I found. Download it.
Rip fonts from /system/fonts/
Use the code above and push the files (changing the name of the file...and the location, as stated).

it worked......thanks a lot
now if i use rom toolbox will the problem occur again ??
if i use any roms stock or custom how do i install them ??And which one should i use ??
cheers......

suckerboy said:
it worked......thanks a lot
now if i use rom toolbox will the problem occur again ??
if i use any roms stock or custom how do i install them ??And which one should i use ??
cheers......
Click to expand...
Click to collapse
recommend using fastboot over toolkit... a lot of problems occur because they used toolkit...
Sent from my Galaxy Nexus using xda app-developers app

kyokeun1234 said:
recommend using fastboot over toolkit... a lot of problems occur because they used toolkit...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
It's not a toolkit. It's an App that contains ROM Manager, Titanium Backup(that's what I call it), CPU manager, theme manager, and bunch of other manager.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^

Dragn4rce said:
It's not a toolkit. It's an App that contains ROM Manager, Titanium Backup(that's what I call it), CPU manager, theme manager, and bunch of other manager.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
Click to expand...
Click to collapse
Lol read it wrong. My mistake
Sent from my Galaxy Nexus using xda app-developers app

kyokeun1234 said:
recommend using fastboot over toolkit... a lot of problems occur because they used toolkit...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
It seems Jellybean introduced something that brought some incompatibility with some fonts (and with it might have gotten to affect apps as well, as expected), but some still work (i've tried a few, works flawlessly, backup before applying). Checkout this thread out.
Dragn4rce said:
It's not a toolkit. It's an App that contains ROM Manager, Titanium Backup(that's what I call it), CPU manager, theme manager, and bunch of other manager.
--------------------------------------------------
If I have helped you.... hit that sexy thanks button. ^_^
Click to expand...
Click to collapse
There's other ways to do it: if I'm not sure if something works, I rather know how it's done at source level for example; if i cannot, then just seach/confirm how other people are doing it, with good results.

Can't flash any 4.3 rom

I'm on twrp 2.3.6.1 and can't flash any 4.3 ROM. Any fix? And twrp says no open recovery script for your device. I'm on a rooted stock 4.0.4
Sent from my SGH-M919 using xda premium

U need a newer twrp 2.6.1.0 would a be a good version to use. 2.6.3.0 has a few bugs
Sent from my SGH-T989 using Tapatalk

Ahh thank you
Sent from my SGH-M919 using xda premium

Is there a way to update via goo manager app? I tried to update by doing menu>install open recovery script. But it doesn't recognize my device. Anything I could do? I don't have an Android to USB cable handy.
Sent from my SGH-M919 using xda premium

'Murica said:
Is there a way to update via goo manager app? I tried to update by doing menu>install open recovery script. But it doesn't recognize my device. Anything I could do? I don't have an Android to USB cable handy.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
You can update by grabbing the recovery IMG file from their site and use android terminal emulator to install it!
su
dd if=/sdcard/openrecovery-twrp-hercules-2.1.8.img of=/dev/block/mmcblk0p22 <- (this is for Hercules obviously)
And the "openrecovery..." Is the one you downloaded and place it in the root of sdcard make sure it's word for word and you should be good to go!

PhlexPlexico said:
You can update by grabbing the recovery IMG file from their site and use android terminal emulator to install it!
su
dd if=/sdcard/openrecovery-twrp-hercules-2.1.8.img of=/dev/block/mmcblk0p22 <- (this is for Hercules obviously)
And the "openrecovery..." Is the one you downloaded and place it in the root of sdcard make sure it's word for word and you should be good to go!
Click to expand...
Click to collapse
So I type 'SU' and hit enter. Than I copy and paste ' dd if=/sdcard/openrecovery-twrp-hercules-2.1.8.img of=/dev/block/mmcblk0p22' replacing ' openrecovery-twrp-hercules-2.1.8.img' with the name of my recovery and then replacing ' mmcblk0p22' with 'Hercules' and hitting enter?
Sent from my SGH-M919 using xda premium

'Murica said:
So I type 'SU' and hit enter. Than I copy and paste ' dd if=/sdcard/openrecovery-twrp-hercules-2.1.8.img of=/dev/block/mmcblk0p22' replacing 'openrecovery-twrp-hercules-2.1.8.img' with the name of my recovery and then replacing ' mmcblk0p22' with 'Hercules' and hitting enter?
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
No not quite, if you're using the phone that's appropriate for the forum you just copy and paste
Code:
su
dd if=/sdcard/openrecovery-twrp-hercules-2.1.8.img of=/dev/block/mmcblk0p22
And openrecovery-twrp-hercules-2.1.8.IMG with whatever your name of the IMG file is, so if it's openrecovery-twrp-hercules-2.6.1.0.img then that would replace it. The block mmcblk0p22 does not get changed or else your device will brick!
So to clarify:
The
Code:
dd if=/sdcard/openrecovery-twrp-hercules-2.1.8.img
is the path to where the img file for TWRP is. If you're downloading 2.6.1.0, and move the img file to the root of your SDcard, then it might be something like
Code:
dd if=/sdcard/openrecovery-twrp-2.6.1.img
Now the
Code:
of=/dev/block/mmcblk0p22
is where the img is going to be written to. From what I see, the last bit
Code:
mmcblk0p22
varies on the device and where the recovery installs. It's a different location for the Galaxy S4 compared to the T989 (also known as hercules).
Say if you were to rename the download to something easy to type out, like just recovery.img and placed in the root of the sdcard, then it would look like
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Then you should be able to boot into recovery and it should be updated!
If something goes wrong, your device will brick, so make sure you download the right file. I flashed the .tar by accident on a friends phone, but Odin can easily fix it by flashing it with that.
Sorry for the short responses, I was on my phone when I was replying!