Hi guys,
I've done a fair share of searching but it seems nobody is having the same issues
Basically, I thought i'd try out these new tweaks I found, the V6 Supercharger and the 3G Turbocharger from zeppelinrox - The V6 installed fine and was running smoothly but when i installed the faster version of the 3G turbocharger sent my phone into a bootloop (it eventually came back on to my relief). My HTC Wildfire is now thrown into a bootloop every time i enable mobile data. WIFI works fine.
I have reflashed my ROM, wiped data and dalvik cache, but when i flash the G_apps, the phone goes into the boot loop - and thats after a full wipe and reboot (i have now restored a backup - but the issue is still apparant)
Another thing worth mentioning is my local.prop file is empty and i'm not sure if this should contain any script.
Any help appreciated. Phone Spec below.
Thanks
Phone Model: HTC Wildfire Buzz
Android Version : 2.3.7
Rom: Cyangoen Mod-7.1.0.1-Buzz
Kernal: 2.6.35.14-nFinity [email protected] #1
Radio: 3.35.15.31
Baseband: 13.45.55.24U_3.35.15.31
Hboot: 6.01.1002
S-OFF
V6 Supercharger - Unsupercharged
3G Turbo Charger - Uncharged
This was caused by the 3G / V6 Script:
http://forum.xda-developers.com/showthread.php?t=1015532&page=200
Read Post #1998 onwards (The next 2 Pages as well). You have to clean wipe and install another ROM (Not restoring anything from your existing setup), and if it still doesn't work, use an RUU to go back to the Stock ROM and then come back to whichever ROM you are using.
Fix for bootloop after 3g turbocharger script install
FIX:
Ran an RUU for wildfire.
- Downloaded (RUU_Buzz_HTC_WWE_1.14.405.2_R_C_Radio_13.45.55.24_ 3.35.15.19_release_141106_signed) from android forums.
- Connected phone to PC and ran RUU
- This downgraded phone OS to eclair (android 2.1)
- Let it do the bizniss
- Had to re-root with unrevoked 3
- Re-Flashed CM7 and gApps
All ok
I'll say one thing, CM7 doesnt need a v6 or a 3G super/turbocharger. It works fine without them. The minfree values are set at an ok level and I always have HSDPA signal. Its not worth the effort.
Yeah after carefully tweaking this and that - all one change after the other and testing a lot before going on - I've been pretty much satisfied with my old buzz. Until I decided to give that 3G Supercharger a try (because of 3G didn't ever work really good - the only thing I was not completely satisfied with)...
It turned out that there hasn't been any improvement from my perspective so I just reverted the settings and went on.
It took me 2 weeks to find out where the bootloops suddenly came from (1 day to narrow down the prob had to do with switching on data and at least 10 days for the 2g/3g part).
Is there anybody who can explain more specific a) what causes this behaviour and b) what would be necessary to eliminate the cause (and probably avoid it in the future)
I won't get misunderstood but just "do an RUU update" sounds a bit like the standard no.1 suggestion "format and re-install" in all those amateur winsucks forums...
3xeno said:
This was caused by the 3G / V6 Script:
http://forum.xda-developers.com/showthread.php?t=1015532&page=200
Read Post #1998 onwards (The next 2 Pages as well). You have to clean wipe and install another ROM (Not restoring anything from your existing setup), and if it still doesn't work, use an RUU to go back to the Stock ROM and then come back to whichever ROM you are using.
Click to expand...
Click to collapse
Thanks for the hint but even after reading all the related posts several times I don't feel enlighted somehow (besides the information that I don't need any super charge scripts with CM - which I'm half the way to be convinced of )
noone? I just want to find out what exactly is the problem (to avoid it in the future) and I'm really curious why a complete wipe doesn't help. The Supercharger scripts just tweak values in config files (correct me if I'm wrong) - so if the problem is caused by the script(s): why can't it be solved by simply revert those changes (or replace the files by the default ones)?
Fix for bootloop after 3g turbocharger script install
eventcom
Did you find anything more about this problem?
I have the boot loop after using 3g/4g optimizer from the market, but I can get partial network use if I enable only 2g and not 3g. Better than nothing while I see if it can be fixed without a RUU.
Just wondering if a RADIO flash may solve the problem.
Regards.
Phone Model: HTC Wildfire Buzz
Android Version : 2.2.1
Rom: Stock
Kernel: [email protected] #1
Radio: 3.35.20.10
Baseband: 13.55.55.24U_3.35.20.10
Hboot: 6.01.1002
S-OFF
st3v3droid said:
Did you find anything more about this problem?
Click to expand...
Click to collapse
nope unfortunately not, but it seems, that the problem still occurs - see in this thread or here in that one - I've given it another try to flash radio again - with no help. The information about changed values in build.prop isn't new to me (as I did expect something like that) - what I don't know is which values exactly and how to overwrite them (if too many) when flashing a new rom...
So I went a bit deeper into the build.prop and made a simple diff against the build.prop of October 2011 (has been an earlier nightly and that problem definitely didn't occur at that time).
The only differences were those:
This looks like a simple addition for identification
Code:
+++ ro.cm.device=buzz
Perhaps that's a better guess (looks like this had been added sort of randomly anyway? - qualifies):
Code:
+++ # For PDP overlap problem
+++ ro.ril.avoid.pdp.overlap=1
That shouldn't harm anything:
Code:
+++ # update the acoustic table for Buzz NEL lab testing
+++ ro.ril.update.acoustic.table=1
My own changes which didn't cause any trouble before:
Code:
--- dalvik.vm.heapsize=24m
+++ dalvik.vm.heapsize=32m
+++ ro.compcache.default=0
That shouldn't have to do with the problem, too:
Code:
+++ persist.sys.rotationanimation=false
+++ persist.sys.scrollingcache=2
but that one probably?:
Code:
+++ # Lock dirty_ratio to 20 when USB is mounted for improved transfer speed
+++ ro.vold.umsdirtyratio=20
So I simply commented out the stuff I guessed to be responsible (no. 2 and 6) and restarted - no success. Reboots again when turning on 3G
I get the same problem, Had CM7 running fine with no problems but started to get bootloops upon upgrading to CM9.
Found a temp fix by reflashing radio but the problem seems to come back sporadically using any cm mod (haven't tried stock yet)
Any ideas?
Doddster said:
I get the same problem, Had CM7 running fine with no problems but started to get bootloops upon upgrading to CM9.
Found a temp fix by reflashing radio but the problem seems to come back sporadically using any cm mod (haven't tried stock yet)
Any ideas?
Click to expand...
Click to collapse
that sounds exactly like LucidSomnia's report in the thread I've used to continue with my experiences. I can't tell if my solution (if it was any and not by accident) will help you but it shouldn't hurt to give it a try...
Tried pretty much everything, flashed several different versions of Buzz Radio, tried factory resets, data wipes.
I would guess it as a kernel or firmware error and it *must* be fixable, just like the camera.
P.S The camera works occasionally, I get viewfinder but no way of taking picture and if I install the 3rd party app Line camera I can take pictures with no viewfinder.
Doddster said:
Tried pretty much everything, flashed several different versions of Buzz Radio, tried factory resets, data wipes.
I would guess it as a kernel or firmware error and it *must* be fixable, just like the camera.
Click to expand...
Click to collapse
As you can see in my posts (in three threads) I've done a lot of stuff, too, what did the trick in the end (if it was not just by accident) was
Total/full/mega wipe (except SD card)
mounts & storage / boot, cache, system, data, sd-ext
advanced / dalvik-cache
main menu / wipe all (factory reset)
flash a fresh ROM
flash a different radio (older one in my case)
Boot
after that just the same procedure
mounts & storage / boot, cache, system, data, sd-ext
advanced / dalvik-cache
main menu / wipe all (factory reset)
flash a fresh ROM
flash a different radio (newest in my case)
It might be possible, that it would have worked to just flash the older radio / wipe caches / boot / flash the newer radio - no idea, but the actions in the exact order above have been successful for me (after trying a lot of things).
But just to make sure (because you're talking about CM9 I guess): my problem has been that the phone did bootloops every time and immediately when I turned on 3G data. No exceptions, nothing occasionally or random. With different Versions of CM7 (older nightly, RC, stable and newer nightly). And just 3G. Everything else did work like a charm.
If that's the case with you I'd give my method a try and if that doesn't work I'd do an RUU (the safe flash variant first of course).
eventcom said:
It might be possible, that it would have worked to just flash the older radio / wipe caches / boot / flash the newer radio - no idea, but the actions in the exact order above have been successful for me (after trying a lot of things).
But just to make sure (because you're talking about CM9 I guess): my problem has been that the phone did bootloops every time and immediately when I turned on 3G data. No exceptions, nothing occasionally or random. With different Versions of CM7 (older nightly, RC, stable and newer nightly). And just 3G. Everything else did work like a charm.
Click to expand...
Click to collapse
Yes mate! So far so good! No bootloop when enabling mobile data, even after reboots (with mobile data left on)
Steps followed:
(In recovery)
Wipe Cache,
Factory Reset.
Flashed CM7
Flashed Radio (3.35.19.25) using CMrecovery 2.5.0.7
Thanks eventcom
**Dunno if I'm gonna have the balls to install CM9 again after all this
Doddster said:
Yes mate! So far so good! No bootloop when enabling mobile data, even after reboots (with mobile data left on)
Click to expand...
Click to collapse
glad to hear that it helped
**Dunno if I'm gonna have the balls to install CM9 again after all this
Click to expand...
Click to collapse
I'm not really sure about what exactly caused the problem (at my side at least) - but even if CM9 on the Wildfire is highly experimental this particular problem doesn't look to me that it has to do with the ROM. I slightly remember a few people having this problem after flashing a different ROM but in most cases this could be solved by a simple restore. Did you also use some tweaks - like a different kernel, RAM scripts or something similar?
nope, nothing different from what was included on the CM7 and CM9 builds. :/
It's frustrating as ICS actually runs ok on the wildfire, it's only till it hits the radio or camera hurdles it lets itself down lol
I'm getting another phone soon so I will be using my Wildfire for development and I'll put all my effort into helping us wildfire'ers run ICS with no hassle.
Im gonna stick my neck out here, all the incidents ive come across regarding the issues raised have involved one, some or all 3 aspects
1.overclocking too high.
2. V6 supercharger scripts.
3. Cm9
Could be coincidence or could be the reason!
Forum fishing.... Who's biting!
CM9 in my case, it's defo something to do with the radio.
I have no probs running max clock on CPU and I haven't touched other scripts
Doddster said:
CM9 in my case, it's defo something to do with the radio.
I have no probs running max clock on CPU and I haven't touched other scripts
Click to expand...
Click to collapse
Have you ever had the problem with the radio outside of cm9?
Ive never tried cm9 nor had issue with any of my radios but have had bootloops when i tried the v6 scripts back in my early days.
Forum fishing.... Who's biting!
slymobi said:
all the incidents ive come across regarding the issues raised have involved one, some or all 3 aspects
1.overclocking too high.
2. V6 supercharger scripts.
3. Cm9
Click to expand...
Click to collapse
Yes, on the other hand overclocking can be the reason for almost every problem LOL - same goes with the highly experimental stuff. I'm not following the CM9 and ICS threads explicitly but I stumble over them here and there. I mean I appreciate that some people (I mean users not devs) are willing to flash and test a ROM where 25% of the hardware can't be used almost reliable - because in the end there might be a useful port (e.g. of CM9) for our GPU-less Wildfire. But I use my phone on a daily basis and don't have the time to flash it twice a day (+/- 5 LOL) and to hunt for errors.
Regarding the V6SC: That's why I would like to have an (Android/CM) expert look into it. I suspect there might either be a conflict of the script with important system stuff, an unknown trigger of something technically harmful or simply a hidden bug which doesn't affect many users - but that's just one more theory. Maybe there's something happening deeper in the hardware which is triggered by a combination of situations (e.g. could have to do with the s-off-ing or rooting process).
]Yes, on the other hand overclocking can be the reason for almost every problem LOL - same goes with the highly experimental stuff. I'm not following the CM9 and ICS threads explicitly but I stumble over them here and there. I mean I appreciate that some people (I mean users not devs) are willing to flash and test a ROM where 25% of the hardware can't be used almost reliable - because in the end there might be a useful port (e.g. of CM9) for our GPU-less Wildfire. But I use my phone on a daily basis and don't have the time to flash it twice a day (+/- 5 LOL) and to hunt for errors.
Regarding the V6SC: That's why I would like to have an (Android/CM) expert look into it. I suspect there might either be a conflict of the script with important system stuff, an unknown trigger of something technically harmful or simply a hidden bug which doesn't affect many users - but that's just one more theory. Maybe there's something happening deeper in the hardware which is triggered by a combination of situations (e.g. could have to do with the s-off-ing or rooting process).
Click to expand...
Click to collapse
I try to follow all threads here in wildfire as well as a handful outside and like i said the main 3 factors mentioned above are nearly always present or come to be eventually
I dont think it will ever be pinpointed or whittled down to just one reason due to there being so many possible causes/possible triggers. I can however say from my own experiences that ive not had a single bootlooping issue since the day i removed and never again used any v6/juuwes enhancing scripts. I keep my processor at 633 max,264 min ondemand/smartass, my readahead sd speed never over 1024(516 is my preference, to limit sd errors) set on any rom i use.
I always unzip the rom and study within to edit, mod, remove certain elements i desire/dont need or want prior to flashing it.
This way i have the setup i want and need for my own personal liking.
Regards slym.
Forum fishing.... Who's biting!
Click to expand...
Click to collapse
Related
This is a guide I’ve put together from my (in)experience with flashing ACS. It mainly comes from the replies of k0nane and theimpaler747 in the SyndicateROM thread. However, since there’s so many pages that can be tricky to search for idiots like me who just throw up random posts for others to solve their problems, I thought it would be good to summarize it along with anything I happened to notice from flashing a couple of Epics. Consider it the FIBI guide.
Step 1: Read all posts by k0nane on page 1 of the SyndicateROM thread before doing a damn thing! http://forum.xda-developers.com/showthread.php?t=976194
Instructions for CWM are in this thread: http://forum.xda-developers.com/showthread.php?t=897612
Useful hotkeys:
Download mode - Hold down 1 on the keyboard when you power on the phone
Recovery mode - Hold Volume down+camera+power to power on the phone
Reset phone - Hold volume up+camera+power. This generally works when the phone is completely locked up.
Flashing:
When going between versions of ACS, check their notes to see if you need to do anything other than flash. You can go between some versions without wiping or losing anything. You can also flash between standard and fully loaded without wiping or losing anything.
Sdcard doesn’t mount in CWM, but shows up in Android - Format the sdcard in Android.
Boot hangs on the Samsung screen – Redownload, format your SD card and reflash
Boot screen flashed between different things – Wipe cache & data 3x and reflash
Journaling:
Enable journaling – In CWM, go to backup and restore. Backup, then restore using that backup. Journaling enabled!
Make it so you don’t need journaling – Keep a copy of the ROM on your phone at all times. Should you ever have data corruption, jump into CWM and flash the ROM again. It’s quick, no wipes needed.
If you restore a backup made in CWM and want to have non-journaled again – Flash the ROM after restoring.
Other issues:
FC in a specific app – Go into manage applications and clear data for that app
FC in several apps – In CWM > Advanced, try fixing permissions. Can also clear caches, and if that doesn’t work, reflash the ROM.
If you have any major issues that seem unresolved, Odin everything back to stock with EB13, format your sdcard in android, re-download everything, re-install CWM, re-read all of k0nane’s posts on page 1 and try again.
If you want ads back – Install adfree from market and hit revert
If your phone is freezing often - Flash either the vision kernel found here: http://forum.xda-developers.com/showthread.php?t=1012136 or the Twilight 1.0.4 kernel found here: http://forum.xda-developers.com/showpost.php?p=12504067&postcount=5904. I haven't had the freezing issues, but I'd recommend trying the vision kernel first as it has some other potential benefits.
Recommended tweaks and add ons:
Fugutweaks – This will smooth out a few random things on the phone. I’ve noticed more responsiveness on the lock screen and icons on my homescreen. Small, but nice. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=981125
Impaled Keyboard – Makes the keyboard less likely to skip keys. Still have some, but they’ve gone down a lot. I use the Speed Demon Edition, still had a fair amount of dropped keys with standard one. Install the ZIP in CWM, file can be found here: http://forum.xda-developers.com/showthread.php?t=1025533&page=18
SetCPU – Handles scaling the CPU and overclocking. Use ondemand setting for smooth performance. If you have issues when the phone is idle or it doesn’t wake up properly, set minimum CPU to 200Mhz. Free for XDA members, APK can be found here: http://forum.xda-developers.com/showthread.php?t=505419
Battery Calibration – If you want to calibrate your battery without going into CWM, grab the app from this thread: http://forum.xda-developers.com/showthread.php?t=1024867. It’s now available from the Android Market.
Vision Kernel – Pretty much Twilight + gives you 1.4Ghz and Voodoo colour which improves balance when brightness is at 100%. Flash in CWM, wipe dalvik. Kernel can be found here: http://forum.xda-developers.com/showthread.php?t=1012136
And a final note that I'm now about 10 hours into testing... if you are using fully loaded and want better battery life, really try standard. It very easy to switch, it flashes over fully loaded with no wipes or data loss, the only thing you lose is that it resets your homescreens. But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Great info! I recently installed the newest SyndicateROM 1.1.0 on my Epic and the only trouble I had was with the included Twilight 1.1.0 kernel. My phone kept freezing and I would have to pull the battery to reboot.
This is an issue that has been documented with the ROM and is said to be caused by the kernel and its adjustments to voltage and overclocking, not all phones handle this well.
To fix the issue I flashed the Twilight 1.0.4 kernel, as suggested by k0nane, and I am about a day into testing without any freezing issues. The only problem is that the Twilight 1.0.4 kernel has a known issue with video recording and it does not work.
Let me say that the performance increase from installing SyndicateROM and ext4 are well worth the trouble.
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
is your brightness at 100%??? what was the difference between standard and fully loaded again??
VeNoM vZ said:
is your brightness at 100%??? what was the difference between standard and fully loaded again??
Click to expand...
Click to collapse
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
k0nane said:
SyndicateROM Standard includes LauncherPro. All Samsung and Sprint bloatware are completely gone!
SyndicateROM Fully Loaded - the choice of ACS team lead rjmjr69 - features TouchWiz instead of LauncherPro, and adds in Social Network Sync, Facebook, BuddiesNow, Program Monitor, and the stock live wallpapers. All the rest of the bloat is still gone!
Click to expand...
Click to collapse
Catalyst Shift said:
What does the brightness have to do with anything? And for the differences, here's from the SyndicateROM thread:
Click to expand...
Click to collapse
The brightness for battery life.
No, brightness is not at 100%. I generally use 0-25%, though I'll kick it to 100% when viewing photos or when I'm outside. Even with the lower brightness setting, I'd always have to recharge in the afternoon. I'm still doing a lot of testing for ways of having the battery last longer, today is longest it's ever gone for. I'll be adding more information when I feel like I've got a solid way of having it all setup.
OP, could you add the freezes and "terrible battery life" solutions? Namely, flash the kernel in the second post or VisionKernel. It's the most annoying one to answer multiple times daily.
Thanks much for this! Hopefully people read it.
I want to get the battery situation on my phone sorted out before adding it to the list. I was having pretty bad battery life, but switching to standard and removing gallery has made my phone last all day for the first time ever. I want to do some experiments between setcpu options, juicedefender and the vision kernel to see what works best. Hopefully by this weekend I'll have a more detailed idea as to how to get better battery life.
But for now, anyone having battery issues my current setup is using ACS standard and replacing gallery with quickpic. This has doubled my battery life.
Hey wassup everyone, first time writer long time viewer, and first let me say thanks to all the great people that have provided us with great roms for the epic and the syndicate team as well, Im currently using a Epic 4G with sindicate rom freeze 1.1.0 and i must say its awesome, aside from my battery dying really quickly when im runing it at 1.3ghz its actually great, usually i end up operatig it at 800mhz to actually save some battery life last me for 3 days at a time, and when i have it pluged in or show off my awesome epic i raise it back upto 1.3ghz, big difference cuz when i raise it up there my battery drains rather quickly like 3 percent a minute or so.....
well anyways now that, thats says, I have CWM 3..0.5 with syndicaterom twilight 1.1.0 and ive been sucessful at loading custom boot animation, but one thing is that im having trouble is loading the animation with sound? any idea onhow i can od that?, what are the steps, cuz so far ive been using root explorer to transfer and change bootanimation to load up on my screen, but i have no idea where to put the sound or how to even get it to load with the bootanimation any one have any ideas? please help, i do all his trought my phone, put the bootanimation on my sd and work from there and trasfer it to the system/media, most bootanimation that do have sound on them say to put it on the system/custimization/resources but i look every where and the syndicate rom doesnt have that archieve just the system/media, how can i load the sound into my boot? and how can i change the power off animation as wll?
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals..
This might.. just maybe (crosses fingers) alleviate the never ending repeating of questions in the main sfr thread
Catalyst Shift said:
Have you tried the vision kernel? That might fix your freezing without breaking video recording.
Click to expand...
Click to collapse
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
The first sign of trouble came when I installed a fresh version of SyndicateROM 1.1.0 and then flashed Vision kernel 1.1. The phone booted-up fine but when I went to shut down it immediately froze and I had to pull the battery.
Im going to stay on Twilight 1.0.4 kernel for a while until I find something else.
I have tested Twilight 1.0.4 kernel for about a day or two and have not had any problems so far. I even overclocked with SetCPU to 1.2GHz without any issues.
tmspyder said:
Maybe someone should make a wiki "Trouble shooting guide" formatted like the ones found in the back pages of user manuals.
Click to expand...
Click to collapse
I would be more than happy to contribute my experiences if this gets up and running. PM me with any updates to the "SyndicateROM [TSG] WiKi"
Please Help a Novice
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen. Have I bricked my phone? How do I recover? Please please please help...Haven't even had my phone for a day...
By the way, the error I'm getting is:
ClockworkMod Recovery v2.5.1.0
E:Can't open /cache/recovery/log
I backed up before I installed this ROM, and Restore brings me back to this same screen / message
mercerma said:
I have installed this ROM, followed the directions and thought I did everything right. But when I rebooted the phone, I just get the Clockwork Recovery screen.
Click to expand...
Click to collapse
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Hey, great idea for the thread.
Something I learned:
I was having AWFUL freezing problems. Tried all the fixes (vision kernel, old twilight) to no avail. If these don't fix your problems, try Genocide Kernel (on these forums). Solved my problems.
Catalyst Shift said:
But really, this is day 1 of it for me and 10 hours in I'm at 62% battery remaining. Usually by this time I'd be around 20%.
Click to expand...
Click to collapse
Ok, so im thinking of switching to the standard edition of he rom cuz im currently using the fully loaded added the 1.0 kernel vision on it to get the 1.4ghz, and its pretty smooth its stable at times so im keeping it at 1.3 for now until its set more stable..... however when u said that ure at 10 hours and u still have 62% whats the speed u have ure epic set at and whats the brightness?
Nolyrics2 said:
Just tested Vision kernel 1.1 and ran into countless issues. My phone would not open camera, gallery, or music apps. And after that debacle I didnt even bother to find out if any other apps were misbehaving.
Click to expand...
Click to collapse
Fix permissions in CWM/etc.
Kernels cannot cause that. It's that simple.
Nolyrics2 said:
Please elaborate on the steps that you took to install the ROM and CWM.
What version of CWM are you running?
What modem do you have installed (...DK28, EB13, EC05)?
Have you transfered the SyndicateROM 1.1.0 onto your SD card before you installed CWM?
Did you wipe data, cache, and dalvik cache at least three times each before installing the .zip?
Your phone most likely is not bricked, that is a very hard to task to achieve. Worst case scenario you may have to do a clean wipe with odin and flash the stock ROM to start the process over. We can try to help you with any issues you may have but in the mean time try searching to the forum to find answers to these questions.
Click to expand...
Click to collapse
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
I installed CWM previous to transferring the rom to my sd card
I did not the first time, but per instructions on the page where I downloaded the ROM, I reformatted my sd card, redownloaded the ROM, wiped everything 3x's and tried to reinstall. Same result. I keep getting the error on just about everything I do that states "E:Can't open /cash/recovery/log"
And thank you for your advise, any more would be greatly appriciated. I did search the forum, but there is so much information, hard to find what I really want, especially as a novice. I plan to not be a novice for long thanks to xda!
mercerma said:
I used the one step root process I found here to install CWM 2.5.1.0. I then downloaded the ROM, copied it to my SDcard, then used CWM to install the zip from my sdcard.
I don't know what modem I have, is there a way to check with my phone in it's current state?
Click to expand...
Click to collapse
I could probably answer that question, im still a noob, but from what i know u need to install CWM version 3.0.5/6 in order for u to run does roms, thats why ure having trouble flashing it, since Syndicate roms are EXT4 Base Roms anything lower then CWM3 wont support since they are RFS files, go here and follow the steps
http://forum.xda-developers.com/showthread.php?t=976194
download the CWM3 and root it again, u can run the CWM Root over the previous 1 so dont worry, i did it that way and i had no problems what so ever, as to check to see what modem u had, go to settings, about phone, under base band version check to see if the last 4 letters says EB13, or DK28, or if u have the ECO5 which is the newest stock base update that came out.
Also its best to know if ure phone is from stock, or if u updated from any of the first 2 version updates, EB or DK, if u where like me that waited for the update and stayed at Eclair then updated when the ECO5 OTA came out then u should be fine....
Just incase u are from a update of EB or DK here is the link for does 2 versions of CWM3
http://forum.xda-developers.com/showthread.php?t=897612
if im wrong then someone please correct me im still a noob learning.
EDIT: just noticed that u said ure phone is messed at that point, umm u can try to do a factory reset then restart ure phone see if that fixes the problem, then try follow the steps above, if that doesnt work, u will have to download odin, which is also in that link and reflash back to stock, everything is there so if u follow does instrunctions u wont have a problem.....its actually pretty easy.....
Welp, the sleep of death. After not using the phone for bouts of 30ish minutes (possibly correlated to having an incoming SMS during that period), I will hit the power button only to find the phone does not respond. I will have to pull the battery, and when I reboot, ~80% of battery remains (it was fully charged before).
This happens on battery and on the charger alike.
Running CM7/MIUI (happens on both), and Chad's Latest.
Help!
Before you rule out hardware/software failure, you should try an alternate battery. Quick Q/A rundown:
*How long (in hours/days/weeks) has this issue been occurring?
*Have you removed any system apps?
*Install any partially incompatible mods?
It started recently, when I changed things up a little bit:
1) I got a new phone (replaced the HTC INC)
2) replaced the SD card to 16gb
It sounds more like a battery issue, have you tried switching batteries?
SlimSnoopOS said:
It sounds more like a battery issue, have you tried switching batteries?
Click to expand...
Click to collapse
The times I've had that issue it was almost always kernel related. Some kernels attempt to do things that simply don't work too well on certain ROMs or hardware. I'd be suspect of whatever sleep settings the kernel has.
Wow, I would not have thought of that. I haven't been very experimental with kernels, I'm one of those "find one kernel that works and stick with it" type users.
Thanks, I tried an older version of chad's, but maybe his whole line doesn't work? On two phones, that seems unlikely, but I will give it a whirl. I will keep stock CM7 kernel and report back if it gives me problems.
I hope it isn't Chad's...I love those kernels....
Well, I changed kernels to default, and it's still happenning. I get random reboots, about 4x a day. I reformatted my SD card and it helped performance a lot, and I thought that was causing the reboots, but the problem persisted.
Any help? Please? This is strange and it drains my battery.
Seems to happen around getting a text message/notification.
My thoughts revolve around: 1) the 3g is f*cking up my phone, but that would be strange, or 2) the vibration associated with the notification is rebooting the phone? Thoughts?
The way I see it there are a couple remaining options to try:
1) Flash a different rom outside of MIUI & CM7; however I'm doubtful this would resolve it as you experience reboots on two different roms.
2) Revert to stock Froyo using RUU file and see if reboots continue. RUU can be found at: dougpiston.com and there are threads detailing this process in the Droid Inc Dev. Section
3) Are you able to try a new/different battery?
Couple additional questions:
When you wipe & flash roms, do you Format Boot and Format System in addition to Format Data/Wipe Cache/Wipe Dalvik Cache? If not, possibly try this.
You experience reboots while within a rom, does your phone reboot while you're in Recovery? To clarify, if you were to attempt to manually flash a new rom does it reboot prior to/while in the process of flashing a rom?
-I have true s-off, permaroot and superCID
-ENG hboot and CWM work fine
-can successfully load and run ROMs
Device no longer sees a SIM card, yet been testing various ROMs for over 6 months with this handset.
I've taken it apart , and SIM slot looks ok.
I've tried eft wipe, superwipe, all my working nandroids, updated radio (currently running cm9/aokp40) to no avail.
Can anyone point me to how I can determine whether this is a S/W or H/W issue?
I'm leaning towards downgrading to stock/s-on then repeating the unlock to re-set my unlocked status for lack of any other options.
While googling not finding much if anything on radio data, so thanks in advance.
IF this is S/W based and you can help to fix I've a working TP2 in box as a reward/incentive.
If I am not mistaken the newer Roms need a newer SIM card, i.e.: the older ones (I think like 3-5 years old) won't be recognized with say the new radio (*.19)
I'm not sure what the new # is, but mine has 39.01a on the side, and works with the latest radio and CM9, EliteMod ICS, etc.
EDIT: But that might only refer to T-Mobile, not sure how it is with Fido/Rogers.
kbeezie said:
If I am not mistaken the newer Roms need a newer SIM card, i.e.: the older ones (I think like 3-5 years old) won't be recognized with say the new radio (*.19)
I'm not sure what the new # is, but mine has 39.01a on the side, and works with the latest radio and CM9, EliteMod ICS, etc.
EDIT: But that might only refer to T-Mobile, not sure how it is with Fido/Rogers.
Click to expand...
Click to collapse
Food for thought thanks, the SIM stopped being recognized after having flashed the "no service fix" update to this ROM http://forum.xda-developers.com/showthread.php?t=1749445 and have asked in that thread whether anything in the fix file could've set something off on my device.
IT IS an older SIM that I'm using but up to now have used every ROM with it without a hitch. I'll downgrade the radio now as an option.
igor45 said:
Food for thought thanks, the SIM stopped being recognized after having flashed the "no service fix" update to this ROM http://forum.xda-developers.com/showthread.php?t=1749445 and have asked in that thread whether anything in the fix file could've set something off on my device.
IT IS an older SIM that I'm using but up to now have used every ROM with it without a hitch. I'll downgrade the radio now as an option.
Click to expand...
Click to collapse
I noticed that it said "only for 2.7.13", though that seems to be specifically for a version of MUIU.
though when I unpack the fix :
Code:
assert(getprop("ro.product.device") == "vision" || getprop("ro.build.product") == "vision");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");
unmount("/system");
Which basically only verifies that the phone is a HTC Vision (as per existing build.prop), mounts the /system partition, then extracts the package's content of /system to your rom
in this case a single file:
/system/framework/framework-res.apk
So from just that, I can't really see the fix having a prolong effect on all your other roms, unless you failed to do a full wipe (factory reset and wipe cache/dalvik cache in recovery before flashing a brand new rom).
This is the only thing I've changed in framework-res.apk:
Code:
<bool name="skip_restoring_network_selection">false</bool>
v1r0x said:
This is the only thing I've changed in framework-res.apk:
Code:
<bool name="skip_restoring_network_selection">false</bool>
Click to expand...
Click to collapse
right but even that change would be completely wiped out if he wiped/changed roms, so would have to be another factor that caused it.
kbeezie said:
right but even that change would be completely wiped out if he wiped/changed roms, so would have to be another factor that caused it.
Click to expand...
Click to collapse
Yes. Maybe it's just coincidence..
But I hope there is a fix for that problem.
Sounding like my SIM slot at this point then. But I didn't just flash the fix on its own. I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Sent from my HTC Vision using xda app-developers app
igor45 said:
Sounding like my SIM slot at this point then. But I didn't just flash the fix on its own. I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Maybe nothing to do with this but was using Elitemod/CM9/AOKP before flashing and "su" reported that it needed to close. I'D been experiencing few FCs with that ROM installed.
Didnt thing this would affect it once rebooted to CWM.
igor45 said:
I first flashed the updated zip from later in the thread that included the fix w/the complete ROM. Wonder if anyone else has tried that file?
Click to expand...
Click to collapse
which file do you mean with that?
igor45 said:
Maybe nothing to do with this but was using Elitemod/CM9/AOKP before flashing and "su" reported that it needed to close. I'D been experiencing few FCs with that ROM installed.
Didnt thing this would affect it once rebooted to CWM.
Click to expand...
Click to collapse
Can you be more specific on the EliteMod part, are you simply talking bout the EliteMod ICS rom, or putting EliteKernel on top of a CM9 or AOKP port? (if just the rom, I'm not aware of a 'fix' that was meant for EliteMod).
v1r0x said:
which file do you mean with that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=28906048&postcount=74
... maybe something in yozgats file?
igor45 said:
http://forum.xda-developers.com/showpost.php?p=28906048&postcount=74
though I see it doesn't include the fix... maybe something in yozgats file?
Click to expand...
Click to collapse
Are you saying you used a fix from one rom (light) with another rom (elitemod)? I'm not getting very clear information from you just bits and pieces.
to clarify
kbeezie said:
Are you saying you used a fix from one rom (light) with another rom (elitemod)? I'm not getting very clear information from you just bits and pieces.
Click to expand...
Click to collapse
LOL - bit of a noob here though not that bad, so no I didn't mix fixes/ROMs :highfive:
I was on latest Elitemod/CM9/AOKP
To be clear,
1 - I first flashed the file from post 74 in the thread that included the bugfixes and few enhancements to the original.
(So wondering whether there's something in that file, and yes it does include the fix)
----this is where "no sim inserted" occurs---
2 - when ROM came up good but no SIM, i reverted to my nandroids, trying each one of them.
3 - then tried full wipes with fresh ROM flashes
4 - then tried superwipe/efs wipe AND updated radio and tried each nandroid/fresh installs again
5 - now downgraded radio to what I had (minus the rils) and living with WIFI only connection til I can fix the SIM issue
btw "Elitemod/CM9/AOKP" are three different roms If you just mean EliteMod ICS just say that , helps reduce the confusion. (since some people do separately install AOKP or CM9 by itself, and then flash EliteKernel on top of those).
k, as for #1 when I originally read about the 'fix', that was for a completely different rom than EliteMod and course probably wouldn't work anyways.
Secondly with EliteMod ICS, I've found that I had to be on the .19 radio (note my signature) in order to boot up with it and manage both data and wifi connection, there was no need to 'patch' anything because nik3r already included the proper ril/data for the newest radio in the rom/kernel itself. And it doesn't matter if you're on either the G2 hboot (0.76.0000 I think) or the DZ hboot like I have, since it's not a sense rom or a rom of that size.
If you are on a functional phone right now (outside of the non-Wifi data connection of course), I would recommend upgrading your recovery to 4EXT recovery first (something like the 4EXT Touch Recovery 1.0.0.5 RC5 that can be installed from the app, the app itself is found in google play and can install the recovery for you, there is a free version of the app that I have if you simply want the installer but I Recommend the paid version since you can control most of it's preferences from the app before rebooting into recovery).
From there (assuming you have everything you need backed up to the computer including say any titanium backup files):
Just to knock out a number of possibilities will just act like we're going to do a 'full' setup, assuming that 1) You are already using an ENG S-OFF hboot and 2) have already upgraded the radio to the latest .19 version
1) re-partition the SD card via 4EXT (I recommend a 2GB sd-ext, skipping the sd-ext2 and skipping swap), so that's freshly setup [that and if you chose to use the dataswap mod for EliteMod the 2GB sd-ext is needed to compliment it, never make a sd-ext less than ~1.5GB in size]
2) once you got that re-partitioned toggle the USB storage so you can copy back all the files you need including the rom files etc etc.
3) "Wipe/Format" menu to do
a) Factory Reset/Wipe
b) wipe cache+dalvik
c) Battery stats (cuz why the hell not, it *could* help lol)
4) No need to do an EFS wipe since the EliteMod rom zip does this for you upon installation, so Flashing the EliteMod Rom, then any optionals (Gtalk, google gallery, T-mobile wifi calling, DataSwap mod) on top of that.
PS: if you like to multitask active apps quite a bit (i.e.: background notifications etc), I would recommend the 64MB Dataswap mod at the very least, especially with all that free space you'll have on /data partition from the use of an sd-ext partition.
5) Reboot, once fully booted, reboot again
6) check connectivity for both SIM/Wifi/Etc.
If you're *still* having problems, even after physically pulling the sim out, blowing some dust out, or whatever you can and putting it back in, I'd start to wonder if 1) the sim is too old for whatever reason [ie: with whatever update], 2) the sim got damaged [maybe via some kind of sim update?], or 3) the sim slot is maybe damaged? 4) or the universe just hates you right now.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
PS: I highly recommend Titanium Backup, it's been very useful in flashing a fresh clean rom, but then being able to restore most of my applications with their settings/data intact.
kbeezie said:
btw "Elitemod/CM9/AOKP" are three different roms If you just mean EliteMod ICS just say that , helps reduce the confusion. (since some people do separately install AOKP or CM9 by itself, and then flash EliteKernel on top of those).
k, as for #1 when I originally read about the 'fix', that was for a completely different rom than EliteMod and course probably wouldn't work anyways.
Secondly with EliteMod ICS, I've found that I had to be on the .19 radio (note my signature) in order to boot up with it and manage both data and wifi connection, there was no need to 'patch' anything because nik3r already included the proper ril/data for the newest radio in the rom/kernel itself. And it doesn't matter if you're on either the G2 hboot (0.76.0000 I think) or the DZ hboot like I have, since it's not a sense rom or a rom of that size.
If you are on a functional phone right now (outside of the non-Wifi data connection of course), I would recommend upgrading your recovery to 4EXT recovery first (something like the 4EXT Touch Recovery 1.0.0.5 RC5 that can be installed from the app, the app itself is found in google play and can install the recovery for you, there is a free version of the app that I have if you simply want the installer but I Recommend the paid version since you can control most of it's preferences from the app before rebooting into recovery).
From there (assuming you have everything you need backed up to the computer including say any titanium backup files):
Just to knock out a number of possibilities will just act like we're going to do a 'full' setup, assuming that 1) You are already using an ENG S-OFF hboot and 2) have already upgraded the radio to the latest .19 version
1) re-partition the SD card via 4EXT (I recommend a 2GB sd-ext, skipping the sd-ext2 and skipping swap), so that's freshly setup [that and if you chose to use the dataswap mod for EliteMod the 2GB sd-ext is needed to compliment it, never make a sd-ext less than ~1.5GB in size]
2) once you got that re-partitioned toggle the USB storage so you can copy back all the files you need including the rom files etc etc.
3) "Wipe/Format" menu to do
a) Factory Reset/Wipe
b) wipe cache+dalvik
c) Battery stats (cuz why the hell not, it *could* help lol)
4) No need to do an EFS wipe since the EliteMod rom zip does this for you upon installation, so Flashing the EliteMod Rom, then any optionals (Gtalk, google gallery, T-mobile wifi calling, DataSwap mod) on top of that.
PS: if you like to multitask active apps quite a bit (i.e.: background notifications etc), I would recommend the 64MB Dataswap mod at the very least, especially with all that free space you'll have on /data partition from the use of an sd-ext partition.
5) Reboot, once fully booted, reboot again
6) check connectivity for both SIM/Wifi/Etc.
If you're *still* having problems, even after physically pulling the sim out, blowing some dust out, or whatever you can and putting it back in, I'd start to wonder if 1) the sim is too old for whatever reason [ie: with whatever update], 2) the sim got damaged [maybe via some kind of sim update?], or 3) the sim slot is maybe damaged? 4) or the universe just hates you right now.
---------- Post added at 06:27 PM ---------- Previous post was at 06:26 PM ----------
PS: I highly recommend Titanium Backup, it's been very useful in flashing a fresh clean rom, but then being able to restore most of my applications with their settings/data intact.
Click to expand...
Click to collapse
Yes understood that the "fix" was a trivial patch and that it pplies only to the MIUI multilang version in question - trust me I would not have mixed those two up. I opted to first flash the version from the later post since it included app/framework enhancements WITH the "no service fix"
Yes I was on Elitemod ICS (AOKP base) with modified CM9 kernel. Sorry for that confusion.
I'd previously used Elitemod AND AOKPs with my old radio with no issues whatsoever. never had to tweak a thing.
FWIW I'm on hboot .84.2000 ENG s-off and yes using clockworkmod recovery
I'd like to try 4ext - looking into it now.
Appreciate the help.
Maybe I'll put this on hold til I get a new sim from FIDO...
igor45 said:
Maybe I'll put this on hold til I get a new sim from FIDO...
Click to expand...
Click to collapse
Yea the issue in general sounds just weird overall, hopefully it'll get resolved one way or another.
kbeezie said:
Yea the issue in general sounds just weird overall, hopefully it'll get resolved one way or another.
Click to expand...
Click to collapse
Indeed - still hoping that there's someone that can offer a method of testing to see whether its a H/W issue. Must be somethng in adb and/or bootlogs? Perhaps in the bootloader for Radio.
well reading over this thread have you tried another sim? your sim in another phone? you can run some very simple tests in the diagnostics menu. go to dialer and type *#*#4636#*#*
go into phone info and play around with turning radio on and off and gsm only etc to see if anything appears ok. the best ways to test software/firmware or hardware faliure you seem to have tried, wipe fully, flash new rom, new radio...
I guess you can always try to unroot? if it still won't work then my guess is hardware
Sent from my HTC Vision using xda premium
demkantor said:
well reading over this thread have you tried another sim? your sim in another phone? you can run some very simple tests in the diagnostics menu. go to dialer and type *#*#4636#*#*
go into phone info and play around with turning radio on and off and gsm only etc to see if anything appears ok. the best ways to test software/firmware or hardware faliure you seem to have tried, wipe fully, flash new rom, new radio...
I guess you can always try to unroot? if it still won't work then my guess is hardware
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
thx for the suggestions
Have my sim working in my backup phone and works in every other phone I've tried. Yes have also tried airplane mode on/off data on/off - etc...
Did try to unroot yesterday but ran out of time, had to run off to work.
Want to do it right so will try again today as I've a bit more time.
playing with diagnostics menu now thanks.
Hi
Guys i need your help. Pleas can someone tell me for now what mods is much better for I927R (Also withe very stability and with much less bugs) ?!
I found Liquid Smooth but it have some problem so i need your guide about other mods.
Thank you
ICS Roms are the best and most stable... Stock ICS from AT&T UCLJ3 or any roms based off of it ... Dman's daily driver, Ice Pop Rom by RawRaw, LiteRom by TheGreaterGood...
Unfortunately none of those are being maintained but I had been running Dman's for the last couple months, great battery life when paired w/ JuiceDefender (20+hours of heavy use when I'm not sleeping).
Now the newest CM10.1 by Spyke seems pretty solid ... Just a couple of issues.
ICS is the only one you'll get bug free, though. Stock is hard to compete with when we're pairing up roms without a true Devdeloper.
On this subject, I've just reverted back to using IcePop ROM after (unhappily) downgrading from Spyke's latest 10.1 ROM - just mainly because of the Bluetooth headset issue, which I really need working for work purposes.
I'm just wondering if there are any ICS builds that have GPS working correctly? I tried flashing the Rogers modem (since my phone was originally a Rogers import, flashed to AT&T ICS, then played with ICS from there) and first time I ran GPS status it took 771 seconds... I'm going to keep trying just in case that was the first time only, but 12 minutes is still a very long time for an initial fix .
Also - I've found that I'm getting more and more bootloop problems even with clean installs - so wiping cache, data, dalvic, etc. Is there some way to do a *thorough* wipe without bricking the phone? I can back all my data up no worries, but next time I move to JB (in the optimism that the BT issues will be fixed soon, judging by the positive progress being made by Spyke ) I would like to do a clean build from scratch and not have to gamble being able to start the phone up again
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
I, also, had reverted to using JB Because GPS wouldn't work ... There's a thread in here (search for it) that shows the solution to the GPS fix, its editing sirgps.conf and gps.conf ... I was getting a fix on GPS in under 30 seconds.... GPS was a huge let down in the stock ICS rom, Even when using TheGreaterGoods LiteRom w/ GPS fix I found after a couple of days my gps didn't hold....
Thanks for the reply.
I was considering formatting /system this morning when I was getting stuck in a boot loop from trying to get M3 running, but decided it was a risk I'd have to check up on first . Next time I do a build from scratch (I'm going to resist until the BT stuff is working - fingers crossed!) I'll do that.
I remember having a look at the gps.conf fix but don't recall anything about sirgps.conf - so I will look it up, thanks!
As an aside, I've been checking the GPS fix a couple of times since my last post and it is coming up in under 30 seconds each time... I'm wondering if my attempt to flash the Rogers modem did in fact fix the issue... I'd do a reboot but I'm too scared I won't get the phone up again XD
EDIT:
Found the fix, I did a few of the changes (rather than all of them), and it's now picking up 8 satellites instead of 3-5, and getting a stronger signal from each... and all I did was point it to the AU ntp server, and tell it I'm not on the ATT network . I'll save the suggested settings to a text file on my SD card so next time I'm out and about and if it plays up I'll have access to the details.
yohan4ws said:
David - I always go into mount options of CWM and format /system prior to a new flash .. I'm not sure if flashing with Odin will get rid of any previous settings, its something to attempt though.
Click to expand...
Click to collapse
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
davidpartay said:
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
That has to be very concerning to you, I've never had an issue booting any ROM. And very strange flashing the Kernel separately would resolve your booting issues...
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
If I were in your position I would try and do a full revert back to the earliest version of gingerbread I could find on samfirmware and then use Kies to udpate - THEN I would retry flashing to a newer JB or ICS Rom.
Pretty time consuming but that is the price we pay to mod
davidpartay said:
Had to restart my phone tonight and got caught in a boot loop again... after trying a few things I flashed Lite Kernel (I'm still using ICS again at the moment) and that seems to have solved the boot loop issues. I'm thinking that with all the ROM flashing I've been doing the fact that I actually had the phone running without flashing an ICS specific kernel (after running JB) was screwing things up.
Interestingly though, I tried installing Spyke's M3 ROM from a complete user wipe, system format, everything gone - and I still got a boot loop so next time I try it I'll grab a copy of LiteKernel and do that separately.
Click to expand...
Click to collapse
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
yohan4ws said:
Did you try to flash any of the stock roms w/ Odin ? I have read that we can only flash back to stock Gingerbread from JellyBean if we flash a GB or ICS CWM ROM and then go back with Odin otherwise there will be boot issues.
Click to expand...
Click to collapse
Not yet. I'll have to check which ones I have - I'm certain I have the AT&T ICS rom from November but then I'd have to go digging through my email for the unlock code again, so I'm trying to avoid doing that at this point . If i can find the stock GB Rogers rom at some point I might flash that one back on before I do any more upgrades. The phone is up and running at this point though, so I'm not too fussed. I've also noticed that it's a little quicker than before so I think the version of LiteKernel I installed was a good idea anyway.
bubor said:
My phone has an issue, simple I couldnt reboot it, I must power off and wait a little. You can try it when you flash something, just remove battery and usb cable, and wait 2 minutes, before you turn on.
Click to expand...
Click to collapse
I've tried pulling the battery a few times, but probably no longer than 30 seconds. Next time I'll give it a couple of minutes. I tend to do this late at night when I'm not expecting any calls (except fire brigade but I have a pager for that too) so time without a phone is no issue to me
Yesssss
After much irritation at continually getting stuck in boot loops again, I've 'Oneclicked' the phone twice, got fed up with the AT&T ICS ROM within about 5 minutes, gave up on IcePop because of buggy GAPPS...
And thought, bugger it. Format /system. Factory reset. Clear cache + Dalvik. Installed in this order:
Jellybean 4.2 ROM from 0217
Spyke's M3 update
PAC rom
GAPPS dated 0427
"Kick-ass Kernel"
and it BOOTED FIRST GO
I am pleased
Does JB need already to be installed before putting the M3 revisions on? Maybe that's where I've been going wrong all along, because my attempts at running both the standard M3 and PAC ROM (even immediately after OneClicking) resulted in boot loops or eternal boot loading.
Uhh... what do you mean by "One Clicking" ??
I know there's a "superoneclick" that will flash and root the rom all at once, but I never personally found it to work for our glides.
Using CWM and installing the ROM through the CWM boot menu is severaly key presses so ... not too sure what you're referring to.
Also, I've always downloaded to a hardwired computer then copied over USB to my phone and flashed ... sometimes the download will have errors if I grab it from my phone.
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
davidpartay said:
I'm assuming it's a variant of SuperOneClick... The title is 'Odin3Excution v1.85' and then underneath it says 'I927UCLG9_OneClick'.
And it worked just fine, I did have a stock rom that I tried to flash with Odin but it kept giving me errors, the OneClick method worked.
Click to expand...
Click to collapse
Interesting... for future reference, www.samfirmware.com has the stock firmwares, then there's the superUser file floating around the forums that allows you to root by flashing it. Passed that, remove bloat.
Glad you got it working! Welcome to JB
My phone's software/kernel/partition (or something like that) is so messed up that my battery life sucks on all roms (even on roms I changed back to after receiving the problem that never had the problem), my phone seems to overheat, and reboots/freezes all the time. Battery stats says nothing really. My battery life is like TWO to THREE times LESS than before I flashed a bunch of ROM and kernels.
So basically I need something flashable that:
- Wipe all RE-BUILDABLE partitions COMPLETELY (and then rebuilds them) and/or gives cleans all partitions
- Formats and cleans everything on the phone (in a way it doesn't break any default features of the phone)
- Fixes any kernel bugs/glitches that retain after flashing other kernels
- Fixes all modem issues (like that flashable modem fix I saw but incorporated with everything above)
- Sets everything to default settings
- COMPLETELY and SAFELY removes Wanam and XPOSED framework out of the phone (I think it is causing me problems)
Basically, I think I broke something and want to completely fix the issue, so I can SUPER clean flash a KitKat rom and not have uncommon issues that the ROM does not have (I'm currently on 4.3)
Mystery? said:
My phone's software/kernel/partition (or something like that) is so messed up that my battery life sucks on all roms (even a rom I changed back to after receiving the problem), my phone seems to overheat, and reboots/freezes all the time. Battery stats says nothing reallu. My battery life is like TWO to THREE times LESS than before I rooted it and flashed a ROM.
So basically I need something flashable that:
- Wipe all RE-BUILDABLE partitions COMPLETELY (and then rebuilds them) and/or gives cleans all partitions
- Formats and cleans everything on the phone (in a way it doesn't break any default features of the phone)
- Fixes any kernel bugs/glitches that retain after flashing
- Fixes all modem issues (like that flashable modem fix I saw but incorporated with everything above)
- Sets everything to default settings
- COMPLETELY and SAFELY removes Wanam and XPOSED framework out of the phone (I think it is causing me problems)
Basically, I think I broke something and want to completely fix the issue, so I can SUPER clean flash a KitKat rom and not have uncommon issues that the ROM does not have (I'm currently on 4.3)
Click to expand...
Click to collapse
Use your recovery (twrp being the best one to do this) and wipe everything. back up your internal memory, then remove your sdcard.
boot into recovery and go to wipe menu and click all the options. The wipe will fail on extsdcard but that's because you have removed your sdcard. shut power off, replace your sdcard and boot back into recovery. Flash whatever rom you have on your sdcard. This should fix any problem you have had. If you are still getting overheating bootloops bla bla bla, then this is a phone issue.
Oh and don't do a titanium restore since you don't know what exactly is messing with your phone.
Seconded, all opposed? <crickets.wav grasshoppers.wav.bak>...
Sent from my SM-N900T using Tapatalk
Mystery? said:
My phone's software/kernel/partition (or something like that) is so messed up that my battery life sucks on all roms (even on roms I changed back to after receiving the problem that never had the problem), my phone seems to overheat, and reboots/freezes all the time. Battery stats says nothing really. My battery life is like TWO to THREE times LESS than before I flashed a bunch of ROM and kernels.
So basically I need something flashable that:
- Wipe all RE-BUILDABLE partitions COMPLETELY (and then rebuilds them) and/or gives cleans all partitions
- Formats and cleans everything on the phone (in a way it doesn't break any default features of the phone)
- Fixes any kernel bugs/glitches that retain after flashing other kernels
- Fixes all modem issues (like that flashable modem fix I saw but incorporated with everything above)
- Sets everything to default settings
- COMPLETELY and SAFELY removes Wanam and XPOSED framework out of the phone (I think it is causing me problems)
Basically, I think I broke something and want to completely fix the issue, so I can SUPER clean flash a KitKat rom and not have uncommon issues that the ROM does not have (I'm currently on 4.3)
Click to expand...
Click to collapse
I would go back to stock for 2 days and see what happens.
TWEAKED N3
dragonstalker said:
Use your recovery (twrp being the best one to do this) and wipe everything. back up your internal memory, then remove your sdcard.
boot into recovery and go to wipe menu and click all the options. The wipe will fail on extsdcard but that's because you have removed your sdcard. shut power off, replace your sdcard and boot back into recovery. Flash whatever rom you have on your sdcard. This should fix any problem you have had. If you are still getting overheating bootloops bla bla bla, then this is a phone issue.
Oh and don't do a titanium restore since you don't know what exactly is messing with your phone.
Click to expand...
Click to collapse
Why go thru all the machinations with the extSD card? Why not just uncheck that in wipe options?
How about formatting partitions?
les_garten said:
Why go thru all the machinations with the extSD card? Why not just uncheck that in wipe options?
How about formatting partitions?
Click to expand...
Click to collapse
He does not need to format partitions. And when making suggestions, i tend to make sure that i make the process as simple as possible, and with as little wiggle room for error. Remove the Sdcard, there is no room for error. Can wipe something thats not there.
@dragonstalker, I did what you said, I think for the few hours on Darthstalker I was on, I was getting really good battery life
@BACARDILIMON, but when I went to KitKat (stock rom). My battery life became worse than what I had when I made this thread. Da heck?!
Mystery? said:
@dragonstalker, I did what you said, I think for the few hours on Darthstalker I was on, I was getting really good battery life
@BACARDILIMON, but when I went to KitKat (stock rom). My battery life became worse than what I had when I made this thread. Da heck?!
Click to expand...
Click to collapse
what kernel did you flash with the kit kat rom. And did you make sure that it was a 4.3 compatible kit kat rom?
dragonstalker said:
what kernel did you flash with the kit kat rom. And did you make sure that it was a 4.3 compatible kit kat rom?
Click to expand...
Click to collapse
I flashed to stock through the instructions linked on the Infamous Touchwiz ROM for KitKat. I went to completely stock (with stock kernel) and my battery life got much more worse than before - after changing the settings and whatnot. Flashed Colonel X R13 and boom battery went to 6 hours although not as much as 8 like I used to have in the JB stock ROM days.