MEANROM 3.4 install issues - Sprint HTC EVO 4G LTE

every time i do a fresh install from zip i do factory reset, wipe both d and c , and try to install, it gets through but says error at end. I reboot phone and it runs the new mean rom and the meanrom is also located on the sd with the files for over clocking. Is it ok to run like this still and what am i doing wrong? Everything has seemed to work so far. But it does seem like i have battery drain issues and i can watch my battery go down 10 percent every hour not sure if this is normal.

deneid310 said:
every time i do a fresh install from zip i do factory reset, wipe both d and c , and try to install, it gets through but says error at end. I reboot phone and it runs the new mean rom and the meanrom is also located on the sd with the files for over clocking. Is it ok to run like this still and what am i doing wrong? Everything has seemed to work so far. But it does seem like i have battery drain issues and i can watch my battery go down 10 percent every hour not sure if this is normal.
Click to expand...
Click to collapse
Could be a bad download, check the MD5 sum and re-download if need be.

DNarsingh said:
Could be a bad download, check the MD5 sum and re-download if need be.
Click to expand...
Click to collapse
ive downloaded multiple times from the direct forum.and i have used different versions starting back at 2.8 I havent had any issues running the rom,

I suggest to get the last version of TWRP and redownload and check md5. It should work.
Sent from my EVO using Tapatalk 2

Did you try to super wipe? That should start you completely new then flash the ROM

ill give it a try, how much better should the battery be?

It depends on what you are doing. If your on your phone streaming, or playing a game for that hour that might sound ok Imo. I usually get between 10-11 and a half hours with 2-3 hours being screen on time. But it will vary also if your OC and how much

Seen happen, sometimes very simply caused by where you are installing and mounted from. If you are mounted as internal, install from the internal SD. If external, install from external SD. It may work from time to time and with small update.zips as the reciprocal, but large ones will give errors at times. So, check where you are mounted.

hey guys i did a fresh install right now and i used the file downloaded from the ota updater 3.4 and it worked fine, thanks for the help. I am OC at 1.7 i dont think i detect much of a difference and wondering if i should just leave at stock? Also is there a way to download more then 1 item at a time from the play store this gets really annoying every time i re-rom and have to download 25 apps
thanks for your help guys i gave u some kudos
PRAISE ODIN!
:highfive:

Install
deneid310 said:
every time i do a fresh install from zip i do factory reset, wipe both d and c , and try to install, it gets through but says error at end. I reboot phone and it runs the new mean rom and the meanrom is also located on the sd with the files for over clocking. Is it ok to run like this still and what am i doing wrong? Everything has seemed to work so far. But it does seem like i have battery drain issues and i can watch my battery go down 10 percent every hour not sure if this is normal.
Click to expand...
Click to collapse
ok so I'm about to attempt a custom rom for the 1st time on my LTE. I've did this several times on my OG EVO. Is their anything I should do, check or be aware of before I flash. I've read about this new Mean Rom and it sounds like the business, so why not! Also do you guys prefer CWM or TWRP? Currently i'm running CWM as I was on my OG. I also couldn't receive the latest OTA from sprint. I tried yesterday and it went to CWM recovery but prompted an error before it installed.?!!?!!?!

Twrp recovery is more stable for our devices, use goo manager from the play store. Once installed open it up and hit the menu and download and install recovery from there, it will flash twrp for you

banccalif said:
Twrp recovery is more stable for our devices, use goo manager from the play store. Once installed open it up and hit the menu and download and install recovery from there, it will flash twrp for you
Click to expand...
Click to collapse
like banccalif said, use twrp, Download goomanager from play store to get it . Works amazing.
here is a step by step video watch?v=6bLaJc4_f0k (add youtube.com before watch sorry still rookie poster and wont allow links)
if you dont see the zip file on your rom make sure to go to mount (in the twrp recover) and make sure mount sd is clicked
Praise Odin

Before you dive into Meanrom 3.5 you need to make sure you are on the latest firmware, kernel, and radio. If you are currently s-on on hboot 1.15 you will probably have problems after installing. Make sure you read all the posts in the Meanrom thread that have been posted since the ota came out before proceeding.
Sent from my icrap 2 using Tapatalk HD

Related

First Time Rom Flash

