[Q] Boot Manager. Anyone have it working on the Shift - EVO Shift 4G Q&A, Help & Troubleshooting

I like the idea of booting to different roms on the fly. The support lists almost every HTC phone but ours. I loaded and manually set all parameters but it force closes every time I try to install a zip to the rom slot.
I've uninstalled and wiped several times but to no avail.
No response to emails as of yet.
Any thoughts?
Thanks.

A lot of devices need modified code to get this up and running, the Devs for BM are going to start working on the shift soon.
Also to find your own personal problem about the FC's you may want to check /sdcard/BootManager/log.txt and/or your logcat while running.
Even if you fight past that, you'll still have issues with the scripts modifying the boot.img. Testing for the shift should start soon, official support will be sure to follow =P
@Emails, you can also try their forums. They are really dedicated to getting this to work for everyone.

Related

Wake issues with newer ROMS

I am posting a new thread because I'm experiencing the issue with several diffrent ROMs so obviously it's a general issue not a ROM specific one. Also I have read through countless pages of posts with no luck so hopefully someone can shed some light. Over the past few days I've flashed (forgive my spelling) dude's .5, ravenge, cynogen 3.4 and I have been having issues with the phone not waking after either I put to standby myself or the screen times out. I know it's not an issue with my phone or card because I go back to virtudude's ROM without the issue. I have tried everything, formatting my partition, ext2, ext3, wipe, no wipe, everything I can think of and still have the issue accross mutiple ROMs. I know it's not just me because my friend with a G1 is having the same issue, as well as many people posting in the threads. Can someone please point me in the right direction to fix this issue please?
My phone:
G1 with JF 1.42
Newest SPL 2005
Newest 26I radio
8gb SD card, class6, ext2 or ext3 partition (same issue on either)
Thanks in advance for any help!
me too
I noticed this same problem, its related to wifi, when I disable wifi my phone wakes up, also I have searched everywhere too for a solution. I think the compiled wifi deiver in these roms are not compiled right. So its either this or some other problem.
Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.
I am doing a test, im leaving wifi on while the screen is off in settings, will report back
This happens to me also but its only with hero I also have the new radio and spl. I can run hero with no problems as long as I don't use apps to sd or lucids txt. The wired thing is that after I use any apps to sd it works great but only for a day sometimes a few hours. Then I will start to see freezing up or it won't wake up at all, unless I reboot or pull battery. I've tried to reformat my card, resize my partition I'm also lost on this one fresh out of ideas.
Do you guys think it might have somthing to do with the sdcards? Im useing a 4g class 6 transcend micro SD, its only about 2 weeks old. Jason what other roms gave you these problems?
defconoi said:
Is your phone connected to wifi with wpa2 personal? One other thing I noticed is this happens at random, when it does happen adb and ddms say device is offline when the led is blinking, also bottom of phone gets hot.
Can any devs shed some light on what exactly happens when the phone shuts off? Because something is locking the phone up when the light goes off and is in standby.
Click to expand...
Click to collapse
I personnally don't see the correlation between locking and WiFi, I was at work the other day and flashed a ROM and it was doing it. I have my WiFi off at work so that wouldn't have been the case that day. I do notice the bottom of the phone getting hot though.
In response to the other person with the sd card question I really don't think it's that as I have a class 6, have formatted every way possible. Unless the issue has to do with apps2sd, I use apps2sd on every ROM.
Glad to see I'm not the only crazy one on xda!
joe v said:
Jason what other roms gave you these problems?
Click to expand...
Click to collapse
Almost every ROM to come out in the last couple weeks has done it. TheDude's .5, Ravenge's ramjet, Cyanogen's 3.4.1, and the Cyanogenized Rogers ROM.
You know looking at these the one thing these all have in common is being Cyanogenized. And the only ROM to come out in the past few weeks that hasn't had that issue is Virtuedude's Rogers ROM, which isn't Cyanogenized.
If any devs are reading this thread if you can make a version of your most recent ROM without Cyan's build kernel and boot and see if that helps. I'd be happy to test it for you to try and get to the bottom of this. If you wanna shoot me an email hit up jasonsyn at gmail.
I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.
indiekid97 said:
I've had the same problem, but for me it started after flashing Cyanogen's 3.4 release. Since then I've reverted back to his 3.3.3 release and everything is fine again. Perhaps it has something to do with the new SPL and these ROM's?
That seems to be the one constant among all of us with problems, we've all flashed the new SPL and radio.
EDIT: I asked cyanogen about it, we'll see what he says.
Click to expand...
Click to collapse
Yeah but I've had the new SPL and Radio for a month and this just started a week or so ago...
I am having the exact same issue. I usually have wifi bluetooth and 3g disabled (saves battery) I noticed this started after grabbing the new spl, ever since it's been freezing in standby randomly. I'm going to try Virtudude's rogers rom to see if the combination of Cyanogen's boot image and the new spl is causing the freezing. Hopefully seeing as Virtududes rom isn't based on Cyanogen's boot image it won't freeze. I'll report back with my results.
I thought my button got worn out. I never had the symptoms on rc33. When I switched to cupcake back during hatkuros prime just before dudes first releases I noticed it. I thought if it wasn't my button it might be somehow related to jf kitchen since almost all my roms touch it at some point. Just speculation though, donno what causes it.
Hey what recovery image are you all running?
I'm gonna flash the new Cyanogens 1.2 Recovery image and see if that's the issue.
Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.
Jason Syn said:
Ok so how gay is this? I just hung up from a phone call and the phone is stuck sleeping! I was using it and it won't wake up, this is so incredibly frustrating!!
I have the new recovery image, 3.4.1, and still issues.
Click to expand...
Click to collapse
try holding down menu or the power button...i had this issue and my sd card would "unmount unexpectedly" and then this ended up into my sd bein fried
for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.
dbhatesyou said:
for those who are having this issue, try saving a log of it from ddms after that adb shell reboot thats what ive been doing ... instead of removing the battery, though my issues seem to happen every 24 hours i was on cy's 1.1 just flashed 1.2 perhaps that was is the issue?.. either way... we should try to collect all the info we can while this is happening to us.
Click to expand...
Click to collapse
Ok I'll be happy to but I'm a linux virgin...would you mind giving me step by step in adb and I'll give whoever the log that can make sense of it.
This happens to me also on The Dudes Roger built. I don't have WiFi enabled so it isn't that it seems pretty random and just I get no response from the phone and have to so the soft reset (Call Menu Power) and then it'll work again. Normally only happens like once a day though so I can live with it but it is a inconvenience and can be annoying if it does it when you actually need to use your phone for something with some importance.
well if you're on linux and have it to where adb runs from terminal , just type
Code:
adb shell reboot
but before all that ddms (dalvik monitor) just type ddms in terminal it will boot up and show everything your phones basically working with.. and issues,
now if your linux terminal doesnt work well with adb (cant get it to work , google "50-android.rules" and "51-android.rules" n see if those help, and also set your echo path right )
now if you're on windows just hit windows key + r type cmd , and set yourself into the sdk/tools directory, then type ddms that will start the dalvik monitor (try and save a log) make sure the log saves before rebooting the phone, when you're done you can just ctrl+c and type adb shell reboot, and your phone should reboot.
[just the basic]
i've ran into this intermittently...most of the time while using the browser or using the onscreen keypad during a phone call.
I'm on JF CRB43(which is 1.51 i think) with the Hard SPL and JF Recovery.
Only thing I've been able to do to get the phone to wake up is wait. eventually it'll come around. or pull the battery, which i try not to do.

