I have just flashed cm-11-20140118-NIGHTLY-endeavoru, gapps-kk-20140105-signed and recovery-6.0.4.5-endeavoru.img. Now I get stuck at the CM logo, it just keep spinning around. From what I can read online, it should work, and does work for other users. But no matter what I do, I cannot get past the boot animation.
Does anyone have any idea as to why that is. Everything is done right. I have flashed several ROMs many time sover on my HOX, and bootloop has always been resolved by flashing boot.img via Fastboot, but that does not work either.
Did a complete full wipe before?
Gesendet von meinem HTC One X mit Tapatalk
One-X-master said:
Did a complete full wipe before?
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
Wiping of data should never be a requirement. But I did wipe/hard reset after installing CM.
shopperen said:
Wiping of data should never be a requirement. But I did wipe/hard reset after installing CM.
Click to expand...
Click to collapse
If you flash a new ROM its always better to wipe data and format system.... Or just factory reset in recovery will be enough
Gesendet von meinem HTC One X mit Tapatalk
One-X-master said:
If you flash a new ROM its always better to wipe data and format system.... Or just factory reset in recovery will be enough
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
It is often a solution to several issues yes, but it is not better. No official System Updates ever requires factory reset. Not that it really matters, if that would be the requirement, then okay. I just think it is a bit amateurish of Cyanogen Inc. not to have resolved that yet. And in any case, it does not work. I think it is because my phone is for the Scandinavian market, and there might be something different, since I cannot find anyone from the cold north who have managed to install CM11 on their HTC One X.
Flashed boot.img?
Sent from my C6903 using Tapatalk
tomascus said:
Flashed boot.img?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Already tried that. Perhaps CM11 requirs S-Off to work.
shopperen said:
Already tried that. Perhaps CM11 requirs S-Off to work.
Click to expand...
Click to collapse
No it doesn't require otherwise nearly no one could flash it...like I said...also flash philz latest recovery and do a complete full wipe...including factory reset and format system...
Then flash the ROM again and afterwards the gapps .. It SHOULD work then...you NEED to do factory reset in recovery!!!
Gesendet von meinem HTC One X mit Tapatalk
One-X-master said:
No it doesn't require otherwise nearly no one could flash it...like I said...also flash philz latest recovery and do a complete full wipe...including factory reset and format system...
Then flash the ROM again and afterwards the gapps .. It SHOULD work then...you NEED to do factory reset in recovery!!!
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
I have already tried all of that. It does not work. When stuck in boot animation for CM, it is usually because you have flashed the wrong ROM for your device. Since that is not the case here, I do believe that Cyanogen Inc. just haven't made the CM11 compatible with the European market version of the HTC One X.
shopperen said:
I have already tried all of that. It does not work. When stuck in boot animation for CM, it is usually because you have flashed the wrong ROM for your device. Since that is not the case here, I do believe that Cyanogen Inc. just haven't made the CM11 compatible with the European market version of the HTC One X.
Click to expand...
Click to collapse
Completely wrong...its already compatible since its out...since 24th December.... Its working for all so you are doing something wrong...try another gapps package like that from paranoid android...it should work...or flash a custom kernel like audahadi's aosp kernel and maybe then it works......but at first try also fastboot erase cache...that helps often too
Gesendet von meinem HTC One X mit Tapatalk
One-X-master said:
Completely wrong...its already compatible since its out...since 24th December.... Its working for all so you are doing something wrong...try another gapps package like that from paranoid android...it should work...or flash a custom kernel like audahadi's aosp kernel and maybe then it works......but at first try also fastboot erase cache...that helps often too
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
I really appreciate all the advice. It can often be difficult to find help with these kind of issues. But truth be told, CM isn't worth all that effort. I have a stock LG G2, and it runs perfectly with root. So I may try another kernel, but that will be the final thing I'll try. I have already invested 6+ hours in this, and unless Cyanogen Inc starts offering official support within the community, I am just going to stick to stock ROMs. Fastboot erase cache is something I haven't tried either, but that shouldn't make a difference after a factory reset.
Again thank your for your responses and assistance. But I am stopping here.
shopperen said:
I really appreciate all the advice. It can often be difficult to find help with these kind of issues. But truth be told, CM isn't worth all that effort. I have a stock LG G2, and it runs perfectly with root. So I may try another kernel, but that will be the final thing I'll try. I have already invested 6+ hours in this, and unless Cyanogen Inc starts offering official support within the community, I am just going to stick to stock ROMs. Fastboot erase cache is something I haven't tried either, but that shouldn't make a difference after a factory reset.
Again thank your for your responses and assistance. But I am stopping here.
Click to expand...
Click to collapse
Cm11 is already official for our device.. Fastboot erase cache is deleting the cache for flashing...and that can prevent from booting ...the cache which will be wiped in recovery is for data bla bla for the apps etc..but the cache which is erased in fast boot is also in another place...
If you have a LG G2 why then still using and trying to flash roms on hox? ...I also flashed the different cm11 Roms and never had any problems with not booting etc..
Gesendet von meinem HTC One X mit Tapatalk
One-X-master said:
Cm11 is already official for our device.. Fastboot erase cache is deleting the cache for flashing...and that can prevent from booting ...the cache which will be wiped in recovery is for data bla bla for the apps etc..but the cache which is erased in fast boot is also in another place...
If you have a LG G2 why then still using and trying to flash roms on hox? ...I also flashed the different cm11 Roms and never had any problems with not booting etc..
Gesendet von meinem HTC One X mit Tapatalk
Click to expand...
Click to collapse
Because I really like my HOX. It is still the best smartphone I have ever had. So I thought it could get an life extension via CM11, since Android 4.4 requires less memory to run and is more battery efficient. But appearently it's just not working on my phone. I will try fastboot erase cache and maybe another kernel when I get home from work today.
It works! I have no idea what I did different. Just redid everything I have tried over the past few days again, and this time it worked. Maybe there was an issue with my computer, it had been running for 4 days without reboot.
shopperen said:
It works! I have no idea what I did different. Just redid everything I have tried over the past few days again, and this time it worked. Maybe there was an issue with my computer, it had been running for 4 days without reboot.
Click to expand...
Click to collapse
HI I've got same issue on my HTC One S (Ville).
I upgraded CWM to latest version (6.0.4.8) and done that:
- Wipe data / factory reset
- Wipe dalvik cache
- Install CM11 from zip + Gapps from zip
- Wipe data/ factory reste (again)
but I'm still stuck on rotating Cyanogen logo...
Any idea ?
julien.gresse said:
HI I've got same issue on my HTC One S (Ville).
I upgraded CWM to latest version (6.0.4.8) and done that:
- Wipe data / factory reset
- Wipe dalvik cache
- Install CM11 from zip + Gapps from zip
- Wipe data/ factory reste (again)
but I'm still stuck on rotating Cyanogen logo...
Any idea ?
Click to expand...
Click to collapse
If you wipe data/factory reset after flashing the Rom you dont need to wonder yourself why it's not working flash the Rom and the gapps again and if boot.img needs to be flashed via fastboot do it otherwise just reboot...man really xD
Gesendet von meinem HTC One_M8 mit Tapatalk
One-M8-Master said:
If you wipe data/factory reset after flashing the Rom you dont need to wonder yourself why it's not working flash the Rom and the gapps again and if boot.img needs to be flashed via fastboot do it otherwise just reboot...man really xD
Gesendet von meinem HTC One_M8 mit Tapatalk
Click to expand...
Click to collapse
I feel really stupid...
Reading too much posts about wiping after flashing ROM. Sometimes ot's good to know what I'm doing.
About boot.img: do you take it from latest Android SDK ?
I may have a problem to connect my phone on my Windows 8: is there another way with CWM to flash boot.img without using factboot command ?
julien.gresse said:
I feel really stupid...
Reading too much posts about wiping after flashing ROM. Sometimes ot's good to know what I'm doing.
About boot.img: do you take it from latest Android SDK ?
I may have a problem to connect my phone on my Windows 8: is there another way with CWM to flash boot.img without using factboot command ?
Click to expand...
Click to collapse
Wiping after flashing Rom means wiping cache and dalvik cache...second if you really have the HTC Ville go to its forum...also you have to take the boot.img from the Rom.zip not from any sdk...and yea for drivers etc go to HTC Ville thread or one s forum
Gesendet von meinem HTC One_M8 mit Tapatalk
I had the same issue, tried to load CM11 a couple of times, coming from Viper. I knew I had done it all in order.
Kept retrying and then it just took. Strange, but I'm loving it now.
UPDATE!
The bootloop was caused by a low hboot number, i flashed android revolution and it is now working! thanks for your help! when i sell my crap iphone, imma donate to you leefear!
Related
I've tried to flash the two different ROMs out for JB and for some reason it is not getting past the Nexus Logo Boot screen. I can flash any ICS ROM but JB never gets past the boot screen. I've been flashing ROMs since the OG Droid and have never experienced this before.
Steps already taken:
1) Full wipe
2) Format of system and data
3) executed Super Wipe Script
4) Battery Pulls
5) Backed out of CWM and unmounted system and data
6) Flashed Various AOKP and AOSP ROMs and tried to JB ROM from those ICS ROMs
7) Performed a factory restore of the phone using WugFresh's ToolKit (un-rooted and locked phone) and then Rooted, unlocked, and flashed CWM again
8) Flashed Team Win Recovery and re-flashed JB ROMs
I have tried everything I can think of and yet nothing has worked. Has anyone Else experienced this or does anyone have any suggestions on what I can possibly do to get past the Nexus Boot screen? Thanks in advance.
how long are you waiting after the install?
Zepius said:
how long are you waiting after the install?
Click to expand...
Click to collapse
Average wait time is 20 minutes but I've waited up to 4 hours.
which rom are you flashing?
try this one: http://www.teambamf.net/topic/4064-romtoro-jellybamf-13/
it works for me perfectly (thanks adrynalyne)
Zepius said:
which rom are you flashing?
it works for me perfectly (thanks adrynalyne)
Click to expand...
Click to collapse
I've tried Liquid Vicious Versions 1-3 and BAMF Versions 1.0 and 1.2. Thanks for the updated BAMF...I'll try that one now.
I am having the same problem as you, I flashed multiple JB roms and it is stuck at the X screen. I can flash ics roms easily tho.
I had the freeze at logo issue a few times while I was trying to get my JB up and running.
1. I got superwipe from http://forum.xda-developers.com/showthread.php?p=20473980
2. I dl JellyBelly and GApps from http://rootzwiki.com/topic/28677-rom-jelly-belly-v17-07012012-jellybean-41-its-all-about-speed/
3. Cleared cache/factory reset
4. Flashed and used superwipe
5. Flashed JellyBelly then GApps
I had to wait about 5 minutes while it booted. Hope this helps, yall.
I'll definitely try those steps...Thanks!
Sent from my HTC One X using Tapatalk 2
keno23 said:
I'll definitely try those steps...Thanks!
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Glad to pass along the help I got earlier :highfive:
consultant.ben said:
I had the freeze at logo issue a few times while I was trying to get my JB up and running.
1. I got superwipe from http://forum.xda-developers.com/showthread.php?p=20473980
2. I dl JellyBelly and GApps from http://rootzwiki.com/topic/28677-rom-jelly-belly-v17-07012012-jellybean-41-its-all-about-speed/
3. Cleared cache/factory reset
4. Flashed and used superwipe
5. Flashed JellyBelly then GApps
I had to wait about 5 minutes while it booted. Hope this helps, yall.
Click to expand...
Click to collapse
Unfortunately it did not work...same Nexus Bootscreen forever. Thanks though.
i have the same the problem with my phone , i flash the jb rom it works fine the first time booting i setup my account download my apps every thing works fine BUT when i re-start the phone the phone got stock on the google logo and don't re-start again, so guess what i have to try another rom so i try a regular ICS rom guess what on the first boot the phone got stock on the boot logo so i try another ICS rom and the same thing happing stock again on the boot logo, so i have to do flash the google factory rom to my phone got back to work
Same her.. infinite boot loop.. I'm tired of unbricking back to stock
Flash all kinds of from and kernel combo and still got boot loop.. I hope someone can help us with this..
Try mROM http://forum.xda-developers.com/showthread.php?t=1763823
Make sure wipe/factory reset and also wipe caches while you're at it. Also make sure that CWM is updated.
keno23 said:
Unfortunately it did not work...same Nexus Bootscreen forever. Thanks though.
Click to expand...
Click to collapse
Same here, I've tried just about every rom out there now and have cleaned the phone out several times. Wonder if there is anyone who had a boot longer than 20 minutes and finally was able to get it to boot, wonder what they did to get it to boot. I've waited hours with some of these roms and still no luck.
nothingshocking said:
Same here, I've tried just about every rom out there now and have cleaned the phone out several times. Wonder if there is anyone who had a boot longer than 20 minutes and finally was able to get it to boot, wonder what they did to get it to boot. I've waited hours with some of these roms and still no luck.
Click to expand...
Click to collapse
Are you wiping dalvik and system cache along with doing data wipe?
mb9023 said:
Are you wiping dalvik and system cache along with doing data wipe?
Click to expand...
Click to collapse
wipe data/factory reset -> wipe cache partition -> wipe dalvik -> format /system -> format /data -> format/cache. I've tried super wipe. All Roms never get passed the boot animation. I get past the "Google" unlock symbol, but it just sits at the boot animation. It doesn't reboot or anything, just sits there for hours or when I get bored looking at it after about 30 minutes or so.
@nothingshocking
We have the same problem.. I been flashing all kinds of jb rom since last week..I'm not new in flashing rom and kernel so I know what doing.. it so weird that it only stay in Google logo (x) when I flash jb rom..but if I flash ics it will boot up.. hayzzz I hope someone can help us with this issue.. calling all great dev. I hope u can help us..
Sent from my Galaxy Nexus using XDA Premium App
landrian18 said:
@nothingshocking
We have the same problem.. I been flashing all kinds of jb rom since last week..I'm not new in flashing rom and kernel so I know what doing.. it so weird that it only stay in Google logo (x) when I flash jb rom..but if I flash ics it will boot up.. hayzzz I hope someone can help us with this issue.. calling all great dev. I hope u can help us..
Sent from my Galaxy Nexus using XDA Premium App
Click to expand...
Click to collapse
Not going to happen man...I've tried EVERYTHING and have gotten feedback from various devs to no avail. All I get is Nexus boot logo FOREVER.
Solution is to flash it back to stock (plus unroot and re-lock) and then take it in to a store and get another one shipped to you since it's still under the annual warranty. As for the issue for bringing it in, just say it boot loops at random times (that's not technically a lie).
Sent from my Galaxy Nexus using Tapatalk 2
Have you tried flashing the JB Boot loader and then flashing the JB ROM??
It is from jakeday and his Jelly Belly ROM
adclem said:
Have you tried flashing the JB Boot loader and then flashing the JB ROM??
It is from jakeday and his Jelly Belly ROM
Click to expand...
Click to collapse
That doesn't work either. Thanks though.
Sent from my HTC One X using Tapatalk 2
Hey guys,
I think I just bricked my phone...
I was trying ViperX Rom and somehow that didn't work. I did everything full wipe, flashed included boot.img, installed rom, flashed boot.img again, but it just didn't boot. So I thought, I just restore my backup with twrp. Everything seemed fine, but I don't have a IMEI in the options, no signal, nothing. I think TWRP said something at the beginning of the restore about "Couldn't mount android secure", any ideas?
Assume you flashed the boot.img from the nandroid backup also and not still on the viper one?
Sent from my HTC One X
Do I have to do that manually? It said "restoring boot" in the process.
Also I can see my IMEI in the bootloader, so it's still there.
Yeah, it can't be flashed/restored automatically due to lack of s off.
Sent from my IceCold One X
TToivanen said:
Yeah, it can't be flashed/restored automatically due to lack of s off.
Sent from my IceCold One X
Click to expand...
Click to collapse
YEEEESSSSS, that did it, god thanks!
But I'm still wondering why the ViperX Rom woudln't boot...
What is your hboot version?
Sent from my IceCold One X
1.39
edit: I really followed the instructions step by step. I did: Wipe Cache, wipe dalvik, wipe data, wipe system. Then I booted into bootloader and flashed the boot.img which was in the ViperX 3.4.3 zip. Then I booted into recovery erased cache again and installed the viper rom. I checked "Full wipe" in aroma. Then I didn't boot but went into bootloader again and flashed the boot.img again. After that I wiped the cache again and did the final reboot and it didn't boot.
edit2: okay, I just found this in the viper thread:
3.4.3 has booting up problems as you can read on the last pages. Download 3.4.0 from the OP and install that. Then do the ota's to 3.4.3
Click to expand...
Click to collapse
Crap, usually I read the threads for 2 days to find out if there are problem, ah well, my bad!
Edit : was already in my quoted text
Mr Hofs said:
Edit : was already in my quoted text
Click to expand...
Click to collapse
nice, installed ViperX 3.4.0 and it worked fine what an awesome rom on the first look btw
Kamairo said:
nice, installed ViperX 3.4.0 and it worked fine what an awesome rom on the first look btw
Click to expand...
Click to collapse
Agreed, it's one of the best I've tried. It was like having a new phone when I first put it on. Glad you got it sorted.
Sent from my HTC One X
Hi all,
I have an international (Asia_TW CID__621) HOX. After running CM10.1 for the past while I decided to try CM11. I was at hboot 1.33 so I needed to take care of that first so I found out how to do so by flashing a nandroid backup and allowing it to update to the most recent stock ROM. All was well with the up to date HTC Sense ROM however I still decided to move to CM11 which I did. After a few bugs in CM11 that I didn't like I've decided to give the stock rom a shot again however I am running into a few issues.
I re-flashed the same nandroid backup as I did previously as well as boot and recovery images. Now I boot into the stock rom and the touchscreen does not work. Not the end of the world, I plugged in an OTA USB cable with a mouse and used my mouse to setup the phone, I then made the phone check for an update and one was found and it downloaded, rebooted, installed, rebooted, and I am back into the OS again however I still have no mouse and even worse I have no data or wifi either and they can not be enabled.
Anyone have any idea what I have done wrong? Do I need a different kernel or something? I believe that even after the first update the hboot was still at 1.33. Do I need to move the hboot back to a previous version? What to do what to do?
Thanks xda for your help.
You can't lower the hboot without s-off...try to get a nandroid backup for your new main version which is for hboot 1.7x and restore it...be sure to flash the boot.IMG of that backup...then all should work..
Gesendet von meinem One X mit Tapatalk
One-X-master said:
You can't lower the hboot without s-off...try to get a nandroid backup for your new main version which is for hboot 1.7x and restore it...be sure to flash the boot.IMG of that backup...then all should work..
Gesendet von meinem One X mit Tapatalk
Click to expand...
Click to collapse
Thanks for the response One-X-master.
I managed to do just that shortly after posting. I re-read the "Getting back to stock" thread here http://forum.xda-developers.com/showthread.php?t=1859714 and then I downloaded the CID__621 Nandroid Backup 4.18.950.2 from THIS THREAD. I extracted it, flashed boot.img via fastboot, copied it to /sdcardo/clockworkmod/backup/ and restored via recovery, and also flashed the recovery.img that was in the nand backup although it is not the stock recovery. I'm still looking for the 4.18.950.2 recovery image however everything is working now and there are no pending updates so not having the current recovery isn't the end of the world right now
https://www.dropbox.com/s/h0kko0c304992w7/Stock recovery 4.18.img
This should do the trick whenever you need it.
Mr Hofs said:
https://www.dropbox.com/s/h0kko0c304992w7/Stock recovery 4.18.img
This should do the trick whenever you need it.
Click to expand...
Click to collapse
Thanks Mr Hofs
Hi friends. I have a small problem with the launch of Android 4.1.2 system after the downgrade of cKitkat CM11. The phone gets bootloop and even after a long wait, do not want to start. I do not have a computer at this time The jellybean was winning by as packed zip with CWM latest version of this topic http://forum.xda-developers.com/showthread.php?t=2582851 How to eleminated bootloop after downgrade?
Refresh
Make sure you wiped data and cache before install...
Gesendet von meinem GT-I9100
Hi, all. I have custom ROM Eragon v 2.5 and i wanna it update to v 3.0. What is the best procedure ? Thanks.
Is it a must dat I will first have a Eragon Rom before I will start updating to the latest version like 2-3.0 or should go ahead in downloading the latest update???
Why don't you ask that in the Eragon thread??
Because am a new member and I wasn't allowed to post there, please if u were opportune to post there, please help me ask the same question
can i do this ?
1. dowloading ROM v 3.0 and copy into internal sd card
2. reboot to recovery
3. factory reset
4. "instal zip from sd card" and choose Eragon v3.0
Yes or not ? Please sorry, but i´m beginner. Thanks.
I guess I need more research on this stuff to avoid bricking my phone
yeah
i did it yesterday and i workd great..
Flash your phone to Stock 25/7
Flash CWM
Put eragon 3.0 in sd
Restart to CWM
whipe cash only.
Install eragon 3.0.
works great.
if you have questions, just ask .
showshow747 said:
Hi, all. I have custom ROM Eragon v 2.5 and i wanna it update to v 3.0. What is the best procedure ? Thanks.
Click to expand...
Click to collapse
if i read correctly you are on Eragon v2.5 already
Copy Eragon V 3.0 to internal SD
boot into CWM
wipe davlik cache and wipe data ( no factory reset, as you will lose all personal data)
install zip from internal SD card (Eragon_P_8000_V.3.0.zip
reboot the phone
enjoy Eragon v3.0
hi
to install eragon.rom
you need to be rooted and install cwm recovery
1. download and copy the rom.zip to your sdcard ( i prefer the external , but internal card is ok too)
2. if you are coming from stock rom or from older eragon releases perform a factory reset and wipe cache (to prefend issues)
3. flash eragon rom .zip and wait till the procedure is finished
4. reboot your phone.
p.s you can also use the search option in eragon thread. maybe you will find all you want to know
Peinne said:
i did it yesterday and i workd great..
Flash your phone to Stock 25/7
Flash CWM
Put eragon 3.0 in sd
Restart to CWM
whipe cash only.
Install eragon 3.0.
works great.
if you have questions, just ask .
Click to expand...
Click to collapse
Please give me the link to stock 25/7
---------- Post added at 03:47 PM ---------- Previous post was at 03:36 PM ----------
skeleton1911 said:
hi
to install eragon.rom
you need to be rooted and install cwm recovery
1. download and copy the rom.zip to your sdcard ( i prefer the external , but internal card is ok too)
2. if you are coming from stock rom or from older eragon releases perform a factory reset and wipe cache (to prefend issues)
3. flash eragon rom .zip and wait till the procedure is finished
4. reboot your phone.
p.s you can also use the search option in eragon thread. maybe you will find all you want to know
Click to expand...
Click to collapse
For the first time user, after rooting and booting into cwm recovery mood, only wipe cache and flashing of eragon 3.0 rom .zip is required right?
Paulplayboy said:
Please give me the link to stock 25/7
---------- Post added at 03:47 PM ---------- Previous post was at 03:36 PM ----------
For the first time user, after rooting and booting into cwm recovery mood, only wipe cache and flashing of eragon 3.0 rom .zip is required right?
Click to expand...
Click to collapse
Wipe cache and perform a factory reset. Then flash eragon
Gesendet von meinem Elephone P8000 mit Tapatalk
1000 x thanks
skeleton1911 said:
Wipe cache and perform a factory reset. Then flash eragon
Gesendet von meinem Elephone P8000 mit Tapatalk
Click to expand...
Click to collapse
Hi, my friends. Thank you very much - Peinne, Fmcheetah and Skeleton1911 My phone is updated to version 3.0 and all works OK. Scanner is fully functional (app Camscanner). I need this app for my work. :good::good::good::good::good::good::good: Other features I will try later. But now many thanks, Skeleton1911 special
showshow747 said:
Hi, my friends. Thank you very much - Peinne, Fmcheetah and Skeleton1911 My phone is updated to version 3.0 and all works OK. Scanner is fully functional (app Camscanner). I need this app for my work. :good::good::good::good::good::good::good::good::good::good: Other features I will try later. But now many thanks, Skeleton1911 special
Click to expand...
Click to collapse
[emoji14] no problem
Gesendet von meinem Elephone P8000 mit Tapatalk
skeleton - thanks
skeleton, please check for donors.
In your ROM i apply Go Launcher and Elegant Theme, screens :
(In Slovak Language)
showshow747 said:
please check for donors
Click to expand...
Click to collapse
Thank you very much. I do greatly appreciate it!
Gesendet von meinem Elephone P8000 mit Tapatalk
Paulplayboy said:
Is it a must dat I will first have a Eragon Rom before I will start updating to the latest version like 2-3.0 or should go ahead in downloading the latest update???
Click to expand...
Click to collapse
Hi,
Seem you are already in Eragon V2.5, just download the latest V3.0 ROM and copy it to the External SD Card.
1. Boot into CWM
2. Wipe davlik cache and wipe data ( no need factory reset)
3. Install zip from external SD card (Eragon_P_8000_V.3.0.zip
4. Wait till complsted then Reboot the phone
5. Enjoy your phone with latest Eragon v3.0
Hope this help.
I just flash into V3.0 and it better than stock ROM, i have better battery life with this Eragon ROM.