Hi all, I'm preparing to flash a ROM for the first time and decided to choose the Das Bamf remix 2.05 beta 6 that just barely came out. Now keep in mind I've -NEVER- flashed a ROM before so I've been reading ALOT trying to wrap my head around all this so I know for sure what I'm doing. I manually rooted the phone several weeks ago with ADB and the command sequences in a command terminal and now I want to mod it further.. so I took a look at the direction in the thread and I have a few questions and I'm sorry, I'm a nub,, so bear with me,... Copied from the thread...
Things to know:
A FULL WIPE IS HIGHLY RECOMMENDED!
What is the best way to do this?
Want a smooth camera? Overclock to 1.4ghz. This is the trick others are using to make the camera smooth in their rom
I understand you can use setCPU for this but others have said the Kernel seems to OC itsef a bit and not to use setcpu... which way is best to do this?
Rom Manager seems to cause corruption issues, flash the ROM manually via clockwork.
I did install Rom Manager and bought the premium version. Now I shouldn't be usign it? and I rooted so I have clockwork installed but not sure how I'm supposed to use it to manually with it.
I appreciate any and all help.. even a good link to how to manually flash with clockwork would be fine as well, I don't mind a little reading to get a better understanding! thanks!
seabhac said:
Hi all, I'm preparing to flash a ROM for the first time and decided to choose the Das Bamf remix 2.05 beta 6 that just barely came out. Now keep in mind I've -NEVER- flashed a ROM before so I've been reading ALOT trying to wrap my head around all this so I know for sure what I'm doing. I manually rooted the phone several weeks ago with ADB and the command sequences in a command terminal and now I want to mod it further.. so I took a look at the direction in the thread and I have a few questions and I'm sorry, I'm a nub,, so bear with me,... Copied from the thread...
Things to know:
A FULL WIPE IS HIGHLY RECOMMENDED!
What is the best way to do this?
Want a smooth camera? Overclock to 1.4ghz. This is the trick others are using to make the camera smooth in their rom
I understand you can use setCPU for this but others have said the Kernel seems to OC itsef a bit and not to use setcpu... which way is best to do this?
Rom Manager seems to cause corruption issues, flash the ROM manually via clockwork.
I did install Rom Manager and bought the premium version. Now I shouldn't be usign it? and I rooted so I have clockwork installed but not sure how I'm supposed to use it to manually with it.
I appreciate any and all help.. even a good link to how to manually flash with clockwork would be fine as well, I don't mind a little reading to get a better understanding! thanks!
Click to expand...
Click to collapse
Wipe in clockwork. factory reset/cache/dalvik cache to do a full wipe. the kernel, depending on which one it is, is slightly over clocked. also rom manager does cause problems when installing roms. download them on your pc, or browser via the phone, place on teh root of the sd card (not in a folder) and flash in clock work
seabhac said:
Hi all, I'm preparing to flash a ROM for the first time and decided to choose the Das Bamf remix 2.05 beta 6 that just barely came out. Now keep in mind I've -NEVER- flashed a ROM before so I've been reading ALOT trying to wrap my head around all this so I know for sure what I'm doing. I manually rooted the phone several weeks ago with ADB and the command sequences in a command terminal and now I want to mod it further.. so I took a look at the direction in the thread and I have a few questions and I'm sorry, I'm a nub,, so bear with me,... Copied from the thread...
Things to know:
A FULL WIPE IS HIGHLY RECOMMENDED!
What is the best way to do this?
Want a smooth camera? Overclock to 1.4ghz. This is the trick others are using to make the camera smooth in their rom
I understand you can use setCPU for this but others have said the Kernel seems to OC itsef a bit and not to use setcpu... which way is best to do this?
Rom Manager seems to cause corruption issues, flash the ROM manually via clockwork.
I did install Rom Manager and bought the premium version. Now I shouldn't be usign it? and I rooted so I have clockwork installed but not sure how I'm supposed to use it to manually with it.
I appreciate any and all help.. even a good link to how to manually flash with clockwork would be fine as well, I don't mind a little reading to get a better understanding! thanks!
Click to expand...
Click to collapse
Sounds like you read up on the topic. Thank you. My only advice is that the gb roms all have tiny little bugs in them. Read up and if you don't care go for it.
If you want a completely stable phone... Stick with a group Rom. If you want all the cool new features and don't mind working around a few bugs... Go gb. Also make.sure to use the correct radio. Probably the MR 2!
Good luck.
seabhac said:
Hi all, I'm preparing to flash a ROM for the first time and decided to choose the Das Bamf remix 2.05 beta 6 that just barely came out. Now keep in mind I've -NEVER- flashed a ROM before so I've been reading ALOT trying to wrap my head around all this so I know for sure what I'm doing. I manually rooted the phone several weeks ago with ADB and the command sequences in a command terminal and now I want to mod it further.. so I took a look at the direction in the thread and I have a few questions and I'm sorry, I'm a nub,, so bear with me,... Copied from the thread...
Things to know:
A FULL WIPE IS HIGHLY RECOMMENDED!
What is the best way to do this?
Want a smooth camera? Overclock to 1.4ghz. This is the trick others are using to make the camera smooth in their rom
I understand you can use setCPU for this but others have said the Kernel seems to OC itsef a bit and not to use setcpu... which way is best to do this?
Rom Manager seems to cause corruption issues, flash the ROM manually via clockwork.
I did install Rom Manager and bought the premium version. Now I shouldn't be usign it? and I rooted so I have clockwork installed but not sure how I'm supposed to use it to manually with it.
I appreciate any and all help.. even a good link to how to manually flash with clockwork would be fine as well, I don't mind a little reading to get a better understanding! thanks!
Click to expand...
Click to collapse
I only use ROM Manager to reboot into ClockworkMod Recovery. It is the second option when you open ROM Manager. My method of flashing a new ROM (performing a full wipe plus a few steps):
1. Reboot into ClockworkMod Recovery from ROM Manager.
2. Use Nandroid to backup your current configuration. Select backup and restore and then backup.
3. Select wipe data/factory reset. This will wipe all applications, contacts, text messages, bookmarks, etc. There are ways to back this information up (Titanium Backup for applications), but I will not go into full detail here.
4. Select wipe cache partition.
5. Select advanced and then wipe dalvik cache. (Most people recommend doing steps 4 and 5 three times in order to ensure it was done.)
6. Also in the advanced menu, select wipe battery stats. (You should do this when charged 100%, recommended for any new ROM flash.)
For some reason, if you flash in ROM Manager it can corrupt the ROM/flash. To avoid this, always use ClockworkMod Recovery.
If the ROM you flash utilizes one of Imoseyon's kernels (which BAMF does), you can use the speedtweak.sh method in terminal emulator (download from Market) descriped in Imoseyon's kernel thread. With a BAMF ROM, none of this is required. You can utilize the included BAMF Toolkit to overclock/underclock and set the governor. The Toolkit also includes a terminal emulator if you wish to try the speedtweak.sh method.
The above steps should be followed when flashing a new ROM. When upgrading versions of the same ROM, you can generally perform a minimal wipe. My understanding of a minimal wipe is the cache and dalvik cache only (three times).
Hope I didn't leave anything out. If so, others can correct me.
Thank you for describing this.. I watched several videos and read up alot but I don't want to mess up anything and do ti right.. I've got the BAMF remix 2.05 version 6 on my root directory on the SD card now and I'll wait till the phone is at full charge before running thr0ough this procedure. Thank you once more wool!
seabhac said:
Thank you for describing this.. I watched several videos and read up alot but I don't want to mess up anything and do ti right.. I've got the BAMF remix 2.05 version 6 on my root directory on the SD card now and I'll wait till the phone is at full charge before running thr0ough this procedure. Thank you once more wool!
Click to expand...
Click to collapse
You will also have to flash the MR2 radio. There is a thread in the Development Forum. If you search the thread, you should be able to come up with the method to do this.
http://forum.xda-developers.com/showthread.php?t=1115714
I flashed the ROM first, pulled the battery, and then booted in hboot (volume down plus power button). From there, hboot should find the radio and update. Most importantly, make sure the radio file you put on the root of your SD Card is named 'PG05IMG.zip' If you have Windows 7, make sure the .zip is not in there twice. By default, Windows 7 does not show file extensions.
to be safe with ur download make sure to check the md5
command in terminal and adb is
# /system/xbin/busybox md5sum /sdcard/so-so
i think.. lol
checking the md5 ensures ur download is legit.. i had a couple bad downloads causing bootloop.
Sent from my ADR6400L using XDA App
alluzzion2o9 said:
to be safe with ur download make sure to check the md5
command in terminal and adb is
# /system/xbin/busybox md5sum /sdcard/so-so
i think.. lol
checking the md5 ensures ur download is legit.. i had a couple bad downloads causing bootloop.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Easy way with the MD5 I found is to download AFV (Android File Verifier) from market. I download the ROM from xda app onto phone, run AFV on ROM from phone and verify MD5 while also having thread up on computer. Seems easier with those long numbers.