[Q] Can't get SuperOneClick to run. Help?

I upgraded my AT&T Samsung Captivate from Froyo to Gingerbread a couple weeks ago, when AT&T released it. I had nothing but problems with it - my phone would reboot repeatedly, it would freeze multiple times a day. I tried factory resets, GSM resets, removing apps, nothing helped. My phone was basically unusable. I gave up and took it to a local AT&T Service Center. They seemed very aware of the problems, and recommended reverting it back to Froyo. I had them go ahead and do it. They got Froyo back on it, although they somehow broke the Contacts. Each time they pressed the Contacts icon the phone would Force Close. The "tech" didn't know what to do about it, and recommended that I go to the AT&T Retail Store and see if I was eligible to buy a new phone! Once home, I did a Factory Reset (from the Menu button), which resolved the Contacts issue.
I'm OK with having Froyo instead of Gingerbread. There are a couple features I like better in Froyo anyway (Data Network Mode off the power button, Silent option from the pulldown menu). The only thing I miss is the ability to install non-Market apps. I figured the easiest way to get that would be to root the phone (I had rooted a previous Captivate, but didn't do this one after it was replaced, since I was waiting for the Gingerbread update). Anyway, I downloaded the latest version of SuperOneClick and installed it, but when I try to run it I get an error message, saying that SOC stopped working and Windows is looking for a solution. I’ve tried running it on Win7 32 bit and Vista 32 bit machines with the same results. I’ve tried running it as an Administrator. I’ve Allowed it when asked for permission. Is there something I'm missing in order to get the program to run? I know there are other ways to root it, and other ROMs that I could run that people here would say are way better. I like SOC because it's fast, easy, and allows me to unroot if necessary. Froyo does what I need it to do, so I don't need a different ROM. Can someone just please tell me what I need to do to get SuperOneClick to run?
BTW, before anyone suggests it, before even trying to root I called AT&T Tech Support and asked them to push a patch which would allow me to install non-Market apps. After 1 hour and 22 minutes on the phone, in which the tech consulted his manager, and a higher level tech support in Alabama, they determined that it could not be sent to my phone (just kept saying Pending). They really couldn't explain why it wouldn't work, just that it wouldn't. Rooting seems to be my best and easiest bet.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
I managed to get SuperOneClick running and was able to root my phone. I think the problem was that I had downloaded multiple versions in my attempt to get it to work and they weren't playing together well.
Maybe it could be a driver incident... check it how to fix it dude.

