I have hboot 1.5 and rooted my Evo 3D using the HTC method.
Anyway my screen will work in hboot, recovery, and on the HTC splash screen, but after that it just goes black.
I know my phone is fully booting though because the notification light works when I get a new message etc, and I can swipe the lock ring and feel the screen vibrate on keypad for my pin.
I think this happened after flashing a kernel in joeykrim's flash gui app.
I've tried flashing new roms or restoring a backup in recovery but nothing works.
Considering that I still have recovery and hboot is there anything I can do?
lrrowley said:
I have hboot 1.5 and rooted my Evo 3D using the HTC method.
Anyway my screen will work in hboot, recovery, and on the HTC splash screen, but after that it just goes black.
I know my phone is fully booting though because the notification light works when I get a new message etc, and I can swipe the lock ring and feel the screen vibrate on keypad for my pin.
I think this happened after flashing a kernel in joeykrim's flash gui app.
I've tried flashing new roms or restoring a backup in recovery but nothing works.
Considering that I still have recovery and hboot is there anything I can do?
Click to expand...
Click to collapse
Try wiping everything (data, cache, dalvik) then do a factory reset, then flash a ROM and boot.
Twolazyg said:
Try wiping everything (data, cache, dalvik) then do a factory reset, then flash a ROM and boot.
Click to expand...
Click to collapse
I just tried that a couple times and the screen is still going black after the HTC screen
You may need to wipe more than just /data etc. Either go find a good super wipe or format /system /boot /cache and /data might as well wipe android secure on the sd card too. Most likely you have a few leftover modules from your kernel that aren't playing nice. After doing this load the rom you want on the sdcard. Then flash it from fastboot on the computer. You won't be able to use joeykrms gui since by formatting everything you won't be able to boot untill everything is replaced. Flashing through fastboot on the computer will accomplish this for you.
3VO Sent
lrrowley said:
I have hboot 1.5 and rooted my Evo 3D using the HTC method.
Anyway my screen will work in hboot, recovery, and on the HTC splash screen, but after that it just goes black.
I know my phone is fully booting though because the notification light works when I get a new message etc, and I can swipe the lock ring and feel the screen vibrate on keypad for my pin.
I think this happened after flashing a kernel in joeykrim's flash gui app.
I've tried flashing new roms or restoring a backup in recovery but nothing works.
Considering that I still have recovery and hboot is there anything I can do?
Click to expand...
Click to collapse
You shoot boot in bootloader then hit power button > connect usb > it should say fastboot usb> flash the boot.img from the rom you flashed using command fastboot flash boot boot.img ( make sure you copy boot.img in you fastboot folder) > then fastboot boot cwmxxxxxxx.img > then flash a 2.3.4 kernel not any other ( ziggy anthrax etc ) then try to reboot. If you have wiped you rom then flash boot.img from the rom you wanna flash then boot into recovey using fastboot > then flash rom.zip >then flash a 2.3.4 kernel
Sorry i wasnt able to explain clearly .....i wanna go to work
hope this helps.
Dont forget to thank if i helped you
mnomaanw said:
You shoot boot in bootloader then hit power button > connect usb > it should say fastboot usb> flash the boot.img from the rom you flashed using command fastboot flash boot boot.img ( make sure you copy boot.img in you fastboot folder) > then fastboot boot cwmxxxxxxx.img > then flash a 2.3.4 kernel not any other ( ziggy anthrax etc ) then try to reboot. If you have wiped you rom then flash boot.img from the rom you wanna flash then boot into recovey using fastboot > then flash rom.zip >then flash a 2.3.4 kernel
Sorry i wasnt able to explain clearly .....i wanna go to work
hope this helps.
Dont forget to thank if i helped you
Click to expand...
Click to collapse
Oh man thanks so much! It totally worked!
Am I going to have to do this same procedure every time I want to flash a rom from now on, or should things be fixed?
lrrowley said:
Oh man thanks so much! It totally worked!
Am I going to have to do this same procedure every time I want to flash a rom from now on, or should things be fixed?
Click to expand...
Click to collapse
I don't know exactly if you have to follow same steps for different roms. Flash image GUI is to flash. recoveries and kernel. I had only used that software twice for kernel and never tried it for recovery. It has some issues with few kernels. Some work some dont. I use. the steps posted in second post of infected eternity rom thread . I don't follow all steps as all of them are not necessary.
And I think only 2.3.4 kernels work on hboot 1.50 with flash image GUI.Roms and kernels are meant to be flashed from fastboot using PC. untill we get s-off.
Related
OK so.... NONE OF THE CUSTOM ROMS BOOT!!!??!??!?!??!! :'(
Device Summary:Carrier unlocked AT&T, UNLOCKED BL, with a 2.3.4 fruit cake flash -No webtop [current state] ( fruit cake flashes perfectly)
Followed all instructions supplied by the Dev's on their respective threads/sites.
Alien 2 Beta: Stuck at "DUAL CORE" screen
Alien 3 Beta: Stuck at "DUAL CORE" screen
CherryPi .3: Stuck at "DUAL CORE" screen
piCrust .3: Stuck at "DUAL CORE" screen
Have wiped all user data and cache via CWM, and even 'fastboot -w in other cases. Also have resorted to wipe Dalvik cache which shouldn't need be done.
*****EDIT*****: I'm also on the latest radio, and latest 'CWM' from tenefar via 'fastboot flash recovery'
Worth asking, though you've probably considered it:
Did you wait upwards of 10 minutes for each? New ROMs wipe app cache among other things, and the first boot takes quite a while. Definitely avoid RSD until you get your answer, though. G/L
-omni
Just have to ask because I have been stuck on the Dual Core screen before... Are you sure you are unlocked? You have the unlocked text in the upper left hand corner??
omni_angel7 said:
Worth asking, though you've probably considered it:
Did you wait upwards of 10 minutes for each? New ROMs wipe app cache among other things, and the first boot takes quite a while. Definitely avoid RSD until you get your answer, though. G/L
-omni
Click to expand...
Click to collapse
LOL, post usually note that the initial boot after flash is ridiculously long..... but I definitely waited >10 mins, almost an hour at longest on the Alien 3 beta flash just now, then I pulled batt and Fruit caked to 2.3.4.
(worried I might turn the soft-brick to a Hard-Brick if the battery died)
bamastang said:
Just have to ask because I have been stuck on the Dual Core screen before... Are you sure you are unlocked? You have the unlocked text in the upper left hand corner??
Click to expand...
Click to collapse
Yup still have the unlocked text...... :-/ FRUSTRATING
same thing happened to me with Ninja and Alien ...i waited 30+ mins..
so i just fruitcaked back to 2.3.4 ..
defnow said:
same thing happened to me with Ninja and Alien ...i waited 30+ mins..
so i just fruitcaked back to 2.3.4 ..
Click to expand...
Click to collapse
lol, it seems like no-one who has had this problem has posted till now? xD
But did you finally get into the launcher? or a complete Boot animation???
do you using correct kernel?
What did you use to unlock/root the device?
As in method/tools/etc.
EDIT-
http://forum.xda-developers.com/showthread.php?t=1182871
I used this tool personally, on Windows 7 x64, and it worked without a hitch.
If you read the thread carefully, all of the instructions are in the OP, but if you have any additional problems, you can find fixes/help throughout the thread (or just post of course).
Otherwise, should go off without a hitch!
Jean-DrEaD said:
do you using correct kernel?
Click to expand...
Click to collapse
Tried stock GB and Faux's kernel, but this wouldn't matter cause rom's flash their own kernel right? According to the progress scripts on CWM..
Jonestown said:
What did you use to unlock/root the device?
As in method/tools/etc.
EDIT-
http://forum.xda-developers.com/showthread.php?t=1182871
I used this tool personally, on Windows 7 x64, and it worked without a hitch.
If you read the thread carefully, all of the instructions are in the OP, but if you have any additional problems, you can find fixes/help throughout the thread (or just post of course).
Otherwise, should go off without a hitch!
Click to expand...
Click to collapse
I used the pudding/fastboot oem unlock method for x64 windows, the application put together should do the exact same thing but without the user needing to do the actual steps individually, but any ways will give it a go
weaz_da_smel said:
Tried stock GB and Faux's kernel, but this wouldn't matter cause rom's flash their own kernel right? According to the progress scripts on CWM..
Click to expand...
Click to collapse
flash kernel after flash the rom because that... try FR an ATT kernels...
weaz_da_smel said:
OK so.... NONE OF THE CUSTOM ROMS BOOT!!!??!??!?!??!! :'(
Device Summary:Carrier unlocked AT&T, UNLOCKED BL, with a 2.3.4 fruit cake flash -No webtop [current state] ( fruit cake flashes perfectly)
Followed all instructions supplied by the Dev's on their respective threads/sites.
Alien 2 Beta: Stuck at "DUAL CORE" screen
Alien 3 Beta: Stuck at "DUAL CORE" screen
CherryPi .3: Stuck at "DUAL CORE" screen
piCrust .3: Stuck at "DUAL CORE" screen
Have wiped all user data and cache via CWM, and even 'fastboot -w in other cases. Also have resorted to wipe Dalvik cache which shouldn't need be done.
*****EDIT*****: I'm also on the latest radio, and latest 'CWM' from tenefar via 'fastboot flash recovery'
Click to expand...
Click to collapse
start from scratch...go back to stock via RSD...
DO NOT DO THIS
if the fuse is blown YOU WILL BRICK
I would fruitcake back to 1.83 then flash to the rom you want, since its voda I would try a working international rom first.
DO NOT GO BACK VIA RSD YOU MIGHT HARD BRICK.
wipe all data in fastboot -> flash stock 2.3.4 via fastboot -> wipe all data again
Not trying to hi-jack the thread but I have the exact same problem so I thought I'd post here and give a detailed description of what I've done instead of creating another thread just like this one.
I unlocked the bootloader using the latest version of pudding
Then I downloaded fastboot and installed CWM
I downloaded the ROM of my choice meaning Alien 3 and the theme, and later when that didn't work Redpill 3. Also for the record I've tried installing with Alien 3 standalone and wait for boot up, and with both - neither worked and Redpill produces the same result.
Anyway back to the process
After downloading and putting the file of my choice on the external sd card I boot up into android recovery (flashed to CWM) I go to advanced and wipe the dalvik and then wipe the regular cache partition.
I reboot and immediately go to fastboot,
I do the fastboot -w command and then the fastboot reboot command and immediatley go back to CWM
I install using the external sd card and choose the zip of my liking.
It installs great and I then wipe the dalvik and cache again.
I reboot and I get stuck at the red M dual core screen.
The only way to get unstuck is to reflash with 183-sb-release.zip which is the fruitcake release I think. I got this from someone on a forum describing a similar problem for which this was the solution. However afterwards he was able to reinstall a custom rom without problems, while my problem remains.
*Edit - I have an AT&T phone
diviluxfloss said:
After downloading and putting the file of my choice on the external sd card I boot up into android recovery (flashed to CWM) I go to advanced and wipe the dalvik and then wipe the regular cache partition.
I reboot and immediately go to fastboot,
I do the fastboot -w command and then the fastboot reboot command and immediatley go back to CWM
I install using the external sd card and choose the zip of my liking.
It installs great and I then wipe the dalvik and cache again.
I reboot and I get stuck at the red M dual core screen.
Click to expand...
Click to collapse
To double check -> Are you using latest unlocked CWM from xda or rom managers one?
Also to double check -> you did Wipe data / Factory reset as well?
You should do all three Wipe options before and after flashing the rom -> wipe cache, wipe data / factory reset, wipe davik.
After that reboot and give it a couple of minutes to boot.
If that doesn't work, do a battery pull and try booting again.
Thank you for the swift reply
I have the latest CWM from XDA.
I have tried several enumerations including wipe cache, wipe dalvik and wipe data/factory reset.
I've also tried removing the battery.
Still no success :/
diviluxfloss said:
Thank you for the swift reply
I have the latest CWM from XDA.
I have tried several enumerations including wipe cache, wipe dalvik and wipe data/factory reset.
I've also tried removing the battery.
Still no success :/
Click to expand...
Click to collapse
Alright, then the second thing I would try is flashing one of the custom ROMs via fastboot:
moto-fastboot flash boot boot.img
moto-fastboot flash system system.img
moto-fastboot -w
moto-fastboot reboot
p.s. and if you don't have the latest radio,-
moto-fastboot flash radio radio.img
Again thank you for the swift reply
Is flashing with fastboot dangerous in comparison to cwm? Ie. is there a larger risk of inherent soft/hard-bricking?
Also here comes a noob question so I hope you'll be lenient with me, but what is a radio per say and how will it help during the flashing of a rom?
Thank you I appreciate the help so far!
diviluxfloss said:
Again thank you for the swift reply
Is flashing with fastboot dangerous in comparison to cwm? Ie. is there a larger risk of inherent soft/hard-bricking?
Also here comes a noob question so I hope you'll be lenient with me, but what is a radio per say and how will it help during the flashing of a rom?
Thank you I appreciate the help so far!
Click to expand...
Click to collapse
The only truly dangerous method of flashing is SBF (RSDlite). CWM and fastboot are safe.
If you unlocked the bootloader youserlf, you already know what fastboot looks like. Often, fastboot helps where CWM fails.
Before using fastboot, make sure you have phone drivers installed, also make sure you have "moto-fastboot" version and not "fastboot", as the latter can't flash large files, e.g. - system.img.
Phone drivers for Windows x64 can be downloaded here (though your probably have them already if you unlocked the BL) -
http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
Download moto-fastboot for your operating system here (if you don't have it already, obviously) -
http://forum.xda-developers.com/showthread.php?t=1138092
"Radio" is software that handles cellular connection, mobile data, etc.
I've read that there could be a boot problem if wrong radio is used.
Besides, the latest 2.3.4 radio includes many bug fixes and better mobile data speeds.
You can check if you have the latest one under "About Phone" -> "Baseband version". Latest one for ATT is N_01.77.30P.
It can be downloaded here - http://bandbinnovations.com/xda/gingerbread/Gingerbread-4.5.91.zip
(The archive contains all stock 2.3.4 partitions, but you can simply extract radio.img and flash it separately via fastboot)
Cheers.
Great
I'll try flashing the radio and then the files as mentioned in your previous post. A problem though is that when I look through the zip files I only find a boot.img file for the custom rom.
Where is the system.img file located and if I simply install these through moto-fastboot (thanks for the heads up btw as I only had fastboot) what happens to the smaller files located on the zip which won't be associated to the img files?
*Edit I compared these to the fruitcake zip and in the custom roms I have a folder called system which I believe contains all the info while the fruitcake files have an img. I'm guessing not compatible? Or can I simply make an img file with the system folder and flash thusly?
Need some help and am not having any luck on the forums.
I have an Hboot 1.5 Evo 3D rooted with the Synergy ROM. I have EXT4 files, and a ziggy kernal.
I have had the ROM or 2 months. I overclocked it to 1.8 GHZ the other day and locked the phone up. I kept trying to reboot and when I did it just locked up. I overcloked in SetCPU, and it was checked "set at boot", so I couldn't get it back down. I kept doing this, tried a factory reset in hboot, and now the only thing the phone does is tries to boot the rom and gets stuck after about 30 seconds.
What can I do? Is this phone fried? I tried to use the command prompt on my computer and can't get anything to communicate with the phone via fastboot USB. Answers needed as I have had a non functioning phone for 4 days. An answer or a link would be greatly appreciated.
Boot into recovery and flash a new rom (or reflash the rom). Make sure you wipe data/cache partitions/dalvik cache before flashing the rom and then wipe the dalvik cache again after flashing the rom.
Theonew said:
Boot into recovery and flash a new rom (or reflash the rom). Make sure you wipe data/cache partitions/dalvik cache before flashing the rom and then wipe the dalvik cache again after flashing the rom.
Click to expand...
Click to collapse
Can't get into clockwork mod recovery to do that. Don't know what the problem is but I am about to just run this thing over and take it to Best Buy.
bgdog86 said:
Can't get into clockwork mod recovery to do that.
Click to expand...
Click to collapse
Reflash ClockworkMod recovery then, via fastboot. Use this: http://forum.xda-developers.com/showthread.php?t=794638.
I flashed a ROM (InfectedROM) all was working and the phone was up and running until the phone crashed. The phone then went into an endless reboot so I booted into recovery (TWRP) and I restored the nandroid backup I made before I started, but now it goes to the HTC splash with the white background and won't do anything else.
[Edit]
Well I managed to kinda fix the problem. I booted into recovery and selected wipe all data (Factory reset), then I re-flashed InfectedROM and managed to get the phone to boot. Still can't understand why my nandroid backup don't work to make the phone boot.
I would like to revert back to the stock ROM but being able to use my phone is better than not...
My Device:
hboot: 1.5
Unlocked via HTC's method
trm96 said:
I flashed a ROM (InfectedROM) all was working and the phone was up and running until the phone crashed. The phone then went into an endless reboot so I booted into recovery (TWRP) and I restored the nandroid backup I made before I started, but now it goes to the HTC splash with the white background and won't do anything else.
[Edit]
Well I managed to kinda fix the problem. I booted into recovery and selected wipe all data (Factory reset), then I re-flashed InfectedROM and managed to get the phone to boot. Still can't understand why my nandroid backup don't work to make the phone boot.
I would like to revert back to the stock ROM but being able to use my phone is better than not...
My Device:
hboot: 1.5
Unlocked via HTC's method
Click to expand...
Click to collapse
Well when you did this did you fastboot boot recovery.img and wipe and then try the nan? Maybe what you need to do.. Also if you make future ones I would fastboot boot recovery.img and then make a nandroid backup..
reaper24 said:
Well when you did this did you fastboot boot recovery.img and wipe and then try the nan? Maybe what you need to do.. Also if you make future ones I would fastboot boot recovery.img and then make a nandroid backup..
Click to expand...
Click to collapse
Does it make a difference if I fastboot boot recovery.img to wipe before I restore my nan backup? To answer you question, no I did not. Here's what I did form the get go:
1) unlocked my bootloader via HTC's unlock method leaving my phone's bootloader unlocked with s-on
2) I after a while decided to try out anther ROM I went with InfectedROM, So I booted into recovery (TWRP) holding the vol down key while pressing the power key and made a nan backup
3) I rebooted my phone using reboot system from TWRP
4) I then rebooted my phone (adb reboot bootloader)
5) I went into fast boot and booted into recovery (fastboot boot recovery.img)
6) I wiped all data then went into install from zip selected the InfectedROM zip on my sdcard
7) Rebooted via recovery's reboot command
Please bear with me while I am a wiz at using the command line in both Linux and Windows I am a noob when it comes to flashing roms and such.
trm96 said:
Does it make a difference if I fastboot boot recovery.img to wipe before I restore my nan backup? To answer you question, no I did not. Here's what I did form the get go:
1) unlocked my bootloader via HTC's unlock method leaving my phone's bootloader unlocked with s-on
2) I after a while decided to try out anther ROM I went with InfectedROM, So I booted into recovery (TWRP) holding the vol down key while pressing the power key and made a nan backup
3) I rebooted my phone using reboot system from TWRP
4) I then rebooted my phone (adb reboot bootloader)
5) I went into fast boot and booted into recovery (fastboot boot recovery.img)
6) I wiped all data then went into install from zip selected the InfectedROM zip on my sdcard
7) Rebooted via recovery's reboot command
Please bear with me while I am a wiz at using the command line in both Linux and Windows I am a noob when it comes to flashing roms and such.
Click to expand...
Click to collapse
So you are on the latest software? If you want something close to stock just to keep things smooth you could try fresh rom or my rom I did both of these are stock based... If you want just the stock look with stock everything go for the stock rooted copies they have in the dev section..
I never made a nandroid copy of my orignal rom since a ruu will always save you when you have to unroot
Does the nandroid back up cause reboots or a hang... Sometimes it takes a good 3 mins for it to move on depends...
When you made the nan backup were you on the 2.08 software or the 2.17 ? Did you update to the 2.17 after you made a backup in the past?
reaper24 said:
So you are on the latest software? If you want something close to stock just to keep things smooth you could try fresh rom or my rom I did both of these are stock based... If you want just the stock look with stock everything go for the stock rooted copies they have in the dev section..
I never made a nandroid copy of my orignal rom since a ruu will always save you when you have to unroot
Does the nandroid back up cause reboots or a hang... Sometimes it takes a good 3 mins for it to move on depends...
When you made the nan backup were you on the 2.08 software or the 2.17 ? Did you update to the 2.17 after you made a backup in the past?
Click to expand...
Click to collapse
I am indeed running the latest software. Thank you I will check out your ROM!
My nandroid back backs up and restores fine but after I reboot after doing a restore the phone does not boot, it just stays on the HTC logo with the white screen.
I did not do any updates after I did my nan backup.
trm96 said:
I am indeed running the latest software. Thank you I will check out your ROM!
My nandroid back backs up and restores fine but after I reboot after doing a restore the phone does not boot, it just stays on the HTC logo with the white screen.
I did not do any updates after I did my nan backup.
Click to expand...
Click to collapse
the boot.img file you have in your restore set up is invalid... i would try to resave your settings agin and then restore from there...boot.img should write to the boot partition if not through recovery then through manual flashing in fastboot
MeanROM is also pretty nice. It is like FreshRom and CleanRom in the way that it is based around Stock, except that it has some pretty beefy features.
Hi this is my first post!
im having some problems with installing cm10 on my evo.
Im have HBOOT-1.19 because i updated my phone like 2 days ago. so im on sense4.1 also
my evo is unlocked and rooted and installed recovery(twrp)
I tryed to install many of cm10s like cm-10-20120912-NIGHTLY-jewel.zip
but i couldn't get it work
i can flash it, but when it reboots, loading forever with boot animation on(with blue circle) i waited 1h30min but still loading
does anybody know how can i install cm10 to my updated evo???
thanks!
and..... sorry for my bad english. its not my first language so.....ya! haha
You need to fastboot kernel do you have the adb tools package? Also English is not your mother tongue yet you know the phrase swag ninja? Sorry I have a short attention span
Know the limits of your H-boot....
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
thanks guys i got it to work !!!
swagninja said:
thanks guys i got it to work !!!
Click to expand...
Click to collapse
For flashing without needing a PC flash image gui is the bees knees, used it on my 3D faithfully since don't own a PC, all you need to do is extract the boot.img (most roms and kernels have them posted since this is now a common issue) flash it through the GUI.apk, go to recovery, wipe, flash & proceed
Leading The Evolution EVO LTE
is it just me or did voice search get screwed up in the newest nightly for cm10 rarely recognizes what i say anymore when before it recognized almost everything
noneed2aim said:
is it just me or did voice search get screwed up in the newest nightly for cm10 rarely recognizes what i say anymore when before it recognized almost everything
Click to expand...
Click to collapse
speak into the top of your phone, a bit annoying but it uses top microphone for some reason
om4 said:
speak into the top of your phone, a bit annoying but it uses top microphone for some reason
Click to expand...
Click to collapse
thanks i also wanted to know if there was a way to sync contact pics with facebook or is that unavailible as of the latest build
As far as I know Google removed Facebook sync, but I think it was just contacts anyway. There's a few Facebook sync apps in the market
swagninja said:
thanks guys i got it to work !!!
Click to expand...
Click to collapse
hi swagninja i'm new to flashing an in the same boot as you have hboot 1.19 sense4.1 and android 4.0.4
I have bean trying to flash cm10 for last couple of days and cant get pass boot animation can you please tell me which method you use to get it work and explain how you go about it
thanks in advance
The kernel has to be flashed separately, make sure to wipe the partitions before installing cm10
om4 said:
The kernel has to be flashed separately, make sure to wipe the partitions before installing cm10
Click to expand...
Click to collapse
can you give a quick explanation how you flash the kernel separately and how you go about wiping the partition before installing cm10
Extract the boot image from the rom zip, drop in in your adb folder and restart phone in boot loader. Open the terminal and navigate to the folder and type fastboot flash boot boot.img, then open twrp recovery. Go to wipe and wipe Dalvik, Cache, Factory reset, and wipe system. Install cm10 and again clear dalvik and cache then reboot
om4 said:
Extract the boot image from the rom zip, drop in in your adb folder and restart phone in boot loader. Open the terminal and navigate to the folder and type fastboot flash boot boot.img, then open twrp recovery. Go to wipe and wipe Dalvik, Cache, Factory reset, and wipe system. Install cm10 and again clear dalvik and cache then reboot
Click to expand...
Click to collapse
if i do a system wipe will this wipe boot image that i just flash with flash image gui
Boot partition is locked in recovery which is why you have to fastboot kernel, besides that you aren't wiping the boot, you are wiping system
Partitions:
Boot
System
Recovery
Data
Cache
om4 said:
Boot partition is locked in recovery which is why you have to fastboot kernel, besides that you aren't wiping the boot, you are wiping system
Click to expand...
Click to collapse
when i finish flashing the new rom what steps to follow if i want to go back to my stock rom
Wipe the phone and flash kernel and ROM with stock
om4 said:
Wipe the phone and flash kernel and ROM with stock
Click to expand...
Click to collapse
Wipe the phone and flash kernel and ROM with stock
where will i get the kernel and Rom with stock
In the android development section
om4 said:
In the android development section
Click to expand...
Click to collapse
what is the android development section and where do i locate it
Okay I know this is a noob question so PLEASE excuse my noob-ism. Not sure if this should be in Q&A or Dev so please move to the correct section if I posted in the wrong one.
Okay, so my phone was originally 4.0.4 with a 1.19 HBOOT and 4.1 Sense. I rooted my phone, read up on a couple of threads and youtube videos regarding how to flash CM10 and from what I got if you have 1.19 HBOOT you can't just flash it using TWRP because you can't go S-OFF. Here is where I was a bit confused and think I went wrong. I read in the description of this video http://www.youtube.com/watch?v=HsQKOhqdPpM that if you aren't S-OFF that there is a workaround, which linked me to this page http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397 . So the 1st option said that it's possible to flash using Flash Image GUI to flash CM10 THEN to flash it in recovery, which I did. However now that I look closely at the pics it says only for EVO4G and the 3D. Here's where I'm at, Flashed using Flash Image GUI, then rebooted to HBOOT, then recovery, then flashed using TWRP. It looked like a success after rebooting because I seen the CyanogenMod boot screen but it's been about 25 minutes and it's just stuck there. Read up on it some more and it said that it should only take about 5-7 minutes for the first boot. I don't know what to do from here. Is there any way to still boot CM10 on my device since it seems essentially stuck at the "CM" boot screen? If not, what ROM would take me back to where I initially started off previous to trying to flash CM10 (like sense essentially)?
Once again, sorry for the noob-ism but kinda stuck here. Thanks!
I would try going into recovery and wipe Dalvik, Cache and then factory reset, do not wipe system just the 2 I mentioned and reboot, if it stays on boot anim, go to bootloader and fastboot kernel and reboot
If you have SDK or adb tools then open terminal and navigate to the folder, open cm10 zip and extract the boot image and place it in that directory, with you phone in fastboot, type fastboot devices to ensure you are connected and type fastboot flash boot boot.img it will state write time and ok, then try reboot again
hold down the power button until the phone shuts off, when it does, hold power and volume down to get to boot loader, press volume down to recovery and then press power, in recovery wip all and restore nandroid back up,,,hope you made a back up hope this helps
It's probably something corrupt in dalvik or cache, could also be a kernel mismatch but I think it's more likely phone was not properly wiped prior to flashing cmx
drlzanej said:
hold down the power button until the phone shuts off, when it does, hold power and volume down to get to boot loader, press volume down to recovery and then press power, in recovery wip all and restore nandroid back up,,,hope you made a back up hope this helps
Click to expand...
Click to collapse
Didn't make a backup, noob mistake. I've rooted phones before but this is my first one putting a custom rom on.
om4 said:
It's probably something corrupt in dalvik or cache, could also be a kernel mismatch but I think it's more likely phone was not properly wiped prior to flashing cmx
Click to expand...
Click to collapse
THANK YOU! IT WORKED!
mista_k said:
Didn't make a backup, noob mistake. I've rooted phones before but this is my first one putting a custom rom on.
THANK YOU! IT WORKED!
Click to expand...
Click to collapse
no problem just keep in mind that when switching roms, especially different bases (ics sense, aosp ics, aosp jb) wipe the dalvik and cache because they can easily be corrupted
om4 said:
no problem just keep in mind that when switching roms, especially different bases (ics sense, aosp ics, aosp jb) wipe the dalvik and cache because they can easily be corrupted
Click to expand...
Click to collapse
Sorry to hijack the thread but I am in the same situation.
Wiped Dalvik, Cache and even System...
But still, can't get pass the CMX boot animation.
Any suggestions?
Thanks
EdRF said:
Sorry to hijack the thread but I am in the same situation.
Wiped Dalvik, Cache and even System...
But still, can't get pass the CMX boot animation.
Any suggestions?
Thanks
Click to expand...
Click to collapse
S-on or s-off
You'll have to flash the kernel seperate if your s-on via fasboot or flash image gui
Sent from my EVO using xda premium
om4 said:
If you have SDK or adb tools then open terminal and navigate to the folder, open cm10 zip and extract the boot image and place it in that directory, with you phone in fastboot, type fastboot devices to ensure you are connected and type fastboot flash boot boot.img it will state write time and ok, then try reboot again
Click to expand...
Click to collapse
Following this step of the process fixed this same issue for me.
Thanks both (hut thanks button too )
I flashed via flashgui and also via fastboot.
Then flashed the rom.
But still stays in the boot animation.
Sent from my EVO using xda app-developers app
corcgaigh said:
S-on or s-off
You'll have to flash the kernel seperate if your s-on via fasboot or flash image gui
Sent from my EVO using xda premium
Click to expand...
Click to collapse
CaptinStabN said:
Following this step of the process fixed this same issue for me.
Click to expand...
Click to collapse
EdRF said:
Thanks both (hut thanks button too )
I flashed via flashgui and also via fastboot.
Then flashed the rom.
But still stays in the boot animation.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Hmm...well this time I just went to recovery. Made a backup and erased, cache, dalvik, system. Did a factory reset as well (didn't do that before) and in the end did as you guys suggested. Flashed rom and then boot.img via fastboot. Thank you very much!!! :victory:
Haven't been as active lately because I've been very sick but factory reset would have been my first suggestion. If you are starting a fresh install you should always wipe cache, dalvik, factory reset and then wipe system. I used to refer wipe scripts but for this phone there has been an unusually high number of users who's partitions (mostly internal sd) end up corrupt after using a wipe script. I don't know why, they are generally reliable and in most cases are better as they can wipe areas of the partitions that you miss wiping normally. If you are familiar with reformatting and you can back up internal regularly then you should try a wipe script. It's just a bit more convenient when it does work then manually wiping each partition.
Nothing works!
om4 said:
Haven't been as active lately because I've been very sick but factory reset would have been my first suggestion. If you are starting a fresh install you should always wipe cache, dalvik, factory reset and then wipe system. I used to refer wipe scripts but for this phone there has been an unusually high number of users who's partitions (mostly internal sd) end up corrupt after using a wipe script. I don't know why, they are generally reliable and in most cases are better as they can wipe areas of the partitions that you miss wiping normally. If you are familiar with reformatting and you can back up internal regularly then you should try a wipe script. It's just a bit more convenient when it does work then manually wiping each partition.
Click to expand...
Click to collapse
Okay so I did all of this and still..... doesn't work. I'm not really a phone wiz. I paid someone to root my phone before and I used the CM10 ROM, everything was fine until I tried to change my font, the phone rebooted and got stuck on the CM 10 boot screen. I went to recovery and restored my phone from September. I then went to Flash Image GUI and flashed the boot.img for CM!0. Then went into recovery and flashed CM!0 and gaaps and wiped the cache, delv cache, system and factory reset. When I rebooted I was still stuck on the boot screen. :/ I am able to restore back to September but my camera or wifi doesn't work. Anyone know how to help me?
Try flashing meanrom, it has the kernel installer and doesn't require flash image or fastboot. If you still have any issues with the camera then relock the bootloader and flash ruu. If that doesn't fix the camera then its most likely hardware failure.
flash gui image htc evo lte
I'm rooted s-on HTC evo 4g lte. I got the boot 2.09.
I downloaded flash GUI image. I backup my stock
ROM. Then I flash cm10.1 and everything worked
Fine. Now want to go back to my stock ROM.plz help
Me don't know how.........?????????????
SunnyDNuts said:
I'm rooted s-on HTC evo 4g lte. I got the boot 2.09.
I downloaded flash GUI image. I backup my stock
ROM. Then I flash cm10.1 and everything worked
Fine. Now want to go back to my stock ROM.plz help
Me don't know how.........?????????????
Click to expand...
Click to collapse
Flash the backup you made of your stock ROM.
Sent from my EVO using xda premium
I tried. It either says the file is to big or don't have the right file
I tried all the files on the backup
---------- Post added at 09:40 PM ---------- Previous post was at 09:15 PM ----------
FinZ28 said:
Flash the backup you made of your stock ROM.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I tried compressing the backup file so GUI would search for the
Kernel but it can't find the image
Bootloop Battery Issue
I recently flashed paranoid android to my verizon GS3 but after trying to boot I got stuck in a bootloop. It ran all last night but didnt accept a charge, and now won't turn on at all. When the battery is taken out and put back and then plugged back in it comes up with the battery charging symbol briefly but then immediately shuts off again. It wont turn on in download/recovery mode either. What should I do?
ross7alex said:
I recently flashed paranoid android to my verizon GS3 but after trying to boot I got stuck in a bootloop. It ran all last night but didnt accept a charge, and now won't turn on at all. When the battery is taken out and put back and then plugged back in it comes up with the battery charging symbol briefly but then immediately shuts off again. It wont turn on in download/recovery mode either. What should I do?
Click to expand...
Click to collapse
Do you have android sdk setup on your PC?
No but I can download it. Where should I find it?
---------- Post added at 05:27 AM ---------- Previous post was at 05:21 AM ----------
bigdaddy619 said:
Do you have android sdk setup on your PC?
Click to expand...
Click to collapse
Ok I found it and Im downloading it now. How will this help me?