How to flash custom rom after rooting with CF-root

Hello, im new to androids and rooting, and i own a galaxy s2 which i have just rooted with Chainfires CF-root which also installed Clockwork mod recovery. I have a couple of questions on how to install custom roms, for example if i would like to flash villainrom, what are the exact steps i need to take? I have read as much as possible but im not sure if the same applies to custom roms in general.
So far im thinking i have to put the custom rom on my phones sd card and then flash it via clickwork mod, however i have read something about doing a nandroid backup and data wipe bdfore flashing the rom. Ideally i would hope somebody can do a quick step by step guide explaining the above, and tell me weather this applies to custom roms in general?
Im very grateful for any help, thx in advance
Once you have rooted your phone make sure you have enabled usb debugging.
Go to settings, applications, development, enable usb debugging.
Then connect phone to pc, and transfer rom.
Then boot into recovery mode, to do this switch phone off, then press vol up, home and power.
Then wipe data, wipe cache, go to advanced and wipe dalvik cache.
Then go to install zip from sd card, select zip, click ok and cwm will take care of the rest
Thx so much for the breakdown of how to do this, will this cause me to loose all data?
Baz-L said:
Thx so much for the breakdown of how to do this, will this cause me to loose all data?
Click to expand...
Click to collapse
Yes you will lose all data.
It's worth doing a backup, you can use titanium backup.
Download it from the market.
I don't tend to back things up, as contacts etc are synced and backed up with my google account.
And I just redownload my apps.
You'll find some roms don't wipe data, but it's generally advisable to always wipe before flashing any rom, and therefore backup if you have a lot of data.
JGS2 said:
Yes you will lose all data.
It's worth doing a backup, you can use titanium backup.
Download it from the market.
I don't tend to back things up, as contacts etc are synced and backed up with my google account.
And I just redownload my apps.
You'll find some roms don't wipe data, but it's generally advisable to always wipe before flashing any rom, and therefore backup if you have a lot of data.
Click to expand...
Click to collapse
Ok so its basicaly that same process when flashing any custom rom? just needed it step by step, thx for the tip on titanium bu, and thx again for ur help, much appreciated;-)
Baz-L said:
Ok so its basicaly that same process when flashing any custom rom? just needed it step by step, thx for the tip on titanium bu, and thx again for ur help, much appreciated;-)
Click to expand...
Click to collapse
Yeah pretty much the same for every rom.
It's always worth reading the first post in every thread though, as I came across a rom recently that could only be flashed using odin, I think it was litening rom.
But if not 99% of custom roms can be done the way I described
And I know what you mean about needing things step by step, these forums seem very complicated at first, the best advice I can give you is to read read read.
When I first joined earlier this month everything seemed so complicated but it's fairly straight forward when you get used to it.
I now flash about ten times a day, but I have a problem lol
JGS2 said:
Yeah pretty much the same for every rom.
It's always worth reading the first post in every thread though, as I came across a rom recently that could only be flashed using odin, I think it was litening rom.
But if not 99% of custom roms can be done the way I described
And I know what you mean about needing things step by step, these forums seem very complicated at first, the best advice I can give you is to read read read.
When I first joined earlier this month everything seemed so complicated but it's fairly straight forward when you get used to it.
I now flash about ten times a day, but I have a problem lol
Click to expand...
Click to collapse
Sorry for the delayed reply, lol jeez 10 times a day, i get how it can be so fun and addictive though, trying custom roms and themes etc.
As i said though im new to android, came from an iphone 4 which i always used to jailbreak.
And yeah i know what you mean, im doing my best to read as much as i can, but here on xda things move so fast and theres that many different things to learn it gets scary hehe.
Im still to try and flash a rom, i was going to try villainrom first, but do you have any other suggestions on which devs/roms i should check out, seeing as all this is new i might aswell get some practice in....
I do have another quick question, when i connect my fone via usb, which folder do i put the zip rom file into, is it External SD?
Anyways thanks again for your help, really appreciated!
EDIT* got it sorted!
Yeah ten times a day isn't an exaggeration either lol
I find what happens is I flash a rom, then a dev releases an update for another rom then I flash that, then I flash a different modem, then I find another rom, then another update and the cycle continues
You said you sorted it, but the rom zip file just goes in the root of your internal memory.
It's not overly important as you can find the file through cwm anyway.
As sometimes I'll download a rom through my browser and then it goes to the downloads folder.
But if I download it on my pc, I will just transfer the file to the root of my internal memory on my phone.
JGS2 said:
Yeah ten times a day isn't an exaggeration either lol
I find what happens is I flash a rom, then a dev releases an update for another rom then I flash that, then I flash a different modem, then I find another rom, then another update and the cycle continues
You said you sorted it, but the rom zip file just goes in the root of your internal memory.
It's not overly important as you can find the file through cwm anyway.
As sometimes I'll download a rom through my browser and then it goes to the downloads folder.
But if I download it on my pc, I will just transfer the file to the root of my internal memory on my phone.
Click to expand...
Click to collapse
Yeah thanks again i managed to get it sorted i guess i overthink things sometimes, but i followed your guide above and now im running villainrom
had to do a bit more reading/asking on the backup/restore front, knowing what the diff between nandroid/titanium is etc, and how and which to use to restore.
Also you mentioned above about backing up your contacts with google, i tried to do that but couldnt seem to, how did you manage it? as i cant restore contacts from my windows pc via kies right? now that im rooted with a custom rom.
Anyways thx again for the help pal, you've been awesome!