[TIPS & TRICKS] Common ICS problems

Common ICS Problems
If you plug in USB while your tablet is asleep you will have a SOD​
Installation Problems
Install tips from tlb1961 here and lyricalpapa in post #3
Try not to use any backup's as they cause many problems.
Make sure your using CWM 5.5.0.4 Beta 15 (comes with the nvflash in TeamDRH ICS thread)
On your first boot let it sit for 30-60min (the longer, the better) and then reset.
If all else fails try this
Th3DmaN's G-Tablet Tools for anyone who is having trouble connecting and flashing their G-Table
Speed Problems
Different launchers such as Apex or Nova or any compatible launcher may or may not increase smoothness. There is no problem with installing them on top of the stock launcher as only one launcher runs at a time.
Battery and Power Problems
Your tablet went to sleep and wont wake up, try pushing the power button a couple of times and wait 5 seconds inbetween presses.
Your tablet has completely frozen, try pushing the power button for 30+ seconds. If that doesn't do it, you can leave your tablet alone for a couple hours and try again (may or may not work) or you can wait till the battery dies or if your impatient you can open the tablet up and press the internal reset, it looks like this. Here are some helpful pictures and a video for opening it up. If you have no reset button you will need to disconnect the battery, here's what it looks like. If you do get a SOD do this to help the developers.
Connection & Browser Problems
WiFi not working, try to "forget" the WiFi and re-enter your password. Also can try resetting your router or changing the security. Some say ICS does not like high channels.
If your having market errors, try force closing and clearing the cache in settings\apps\all. If that doesn't work then find every market reference and force close then clear the cache and reset.
Your computer doesn't recognize your tablet, you will need MTP drivers read the ICS rom page again. For Windows XP you need to disable debugging. For linux try Th3DmaN's guide.
Adhoc does not work with this build.
Stock browser seems to lock up after a bit. Possible fix is to disable java. Thanks plastikman
Screen and Sound Problems
1080p on H/W? Use Handbrake and import this profile. Here's the high profile settings for 720p, for those wanting the best quality.
Videoplayers such as MxVideo player, can play H/W video but the sound will need to be changed to S/W.
Icons and text too small? Try using this guide. CAUTION Changing the DPI really messes with the Market.
DSP Manager has been causing slowness/audio problems. Try stopping it to see if that's the problem. You can delete it safely if causing problems.
Game and Apps Problems
Alot of games and apps are not updated for ICS yet so they won't work correctly.
Hulu flash hack here. It should work. Anyone with Hulu can you post your results.MAY NOT WORK ANYMORE
Bypassing Exchange Security Policy try this
Connecting the ICS Mail app to Microsoft's Cloud hosted Exchange services check here
Gamepad support - follow jazzruby's guide here
Miscellaneous Problems
Errors popping up constantly, you need to reinstall again and make sure this time you erase everything.
Nandroid backups, you need to follow this guide
Important Notes
The SOD (sleep of death) we talk about is when the device goes into a sleep mode and there is absolutely no other way out but by pressing the internal reset. This is also called a kernel panic.
We are always talking about roms on Bootloader 1.2 unless specified.
When installing or removing things from the system, it is always a good idea to reset and clean the cache, clean the dalvik cache and fix permissions.
USB problems sometimes are caused by your own computer, you may have to restart/change USB port/change USB cables/check your USB drivers
Windows 7 is the implied OS most are working on, if you have different then ask.
IF I'M MISSING SOMETHING PLEASE LET ME KNOW
Stuff that WILL cause a SOD (sleep of death) causing you to push the internal reset
DON'T DO THESE
If you plug in USB while your tablet is asleep you will have a SOD
If you do get a SOD please do this so the developers can help.
Use the reset button
Don't power the tablet off at all, just use the internal reset button
Don't touch the tab or do anything but logging into adb.
If for some reason you can't open adb, you can use terminal on the rom
At the prompt type:
Code:
su
Hit enter and then
Code:
cat /proc/last_kmsg
If this doesn't work, the easier way is to access it is with a root explorer by going to /proc and then copy last_kmsg to /sdcard (rename to last_kmsg.txt or zip it up in a file).
Copy and paste the results to a paste bin and post the link. If you don't know pastebin then just post the last 10 lines or so.
tlb1961 install guide
Howdy all,
Glad to hear most are having good luck with this newer revision. To those seeing odd issues after install, I would suggest start over from scratch and clean out the gTab prior to reinstall including repartition the internal SDCard. Run the ROM for a bit before installing anything else. If you have a lot of media files on an microSD card then let it sit for a little while. Once the ROM is running smoothly you should then apply the latest the3dman GApps package.
I know it's tempting to try and hang onto old configs and settings, but it will give you a better experience in the long run if all old data is cleared.
Click to expand...
Click to collapse
lyricalpapa installation essentials
Here's some things I do that work for me:
1. Give my tablet time to boot - let G-Mail, Google Maps, and the other apps load in, talk to the mail server, etc. I watch the activity in the "broadcast" symbol and wait for the browser widget to display its bookmarked pages.
2. Follow the dev's install instructions and @serialplague's FAQ - goes without saying.
3. Have Patience - I give the cache driver's balancing and optimising routines time to do their work after I load a ROM, plus any time I add/remove apps or any time I make changes to the settings. Remember this is a Beta Test ROM and not a snapshot image of a fully tested, optimised, and balanced ROM that you would get if you were to buy a new ASUS Transformer or whatever.
4. Use the apps the Dev's gave us with the Beta ROM - I use the Elixir app regularly to check if the CPU and I/O activity levels have dropped down to near 0% for both. I check them after installing my ROM's, etc. (I also now use the Diagnosis app thanks to @oldtimer)
5. Remember the G tablet only has 512M DDR-2 RAM on board and was built to run with a 2.2 Froyo ROM, a cadged 2.6.32 kernel, and slow generic drivers. Google's minimum published specification for a system running Honeycomb or newer is a Nvidia Tegra-2 processor and 1G of RAM. So the challenge is to modify and tune the 2.6.39 kernel drivers and the ICS ROM to live within the available 512M RAM.
6. edit-no longer needed
7. Killing unnecessary apps sometimes frees up enough memory to stop the CPU and I/O churning. But I have to be careful which apps I kill using an app like Advanced Task Accelerator - it can shut down necessary services - although Android will usually restart them automatically (and kick up the CPU and I/O activity while doing so)
8. Remember that Google Apps come with a high overhead price - the standard Viewsonic set-up for the G tablet does not include GAPPs, and it runs very fast. The same for many other tablets that don't have a Tegra-2 and 1G of RAM. Game players might want to experiment with not loading GAPPs. In the past I've done this by downloading all the apps that I was interested in from GAPPs, then copying them all out to my PC using the "adb pull" command ("adb remount" to get in as root). Then I wipe and reload the ROM without GAPPs, and use "adb push" to put the apps in the right directories. Then on my G tablet, I find the apps using Root Explorer and "click" on them to install them.
Lyricalpapa
Click to expand...
Click to collapse
How do I stop my tablet from downloading every app I have ever owned or used from the market when I log into my android account.
I suspect I am doing something wrong because the tablet is very laggy with ICS.
When you first install it will ask you if you want to use your backups, just uncheck that. Or you can let it sit for awhile, 30min to an hour, it sucks but once everything calms down its much better.
Android Keyboard
Good men of this forum,
It seems that with the new ICS rom, I am having issues with my android keyboard. If my tablet is vertical, I have the dialpad-looking keyboard with what seems to be Japanese characters on a few buttons. When my tablet is in the horizontal orientation, the keyboard disappears completely. I have searched the popular forums here and with Google. I'm terribly sorry if I have missed a tip somewhere.
I used the flashing procedure on the TeamDRH website to the letter, and I am no stranger to flashing custom ROMs to android devices. The keyboard continues to work beautifully under Froyo and Gingerbread ROMs, as well as the earliest beta of ICS. I only seem to have an issue with this version of ICS.
I'm also getting frequent Google Apps errors about the services stopping. After signing in with my account, Market crashed and disappeared from my apps menu altogether.
It seems that I have a fairly unique problem. I'm a linux sysadmin and I'm very handy with the command line if you need dmesg or kernel output.
Thank you in advance.
I've heard a couple of people are having problems with the GApps, have you tried installing with the lite 7b GApps?
No Luck
Thanks for the reply!
I have tried both the full and lite versions of 7A and 7B for this ROM with no luck. When I perform a first-time boot of the tablet after a ROM and Gapps, the very first message I encounter is "Unfortunately, the process com.google.process.gapps has stopped" for any version of Gapps, and it continues to pop up every several seconds that the tablet is in use.
I have also tried installing the ROM without Gapps at all and the keyboard is still nowhere to be found. Odd that the keyboard works in the first beta (1E), but this ICS (2B) is much faster than the old one
If anyone has a link to download the ICS Preview 2A instead of 2B I would be interested in trying it out, the links on TeamDRH's website all point to 2B now.
Other useful info: I know for certain that I am running the 1.2 bootloader and I'm using the newest Clockworkmod v5.5.0.4 Beta 15. I like to re-format before every flash to ensure a clean start.
Thats very odd it sounds like the download may have been corrupted. I've seen it happen a couple of people.
I still have 2A and some previous ones, kinda a catalog lol, just PM if you want to go that way.
I'm a newb
Thank you very much for the help you've provided me.
I tried downloading 2B a few more times with the same issue :/ so strange. Unfortunately for me, I am below the 10 post minimum to allow PMs. It's kind of ironic actually, I've been a member for years and always found my answers without having to ask because xda is wonderful about providing info
Thanks again.
Sent ya an email
simplyphp has a great writeup on an installation method you could try his way
SUCCESS!
Using the simplyphp method you referred me to, not only does the 2A ROM work, but the newest ROM and Gapps as well! I must admit that I'm a little embarrassed that I can't actually identify the original problem, but I believe it has something to do with my installation of Clockworkmod. I got it from a forum here that is trustworthy, but it didn't seem to work exactly as I needed it until I installed it with nvflash. I also had a strange problem with the first flash (out of the two that I am supposed to do) in that it wouldn't boot all the way into the TnT factory OS and was in an endless reboot. I simply turned it off, booted into APX mode once again, and continued with the listed steps and it worked flawlessly. I would thank simplyphp but I can't post on development threads yet!
So thank you and have a "Thanks!", I hope I've contributed to your wealth of knowledge on troubleshooting.

