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
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?
Hello my friends.
I unlocked the BL and install the CWM. So i try to install a new ROM at my Atrix.
I made the installation of the Neutrino V1.4 GT, but after made the installation of the .zip , my atrix got stuck at the boot screen.
So i made the restore of the backup that I already made, and the smartphone starts ok.
After that i tried install other ROM , CM7-ICS-FINAL and I got the same stuck boot screen.
I found other Thread about that same problem, and the user found a solution but he forgot to post that solution, just wrote ''problem solve''.
Anyone know what can i make to install the ROM ? Thanks for your attention
blindox said:
Hello my friends.
I unlocked the BL and install the CWM. So i try to install a new ROM at my Atrix.
I made the installation of the Neutrino V1.4 GT, but after made the installation of the .zip , my atrix got stuck at the boot screen.
So i made the restore of the backup that I already made, and the smartphone starts ok.
After that i tried install other ROM , CM7-ICS-FINAL and I got the same stuck boot screen.
I found other Thread about that same problem, and the user found a solution but he forgot to post that solution, just wrote ''problem solve''.
Anyone know what can i make to install the ROM ? Thanks for your attention
Click to expand...
Click to collapse
You are most likely using an outdated CWM (my guess would be Tenfar's). If it doesn't support ext4 then any ROM based on CM7 will not boot. Either use the one that comes with ROM Manager, romracer's, or TWRP.
+1
That would be my guess, the recovery.
ghost_og said:
You are most likely using an outdated CWM (my guess would be Tenfar's). If it doesn't support ext4 then any ROM based on CM7 will not boot. Either use the one that comes with ROM Manager, romracer's, or TWRP.
Click to expand...
Click to collapse
yes use romracers recovery
and.wipe data
wipe cache
wipe dalvic.cache in advanced.options
Sent from my MB860 using Tapatalk
Thanks for all the support ! I will download the romracers recovery and retry install the new ROM!
ghost_og said:
You are most likely using an outdated CWM (my guess would be Tenfar's). If it doesn't support ext4 then any ROM based on CM7 will not boot. Either use the one that comes with ROM Manager, romracer's, or TWRP.
Click to expand...
Click to collapse
live4nyy said:
+1
That would be my guess, the recovery.
Click to expand...
Click to collapse
ltdanno360 said:
yes use romracers recovery
and.wipe data
wipe cache
wipe dalvic.cache in advanced.options
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Be sure to let us know if it worked in case anyone else with the same issue can find the answer much easier.
blindox said:
Thanks for all the support ! I will download the romracers recovery and retry install the new ROM!
Click to expand...
Click to collapse
Hello my friends..
I made the install of the romracers recovery.. and i installed the ROM ( Neutrino ROM ).
But Now it gets to the boot up screen that says "Neutrino ROM ... system loading" the screen will black out for a couple seconds and then come right back to that screen in a loop. its been happening for about 15 minutes.
obs : I forgot to make the backup
Thanks for the help!
Did you use the recovery for the factory data reset and wipe cache/dalvik cache? You might want to try fastboot wipe as well.
blindox said:
Hello my friends..
I made the install of the romracers recovery.. and i installed the ROM ( Neutrino ROM ).
But Now it gets to the boot up screen that says "Neutrino ROM ... system loading" the screen will black out for a couple seconds and then come right back to that screen in a loop. its been happening for about 15 minutes.
obs : I forgot to make the backup
Thanks for the help!
Click to expand...
Click to collapse
live4nyy said:
Did you use the recovery for the factory data reset and wipe cache/dalvik cache? You might want to try fastboot wipe as well.
Click to expand...
Click to collapse
hello my friend,
i just made the WIPE CACHE AND WIPE DALVIK CACHE and the install of the ROM.
When i saw the screen NEUTRINO I was happy, until the time the ''system loading" getting black out for a couple seconds and then come right back. I knew there was something wrong.
Now I will make the process again with the factory data reset and then i will post what happened
Thanks
MY FRIEND..
thanks for all the support! I made the again the process with the factory reset and now the ROM is installed correctly.
Let me ask a question. I want to install a new kernel to try the overclock 1.3GHZ. That new kernel can be installed with the romracers ?
Thanks for the attention
**HAPPY NEW YEAR
live4nyy said:
Did you use the recovery for the factory data reset and wipe cache/dalvik cache? You might want to try fastboot wipe as well.
Click to expand...
Click to collapse
Yes, romracer is recommended. It is the only recovery that is specifically developed for the Atrix 4G. You could also try the TRWP Recovery but romracer's recovery is proven to work well and recommended by most.
Glad everything worked out.
blindox said:
MY FRIEND..
thanks for all the support! I made the again the process with the factory reset and now the ROM is installed correctly.
Let me ask a question. I want to install a new kernel to try the overclock 1.3GHZ. That new kernel can be installed with the romracers ?
Thanks for the attention
**HAPPY NEW YEAR
Click to expand...
Click to collapse
I installed the ICS rom by zeubea on my htc legend, i followed the installation and it worked good. and then i installed the gapps, and now my phone is bootlooping.
when i try to do fastboot and re-install the rom, i get this message which says something about legendimg.zip file, and it quickly disappears.
and when i try to go to recovery the device shows the backgroud of the recovery but nothing happens.
if anyone understand my question and can help me do something to make my legend work again i will thank you very much
guyshapira said:
I installed the ICS rom by zeubea on my htc legend, i followed the installation and it worked good. and then i installed the gapps, and now my phone is bootlooping.
when i try to do fastboot and re-install the rom, i get this message which says something about legendimg.zip file, and it quickly disappears.
and when i try to go to recovery the device shows the backgroud of the recovery but nothing happens.
if anyone understand my question and can help me do something to make my legend work again i will thank you very much
Click to expand...
Click to collapse
Just read the whole thread in dev section. Someone already figure it out.
Sent from my legend using XDA
petalyaa said:
Just read the whole thread in dev section. Someone already figure it out.
Sent from my legend using XDA
Click to expand...
Click to collapse
the problem is that when i try to go to recovery i see the recovery background image and nothing happens so i can't install other version of the rom.
never mind, i got it to work.
all i had to do is press VOL UP + POWER button.
everyday i learn new things
Tried to update from CM7.2 to CM9.1 by instruction:
1. wipe data
2. wipe cache
3. wipe dalvik
4. flash rom..
5. reboot
and 9.1 didnt run at all.. bootloop..
also tried
1. wipe all
2. flash
3. wipe all
bootloop...
1. wipe all
2. flash
3. wipe all
4. gapps
5. wipe all
bootloop...
rolled back to 7.2 - works fine..
p.s.
sorry for my english
Why are you NOT wiping (formatting) boot and system? If you don't your leaving all the files for the previous rom installed hence why your having issues...
Installation is so easy if you use a bit of thought,
Format boot, system, data, cache and SDext DONOT FORMAT SD CARD!
Flash rom then flash gapps then reboot.
Sent from my Legend using xda app-developers app
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?
So I had a Desire C for an year or so, and I flashed the heck out of it, so I am fairly experienced with flashing, rooting, adb/fastboot commands and that kind of stuff. For two weeks now I have a Desire X. But after flashing Half-Sense, myONEdx+, mySENSEdx+ (ofc. after flashing boot.img for each one) I just get a black screen (backlit black screen, so it's actually on). But after flashing to a non-backup stock rom (including ones with busybox, init.d support) they work fine. So essencialy I can't flash anything non-stock. Wat do?
Same here, flashed fulmix rom black screen and then reboot to recovery...
Restored backup and woeking...
Using TWRP 2.6 and my own kernel just write protection disabled..
Sent from my HTC Desire X using xda premium
jeyko said:
So I had a Desire C for an year or so, and I flashed the heck out of it, so I am fairly experienced with flashing, rooting, adb/fastboot commands and that kind of stuff. For two weeks now I have a Desire X. But after flashing Half-Sense, myONEdx+, mySENSEdx+ (ofc. after flashing boot.img for each one) I just get a black screen (backlit black screen, so it's actually on). But after flashing to a non-backup stock rom (including ones with busybox, init.d support) they work fine. So essencialy I can't flash anything non-stock. Wat do?
Click to expand...
Click to collapse
On which Hboot are you, btw the best TWRP recovery is 2.5 because 2.6 is alpha
GtrCraft said:
On which Hboot are you, btw the best TWRP recovery is 2.5 because 2.6 is alpha
Click to expand...
Click to collapse
I tried on TWRP (dunno which version), the official CWM one and (my favourite and best) PhilZ CWM. I am on the JB hboot 1.25.0002
jeyko said:
I tried on TWRP (dunno which version), the official CWM one and (my favourite and best) PhilZ CWM. I am on the JB hboot 1.25.0002
Click to expand...
Click to collapse
You don't install everything with the ICS Hboot way? and did you do a full wipe (system, data, dalvik cache and cache)?
GtrCraft said:
You don't install everything with the ICS Hboot way? and did you do a full wipe (system, data, dalvik cache and cache)?
Click to expand...
Click to collapse
Yes, SIDENOTE/offtopic I had a soft brick after a few days of use after trying to install ACID audo which led me to reinstall my Windows so the adb drivers work properly and then I could adb push another vanilla zip. All this because I don't have another device with sdcard support lol.
jeyko said:
Yes, SIDENOTE/offtopic I had a soft brick after a few days of use after trying to install ACID audo which led me to reinstall my Windows so the adb drivers work properly and then I could adb push another vanilla zip. All this because I don't have another device with sdcard support lol.
Click to expand...
Click to collapse
Try to flash a JB rom and after that, wipe cache and dalvik again
GtrCraft said:
Try to flash a JB rom and after that, wipe cache and dalvik again
Click to expand...
Click to collapse
That's what I've been doing but mkay, gonna flash fulmix and report in 15 mins or so.
jeyko said:
That's what I've been doing but mkay, gonna flash fulmix and report in 15 mins or so.
Click to expand...
Click to collapse
Maybe wiping cache in fastboot will work: ''fastboot erase cache''
GtrCraft said:
Maybe wiping cache in fastboot will work: ''fastboot erase cache''
Click to expand...
Click to collapse
Yeah, I do it every time, and this try on flashing fulmix failed too. I don't get what the problem would be. Is there a way to logcat everything?
jeyko said:
Yeah, I do it every time, and this try on flashing fulmix failed too. I don't get what the problem would be. Is there a way to logcat everything?
Click to expand...
Click to collapse
Yeah if you are in bootloader or recovery it is possible, although I'm not that good with logcat's