[Q] Is my device bricked?

Here's what's happenning.
- Device was rooted using HTC unlock method with HB00t 1.5
- Was running Synergy Rom
- Wanted to get latest OTA from Sprint so I followed the steps from another thread :
http://forum.xda-developers.com/showthread.php?t=1447839&page=2- Went through steps and unlocked my device again
Used file from post #16
- Did my updates, unlocked device, booted back into HBoot
- Decided I would try the Infected Eternity Rom this time so I followed those steps as stated in their thread. Did a clean flash. Flashed Superwipe, flashed data ext optimizer tool, flashed eternity rom w/ 3.5 sense
- after message said installation was complete, i got error message when i went back to main menu in recovery:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lastçlog
E:Can't open /cache/recovery/last_log
- device wouldn't boot once I rebooted from CWM. It would hang a the HTC white screen, then reboot again, keeps repeatedly doing this.
- Then I rebooted back in HBoot by pressing Vol Down and Power buttons. Went to recovery, flashed Synergy rom. Install was fine, still can't boot up device. Having the same issue. Device would hang at HTC white screen and continue to cycle on and off trying to reboot.
- Rebooted back to HBoot by pressing Vol Down and Power buttons. Went into recovery with CWM, restored my back up. Everything went fine except I got message:
sd-ext.img not found. Skipping restore /sd-ext.
As of right now, I can still boot into HBoot. I've tried reflashing Synergy rom again, but still nothing.
From my search, it says that based on my error message:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/lastçlog
E:Can't open /cache/recovery/last_log
It could be a HW or SW issue.
Phone is still under HTC warranty, if I need to return it, what do you say to support department?
Thank you.
Have you tried flashing through fast boot through a usb connection? I know the h boot 1.5 are tough to do when you need to change kernals which is what happens when you got to a 3.5 Rom. I had some trouble too if you open recovery through fast boot and do everything that way all should be good.
Edit: as long as you can get into recovery I think you'll be okay.
I can definitely still get into recovery and HBoot. So I would assume those are good things.
Read another thread suggesting to use TWRP instead of CWM.
Will try both flashing with fastboot from usb and twrp and see if that helps.....
If anyone else have other suggestions,
fastbook using android sdk...
it's never bricked unless it won't turn on.
next time, don't try to fix it if it aint broken.
Unlocking via htc will require you to follow the following. The kernel can't be written unless you follow the directions below which can cause the issue you stated.
http://forum.xda-developers.com/showthread.php?t=1239821
Just let us know what happens it is most likely just a kernal problem. Look up how to do the fast boot to make sure it works right. Fingers crossed.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I had an error like that once before. I believe I had to format my sd card. I also formatted my sd-ext partition. Hopefully you have a backup of your sd card so you can try doing that. Of course you'd need to take your sd card out, and use a card reader to format it using your computer.
Sent from my HTC Evo 3D using Tapatalk
That's not a brick a brick is where you can't even get into hboot tho if your slick enough you could still fix a bricked phone lol
cobraboy85 said:
next time, don't try to fix it if it aint broken.
Click to expand...
Click to collapse
Actually, the reason for wanting to switch over to a different ROM was because with the Synergy rom, I was getting random reboots. Sometimes as much as 3 times a day. Other times, once or twice a week only. It seemed to be an issue that was never really addressed as it's still being asked in their thread now a days. So wanted to see if the Eternity Rom was more stable.
Back to the OP, just wanted to be clear that when I refer to rebooting back into recovery, I am not simply booting into HBoot and then selecting the "recovery" option on the menu. I am aware that I cannot use this method as I have Hboot 1.5. I am using a CMD window to fastboot the recovery program (either TWRP and CWM).
In my cmd window, I change into the propper directory with all my files. Then use commands:
adb reboot bootloader
fastboot boot recovery.img (used: fastboot flash recovery "FILE" to flash onto device)
And then I flash the zip files from there on.
In any matter, was able to get Synergy up and running again. For some reason, I couldn't get it working with CWM but was able to do so with TWRP.
Still getting the occasional random reboot. Have had it up and running for a day now and already one random reboot just a couple hours ago.
Still can't get Eternity w/3.5 Sense running though. So I have a quick question in regards to that. In following the steps on their thread:
http://forum.xda-developers.com/showthread.php?t=1277431
step 5 indicates that I need to copy over the boot.img file once I extract the rom.zip file to the same folder I used to unlock. However, I found two boot.img files under the Kernel folder. Which one do I use? Actually tried both and both gave me the same results (hangs at the HTC white screen and cycles on/off).
Note: the boot.img were found under sub folders "Shooter" and "Shooteru" in the kernel folder.
kyaj9 said:
Actually, the reason for wanting to switch over to a different ROM was because with the Synergy rom, I was getting random reboots. Sometimes as much as 3 times a day. Other times, once or twice a week only. It seemed to be an issue that was never really addressed as it's still being asked in their thread now a days. So wanted to see if the Eternity Rom was more stable.
Back to the OP, just wanted to be clear that when I refer to rebooting back into recovery, I am not simply booting into HBoot and then selecting the "recovery" option on the menu. I am aware that I cannot use this method as I have Hboot 1.5. I am using a CMD window to fastboot the recovery program (either TWRP and CWM).
In my cmd window, I change into the propper directory with all my files. Then use commands:
adb reboot bootloader
fastboot boot recovery.img (used: fastboot flash recovery "FILE" to flash onto device)
And then I flash the zip files from there on.
In any matter, was able to get Synergy up and running again. For some reason, I couldn't get it working with CWM but was able to do so with TWRP.
Still getting the occasional random reboot. Have had it up and running for a day now and already one random reboot just a couple hours ago.
Still can't get Eternity w/3.5 Sense running though. So I have a quick question in regards to that. In following the steps on their thread:
http://forum.xda-developers.com/showthread.php?t=1277431
step 5 indicates that I need to copy over the boot.img file once I extract the rom.zip file to the same folder I used to unlock. However, I found two boot.img files under the Kernel folder. Which one do I use? Actually tried both and both gave me the same results (hangs at the HTC white screen and cycles on/off).
Note: the boot.img were found under sub folders "Shooter" and "Shooteru" in the kernel folder.
Click to expand...
Click to collapse
gotcha. and is it eternity 3.0?
I have been running 1.4.2 with absolutely no issues now for 4 weeks. running Chad's RLS09 kernel that was pulled at the beginning of this month
you should give that set up a shot man. most reliable rom in my opinion.
k2buckley said:
I had an error like that once before. I believe I had to format my sd card. I also formatted my sd-ext partition. Hopefully you have a backup of your sd card so you can try doing that. Of course you'd need to take your sd card out, and use a card reader to format it using your computer.
Sent from my HTC Evo 3D using Tapatalk
Click to expand...
Click to collapse
The only back ups I have when I first rooted the device.
As long as formatting the SD card doesn't mean I am losing anything vital to the operation of the device, I would have no issues with having to put everything back on manually.
cobraboy85 said:
gotcha. and is it eternity 3.0?
I have been running 1.4.2 with absolutely no issues now for 4 weeks. running Chad's RLS09 kernel that was pulled at the beginning of this month
Click to expand...
Click to collapse
No it's the 3.5. I wanted to try the one with Sense 3.5.
For the good news!!! Finally got it to work. Backing up my apps with Ti Back up as I am writing this.
The only difference I did this time around was that after flashing Superwipe, I DID NOT flash the optimizer tool.
In all my other attempts, whether with TWRP or CWM, I was also flashing the optimizer after flashing Superwipe. Don't know if that was the actual cause or not with the install, but that was the ONLY step I did not do this time around.
From what I read, the optimizer is suppose to make the rom run faster because of the ext 4 partition. So my question now that I have up and running is will NOT having it flashed have any significant results?
On another thought, I did flash the optimzer as needed when I re-flashed Synergy. Does this carry over to the new rom or was I suppose to do again also for Eternity?
In any matter, thank you to all who helped. I will run Eternity for a week or so and see how stable it is first before trying anything else.
EDITED NOTE: Perhaps it should also be noted that I did download the latest build of Eternity also beforing getting it flashed and finally getting it running. Build 180. The file I couldn't get running was build 155.
OK...less than an hour into the rom and already experiencing some issues. It could be my flashing...but anyways.
When I try to run apps that require SU, it's saying that I the device is not rooted.
Could this simply be a case of a bad flash or am I missing something? Again, this is only apps that generally, would ask for super user permission. All other apps (games, etc) works fine.
Also, I do have the SU app updated to the latest version and it's visible in the APPS drawer.
To be specific, when I run the Adfree Android app, I get: "Fatal Error: Unable to get root"
Also, when I run MSL Reader, I get error: Couldn't find the superuser binary in any known path. Are you sure you are rooted?
kyaj9 said:
OK...less than an hour into the rom and already experiencing some issues. It could be my flashing...but anyways.
When I try to run apps that require SU, it's saying that I the device is not rooted.
Could this simply be a case of a bad flash or am I missing something? Again, this is only apps that generally, would ask for super user permission. All other apps (games, etc) works fine.
Also, I do have the SU app updated to the latest version and it's visible in the APPS drawer.
To be specific, when I run the Adfree Android app, I get: "Fatal Error: Unable to get root"
Also, when I run MSL Reader, I get error: Couldn't find the superuser binary in any known path. Are you sure you are rooted?
Click to expand...
Click to collapse
k I'm gonna help you out a little bit here...
re-download rom.
before you flash, wipe data twice, and cache twice.
under recovery settings, format system.
flash superwipe.
flash rom.
don't use titanium backup.
don't use ext4 data optimization tool.
you still have problems after that, then use a different rom.
and if you get the SU error, reboot to recovery and under advanced options or whatever, select "fix permissions"
It seems like you have a partitition issue on your internal or external memory in your case i think your internal memory is having trouble try black rose and associated partition tool to fix your partition schema
cobraboy85 said:
k I'm gonna help you out a little bit here...
re-download rom.
before you flash, wipe data twice, and cache twice.
under recovery settings, format system.
flash superwipe.
flash rom.
don't use titanium backup.
don't use ext4 data optimization tool.
you still have problems after that, then use a different rom.
Click to expand...
Click to collapse
cobraboy85 said:
and if you get the SU error, reboot to recovery and under advanced options or whatever, select "fix permissions"
Click to expand...
Click to collapse
Making sure I wiped out everything was the first priority I took. I did re-download the rom just to be sure it was a good download also.
Can't seem to get 3.5 version working propperly, but I did get 3.0 version up and running. Have had it for a couple days now with no issues so just gonna stick with that. Wanted to try out the sense 3.5 first, but the fact that there's no 4g support for it yet means I am probably better off with just using the 3.0 Sense.
Thanks for your help....
mahmutmuratdemir said:
It seems like you have a partitition issue on your internal or external memory in your case i think your internal memory is having trouble try black rose and associated partition tool to fix your partition schema
Click to expand...
Click to collapse
Not familar with Black Rose....but if I am not mistaken, isn't that just a HBoot for the Nexus 1?
yes it is made for nexus one to flash higher andrid versions but i think it can be used in some other models for partitioning internal memory
Sent from my Nexus One using XDA App