[Q] Über-crash = reformat? What to do? thx

Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)
Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*
I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.
JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.
Logs or it didn't happen.
Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.
I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...
Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.

S5 glitching in and out of monitor mode? or just a patchwork mess?

Im new to all this so pay no attention if its nonsence...
My S5 G900f has a qualcomm snapdragon chipset, that doesn't support monitor mode, which i believe means that it doesnt support packet injections or packet capturing (driver related?)
using the dsploit.apk for things like session hijacking, replacing web page images of a target and using script 'injection' to inject custom java script into a target web page, all sounds like things you'd need monitor mode to do. and if it is then i was able to do it with my S5.
I dont know a lot about coding or how it all fits together and communicates with the hardware, so i may sound completely stupid, but this has done my head in for ages, so why not get it out there.
1. when i attempted to upgrade from my first custom rom, i had a bit of trouble, softbricked my phone and then flashed the two roms in various, alternate, wipe, format and install combinations until it finally booted to set up, and i stopped panicking. but this caused features from the first rom to appear within the second rom.
ie: 3minute battery mod was installed through a add-on zip along with the first rom and nothing to do with the second at all.
2. inconsistencies within the file system, like file names that were apps included with the first rom.
3. dsploit.apk was bugged and crashed every 5 or 10 minutes. then would seem to glitch or stutter for a couple seconds before correcting its self and accomplishing its pen test.
4. i also remember watching green text in the terminal as it failed to connect or ID some part of the system but continued to retry in quick succession until it glitched and worked. (i think this was a similar type of app i was trying out at the same time but instead of GUI stutters, i could see the text rapidly stuttering and glitching.)
4. the dsploit.apk worked for me back then, even though it was temperamental. ive downloaded the apk a couple times since with various roms and ive got no where with it...
was thinking maybe different aspects of the two roms had been filed or grouped together and created unstable triggers within the software, allowing it to briefly communicate with the chipset. i may be way off, but ive been sat here waiting for someone to solve this issue forever, i thought id share my thoughts, on the off chance it turns out to be something and i can finally get my S5 into monitor mode without OTG cables and other unwanted auxiliary components.
thanks in advance
G Carter
Do a clean install of you ROM, and please, don't panick. If you want to have a good time flashing ROMs and stuff, panicking is the last thing you want to do, it will cause stress and stress can lead to not being careful enough so stuff like this happens, well, always, if you are experiencing issues do a clean install. Just boot into recovery (I recommend TWRP) and wipe everything except external sd. Open ADB and sideload the ROM (or, if you have enough memory on a flash drive, plug it into your android and flash it from there) and then Google Apps.

Categories

Resources