Related
Hey everyone, I started this guide myself after coming to the conclusion that there wasn't any real clear or even good guide to flashing a recovery after having to use the HTCDEV tool to unlock your bootloader. If you had to use the HTCDEV tool method it is becasue your bootloader is version 1.50 and the revolutionary method will not work for you at this point in time.
This is my own guide I wrote and is soley my own work despite what some insecure noobs think on these forums. I'm not claiming to have discovered this method first, I'm just sharing my knowledge in a neat little guide to just be of any help to those who need it!
Please visit here if you havent used the HTCDEV Tool yet to unlock your bootloader. [http://htcdev.com/bootloader/]
After using the HTCDEV tool you will need
a recovery and Superuser permissions to have root access. The only recovery I was able to flash and get working correctly using this method was the exact version of cwm that you can download from this guide. I was not able to get TWRP or any other recovery to work this way...
**make sure you have ADB set up on your computer (download AndoridSDK and open up SDK Manager and install the add on packages)**
Step 1: Download the cwm zip from this post and place the .img file in your
androidsdk/tools folder. Then download the su zip folder and place this on the root of your SD card
Step 3: Reboot the phone into bootloader (Vol down + Power), then select fastboot usb next.
Step 4: open up your command prompt and enter these lines of command
Code:
CD C:\AndroidSDK\tools
(your's might look different)
Code:
fastboot flash recovery c:\androidsdk\tools\cwm-4.0.1.4-shooter(1).img
**you should now see that it will flash the recovery in your command promt window**
Step 5: When its done flashing the recovery go ahead and boot into recovery and flash the su zip file so you will have root permissions!!
You should be done after this you can flash roms or reboot normally.
Nevermind.
Couple things wrong/could be done better with this post, no offense, just things you'll want to correct or add.
~ You're going to want to explain how to get ADB going, because as of the past few versions, it's very convoluted to get.
~ You can't directly reboot into Fastboot (at least, not without being fully rooted already). The phone must be fully turned off, and before you even do that, you need to turn off the "fast boot" option in the Android power settings completely off. That "fast boot" option is completely unrelated to Fastboot mode but if you leave "fast boot" checked on, the phone doesn't fully power off when you press and hold power.
~ As far as formatting goes, you'll want to wrap the command prompt lines in code tags which are these: [.code].[./code] (no periods). That way, it looks like this:
Code:
cd C:\AndroidSDK\tools
The same goes with the fastboot command, because otherwise it's confusing as to what the entered code really should be.
~ You've packaged the recovery as a RAR, when in reality, you don't actually need to package it up as anything, you can directly upload the img. Also, for the sake of convenience, because not everyone has the same ADB path (and by extension, not everyone will be able to copy and paste the command you put up) you can rename the image to just "recovery.img" because when you're tying the fastboot recovery flash command out, it's irritating to type out the full name of the recovery.
The HTC unlock method does not give you S-Off. You'll still be S-On, but you're able to install a recovery then flash the SU zip. Its important to note that the newest version of cwm that I was able to get working was 4.0.1.4. I was not able to get any version of TWR working. You are also unable to flash custom boot.img's, making kernel modification impossible.
Thanks for the input! I will revise the guide just wanted something quick for people out there that were thinking that they could not have any recovery after using the htc dev tool, and thus not being able to flash any custom roms.
I never got TWRP flashed either, or any other version of cwm except the one I posted on the thread...but its better than no recovery and it gives you the ability to obtain root access so you can also use rooted apps.
I have now used both revolutionary and the HTCDEV tool multiple times, the HTCDEV tool being a bigger pain in the rear than I had figured but it was only because no other recovery would install except for cwm via fastboot adb.
As for custom kernels, maybe using a rom with a baked in kernel would be a good option since it would flash together with the rom.
Also, It would not let me attatch the file as a .img file there were errors so I had to zip them in order to attatch them in my thread.
Unknown_Hero said:
Thanks for the input! I will revise the guide just wanted something quick for people out there that were thinking that they could not have any recovery after using the htc dev tool, and thus not being able to flash any custom roms.
I never got TWRP flashed either, or any other version of cwm except the one I posted on the thread...but its better than no recovery and it gives you the ability to obtain root access so you can also use rooted apps.
I have now used both revolutionary and the HTCDEV tool multiple times, the HTCDEV tool being a bigger pain in the rear than I had figured but it was only because no other recovery would install except for cwm via fastboot adb.
As for custom kernels, maybe using a rom with a baked in kernel would be a good option since it would flash together with the rom.
Click to expand...
Click to collapse
...why did you use the HTC Dev tool after Revolutionary? Do you realize what you've done by doing that?
I hope what you meant was that you had the 2.3.4 stock update and tried to use Revolutionary, found out it didn't work, and then tried the HTC Dev tool, because running the HTC Unlock after successfully using the Revolutionary tool is not the best idea on the planet.
The downside to using HTC's Unlock (for those who think 'oh, i have root and recovery, i'm ok) is that you can't use custom kernels or updated Radio stacks.
Baked in kernel won't matter, the boot partition (as far as I can tell) is still locked.
So you just troll chat rooms and kang people's work and claim it as your own eh? Way to kang this entire writeup. You didn't figure this out.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
First off I didnt use both rooting methods...I used revolutionary on my own evo and had to use the devtool on a friends....I'm not that stupid I know the difference between the two. The reason I started this post was because when I was having difficulties when flashing a recovery on my freinds phone after using the dev tool I couldn't find any help or thread on getting this to work. Maybe I didn't look hard enough but the only help I got was off android forums and there was a real vague description on getting the recovery to flash...I was trying to help not troll...nor did I calim this was MY discovery at all in my thread lol.
Unknown_Hero said:
First off I didnt use both rooting methods...I used revolutionary on my own evo and had to use the devtool on a friends....I'm not that stupid I know the difference between the two. The reason I started this post was because when I was having difficulties when flashing a recovery on my freinds phone after using the dev tool I couldn't find any help or thread on getting this to work. Maybe I didn't look hard enough but the only help I got was off android forums and there was a real vague description on getting the recovery to flash...I was trying to help not troll...nor did I calim this was MY discovery at all in my thread lol.
Click to expand...
Click to collapse
That's ok, I assumed that you didn't run both on your phone, I just wanted to make sure. I think the guy above me might be going overboard though.
Unknown_Hero said:
First off I didnt use both rooting methods...I used revolutionary on my own evo and had to use the devtool on a friends....I'm not that stupid I know the difference between the two. The reason I started this post was because when I was having difficulties when flashing a recovery on my freinds phone after using the dev tool I couldn't find any help or thread on getting this to work. Maybe I didn't look hard enough but the only help I got was off android forums and there was a real vague description on getting the recovery to flash...I was trying to help not troll...nor did I calim this was MY discovery at all in my thread lol.
Click to expand...
Click to collapse
Liar. You copied everything out of the Synergy chat room after someone else did it and there are chat logs to prove you kanged it.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
Thank you I appreciate constructive criticism I know you were just trying to help and my post was pretty noob I don't know why McLabia is trippen though...oh well not worried about it I have much to learn and you got to start somewhere!
McLabia said:
Liar. You copied everything out of the Synergy chat room after someone else did it and there are chat logs to prove you kanged it.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
Click to expand...
Click to collapse
Your joking right???? I have never even used synergy chat room bro...I created this noob post myself and im being 100 percent honest you need to chill and be a little respectful. I'm for sure not a liar and did not "Kank" this post from anyone dude why would I need to steal info about flashing a recovery??? Wow, some people have their pants on way too tight lol.
Unknown_Hero said:
Thank you I appreciate constructive criticism I know you were just trying to help and my post was pretty noob I don't know why McLabia is trippen though...oh well not worried about it I have much to learn and you got to start somewhere!
Click to expand...
Click to collapse
Im not tripping. I'm pointing out the fact that you straight trolled the chat and the posted this like it was yours. You did nothing. Someone else did. Straight up thief.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
McLabia said:
Im not tripping. I'm pointing out the fact that you straight trolled the chat and the posted this like it was yours. You did nothing. Someone else did. Straight up thief.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
Click to expand...
Click to collapse
Your outta your mind homie I didn't steal this from anyone and i definetely wasn't in a chat room go ahead and show me some proof then lets see it, prove that im a liar and a theif your going to look like such an idiot when you prove yourself wrong lol...man I thought this was a joke but this guy is too serious
Unknown_Hero said:
Your outta your mind homie I didn't steal this from anyone and i definetely wasn't in a chat room go ahead and show me some proof then lets see it, prove that im a liar and a theif your going to look like such an idiot when you prove yourself wrong lol...man I thought this was a joke but this guy is too serious
Click to expand...
Click to collapse
Incoming by the person that Actually figured this out and putting another kanger on blast.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
was asked pics be removed
This doesn't even prove anything!!! Its not even close to what i posted LOL. Buddy you need to get a life man I wasn't in the chatroom and what I posted is completely different...what your saying then is that everyone has kanged something at one point in time...just because a topic was brought up and there's a post about elsewhere means it's stolen?? I hope you get all your issues figured out in your sad life bro I'm going to continue mine content on the fact that I'm not a kanger lol you say I have alot of respect for the devs and users on XDA and would never steal some ones work for the sole purpose of stealing the spotlight from them...I don't care about that I don't even have that kind of time in my day troll chatrooms to "kang" peoples work. You sound like a 16 year old emo girl get a grip...I came up with this on my own and I'm proud of it!
Sent from my PG86100 using XDA Premium App
Unknown_Hero said:
This doesn't even prove anything!!! Buddy you need to get a life man I wasn't in the chatroom and what I posted is completely different...what your saying then is that everyone has kanged something at one point in time...just because a topic was brought up and there's a post about elsewhere means it's stolen?? I hope you get all your issues figured out in your sad life bro I'm going to continue mine content on the fact that I'm not a kanger lol you say
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Lol. Busted and still denying it. Sad. I hope your phone bricks.
Sent from my rooted, Dark Horse INFECTED Synergy bolt running Ziggys latest.
Lol busted from two screenshots that show absolutely nothing to prove...
my phone won't brick because I know how to dev on it, and I don't need chatrooms to do it
looks like your Busted for being a Nub
Unknown_Hero said:
Lol busted from two screenshots that show absolutely nothing to prove...
my phone won't brick because I know how to dev on it, and I don't need chatrooms to do it
looks like your Busted for being a Nub
Click to expand...
Click to collapse
LOL. Two screenshots that show the time that it was done compared to your post. Give it up thief. Youre a terrible liar and a straight up kanger.
I did my research on how to install ROMS with a locked S On and Kernels, but just got even more confused about the process. I am coming from an Evo 4g CDMA.
I have H BOOT 1.5 unlocked S ON. My back up was lost. I tried to flash something like the newest MIUI using TWRP 1.1. w/e. I can't get past the boot screen for MIUI. As I was reading up on the forums, it seemed to me that you had to use a program called Flash Image GUI to get a kernel going on a ROM. Though, here is where I was confused. If a ROM has a kernel in it and I flash the ROM, does the Kernel part of that flash not get set up as well?
Would I need to flash the rom like normal from the SD Card then use something separate to flash a Kernel? If so, I am kinda boned. I can't get into the phone, just the recovery and can't get that program installed on the phone Trying to flash up Xplode now to see if maybe I just got a bad download.
If these questions were answered, please forgive me, I did try to find the answers, but as I read up more and more, it was getting to be more and more confusing to my personal issue at hand.
Thanks for the help!!
If you grab the kernel from your Miui zip, it's in the zips root called boot.img
Put that into your folder with your fastboot exe
Boot into bootloader the same as when you flashed the CWM
Use fastboot command... fastboot flash boot boot.img
this will flash the kernel and you should be able to boot up properly
Oh, well that is the problem. I had someone else flash TWRP for me. Guess I need to find out more on how to flash up that to get the kernel going. This S On thing is a massive PITA, lol. Guess once I get the phone up and going and I can use that program, things will be way easier
Nametaken said:
Oh, well that is the problem. I had someone else flash TWRP for me. Guess I need to find out more on how to flash up that to get the kernel going. This S On thing is a massive PITA, lol. Guess once I get the phone up and going and I can use that program, things will be way easier
Click to expand...
Click to collapse
I see. i skipped the how to part since i thought you had alrady flashed the CMW your self, it's fairly easy.
you need..
1) to install the evo 3d usb drivers.. filename HTCDriver3.0.0.007.exe .sorry i don't have a link, i got them off these forums somewhere
2) you need the fastboot.exe , again search google/these forums
then shut down your phone
pull battery out, then back in
hold down volume- (minus) and then hold the power button as well, only let go once in the bootloader, choose the fastboot option then insert usb cable to phone->pc .. you should see fastboot-usb message come up on your phone
then you can type out that fastboot command in the previous post from a dos command prompt, from the directory with your fastboot exe and boot.img
It's easier to put rom you want on the SD card make sure debug is on.
Adb reboot bootloader . Now
Fastboot boot recovery.img now wipe and flash rom you are good to go man. Works flawless .
Sent from the Reaper.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Sorry about posting in the wrong area.
What I did, which can help out other 3D noobs is this:
Since I just unlocked and have no back up, my kernel was still stock
Downloading a stock rom and moving it to my phone via comp, twrp recovery mode>> USB Toggle allows you to connect to PC! Put the rom on the main part of the SD card and just flash like normal.
Here you should be able to boot up like normal again.
Let me say, Flash Image GUI is a noobs friend till you can learn to use adb more.
I was told you can put a Rom on your card and just flash allowing the kernel to flash as well. I have not had success with this with HBoot 1.5 S On.
Flash Image GUI:
Download the rom you want, Aosp to Sense is fine.
Open Flash GUI and choose the Browse option.
Locate your rom on your card and choose it.
The app will give you a message saying the rom is big yada yada, say yes.
Wait a few moments as it finds the kernel. Once it does, choose flash Image.
Choose reboot recovery and flash the exact rom you picked with the App. Reboot and win.
This is just what I, a noob, have found to work.
I have NOT been able to just flash any rom on the SD Card and have it work. Flash Image UI has NOT been able to get Virus' Rom to load
A's I find more noob friendly tips I can report.
Thanks everyone else for the input! I won't lie, I came from an Evo 4g and am totally lazy as I am used to S Off and just flashing away. S On, I hate you. ADB, I fear you. Flash Image GUI, I want to marry you!
CDMA 3D, I wish we had more AOSP lol
Hope this helps out some people.
Sent from my PG86100 using XDA
Nametaken said:
Sorry about posting in the wrong area.
What I did, which can help out other 3D noobs is this:
Since I just unlocked and have no back up, my kernel was still stock
Downloading a stock rom and moving it to my phone via comp, twrp recovery mode>> USB Toggle allows you to connect to PC! Put the rom on the main part of the SD card and just flash like normal.
Here you should be able to boot up like normal again.
Let me say, Flash Image GUI is a noobs friend till you can learn to use adb more.
I was told you can put a Rom on your card and just flash allowing the kernel to flash as well. I have not had success with this with HBoot 1.5 S On.
Flash Image GUI:
Download the rom you want, Aosp to Sense is fine.
Open Flash GUI and choose the Browse option.
Locate your rom on your card and choose it.
The app will give you a message saying the rom is big yada yada, say yes.
Wait a few moments as it finds the kernel. Once it does, choose flash Image.
Choose reboot recovery and flash the exact rom you picked with the App. Reboot and win.
This is just what I, a noob, have found to work.
I have NOT been able to just flash any rom on the SD Card and have it work. Flash Image UI has NOT been able to get Virus' Rom to load
A's I find more noob friendly tips I can report.
Thanks everyone else for the input! I won't lie, I came from an Evo 4g and am totally lazy as I am used to S Off and just flashing away. S On, I hate you. ADB, I fear you. Flash Image GUI, I want to marry you!
CDMA 3D, I wish we had more AOSP lol
Hope this helps out some people.
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
ADB is pretty simple to flash with lol
All you do is keep a copy of the recovery.img you are using in your adb folder...
You hold shift down right click on the folder that adb is in platform tools folder is where it's at say open cmd prompt to it. That is the fast painless method
Make sure you have a rom on your sd card.... Also that debug is turned on...
Plug phone in hook to computer...
ADB:
adb reboot bootloader
now:
fastboot boot recovery.img takes you into recovery...
Now wipe don't wipe SD card...
Flash rom your set works on virus roms and any other rom 0 issues
Also Flash GUI works for everyone nothing wrong with it....
I just prefer Good Old Adb to do my work If you need any help feel free to ask man.. I'll do what I can to help ya out if you get stuck..
reaper24 said:
ADB is pretty simple to flash with lol
All you do is keep a copy of the recovery.img you are using in your adb folder...
You hold shift down right click on the folder that adb is in platform tools folder is where it's at say open cmd prompt to it. That is the fast painless method
Make sure you have a rom on your sd card.... Also that debug is turned on...
Plug phone in hook to computer...
ADB:
adb reboot bootloader
now:
fastboot boot recovery.img takes you into recovery...
Now wipe don't wipe SD card...
Flash rom your set works on virus roms and any other rom 0 issues
Also Flash GUI works for everyone nothing wrong with it....
I just prefer Good Old Adb to do my work If you need any help feel free to ask man.. I'll do what I can to help ya out if you get stuck..
Click to expand...
Click to collapse
You can not flash some ROMS through ADB/Fastboot with s-on, it just doesn't work no matter which way you go about it. Flashing a recovery is easy but that was not the OP's problem. The "noob" way that the OP suggested is the only way to get roms with custom boot.img in the zip to stick. I just installed CM9 and ADB/fastboot was of no use. Getting into recovery is easy but will not provide results unless you have used FlashImageGUI.apk first on a working ROM.
Nether CWM nor TWRP work to flash such ROM's with the right boot.img. You must use FlashImageGUI.apk!
StevetotheH said:
You can not flash some ROMS through ADB/Fastboot with s-on, it just doesn't work no matter which way you go about it. Flashing a recovery is easy but that was not the OP's problem. The "noob" way that the OP suggested is the only way to get roms with custom boot.img in the zip to stick. I just installed CM9 and ADB/fastboot was of no use. Getting into recovery is easy but will not provide results unless you have used FlashImageGUI.apk first on a working ROM.
Nether CWM nor TWRP work to flash such ROM's with the right boot.img. You must use FlashImageGUI.apk!
Click to expand...
Click to collapse
I never had any issues using cwm the older version 4.0 to flash any rom the fastboot method Anyway's older TWRP and Newest CWM had some issues with not wiping right to flashing funky...
I will help the OP out if he ever gets stuck
Yeah reaper your right! I think I came off like a ****, I am one, but didn't mean to come off sounding snide.
Sent from my HTC Evo 3D using XDA
StevetotheH said:
Yeah reaper your right! I think I came off like a ****, I am one, but didn't mean to come off sounding snide.
Sent from my HTC Evo 3D using XDA
Click to expand...
Click to collapse
It's all good man no worries Your cool
Sent from my PG86100 using xda premium
Dah da dat ta ta! (Swoops in with my 2 cents)
See the Guide/Flashing Notes in my signature for a walkthru for flashing roms, recoveries, etc. All up to date. Choose your method: fastboot & recovery or flashimage & recovery.
Note: TWRP 2.0 with Dumlock is a workaround to avoid using fastboot (pc). FlashImage is not a requirement, its also a workaround vs fastboot.
mpgrimm2 said:
Dah da dat ta ta! (Swoops in with my 2 cents)
See the Guide/Flashing Notes in my signature for a walkthru for flashing roms, recoveries, etc. All up to date. Choose your method: fastboot & recovery or flashimage & recovery.
Note: TWRP 2.0 with Dumlock is a workaround to avoid using fastboot (pc). FlashImage is not a requirement, its also a workaround vs fastboot.
Click to expand...
Click to collapse
Nice I was wondering when you was gonna pop in . LOL
Sent from my PG86100 using xda premium
Thanks erryone. I hope others were able to get some help here that are new to 3vo and flashing. I am so waiting for a nub proof s-off method.
Sent from my PG86100 using XDA
There is the HBOOT downgrade. I have ZERO linux experience whatsoever and thought the process was very easy. I know it says to 'brick' the phone, but it is honestly not that scary. I have done two of these already both being successful on the first attempt. The live cd by closeone actually takes care of almost everything, except for actually doing the brick. Trust me being on 1.40 s-off is much much nicer.
So I was trying to update my old energy ROM to ICS and I'm kind of hosed. Got instructions here: http://forum.xda-developers.com/showthread.php?t=1362759
Basically:
- Root your device
- Install a custom recovery
- Install the downloaded ROM .zip found in post #3
- Make sure to do a Factory Reset / Wipe before installing ROM
For the record, these steps are out of order. Steps 4 and 3 are switched and I didn't notice till it was to late. What I did next was do the factory reset and then try to re-install the ROM. Everything seemed to go fine until it was time for a reboot. Then it froze on the HTC logo.
Could use some ideas as to what my next move should be. Since it was a previous version of Energy ROM + Faux kernel, phone is definitely rooted, etc. Perhaps I should start over with a stock Gingerbread ROM?
jcllings said:
So I was trying to update my old energy ROM to ICS and I'm kind of hosed. Got instructions here:
...
Perhaps I should start over with a stock Gingerbread ROM?
Click to expand...
Click to collapse
Apparently I am also supposed to flash the kernel as per this thread which I've finally found:
http://forum.xda-developers.com/showthread.php?t=1645641
In order to find it, I had to search for it using Google as this forum software is so haphazard. Also not mentioned in the instructions. Will try this next if I can get at it through just the custom recovery.
Still wrong. Coming from GB and going to ICS you need to flash the ICS RUU in bootloader. I don't know how many times its been mentioned or how many other threads have been started because of this issue.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
First im not resbonsible for anything that can happen to your phone this what i do if it didnt work im not resbonsible.
If you are rooted via HTCDev S-On Hboot 1.490018 and up you need to Run a command prompt and flash the boot.IMG that comes with the ROM (if not included extract the ROM and search for its in the .Zip file then move that file into a folder in the Root lf ur C Drive put your phone into fastboot mode (remove battery then put it back then press lock/on button and the volume up button at the same time) then connect it to your PC and run command prompt press on start and search for cmd then run it and type the following :
Cd c:\android (or whatever you named the folder)
After that type:
Fastboot flash boot boot.IMG
After its done unplug your phone from ur PC reboot it and it should work perfectly (it may stay at the HTC Logo for 10-20 minutes)
HOPE IT WORKS ENJOY!
Sent from my GT-P7500 using XDA Premium HD app
Double0EK said:
Still wrong. Coming from GB and going to ICS you need to flash the ICS RUU in bootloader.
...
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Click to expand...
Click to collapse
Awesome. Thanks for the tip. Will see what I can make of it.
I notice that there is a file, PH85IMG.zip in the same directory as the modded ROM. The name isn't very descriptive. Clue?
jcllings said:
So I was trying to update my old energy ROM to ICS and I'm kind of hosed. Got instructions here: http://forum.xda-developers.com/showthread.php?t=1362759
Basically:
- Root your device
- Install a custom recovery
- Install the downloaded ROM .zip found in post #3
- Make sure to do a Factory Reset / Wipe before installing ROM
For the record, these steps are out of order. Steps 4 and 3 are switched and I didn't notice till it was to late. What I did next was do the factory reset and then try to re-install the ROM. Everything seemed to go fine until it was time for a reboot. Then it froze on the HTC logo.
Could use some ideas as to what my next move should be. Since it was a previous version of Energy ROM + Faux kernel, phone is definitely rooted, etc. Perhaps I should start over with a stock Gingerbread ROM?
Click to expand...
Click to collapse
I don't want to put down energy rom, but it hasn't been updated since the original leak, and the instructions were never clarified - he simply never explained the PROPER way to switch from gingerbread to ICS. ARHD gives a better explanation, but I think post #2 in the everything ICS thread gives the best and links to everything you should need..
You have to be careful anytime you are switching to a totally new OS. All the devices I know, switching from 2.1 to 2.2, or 2.2 to 2.3.. or to 4.0+.. it is USUALLY not just a "flash over the old OS".. just something to keep in mind for any of your other or future devices..
yuseiatlas said:
First im not resbonsible for anything that can happen to your phone this what i do if it didnt work im not resbonsible.
...
After its done unplug your phone from ur PC reboot it and it should work perfectly (it may stay at the HTC Logo for 10-20 minutes)
HOPE IT WORKS ENJOY!
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
I'm trying to get RUU now. When I tried the above earlier, got as far as the wirly Energy rings though but then it restarts.
Silentbtdeadly said:
I don't want to put down energy rom, but it ...
other or future devices..
Click to expand...
Click to collapse
Well as far as I know, it ain't like he is getting paid much so it would seem to be a miracle if any of this stuff gets updated. ;-) If I don't have this figured out by Tuesday, I'll use it as an excuse to get a new phone. This one has a crack or two in the screen anyways.
Still, even so I would MUCH rather get this one working again. 'specially since I'm between software gigs & cash is tight. If Energy ROM hasn't been updated and there's a better and/or more complete set of instructions maybe I should be looking at something else. Will continue hunting through these forums for info but can use all the help I can get since this forum software ain't exactly friendly. Probably best to see if I can get it back to stock on ICS and then work forward from there. Having said that, I have an RUU that I am working with, its: PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip
Tried just flashing it but apparently there's more to it than that.
Latest problem is that I can't get it re-locked without enabling USB debugging. Can't do this since I don't have a working OS. Can it be done from CLI or recovery?
Uh.... hmmm... mysterious. Seems to have fixed itself. Will try a restart and see what happens.
jcllings said:
Latest problem is that I can't get it re-locked without enabling USB debugging. Can't do this since I don't have a working OS. Can it be done from CLI or recovery?
Uh.... hmmm... mysterious. Seems to have fixed itself. Will try a restart and see what happens.
Click to expand...
Click to collapse
I was saying that there are some other options, other roms, that have better instructions and have been updated fairly well.. that is all.
The thread I was talking about by glacierguy is here - it links to tons of resources and should answer most questions you may come up with. For example it has "Relock phone (fastboot oem lock)" you can issue fastboot commands while your phone is booted into the bootloader - so this has nothing to do with usb debugging..
There is tons of information here, I know it isn't absolutely organized, but there are a lot of guys here who tried to make the information as easy to find as possible..
Did u try to restart it again it usually takes a couple of times but anyway should either return to stock or use the RUU for the ICS ROM
Sent from my GT-P7500 using XDA Premium HD app
jcllings said:
Well as far as I know, it ain't like he is getting paid much so it would seem to be a miracle if any of this stuff gets updated. ;-) If I don't have this figured out by Tuesday, I'll use it as an excuse to get a new phone. This one has a crack or two in the screen anyways.
Still, even so I would MUCH rather get this one working again. 'specially since I'm between software gigs & cash is tight. If Energy ROM hasn't been updated and there's a better and/or more complete set of instructions maybe I should be looking at something else. Will continue hunting through these forums for info but can use all the help I can get since this forum software ain't exactly friendly. Probably best to see if I can get it back to stock on ICS and then work forward from there. Having said that, I have an RUU that I am working with, its: PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14.550L.17DC_30.78.550L.15_release_259626_signed.zip
Tried just flashing it but apparently there's more to it than that.
Click to expand...
Click to collapse
If you're.gonna flash that last file you mentioned, you need to rename it to PH85IMG, since its a stock ruu and not just a flashable Rom.
Sent from an Amaaaaaazing place :-D
Woohoo! I've succeeded in getting the aforementioned RUU installed. Should be much less of a problem from here forward.
yuseiatlas said:
First im not resbonsible for anything that can
...
Sent from my GT-P7500 using XDA Premium HD app
Click to expand...
Click to collapse
Of course you are responsible. Heaven forbid anyone should take responsibility for their own actions or anything crazy like that.
Since English may not be your first language, I'll be clear. I'm just kidding.
Silentbtdeadly said:
I don't want to put down energy rom, but it hasn't been updated since the original leak, and the instructions were never ...
other or future devices..
Click to expand...
Click to collapse
Now that I have the RUU, could use some examples of projects that are more up-to-date so that I can move forward.
jcllings said:
Now that I have the RUU, could use some examples of projects that are more up-to-date so that I can move forward.
Click to expand...
Click to collapse
Whoops, you covered this earlier. Will chase down the link and see where it goes.
jcllings said:
Now that I have the RUU, could use some examples of projects that are more up-to-date so that I can move forward.
Click to expand...
Click to collapse
If you want cutting edge(these both have features no other rom has added yet, and are very current update wise) and like the senseui, try remix's http://forum.xda-developers.com/showthread.php?t=1673609 or if you want with less sense and more of an aosp-ish feel go for his http://forum.xda-developers.com/showthread.php?t=1623184
ARHD is what is being used for the base for many roms because it is solid and bugless, energy has more features that he had included in his gingerbread rom.. I've heard good things about capromce, but I have no idea what features he has added that are or aren't included in the others..
Heheheh and its not my first language thats why you might see a lot of grammar and/or writen mistakes, just for the futur before you flash any new ROM Back-Up you current or the original ROM just in case something like this happen so you can restsore it without worrying and hope i helped
Sent from my GT-P7500 using XDA Premium HD app
Righteous! Up and running on Speed ROM 4.0. Thanks so much to everyone who collaborated. Copious mashing of the Thanks button.
CM9 looks really awesome, but the consistent problem that I'm having with the different builds being offered is that wireless card doesn't turn on. I did get it going on Countershrike, but 4G wasn't working for some oddball reason and I wanted to try out other ROMs. I'm really liking Neo's 1.6 Linaro so far, but yet again, no wi-fi. It it were just one ROM I was having a problem with that would be one thing, but this is happening consistently no matter which ROM I'm installing.
Yes, I did use the fastboot with the image from the respective ROM threads whenever I encountered the "parsing" error, so I don't think that's it. Perhaps in the case of Neo's ROM I shouldn't have updated when prompted.
What am I doing wrong?
AOKP builds require you to toggle the native hotspot after reboot to make WiFi work. Newer CM9 builds work fine out of the box. Not sure about Gray's build, but I know that my CounterShrike build, Neo's Rage build, and Snuzzo's Linaro build work fine out of the box with nothing special required.
Sent from my ADR6425LVW using Tapatalk 2
I'd your getting a parsing error then I think its not flashing the boot.IMG so then WiFi might not work. Does it work on sense? Some peoples phones don't like aosp.
Sent from my Rezound fueled by jelly beans.
shrike1978 said:
AOKP builds require you to toggle the native hotspot after reboot to make WiFi work. Newer CM9 builds work fine out of the box. Not sure about Gray's build, but I know that my CounterShrike build, Neo's Rage build, and Snuzzo's Linaro build work fine out of the box with nothing special required.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Whoops, strike that. It was actually just your ROM that was the one where wi-fi worked fine and not Grey's. Sorry about that, like I implied, I've tried out at least four of them today. I'll try your suggestion.
jon7701 said:
I'd your getting a parsing error then I think its not flashing the boot.IMG so then WiFi might not work. Does it work on sense? Some peoples phones don't like aosp.
Sent from my Rezound fueled by jelly beans.
Click to expand...
Click to collapse
Just tried an AOSP, this time Neo's Rage 1.9, still no wi-fi. Sigh......frustrating, Why doesn't this appear to be an issue for all the other Rezound users?
This is just bizarre, only Countershrike has had wi-fi operational so far out of the five ROMs I've flashed. Curious and curiouser.
All CM9 builds have working WiFi out of the box.
zhuge_liang said:
just tried an aosp, this time neo's rage 1.9, still no wi-fi. Sigh......frustrating, why doesn't this appear to be an issue for all the other rezound users?
This is just bizarre, only countershrike has had wi-fi operational so far out of the five roms i've flashed. Curious and curiouser.
Click to expand...
Click to collapse
youre doing it wrong
Make sure you're doing a clean flash (choose Wipe either right before or right after flashing) and flashing the kernel with "fastboot flash boot boot.img" (if you're S-On). I've sometimes had troubles with the PH98IMG.zip that is sometimes created to flash the kernel.
scy1192 said:
Make sure you're doing a clean flash (choose Wipe either right before or right after flashing) and flashing the kernel with "fastboot flash boot boot.img" (if you're S-On). I've sometimes had troubles with the PH98IMG.zip that is sometimes created to flash the kernel.
Click to expand...
Click to collapse
Wipe before flashing.
Perhaps I should flash boot.img from SDK instead of bootloader menu. And it looks like my command line syntax may have been slightly off.
I used "flashboot boot boot.img" The command was accepted but again, you may have just pointed out my error.
Just to be clear, I am wiping everything before flashing. I'm thing the issue is isolated to PM98IMG and the bootloader step. Is the boot.img proprietary to the ROM it's posted with?
Sent from my Rezound using xda app-developers app
Zhuge_Liang said:
Perhaps I should flash boot.img from SDK instead of bootloader menu. And it looks like my command line syntax may have been slightly off.
I used "flashboot boot boot.img" The command was accepted but again, you may have just pointed out my error.
Just to be clear, I am wiping everything before flashing. I'm thing the issue is isolated to PM98IMG and the bootloader step. Is the boot.img proprietary to the ROM it's posted with?
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
The command is:
fastboot flash boot boot.img
O M G
no...
Y O U R E D O I N G I T W R O N G
cslingerland said:
O M G
no...
Y O U R E D O I N G I T W R O N G
Click to expand...
Click to collapse
I get that I'm the new guy here and all what with my questions that may come off as "t3h n00bish" to someone like yourself, but acting in the manner that you are likely isn't representing this community very well. This sort of thing is self-taught for the most part, same as it was for you at some point and I've taken the time to research a lot of this on my own.
If you have something productive to contribute to the discussion, then by all means stay and contribute, otherwise move on.
Zhuge_Liang said:
I get that I'm the new guy here and all what with my questions that may come off as "t3h n00bish" to someone like yourself, but acting in the manner that you are likely isn't representing this community very well. This sort of thing is self-taught for the most part, same as it was for you at some point and I've taken the time to research a lot of this on my own.
If you have something productive to contribute to the discussion, then by all means stay and contribute, otherwise move on.
Click to expand...
Click to collapse
ok heres my help.
assuming adb and fastboot are in your knowledge base,
1. unlock
2. flash amon ra
3. download rom
4. flash rom
5. extract kernel from rom
6. place in fastboot directory
7. boot phone to fastboot
8. "fastboot flash boot boot.img"
9. done mofo
---------- Post added at 12:42 AM ---------- Previous post was at 12:34 AM ----------
cslingerland said:
O M G
no...
Y O U R E D O I N G I T W R O N G
Click to expand...
Click to collapse
wow... what an ass hole
cslingerland said:
ok heres my help.
assuming adb and fastboot are in your knowledge base,
1. unlock
2. flash amon ra
3. download rom
4. flash rom
5. extract kernel from rom
6. place in fastboot directory
7. boot phone to fastboot
8. "fastboot flash boot boot.img"
9. done mofo
Click to expand...
Click to collapse
I had come across adb yesterday when I had Google searched for "how to remove clockworkmod" since it crept back onto my phone (likely through a Titanium restore during one of my previous ROM install attempts) and interfered with amon-ra. I realized that forcing amon-ra through adb was the way to go. After fighting with the PH98IMG part, I stuck with SDK and flashed it that way and finally got wi-fi working in Neo's AOKP 1.6. I'm not sure about 4G yet, but that may be the next problem I have to tackle.
I hadn't understood that the correct boot.img was to be extracted from the actual ROM zip file having gotten that confused with the whole PH98IMG thing. But thanks for posting back anyway.
EDIT: Nevermind, it seems 4G is working fine. I'm streaming Netflix perfectly and last I checked 3G doesn't produce the bandwidth to support streaming a movie, at least not at an acceptable resolution. The signal indicates 3G, but the performance in this case couldn't possibly be a 3G performance. Speed Test is showing 3G speeds. I'll have to check the thread for this ROM to see if anyone else has had issues with this.
cslingerland said:
ok heres my help.
assuming adb and fastboot are in your knowledge base,
1. unlock
2. flash amon ra
3. download rom
4. flash rom
5. extract kernel from rom
6. place in fastboot directory
7. boot phone to fastboot
8. "fastboot flash boot boot.img"
9. done mofo
---------- Post added at 12:42 AM ---------- Previous post was at 12:34 AM ----------
wow... what an ass hole
Click to expand...
Click to collapse
Are you talking to yourself?
Sent from my HTC Rezound
cslingerland said:
ok heres my help.
assuming adb and fastboot are in your knowledge base,
1. unlock
2. flash amon ra
3. download rom
4. flash rom
5. extract kernel from rom
6. place in fastboot directory
7. boot phone to fastboot
8. "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Ok, I tried everything here; even tried the CleanWipe by Scotty (http://forum.xda-developers.com/showthread.php?t=1562176), going back to RUU, then steps 1-8 above. Unfortunately I still cannot get the wifi to work on Neo's TRON v1.2.
My status: I am S-Off, HBOOT 2.27, Baseband 2.22.10.0801r & 2.22.10.0803r. The Kernel Version showing under Settings:About phone = 3.0.16-FunkyBean-v2.3-gb2f996c. I've also tried just the wipe before fastbooting the boot.img several times.
The last time I tried it, I flashed the rom 3 times before I proceeded to do anything else. And I also attempted to toggle the hotspot, and still nothing. In Settings:About phone:Status both the wifi and bluetooth addresses show "Unavailable". I am at a loss here - was hoping to make Tron my daily ROM based on everyone's comments in the forum, but without wifi & bluetooth, I'm going to have to try CounterShrike as Zhuge_Liang was able to get it work 'out of the box'.
Any other comments or suggestions on making wifi work on Neo's Tron would be appreciated.
If you're s-off, no need of fastboot flashing. Unsure what's happenning here as wifi should just completely work right. Even bluetooth should work right. Try this out and see how well it works for you ....
http://www.androidfilehost.com/?fid=9390248398092763844
If you need ics gapps
http://goo.im/gapps/gapps-ics-20120429-signed.zip
Snuzzo,
Thanks for the suggestions. I tried them but to no avail. I guess I'll have to go without using wifi unfortunately. I've tried different ROMs and nothing seems to work. Maybe some hardware broke?? Everything else seems to work fine except wifi and bluetooth.
Any luck getting wifi fixed? I've been having the same problem.
A long while back I used the HTC official unlock ( cant remember what it is called ), I installed clockword recovery (5.8.1.5) and rooted but didnt mess with my rom beyond that.
Today my daughter was playing a game and the phone suddenly rebooted (saw it happen) it reboots to recovery. I tried clearing the cache and factory reset still wouldnt boot. Decided to try a ROM to see if that would fix it (did CG ROM Jelly Bean) no change. Not really sure what my next step should be.
It does say "E:unknown misc partition fs_type "ext4"" at the bottom of the clockwork recovery page.
still working on this to no avail, not really sure what to try next. I am worried the tablet may have died proper like.
Halp please!
Sent from my SPH-L900 using xda app-developers app
yehoshua said:
Halp please!
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
try flashing ruu with fastboot see http://forum.xda-developers.com/showthread.php?t=1428104
copperdawgnc said:
try flashing ruu with fastboot see http://forum.xda-developers.com/showthread.php?t=1428104
Click to expand...
Click to collapse
Sorry for the long reply, I spent a TON of time figuring out how to do all this stuff for the version of stuff I beleive I have. At any rate the problem I am consistantly encoutnering is that I cant get to hboot at all. I also cant find advice on how I might repair hboot from recovery. I do have adb access from recovery and can do adb reboot-bootloader but it just thinks for a bit and comes back to recovery. I also tried many times doing the vol-down + power button to get to hboot.
So what is the next step if you cant get to hboot?
so have you done something like
adb reboot-bootloader
fastboot flash zimage zImage
fastboot flash zimage zImage
fastboot reboot
copperdawgnc said:
so have you done something like
adb reboot-bootloader
fastboot flash zimage zImage
fastboot flash zimage zImage
fastboot reboot
Click to expand...
Click to collapse
Yes, when I do adb reboot-bootloader it just reboots into recovery again. fastboot gives the <waiting for device>. I also tried copying the rom.zip from the ruu to an sd card and then using recovery to flash to it. It starts to try then ends with "Installation Aborted".
Not sure if there is a small easy to flash to rom that I could try, even if it wouldnt have much in the way of function. Not sure if this whole thing implies my flash is partially dead or something.
Thanks
Anyone have any ideas for me? I don't really see other posts covering this problem.
Thanks
yehoshua said:
Anyone have any ideas for me? I don't really see other posts covering this problem.
Thanks
Click to expand...
Click to collapse
Moderator moved the thread (thanks), mayhap someone in here can help. Anyone have any ideas?
Only thing I can think of is grabbing a proper RUU executable, there might be a thread in the view dev area that links to some, plugging in your view and try running that. You'll loose root and all but it may bring it back to life
Sent from my ADR6410LVW using Tapatalk 2
gersto said:
Only thing I can think of is grabbing a proper RUU executable, there might be a thread in the view dev area that links to some, plugging in your view and try running that. You'll loose root and all but it may bring it back to life
Sent from my ADR6410LVW using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the idea Gersto but I cant get to fastboot so I cant use an RUU (Unless there is something I dont know). I experimented a bit trying to get the errors about the misc partition and ext4 to go away but nothing I did to that stuff seemed to persist. I do have root and can access it from adb shell.
Not sure if it is the culprit but if anyone knows how to fix the problem wit my misc partition I am all earsl.
Thanks