Related
I have been reading and attempting two flash anything for 2 days. I am new as I have stated in some threads and need baby steps unfortunately like im
sure some others do. I have been able to unlock, root, and get into recovery but after that no dice. I get everything Im suppose to do but... I am not able
to flash anything and I have looked for help in threads and have had some help and success but more importantly all detail is not clear to me all the time. I
am on here because I want the most out of my phone and all the goodies and appreciate the work of everyone. Coming from Windows to Android is
different and I understand will take sometime to gain the knowledge needed but it seems as you/we are supposed to know everything already or if you/we
dont understand what to do then you/we shouldnt be flashing some say. I disagree with that because I started the same way on my HD and eventually
was able to help new ppl to the forum. We all have been there at some point trying to learn and being clueless then finally getting it. For instance I was
looking at a theme thread and there was no instruction from the author am I just suppose to know what to do with the file being that Im not a week into
this and have never dealt with android? Also what to write in some command prompts is not the same for everyone different and thats not always clear.
With that being said this being a new device I would hope that things will be more written out to help and if its not at least be able to get help. This is just
in some cases not all . Again I am thankful for everyones work on here.
Now with the files I have trouble with are pretty much every file I have placed on my sd card not being recognized except Modocas rom until I renamed it
update.zip. Until then in recovery nothing would be recognized and even still the rom failed to install in which I have no clue why and have been seeking an
answer and so have others. If anyone has any suggestions it would be greatly appreciated for me and others and also to give detail on what to do with
what we are given. Thanks to everyone who contributes on here and make the experience that much better.
Every one of the instructions that are on this forums (in the dev area) are explained in detail. You must have some core understanding of basic linux commands and android file system. Those we are not going to teach you here. There are many documents on android itself (search on google) and HTC also has a lot of documentation on flashing.
However with that said, rooting instructions were to the point and should be able to follow without issues. thefallen has written it instructions for windows/dos and I've recapped them for linux/osx. To be honest, commands are the same for adb and fastboot.
Amon_Ra also has a good instructions on how to update his recovery. Pretty much if I should recap, I'd say boot phone in boot loader and fastboot flash recovery new_recovery_image.img
As for the themes and most of the updates, always run a nandroid first and update. What do I mean by that? Nandroid is the backup utility in Amon_Ra's recovery. If you ran it, you can restore to that. Call it a restore point but it's more than that (read on that so you know what it actually does). Why nandroid? So you can restore if you don't like the effects of what you just done. Now you can just update via zip that you download.
I think it's very simple. What do you need explained in detail? Most of the stuff you are requesting is simple knowledge. I am not saying I am holier. I am just saying I am used to the commands. Once you flash it a few time, it'll come to you too. But please do read up on how to restore an image from HTC. Go to HTC Global, and support and pull up google ION.
Read thru the instructions. If you are still confused, feel free to PM me.
If recovery is only recognizing update.zip, are you sure you have Amon_Ra's recovery on there? Have you tried to reflash his recovery image?
Thank you guys. I figured out what I was doing wrong.
I guess I missed this over the weekend and I am looking for the original install that I dont need to have root for. I have been reading over the threads here and in the Dev forum and I am not seeing any links to the download for Non-Root users.
I am to much of a ***** to root my phone. i spent way to much cash on it and i am too worried something will go wrong.
So here is want I am asing for
A. The original non root install with instructions on how to do it
or
B. Someone to help walk me through the process of rooting and getting FroYo 2.2 set up on my phone.
Please shoot me a PM if your willing to help out. I am just way to worried if I do this without someone who knows what they are doing I am going to screw up my phone, and my wife would never let me buy another one ...lol
Can somsone help out a fellow Dev, thanks
Sorry I can't post links but here you go
androidandme.com/2010/05/news/how-to-manually-install-android-2-2-on-your-nexus-one/
Ya just found it buried in a thread
Thanks
See if I would have spent another 10 minutes searching I would have found it without having to ask ...lol
Got to remember to scan threads for 30 minutes not 20 before asking ...lol
Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)
Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.
Paul22000 said:
Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)
Click to expand...
Click to collapse
Paul, is that Avatar a picture of YOU?
OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol
attn1 said:
Paul, is that Avatar a picture of YOU?
Click to expand...
Click to collapse
All I wil say is:
λ
LOL ...........
you don't need to root to install froyo and you don't need to hook up your nexus to a pc. my method is pretty simple and it works.
edit: I shouldn't say it's my method. Its actully a backdoor to installing froyo.
theletterj said:
Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.
Click to expand...
Click to collapse
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a nandroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader by flashing the Google Froyo Release with the stock recovery:
Google Froyo Release
You must be on release ERE27 for this to work.
Here's a link to some instructions on how to use the stock recovery program:
jp_macaroni's thread
I suspect that since most people have already rooted or cannot get to ERE27, Paul's guide is the best way to go for them.
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.
jcohenlv said:
OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol
Click to expand...
Click to collapse
Yeah you know, everyone is new once. It's easy to sort out the tripe from the real deal when you've been around the block once or twice. Paul is doing his best to be helpful and not cause more confusion.
The problem isn't that people can't search so much as it is that searches yield too much conflicting information, so lets not jump down people's throats when they ask for a point of clarification. Instead, lets start asking moderators to sticky good info and pulling redundant/bad info so that searches are more meaningful. The number of new threads in here because of the Froyo release is mind numbingly high. Let's all try to exercise some patience.
attn1 said:
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a Nadroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader:
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.
Click to expand...
Click to collapse
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.
theletterj said:
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.
Click to expand...
Click to collapse
You only need to unlock the bootloader. You do not need root.
Unlocking the boot loader allows installation of an alternate recovery, which allows you to install custom software to the existing ROM or to install a custom ROM. It's updating the ROM that allows you to gain root access, not unlocking the boot loader. It goes in this order:
> Unlock boot loader (void warranty - still not rooted)
> Install custom recovery
> nandroid backup (recommended/optional)
> Update ROM (for root access - or not)
The original instructions worked perfect
All that was needed was to change the name to update.zip load it on the root of the SD card then but the phone in bootloader and load recovery from SD.
Took about 5 minutes.
Once the phone came up it did a few things and took about another 5 minutes to chill on the processes then I was able to use the phone without any problems.
So for those interested here are the exact steps:
This is for NON Rooted T-Mobile Version!!!!
To manually install Android 2.2 on the Nexus One, perform the following steps:
1. Download the official Android 2.2 firmware for the Nexus One.
2. Copy the file to your microSD card and name it update.zip (newb warning: not update.zip.zip)
3. Power off your phone.
4. Hold down the VOLUME DOWN button and power it back on.
5. The phone will now search for files like PB00IMG.zip, etc. This is normal. Scroll down to recovery (using Volume Down Key) and press the POWER button.
6. When you see the “/!\” symbol, press the POWER button and the Volume Up button at the same time. You should be presented with a menu and one of the options should be “Apply sdcard:update.zip”.
7. Use the trackball to navigate to “apply sdcard:update.zip” and select it.
8. When you see “Install from sdcard complete”, select “reboot system now”.
Wait 5 minutes, phone will reboot once rebooted let the phone sit for about 5 minutes then you are good to go. It couldn't be any easier
I recently had to give up my rooted preordered Incredible for a refurb due to heat issues and reboot (loop) issues. For those looking for a guide as to what to do if you have to return your phone to Verizon and want to unroot. I welcome any comments to update/add to this information:
1) Make a NANDROID Backup if you want to simply port it over to your new phone
2) Mount your phone as DISK DRIVE
3) Walk the directories and delete any cached thumbnails of web sites you have visited
4) Copy any pictures you want to keep which were saved on the phone
5) Reboot into ClockWork recovery
6) Wipe the Dalvik Cache
7) Wipe the Data/Factory Reset
8) Go back
9) Wipe Data (main menu)
10) Power Down your phone
11) Remove your SD Card
12) Download one of the RUU's which are hosted around the web:
http://www.shipped-roms.com/shipped/Incredible/
13) Turn on your phone and plug it in to your USB
14) Run the RUU and let it do it's thing. When its done, so are you
15) If you have a screen protector, remember to remove it.
Any additions are welcome!
Yes it will revert everything back to normal, that's called an RUU btw
Cool
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
if i root and uninstall some apps, will this restore my phone to stock and allow me to get all future HTC updates?
jdmba said:
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
Click to expand...
Click to collapse
I don't think so, but it's easy enough to do a wipe and then apply the RUU (and hey, for the hell of it, you could wipe again).
Steps?
[deleted ... first post updated]
I'm pretty sure the RUU will completely wipe your phone. However, you can take giantcrazy's advice and wipe before running the RUU.
One more try
[deleted ... first post updated]
Ok, here is what you want to do.
there would be two things you need to un do before sending them back this phone.
make sure it says S-ON.
and then make sure you have stock recovery.
If you have these two things, your gold bod.
Probably to noob to know any better
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, big thanks for any suggestions
A Lex and Er said:
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, thanks
Click to expand...
Click to collapse
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
ACD168 said:
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
Click to expand...
Click to collapse
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is not as thrilled about my learning experience as I am.
I already rooted and unrooted once, will I get stock recovery back after unrooting?
A Lex and Er said:
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is as thrilled about my learning experience as I am.
Click to expand...
Click to collapse
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
A Lex and Er said:
I already rooted and unrooted once, will I get stock recovery back after unrooting?
Click to expand...
Click to collapse
To find out real fast if you have the stock recovery or clockwork-mod recovery, boot into HBOOT, (power off phone, hold vol down and power til screen turns on) and then vol down to select recovery and push the power button I think to select and then if you get a red triangle that means stock recovery.
Also need to return phone
I just got off with Asurion and they are over nighting a replacement. I had rooted my phone, installed some root only apps like wireless tethering and set cpu, removed some bloat like CityID and Tweet/Peep, and changed the boot animation. No custom ROM or radio update.
Then I wanted to get the OTA update so I applied s-off and flashed back to stock recovery.
So what do I need to do to return this phone. I know I will need to apply s-on. Then should I flash a stock 2.1 or just revert the changes I made to boot animation, restore the bloatware, and remove the root apps? Do I need to remove any other files that go with being root?
Thanks.........MM
ACD168 said:
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
Click to expand...
Click to collapse
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
A Lex and Er said:
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
Click to expand...
Click to collapse
First off, you are very welcome my friend, anything I can do to help do hesitate to ask!, and your not hijacking any thread brother, that's what these threads are for!!!
Thats real cool of the VZW employees!!
adb and sdk isnt that difficult I can help you!!
Read my post about warranty exchange.
I know alot of people are "better safe than sorry" mentality. but I have returned 2 phones that were fully rooted, updated, s-off running custom roms and I had no issues. in fact ive never had an issue using warranty exchange. ive exchanged phones that I broke (like broke.. with pieces coming off). I just call and tell the operator lady my phone doesnt work, i dont know why.. it was just working earlier and now it wont turn on.. they send me a new phone and I send back the broken one and everyone is happy.
They only confirm that the numbers on the phone match your account. Not the reasons you are sending it Back. the warhouse guy that opens your box isnt the same guy you talked to, nor do they have information about your phone call to the tech. They simply open the box, scan the numbers and move on.
dont stress to much about it
Great info here
Thanks to every one of you on this thread. I am finally breaking free from WinMo and getting Dinc after a lot of research. I like Verizon but hate the bloatware they pack onto Androids and all the other phones, so I will be fiddleing with ROMs. If I screw up I am looking here first to see how to get it back to stock so I can get my new one with the insurance coverage.
Everytime I get to serouosly looking around these forums I learn great new stuff. I will donate to the XDA someday soon!
Okay. so im a noob. Just need to ask. What do you guys mean by stock recovery? I just rooted my phone but need to unroot to send it in for work at Verizon. Could you help me out?
Hey guys... So I'm enjoying my DHD, It was on the 3 U.K network, unlocked it, rooted t, running leeedroid atm, however, if I ever need to get it back to a stock rom in case I wanna take it back, how do I go about it?
Remember it was originally on 3 U.K.
Thanks
There's threads all over the dev section, go have a look at them.
I think most people who have sent them back with custom ROMs on there have just been flashed back to stock anyway, so they don't seem to mind that much, but just in case.
As far as I'm aware though it's as simple as downloading a piece of software called a RUU for your phone, which in your case is 3, running it with the phone plugged in and then laughing at how easy it is =)
OR
Putting the img on the root of your SD card, going into bootloader (volume down and power on, then bootloader) and it automatically finding it, installing it and then reboot.
But I'd suggest reading a few of the threads about it and using the search button because as with all these things, there's always a risk it'll brick
After a quick search this thread http://forum.xda-developers.com/showthread.php?t=1267345&highlight=ruu has a link to the ruu you might want, then just ota update it.
Brilliant. Sounds good enough.
Also, how can I change the splash screen of the phone? Hate the "3" Logo coming up when I restart the phone.
JccageX2 said:
Brilliant. Sounds good enough.
Also, how can I change the splash screen of the phone? Hate the "3" Logo coming up when I restart the phone.
Click to expand...
Click to collapse
Good good. Like I said though, most people seem to just send it back and they'll do it for you
I'm not positive you can, I've never seen any thread saying how to get rid of it. You can have a nice boot animation though from uot (google "uot kitchen")
Here is a link on changing the bootsplash. Its fairly easy to make one yourself, or you can ask one to be made for you. Their are quite a few posted you might find one you like
http://forum.xda-developers.com/showthread.php?t=1059520
Help! Really need to go back to stock firmware before tomorrow morning, I'm on 3 U.K and need the right RUU!
When I got it it was already on 2.3.3, What RUU Can I flash? Or how else can i go back to stock, help D:
Evening all,
I have a DHD that is stuck in HBOOT/FASTBOOT, or at least that and the stock recovery program is all I can get to.
I tried an AAHK, and it basically tried to do a downgrade and has left the phone with no data, still at s-on, and I can't find an operator RUU(three uk) to flash it back to a useable state.
Is there a three RUU available?
I'm running around in circles as I can't make a gold card, due to not having another DHD available to retrieve the MMC2. All I need is a goldcard and then I can flash a WWE, but I cant find anywhere to make one without the phone or a similar one.
I dont think it turned the microsd properly into a gc, before it tried to downgrade. Is their anyway I can test to see if the memory card has been successfully goldcarded?
Any help would be greatly appreciated.
Thanks
James
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Teichopsia said:
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Click to expand...
Click to collapse
Mine has a lot of those symptoms to be honest. If I vol down/power to get to Hboot, it sits there with no keys being able to be pressed, just highlighted blue FASTBOOT and not even checking for files on memory card
If I just turn it on, it sits at the three splash screen, which i assume is the equivalent of the HTC one for branded phones.
I have now turned it on and left it on as per those linked threads, in the hopes the sd is a proper gold card and it is just slow. Fingers crossed.
Thanks for the pointer
James
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Teichopsia said:
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Click to expand...
Click to collapse
Well what I did, was follow the AAHK instructions, cleaned up my environment etc, went through the install. When it asked to do the downgrade, I said yes, then it asked about wiping and was I sure, so I said yes. It then rebooted the phone and it is now as it is. I pulled the battery and tried vol-down/power, which brings up HBOOT, but it doesnt let me do anything, vol keys and power do not work and it doesnt start looking for image files.
From that thread, it was mentioned it just could be going very slow, and people have just left it overnight. This is what I have done now, and will see if it has accessed the files on the memory card and downgraded properly in the morning.
Thanks
James
Have you tried looking for the RUU here?
Last I remember when aahk downgrades, you will be asked to reboot to basic recovery twice
Panic over, thankfully! Not my phone, you see!
It was so easy to root my S2 and the X10 before that, and the iP3G before that(and custom winmo, and nokia etc etc), I said give it to me, i'll sort you out with some ICS rom action.
Then it all went wrong as explained in my previous posts.
2 days later, i finally found the H3G RUU I needed to get an system on it. Silly branded phones. Took 4 hours to download as it was on a throttled download service(my 100MB leased line usually eats 300MB in seconds, but not this time)
So long story short, into FASTBOOT USB, ran the RUU and it completed and put froyo on the phone, and as a happy coincidence it was at a level that didn't need a downgrade, so AAHK ran through like a trooper, busybox installed and hey presto, ENG S-OFF. IceColdSandwich installed through cwm and one happy mate, who then proceeded to ring his wife and tell her to rent a film, as he would be tinkering with the phone all night lol
It was getting to the point I was going to have to give him my S2, and as I've just taken possession of a Sony SmartWatch, I didn't want to do that!!
Thank for everyone's help and pointers, not sure what went wrong the first time(probably a memory card/incompatibility/goldcard problem), but all sorted now.
James