[GUIDE][ROM FLASHING][WALK THRU] Easy to do! All Questions Welcome!

This will help anyone who keeps having flashing issues.
More detailed instructions in my GUIDE!
http://forum.xda-developers.com/showthread.php?t=2295557
THIS IS ONE QUICK/SIMPLE ERROR FREE ROM FLASHING PROCEDURE
This should eliminate a few posts saying, stuck in download mode, stuck at logo. just vibrates and them MANY other issues that somehow, everyone seems to find.
Here is my quick rom flashing process I use ALWAYS (yes always)
THINGS YOU NEED ON extSDCARD
1. Extra kernels (2 or 3 you know works for your device)
2. Optional: 2 recoveries that can be flashed (I use CWM & TWRP)
3. Optional: apps.zip (a zip created from Titantium BU, containing Root Explorer, TU Backup, Quickpic, ES File Explorer and Terminal Emulator)
Flashing the rom: TOUCHWIZ/AOSP ROMS
1. Backup current rom (to the extsdcard)
2. Complete wipe, (I do complete, some people do not) Complete = No Issues [FACTORY RESET + CLEAR CACHE + CLEAR DALVIK CACHE + CLEAR DATA]
3. Flash the rom
4. Flash the kernel (your device kernel) (I know some roms have their own kernel) this is where your problems start.
AGAIN: FLASH YOUR KERNEL, you KNOW it works. 1 more time FLASH YOUR KERNEL. (you can experiment with other kernels after you boot)
AOSP ROMS - require you to flash gapps before you boot. [This is not required for TouchWiz roms]
5. Boot the rom.
FINISHED!!!! SUCCESS!!!
Total time to flash a rom:
7-10min
Errors - NONE
This goes for every rom in my guide.
TIPS:
This flash procedure is for Touchwiz Roms, if you are flashing AOSP roms, you must flash the gapps package associated with the rom you are flashing.
**** SGH-I337M Users: Often requires flashing a different kernel than the one included in most ATT ROMS. Any GT-i9505 kernel will work and Adam kernel and Faux kernel are both confirmed working for us Canadian users.
Note: Flash KERNEL directly after ROM then reboot device.
[Special thanks to blyndfyre for this helpful tip].
The extra recovery I flash if a rom does not like the recovery I am using.
Yes, you can flash recoveries back and forth.
Apps.zip I flash after the rom is up & running. This I use to get the rom setup (like root explorer and others needed)
I am in no way responsible for anything that may do damage to any device - Use these tips at your own risk - period!
If you found this useful in any way, please hit the THANKS button for my effort.
RESERVED
TheAxman said:
Any questions? Anyone.
Click to expand...
Click to collapse
I've been running into a lot of issues when trying to flash different ROMs. For instance, right now I'm on CleanROM 1.6 - I just tried to install PureGv2.
Steps I took:
Have Goo and ROM Manager installed after clean install of CleanROM 1.6
Flash CWM from ROM Manager
Install Recovery Script from Goo
Reboot into recover from Goo
TWRP loads
Wipe data, cache, dalvik, etc
Install PureGv2
I forget the error off the top of my head but it doesn't install
In a nutshell I'm asking what am I doing wrong? Do I need to flash another kernel?
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
TheAxman said:
Flash your verizon kernel. Correct. I know it is a vzn rom, but do it anyway.
Click to expand...
Click to collapse
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
harrytery said:
Was looking through Tomsgt's Youtube channel and stumbled across a video of his that showed his "About Phone". Everything was identical to mine, so I'm still a little lost as to why I can flash certain ROMs but not others. Sac/Gru's ROM soft bricked my phone, Hyperdrive5.7 didn't install, CleanROM does. It's just funky...maybe I'll just Odin back to stock, flash the MDK and start fresh.
Could the downloads be a problem? I downloaded 2 of the ROMs from work today on a 50meg pipe and they didn't work.
Do you download the ROMs to your phone or to your computer and then move them to your SD card?
If you download to your phone, do you move them to the SD card or leave them in the download folder on the internal storage?
If you do the latter, do you use a micro SD adapter or plug the phone in and move them that way?
Click to expand...
Click to collapse
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
TheAxman said:
Download to the computer,then copy to the phones extsdcard, should be ok, make sure you do a md5 check on the files to make sure they are the correct size.
Click to expand...
Click to collapse
Alright sounds good. Flashing back to stock later today then re-rooting
thanks for the help
Remember always do a BACKUP before you do anything.
First off, big thanks for this thread.
Now I'm running Cleanrom 1.5. If I wanted to install a new rom can someone please explain exactly what I do to go about it? As jargon free as possible would be awesome.
Sent from my SCH-I545
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Vampyre111 said:
I certainly scared the carp outta me the other night. I'm using the Carbon ROM and while I do like it, I miss a couple of the S4s features. I picked what looked like a good modified stock ROM and proceeded to flash it.
I'm using Goo and TWRP for the job. I checked of all 3 boxes for clearing cache, davik and factory reset.
Then I chose the file and started it.
The first result, it acted like if was doing everything but nothing changed. Phone still worked fine.
On the next try, I waited for TWERP to start and I reselected the ROM I wanted and flashed it.
When it booted up, I was very happy to see the original screens come up. Then it stopped on the one with the Verizon check mark. The blue LED slowly pulsing and nothing else for about 30 min. I removed battery to try and start over. Same thing again.
Time to goto my backup and restore my phone back to Carbon.
IT FAILED.
Now my phone is stuck in a weird looking boot up loop. After a few tries I was able to get into recovery
mode. TWRP started loading, froze and crashed! Even though I am a total noob at this, I still did not panic.
I'd restart my phone by removing the battery, going into recovery mode and then wildly press every button on my phone hoping to break the loop. It worked! I chose a different save and tried it all over again. FAIL.
ON the next I wiped every bit of old data off. Chose Factory restore crossed my fiingers....it work! My phone is fine now.
Thanks to that ordeal and this thread I think I know what I did wrong even though this never happened to me. before.
1) WIPE THE DATA
2)INSTALL A COMPATABLE KERNAL FIRST
V^^^^V
Click to expand...
Click to collapse
I can not stress enough HOW IMPORTANT THE KERNEL IS!
Hmm so everyone is a now a Oriental Flash Master from the far East now huh?
What recovery is everyone using?
[updated: 07-12-2013]
Flashing Questions
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
xander45 said:
So, if you just need to add something, like different Kernerl, do you have to wipe and start from scratch?
Should you.
If so, and you backup apps and data in Titanium, then what you do a full wipe, flash entire rom, and reinstall the apps and data associated therewith?
Last, I have asked this but cannot seem to get an answer.
Installed Hyperdrive 7 (also had 5.7 and 6). Rom is super smooth and fast, working like a charm. but I want Verizon Visual Voice Mail.
I tried to copy the apk file to the devices system/app directory but get permission denied message....tried to install, and get failed message....
Click to expand...
Click to collapse
did you set the permissions for the app? That should work actually. Look at one of the apps in that directory, and set the permissions the same for the voice app. Reboot and see what happens.
Good luck.
May want to post this question also in my guide thread.
http://forum.xda-developers.com/showthread.php?t=2295557
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Painterface said:
Sorry if this is dumb, but how do I know what kernels for sure work with my device and how do I get them to my external sd card? I suppose the one that is currently on my device(how to get that to sd?), but what others?
Thanks.
Click to expand...
Click to collapse
Please bring the question over to my thread up above. It shows also what kernels to use. We will help there.
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
theoneknownasbob said:
Another noob question: so you still advise flashing a kernel even if the ROM creator says that the ROM comes with the appropriate kernel and that no extra flashing is required? I've got the Verizon Galaxy S4 variant and specifically am thinking of Dubbsy's Google Play Edition ROM.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
You would flash the rom, and after, flash your verizon kernel, simple as that.

