Im currently a HTC Hero developer and my recent work is Hero 2.0 ROM
And I see that Tattoo hasnt much going on, so I thought why not help you guys out a little.
Things I need to do so:
- Testers with some kind of android experience and that are willing to test stuff.
MOD EDIT - To request money for a new device so you can make roms is a no no on XDA. Donations towards work already done is ok, but for work still yet to be done, this not permitted
OP EDIT: I understand that, came out the wrong way
What I've planned:
- Root
- Custom recovery
- Custom rom
Regards,
b
Yes please
behnaam that would be great!
unfortunately i'm very new to android and the htc tattoo is my first smartphone ever. but i'm willing to donate if your thread gets more feedback.
Need somebody to test the recovery.img, if we have that running its a good starting point.
PM me if interested to help!
I would love to see this work, and i'd gladly help you out it the phone were mine. However the Tattoo that i posses is actually my fathers and there is nothing i can do about it...
If it was the magic we're talking about id gladly put my hand into fire
Would be great.
Wating.
Thanks in Advance.
I'm also new to Android.
It's very good to seem some talented devs interested in the Tattoo.
It's a great little budget android phone that needs some attention
Behnaam, I'm very limited in time during the weekdays but if you need someone help testing some roms, feel free to PM me.
Good luck!
PS - How are you planning to bypass the bootloader security checks ? I'm under the impression that on Android 1.6 the boot images have to be signed, so that they will be accepted by the bootloader ?
mainfram3 said:
It's very good to seem some talented devs interested in the Tattoo.
It's a great little budget android phone that needs some attention
Behnaam, I'm very limited in time during the weekdays but if you need someone help testing some roms, feel free to PM me.
Good luck!
PS - How are you planning to bypass the bootloader security checks ? I'm under the impression that on Android 1.6 the boot images have to be signed, so that they will be accepted by the bootloader ?
Click to expand...
Click to collapse
Dont tattoo bootloader allow booting into a boot.img? Since I remember we had the same issue with Hero, that the bootloader didnt allow flashing boot imgs, but it allowed booting them up, so the workaround was to boot into a custom recovery img with adb root permissions and from there flash the new recovery.
Give us the instructions, we will try it and let you know.
if you give the instructions i will test also..
I like to help too... the tattoo scene is so dead.
behnaam said:
Dont tattoo bootloader allow booting into a boot.img? Since I remember we had the same issue with Hero, that the bootloader didnt allow flashing boot imgs, but it allowed booting them up, so the workaround was to boot into a custom recovery img with adb root permissions and from there flash the new recovery.
Click to expand...
Click to collapse
I took a very fast look at this, when I noticed the Superboot method for the N1.
What I found it that "fastboot oem boot" will boot the phone but I couldn't find a way to pass a custom boot image. IIRC, adb commands were not responsive, and you could only use fastboot by prefixing the commands with "oem". But then again, this was a very very fast look at all of this, since I'm a total Android newbie (but with a firm grasp of Linux ).
So, your idea is to create a custom recovery image that will enable full ADB commands ?
Why not go through the Superboot way ? Compile an image with a kernel for the Tattoo, that once booted copies a chmodded su to the Tattoo filesystem ? This is what I was thinking about, until I read that the Superboot only worked on "Holiday" N1's and that the other had to be unlocked, using "fastboot oem unlock". Once again, let me stress that I'm preety new to this, so I may be missing something. Don't let me put you down
awesome
I would be more than happy to test as well. I agree with the fact that the tattoo scene is pretty much dead. Not as many apps, no way to root, and no way to update to 2.1
Send me stuff and ill test it! thanks a bunch
I stand corrected.
We can, at least, upload and start the boot of a boot image.
I ran:
Code:
adb shell reboot oem-72
fastboot boot superboot.img
And I got
Code:
downloading 'boot.img'... OKAY!
booting...
Obviously, it hangs there (superboot has a kernel for N1), but I now believe that if we have a valid Tattoo boot image, maybe we can boot it and run a superuser-like rooting technique.
I have no time to investigate how to compile a kernel, prepare a ramdisk and convert them into a bootable image, but for someone more used to the Android OS, this should be a good path to try.
You have my support. I'm a newbie to the Tattoo hacking scene, but once I get mine, I'll be sure to help out.
As soon as we can root and make our own ROMs, well, we'll have some fun
Ok guys thnks for info, now I know that the oem method works.
Gonna make a superboot for Tattoo for testing, posting it here today, try it and tell me (when I posted it)
[apart] I'm agree with XDA, what is it that the way to request money for a device, promising development ? It's not in community spirit.[end apart]
In fact, i tried to boot a stock boot.img using fastboot boot, and it's don't work. Locked ?
drakaz said:
[apart] I'm agree with XDA, what is it that the way to request money for a device, promising development ? It's not in community spirit.[end apart]
In fact, i tried to boot a stock boot.img using fastboot boot, and it's don't work. Locked ?
Click to expand...
Click to collapse
Came out the wrong way, meant more can be done if i actually had the device... anyways..
Did u try too boot into oem-72 mode? and then fastboot boot boot.img?
drakaz said:
[apart]In fact, i tried to boot a stock boot.img using fastboot boot, and it's don't work. Locked ?
Click to expand...
Click to collapse
Hi.
Where did you get that boot image from ?
I tried to boot a boot.img using fastboot, from RUU update, in RUU mode.
Related
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
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.
Dear experts, I have seen similar threads as with the issue I am facing but I wasnt sure of few parts and if the process as a whole could work for me.
Here's what I know and what the problem is all about, appreciate any help to get back the phone in working condition.
First the basics:
HTC first
GSM unlocked, Bootloader unlocked and TWRP installed
I wanted to delete and format the device as I intended to give this to my friend and I did go to TWRP menu and then clicked on advanced wipe etc and realized I did erase everything the phone needs even to bootup. This I have done without taking backup.
What it looks like now:
When I boot the device out from TWRP, the 'F' logo comes up and stays like that for ever. If I go to TWRP pressing the power and volume down together, it goes to the TWRP menu and thats it..no options seem to help me on this screen to go past the 'F' logo at startup. If I simply power down the device on the 'F' screen it restarts and goes to the same screen making it look like its in a loop. Not sure if this is called soft-brick or hard-brick but it looks like the phone is of no use to me right now.
Can you guys please help me with resolving the problem..any help will be much appreciated
kuldeep_ch said:
Dear experts, I have seen similar threads as with the issue I am facing but I wasnt sure of few parts and if the process as a whole could work for me.
Here's what I know and what the problem is all about, appreciate any help to get back the phone in working condition.
First the basics:
HTC first
GSM unlocked, Bootloader unlocked and TWRP installed
I wanted to delete and format the device as I intended to give this to my friend and I did go to TWRP menu and then clicked on advanced wipe etc and realized I did erase everything the phone needs even to bootup. This I have done without taking backup.
What it looks like now:
When I boot the device out from TWRP, the 'F' logo comes up and stays like that for ever. If I go to TWRP pressing the power and volume down together, it goes to the TWRP menu and thats it..no options seem to help me on this screen to go past the 'F' logo at startup. If I simply power down the device on the 'F' screen it restarts and goes to the same screen making it look like its in a loop. Not sure if this is called soft-brick or hard-brick but it looks like the phone is of no use to me right now.
Can you guys please help me with resolving the problem..any help will be much appreciated
Click to expand...
Click to collapse
Sideload the stock rom and then flash it I've been in your situation and that's all that was needed to be done.
Be sure to also flash the boot.img if you aren't s-off
More questions
Thanks Abraham for your quick response.
I am starter with Android so, please help me how to sideload and also on where to get stock rom. I will also be lying if I said I understood whats s-off..? Please help further
Thanks
abrahammmmmmm_ said:
Sideload the stock rom and then flash it I've been in your situation and that's all that was needed to be done.
Be sure to also flash the boot.img if you aren't s-off
Click to expand...
Click to collapse
S-ON it is
I have checked on HBOOT screen and its S-ON
kuldeep_ch said:
I have checked on HBOOT screen and its S-ON
Click to expand...
Click to collapse
No problem! just be sure to hit that thanks button
Well then you'll have to make sure you flash the boot.IMG as well,
So what you'll do is
1) find the stock ROM around these threads
2) sideload the ROM
3) flash it
4) flash the boot.IMG inside the rom
5) you're done!
Understanding what s-on/off won't be of use here really d:
And the stock ROM is somewhere around these threads. About the side loading you might find a tutorial for that on YouTube. Sorry if it seems that I'm just leaving you in the dust but I am typing this in a hurry since it's 2:50 am at my place. I will be back to whip up a tutorial for you if YouTube wasn't of much help
Okay
Let me try my best till its like a more sociable time for you tomm morning, I will post my updates on the thread on how far I go and any questions I may have..
abrahammmmmmm_ said:
Well then you'll have to make sure you flash the boot.IMG as well,
So what you'll do is
1) find the stock ROM around these threads
2) sideload the ROM
3) flash it
4) flash the boot.IMG inside the rom
5) you're done!
If you need help with a tutorial or need me to go in depth with something it'll be quite a while from now because it's 2:40 am at my place. I'll assume you're a more advanced user since you've already got twrp and sound like you know what you're talking about
Click to expand...
Click to collapse
kuldeep_ch said:
Let me try my best till its like a more sociable time for you tomm morning, I will post my updates on the thread on how far I go and any questions I may have..
Click to expand...
Click to collapse
Yeah, just be sure not to wonder off too far from these threads on to other forums and flash or do something that can brick the device
Oh and btw I edited my post bc I saw your othe reply stating that you aren't all that too advanced with this
boot.img
I should be finding the boot.img on the stock ROM itself, isnt it..?
kuldeep_ch said:
Let me try my best till its like a more sociable time for you tomm morning, I will post my updates on the thread on how far I go and any questions I may have..
Click to expand...
Click to collapse
kuldeep_ch said:
I should be finding the boot.img on the stock ROM itself, isnt it..?
Click to expand...
Click to collapse
That's correct. Unzip the ROM and it should be there
This is how far I could get
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you
Finally got it fixed
Thanks for the help..it all worked fine and the device is now working fine..
Thanks for all the guidance
kuldeep_ch said:
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you
Click to expand...
Click to collapse
kuldeep_ch said:
Thanks for the help..it all worked fine and the device is now working fine..
Thanks for all the guidance
Click to expand...
Click to collapse
Great! Sorry I was away but it was getting very late. I'm glad everything worked out tho
kuldeep_ch said:
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you
Click to expand...
Click to collapse
wait a sec...you dont have a rom or kernel on your device at the moment right?
then there is no way to turn on usb debug on or off cause there is nothing managing the device.
um...use cmd and do adb devices. if its not there then i have no idea but if fast-boot goes into usb mode try flasing it using code
not sure what you would use, but see if "fastboot flash update nameofROM.zip"
but im not sure if that is the right code
stock rom for htc first
kuldeep_ch said:
Got all stock ROM and the IMG files, installed android SDK
ADB doesnt recognize the device to copy the file for sideloading
Guess issue is with the fact USB debugging was disabled earlier on my device
Can you please advise further
Is it better to chat on google chat or something so its even faster and I could get this fixed tonight (my time)
Thank you
Click to expand...
Click to collapse
can you provide a stock rom for htc first because i am having a same issue as yours ........ mine is s off too .....
abrahammmmmmm_ said:
No problem! just be sure to hit that thanks button
Well then you'll have to make sure you flash the boot.IMG as well,
So what you'll do is
1) find the stock ROM around these threads
2) sideload the ROM
3) flash it
4) flash the boot.IMG inside the rom
5) you're done!
Understanding what s-on/off won't be of use here really d:
And the stock ROM is somewhere around these threads. About the side loading you might find a tutorial for that on YouTube. Sorry if it seems that I'm just leaving you in the dust but I am typing this in a hurry since it's 2:50 am at my place. I will be back to whip up a tutorial for you if YouTube wasn't of much help
Click to expand...
Click to collapse
can you please provide a tutorial and and all the link because i m kinda noob . I am unable to find them .
Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.
WOW, just WOW, awesome work rbox!
I was definitely not expecting this.
rbox said:
Well it's a little early for Christmas... but here is a special gift. This will allow the bootloader to load things from boot or recovery without them needing to be patched. This is not a full unlock and will not enable fastboot boot or fastboot flash. Obviously this will only work if you are rooted.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Using this tool won't brick your Fire TV, but doing stupid things afterwards might. I will stress here that flashing something bad to boot is a guaranteed way to brick because if the kernel can't boot you have no way to get back to recovery. For testing kernels, it's best to flash recovery to the boot partition and the new kernel to test to the recovery partition.
To use:
Downgrade: You must first downgrade to 51.1.0.2. If you already have CWM installed, you can skip this.
adb push aftv-unlock /data/local/tmp/
adb shell
chmod 755 /data/local/tmp/aftv-unlock
su
/data/local/tmp/aftv-unlock unlock
Afterwards you should see this message:
Code:
Attempting to unlock...
All done!
If not, something went wrong. If for whatever reason you want to relock the bootloader, you can use this command:
Code:
/data/local/tmp/aftv-unlock lock
You can download it here.
Click to expand...
Click to collapse
Congrats to you
And Merry Christmas to us FTV users!
BTW, could you please tell me the console messages for lock failure and unlock failure? (may they never occur)
..
JJ-KwiK said:
Awesome!
Thanks man!
Click to expand...
Click to collapse
maybe we can get some real mods for this device now. different roms and what not.
just ran the unlock and it worked like a charm
Rbox do you know if the bootloader can boot from usb?
Does this require a minimal CWM version of yours?
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "
Truly amazing. Can't wait for full fledged android on this.
Nice to see this, but it doesn't help much when you have a Fire TV with a non-rootable firmware.
jmandawg said:
Rbox do you know if the bootloader can boot from usb?
Click to expand...
Click to collapse
The bootloader will only boot from the boot partition or the recovery partition on the mmc. But I'm working on a boot menu that will allow you to easily boot additional kernels which can then load your os from wherever you want.
toe-rag said:
I installed your Recovery (CWM) - on all 4 of my AFTVs - when you first released it ..
I've not had any reason to upgrade to the latest versions.... I'm just using the heck outta the AFTV as it is built, with all the nice rooted options. I really don't need anything else yet, so ...
with that said " can I just install this unlock-lock feature? "
Click to expand...
Click to collapse
Yes. This is independent of anything. The only dependence is the latest version of CWM requires it.
I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.
KLit75 said:
I installed ccm when you first released it then upgraded to the latest firmware the other night. Thanks a lot btw! But, can I assume (as a novice) this is not something I need to do right now. What I mean is is this just for people that want to experiment with new kernels or is there some advantage I'm missing? Thanks again and sorry if my question is a little too basic for this thread. I'm just genuinely curious.
Click to expand...
Click to collapse
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.
Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.
KLit75 said:
Thanks for the response. I did, in fact just update cwm and am running your latest fw update. I guess "need" isn't the right word. But if I unlock it tonight the cool stuff is still forthcoming.
Sorry just 2 questions:
1. Unlocking and keeping it unlocked indefinetly is ok?
And here's one that s on a slightly different subject...
2. I noticed updating with your fw saves my settings. Is there a safe way to factory restore using cwm without the risk of losing root?
That's actually the one I'm most interested in now. My aftv has been having issues that are hard to troubleshoot. An option to factory restore would be great. I mostly use it for xbmc so the only thing I care about losing is root. Thanks.
Click to expand...
Click to collapse
Of course keeping it locked is fine... i wouldn't have released the tool if it wasn't.
As I've stated in MANY OTHER THREADS... factory reset in CWM is perfectly fine and has nothing to do with root.
rbox said:
If you don't care about updating your CWM version, or using any of the other cool things I'll release in the future that needs it, then no. You don't need to do this.
Click to expand...
Click to collapse
That's great. Thanks again
Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance
Hi, I unlocked the bootloader and it was successfully. Thank you rbox
barrist said:
Thanks for this! Was very happy that the AFTV i ordered from eBay was rootable.
at the risk of being "that guy", can someone explain to a relative dummy like me the future potential with an unlocked bootloader? are we talking maybe an Android TV rom down the road? .. Apologies in advance
Click to expand...
Click to collapse
Nothing that people couldn't already do with my old CWM. Custom ROMs and whatnot has been possible for a while. This just makes things a little easier because kernels don't need to be patched.
Yea! Install failed yesterday. I've had SU problems I think. Couldn't get the # prompt. Reinstalled latest ROM and SL'd SU from the store. The Unlock finally took. Thanks.
nice, thanks rbox, you rock.
hey guys, Just trying to get my bearings on where to start. A friend game me a HTC Desire 510 that was not loading for him. Just sticking on the HTC loading screen.
He managed to "unlock" it. Not sure if it has root access.
In anycase it will not loal anymore, stuck on HTC load screen. I followed a few threads and tried to reset/restore things but now it looks like i need to just reinstall the OS.
Where I am lost is where/can i get the stock OS for this phone?
If not , do i need to get root access, load in a bootloader and then load in a custom ROM?
last time I did all this before was 2 years ago on a Samsung so I am a little rusty on the steps.
details
HTC Desire 510 - europe (Irish)
HBOOT - 3.19.0.0000
Radio 01.02.012
When I load up the bootloader I have "Sofrware status: Officaial *** at the tope and UNLOCKED under that.
Cheers
check the htc website for the latest rom(update) also this thread is sprint/virgin/boost
http://forum.xda-developers.com/desire-510/development/virgin-sprint-htc-desire-510-stock-t2961521
cricket stock rom: http://forum.xda-developers.com/desire-510/help/stock-rom-cricket-htc-desire-510-t3161697
id see if the htc site works first but thats just me.
hope i was of help to you with your issues if not wait for more experanced members to assist.
roymcd said:
hey guys, Just trying to get my bearings on where to start. A friend game me a HTC Desire 510 that was not loading for him. Just sticking on the HTC loading screen.
He managed to "unlock" it. Not sure if it has root access.
In anycase it will not loal anymore, stuck on HTC load screen. I followed a few threads and tried to reset/restore things but now it looks like i need to just reinstall the OS.
Where I am lost is where/can i get the stock OS for this phone?
If not , do i need to get root access, load in a bootloader and then load in a custom ROM?
last time I did all this before was 2 years ago on a Samsung so I am a little rusty on the steps.
details
HTC Desire 510 - europe (Irish)
HBOOT - 3.19.0.0000
Radio 01.02.012
When I load up the bootloader I have "Sofrware status: Officaial *** at the tope and UNLOCKED under that.
Cheers
Click to expand...
Click to collapse
Are you in Europe? If you are that's most likely a 64 bit phone and you'll need Philz Touch Recovery unless you have one installed. You'll also need to find a 64 bit stock HTC desire 510 rom.. It should work after installing them.
Edit: The HTC websites rom updater will not work since the phones boot is unlocked.. Just try what I said above.
Yes I am in Europe.
Will give what suggested a go and let you know..
cheers
here is your man for the job
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button
bcbradley12 said:
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button
Click to expand...
Click to collapse
It's actually fastboot oem lock
bcbradley12 said:
ok mthis has happen to me before alright take the sdcard out reboot to fastboot relocok bootloader by typing 'fastboot oem relock' get the ruu for your phone then it will help you if you find this helpful hit the thank you button
Click to expand...
Click to collapse
MrMike2182 said:
Are you in Europe? If you are that's most likely a 64 bit phone and you'll need Philz Touch Recovery unless you have one installed. You'll also need to find a 64 bit stock HTC desire 510 rom.. It should work after installing them.
Edit: The HTC websites rom updater will not work since the phones boot is unlocked.. Just try what I said above.
Click to expand...
Click to collapse
Ok guys , getting around to trying this now but running into some small problems.
Question 1
I have installed adb.exe and it does work with my main phone (HTC m8) but when i plug in the broken phone it does not pick up that phone (when i do a ">adb.exe devices") I saw some comments saying that I need to enable debug mode but how can I do that when i cannot even load the phone up ?
Question 2
I would like to install this Philz Touch Recovery , so i can installed the new RUU but I see on some sites that I need to install ClockworkMod first. Now I am not sure if this is needed or not but i still have the problem of being unable to install it from the bootloader screen. There is no option to install from zip? So this might sound like a real n00b question but how can install anything to my phone when all i have it the bootloader screen. My options when i boot up are . . .
Fastboot
-->HBOOT
-->RAMDUMP
-->REBOOT
-->REBOOT fastboot
-->power down
recovery
factory reset
simlock
check smartSD
image CRC show barcode.
Review. . .
I would think my issue is with the broken phones connecting to my laptop and the use of adb.exe. If I could get that working i can use adb.exe to installl clockworkmod and from that I can boot up the phone and install Philz Touch Recovery, and then using phils installer I can install the original 64bit Rom and be in business?
does that seem right?
Cheers
roymcd said:
Ok guys , getting around to trying this now but running into some small problems.
Question 1
I have installed adb.exe and it does work with my main phone (HTC m8) but when i plug in the broken phone it does not pick up that phone (when i do a ">adb.exe devices") I saw some comments saying that I need to enable debug mode but how can I do that when i cannot even load the phone up ?
Question 2
I would like to install this Philz Touch Recovery , so i can installed the new RUU but I see on some sites that I need to install ClockworkMod first. Now I am not sure if this is needed or not but i still have the problem of being unable to install it from the bootloader screen. There is no option to install from zip? So this might sound like a real n00b question but how can install anything to my phone when all i have it the bootloader screen. My options when i boot up are . . .
Fastboot
-->HBOOT
-->RAMDUMP
-->REBOOT
-->REBOOT fastboot
-->power down
recovery
factory reset
simlock
check smartSD
image CRC show barcode.
Review. . .
I would think my issue is with the broken phones connecting to my laptop and the use of adb.exe. If I could get that working i can use adb.exe to installl clockworkmod and from that I can boot up the phone and install Philz Touch Recovery, and then using phils installer I can install the original 64bit Rom and be in business?
does that seem right?
Cheers
Click to expand...
Click to collapse
Never mind if figured it out. .
roymcd said:
Never mind if figured it out. .
Click to expand...
Click to collapse
Nice to see you figured it out!
MrMike2182 said:
Nice to see you figured it out!
Click to expand...
Click to collapse
Well now that you say that. I am having a strange issue. The phone will boot but only when I select "recovery" mode from the bootloader?
I presume what I have done is flashed the wrong image to the wrong section. I think i need to to flash something to boot and not to recovery when I was running the "fastboot flash recovery image.img!"
ideas?
roymcd said:
Well now that you say that. I am having a strange issue. The phone will boot but only when I select "recovery" mode from the bootloader?
I presume what I have done is flashed the wrong image to the wrong section. I think i need to to flash something to boot and not to recovery when I was running the "fastboot flash recovery image.img!"
ideas?
Click to expand...
Click to collapse
I don't get what you're trying to do. If you wanna get back up and running, all you have to do is relock the bootloader and run the RUU... That's it. Your recovery doesn't matter. You don't need a custom recovery for that. Any custom recovery you have will be replaced by the stock one when you run the RUU.
I haven't been on this forum much lately, (so please correct me if I'm wrong, somebody) but from what I remember, the only custom recovery available for the 64-bit variant 510 is Philz. If that's the case then you shouldn't be flashing CWM
Surj138 said:
I don't get what you're trying to do. If you wanna get back up and running, all you have to do is relock the bootloader and run the RUU... That's it. Your recovery doesn't matter. You don't need a custom recovery for that. Any custom recovery you have will be replaced by the stock one when you run the RUU.
I haven't been on this forum much lately, (so please correct me if I'm wrong, somebody) but from what I remember, the only custom recovery available for the 64-bit variant 510 is Philz. If that's the case then you shouldn't be flashing CWM
Click to expand...
Click to collapse
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.
roymcd said:
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.
Click to expand...
Click to collapse
I did say you needed philz touch recovery if you have a 64 bit phone and you never really answered the 64 bit question and I asked because you said you are in Europe (Irish) and if you do have a 64 bit phone then you do need philz if you want to use other roms like the rest (most) of us on here do.
MrMike2182 said:
I did say you needed philz touch recovery if you have a 64 bit phone and you never really answered the 64 bit question and I asked because you said you are in Europe (Irish) and if you do have a 64 bit phone then you do need philz if you want to use other roms like the rest (most) of us on here do.
Click to expand...
Click to collapse
Yeah it was a 64bit phone.
I wanted the original OS back on the phone so that is why i did not need phils tool.
roymcd said:
Yeah it was a 64bit phone.
I wanted the original OS back on the phone so that is why i did not need phils tool.
Click to expand...
Click to collapse
I kinda figured all that out on my own already but why do you just want stock? Why don't you want a rooted phone so you can do a lot more with it?
---------- Post added at 05:46 AM ---------- Previous post was at 05:28 AM ----------
roymcd said:
Yes you seem to be correct . I locked the bootloader and then used the command "fastboot flash boot <htc_orginal_ruu>" and it started working again.
I had lots of issues trying to get the CWM installed . It was someone else on this thread that suggested that but I think that info was wrong.
And just to conform for others that may read this someday you do not need Phils recover if you want to get the original system running. if you want to install custom ROMs then you need it then.
Thanks for the input. Half the time its just good to write out your problem so you can understand.
Click to expand...
Click to collapse
I've read through this entire thread more than 3 times and I never once seen anyone in this thread tell you to run CWM(ClockWorkMod).. or to even use that so where did get that idea from... The only thing I suggested was Philz Touch Recovery as did @Surj138 for a good reason cause it's the only one that's 64 bit for your phone!
MrMike2182 said:
I kinda figured all that out on my own already but why do you just want stock? Why don't you want a rooted phone so you can do a lot more with it?
---------- Post added at 05:46 AM ---------- Previous post was at 05:28 AM ----------
I've read through this entire thread more than 3 times and I never once seen anyone in this thread tell you to run CWM(ClockWorkMod).. or to even use that so where did get that idea from... The only thing I suggested was Philz Touch Recovery as did @Surj138 for a good reason cause it's the only one that's 64 bit for your phone!
Click to expand...
Click to collapse
It was from other threads that I read to install Phils recovery I would need install CWM but I think now that is for other phones. I said it was in this thread by mistake.
As for going for the original ROM as opposed to a custom ROM my reasoning is three fold. . . .
1. This phone will not be staying with me. Will be giving it back to my friend who is giving it to his daughter. She is would have no use for a root phone.
2. The last time I was using custom ROM was with my Samsung S2 about 3 years ago. I did like all the extra features, free apps and full customization that you can do with it but I did find that no matter what custom ROM I found there would be little problems with each one. Performance would slowly drop the more i switched around the custom ROMS.
3. Custom ROMs are great and all but we cannot be 100% sure there is not hidden male-ware in some of them that is robbing my data. It was going to be a spare phone for playing games then i would not mind but to give to someone as there main phone is not the best option.
roymcd said:
It was from other threads that I read to install Phils recovery I would need install CWM but I think now that is for other phones. I said it was in this thread by mistake.
As for going for the original ROM as opposed to a custom ROM my reasoning is three fold. . . .
1. This phone will not be staying with me. Will be giving it back to my friend who is giving it to his daughter. She is would have no use for a root phone.
2. The last time I was using custom ROM was with my Samsung S2 about 3 years ago. I did like all the extra features, free apps and full customization that you can do with it but I did find that no matter what custom ROM I found there would be little problems with each one. Performance would slowly drop the more i switched around the custom ROMS.
3. Custom ROMs are great and all but we cannot be 100% sure there is not hidden male-ware in some of them that is robbing my data. It was going to be a spare phone for playing games then i would not mind but to give to someone as there main phone is not the best option.
Click to expand...
Click to collapse
Understood sir!!