Related
[TOOL] Revert To Stock ICS for the VZW Galaxy Nexus
OVERVIEW
I have created an all-in-one script that will revert your Verizon Galaxy Nexus to stock ICS (Build IMM76K). I have found some of the 'toolkits' to be awesome resources, but a bit flaky when trying to return to stock. This tool is a self-contained EXE and can be run offline as it does not need the internet during the process to download any supplemental files.
!WARNING!
This process WILL WIPE ALL DATA on your phone! You must manually backup all user data, documents and media before performing this process. I take no responsibility for any loss of data to your phone. This script is clean and has been tested, but as with all online guides, this is done at your own risk. Make sure your phone has at least 75% battery before continuing.
WHAT THIS WILL DO
Reset radio, bootloader, and software to factory versions. Unroot your phone. Remove all settings and accounts. Delete all data/apps and replace system apps with old original ones.
WHAT THIS WILL NOT DO
Relock your bootloader or make you coffee.
INSTRUCTIONS
STEP 1: Make sure your phone is UNPLUGGED from your computer, then download and install the Samsung Galaxy Nexus drivers (VZW)
STEP 2: Download/extract my Revert To Stock Tool for the VZW Galaxy Nexus
STEP 3: Power off your phone, then boot into 'Fastboot mode' by holding down both volume buttons and then the power button until you see the screen with the green "Start" arrow (shown below).
NOTE: If your phone boots up normally into your Android OS, then you did not press the buttons correctly. Power off your phone again, and repeat the process until you see the correct screen.
STEP 4: Plug your phone into your computer and let Windows install any necessary device drivers that it detects.
STEP 5: Once it is finished, run the tool (filename: VZW-GNex-RevertToStock.exe), and follow the on-screen prompts to revert your phone to stock ICS (Build IMM76K)
CONCLUSION
Let me know if you have any questions or run into any hiccups along the way. I am always willing to modify the script or the guide to make it more user-friendly.
NOTE: If you receive any virus alert notifications when extracting or running my tool, then know that they are false positives. My executable is clean.
Thread Updates:
2012-02-23:
Added verbiage describing what this script will/will not do.
crobs808 said:
**reserved for thread updates**
Click to expand...
Click to collapse
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!
CorkyRogers said:
Hi. I hope this doesn't sound too noobish. I just rooted for the first time the other day using the GNex Tookit Ver. 7.8. to the AOKP JB Rom. I have a Verizon Galaxy Nexus.
Basically I need to go back to stock. It was a CLNR phone and thought it was running great for a day until I started noticing a bunch of dead pixels. So I need it back to Stock.
Is it really as simple as running your tool? Also, will it revert back to the original googe apps? b/c im having some issues with apps now on this rom?
1 last question, I understand it'll go back to stock does that mean I lose root and the bootloader becomes unlocked?
Thanks well in advance!
Click to expand...
Click to collapse
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.
crobs808 said:
Yes, this will take you back to the original ROM which includes the original Google Apps (Gapps). Yes, you will LOSE root, but this will NOT re-lock your bootloader. Very good questions - I have updated some of the verbiage in the original post to clarify these points.
Click to expand...
Click to collapse
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?
CorkyRogers said:
Ok cool. If I wanted to lock the bootloader, could I use the toolkit after I've used ur script?
Click to expand...
Click to collapse
If you wanted to lock the bootloader, just boot into the bootloader and run fastboot oem lock. Don't rely on toolkits.
Edit: HA! I just realized what thread I'm in.
Cilraaz said:
Edit: HA! I just realized what thread I'm in.
Click to expand...
Click to collapse
oops?
Zepius said:
oops?
Click to expand...
Click to collapse
Hopefully this is the last question. When I unlocked/rooted I was on build IMM76Q. Would that affect returning to stock?
Zepius said:
oops?
Click to expand...
Click to collapse
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).
Cilraaz said:
No oops, but it is like walking into an Obama rally and shouting how great Romney is (or vice versa).
Click to expand...
Click to collapse
Good thing this isn't a ToolKIT then, just a tool
Not sure why someone arbitrarily rated this thread with "1" star. Kinda uncool, since this will help people.
not working
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.
harshybar said:
It keeps saying echo off, plug in your device. I installed the drivers and still nothing,.
Click to expand...
Click to collapse
Try a different port, or a different computer. Or spin up a VM if you've got one.
Not restarting
Hi! I found this thread linked in the GNex Toolkit 7.8 thread when I was looking for a solution because it failed to flash the stock image & unroot. I followed all the instructions, and pressed enter after fastboot restarted twice, and got to where it says "Flashing stock rom/system". I have now waited 20mins (the tool estimates 5mins), and my phone isn't restarting out of fastboot mode. It has a blue highlighted line on the bottom that says "Fastboot Status - Okay1515.FA02".
Should I keep waiting? re-run the tool? just try restarting my phone manually?
Please help!
Thanks!
Oh! Was running LiquidSmooth 1.5MR1 prior to starting this...no idea if that would still be working or not if I restart now...
EDIT: I got brave - restarting from fastboot manually just restarted Liquid, so it didn't rewrite the system. Some more searching, and I found a different dl link to try for the system image, put it in the right folder, and the GNex Toolkit worked like it was supposed to. I have to say, though, this tool is much less intimidating haha! Thanks!
So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!
mwreeves said:
So, I am in quite the predicament:
First of all, my phone stopped fully booting into the OS. I can get into fastboot and recovery but when I reboot the system it gets to the android screen and then goes black. Second of all, my usb port is broken.
I am pretty sure that there is nothing to be done, but if anyone has any suggestions that would be AMAZING!
Click to expand...
Click to collapse
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.
crobs808 said:
Try a different USB cable and a different USB port. It takes a lot to break those ports on your phone, you may just have a bad cable.
Click to expand...
Click to collapse
I thought that too. I tried 3 computers and 6 cables: nothing worked. It hasn't been able to connect to a computer for a month now and it stopped charging 2 weeks ago. I have looked at replacing the port with a new mic/usb module but the phone still won't boot so it wouldn't really be worth it.
i just did this and it saved my phone!!!! thank you so much
DadamsJR said:
i just did this and it saved my phone!!!! thank you so much
Click to expand...
Click to collapse
You're welcome
crobs808 said:
You're welcome
Click to expand...
Click to collapse
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.
charlie.sears said:
I wish it were easier to find this thread!
You saved my phone after I stupidly pulled the battery during the root process from the toolkit and got stuck in a reboot loop with the Google logo showing and the little unlock icon.
Click to expand...
Click to collapse
Asks mods to sticky it
Hello,
I've been having a problem with my SGH-T989, that's been bothersome. At first I thought it was hunted but it has been turning on instantly when connecting it to a wall charger or USB cable.
I first spotted this problem when flashing SlimKat rom, but soon after that I changed to Jedi Mind Tricks JB8 and the same thing keeps happening. I'm probably guessing it's because I formatted the internal storage before flashing? Maybe I have to change the kernel?
Things I've tried:
- Turned off battery saver option
- Changed roms
- Tried both USB and wall charger
- Connected it while turned off and also while on and then turned off
- Exorcism?
Please help!
If anybody has the solution to this problem, I would appreciate it if you'd share it!
What recovery are you using? I might be wrong or it may be another device i own but i think it's something to do with recovery version....
just to be sure, is the phone off and then when plugging in the charger the phone boots on instead of a battery alert showing that your receiving charge?
minlo said:
What recovery are you using? I might be wrong or it may be another device i own but i think it's something to do with recovery version....
just to be sure, is the phone off and then when plugging in the charger the phone boots on instead of a battery alert showing that your receiving charge?
Click to expand...
Click to collapse
I'm using the latest CWM 6.0.4.3, and yeah it boots instead of showing the battery progress.
im searching but not getting results....i dont wanna say try teamwin recovery but im not expierencing that on 2.6.1....iif my memory right there wasnt a fix but for some reason i think im confusing the bug with my dell streak7
i know it was a clockwork mod version with this bug
i doubt wiping internal storage would cause this, i think boot files are on where your recovery is saved to the device....but i am atleast halfway noob ao i maybe mistaken
when i get to a pc im sure ill find a result....
minlo said:
im searching but not getting results....i dont wanna say try teamwin recovery but im not expierencing that on 2.6.1....iif my memory right there wasnt a fix but for some reason i think im confusing the bug with my dell streak7
i know it was a clockwork mod version with this bug
i doubt wiping internal storage would cause this, i think boot files are on where your recovery is saved to the device....but i am atleast halfway noob ao i maybe mistaken
when i get to a pc im sure ill find a result....
Click to expand...
Click to collapse
Thanks for the hardwork. I have been also trying to find help on the internet and couldn't find anything... that's why I came here!
Help!
what i found which isnt much but try powering down phone first and after power down then plug cable in
edit nvm seen your list lol
.....seems to be intermittant for others and sometimes corrects itself without solution....lots of posts about it but not one single reply of a solution....i searched multiple terms and 10 pages deep to no avail.....
did u manually flash ur recovery or did you use rom manager etc??
maybe reflash your recovery or change to teamwin?
one trend was that it wasn't rom related but in 2011 2012 the trend was asop roms from what i read
have you tried teamwin recovery? Idk thats what i used since i bought my s2 and have not had any issues....
i test booted both ways and had the ability to charge will off....My kids s2's stock unrooted(been slacking) charge also...
2.6.1 is the version I have used, i know there was issues with 2.6.3 but in the dev section i believe it was updated and less problems for some
try using twrp maybe its your recovery
minlo said:
what i found which isnt much but try powering down phone first and after power down then plug cable in
edit nvm seen your list lol
.....seems to be intermittant for others and sometimes corrects itself without solution....lots of posts about it but not one single reply of a solution....i searched multiple terms and 10 pages deep to no avail.....
did u manually flash ur recovery or did you use rom manager etc??
maybe reflash your recovery or change to teamwin?
one trend was that it wasn't rom related but in 2011 2012 the trend was asop roms from what i read
have you tried teamwin recovery? Idk thats what i used since i bought my s2 and have not had any issues....
i test booted both ways and had the ability to charge will off....My kids s2's stock unrooted(been slacking) charge also...
2.6.1 is the version I have used, i know there was issues with 2.6.3 but in the dev section i believe it was updated and less problems for some
Click to expand...
Click to collapse
Prince_Of_Jokers said:
try using twrp maybe its your recovery
Click to expand...
Click to collapse
I'll try using TWRP once I get home. I'll post if it ends up working.
any results?
http://forum.xda-developers.com/showthread.php?t=2240607&page=4
thread with thdude post
6.0.4.4 compiled by thddude, popular dev for s2
http://get.xda-developers.com/XEJ3xBl6gHKahtHBs6e7gw/1391298275/4/1/8/recovery-6.0.4.4-hercules.zip
link for recov
minlo said:
any results?
http://forum.xda-developers.com/showthread.php?t=2240607&page=4
thread with thdude post
6.0.4.4 compiled by thddude, popular dev for s2
http://get.xda-developers.com/XEJ3xBl6gHKahtHBs6e7gw/1391298275/4/1/8/recovery-6.0.4.4-hercules.zip
link for recov
Click to expand...
Click to collapse
Sorry, I came back home and didn't have any internet. But these past few weeks as I was charging my phone it sometimes did stay turned off. I only noticed this when connecting the phone to my car charger. It isn't as functional as I'd like it but it'll work. Maybe if someday I decide to change ROMs I'll try out TWRP and try posting if it worked on this post (just in case somebody with the same problem comes across this post).
Thanks to everybody!
Q&A for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SM-T900] CyanogenMod for Tab Pro 12.2 SM-T900 (v2wifixx). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Rooting Tab Pro 12.2 with last firm done!
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Don't needed. You can root the normal cf-auto-root with latest sock without problem.
After we pm chat last days about rollback to T900UEUAND4 as unique possibility for rooting, i decided to do a last try before that, and luckily works perfect:
-just did a factory reset to restore from B3 recovery i been trying to prev installed T900UEUANI1 stock, wipe caché with stock recovery, odined cf-auto-root and voilá, just rooted!
No need to do the old B3-rollback-prior-D4 method now. Just a normal auto-root with no hassling.
temp maybe?
chhaggerty said:
It sounds like you maybe having a "Sleep of Death" (SOD) issue. The T520 and P900 have had similar problems. I will out of town until Monday but I'll do some research and hope to have a solution soon.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
crpalmer said:
There is a deadlock in Samsung's code triggered by the CPU boost driver. Look in the t520 device repo for the commit that disables it (actually probably 2 commits because I removed some functionality that doesn't make sense for this processor).
Click to expand...
Click to collapse
Dauntless said:
Device: SM-T900
Android: 4.4.2 (Stock, unrooted)
Kernel: 3.4.39-2534013
When putting the tablet into sleep mode, it will automatically shut itself down. When I try to turn it back on, the tablet will only do so after I plugged in the charger. The battery itself is fully charged.
I've updated to the latest available firmware version that's available to me. I couldn't find any list of known issues, so I'm wondering if this is a common problem and if I should return my tablet?
Click to expand...
Click to collapse
Same here. It seems that the problem maybe is temperature: after some time charging it gets really hot and maybe can't awake from that and need rebooting.
I've disabled the magnet sensor vía 3rd app to off the close-lid functionality but don't improve the problem.
Here in summer the room gets to +30°c and the Tab ups to almost 65°c when it gets hot!
Maybe it just reach the temp threshold and self shutdown, or intend that not letting awake.
Perhaps CM11 build here charges battery too fast, with higher voltage than allowed and provoque overheating. I mean, i really feels that it's charging real fast..
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Posted update last night, check it out
Thanks, btw, i was able to use ODIN to get a good version of TWRP and the ROM installed smoothly. I have encountered a few small bugs but nothing to report that is new. I noticed the "sleep of death" I think you are referring to, deep sleep resulting in a manual reboot to wake up. I have noticed my bluetooth disconnects and reconnects every few minutes during deep sleep..not sure why. will report back. Thanks SO SO much for the development, i love it, so sick of the green and blue and the settings tabs on this stock OS disgust me. I am curious tho, am I the only one who noticed significant slowdown and lag compared to stock? I do not put a lot of stock in benchmarks (skewed toward uncle sammy) but they also showed big slowdown....just my very humble and grateful early experiences. Thanks again.
total reflashing needed?
chhaggerty said:
Posted update last night, check it out
Click to expand...
Click to collapse
Well thanks, but,i don't see a flashing update but an entire 221MBs rom to flash..
Can you post just the little update file , if there's any, to flash above the installed rom?
I don't want to install rom, apps and config all over again.
Thanks!
-----
lingarajug said:
Well currently its winter and cold. My tab was cool but it does not respond after deep sleep unless i reboot. Dev said he will look into it and i will wait. Not sure if temp is cause as mine was not definitely not hot.
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
-----
arcadia2uk said:
For rooting the latest firmware, did you use the CF-Auto-Root from the main site, marked KOT49H.T900XXUANB5, or a new one made for the KOT49H.T900UEUANI1? If the latter, would you mind posting a link to a T900UEUANI1 compatible version?
Click to expand...
Click to collapse
Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Reboot from Android with 'reboot to recovery' option and when the TWRP splash logo shows it enter in a bootloop always to this instance that TWRP logo appears.
Then i just installed the good old UAND4 rom and it works fine.
Maybe i shouldn't go to recovery direct from android to prevent bootloop happen and try to go the normal way from boot.
Don't know, maybe I'll try some day.., or maybe better wait to Android L comes to us.
Please advice all that stuff in the respective threads, i can't.., cause' these 'noobs-wait-to-10-posting-before' rules..
Greetings.
bertoxo said:
1. Can you post just the little update file , if there's any, to flash above the installed rom?
2. Yes you are right, i'd tried again and it SODs no matter what temp are. A shame.
3. Well there's a problem right now, seems that this rom prevent to enter recovery.., this is what happen to me:
Click to expand...
Click to collapse
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
arcadia2uk said:
1. You can "dirty"-flash (install w/o wiping) the new ROM over the old one - nothing to re-install - if you wish you could extract the kernel (boot.img) and flash it by Flashify
2. There haven't been reported any SOD issues after flashing chhaggerty's latest ROM version
3. I have had no issues with with TWRP after having flashed the KOT49H.T900UEUANI1 - I just assume that some parts of the Firmware, not touched by cm, has been improved (but since this is WIFI only, it might not be the case for a non phone device) why I preferred to make the update.
Click to expand...
Click to collapse
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
bertoxo said:
1- but dirty flashing the update full rom performs well?
1.2- only the boot.img is needed for update?
3- have you tried the reboot-to-recovery option from android?
Thanks.
Click to expand...
Click to collapse
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
arcadia2uk said:
The changes done between the two versions (99% sure) was only some modifications in the kernel-code. Why flashing the kernel only should be fine, it will resolve the SOD and also make it run cooler. But if you wish you can also dirty-flash. However, cover your bases with a full back-up.
No issues at all with the reboot to recovery option
Click to expand...
Click to collapse
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
bertoxo said:
Can you give me the boot.img update only to try (5MBs)?
220MBs in the posted download site go sooo sloow on any server..
Thanks a lot!
Click to expand...
Click to collapse
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
HERE it is
unzip the downloaded file
place boot.img on your SD
use Flashify to flash the kernel
after this I believe flashify will boot you up in recovery, just reboot and you should be good to go.
Just remember to make a back-up for just in case...
Click to expand...
Click to collapse
Thanks!
Installed boot.img and works flawlessly. Now i can back using lid cover again and no more hangs.
I hope they can solve the auto-rotate thing next time.
flashing screen, powering down...
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
My guess is that gaming need more power, why I would stop greeify and reset the governor to interactive while gaming. But other than that I have no ideas, as I haven't heard of this problem before.
This ROM is fantastic! Smooth, fast, responsive and just as described...big thanks.
spk99 said:
I have twrp 2.8, v2 of our Cyanogenmod, set processor to on demand as suggested...
Still when I play games like CoC and others, if I am not plugged in even with a lot of bat% left, I get a flashing screen and occasionally my tab just decides it needs to shut off.
Any thoughts on what to do? I have greenify and Xposed installed too...
It pretty frustrating.
THANKS GUYS!!
Click to expand...
Click to collapse
I don't know if you noticed, but chhaggerty just released a version 3, maybe this will work as there has been some work on the governors.
chhaggerty said:
New update see OP
Click to expand...
Click to collapse
Can i use the 4.4.4 GAPPS instead of 4.4.3 you are posting?
arcadia2uk said:
Thanks for another quality update, notably when reading how other cm11 exynos versions always seems to break something. With your T-900 cm11, I have never had any issues. The latest version is still running smooth, the changes in the CPU governor will probably allow for better battery life with the added conservative setting. However, I don't know what trade-off this will have on performance.
Click to expand...
Click to collapse
Maybe they start to use the big.LITTLE behavior of the Exynos, instead of ever using just the full power a15 cluster (battery eater).
I've haven't tried it but since it's a 4.4.4 rom they should work fine.
Error flashing ROM
Hi guys,
I get this error message when I try to flash CM11:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
This is a brand new rooted SMT-900 Tab Pro 12.2". Here's some notes:
- I received the error using V1, V2, and V3, all receive the error message
- I downloaded two copies of v3 from two separate mirrors (CA and AZ), both receive the error message
- I did a factory reset and still received the error message
- Wiped davlik/cache/system partitions
- Tried on TWRP 2.7 and 2.8, both receive same error message
- All I have done to this tablet is root it, install TWRP, and create one backup
Any thoughts? I can try using CWM if someone can give me a quick overview of how to install it and remove TWRP (or keep TWRP).
Hi guys,
I have P601 with phone call feature activated and Tab S Beta rom loaded.Kernel is "Xluco P601 - V4-b3". I have this annoying issue;
It is closing itself randomly!! First it was happening while i was using a Poetic Slimline Smart Cover and i thought that magnetic feature causes that. When i had done using tablet and close the cover, after 3-4 hours it was closing itself. And also this is not a normal close !! But then, it start to happen without using magnetic cover !! It was on its 2nd day and battery around %60-70, when i take it in the morning, it was closed again.This time not after 3-4 hours but around 1 day no usage time.This thing was happening with the others roms too (hyronium, custom etc.) and i always do wipe data, dalvik... and clean rom install.
I also observed these;
1- When "this closing" happens, it needs 12-13 seconds to hold power button for opening. (Device always open 5 secs with holding power button , when i turn off it myself normally)
2- When i put charger cable, not indication appears for charging on the screen (big green battery icon with %.. how much juice left).All powerless black screen only.I mean in this weird close mode, even it does not charge.
This situation, i can describe is like a deep sleep or deep close mode .It is a weird and annoying.I think an app may cause this problem but i don't know which one or is it an app actually ?
Can anyone help, who has the same problem or knows about this situation please? Thanks
no one has no idea ??
KpttpK said:
no one has no idea ??
Click to expand...
Click to collapse
You should try to take xulcos kernal off and put stock back on and see if it does the same thing.Alot of people including me have been having that problem of tablet freezing up and having to hold the power button down to make come back on.The only thing we all have in common is that kernal.When i put stock kernal back on the problem goes away.
mikep2323 said:
You should try to take xulcos kernal off and put stock back on and see if it does the same thing.Alot of people including me have been having that problem of tablet freezing up and having to hold the power button down to make come back on.The only thing we all have in common is that kernal.When i put stock kernal back on the problem goes away.
Click to expand...
Click to collapse
Thanks, i will try this kernel change but, xluco kernel has support of ntfs and many more than stock.So it feels bad to bo back :/ Besides custom kernel, could you suggest another kernel for P601 model and also if possible give me a link of it.
Btw i couldn't find custom kernel link to download, it is broken or something about my internet.So if possible a link for custom kernel for P601 too ? I want to try ntfs supported, otg, and other improved settings, different kernel, then i will return to custom kernel.
KpttpK said:
Thanks, i will try this kernel change but, xluco kernel has support of ntfs and many more than stock.So it feels bad to bo back :/ Besides custom kernel, could you suggest another kernel for P601 model and also if possible give me a link of it.
Btw i couldn't find custom kernel link to download, it is broken or something about my internet.So if possible a link for custom kernel for P601 too ? I want to try ntfs supported, otg, and other improved settings, different kernel, then i will return to custom kernel.
Click to expand...
Click to collapse
His kernal is only custom one for our tablets, I have p600 but from all the times I put his kernal on I have same problem. As soon as I go back to stock the problem goes away. There are many others that have the same problem as well.
I see.Then i will return to stock kernel So can you post a link for P601 Stock Kernel please.Because i couldn't find it here.
KpttpK said:
I see.Then i will return to stock kernel So can you post a link for P601 Stock Kernel please.Because i couldn't find it here.
Click to expand...
Click to collapse
I dont have that tablet I have p600 but you can pull the stock kernal from your rom. I use a app called flashify to flash the kernal out my rom. Im heading out but later I show you exact steps to do. Its very easy.
Guys I don't know if there's something wrong with my phone or not. Whichever rom or kernel I try, there is an abnormal shut down of my device. Like I'm using it and I leave it for a few minutes or so and it shuts down. I'm not sure if it had something to do with deep sleep or anything, but I need help. Please guys anyone
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
YasuHamed said:
on custom kernel, random reboots may happend when
1. trying disconnecting whatsapp call
2. trying disconnecting gsm call
can you plug in audio jack to earphone and notice the device? (a strange excersize but worth trying)
Click to expand...
Click to collapse
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
promiscuss said:
Yes, When audio jack is plugged in I did notice a reboot, however, noticed a reboot without it being plugged as well.
Nothing with calls.
I just let my phone sit for a while and it shuts down. I have to power it up again. When I'm using it continuously it doesn't do that. That is why I'm skeptical if it is related to deep sleep somehow.
Click to expand...
Click to collapse
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
YasuHamed said:
lets step back for a moment
if you are on MIUI10, or Miui 9.6.x
do you experience the same with your phone? if yes then you should take it up to the dealer and have it replaced. if such doesnt happen on MIUI then its some APP conflicting with your rom or kernel. try to list / think all such apps which may have given root access indefinately.
whatsapp on custom rom makes device act funny ( I experienced it many time) so does few repost apps (instagram)
Click to expand...
Click to collapse
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
promiscuss said:
Actually I'm not using miui since I unlocked my BL and it had been months since I've been using custom non miui roms. This just started recently. I get what you're hinting at, but I don't think there's something wrong w the hardware but I can't be too sure.
Anyway, yes about the apps, it did occur to me that this might be the case. So I simple wiped my device internal(don't use sd card) and wiped all system, data and everything to install a new custom rom. After setting it up, I left it for a few moments and it shut down again (had not yet installed any of my personal apps, just the regular gapps
Click to expand...
Click to collapse
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
promiscuss said:
Has been an entire day since it happened again, I've turned on 'Always on display' to just keep a lil activity on device so that it does not shut off, maybe that did it. I'll try one entire day without always on display
Click to expand...
Click to collapse
sir, which custom ROM + kernel + anrdoid version are you on ?
YasuHamed said:
sir, which custom ROM + kernel + anrdoid version are you on ?
Click to expand...
Click to collapse
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
promiscuss said:
Previously I was on AEX pie with derp and now on Havoc 2.0 modded with derp as well.
Click to expand...
Click to collapse
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
YasuHamed said:
Could you try
https://forum.xda-developers.com/redmi-note-5-pro/development/rom-aosip-8-1-t3804473
on
https://forum.xda-developers.com/redmi-note-5-pro/development/insigniux-kernel-t3835939 (kernel)
?
Click to expand...
Click to collapse
Thanks for all your effort, the problem seems to have resolved on its own. I'm not sure what it was.
now it's happening to me but it's much more severe. First it started slowly now it's so frequent that the phone might shut down even on boot. This is really frustrating.
I had the same problem with my redmi note 7, flashed stock rom with MI flash tool, fixed everything for me