Related
Tried searching the forum but couldn't find anything similar.
I rooted my ideos x5 with super one click, installed clockwork mod (perfect recovery by genekolar) and then installed genekolar's newest cyanogenmod [unofficial]. Tried installing 2 times with different downloads, wiping everything both times but I get no service or battery status. I checked my sim card, battery, booted the phone multiple times and checked my APN settings, the phone just doesn't find anything.
I would like to have gingerbread on my phone without installing the official one.
I also tried the MIUI rom but it stuck to the booting screen blasting that welcome jingle full volume every 3 seconds.
Any solutions?
Thanks!
This has been written for 1000000 times. You must update to official 2.3.5 if you want to use .35 kernel ROMs. If locked bootloader is what scares you then you dont need to worry because blefish already found a way to unlock it (http://forum.xda-developers.com/showthread.php?t=1457490). If you still dont want to update to offcial 2.3.5 then you can use .32 kernel ROMs
Oh, my search-fu wasn't good enough this time. Being noob 'n all. Thank you for informing me! I'll change this to solved and leave it here if anyone else is having the same problem
Thank you!!
The Official OTA 4.0.3 ICS update broke auto rotation. The rest of the thing is running smooth as butter, but no auto rotation and the switch isn't doing anything.
Anyone know of a fix to this? I had this prob with the leak but after rooting and reinstall leak from scratch it cured itself. This one isn't doing that.
Is there an app to set the orientation of the screen manually that i can use in the interim??
------------------------------------------
400+ Views later, i think quite a few people have this issue and are trying to find a solution to this.
So far, thank you networkdawg for your app suggestion for manually rotating the screen, however that is a paid for app with a few too many options for my need. I'm currently using Mantano Reader Free to rotate my screen.
https://play.google.com/store/apps/details?id=nl.fameit.rotate
------------------------------------------
Before i accidentally upgraded to the ICS leak, i had my old HC bootloader and was running Lightspeed flawlessly.
Does anyone know of a way to downgrade the bootloader back to HC so i can run a custom bootloader?
OR
a custom bootloader for ICS?
------------------------------------------
Ok so in the end i used jazzyjames' tutorial and blasted HC + HC Bootloader back onto my tab (accelerometer now working once more), rooted, ran Acer Recovery Installer and loaded Light Speed ICS once more.
Everything is working swimmingly. No issues and i got ICS running like a champ.
When the hardworking devs in the dev section have streamlined the ICS bootloader unlocker and installing of a custom recovery a little further, i may try the ICS bootloader once more. But for now, to just have a functional tab, im sticking with the old stuff a little longer.
Thanks Civato, Blackthund3r and jazzyjames for their excellent tools and tutorials. I could not have done it without their help.
------------------------------------------
Update May 08 2012
Did something new, reverted back to stock 3.2.1 (the Gen 2 that was used in Jazzy's revert tutorial), did an OTA upgrade to ICS Official. On first run everything worked.
The minute i rebooted, the accelerometer stopped working.
Followed Civato's tutorial down to the letter, got the custom ICS bootloader working with recovery. Ran like a charm.
Installed a custom ROM (Lightspeed), accelerometer was still not working.
MY TAKEAWAY ---- The accelerometer issues is not a problem with ICS itself, but related to the new chipset firmware and bootloader included with the ICS update. I could be wrong here.
Anyone have any other insights into this?
Back to HC bootloader once more (accelerometer working again) no dice with ICS bootloader :S
I'm not aware of any apps that will switch orientations, only lock it.
Have you tried switching the lock to off then rebooting to see if that resets it?
I have noticed the orientation check isn't as sensitive as it used to be so sometimes I have to wait a few extra seconds or orient the tablet a little more [than usual] to get it to switch over. But it does work.
I have the rotation problem also. As a workaround, I installed this and it works great, although manually.
https://play.google.com/store/apps/details?id=nl.fameit.rotate
veer01_42 I'd be interested in your review of that app if you use it and/or pay for it.
I have the same issue. I have a couple apps that are orientation locked and I can use them to rotate but it's very annoying. Hope this gets fixed soon
anyone try a factory reset to see if that fixed it
A factory reset fixed it for me
Sent from my PC36100 using XDA
Been factory resetting this thing all night, no beans at all.
With the 4.0.3 leak, after one reset it worked for me, but i never got it to repeat again. So don't go factory resetting your tab in a hurry if you know whats good for you, especially if your rotation is working.
Good app, lots of options, but for what i want, this app is too much and it puts an icon next to the clock for quick access, but you cant preset the orientations there. There are only three, locked, auto and whatever you have it in now.
To get to the other options, tap the notification and it brings up a menu with all the other orientations (over 10 of them) its too much for me. But its an extremely powerful app.
Not worth the money as a workaround to a stupid accelerometer.
Encountered the same issue. I was in Portrait mode, playing Draw Something, and suddenly it just rebooted and went into Landscape mode. After a factory reset, it is not fixed. Not sure where to go, but this is highly disappointing for a tablet I paid close to $500 for...
Try wipe cache, it works for me. All said methods in the forum doesn't work for my tablet though.
qpmzal said:
Try wipe cache, it works for me. All said methods in the forum doesn't work for my tablet though.
Click to expand...
Click to collapse
What cache?
Do you mean Pwr Button + Volume Up while toggling screen lock switch?
Or is it something else?
On some a500 that were rooted and accepted the ics ota, a few things got broken during the upgrade. Flash a stock rooted ice rom, but before you do go into recovery and and select backup an restore,click on toggle backup of internal storage. Then you should see enabled on the screen. Then do full reset in mounts and storage plus your normal wipe. This will fully format everything on your tab but sd . When you reflash the new ics rom everything should work fine.
You miss 100% of the shots you don't take....... ..Wayne Gretzky.......
Flash a stock rooted ice rom
Click to expand...
Click to collapse
You mean the 4.0.3 Leak, install that and then use the one click root tool available in the forum?
but before you do go into recovery and and select backup an restore,click on toggle backup of internal storage.
Click to expand...
Click to collapse
Are you talking about Installing the V3 ICS recovery or the original honeycomb?
Then you should see enabled on the screen. Then do full reset in mounts and storage plus your normal wipe. This will fully format everything on your tab but sd . When you reflash the new ics rom everything should work fine.
Click to expand...
Click to collapse
This is in the ICS V3 custom bootloader/recovery right?
variations on problem for different versions
More pieces to the puzzle.
I just downloaded and installed Acer_AV041_A500_1.041.00_WW_CUS1 (very close to stock OTA, but rooted) from XDA and applied it over the stock OTA I had received from Acer directly, Acer_AV041_A500_RV05RC01_PA_CUS1.
Under Acer_AV041_A500_1.041.00_WW_CUS1 screen rotation (and the error 26's) would not clear. I could not get the rotation to work at all, even with multiple reboots, and hard (pinhole) resets.
I restored to Acer_AV041_A500_RV05RC01_PA_CUS1 and rotation is back to it's unstable self, but at least a pinhole reset will clear it.
Hi, hoping someone can offer some advice/help here. First, my setup:
A500 with the v7 Bootloader, Thor's R169 Rom, Recovery 1.7.3 all of which are working just fine.
The problem I have, is the auto-rotate function does not work. I have tried all the suggested fixes I can find on both here and the Tegra Owners forums (and indeed every other link I can find through Google) and none of them work. I have also checked that the hardware switch is OK and it is functioning as it should. This problem has only appeared since installing ICS and applies to any Rom I try, with the auto-rotate not working in any Rom, or with any bootloader.
I have, of course, tried different bootloaders, different roms, full wipes, full formats of all partitions, factory resets, the pinhole reset and a number of different auto-rotate applications from the market. None of them make the slightest bit of difference and auto-rotate continues to be non-functional. Logcat shows continual "MLUpdateData error (code26)" errors with the hardware switch in the on position, and when I then switch it to the off position, shows "Error: illegal state transition from ML_STAT_SERIAL_CLOSED to ML_STATE_DMP_OPENED", followed by "vendor/3rdparty/Invensense/libservers/mlsdk/mllite/mldmp.c|MLDmpStop|161 returning 25
I am satisified from using a program called AdvancedTools from the market, that the sensors are functioning and responding to restart requests, although restarting the sensors using this app still makes no difference. Auto-rotate remains non-functional and nothing I have tried seems to change that.
To a layman like me, it seems like it may be a driver issue or perhaps a kernel issue. Anyone here able to help at all please ?
Hmmm....
60+ views and not a single response. Is it fair to assume that nobody has any idea what is causing this ? Am I the only person seeing this issue ?
phlashbios said:
60+ views and not a single response. Is it fair to assume that nobody has any idea what is causing this ? Am I the only person seeing this issue ?
Click to expand...
Click to collapse
I have the same issue, I do not know what to
Same issues here...
Take a look here:
http://forum.xda-developers.com/showthread.php?t=1690905
The only way that worked for me so far is:
Turn the auto rotation switch off
Power off
Power on
Put the auto rotation switch on
If I turn off the tablet with the switch ON none of the sensors works and you'll have to try a lot of times to make it work again..
Other users solved the problem:
- installing a HC bootloader
- Installing ICS V4 bootloader
- Performing real format before flashing the rom
Let me know what you've tried, we must find a solution!!!
OK, here's the current situation. I installed a stock HC ROM (Acer_A500_4.010.38_COM_GEN1) but left the v7 Bootloader still in place. ROM booted fine and works, but still no sensors working.
I then reflashed the Bootloader with a stock HC Bootloader and all the sensors work again.
This is clearly a Bootloader issue by the looks of it.
I am currently upgrading the Honeycomb 3.1 ROM as an OTA to 3.2.1 and will then update all apps, check all is working again and if so, install the Acer Update Updater and then do the OTA upgrade to ICS and check if all working again on stock ICS. Will report back later as to how things go.
OK, latest update following on from above.
Installed the Acer Update utility from the Marketplace
Updated OTA to stock 3.2. No issues, all working including sensors.
Updated OTA to stock 3.2.1. No issues, all working including sensors.
Updated existing systems Apps to current versions. No issues, all working including sensors
Updated OTA to stock ICS. Tablet boots, all OK and working, including sensors.
Reboot tablet, get a brief message that says Bootloader updating and then it boots into ICS. Sensors now stop working and no amount of fiddling with the rotation lock or factory resets or pinhole resets will make the sensors work again.
This to me is clearly an ICS Bootloader issue ? Anyone disagree ?
How on earth do I/we get this fixed ?
Well, after many hours of messing about, I have managed to get Thor's R169 ROM working and with the sensors working too. It has however required the use of the HC 3.01 Bootloader to have the sensors still working.
For the benefit of others who are facing similar difficulties, can I suggest the following course of action:
Install the APX drivers if you haven't already got them on your PC.
1. Put Thors ROM and Gapps on your SD card or on the Tab's own internal storage
2. Downgrade your existing setup to the unstable 3.01 Honeycomb
3. Use the AfterOTA v1.7 tool to install CWM on the old Honeycomb setup.
4. Boot into CWM Recovery and do the usual Factory Reset and wipe everything you can, including the Flexrom, Dalvik etc.
5. Install Thors ROM from your SD card/storage
6. Install Gapps from your SD card/storage
7. Reboot the tab into normal mode
Voila ! A working Thor ROM with working sensors.
What all my efforts tell me is that there is an issue with the ICS Bootloader and some tablets. Whether it is causing a race condition and not giving drivers time to start up, I am not sure, but restarting the drivers for the sensors makes no difference once the ICS Bootloader is installed. Any ICS Bootloader, including the stock one and all of Skrilax's from versions 3 through to 8, all result in no sensors working for me. This is clearly nothing to do with Skrilax, it is something inherent in the behaviour of the ICS Bootloaders.
For people using ICS ROM's other than Thor's, you will need to check whether they will behave with a HC Bootloader before installing them.
I can only pray that Thor and others continue to release ICS ROM's that are compatible with HC Bootloaders while someone, hopefully is able to figure out what is causing the ICS Bootloader issue.
Thanks all for those that offered advice and guidance. Your help is and will continue to be appreciated.
I am aware that references to Thor are not welcome in these forums. As I have not provided any links, or posted any attachments, I am hopeful that the mods here will see that I am trying to both seek help and indeed offer help to others rather than cause any issues. It could be any ROM this applies to, it just happens to be Thor's I am using.
use same rom thor169 bootloader v3 never botherd to upgrade to 4-5-6or 7
on mine rotation works with a ics v3 bootloader
Hmmm... that's very interesting, because mine definitely does not. My sensors do not work with the stock ICS Bootloader, or any of Skrillax's from v3 --> v8
I have also recently had some problems in this area. Started out as auto-rotate sticking whenever using an app that forced portrait. Then this morning went to flash v170 after being on flex rf1 v3 and auto-rotate quit completely. Tried twice with no luck. Over the past couple of days I have done multiple complete wipes and data formats. Did this again and did not work. So I restored a v169 backup and everything fine again. Flashed v170 and it's working fine. Possibly restoring to an older backup that worked (even if it was honeycomb) might help you. Oh yah, I was on bootloader v6 through all of this.
Hi all,
i has the same problem, sometimes works and sometimes not. now i have the v8 Bootloader, Recovery 1.7.3 and Tegraowners ICS ROM v170.
any ideas?
If you install a HC 3.01 Bootloader, I am pretty confident that will fix it, however, that's not really the answer to the problem, it's just a workaround. So far, nobody with the necessary skills seems to be interested in sorting out what's causing the problem when using the ICS Bootloader.
phlashbios said:
If you install a HC 3.01 Bootloader, I am pretty confident that will fix it, however, that's not really the answer to the problem, it's just a workaround. So far, nobody with the necessary skills seems to be interested in sorting out what's causing the problem when using the ICS Bootloader.
Click to expand...
Click to collapse
No one with the skills has the problem.. no one with the problem is providing real debugging information. (a logcat + dmesg just after boot might give a hint)
Many experience installing an ICS rom with the unlocked bootloader, and having the rotate fail on the first boot; however ensuring rotate is not locked and rebooting solved it for most users (and it never shows again).. If after this reboot its still failing you need to provide the logs above if you want a dev to have any chance.. and provide info that we are sure you have done this reboot. (and not just blindly downgraded to HC or another rom)
Also it helps to be sure what rom is being run..
ezterry said:
No one with the skills has the problem.. no one with the problem is providing real debugging information. (a logcat + dmesg just after boot might give a hint)
Many experience installing an ICS rom with the unlocked bootloader, and having the rotate fail on the first boot; however ensuring rotate is not locked and rebooting solved it for most users (and it never shows again).. If after this reboot its still failing you need to provide the logs above if you want a dev to have any chance.. and provide info that we are sure you have done this reboot. (and not just blindly downgraded to HC or another rom)
Also it helps to be sure what rom is being run..
Click to expand...
Click to collapse
Reset doesn´t help.
E/Sensors ( 144): MLUpdateData error (code 26)
I/ActivityManager( 144): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=org.jtb.alogcat cmp=org.jtb.alogcat/.LogActivity bnds=[784,52][880,148]} from pid 366
I/dalvikvm( 1348): Turning on JNI app bug workarounds for target SDK version 11...
E/Sensors ( 144): MLUpdateData error (code 26)
I/ActivityManager( 144): Start proc org.jtb.alogcat for activity org.jtb.alogcat/.LogActivity: pid=1348 uid=10108 gids={1007, 1015}
D/OpenGLRenderer( 366): Flushing caches (mode 1)
E/Sensors ( 144): MLUpdateData error (code 26)
D/OpenGLRenderer( 366): Flushing caches (mode 0)
E/Sensors ( 144): MLUpdateData error (code 26)
E/Sensors ( 144): MLUpdateData error (code 26)
E/Sensors ( 144): MLUpdateData error (code 26)
E/Sensors ( 144): MLUpdateData error (code 26)
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
first off i'd like to mention this phone was 100% perfect on stock Samsung rom 4.2.2 using Ktoonsez KT-SGS4 kernel for many months, until the day I installed this dreaded MDOB 4.2.2 rom and the "fix" that came with it
everything went bad on me back while I was running 4.2.2 stock unlocked boot loader and could never get it back to normal so this isn't a issue caused by 4.3 knox or 4.3 itself that i'm currently using. (i'm stuck on 4.3 roms but had this issue way before 4.3 existed)
i'm having an extreme amount of issues AFTER installing the MDOB rom, even after changing rom back to stock (flashed back to stock rom with ktoonsez kernel which is what I was using before I installed MDOB rom and phone has been royaly screwed ever since that day) more specifically I think it happened from the "i337M fix" that's included with the rom, either way after installing this rom I've never been able to get my phone back to normal.
everything runs fine except until I install a custom kernel (Ktoonsez KT-SGS4 kernel) then all hell breaks loose.
I don't blame the kernels or my current rom since I've ran this before for many months until the day i installed MDOB rom on my phone my phone was a dream machine.
issues since this rom has been installed include:
Issues:
A. RANDOM SLEEPS OF DEATH (phone shuts off or freezes)
B. random freezing while trying to turn on phone or enter recovery
C. some kernels won't work proper (specifically ktoonsez KT-SGS4 kernel) example gpu stuck at max while idle and downclocking when screen is touched with this kernel
D. wifi won't work with custom kernel on stock 4.3 rom without build prop edit to ro.securestorage.support, although it should
E. weak wifi and mobile signals
F. bad battery life
G. bad call quality
H. More that I can't remember off the top of my head
here's my flashing process, in attempts to remove as much as possible:
I know a few of these steps are probly pointless but hey can't blame me for trying.
step 1. enable usb debugging & unknown sources
step 2. install root & recovery
step 3. fresh boot phone let files settle so they can save (5mins or more) then plug into computer while turned on and delete everything
step 4. reboot into TWRP recovery (version 2.6.3.1) and clear everything, full advanced wipe, factory reset, format data than clear cache/dalvik afterwards just to be sure
step 5. remove SD card plug into computer and format to make sure there's nothing
step 6. install rom
step 7. (sometimes) clear cache/dalvik/permissions after rom install, although fix permissions seems to break my permissions rather than fix them or maby my permissions just break during flashing and I just can't fix them (haven't tested enough to be 100% sure)
i'm SOOO temped to try a full nand erase since i noticed there ARE still lot's files on my phone directory even after wiping, but i know that isn't a good idea;(
once stock kernel is back on my phone these issues are all gone.
Ktoonsez says it's not his kernel (used to work before, so i have no reason not to believe him), he says it's the rom well i'm on 100% stock Samsung rom (exception of kernel) and the rom was built to act the way it does so you can't really blame the rom so who do i blame??
until i went to go try wicked rom and flash back to stock I didn't realize these things were still on here, but now they emerge! wicked rom was giving me some (unrealated?) issue so i decided ima go back to stock so i flashed stock rom via odin (pc) and right away i noticed the 4G symbol, Samsung wallet, desktop not setup proper (no shortcuts) this ONLY happens when switching from wicked rom to stock rom on the first flash, i flash again everything looks how it should, and in order to get it to do this again i have to flash back to wicked rom and flash stock rom again and BAM it happens.
i knew my issue started on the same day that i installed this MDOB rom but after doing a full wipe and MANY "fresh" stock rom installs later i stopped questioning the rom and just lived with a crap phone that reboots itself all the time and has bad battery life, AS SOON AS I SEEN THE SAMSUNG WALLET bam it hit me like a truck, IT WAS THE MDOB ROM INSTALL.
UNLESS stock Samsung rom comes with wallet preinstalled and hidden on stock/wicked roms than the ONLY other way it coulda got on my phone is from the MDOB rom.
I can wipe/delete/factory reset/flash with twrp & odin on pc all I want, my roms are still messed up after FRESH installs. I believe there is still left over files from this rom/fix, I didn't think there would be anything until I noticed when i'm flashing from wicked rom back to complete stock rom using odin on pc I experience things from MDOB rom (while It should be 100% stock after odin (pc) flash, but it's not)
after the first flash from going from wicked rom back to stock I always experience the following "bug" i'll call it a bug since these things ALL HAPPEN AT THE SAME TIME: once I flash AGAIN all these symptoms go away until I go back to wicked rom and flash back to stock rom than right there after this first flash going from wicked rom BACK TO stock ALL these symptoms come back until I flash stock firmware AGAIN, a second time (even though I just flashed it)
Symptoms:
1. Samsung wallet appears in my apps (this was only EVER on my phone once, when I had the MDOB rom on my phone), this thing shoulda never somehow appeared back on my phone in any way shape or form after ditching the MDOB rom, but again is comes back after the first flash going from wicked rom to stock rom.
2. I get the 4G icon from MDOB rom (not the LTE icon I SHOULD have while on stock, when on wicked rom I have a little LTE icon with a tiny 4G above it, the only time I've ever had just a 4G icon (without LTE) like this is when I had MDOB rom on my phone (which is the only other rom I've run other than wicked rom and stock rom).
3. this icon ONLY shows up after the FIRST flash from wicked rom back to stock, once I install stock AGAIN than it returns to it's normal LTE icon.
4. now i'm not just *****in about an icon here, this is just a part of my problem (indicator if you will), when my rom is "bugged" after first install from wicked rom to stock rom my wifi works normal how It used too. but once corrected (flashing again) AND using custom kernel on STOCK firmware it breaks my wifi 100% broken until I use this little build prop edit fix, set ro.securestorage.support = true to false, bam wifi now working but the rest of my problems are still there (wifi used to work 100% on custom kernels and everything until MDOB rom touched my phone and left this "bug" behind)
5. when this 4G icon appears after this "first" flash back from wicked rom to stock rom I also experience something else, my wifi button works during first boot setup and auto enables itself and I have no issues with my wifi connecting (as soon as I see this toggle on I already know once my phone locks onto the network it's gonna give me a 4G icon and not an LTE icon like it should and sure as shiznit it does, as soon as I get my icon back to how it's supposed to be (LTE icon) all of a sudden wifi won't auto connect on a first boot anymore, never, 100% never. (back before installing MDOB rom I used to auto connect 100% of the time on first boot) like it does now only when it's "bugged" out.
6. apps are missing, when this "bug" appears there's no app shortcuts on the desktop of my phone by default after fresh flash like there should be, sometimes they appear on first flash once in awhile (some apps might not even be installed? or just shortcuts missing, have yet to verify)
7. it feels like the phone flashes way too fast (second flash takes longer, I think?) and more/all? apps get installed on second flash, and Samsung wallet get's REMOVED (how'd it even get there? other than bein left behind from MDOB rom, same with the 4G icon, that icon isn't in either of the two roms I use so how does it get there? and ONLY at the same time the wallet magically appears and the rest of this stuff)
8. when this 4G icon appears my phone seems to be great except for the fact that I know my rom didn't install properly since i'm still missing apps ect, once I flash again, apps appear, Samsung wallet DISappears, 4G icon gets replaced with LTE icon and everything is A-OK until custom kernel is installed, remember this is NOT the kernels fault as it ran 100% perfect for many months ON THIS PHONE until the day this MDOB rom was installed, and it's had these issues ever since.
some of the things I've tried:
- Countless wipes, including full advanced wipe, restore to factory, data wipes
- Ton's of fresh installs of BOTH versions of 4.2.2 - now doing same with 4.3 and wicked rom 9.1
- Tried wiping using TWRP and odin mobile (flashed mobile odin via TWRP, it works incase anyone didn't know)
- Tried flashing roms using odin (pc) v1.85, v3.07, v3.09
- Downloaded new copys of roms from new sources to make sure my roms weren't corrupted in anyway
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Amb669 said:
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Click to expand...
Click to collapse
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
hednik said:
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
Click to expand...
Click to collapse
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
I've flashed his rom on and off. Never had the issue. The rom doesn't invade anything a full wipe wouldn't cure. If it doesn't full wipe then it's the recovery. It helps once in awhile if you Odin back to stock or even copy your sdcard contents and format your sdcard to make it fresh. read up on it first.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
Also I recommend doing 9 wipes when swapping roms. It sound ridiculous I know but I do it and have never had issues.
Sent from my SGH-I337 using Tapatalk
Amb669 said:
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
Click to expand...
Click to collapse
Just odin back to stock and set if that clears things up. It should solve any odd problems. The thing with flashing rom's is that someone's issues cannot always be replicated.
Going back to Odined stock will take it back to factory stock then do a factory reset in stock 3e recovery and you should be fine
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
dude...I just got the N6P and ran CM13 within hours. This is what I did...
unlocked the bootloader
downloaded the lastest (MTC19X) image off of https://developers.google.com/android/nexus/images and unpacked it into the C:\Program Files (x86)\Android\android-sdk\platform-tools folder
ran the flash-all.bat
fastbooted TWRP
installed CM13. (didn't wipe internal storage)
installed arm64 open Gapps pico
BAM!!!
right now running stock kernel. it's cool. I'm PrivacyGuard-ing the hell out of all my apps (turned off START AT BOOT and KEEP AWAKE for almost every downloaded app), though, so battery is OK
also using Kernel Adiutor but underclocking values for the CPUs doesn't seem to stick
So it likely worked for you since you had flashed the newest vendor.img first. Apparently there are compatibility issues with certain features that cause them not to work (such as WiFi) if you're using an older one.
chaoticyeshua said:
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
Click to expand...
Click to collapse
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
kaufikauf said:
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
Click to expand...
Click to collapse
Very much so. I appreciate it!
Has anyone encountered the constant popup of the Select Sim Card message? I'm using project fi and I am still unable to find a solution to this issue.