Cant flash some roms

Let me start off by saying Im far from new to the rooting and roming game. Been through several phones. Never run into this issue.
Note 2 - i605
Team Win Recovery - Up to date
Clockwork Recovery - Up to date
MJ9 Radio from Zif
I am able to install CleanROM and Sophisticated. But when I attempt to install CM11, MeanBean, or Gummy the install fails. It attempts to unzip but always ends with failed. This occurs on both recoveries. I have even tried an alternative recovery. Nothing seems to get it done. Please someone help. Like to note I checked my external SD card for errors. It passed.
Sent from my SCH-I605 using XDA Premium 4 mobile app
General consensus seems to be that philz recovery is currently the recovery of choice for 4.3, id say give that a try
Note2.5
This same thing happened to me. I couldn't even install backups I had. I finally gave up, ODIN'd back to stock and reran casual, everything has been fine since. Even re-installing the same exact recovery.
Jiggabitties said:
This same thing happened to me. I couldn't even install backups I had. I finally gave up, ODIN'd back to stock and reran casual, everything has been fine since. Even re-installing the same exact recovery.
Click to expand...
Click to collapse
Im going to give that a shot. I think it may actually be the thing that sorts this all out. Not hat Phillz is not a good option. But that's the other recovery I already tried. Thinking that maybe the Casual I did was not smooth. As it did hang a couple times and was not as smooth as I would have liked. I am going to reply back when I do it to let everyone know how it turned out. Just in case someone else has the same issues.
:good:
So I odin stocked the phone. Perform casual. Much smoother this time. But still no dice. Still able to install only some roms.
Installable:
Sophisticated
CleanROM
Unable to Install:
CM 11
MeanBean ICE
MeanBean Reborn
Gummy
:crying:
Crotty.Josh said:
So I odin stocked the phone. Perform casual. Much smoother this time. But still no dice. Still able to install only some roms.
Installable:
Sophisticated
CleanROM
Unable to Install:
CM 11
MeanBean ICE
MeanBean Reborn
Gummy
:crying:
Click to expand...
Click to collapse
Hmmmm. Somewhere there's a step that's failing you (obviously). Maybe break down your process, from download to flash, and try to pinpoint where it's going wrong. In my experience the things that have caused an install to fail have been either an incompatible or outdated recovery, bad download (check the MD5), or borked system partition (which is when I Odin'd and re-casualed).
Had issues with CM11 until I ODIN'd back to stock LJB, unlocked bootloader/rooted, updated to latest TWRP 2.6.3.1 via ODIN, wiped all partitions included cache, data, dalvik, system, internal sdcard, external sdcard then adb push CM11 plus gapps and installed. Just make sure you can adb push before wiping everything along with checking file CRC and temporarily disable antivirus.
So I the issue ended up being one of an interesting nature but not normal. When I download thw rom of choice to my phone I move it to my SD card. Making sure its out of the distruction path. As is normal practice. I am using Rom Toolbox root browser to make the move. Turns out that although it gave the impression it was moving the files, it did not always do so. So each time I copy a file from place to another I have to check that it was done in full and without flaws. Quite an interesting problem. As a move of that sort should not break files.
Crotty.Josh said:
So I the issue ended up being one of an interesting nature but not normal. When I download thw rom of choice to my phone I move it to my SD card. Making sure its out of the distruction path. As is normal practice. I am using Rom Toolbox root browser to make the move. Turns out that although it gave the impression it was moving the files, it did not always do so. So each time I copy a file from place to another I have to check that it was done in full and without flaws. Quite an interesting problem. As a move of that sort should not break files.
Click to expand...
Click to collapse
It's always something small it seems. Good practice is to download the ROM, get it to it's final destination then check the MD5. I always wait until I've moved it to the SD to check the MD5 just in case there was a bad transfer.

Categories

Resources