Hi to all
I'm starting to try root my tattoo
After installed Android SDK i've followed any (how-to-root) all other most commercial android-phones like magic, hero, etc.
But nothing happens on my tattoo. Many "how-to-root" guides tells to begin the rooting starting from two points.
or flashing with a rooted ROM
or typing "adb shell" command and blablabla
I think that the good way to root our tattoo is the second way.
I've tried to inject the superuser in my tattoo but no hope for the moment.
Your support is much welcomes
hi all
hi ppl im sorry to ask you such s dumbass question and please exxcuse my speling hahaha wel eniway i read about that ne guy that accidently locked his fone hahaha wel i did the same and i wil apreciate it alot if somebody can help me unlocking i tried everyting that you all said and nothing worked and somebody said that you must google for that AdbWin.zip and i did but i dont know what to do with it i have like now idea what to do and i dont even know how to reset it if anybody can tell me how then ill apreciate it as wel hahaha. please somebody HELP ME i beg youi surfed the internet for answers but found nothing, some times this internet is [email protected] useless im about to start crying hahaha so any help as soon as posible wil help allot o yeah and i cant access anything o i have no idea what to do
@Sengine
you cant use the methods out there to root your tattoo. Most methods out there are for the android cupcake i.e 1.5(dream, hero etc) and the tattoo runs android 1.6. Also the first step to rooting your phone is getting a custom recovery image, and as far as i know no such recovery image exists for the tattoo yet. I had a tattoo for a week, sold it and got a hero instead.
@above
Can you at least turn your phone on? try turning it on pressing power and back if u can enter fastboot mode (three android guys on skateboards). then try flashing your phone with the official RUU. Instructions are available on this forum itself. But if you cant even turn your phone on..and the computer doesnt recognise it at all. im sorry to inform you, you may have bricked your phone.
@Sengine
Donot use the methods out there unless they specify that they are safe for the tattoo. else you may brick your phone.
@eldrid: where does the custom recovery image which works on the hero comes from? perhaps we can contact its developer and ask for help.
the most "famous" recovery images for G1&Magic&Hero&Nexus One are made by Amon Ra
Thank You for your support...
But i want to begin a discussion about "which first steps to do for root Tattoo ???"
- Take a recovered ROM and working on to try to have superuser?
- Try via ADB SHELL?
- etc...
Please post your comments.
Have you taken a look at superboot for t-mobile pulse on modaco forum?How the boot.img has been modified?Maybe that will help.
yash08 said:
Have you taken a look at superboot for t-mobile pulse on modaco forum?How the boot.img has been modified?Maybe that will help.
Click to expand...
Click to collapse
Please supply a link to that forum thread, if you can. Cheers.
Here is a link mate:
http://android.modaco.com/content/t...n-1-5-superboot-rooting-without-a-custom-rom/
Click to expand...
Click to collapse
Thanks. Reading that said article now.
EDIT: I think we may have stuck gold....
Any development on this regarding Tattoo?
I can't understand why we cannot downgrade our Donut roms to cupcake like other devices with the G1 method. Since its the same ROM, what is special about this if we have both kernels we can compare differences bassically so find out the method, true?
MiSSigNNo said:
I can't understand why we cannot downgrade our Donut roms to cupcake like other devices with the G1 method. Since its the same ROM, what is special about this if we have both kernels we can compare differences bassically so find out the method, true?
Click to expand...
Click to collapse
Donut and Cupcake are two different setups. One has patches and stuff from cupcake, the other is just a vanilla cupcake.
The thing is that we're stuck on getting the device to allow rooting - the same issue with the Eris. It's driving us insane, but perisistance and a few beers should carry us to the finishing line.
All the G1 exploits have been found and fixed in the HTC Click (Tattoo), so we're pretty much stuck. Unless fastboot can do us a favor, well....
You may want to do the process outlined in modaco's "Superboot" thread. If you can get your device to reboot and load into Android when you upload that boot.img file, try a su and see if we have root.
Other than that, it's a no-go. We'll get there, we need time to revise the plan.
I would recommend Tattoo people and devs to look into kernel exploits and bootloader exploits, like Eris people are doing right now, it may the the last chance of actually being able to root the Tattoo, unless somebody gets their hands on a HTC signed S-OFF bootloader ;P
Related
Just to begin, normally i am pretty on top of stuff when it comes to messing with hardware/software, so i figured this flashing will be easy.
I started off with rooting my Rogers HTC Dream, which worked out just fine.
Then i tried to install the cyanogen mod, and now i cant boot past the rogers logo.
since then i have tried installing android 1.5 radio, cyanogen's recovery image (1.3.1)
i couldnt find a guide for installing any of these, so essentially the only thing i did was enter fastboot, run fastboot boot recovery.img (the same one i used for rooting) and update from update.zip on each of the things i tried to install.
Seems that I missed out on the initial preperation.
Also, Nandbackup didnt work when i tried to use it, it would just fail every time, so i am left without a backup file of my previous state.
So my question is: What can I do to A:get cyanogen's mod working, or B:restore the unmodified rogers-branded rom to my phone
Thanks guys, any help is greatly appreciated. Just got this phone yesterday, and I love it, but now i seem to have gone and messed it up
I have a bunch of bad backups, they have only the boot.img part of several backups.
K here is the order I did anything.
Rooted->cyanomod 3.6.7.2->recovery 1.3.1 (tried to install it through the raw file, didnt seem to work) radio for 1.5 android-> recovery 1.3.1 (through update.zip, worked)
I figured cyanogen's was compatible kuz on a post about rooting the rogers phone, a link was posted, by cyanogen linking to his mod.
Don't believe its compatible...I read your thread in the development section. Like soulife said, try getting a fellow Rogers G1 user to get you a system dump.
yea that requires a fellow rogers user with a g1 xD
all my friends have dumbphones for now, so no luck
PurpleFries said:
yea that requires a fellow rogers user with a g1 xD
all my friends have dumbphones for now, so no luck
Click to expand...
Click to collapse
Try posting in the "Rooting Rogers Dream" thread in Dream General. Maybe someone will provide you a system dump in there?
yea i posted one saying i need a nandroid dump
lets hope someone can get one
PurpleFries said:
yea i posted one saying i need a nandroid dump
lets hope someone can get one
Click to expand...
Click to collapse
Lol best of luck
EDIT: I see you made a new thread. Haha I posted in a more populated thread asking for people to take a look at yours. Hope you don't mind
removed due to second post
I have found these files off a rogers G1
http://forum.xda-developers.com/showthread.php?t=521240&page=13
What exactly do I do now to return my phone to it's initial status.
I already have adb, rogers sdk, random rooting stuff downloaded
Thanks
when i try to restore latest backup in the recovery mode, it starts erroring saying the device has no space
any ideas?
Ok so I think I've bricked my Nexus One. Everything was working perfect until I re-rooted it (to have SetCPU to work). I am now stuck at the loading animation screen (Google Nexus One "X"). It just keeps going and going and going. I've even tried loading my Nandroid backup and still does the same and won't work. Also I've wiped to factory default settings and tried to reinstall Modaco's 1.3 rom.
Someone please help me out...
Flash bacon add-on on top
bye!
So reinstall Modaco's 1.3, then install Bacon Add-On, and then reboot?
Yep That's the solution for some users
ok cool I'll give it a shot right now... I really appreciate it
ok at this moment it's still stuck on the animated screen... now I really don't know what to do...
Try flashing the stock rom
if u have the sdk installed, the run ddms. power on the phone usb connected to pc and see the log in ddms, paste-bin here
I have no idea on how to do that... I'm pretty much stuck at this point
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
shmigao said:
try not flashing Modaco's Rom,
just flash CM's bacon
i think there is a confusion because Modaco's rom is in the rooting threat (made me believe you HAVE to use Modaco's superboot and then go to CM's bacon.
reality is you don't need modaco's superboot. after bootloader unlocking and flashing Amon Ra's recovery image you can go straight flashing CM's Makin' Bacon.
It seems people have been successful with CM's
maybe just go straight back to the start, check that bootloader is unlocked, flash amon ra's recovery, then flash Makin' Bacon
good luck
Click to expand...
Click to collapse
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
if you can get into bootloader mode (this is the lowest level mode you can boot into), you can not brick. Even more so if you can get into recovery (which is usually always possible if you can get to bootloader)
Good you found a way to get out of your situation.
Like i said in Android 101, you CAN NOT brick the phone unless you are updating SPL and Radio. All other stuff is just a minor inconvenience.
risterdid said:
WOW, I really appreciate it and that just worked for me. Thank you to the both of you guys!
Click to expand...
Click to collapse
haha, i am glad it worked! I don't even have my Nexus One in my hands (my biz trip to the States has been delayed again ), but i spend the waiting time doing my research... it's a bit like the Holiday Season, just that the gift giving day gets pushed out further and further...
glad it worked and it confirmed my research - so i can go at it with ease once i can
This is good news. OP, you should update your thread titled with the prefix [SOLVED].
ahh how'd I miss that 101 sticky... thanks for the heads up again guys.
Edited title =)
Am I bricked?
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
DrBlast33 said:
Ok, my issue is that I cant boot into bootloader or recovery (I tried booting with rollerball pushed in, booting with down volume, abd-mac reboot recovery, abd-mac reboot bootloader) and it just goes right into my OS which is crashing every few minutes, and my radio wont work. Any suggestions? If I am bricked, can I send it to HTC even though its rooted and bootloader is unlocked? I dont care if I have to pay for fixing it.
Click to expand...
Click to collapse
First of all, if your phone boots at all, it isn't bricked. A brick is a paperweight - it doesn't do anything. Second, this thread of 5 months old. Third, people have talked A TON about sending phones in to HTC with an unlocked bootloader, do a bit of searching.
And finally, it is very peculiar that your phone doesn't boot into bootloader or recovery. Try plugging your phone into your computer, opening your command prompt, navigate to your adb install direction, typing "adb wait-for-device reboot bootloader", and turning on your phone. Best of luck!
People should be banned for bumping 5 month old threads with posts not even related to the OP's post. Ridiculous.
@rcxquake: thanks for your suggestion. That didnt work, it just rebooted the OS. Ill keep searching for my solution and how to send to HTC if I cant find the solution.
@GldRush98: Sorry for ruining your day. I put in a google search for what I was experiencing and this was one of the top result of anyone remotely close to my issue. Yes, this is an old post, but maybe someone had this issue months ago, and had a solution I wasnt aware of.
And like I said, I found this post, although not exactly my same issue, was as related as Ive been able to find. I didn't find it so ridiculous.
If you can find my same issue on another post, then please help by pointing me to it so I can find my solution. I didn't mean to cause any issues.
Thanks
I for one am glad you posted. I don't know whether this is a solution for you or not, but I'm sometimes only able to get to the bootloader after I've had the phone off the charges, with the battery out, for some time. It varies for me between a few minutes and many minutes. It is hard to say because when I try and it doesn't work, I don't know if I've reset the time by having tried.
Anyhow, I found this thread because I'm having trouble with an N1, and one of the earlier posts may help me. Thanks for bumping the thread for my benefit.
have a g1 1.6 build dmd64, and since i doubt there will be any more ota updates for this phone i have decided to root. i have never rooted a phone b4 but i am pretty tech savvy, i have flashed firmware on a psp b4.. i have heard that the dmd64 build cannot be rooted traditional ways, i have heard that there is a special way to root this build. Is this true? And if there is a special where would i find best guide on how to accomplish the root on dmd64? If anyone has rooted a dmd64 build b4 you are the perfect person to help me out, but any help would be great.
Yes, its true. Check out my recent thread on rooting DMD64
Sent from my HTC Vision using XDA App
jontornblom said:
Yes, its true. Check out my recent thread on rooting DMD64
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Hi i have a DMD64...i installed universal Androot.apk and it will work out for you...google it
Make sure you check if you are actually rooted after rooting with Universal Androot. I used it to initially try and root my G1 with DMD64 and it said it worked but I didn't have root access. I wish I could remember what I actually used to finally get it done.. let me look through my bookmarks and see what I can find for you.
rysk29 said:
have a g1 1.6 build dmd64, and since i doubt there will be any more ota updates for this phone i have decided to root. i have never rooted a phone b4 but i am pretty tech savvy, i have flashed firmware on a psp b4.. i have heard that the dmd64 build cannot be rooted traditional ways, i have heard that there is a special way to root this build. Is this true? And if there is a special where would i find best guide on how to accomplish the root on dmd64? If anyone has rooted a dmd64 build b4 you are the perfect person to help me out, but any help would be great.
Click to expand...
Click to collapse
I just did this with CM6. If you need help let me know.
NOOOOOOOB
I hate posting and asking for help. I enjoy figuring things out for myself. G1 with dmd64. Apparently I have rooted using the ANDRoot method. Shooting for install of Cyanogenmod 6, but not married to that if someone has other suggestions.
Problem? For a long list of reasons I won't get into, I am stuck using a Mac 10.4.
Just makes all instructions I am following a little bit different. I have dreamimg'ed...Put the mod on my root, all kinds of things, even starting from scratch with factory resets etc...
While I haven't "bricked" I have yet to get any MOD working yet. Have started of thinking of "different" ways of doing things so that they will take hold...Yet have realized I am getting awfully close to bricking..
Does ANYONE know of procedure to use/put on MOD using a MAC? I know I'm a NOOB, but I doubt I'm the first...
PeteDetroit said:
I hate posting and asking for help. I enjoy figuring things out for myself. G1 with dmd64. Apparently I have rooted using the ANDRoot method. Shooting for install of Cyanogenmod 6, but not married to that if someone has other suggestions.
Problem? For a long list of reasons I won't get into, I am stuck using a Mac 10.4.
Just makes all instructions I am following a little bit different. I have dreamimg'ed...Put the mod on my root, all kinds of things, even starting from scratch with factory resets etc...
While I haven't "bricked" I have yet to get any MOD working yet. Have started of thinking of "different" ways of doing things so that they will take hold...Yet have realized I am getting awfully close to bricking..
Does ANYONE know of procedure to use/put on MOD using a MAC? I know I'm a NOOB, but I doubt I'm the first...
Click to expand...
Click to collapse
I used the instructions at this wiki. When it comes to flashing the recovery, I had to look into the discussion section and use what one of the users posted to actually get telnet to flash the recovery to my phone. I did however manage to successfully flash my G1 with CM6.
Thank you. Good stuff. I guess my question in particular is...My phone IS rooted (checked with T emulator) but before I flash mod, do I still have to change the radio? Right now I'm listed at dmd64, do I have to goto one of the RC's or can I just flash? I have tried to change the radio but it always stops at the rainbow screen.
PeteDetroit said:
Thank you. Good stuff. I guess my question in particular is...My phone IS rooted (checked with T emulator) but before I flash mod, do I still have to change the radio? Right now I'm listed at dmd64, do I have to goto one of the RC's or can I just flash? I have tried to change the radio but it always stops at the rainbow screen.
Click to expand...
Click to collapse
Personally, I did exactly what that guide I linked said. I'm not sure if you can just flash or if you have to downgrade. I do know, though, that downgrading is pretty simple and it doesn't take much time. As for the radio, I know that CM5 and CM6 (and I am assuming CM7 also) require DangerSPL. When you flash DangerSPL, the instructions also tell you which radio to flash, and to be careful because flashing the incorrect radio can brick your phone.
So, the only thing holding me back was voiding the warranty and the fact I have a rogers phone (build EPE54B).... so I think I have to flash the build to the one that matches the update?
Sooooo if anyone wants to point me in the safest, easiest direction... I would appreciate it... and dos and don't would be appreciated as well. I am new to the phone an android, so feel free to dumb it down.
Does the build actually mean anything? What happens once I change it... and official updates come out? I am going to cut the grass... and then root, so help me out (preferably someone that is on rogers and has done this)
thx in advance! Froyo or Brick, here I come!
had a long day with chores and family day.... but I am back at it, first tutorial down and it seems solid...
Uploaded with ImageShack.us
onward!
Let me know how you make out. I'm on Rogers as well and am debating rooting.
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Let me know how it goes for you.
I am on Rogers and experienced EXTREME instability the moment I flashed the Froyo radio. My phone would crash randomly and frequently.
I suspect it was a problem with my hardware and have returned the phone and am waiting for a new one.
Jack_R1 said:
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Click to expand...
Click to collapse
thx jack, I appreciate it.... sorry for the thread... but in my experience... it is easier having your hand held by someone experienced.... then assuming I am following the right one, lol.... so I follow that entire thread to go from rogers to whatever build I need? heh
I will try this in approx 2 hours.... when the yard work is done!
early quick question, when I go to "CyanogenMod"
it takes me to a thread, but I do not see the download, what am I not seeing? heh
I am at this part
Type: fastboot flash recovery recovery-RA-nexus-v1.7.0.img
it says cannot load image recovery? thx
well everything was working great up until this point, tried it 100 times, heh... so now I sit and wait for guidance? thx
Mr.Kakarot, have you put the .img in the same folder as fastboot? Or, alternatively, if fastboot is in your PATH, you won't have this problem.
i renamed the image to recovery.img and that seemed to work? I will continue after supper!
Jack_R1 said:
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Click to expand...
Click to collapse
followed that first thread to a T and it worked out... had 2 minor stalls but I got through it... I am doing this stuff off and on, thx for that thread... this is going to be a STUPID question I am sure... but following that first thread, what have I done? unlocked, rooted and installed google add ons? phone looks awesome, I will do the rest after supper!
hmmm, got it, lol
done, running 2.2.... so tomorrow at work, i guess I will see if I have any issues....
now that this is done, can I re install that sense ui? What should I do or try now that I have done those 2 tutorials? thx
first off there are no 2.2 froyo/sense roms available as of yet.. so if you want to use a desire rom youre more than likely going to want to downgrade to the latest 2.1 radio that works well with your carrier/area, as froyo has its own radio and needs it to run properly.. once you downgrade.. nandroid>wipe>flash
yea, I did not know it would put me back to 2.1, lol.... went back and then back again to 2.2, lol... sense sure looked good!
Any ideas, suggestions, tips for 2.2? I installed flash! thx
How stable is your phone with the Froyo radio? Any unexplained reboots yet?
well it was quite late by the time I did it, I was playing with it, went to a few flash websites.... and no reboots or shutdowns, I also just woke up.... so I will know today after a full day work/playing, thx
one of the bugs is my camera does not work for video... so I have to update the radio, any suggestions! thx
Nope thats pretty much what you need to do is update the radio
thanks, but I am not gonna lie... still not sure which are radios, roms, senses, lol.... could you point me to the one I need.... or does it matter? thx, I just do not want to brick, obviously!
Also, I did not do this step.... is this what I need to do, or is it unrelated?
11) You should still have root, but if you want BusyBox (or lost root somehow), Cyanogen has done it again! Go back into Recovery and flash froyo-rooter-signed.zip. Then Titanium Backup will work once again.
does not sound like something I need or use, so I did not do it....
as far as stability... my 3g signal looked low all day... but I never had a dropped call, instability or any reboots/crashes.... all is well! thx
go here:
http://forum.xda-developers.com/showpost.php?p=6734240&postcount=9532
havent had problems with the older one, but am going to try the new one just to see.
anyone around?
I tried these 3 things
Step_One_Froyo_Radio_Update.zip
step-two-RoDrIgUeZsTyLe-FroYo-MCR-R16-MOD-V1.8-FIX.zip
and then i ran
2.6.34_AVS-925mV_CFS_1113Mhz_061210.zip
anytime I run setcpu, I get this error
the application process com.mhuang.overclocking has stopped unexpectedly, please try again?
"uninstalled and reinstalled, worked. thx"
hi guys, im stuck...
well not exactly- i have unlocked the bootloader on my nexus one on FRF91.
but what bout after that? i found some links on XDA and it says to superboot? cant do it i keep getting error and most of the tutorials are on windows OS, i use a mac, i would really appreaciate it if anyone can assist me any further with commands on terminal for mac.
i'm a newbie so i really dont know what to do, i've spend almost 8 hrs on this and only got bootloader unlocked.
thanx for your help guys
Why would you play around with a $580 phone if you don't know what your doing, they had a post showing you how to root without unlocking your bootloader. The other thing is you have to explain exactly what you did, and what stock rom you came from and where your trying to go. I'm not familiar with Mac systems but there should have been instructions for that system to. I'm going to check it out for you and see if I can help.
Sent from my Nexus One using XDA App
http://forum.xda-developers.com/showthread.php?t=636795
Do step IV.
Pick a ROM you like from the list in Developers section, download it.
Do step VI.
Not really hard.
blas4me said:
Why would you play around with a $580 phone if you don't know what your doing, they had a post showing you how to root without unlocking your bootloader. The other thing is you have to explain exactly what you did, and what stock rom you came from and where your trying to go. I'm not familiar with Mac systems but there should have been instructions for that system to. I'm going to check it out for you and see if I can help.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I have unlocked the bootloader- theres a unlock logo on boot screen, but then I know I need to do superboot n then flash recovery image!!
That's the part that I tried to do but can't do.. I have all the files,but commands don't seem to work.
I've been trying for almost 12 hrs.
n I'm on stock frf91 which I did OTA for
Let me know if there's anything you can do thnx
Check this video
Kartikp84 said:
I have unlocked the bootloader- theres a unlock logo on boot screen, but then I know I need to do superboot n then flash recovery image!!
That's the part that I tried to do but can't do.. I have all the files,but commands don't seem to work.
I've been trying for almost 12 hrs.
n I'm on stock frf91 which I did OTA for
Let me know if there's anything you can do thnx
Click to expand...
Click to collapse
This site helped me out alot when I first learned, because they have instructions accompanied with video, so it's like you can't go wrong. Sometime the dudes who have just instructions leave out a step and that can f things up for us. When I rooted my N1, the guy who posted the instructions put a period in the wrong place, and it almost had me stuck, but I knew the recovery image and I knew It did'nt belong there. Anyway check this vid, and let me know what happens, start from the beginning even though your boot loader is unlocked.
http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Here's another video with instructions for Mac.
http://www.droiddog.com/android-blog/2010/02/video-tutorial-hack-your-nexus-one/
There are links to files for each step, and the only suggestion I would make is maybe look for the newer 1.7.0.1 Amon Ra recovery image and to not use the Sense ROM that he links to. The recovery image is here on this forum in the Android Development section. I don't use it since I'm still having no issues with the 1.7.0 version that this guy links to in the guide.
As far as ROMs are concerned, I highly recommend going with either CyanogenMod 5.0.8 Stable (because it has fewer issues and is a good place for a noob to start) or with one of the more stable Froyo roms, like Kang-O-Rama .9.