Related
First of all why this topic:
We get to much unnecessary questions about simple things. I hope this will clear some basic questions. So please read this.
Second:
I'm not responsible for you messing up or bricking your phone.
Third:
Youtube videos are not mine!
Root using Unrevoked , Youtube: (German video but still handy)
PART 1
http://www.youtube.com/watch?v=cIgyQPhIiNE
PART 2
http://www.youtube.com/watch?v=gSjqHmDEk2c
S-OFF Youtube:
http://www.youtube.com/watch?v=_cw9xkS20i0&feature=related
Change Partiton Table:
1. Download Android SDK (http://developer.android.com/sdk/index.html)
2. Download HBOOT .img from alpharev http://alpharev.nl/
3. Place the .img in the Android SDK tools folder.
4. Open command prompt , go to the androidsdk/tools folder.
5. Boot in fastboot (Turn off the phone , hold volume down , and turn power on)
6. Enter -> fastboot flash hboot ***FILENAME***.img
7. Wait 1 sec , and you are finished.
8. Turn off the phone , hold volume down , and turn power on , at the top you can see the partition table used.
ADB , installation and basic commands:
http://www.youtube.com/watch?v=RieL7vHt6AE
Hope this topic will make some things clear , and we will have less unnecessary quistions.
Sector51 said:
First of all why this topic:
Change Partiton Table:
1. Download Android SDK (http://developer.android.com/sdk/index.html)
2. Download HBOOT .img from alpharev http://alpharev.nl/
3. Place the .img in the Android SDK tools folder.
4. Open command prompt , go to the androidsdk/tools folder.
5. Open fastboot.exe
6. Enter -> fastboot flash hboot ***FILENAME***.img
7. Wait 1 sec , and you are finished.
8. Turn off the phone , hold volume down , and turn power on , at the top you can see the partition table used.
Hope this topic will make some things clear , and we will have less unnecessary quistions.
Click to expand...
Click to collapse
You mean boot the phone into fastboot?
Thanks
DesirableHTC said:
You mean boot the phone into fastboot?
Thanks
Click to expand...
Click to collapse
Yes boot in fasboot mode then connect via usb.
What would help greatly in this topic is maybe a small explanation as to why people would need to do it in the first place ?
too complicated for me. Im absolutely useless with adb i need an absolute n00b guide to pull this off
Thanks anyway
DesirableHTC said:
You mean boot the phone into fastboot?
Thanks
Click to expand...
Click to collapse
lol , yes , sorry.
edit
DesirableHTC said:
too complicated for me. Im absolutely useless with adb i need an absolute n00b guide to pull this off
Thanks anyway
Click to expand...
Click to collapse
Edit post...
Take a look at the youtube video..it's sooo easy!!!
First of all why this topic:
We get to much unnecessary questions about simple things. I hope this will clear some basic questions. So please read this.
Click to expand...
Click to collapse
I think the main problem is that it is unclear what everything does. I mean, i've read a lot of threads and searched a lot, but it is unclear to me what fastboot for example is. I know that you can flash radio's etc with it, but is it just the same as flashing from sd card?
Then S-Off, it will disable the nand security, but what can you do with it? That's after a lot of reading not very clear to me.
Believe me, i've read a lot, but coming from WM to Android it's a lot to learn. There is a thread missing where all these things are explained. Of course I can follow tutorials, but I want to know what I am doing. That's missing in a lot of tutorials, that it just explains how you can root,flash, s-off etc, but not the reason why you should do it, or what the function of everything is.
I hope that i'm not offtopic here
Sector51 said:
lol , yes , sorry.
edit
Click to expand...
Click to collapse
lol it now says "fastbook"
DesirableHTC said:
lol it now says "fastbook"
Click to expand...
Click to collapse
typo , fixed
Sector51 said:
6. Enter -> fastboot flash hboot ***FILENAME***.img
Click to expand...
Click to collapse
Fyi you dont need to include hboot in the command, infact the command fastboot flash ***FILENAME***.img will suffice
AndroHero said:
Fyi you dont need to include hboot in the command, infact the command fastboot flash ***FILENAME***.img will suffice
Click to expand...
Click to collapse
hmm..oke I did not know that ... it did it with hboot and it worked ... so i will not change that. tnx.
a guide for us that currently have ap2sd+ (ext3 partion) would be nice, you dont need it anymore if you get the n1 table right? (if use together with AOSP ROM ex oxygen) How to remove it safely etc.
Ive tried to s-off my Wildfire like 3 times. The first one i failed cz i chose HBOOT 1.01.0001. The second one it was stucked on Acquiring Root <method 1> then i waited, then it said click anything to exit. after that my third times, it doesnt detect my handset.
Does it mean my WF already s-off or what?
Thanks a lot to who has answered my question
You can check the HBOOT version by pressing Vol - and power when turning it on.
i already know its 1.01.0002
But then when i tried to do it again, the alpharevx doesnt detect my phone. it only said : Android
Then it wanted i put the serial
nvm, it detects now. But it stucks when it says Thank you for participating
hye...
i am rlly new with this forum just rcently bcame a mmber... n of cz vry noob...
i hving this problem when i try to run the alpharev X it says waiting for device..
so?? what had i done wrong i already know that my HBOOT is 1.01.002..
btw sory my english..
Did you set your phone at USB-debug and charge only?
how to enable the USB debug?? i hve set myphone to chrge only still alpharex doesnt detect myphone..
USB debugging is under Settings->Applications->Development
does it take a long time for the alpharev X to dtect the phone cz i follow all ur instructions it still shows waiting for device..
ss_sk said:
does it take a long time for the alpharev X to dtect the phone cz i follow all ur instructions it still shows waiting for device..
Click to expand...
Click to collapse
No. It detects it almost immediately. Possible solutions:
- Make sure USB Debugging is On, as already said above
- Redownload the AlphaRev X Executable file
- Make sure Drivers are installed and working properly. There are 2 aspects to this:
1) Install HTC Sync, and, Uninstall it. The ADB Drivers will be installed
2) The HBoot Drivers are next. Guide to install that is here:
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
i try to install the hboot driver .. i follow the steps but i get stuck cz i cannot find C:/android-sdk-windows/usb driver to install the diver...
ss_sk said:
i try to install the hboot driver .. i follow the steps but i get stuck cz i cannot find C:/android-sdk-windows/usb driver to install the diver...
Click to expand...
Click to collapse
Its an example. The actual file will be the one you downloaded. (Theres a link in the first line of that guide called Unrevoked Modified USB Driver)
thanks i just install the hboot driver.. install htc sync and uninstall htc sync.. so now i hope alpharev x can detect my phone... again thank u 4 the help..
now rise another problem.. alpharev x can detect myphone but when i enter the beta key base my serial no it says invalid beta key...
im pretty sure i enter the right serial key and the right beta key..
ss_sk said:
now rise another problem.. alpharev x can detect myphone but when i enter the beta key base my serial no it says invalid beta key...
im pretty sure i enter the right serial key and the right beta key..
Click to expand...
Click to collapse
Redownload the alpharev zip and run it, worked for me.
Hmmm which rom to test getting bored of cm7
Sent from my HTC Wildfire using XDA Premium App
There are two possible solutions there again. But, before that, make sure you have entered the right details (Right Serial Number (HT0....), Right HBoot Version, Right Device Model).
Once you are sure these are correct:
- Solution 1 - Copy the beta key in your clipboard from the website, then right click the title bar of the AlphaRevX Application, Click Properties, then check mark Quick Edit Mode. Then Right click anywhere inside the window, it will paste the key.
- Solution 2 - Redownload the AlphaRevX Application from the website and retry.
EDIT: Ninja'ed, Oh well.
lol sory mymistake... actually i really put the wrong beta key...
now that i hve S-OFF myphone what should i do now... sorry i really dont know anything..
Two ways again:
1) Follow this guide:
http://forum.xda-developers.com/showthread.php?t=1130044
2) Use Fastboot (Which I used)
- Download Android SDK - http://developer.android.com/sdk/index.html
- Download ClockworkMod Recovery - http://forum.xda-developers.com/show....php?t=1014498
- Extract the Recovery.img file from the 2nd link, and place it in your SDK Setup Path / Tools (eg: C:/android-sdk-windows/tools)
- Open a Command Window (cmd)
- Browse to the tools folder in this Command Window
- Type the command fastboot flash recovery recovery.img
- It will install ClockworkMod Recovery, you are done.
Then, simply follow Part 3 of this guide to install Custom ROMs and Stuff, irrespective of what you followed above.
http://forum.xda-developers.com/showthread.php?t=824396
i hve download the sdk there are 2 package android-sdk_r11-windows.zip and installer_r11-windows.exe..
so which one should i run??
i dont understand this part [- Extract the Recovery.img file from the 2nd link, and place it in your SDK Setup Path / Tools (eg: C:/android-sdk-windows/tools)]
ss_sk said:
i hve download the sdk there are 2 package android-sdk_r11-windows.zip and installer_r11-windows.exe..
so which one should i run??
i dont understand this part [- Extract the Recovery.img file from the 2nd link, and place it in your SDK Setup Path / Tools (eg: C:/android-sdk-windows/tools)]
Click to expand...
Click to collapse
EXE File.
That post simply means, that when you have completed installing your SDK, then, there will be a folder called "Tools" at your install location. Copy Paste the Recovery.img file to the Tools folder.
ok now i hve copy the recovery.img into tools
then open cmd right?? now what??
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
simple29 said:
so i got up to the part where i need to flash clockworkmod recovery into the command prompt however after i type in fastboot oem rebootRUU and it finds my device i move onto the next step "flash recovery recovery-clockwork-4.0.0.4-vivow.img and it cannot load that
i have left my phone plugged in on the htc screen hoping someone can help me successfully complete the root
many thanks in advance
EDIT: can only start in bootloader now, cant use it as actual phone =[
Click to expand...
Click to collapse
what guide are you using? the recovery img has to be in the same folder as fastboot unless you point it towards a different folder
In the same boat as the OP, I've done everything right and I get this error message in cmd with the black screen and white HTC text.
BTW OP - You can go back to using your phone. Take out the battery (with the usb plug out of the phone or computer) and put it back in and turn the phone on normally. You'll just have to go through the process again of fastboot oem rebootRUU to get back to the black screen with white HTC text.
I'm using the CyanogenMod Wiki HTC Incredible 2 Full Update Guide (since I cannot link it in my post), I dunno what the OP is using. Also, the recovery file is in the appropriate location(s) in the android-sdk-windows folder.
im using the cyanogenmod wiki and i tried putting the recovery image for clockwork into the same folder as fastboot and adb and it still gives me that error and i dont have the technical savvy to figure this out
edit: that would be the platform-tools folder in the android sdk folder, thats what i found people did by googling this
and to finalassault, i took out my battery and tried turning it back on normally i just get stuck at the white screen with the green htc lettering so i clearly messed something up unless i just have to wait a few minutes
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
nothing is working and im completely lost, thanks for the help though
also i still cant turn my phone on normally
drcrawfo said:
Try this guide. Use the clockwork image attached instead of the one from the CM7 guide.
http://forum.xda-developers.com/showthread.php?p=14947083
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Same error, except it's just coming up as not able to load this file instead of the other one. Maybe I possibly screwed up whilst doing AlphaRev?
Edit - I just did it a different way and I didn't get an error message:
sending 'recovery' (5022 KB)...
OKAY [ 25.776s]
writing 'recovery'...
OKAY [ 2.254s]
finished. total time: 28.030s
I guess that worked.
Edit 2 - It "worked" but didn't really do anything else. Might have done something wrong on the AlphaRev step. Actually I'll shut up now, something else showed up.
Edit 3 and final edit - Done and done. That was fun.
how did you get it too work???
simple29 said:
how did you get it too work???
Click to expand...
Click to collapse
It sounds like you may have borked your stock rom....if you can boot to hboot and select fastboot then you should be able to flash the CWM from this link http://forum.xda-developers.com/show...php?p=14947083
Follow the instructions on the link not the one from CM Wiki. Make sure you have fastboot.exe and CWM image from the link in the same folder as your adb. If you're using windows 7 64bit then you'll need to run adb in compatability mode (at least that's what I had to do to get it working in 64bit).
You should then be able to flash a rooted, deodexed stock froyo sense rom from this link by Jcase http://forum.xda-developers.com/showthread.php?t=1138274 or use XGunthers Incredibly Debloated Rom here http://forum.xda-developers.com/showthread.php?t=1138202
That should get you up and runnning. Or you could just jump straight into the GB ASOP roms CM7, MIUI, etc.
Let me know if this works for you....
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
edit: got it in compatibility mode, i suppose i didnt install it right because it looks like it does something for a few seconds then seems to stop
simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
Use the link in my post above.
Sent from my Incredible 2 using Tapatalk
simple29 said:
the first link comes up as 404, appreciate the help
also not quite sure what the compatibility mode is for the adb, kind of a noob here =/
Click to expand...
Click to collapse
It's okay don't worry...I'm pretty new to this stuff too since I just got into rooting about 2 weeks ago.
Compatability mode is an option in windows 7. Right click on the adb.exe file and select Properties. Once that comes up, you'll need to select the compatability tab on top and choose run in 'Windows XP Service Pack 2' mode (sorry I'm at work and don't have access to my win7 machine). Then click ok and it should run in compatability mode.
Then just follow the flash instructions from the link drcrawfo posted up and you should be good to go!
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
ok so idk why but i decided to try taking out the sd card and then when i did the flash recovery cwm thing a whole list of commands came up in the command prompt and i have no clue if thats good or bad or what command i should pick
ill list a few just to see if that helps you guys in helping me out
update <filename>
flashhall
flash <partition> [ <filename> ]
and a few more then there were options that followed
edit: and now for somereason it doesnt flash again but if i do fastboot recovery i still get all those options so is there a way to get the cwm to flash through that way
simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
Hmmm..so you have all your files setup in the same folder and when running the commands from cmd they don't do anything? Does it saying anything is being sent?
This may be beyond my expertise. Have you tried posting in the clockwork mod thread in the development section?
Sent from my Incredible 2
I just want to mention that I didn't end up using the exact commands that are given from the wiki, that didn't seem to work for me. I had to mess around with it (including manually pointing cmd to where it was) to get it to work for me. Had all of the drivers, SDK stuff, the path and everything where they should have been. I hope you get this resolved.
nothing is working out for me this is not fun
same boat as you simple but I can still use my phone. I just gave up as none of the methods seemed to work.
simple29 said:
yea i got the compatibility mode, i must have messed something up pretty bad because adb and fastboot dont seem to do much, they go through a quick thing in the command prompt then dont seem to be active after that, also still cant flash clockworkmod
Click to expand...
Click to collapse
You need to open a command window, change the working directory to where adb/fastboot are located and then type adb.exe at the command prompt.
It sounds like you are trying to double-click the adb.exe from Windows Explorer.
yea i was double clicking, im not too savvy with this stuff, how do you change the directory and all that
hey the name of this tread says it all
i bricked my desire and the only posibility was to flash trough hboot.
when the PB99IMG.zip is flashing it is stuck on SPLASH2
what can i do? do i need another PB99IMG file? how do i know which one is right for me?
does my phone need to be rooted??? cause its not :/ yet
please respond
jann32 said:
hey the name of this tread says it all
i bricked my desire and the only posibility was to flash trough hboot.
when the PB99IMG.zip is flashing it is stuck on SPLASH2
what can i do? do i need another PB99IMG file? how do i know which one is right for me?
does my phone need to be rooted??? cause its not :/ yet
please respond
Click to expand...
Click to collapse
what PB99IMG did you flash? are you branded?
i used this
PB99IMG_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_r elease_159811_signed.zip
i tried also every other pb99img i could find... but other din't work at all
should i have a goldcard or rooted phone?
i think i am not branded, but i am not shure ://
if you have your phone on contract with e.g.Orange, O2, Vodafone etc then you are branded.
With a branded phone you need a goldcard to flash an unbranded PB99IMG.
To create a goldcard follow this tutorial. Notice however you need to skip the part where they find the CID of the SD-Card using the phone, and use this tool instead, COPY DOWN THE CID WITHOUT ANY SPACES, COMMAS ETC. JUST LETTERS/NUMBERS. Then follow from the tutorial.
Once you have a goldcard try to use the same RUU you used (PB99IMG_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_r elease_159811_signed.zip)
I guess that is why this metod did't wokr ha? :/
i will try to make a goldcard tomorow...
THANKS!!
jann32 said:
I guess that is why this metod did't wokr ha? :/
i will try to make a goldcard tomorow...
THANKS!!
Click to expand...
Click to collapse
Hmm maybe, you could also try using a RUU instead?. What network are you on?
EDIT: By the way I just noticed you posted a 2nd thread, there was really no need.
i tried RUU
I tried milions of RUU's befor, but always the same. it shows me that i need more than 30% battery power. and i always had like... atleast 90%
I don't know what network i am on. its my friends phone.
and btw... i'm from slowenia
EDIT: sory for the second post... but i am realy starting to get gray hair... i just can't figure it out :/
bortak said:
Hmm maybe, you could also try using a RUU instead?. What network are you on?
EDIT: By the way I just noticed you posted a 2nd thread, there was really no need.
Click to expand...
Click to collapse
one problem... my/his phone is bricked... i can only accses hboot.
WHAT NOW? (
jann32 said:
one problem... my/his phone is bricked... i can only accses hboot.
WHAT NOW? (
Click to expand...
Click to collapse
you mean with the goldcard? yeah I said skip the part where they get the CID (and actually all of the parts where the phone is involved), just use the tool I sent you to get the CID, put your SD in an adapter and follow the tutorial
bortak said:
you mean with the goldcard? yeah I said skip the part where they get the CID (and actually all of the parts where the phone is involved), just use the tool I sent you to get the CID, put your SD in an adapter and follow the tutorial
Click to expand...
Click to collapse
would be ok if i use my OWN desire, switch the sd cards and try it to go to the recovery (since i my desire doesn't work with his sd card, i tried that) and mount sd card trough recovery...
cause i don't have the adapter... do you think that would be a good idea??
jann32 said:
would be ok if i use my OWN desire, switch the sd cards and try it to go to the recovery (since i my desire doesn't work with his sd card, i tried that) and mount sd card trough recovery...
cause i don't have the adapter... do you think that would be a good idea??
Click to expand...
Click to collapse
yeah that'd work exactly the same
when making goldcard.... i+m stuck at adb devices... in setup ADB procedure.
i should find my device pluged in in the computer with thi comand after i go with cmd in the specificated file....
but it says that adb is not a command, but is should be!
i followed the video instructions precicely ://
do you have any ideas what to do ??
jann32 said:
when making goldcard.... i+m stuck at adb devices... in setup ADB procedure.
i should find my device pluged in in the computer with thi comand after i go with cmd in the specificated file....
but it says that adb is not a command, but is should be!
i followed the video instructions precicely ://
do you have any ideas what to do ??
Click to expand...
Click to collapse
go to the folder where you installed adb and note the file directory. If you're having problems there's a section on my guide that can help you out
in cmd type
Code:
cd #file directory#
then carry on with the instructions on the tutorial
i found the directory
and yes i go into the folder android sdk and into the map tools...
then i should type adb devices
but it saids that the adb isn't a comand
jann32 said:
i found the directory
and yes i go into the folder android sdk and into the map tools...
then i should type adb devices
but it saids that the adb isn't a comand
Click to expand...
Click to collapse
woops thanked you by accident lol. tried to quote..
http://developer.android.com/sdk/index.html download this and install this sdk cos i dunno what you did. then make the directory to wherever you install it. Remember to download platform tools from sdk manager.
no... still the same afte installing platform tools
should i install everything??
-android 4.0...
-and so on
perhaps because i have widows 7?
Did you also install USB drivers? Good tutorial for installing sdk can be found in my signature over adb / fastboot guide.
SwiftKeyed from dGB with Transparent XDA App
Hello. I have 2 questions.
1. > What is difference between stock radio [5.xxx] & newest radio [32.xxx] ?
2. > How can i flash radio with DATA++ hboot.
THX!
sry 4my bad english...
zingga said:
Hello. I have 2 questions.
1. > What is difference between stock radio [5.xxx] & newest radio [32.xxx] ?
2. > How can i flash radio with DATA++ hboot.
THX!
sry 4my bad english...
Click to expand...
Click to collapse
It seems you know about radios, so I reckon you know about AdamG radio thread. Cared to read the first post with understanding?
zingga said:
Hello. I have 2 questions.
1. > What is difference between stock radio [5.xxx] & newest radio [32.xxx] ?
2. > How can i flash radio with DATA++ hboot.
Click to expand...
Click to collapse
1. > the newest is 5.17.05.23, where did you even find 32.xxx?
2. > as you on data++ hboot - via fastboot only see alpharev.nl for explanation
kotag82 said:
the newest is 5.17.05.23, where did you even find 32.xxx?
...
Click to expand...
Click to collapse
The latest radio is 32.56.00.32U_5.17.05.23
All radios start with "32" but the number after the "U" is the important one.
weimar-zero
You can flash it via Android Debug Bridge (install ADB on your PC and the HTC driver from HTC Sync).
1. start your Desire in "fastboot-mode" (bootloader / fastboot)
2. You´ve to put the radio-file into the ADB folder (on your PC)
3. Change the name of the radio file in "radio.img"
4. connect PC to Desire via usb
5. make the test on ADB* (attached pic, input "adb devices" -> push enter!). If ADB works you´ll see the serial number of your Desire.
6. ADB input on Windows CMD* to flash the radio "fastboot flash radio radio.img" -> push enter!
*you´ve to go to the ADB Folder with CMD
regards weimar-zero
as always, no guarantees, everything on your own risk
Weimar-zero said:
You can flash it via Android Debug Bridge (install ADB on your PC and the HTC driver from HTC Sync).
1. start your Desire in "fastboot-mode" (bootloader / fastboot)
2. You´ve to put the radio-file into the ADB folder (on your PC)
3. Change the name of the radio file in "radio.img"
4. connect PC to Desire via usb
5. make the test on ADB (attached pic "adb devices"). If ADB works you´ll see the serial number of your Desire.
6. ADB input on Windows CMD* to flash the radio "fastboot flash radio radio.img" -> push enter!
*you´ve to go to the ADB Folder with CMD
regards weimar-zero
as always, no guarantees, everything in your risk
Click to expand...
Click to collapse
You made some big mistakes in your guide:
Radios do not get flashed via ADB, they get flashed via fastboot. And for this is:
1. Fastboot needed (extract file to C:\android-sdk), which is not included in newest SDK
2. Phone needs to be in Fastboot mode, not ADB mode: Turn phone off, press and hold Back + Power Button until FASTBOOT in red higlighted capital letters appears.
Now connect phone to computer via USB (FASTBOOT USB should appear). Then start CMD and change to android-sdk-folder
Code:
cd C:\android-sdk
Now enter
Code:
fastboot devices
Output should show be
Code:
List of devices attached
HTXXXXXXXX device
The "XXXXXXXX" are placeholde for a number (that's your phone's serial number).
If you get this kind of output: download the radio you want to flash as zip. THEN DO NOT RENAME IT!!!. Extract it and copy the radio.img to C:\.
Then enter in CMD the following command
Code:
fastboot flash radio radio.img
.
Now drink a cup of tea/coffee and wait until the process is done.
For an easier flashing process I recommend to use Android Flasher (read carefull before using):
http://forum.xda-developers.com/showthread.php?t=794638
Thank you MatDrOiD,
Your right, you don´t have to rename it, because in the zip the file has the name "radio.img"
Step 3 is not necessary
I did it on this way and it works pretty fine.
@MatDrOiD please tell me my big mistakes in the guide
You've just described in the same way, but just a bit more readable
ps: "ADB mode", what is this? I've never heard.
regards weimar-zero
Weimar-zero said:
Thank you MatDrOiD,
Your right, you don´t have to rename it, because in the zip the file has the name "radio.img"
Step 3 is not necessary
I did it on this way and it works pretty fine.
@MatDrOiD please tell me my big mistakes in the guide
You've just described in the same way, but just a bit more readable
ps: "ADB mode", what is this? I've never heard.
regards weimar-zero
Click to expand...
Click to collapse
IMHO these two mistakes are big ones (descending order):
1.) Telling the OP to rename the file. Reason: If something gets wrong in the process of Radio flashing, the Phone might be completely bricked!
2.) Telling the OP to use ADB, which does not work in Fastboot-mode, in which the Phone has to be. As already mentionend, Radio-flashing is a very sensitive process, all advices should be correct.
To understand what ADB / Fastboot are and what their difference is, I recommend you to read the guide in my signature about it. Would make me happy, if you tell me afterwars, wether you understand everything.
Thanks matdroid 4 info. But i don't see answer on 2nd questions?
So was diffirence between latest & others radios?
Is it difference just in FMradio like in app?
thanks
Updating Radio means updating your hardware. This can cause good things (better signal, battery life), but also the opposite. Radios are not good in general. Some users deal with this one, some with others.
For what its worth my advice to OP would be if current radio works fine with Rom then leave well alone, anything goes wrong with radio flash = proper brick
Sent from my HTC Desire using Tapatalk 2