I just want to make sure I understand the process before I go and mess up my phone. If someone could help me out a bit, that would be awesome.
#1 - Backup
I used a tool called Simple ADB backup (http://forum.xda-developers.com/showthread.php?p=36499906) to backup my phone. I'm not sure if it created an image or what (it's a .ab file at 6GB), but I also used Moborobo to backup contacts & apps. I already have my music, pictures, contacts backed up through gmail and such, so I'm not too worried about the data, only the fact that I want to be able to revert back to a stock ROM in case I mess up.
#2 - Make sure USB debugging is enabled and drivers are installed.
#3 - Wipe / unlock the bootloader through the htcdev website. This wipes all data from my understanding.
#4 - Install CWM or TMRW (this lets me load a ROM?)
#5 - Download ROM and use TMRW to install / load.
Now I've heard various things about S-off vs S-on. IT seems some ROMs can install with or without it and apparently with s-on is safer in terms of avoiding a bricked phone. S-off allows for deeper functionality for certain apps?
Now do I need a toolkit of some kind to do any of this or is that only with certain phone? Where does the SuperSU come into play?
I'm sure this isn't complicated to a lot of you, but this is the first I've looked into rooting. Did the past couple hours researching and figured I need to talk it out before going through with anything. As for ROM, I think I'm leaning towards the Cyanogen right now. It seems like a base version of Jelly Bean but slightly tweaked. I'm mostly looking to keep it clean and simple as possible and removing the bloatware and improve performance.
Thanks in advance, I'm excited!
rumpus01 said:
I just want to make sure I understand the process before I go and mess up my phone. If someone could help me out a bit, that would be awesome.
#1 - Backup
I used a tool called Simple ADB backup (http://forum.xda-developers.com/showthread.php?p=36499906) to backup my phone. I'm not sure if it created an image or what (it's a .ab file at 6GB), but I also used Moborobo to backup contacts & apps. I already have my music, pictures, contacts backed up through gmail and such, so I'm not too worried about the data, only the fact that I want to be able to revert back to a stock ROM in case I mess up.
#2 - Make sure USB debugging is enabled and drivers are installed.
#3 - Wipe / unlock the bootloader through the htcdev website. This wipes all data from my understanding.
#4 - Install CWM or TMRW (this lets me load a ROM?)
#5 - Download ROM and use TMRW to install / load.
Now I've heard various things about S-off vs S-on. IT seems some ROMs can install with or without it and apparently with s-on is safer in terms of avoiding a bricked phone. S-off allows for deeper functionality for certain apps?
Now do I need a toolkit of some kind to do any of this or is that only with certain phone? Where does the SuperSU come into play?
I'm sure this isn't complicated to a lot of you, but this is the first I've looked into rooting. Did the past couple hours researching and figured I need to talk it out before going through with anything. As for ROM, I think I'm leaning towards the Cyanogen right now. It seems like a base version of Jelly Bean but slightly tweaked. I'm mostly looking to keep it clean and simple as possible and removing the bloatware and improve performance.
Thanks in advance, I'm excited!
Click to expand...
Click to collapse
Okay, first, what machine are you on? Linux,mac,xp,vista,7? You can't unlock on 8.1 drivers aren't compatible. But Yes you unlock via HTC dev, I have a tool to help for that if you want to try it it helps first time root you still have to take the info that it gives you and put it into HTC dev then put the code you get from the email you get into the folder but I don't know if you would want that I need someone to test it But continuing.
Unlock via HTC dev if you want to do it manually with the command first.
1. Open a cmd prompt where your fastboot tool is using shift+right click.
2. Boot into fastboot by pulling the battery, then holding volume down and power, then clicking on the first thing which is fastboot by clicking power.
3. Back to the computer type
Code:
fastboot devices
4. If your device is found your good to get your unlock data, if not you need to reinstall drivers/check your connection/or your on windows 8/8.1
5. Now to get your unlock token.
Code:
fastboot oem get_identifier_token
6. Copy and paste this into HTC dev starting at
Code:
<<<< Identifier Token Start >>>>
And ending with this line:
<<<<< Identifier Token End >>>>>
7. Submit the unlock token it will say if its valid or not and send you a email with it is.
8. When you get the email it will have a item called Unlock_code.bin place this item into the same folder in which your fastboot is in.
9. Initiate the command
Code:
fastboot flash unlocktoken Unlock_code.bin
10. It will then send the Unlock_code.bin to your phone, you will see a prompt saying "Unlock bootloader" Then volume up and click yes. It will wipe ALL of your data back it all up before you do anything...
11. When your phone finally reboots. If you would like a custom recovery boot back into fastboot again, (Pulling battery then volume down+power button and clicking on fastboot
12. Then once into fastboot, back to your computer download either
TWRP: http://techerrata.com/browse/twrp2/vigor
PhilZ: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/vigor <-------you must use this if using a ROM by snuzzo "aka Plain-andy or illusion ROM
CWM: Or go here http://forum.xda-developers.com/showthread.php?t=1914215 Download one of the zips, Extract it with your favorite extractor. You should get a .img in a folder, extract it and put it in your fastboot folder. This is only for CWM.
Take one of the .img's from above that you just downloaded and place it in the folder with your fastboot.
13.Back to your computer to push the recovery. Then while your phone is still in fastboot and connected to the computer make sure your device is still found.
Code:
fastboot devices
then if your device shows up, you are good to then flash the Recovery. Initiate this command.
Code:
fastboot flash recovery <name of recovery>.img
14. It should write the img successfully.
15. If you would like to go into recovery, you can either press "bootloader" In the fastboot option then click recovery and go into it from there. Or do
Code:
fastboot reboot
it will reboot your phone like normal. Then you can put your ROM and correlating GAPPS of choice onto your phone via USB Mass storage, along with SU. Put it on the root of your external SD card. Then you can reboot into recovery. After booting normal and transferring the ROM of choice you can then enable USB debugging and do
Code:
adb reboot recovery
16. It will reboot you to the recovery that you used. You might get a lot of errors on your phone. IGNORE THEM!!
17. Go to install and find SU from your external SD card. Install that. Then after that I would suggest STRONGLY making a backup (NANDroid) By clicking the backup button in any recovery, make sure you back it up to your external SD card.
18. Make sure that you have your ROM of choice on your SD card.
19. Wipe the hell out of everything once your ready to install your ROM.... EXCEPT SD CARD
20. Install the ROM and GAPPS in that order.
21. After a confirmed flash, wipe, cache and dalvik.
22. Boot into fastboot. (Power+Volume down and clicking fastboot)
23. Take your original <Name of ROM>.zip and extract it. Open the folder. In the folder will be a item called boot.img
24. Place this boot.img into the folder with your fastboot.
25. Again initiate the command
Code:
fastboot devices
make sure the device is found.
26. Initiate the command, this will flash the kernal aka "boot.img"
Code:
fastboot flash boot boot.img
27. Once you've confirmed that it has flashed the boot.img do
Code:
fastboot reboot
it will reboot your device. WAIT AT LEAST 20 MINUTES!!! FIRST BOOT CAN TAKE A WHILE!!!
28. Once rebooted set up
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Now talking about s-off, if you like to flash ROM's a lot I would suggest it, if not and your just staying on one ROM then just stay s-on. s-off allows you to write to every partition to the phone. s-off can be dangerous as if say you flash a ROM made for the S3, well your phone will flash it happily and well brick itself going down happily... But with s-on it will abort the flash or anything. That being said theres also the advantage of s-off being you can flash a ROM for your phone, flash and go, no computer. S-off can do some stuff inside the phone such as bootlogo's etc.. BUT its not needed for almost any app in the play store or any ROM... s-off just simply means you can write to every partition freely. No its not required. Now if you were to mess up and something goes corrupt on the phone and you need to return to stock for some reason......Well.... You almost kinda need s-off for that.... unless you do
Code:
fastboot oem lock
relock your bootloader and run a RUU..... But while s-off you can simply run a RUU (ROM upgrade utility I think ) But you can just run it.... This is how your would "return to stock" if anything messes up.... s-off can be EASILY obtained via rumrunner, use the universal 0.5.0 it will s-off your device http://rumrunner.us/downloads-2/
Unlike the old version of s-off which requires linux and a 22ga wire.... Hope this answers any questions!
I will post anything if i missed something, have to go, typed this real quick, please don't do this yet I think its right though....
edit: Just checked over it and made some changes... This should be exactly step by step... Or for what I did and what most others did. If I missed anything, someone else please post...
After more research, I am editing my original response.
The above is too many steps for me; I know it can be simpler. I'm going to go with the Everevolv ROM and just want to verify my findings on the install process.
- Make sure all Rezound drivers installed
- Install & update Android SDK
- Unlock bootloader / wipe phone data
- Install TWRP
- Put Everevolv ROM .zip on SD card (not extracted)
- Boot into TWRP & Flash ROM
Now, I have not rooted my phone and I am S-ON, so I know I need to flash in fastboot with the command: "fastboot flash boot boot.img".
Does this mean I flash with the android SDK instead of TWRP? Or at what point in the install procedure do I flash the boot.img file?
From my understanding, this ROM does not require root access. Is this correct?
rumpus01 said:
After more research, I am editing my original response.
The above is too many steps for me; I know it can be simpler. I'm going to go with the Everevolv ROM and just want to verify my findings on the install process.
- Make sure all Rezound drivers installed
- Install & update Android SDK
- Unlock bootloader / wipe phone data
- Install TWRP
- Put Everevolv ROM .zip on SD card (not extracted)
- Boot into TWRP & Flash ROM
Now, I have not rooted my phone and I am S-ON, so I know I need to flash in fastboot with the command: "fastboot flash boot boot.img".
Does this mean I flash with the android SDK instead of TWRP? Or at what point in the install procedure do I flash the boot.img file?
From my understanding, this ROM does not require root access. Is this correct?
Click to expand...
Click to collapse
1. Unlock via HTC dev.
2. Make sure drivers are installed.
3. Push recovery to phone.
4. Back up stock to SD card.
5. Wipe everything including system.
6. Flash ROM and GAPPS.
7. Flash boot.img in fastboot using
Code:
fastboot flash boot boot.img
8. Reboot phone.
If you have any questions with that. I will explain each step more in depth. But steps 1-11 were unlocking help.
Step 12-19 is pushing the recovery, making a back up, rebooting to it.
Step 20-end actually getting the device to boot after flashing ROM. If I need to explain again. I will. In a ever more simplified version. Plus the reason that there were so many steps is because the longest step literally takes like 2 minutes max. The rest is almost like 30 seconds besides actually flashing the ROM and GAPPS. I tried to do as much detail as POSSIBLE!!! Please consider rereading it, if you don't understand a step, ask and I will gladly explain. But it is a COMPLETE STEP-BY-STEP GUIDE. Hope you get your phone rooted, but if you didn't know what fastboot was....you might need some more reading..... I can write up a complete guide of what EVERYTHING means, what EVERYTHING does. But fastboot is just where you flash recovery/boot.img/etc.....any questions, please ask, I will explain or someone can beat me to it
Awesome man, thanks so much! I'll give it another read... I have a few hours set aside later tonight to investigate the whole process once again, so I'll certainly have more questions.
Once again seriously, thanks for the help!
rumpus01 said:
Awesome man, thanks so much! I'll give it another read... I have a few hours set aside later tonight to investigate the whole process once again, so I'll certainly have more questions.
Once again seriously, thanks for the help!
Click to expand...
Click to collapse
sweet. Just PM me or post here :good:
pball52998 said:
sweet. Just PM me or post here :good:
Click to expand...
Click to collapse
Alright man so after re-reading it, it's starting to make a whole lot more sense now. Initially, I was wondering why the hell there were so many steps in your first post. Now I realize you were just going step by step through the HTC unlock process as well, which I'm guessing HTC walks you through more or less but you clarified it in more detail.
Now in a broader step by step list, you said this:
1. Unlock via HTC dev.
2. Make sure drivers are installed.
3. Push recovery to phone.
4. Back up stock to SD card.
5. Wipe everything including system.
6. Flash ROM and GAPPS.
7. Flash boot.img in fastboot using
Click to expand...
Click to collapse
Now my understanding is that unlocking the bootloader wipes all data, but #4 is a backing up procedure... Is this just creating a backup of the stock ROM on my phone at the moment, without any of my apps or personal data? Then #5 would actually be wiping the stock ROM?
These few steps confuse me a little:
20. Install the ROM and GAPPS in that order.
21. After a confirmed flash, wipe, cache and dalvik.
22. Boot into fastboot. (Power+Volume down and clicking fastboot)
Click to expand...
Click to collapse
Are GAPPS included with the ROM download?
#21 - Are you telling me to "cache and dalvik" or is that part of the flash process that I don't have to do in separate steps? For example, are you saying
a) After a confirmed flash, you need to wipe, cache, and dalvik.
or
b) After a confirmed flash, wipe, cache, and dalvik, you need to boot into fastboot.
WTH is dalvik?
Now I think those are my only questions regarding the process for the moment; I'm going to check out some YouTube videos of some of these processes individually to get a better understanding. It sounds to me like most of this makes sense once you actually start going through the process and seeing it instead of reading about it, but I wanted to do as much homework as possible first.
Think I'll go ahead and give this a try tonight... It sounds like with S-on, I can only screw it up so much but we'll see. I did all my chores tonight so I can focus on this tomorrow all night if I wonk it out and just be without my phone during the day.
Oh one last question - Will I be able to get updates / update without flashing again?
Thanks again man!!!
Okay. So my "full" step by step makes more sense now? Good now do you see why I had so many steps? It was each individual part. Step by step. With clear detail or at least I tried
So moving onto the "unlocking wiping data" yes it will wipe every piece of data. But leaves stock. What I would suggest is putting su on your SD card and that being the first thing you flash before wiping or backing up..I've heard you can't back up bare bone stock. It must have root, or so I've heard... So put su on your sd card and flash it first (aka go to install and find it swipe to flash. Su should now flash. You now have root or should). Not very hard, just flashing it won't do any damage.
But backing up. When you back up it pulls every piece of info you have and puts it into a folder on your SD card. Like I have no stock... I accidentally erased it... But besides that. Do you see in my signature how I have 3 roms on my rezound. PAC, CM, And sense 5. See every one of those has been backed up. If I were to restore it, it would automatically restore to the point where I made the backup.
So now let's say. You have your backup of stock. It's on your EXTERNAL SD CARD. It should be about 1-3 gb backup. So now we have that backup made in twrp. Wipee we now have stock saved just incase something happens
So then we go in to the wipe button. Youre going to
factory reset 3 times
Wipe data, cache, dalvik cache, boot and system 3 times each. Don't ask why 3 I really don't know. But one isn't good enough...it's proven... So this leaves you with no OS oooo noooo. But the thing is you have your backup on your external hard SD card. And also your ROM/gapps on there. (gapps is google apps) but you must download the two separately. Both in a .zip format. Not a folder... Can't flash a folder... But there should be a need gapps button on the evervolv page? Click it and it should take you to a download for gapps. Remember all this is on the root of your external SD. So now we have 3 things on your SD card and no OS. O Lordy.... Time to hit up the install button!!! ;D now were going to choose the evervolv ROM. Bam, click add more zips, find gapps, click it. Bam, now you have two zips queed to flash. Just swipe to flash make sure you choose the rom before the gapps. so time passes (less than 5 minutes) and rom and gapps are now flashed. When it gets done flashing you should have some options. One being wipe cache/dalvik. That is where your question of the #21 is... Sooo.... Dalvik is pretty much like our java almost... It runs our apps...soon android will be changing to ART (android run time).
Blah blah blah, doesn't matter!! Lol xD so then after wiping your cache and dalvik after flashing your rom, return to the main menu of TWRP you should see a button on twrp's main menu, at the very bottom right, "reboot" when you click on that you should get 4 options, reboot system, bootloader, recovery, power off. We want to choose bootloader. This will bring us to fastboot (it will say fastboot usb in bug red letters if your in fastboot) where you flash the boot.img that you extracted earlier from the zip and placed it in the same folder as your adb/fastboot you remember? We need to open a cmd prompt and flash this boot.img "aka kernel" so were going to type in that cmd prompt: fastboot flash boot boot.img
This will flash the boot.img to your phone once confirmed, (only about 6 seconds to write it) were going to reboot the phone and hope for the best.. Do: fastboot reboot
It'll reboot your phone, remember first boot can take a while....
Also what do you mean by your last question??????
Sent from my crappy Jailbroken apple iPad.....
Freedoms just another word for nothing left to do... Nothin' ain't worth nothing but it's free.....
Hey man! I did not read your full post just now because I'm tired of thinking about this stuff, but I went through your step by step instructions and everything seemed to work out. I'm currently waiting for on my first boot; it's at the Evervol screen with the heartbeat animation going on. Everything made perfect sense once following your guide to the actual process; it just seems risky since there's no good way to practice unless you have a spare phone or something.
The only thing that tripped me up was that my SD card had all the data from my previous ROM even after everything was wiped. So I formatted it in Windows prior to copying the SU, ROM, and GAPPS zips on there.
Oh and I noticed after wiping and booting into the "clean" stock ROM, I had no service... Obviously, I didn't try to fiddle around with that since I was about to install a new ROM, but I can see that being a problem if this ROM ever loads (been about 22 mins).
I did find this info on a different thread:
1. Go to the dialer and press *#*#4636#*#*
2. Click on "Phone Information"
3. You should notice almost towards the bottom radio settings, Make sure the radio is on and change the settings from WCDMA to GSM (auto)
4. Exit out of the screen by pressing the back button
5. Reset the phone and you will have service.
Click to expand...
Click to collapse
I'll give that shot if it's no bueno!
Thanks again man, I'll post back tonight if I don't fall asleep before it's done loading, lol. Either way I'll post back tomorrow. Seriously thank you again, can't believe you typed all that out for me, even when the first 11 steps were step by step from HTC too. :good: True internet assistance!
Did you flash the boot.img in fastboot?? That can cause you to stay on the boot screen forever. I've had that problem @rumpus01 and glad it all made sense!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Did you flash the boot.img in fastboot?? That can cause you to stay on the boot screen forever. I've had that problem @rumpus01 and glad it all made sense!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
I did indeed as it was listed in your steps, of course!
It's been about an hour now, so I'm guessing something went askew and it is not going to power up. What course of action should I take from here? I'm guessing go back to stock ROM via recovery (the backup I made), and then do the whole process over again, aside from unlocking and what not. I definitely installed SU before making a backup, so hopefully that works out.
Thanks again! It's never simple...
Okay one question. How much did you wipe before you clean installed the ROM? Did you wipe everything but External SD 3 times? Including system?
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Okay one question. How much did you wipe before you clean installed the ROM? Did you wipe everything but External SD 3 times? Including system?
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
No, I did not... I did everything before your post about that, so I'm guessing that's the problem. I also only wiped cache, dalvik cahce, system, and internal storage. There's an option for android secure and factory reset under the wipe menu as well, but I wasn't sure about those...
I tried pulling battery and rebooting, I'm guessing it's dunzo. I am now booted into recovery mode and going to recover to the backup I made, and try the whole thing again after reading your post about wiping multiple times.
EDIT: To clarify, I am wiping everything 3 times before restoring. Then I'm going to reboot normally to see if the restore worked, and then go through the process again except wiping multiple times before installing the ROM this time.
Crap....sorry I didn't mention that to begin with..... And don't do the recover yet. Try wiping everything.... 3x then try booting. After the boot.img flash in fastboot... Sorry I forgot that man.... First off though, if everolv doesn't work. You can always try another ROM. Go s-off (takes at most like 30 minutes) then flash everolv.... But try wiping everything at least 3 times except the SD card. The reason for the two wipes is because one clears main. Then it goes into emmc and clears I think.. Sorry I completely forgot about it and it went over my head....
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Crap....sorry I didn't mention that to begin with..... And don't do the recover yet. Try wiping everything.... 3x then try booting. After the boot.img flash in fastboot... Sorry I forgot that man.... First off though, if everolv doesn't work. You can always try another ROM. Go s-off (takes at most like 30 minutes) then flash everolv.... But try wiping everything at least 3 times except the SD card. The reason for the two wipes is because one clears main. Then it goes into emmc and clears I think.. Sorry I completely forgot about it and it went over my head....
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
Crap I already wiped everything and tried a restore, which doesn't appear to be working haha. And don't worry man, I can't believe you gave that many instructions to begin with. It's a lot of steps! Nothing happens when I boot after doing my recover install. My computer gives the sound of a USB device but says nothing, and my phone doesn't even light up in any way. I'm going to go wipe everything and try rebooting it normally again.
Well just wipe, wipe, wipe, then install the ROM and gapps. Flash boot.img and you should boot fine.... Btw if you want stock, there's a ROM for that xD
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Well just wipe, wipe, wipe, then install the ROM and gapps. Flash boot.img and you should boot fine.... Btw if you want stock, there's a ROM for that xD
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
So after wiping everything, I go to "install" and all the zip files for the GAPPS and SU and ROM are on my Internal storage device... didn't I just clear that 3 times???
I cleared everything including internal storage and selected reboot, and recovery told me SU was not installed and asked if I wanted to. I chose yes and rebooted. Then wiped cache/dalvik cahce 3 times each, and now installing the ROM and GAPPS again... I think I wiped my internal SD card & system in addition to cache and dalvik cache after installing SU but before installing the ROM and GAPPS initially... I wonder if this was the main source of the problem.
Okay. Everything's wiped. There is no os installed. So that being said. You have your ROM and gapps on your SD card. Correct? Or external SD card. Either will work dear sir. Install those and then flash the boot
Img and see your result. That should be the easiest way to boot.
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
pball52998 said:
Okay. Everything's wiped. There is no os installed. So that being said. You have your ROM and gapps on your SD card. Correct? Or external SD card. Either will work dear sir. Install those and then flash the boot
Img and see your result. That should be the easiest way to boot.
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Click to expand...
Click to collapse
WELL WELL, IT IS WORKING. IT blew through that Evervolv boot screen in like 2 minutes this time.
I see that my service is not working, and my computer said MTP USB Device drivers failed to install. I now see that has something to do with transferring media files to PC.
Well, whatever. I am cool with this for now, at least it is installed. Very tired, let's all go to sleep! Thanks again for all the help man, feel like I'm paying someone for remote support lol.
Lol gg man. We got it. Cheers!!! :good:
Sent from my Rezound running PAC-Man with SENSE!! 4.4.2 S-OFF
Related
Ok, I've already searched the forums, both in the Evo3D section and outside, I've also have within the last week tried many different sense roms, all of which had the exact same problem: my camera does NOT work.
The closest thing to working was mike1986's Android Revolution HD (so far). The camera app boots into the window that ask to choose between Done or run the Demo Video. The Demo Video sends ye off to the internet browser. Hitting Done goes straight to my problem.
The application opens into a black screen. Sometimes the backlight is on (noticed this is a 'feature' of the newer roms that has came out/updated within the last month). That's it. After hitting home to exit the application, I have noticed I get either dimmer horizontal strips of the screen or the screen has a ghost of the lighter portions of the screen image that slowly moves to the left. After a few seconds of this strangeness, the screen reverts back to normal. A few times I got the impression that the screen's dual layers having synchronization problems.
I'm about ready to give up and go back to the stock rom, maybe I'll even try the 'cleaned' versions before trying the rooted shooter stockers. If all else fails, I'll even try to use the full OEM installer and return the phone back to stock, if this is the only option left to get a working camera. I'd prefer to use a custom rom that allows undervolting/overclocking and has the fat trimmed off, but if I have to, I'll go back to stock rooted. ...now that I think of it, I started to have problems with the camera right after I applied the HTCDev Root method. And, yes I DID follow the instructions to the letter.
This is quite frustrating as I've have as yet to find a rom that has a working camera! I've already tried the following roms:
Shooter-Rewind-3D-RLS2.1+RLS3
WTSB_Evo3d_1.91
CleanROM_2.7
CleanROM_DE_1.2
Chogardjr3D-2.3.4-Stock
Chogardjr3D-Blue-v1.3
STEAL25_inbREDedROM_2.1clock
viperROM_RC1.3
viperROM_RC2_Rebuild_Test28
Android_Revolution_HD-Evo3D_CDMA_1.1.1 (current)
I haven't tried but already downloaded:
Gerbil-6-shooter_v.2.2.4
freEVO+3D+2.1
WTSB Hydro e3d 2.3 (want to try this one, but keep having problems downloading, the server keeps on downloading a 35kb index.html instead of the rom itself)
If the above roms fails, then I going to try reloading the rooted stock rom
shooter_2.08.651.2_cleaned_v0.4.2
Else one of these two...
Shooter_2.08.651.2_deodexed_rooted
Shooter_2.08.651.2_odexed_rooted
If all these fails, sigh, I gonna start over again with the full oem install...
PG85IMG_2.08.651.2.zip
And see if the camera still broken. If so, then gonna apply all OTA updates FIRST before applying the HTCDev root method again. This is the only thing I did not do before. If this doesn't work, I dunno what else to do then.
Any suggestions, rom-wise or camera-wise? I've been reading around and found a thread in the Amaze section that suggested that the camera problem might be kernel-level. Think this may also apply to the e3d?
I've been doing sleepless nights for the past 5 days already trying roms after roms and apk after apks. I'm about reaching the end of my thread (and patience) and figured it's time to ask the pros here on xda.
Thanks in advance...
-Lance (Lanaka)
Reserved for Fixed Post.
I forgot to upload my hardware/software specs. I'm out of time as I have to go to work, so I'll edit it onto this post during a slow period at work.
K here's my hardware/software specs:
---Hardware:
------Hardware Version: .. 0002
------Processor: ............ 1.2 GHz Qualcomm MSM8660 Dual-Core
------Memory: ............... 1GB
------Display: ................ 4.3 inch QHD resolution
------Main Camera: ........ 5Mpx*2
------Front Camera: ....... 1.3Mpx
---Software:
------Android Version: ..... 2.3.4
------HTC Sense version: 3.0
------Software number: .. Android Revolution HD 1.1.1 by mike1986
------Kernel version: ...... 2.6.35.14RCMIX-ACS-EVO3D-CR-V9-g98e7362-dirty
------------------------- [email protected] #6
------------------------- SMP PREEMPT Mon Oct 24 13:13:49 CDT 2011
------Baseband version: . 0.97.10.0808
------Build number: ........ 2.08.651.2 CL130920 release-keys
------Browser version: .... WebKit/533.1
------PRI Version: .......... 1.24_003
------PRL Version: .......... 10602
Bootloader:
------SHOOTER XC SHIP S-0N RL
------HBOOT-1.50.0000
------eMMC-boot
------Aug 7 2011,10:21:40
---Recovery:
------Team Win Recovery Project (twrp) v1.0.3
------Based on Android System Recovery <2e>
Any other information you need, lemme know and where/how get it.
Mahalo Much
-Lan
Infected eternity ROM works...
Sent from my 3vo
http://infectedrom.com/showthread.php/561-ROM-Eternity-2.3.4?p=10369
Sent from my 3vo
nearly ALL the ROMs you posted, nay, all of them, work - if they didn't there would be a hellstorm in those threads. My guess is it has to do with how you're flashing the ROM. Since you have hboot 1.5, customized kernels (which contain camera stuffs) do not fully apply in a normal flash. You need to first fastboot usb INTO recovery and THEN flash the ROM. That should work. Also, update TWRP to 1.1.1. Of course you'll need to do a wipe as well. Hope this works for you.
You might also want to try one of the many superwipes.
User error. Camera works on roms. Maybe ur phone is broken
Sent from my PG86100 using XDA App
I'd go with what il Duce said. You have to flash the kernel seperately. If you do decide to go back to stock you can always add su and also remove what you don't want.
Sent from my PG86100 using XDA App
fsu311 said:
Infected eternity ROM works...
Click to expand...
Click to collapse
Ok, I'll give it a try next after the ones I've already downloaded. I'm a methodical type of guy (don't like leaving thing left undone).
il Duce said:
nearly ALL the ROMs you posted, nay, all of them, work - if they didn't there would be a hellstorm in those threads. My guess is it has to do with how you're flashing the ROM. Since you have hboot 1.5, customized kernels (which contain camera stuffs) do not fully apply in a normal flash. You need to first fastboot usb INTO recovery and THEN flash the ROM. That should work. Also, update TWRP to 1.1.1. Of course you'll need to do a wipe as well. Hope this works for you.
Click to expand...
Click to collapse
That's what I'm figuring. I start reading the original set of posts, then randomly check out a few posts in the middle, and then read the last 10%. The roms i've picked mostly had either minor issues caused by misflashing or other user errors. A few actually said had an issue or two but nothing that'd stop me from giving the rom a try.
Yup, that's the MO I've been using as instructed in the following thread:
http://forum.xda-developers.com/showthread.php?t=1239821
I'll go thru the step-by-step process I used and you can nitpick where I went wrong,
I've placed a copy of adb.exe, AdbWinApi.dll, fastboot.exe and TWRP's recovery.img into folder c:\adb\
A little tip here, as I play with windoze XP a lot, a trick I used to eliminate the need to cd so much with cmd.exe. I did this after the 3rd ROM!
I place a shortcut link to cmd.exe into this same folder with the above files and exes. Next I open the Properties window for this shortcut, I made the following changes:
Start In: c:\adb
Comment: Starts cmd.exe in adb folder.
What happen is that cmd will open its window with the c-prompt already IN the same directory as my android files. Also, when i mouse-over the shortcut icon, it will popup a message reminding me that this link starts cmd.exe in adb folder.
Then I do the following:
I connect the phone to the laptop using the usb cable, set the phone to disk drive mode. Once Windows recognizes the volume and mounts it, I type the following:
c:\adb>adb reboot bootloader
After the e3d reboots into hboot, I then type the following:
c:\adb>fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 1.250s]
booting... OKAY [ 0.000s]
finished. total time: 1.250s
Once TWRP loads, I then switch to the phone (WITHOUT disconnecting the phone from the laptop). Here on, I use the keys on the phone to navigate to the necessary functions. The proceedure I used mirrors what Steel25 suggested in the following thread:
http://forum.xda-developers.com/showthread.php?t=1269610
I initially thought it was an overkill, but figured probably wouldnt hurt to be safe than sorry.
If the installed rom is something I liked, I nand it first...
I then enter the Wipe Menu proceed to hitting each of the following:
Wipe Cache
Wipe Dalvik Cache
Wipe Everything (Data Factory Reset)
Wipe Battery Stats
Then I go to Advanced/Format Menu and hit each of the following:
Format SYSTEM (/system)
Format DATA (/data)
Format CACHE (/cache)
Format SD-EXT (/sd-ext)
Then I go back to top menu and enter Install Zip Menu, and first I hit:
Wipe Cache and Dalvik Cache
Then I enable:
Reboot After Successful Flash
THEN I:
Choose Zip To Flash
(Navigate to where the rom or app zip is located and select it.) Here I take a break and let TWRP does it thingy and check back on the phone in 5 minutes or so.
After recovery reboots the phone back into system, I let the phone sit on the lockscreen for 10 minutes to let the rom complete it's init process. Then I skip thru the entire initial setup prompts (altho I enter NO for Tell HTC). I reboot phone back into system, let it sit for another 5 minutes on the lockscreen before I hit the Android Market app to trigger the process of linking the phone to my google account. I then let my account sync. Once my new email icon pops up on the notification bar, I check out the camera. By the time I've hit the 3rd rom, I've had read about the camera problem possibly being a kernel level issue, I've since then added this step....
Menu/Settings/About Phone/Software information/More
Here I took note on whether the Kernel version info has changed as well. (And for the most part, yes, the kernel information DOES change with each rom).
K, now ye can start thrashing me...
-Lan
Drewmungus said:
You might also want to try one of the many superwipes.
Click to expand...
Click to collapse
I'll try that, altho I've never used it before. Even when I had my e4g, I never heard of this one until I started my current research on the e3d. Any particular one you'd (or anyone else'd) recommend?
Sigh, lotta work rooting and flashing the 1.50 e3d, compared to the good ol' e4g! >8p HTC!
Mahalo Much!
-Lan
cajones42 said:
Maybe ur phone is broken
Click to expand...
Click to collapse
Gods! I certainly HOPE NOT! It'd be a real b!atch if this proves to be the case.
Seriously, tho. I'm thinking it'd probably not be the case as I had the phone and was playing with it stock and unrooted for nearly a week and during the whole time, the phone's camera worked with nary a problem. That's why as a check value, I'm going to restore the phone back to stock unrooted state AFTER I try the last 4 roms I still have en-queued. This doesn't include the cleaned/rooted stocker, the full/rooted stocker nor the full OEM stocker.
-Lan
unCoRrUpTeD said:
I'd go with what il Duce said. You have to flash the kernel seperately. If you do decide to go back to stock you can always add su and also remove what you don't want.
Click to expand...
Click to collapse
Ok, I'll try that next. Altho, I gonna have to read up on how to prepare the kernel for flashing separately. Am I correct in guessing that I probably could get away with making a copy of the zip file and deleting everything in it except for boot.img, then adb boot into recovery and set the flag for check sign off before flashing the custom zip I just made? If that's not correct, mind pointing me to the apropos thread? (...or tell me what I need to do for separate flashing?)
If all else doesn't work, that's what I intend with the stocker roms. SU, TI, RE. Then time for me to research on where what and how to root out all the bloat meself. I'll worry about that later cuz I no need do that IF i can get a pre-made rom and kernel to take root in me e3d!
Mahalo Much!
-Lan
You DON'T have to flash the kernel seperatly using the boot.img method with HBoot 1.50. As long as you access recovery from fastboot you can flash everything normally & the kernel will stick. Just sayin'
SketchyStunts said:
You DON'T have to flash the kernel seperatly using the boot.img method with HBoot 1.50. As long as you access recovery from fastboot you can flash everything normally & the kernel will stick. Just sayin'
Click to expand...
Click to collapse
except he's already doing that and running into problems...
@OP - man you are wordy lol. Just a simple FYI, when you're phone is running and you hook up to usb with the intention of running adb, DO NOT turn on disk drive, leave it as charge only. Also, the way to flash the kernel as a stand alone is pull the "boot.img" from the ROM zip, put in your path, and then "fastboot flash boot boot.img". Also, there's an app made by dev "joeykrim" called "flash image gui" that allows you to flash kernels (boot.img) from your OS and is known to work with hboot 1.5.
il Duce said:
except he's already doing that and running into problems...
@OP - man you are wordy lol. Just a simple FYI, when you're phone is running and you hook up to usb with the intention of running adb, DO NOT turn on disk drive, leave it as charge only. Also, the way to flash the kernel as a stand alone is pull the "boot.img" from the ROM zip, put in your path, and then "fastboot flash boot boot.img". Also, there's an app made by dev "joeykrim" called "flash image gui" that allows you to flash kernels (boot.img) from your OS and is known to work with hboot 1.5.
Click to expand...
Click to collapse
Ah, didn't know that, mebbe that's why I'm having problems. I'll try reinstall one of the earlier ROM and see if there's any difference. If that doesn't fly, I'll try the kernel separately. I went with hard drive mode cuz I got actual confirmation the device was loaded. Charge only, didn't get any indication that the pc seen the e3d, sigh, noticed the sense and adb interface is rather ...crude.
Heh, wordy, that's what you get when you have an English major for a mother and an English/Japanese Translation Specialist (aka Cultural Attache in the US Army) for a grandfather...
I'll give joeykrim's flash_gui a try too. Just downloaded it. Cross fingers for luck. (roll eyes at 1.50)
Thanks dude, if I could, I'd hit yer thanks button again for good measure.
EDIT: clicked the button again...
Update: Back to work on problem...
Been a while guys. Unfortunately, work becons (or more accurately, intruded). Had to deal with a bunch of sht from my job. Things gone to the dumps there. Well, enuff of that.
In meantime, with my phone being activated and in use, I tried to tether (teeether, hehe) my e4g to my e3d and noticed I'm also having wifi issues. What rang a bell is when I noticed my wifi tether issues disappeared after I turned off 3G. It's like, heeeeey, didn't I read something like this in xda??? After doing some researching (on xda, of course ) I've learned that this is also a kernel issue, most often because the new kernel was not properly flashed in conjunction to having the correct matched kernel modules (wifi, CAMERA, 3g/4g, etc.) installed as well. On reading these, I went 'hmmm...' Looks like all of these issues others and I that have been experiencing are all kernel/module misflashes (no thanks to hboot 1.50). Where I think I hit pay dirt is when I found a xda thread that actually explains in depth Flash Image GUI, which was also mentioned earlier in THIS thread (thanks, il Duce).
So, I have downloaded the apk, installed it. Downloaded a new ROM (Olympus Trinity XE Version IV) STRAIGHT to phone...
Oh, just remembered. I've noticed another possible cause of problems. I've originally downloaded the various files from xda and then either push it to phone or more often just enable hardrive mode and drag/dropped it into the phones sdcard directly. Normally, I check the md5 hash on download, but yesterday, I ALSO checked the md5 hash again after moving it to the phone. Meaning, I downloaded ROM to pc, then checked md5 hash, all good. Copied ROM to phone and then checked md5 hash again. NOT good. Somehow, it changed during the copy process. What prompted me to check was I also downloaded Flash Image GUI to pc and copied it to phone and then had phone try install it. It failed to "parse" file correctly, which tells me that the file may have been corrupted. I downloaded Flash Image directly to phone and tried again, and success! Suspicious now, I checked the md5 hash of all three copies of the apk. The laptop downloaded and the phone downloaded copies matched the source's md5, while the COPIED version did NOT match! Whaaa Daaaa FFF(bleep!)!!! I then checked the two copies of the ROM (pc downloaded and phone copied) and they DON'T match!
Sigh. I'm in a area that has poor 3G connection, while ironically, my laptop's 4G was good.
So, I bit the bullet and endured the nearly hour long download of the ROM directly to phone and double checked the hash (which matched the pc downloaded copy, the source didn't provide a hash). THEN I used the Flash Image GUI app to pull the kernel and modules and pop it into phone. Immediately rebooted phone into recovery. Well, tried. Wished Flash Image GUI gave the option to reboot directly into recovery or bootloader, like those 4-/5-/6-1 Reboot options offered in the various ROMs. Because it just simple did a reboot back into System.
I didn't want to take chance with problems with mismatched ROM/kernels (I was on Android Revolution 1.1.1 at the time), so I quickly turned to adb on my laptop and had it reboot phone into recovery.
Once in recovery, I immediately started doing my usual ROM change process. Wiped using every wipe option (except for sdcard) in TWRP (oh btw, I also updated it to 1.1.1 earlier) in both the standard wipe and advanced wipe menus. Once I did so, I then thought, hey where did Flash Image GUI dump the kernels into? Couldn't remember whether it was DATA or SYSTEM. But decided that with Flash Image GUI it's ain't no hassle to reflash the kernel again after the ROM is installed. Besides, read somewhere that some issues was resolved after reflashing the kernel again after the ROM, so wouldn't hurt to try anyway.
Will let ye know how it goes, TWRP is installing Trinity XE as I type this. Gonna continue the SOP by letting it sit for 7-10 minutes. Skip thru init setup. Reboot. Let sit for another 7-10 minutes. Relink my google account. Let first Sync finish. (Basically let it sit again for another 7 minutes). Reboot. Hit Market and download Flash Image GUI, and pay for it, it's well worth IT!!! Flash the ROM's kernel/modules again. Reboot. And hopefully it should be a-ok!
(cross fingers ...on both hands)!
-Lance
PS: Assuming it's fixed, I'm gonna edit the second post and reflag this thread as resolved. Will put what I did to get it fixed, including all necessary links and credits as expected. I know it's premature, but THANKS, I wouldn't have gotten even this far without you guys (and gals) on XDA!
PPS: Also chris.goodman's AnthraX Kernel thread was also quite informative. Mebbe I'll try a ROM that features AnthraX. Somehow, the thought of being over-clocked to ~1.52G sounds appealing!
I have finally got my phone unlocked and rooted. Now I am trying to install the quicksense ROM. I know I am doing something wrong, because all I get is the white HTC screen at start up, and thats as far as it goes. So, here is what I did, and maybe someone can help me out.
I downloaded amazing quicksense and dragged it into my sd card
I booted into recovery
I did a backup
I wiped the cashe
I went to install from sd card and chose the zipped quicksense file
I then got install from sd card complete
I then went back and rebooted phone
From here the phone freezes on the white HTC screen and does not fully boot.
I had to go back into recovery and do a restore to get my phone working again.
What am I doing wrong. Please help.
Seem like you did succeed at everything except the cleaning parts
Please try again by going into recovery and
1. wipe data/factory reset
2. Wipe cache partition
3. Go to Advance then wipe dalvik cache - after that, choose go back
4. Install rom from sdcard
5. Reboot
I will try and do what you have instructed. However I wanted to ask one question before I do this. In your first step to "wipe data/factory reset", will this reset my phone back to factory, essentially wiping all my data and everything I have on it? I know unlocking the bootloader did that, but it would suck if I had to do this every time I installed a ROM. Just want to make sure what I am up against. Thanks
ms2knights said:
I will try and do what you have instructed. However I wanted to ask one question before I do this. In your first step to "wipe data/factory reset", will this reset my phone back to factory, essentially wiping all my data and everything I have on it? I know unlocking the bootloader did that, but it would suck if I had to do this every time I installed a ROM. Just want to make sure what I am up against. Thanks
Click to expand...
Click to collapse
Hi
I am by no mean a dev so my advices is more like ... well, advice - not instructions my friends
Wipe data/factory reset mean wiping every personal datas that you had on the device and yes, this will reset your phone back to the present rom that you had on the device - in your case is the stock/factory/carriers rom.
Every time you install a new rom you should - and every dev will suggested this - wipe clean your data and whatever info that may still left on the device from previous rom - you may not need to do this when you update to the new version from the same rom. Sometimes the new version of the same rom featured too many changes then the dev will instructed user to wipe all the data. That's why we user should always read the first, second and third post to make sure we keep ourself up-to-date when flashing rom.
Personal data means your google account, emails, contact list, SMS, wifi password, bluetooth pairing and apps setting ... However, we can backup and restore most of these info using diferrent apps. Here are some app that I found helpful in term of backup:
* Gmail account for contacts list
* SMS backup for SMS and call log
* Titanium Backup for apps and it's data: This app is very useful, for example if you use it to backup your email app it will included your setup and password ect ... so after install new rom and restore a particular app, you have an option to restore the app plus it's data or data/app only
Read this thread for some useful tips on how to using Titanium Backup
http://forum.xda-developers.com/showthread.php?t=1324291
Googd luck and welcome to the Amaze
I really do appreciate your advice. I will go ahead and backup everything, and then attempt the ROM install again. Hopefully it will work this time. Again thanks.
Not a problem mate
Since you already backup your rom and QuikSense is a Sense rom anyway, it doesn't hurt to try restoring data from the backup. You can do this (after finish flashing the new rom) by go back into Recovery/Backup and restore/Advance restore/choose the backup file (in case you have more than 1 backup)/then chose restore data
I did this when switching from QuikSense rom to Senseless Rom and it work flawlessly
Worst case scenario is you will have to restore again. This will save a lot of steps.
ms2knights said:
I have finally got my phone unlocked and rooted. Now I am trying to install the quicksense ROM. I know I am doing something wrong, because all I get is the white HTC screen at start up, and thats as far as it goes. So, here is what I did, and maybe someone can help me out.
I downloaded amazing quicksense and dragged it into my sd card
I booted into recovery
I did a backup
I wiped the cashe
I went to install from sd card and chose the zipped quicksense file
I then got install from sd card complete
I then went back and rebooted phone
From here the phone freezes on the white HTC screen and does not fully boot.
I had to go back into recovery and do a restore to get my phone working again.
What am I doing wrong. Please help.
Click to expand...
Click to collapse
How long do you wait?
The first boot may take several minutes.
Do you have adb installed on your computer? If so then from the command prompt (or terminal if your running Ubuntu) type "adb shell logcat" and if it seems like it's repeating itself over and over again then your caught in a loop and would probably just need to clear the data and caches. Your problem should clear right up.
Binary100100 said:
How long do you wait?
The first boot may take several minutes.
Do you have adb installed on your computer? If so then from the command prompt (or terminal if your running Ubuntu) type "adb shell logcat" and if it seems like it's repeating itself over and over again then your caught in a loop and would probably just need to clear the data and caches. Your problem should clear right up.
Click to expand...
Click to collapse
To be honest with you, I did wait for maybe 5 min or less. I guess I thought it would boot normally. I will try again and give it some time.
Being very new to this, I am trying to learn all of this. How do I know if I have adb installed on my computer? Thanks
ms2knights said:
To be honest with you, I did wait for maybe 5 min or less. I guess I thought it would boot normally. I will try again and give it some time.
Being very new to this, I am trying to learn all of this. How do I know if I have adb installed on my computer? Thanks
Click to expand...
Click to collapse
Follow the instructions on this thread here:
http://forum.xda-developers.com/showthread.php?t=928370
Easiest way to set up ADB.
Hope this helps.
Well, I finally got it to work. My probem was that my sd card was not FAT32 but FAT. I think this was the problem I had with trying to flash clockworkmod. I did everything except the wipedata/factory rest, to see if it would work. And sure enough, I am now running Amazing Quicksense 1.5.1. Thanks for every ones help.
I can't find clear cut instructions anywhere but I am sure there is a post on it already... I looked through the CM10 thread in original development but didn't see anything. I am totally stock on 1.22.651.3.
Well, you root using regawmod, you flash the ROM, and then you fastboot flash the kernel
Instructions for each of those are strewn about the forums
My write-up for Installing kernels with H-boot 1.15
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-wip.html
Rooter:
http://forum.xda-developers.com/showthread.php?t=1690919
Sent from my EVO using Tapatalk 2
Skullmonkey said:
I can't find clear cut instructions anywhere but I am sure there is a post on it already... I looked through the CM10 thread in original development but didn't see anything. I am totally stock on 1.22.651.3.
Click to expand...
Click to collapse
The process is fairly similar to most other devices, with the one unusual quirk being HTC's unlock method does not allow the kernel portion of a ROM to be loaded from the custom recovery.
Assuming you have to use the HTC unlock method, this quirk will apply to your process.
There are multiple ways to approach working around the quirk, but I'll provide two common methods.
1) After unlocking the device, which can be done with packaged up software or by directly using HTC's software at htcdev.com, you'll want to make sure you have the RUU (method to revert back to stock) handy in case of any issues.
2) At a high level, a ROM consists of two portions, the kernel and the system. The system will almost always be loaded through the custom recovery and the kernel, due to HTC's quirk in their unlock method, can be loaded via the command line using the fastboot command, or through the phone using my app, Flash Image GUI.
If a mistake is made or something does not load properly, a computer and the command line will be the only option, thanks to HTC's quirk.
3) The order of loading the ROM depends on the method. I would recommend either one of two methods:
1) Flash Image GUI, select the ROM .zip from the sdcard, and FIG will flash the kernel portion.
2) Reboot into the custom recovery, select the same ROM .zip from the sdcard, and the custom recovery will load the system portion.
3) Reboot and everything should work.
Another available method:
1) Reboot into the custom recovery, load the ROM .zip from the sdcard, the custom recovery will load the system portion.
2) Reboot into the bootloader/fastboot mode, extract the kernel file from the ROM .zip, and using fastboot and this command: fastboot flash boot c:\downloads\boot.img, load the kernel.
3) Reboot and everything should work.
If something doesnt work, you'll gain some experience in troubleshooting, which isn't too difficult, but takes more time. If you're new to the process, I'd plan for more time learning the ins/outs.
Hope that helps!
Thanks Joey! Not new to the game but I like to know the process before actually going through with it. I had to flash 2 times and unlock manually but I an now running Jelly Bean! Now to figure out why my WiFi is nothing even being 2 feet away from the router...
Don't forget to wipe dalvic, cache and factory reset before flashing a new ROM or you will have problems.
Sent from my EVO using xda premium
I did. Wiped cache x2, dalvik x2, factory x2, superwipe x5. Should be squeaky clean!
This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.
So im fairly new to unlocking, flashing, etc. I have a HTC One M8 for AT&T that im trying to unlock to use with different carriers. After reading a bit I realized that I had to unlock my bootloader, root, install s-off before I could achieve my goal. I used htc-one.wonderhowto. com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444 to root and unlock my bootloader. Followed the guide to a T and all was fine. Then I was going for S-Off and here's where I encounters my problems. I used htc-one.wonderhowto. com/how-to/get-s-off-your-htc-one-m8-install-custom-firmware-mods-0154461 guide and this is where I believe I fudged up bad. Step one says to download InsertCoin from insertcoin-roms. org/category/devices/onem8 this link. I downloaded the OTA 4.0.6 to 4.0.7 and saved it onto my phone I think maybe I should of downloaded the link for the full ROM and that's why im having this problem but im not sure. I followed each step with the exception to Step 3 which is also where I fudged up. I didnt back up because I didnt think it was needed since the phone was just wiped clean of everything. At step 5 my life changed forever..lol.. but when I flashed it , it said failure. I tried to follow the steps again but it kept failing to flash. So I went back and tried to re-flash SuperSU which was successful but when I go to reboot it from TWRP it says I have no OS installed and it gets stuck on the HTC boot screen unless I put my phone into fastboot mode. Which says ***unnlocked*** and ***tampered*** at the top and im stuck. Please someone help me and tell me what to do.
I recently deleted my OS by my stupidity. I fixed the issue by side loading a stock Rom via adb/twrp sideload. Saved me. There are tutorials on how to do this. Just Google search. You could also put a stock Rom on an external sd and flash that way. Don't have a link to the stock Rom I used, but it's in the resources thread in general section. Hope this works for ya
Sent from my HTC One_M8 using XDA Free mobile app
vansslamcityjam said:
I downloaded the OTA 4.0.6 to 4.0.7 and saved it onto my phone I think maybe I should of downloaded the link for the full ROM
Click to expand...
Click to collapse
The file you downloaded is if you were already on InsertCoin 4.0.6, and updating to version 4.0.7, which was not the case for you. You should have downloaded the full ROM, and that is likely why the flash failed.
If you ever have any doubt about what you are flashing, this should be a red flag to STOP and either read and research some more, or come on here and ask.
vansslamcityjam said:
I didnt back up because I didnt think it was needed since the phone was just wiped clean of everything.
Click to expand...
Click to collapse
That is why you make a TWRP backup before wiping anything.
vansslamcityjam said:
So I went back and tried to re-flash SuperSU which was successful but when I go to reboot it from TWRP it says I have no OS installed and it gets stuck on the HTC boot screen unless I put my phone into fastboot mode. .
Click to expand...
Click to collapse
Did you specifically wipe system in TWRP? If so, that is where the OS is stored, so of course wiping it means you have no OS.
I do not advocate wiping system when flashing ROM, especially if you are new to this. Reason being, it already gets wiped when you flash a ROM anyway (so its redundant). Also, if the ROM fails to flash, you will still have a working OS if you did not wipe system manually. As stated on the wipe screen in TWRP, the default wipe (data, cache, and Dalvik) is all that is usually needed. It says this for good reason.
All you need to do is download a ROM to your computer, and either adb push to the phone, sideload flash, or copy it to a removeable MicroSD card using a USB card reader. Then flash in TWRP.