Database Users

[Q] Braincapped

Hey guys i have this old HTC Tattoo i would like to use for a while i need to test things on.
HTC Tattoo (Orange)
S-on
1.6.61.43 custom firmware
rooted
But i have a problem, i need to get a custom ROM on it.
so far:
1. Would not accept sim unlock code
1. Rooted it once
2. used RUU_Click_Orange_UK_1.67.61.43_release_signed_NoDriver becouse it was needed to accept the simunlock code
3. Lost root, rooted it again with Universal root becouse old method didn't work anymore.
4. Everytime i tried to open recovery menu, it shows a picture with a orange triangle and the phone next to it
5. Installed ROM manager and put Clockwork, nothing.
6. Tried to back up, install rom from ROM Manager, still nothing =(
HELP D:!
Question: How do i fix it so i don't get this trinagle thing and i can go into the recovery menu
EDIT: I forgot to add, i THINK i made the SDCard a Goldcard, but i'm not sure... how do i cheak?

still no reply? kay:

I am going to help you
I am going to help you when I come home from school I know what you have to do and how.

Shaumaaa said:
I am going to help you when I come home from school I know what you have to do and how.
Click to expand...
Click to collapse
=0 i'm back from school

Shaumaaa said:
I am going to help you when I come home from school I know what you have to do and how.
Click to expand...
Click to collapse
Are you back D: ? i still need help

answer
1. That triangle is stock recovery which isn't useful for installing custom roms.
2. You need custom recovery.
3. You need adb.
4 You can install recovery like this one click http://forum.xda-developers.com/showthread.php?t=950759 or manualy using cmd(adb needed).
If installing manualy: You need flash_image and recovery.img .
For cmd, commands are:
adb push recovery.img /sdcard/recovery.img
adb shell
su
flash_image recovery /sdcard/recovery.img
exit
exit
Hope this was helpful for you
Sorry if you waited too much, I didn't have time to answer you.

Shaumaaa said:
1. That triangle is stock recovery which isn't useful for installing custom roms.
2. You need custom recovery.
3. You need adb.
4 You can install recovery like this one click http://forum.xda-developers.com/showthread.php?t=950759 or manualy using cmd(adb needed).
If installing manualy: You need flash_image and recovery.img .
For cmd, commands are:
adb push recovery.img /sdcard/recovery.img
adb shell
su
flash_image recovery /sdcard/recovery.img
exit
exit
Hope this was helpful for you
Sorry if you waited too much, I didn't have time to answer you.
Click to expand...
Click to collapse
I followed the instructions it didn't help, still same problem
no errors with the .exe, but no dice either
flashpermission denied with manual cmd
not enough memory on the device
in rom manager it says i have clockworkmod 5.0.2.0, might be the the problem that my phone is on orange or that it is S-on ? becouse i'm pretty sure it has custom recovery and it is rooted
i was able to root with this method before i used "RUU_Click_Orange_UK_1.67.61.43_release_signed_NoDriver" update
Now i am not able to use that root method, maybe it would have worked before i used it...
How do i downgrade or whatever from this RUU ?

Adb
Do you have adb drivers installed?

Shaumaaa said:
Do you have adb drivers installed?
Click to expand...
Click to collapse
Yes

Don't know then, I had site with better commands which helped me but it's dead now so I can't access them..

[Q] Recover After Bootloop (Embarrassing Story)

Tried to flash the deodexed stock 4.2.2 update through TWRP a few days ago and my N7 started bootlooping
Because I'm out of practice, I didn't make a nandroid beforehand, and now I can't locate the adb files necessary to push recovery and reflash the os.
Can someone help me remember what the f*ck I'm doing and direct me to where I can get an adb cheatsheet + the necessary files OR be super awesome and provide me some steps to follow?
Thanks so much in advance. Can't believe I messed this up so much

Trickee360 said:
Tried to flash the deodexed stock 4.2.2 update through TWRP a few days ago and my N7 started bootlooping
Because I'm out of practice, I didn't make a nandroid beforehand, and now I can't locate the adb files necessary to push recovery and reflash the os.
Can someone help me remember what the f*ck I'm doing and direct me to where I can get an adb cheatsheet + the necessary files OR be super awesome and provide me some steps to follow?
Thanks so much in advance. Can't believe I messed this up so much
Click to expand...
Click to collapse
Can you get into bootloader with power+vol down?

boot into the bootloader, then via fastboot..
fastboot boot recovery recoveryname.img(press enter)
remember to put the recovery img file in the same folder that fastboot is located, on your computer.

bootloader's good to go and I'm in recovery but I need a way to get the rom on my tablet. Mounting sdcard doesn't appear to do anything while connected to my pc
EDIT: tried the CWM flash from sideload option and my command line says it "cannot read 'sideload'" do I need to start/restart the server another way? I feel like a total noob, lol

adb push rom.zip /sdcard/

Pirateghost said:
adb push rom.zip /sdcard/
Click to expand...
Click to collapse
started the daemon then got error: closed

Trickee360 said:
started the daemon then got error: closed
Click to expand...
Click to collapse
Did you update your adb binary as expressed with the 4.2.2 update?
Sent from my Galaxy Nexus

Pirateghost said:
Did you update your adb binary as expressed with the 4.2.2 update?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
no Can I do that through the sdk manager or do I have to update the sdk itself?

sdk manager can handle it

Pirateghost said:
sdk manager can handle it
Click to expand...
Click to collapse
Ugh. SDK manager won't install anything. EIther it says whatever package I'm working on requires API17 (which I'm trying to get, lol) OR it just plain can't "find" the package because acces is denied? What am I doing wrong?

No os installed

Guys help me!
I install android 4.3 on my phone, however I did not do the backup and by mistake I've downloaded the wrong rom, now my phone a message appears in the bootloader "in the OS installed"
I'm desperate with my phone only in recovery mode, please help me fix!

sprafael said:
Guys help me!
I install android 4.3 on my phone, however I did not do the backup and by mistake I've downloaded the wrong rom, now my phone a message appears in the bootloader "in the OS installed"
I'm desperate with my phone only in recovery mode, please help me fix!
Click to expand...
Click to collapse
Do you have a custom recovery installed? If so, load a .zip rom and push it via custom recovery...
.... If not, use ADB to push a reflash of a clean install of 4.3
instructions here my thread
http://forum.xda-developers.com/showthread.php?t=2376681

More info.what Phone mark modelo etc ?
Sent from my XT910 using Tapatalk 4 Beta

mc704 said:
Do you have a custom recovery installed? If so, load a .zip rom and push it via custom recovery...
.... If not, use ADB to push a reflash of a clean install of 4.3
instructions here my thread
http://forum.xda-developers.com/showthread.php?t=2376681
Click to expand...
Click to collapse
i do not have a custom recovery, the only thing it has in the cell and the image I downloaded wrong, my phone is in recovery screen that comes with it when I turn the volume button, after that I do not know what else to do, because I have no how to transfer the image to the correct cell to update, so I need to know how to transfer the image to the correct device

sprafael said:
i do not have a custom recovery, the only thing it has in the cell and the image I downloaded wrong, my phone is in recovery screen that comes with it when I turn the volume button, after that I do not know what else to do, because I have no how to transfer the image to the correct cell to update, so I need to know how to transfer the image to the correct device
Click to expand...
Click to collapse
if you are able to boot to recovery. you have to be in fast boot...
you can either use fastboot to flash over
or
boot into recovery and apply a rom via ADB sideload

mc704 said:
if you are able to boot to recovery. you have to be in fast boot...
you can either use fastboot to flash over
or
boot into recovery and apply a rom via ADB sideload
Click to expand...
Click to collapse
how to apply the room via ADB SIDE load, because I saw that option, so I do not know how to use

sprafael said:
how to apply the room via ADB SIDE load, because I saw that option, so I do not know how to use
Click to expand...
Click to collapse
open command prompt with adb loaded
type adb sideload romname.zip
the rom should be in the same folder the adb/fastboot tools are located

mc704 said:
open command prompt with adb loaded
type adb sideload romname.zip
the rom should be in the same folder the adb/fastboot tools are located
Click to expand...
Click to collapse
the fastboot do you explain this link??
http://forum.xda-developers.com/showthread.php?t=2376681
I'm downloading the android SDK at this time
let's see if I understand
put the phone in adb sideload
will open the CMD in the fastboot folder,
type in adb sideload image-occam-jwr66v.zip

Flashable zip not factory image, try cm10
Sent from my Nexus 4 using xda app-developers app

[Q] D801 - Can no longer boot after bad flash

I would really appreciate some help on this one... I attempted to flash the updated Mahdi Rom (09/20 build) this morning. I'm using the latest Philz Recovery if that matters. I performed the normal wipe procedure and when I went to flash the rom it told me the file was invalid. I think I might have tried to use a zip that wasn't fully downloaded.
I didn't have any other recoveries on my phone (I know... not smart) so I need to figure out how to flash a new rom without using recovery. I'm not completely hopeless and I'm willing to do what it takes to get my phone back!
Any help would be great! Thanks.

Have you tried adb? Your phone will be called sideload when you command adb devices.
Sent from my LG-D800 using Tapatalk

I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?

Rogueharvest said:
I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?
Click to expand...
Click to collapse
You can load adb on Mac. I believe there's a zip somewhere on xda with only the three files need, or download the package from Android. Place it in whatever your username folder is too make life easier. Also add ./ (dot slash) before every command.
Here's the command order for my setup.
cd Android/platform-tools
./adb devices
./adb sideload **DRAG FILE INTO TERMINAL**

Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Update: I think I figured it out. The command prompt needed to be reinitiated.
Thanks again for you help! Moments like that are always a little scary!

Rogueharvest said:
Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Click to expand...
Click to collapse
Does it recognize sideload when you type ./adb devices? If not and you're in adb on Philz unplug/replug the charger.

[Q] GAPPS failed to flash/install, what are my options?

So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?

sirmot said:
So I decided to install PA 4.6 BETA4 on my Nexus 4, 4.3 JWR66Y Phone which is unlocked and rooted. I used the Nexus Root Toolkit to install the latest TWRP recovery, put the pa_mako-4.6-BETA4-20141007.zip and pa_gapps-stock-4.4.4-20141011-signed.zip onto my phone. Went into recovery to flash the two. The PA ROM went successful, tried flashing the gapps and it just says failed. I tried redoing the ROM flash then gapps again but that doesn't work.
I had the dumb idea of moving my nandroid backup to my computer and now I can't transfer it back to my phone using adb sideload. I go into ADB sideload in TWRP, and it just says no devices found when trying to transfer maually. When I try using NRToolkit, it fails as well.
Any advice? I feel like I've searched everywhere. I don't know what the next step to take is. Maybe Flash Stock + Unroot option on the NRToolkit? Have I somehow flashed incompatible zip files?
Click to expand...
Click to collapse
UPDATE: I got the gapps to install successfully. I installed Wifi File Explorer through NRToolkit in order to transfer files to my phone. And transferred the same exact file to my phone. I tried flashing the file and it worked... I'm guessing the wired transfer corrupted the file somehow. Thank you NRT for that option to install apks.

Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord

XxLordxX said:
Hi,
Good to know that you managed to get it working . Could you add a [SOLVED] tag on the title of your thread?
Also, I'd like to point out that when you tried to copy the backup file via adb sideload it had a reason to not work! Adb sideload was born to flash zips which are transfered via adb to the device. Loading then as soon as they are loaded. To copy the files back to your device using adb you should have used the "adb push" command, which is like a "copy/paste" on the shell . Hope this helps in the future.
~Lord
Click to expand...
Click to collapse
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.

sirmot said:
Ah of course that makes sense. I think I tried just pushing the file when I was in the bootloader as well, but it also gave me devices not found. Not sure why, but anyways thanks for the reply. Hopefully this might help out someone.
Click to expand...
Click to collapse
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505

XxLordxX said:
Hi,
In bootloader you mean fastboot right? If so, you can't use adb on this mode. To push a file via fastboot is only the stock image using "fastboot install" or "fastboot boot".
~Lord
"Dream On! Dream Until Your Dreams Come True!" - Dream On (Aerosmith)
Sent from my GT-I9505
Click to expand...
Click to collapse
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?

sirmot said:
Oh I see. So the adb push can only be used when the phone is on normally and connected via adb? Is there a way to transfer files to a phone if it were stuck in fastboot?
Click to expand...
Click to collapse
Hi,
If you're stuck in fastboot you can flash a recovery or use the "fastboot boot" to boot in recovery and then use adb push from there .
~Lord