Related
Hey guys,
quick question. I just picked up a G tab and used Z4 root app. My problem is, everytime I shut off the unit and power it on, for the next use, I lose root and app downloaded apps are gone. Is this a known issue or is there something specific I need to do?
Well maybe you did temporary root ?
I know for a certain fact that after JM6 the z4root wouldnt work well, you might wanna give a go at SuperOneClick.
sedde said:
Well maybe you did temporary root ?
I know for a certain fact that after JM6 the z4root wouldnt work well, you might wanna give a go at SuperOneClick.
Click to expand...
Click to collapse
I try the Z4 multiple times and it was the permanent root option.
Right now it's 100% stock. Where can I get the Super One click?
I just re-booted my VZW Tab and it was rooted with Z4 and it seems to be permanent here. Not sure why yours would not be. Mine is completely stock with root.
siafu said:
I just re-booted my VZW Tab and it was rooted with Z4 and it seems to be permanent here. Not sure why yours would not be. Mine is completely stock with root.
Click to expand...
Click to collapse
Yeah I don't get it at all. The Z4 root app disappear from my list and the new market I installed disappears as well. I have to reinstall both after every boot. Does anyone have any ideas what to do?
Breakthecycle2 said:
Yeah I don't get it at all. The Z4 root app disappear from my list and the new market I installed disappears as well. I have to reinstall both after every boot. Does anyone have any ideas what to do?
Click to expand...
Click to collapse
I would say you should try a hard reset and re-do it.
SuperOneClicker can be found here in xda.
I can also vouch for Z4 permanent root on the Verizon Tab.
I have a real problem I think. Before I go return it, does anyone have a system dump so I can try and reflash this tab and start fresh? I did a system wipe and now Im getting FC in masses. Nothing stays installed and it keeps asking me to log in after every boot as if I just bought it.
I had a similar problem - I couldn't remove anything I had installed to one point and couldn't install anything new. I ran 'dmesg | busybox grep error' in a terminal on it and had lots of errors on the device used for the /data partition. I had to bring it back to verizon and get it replaced. New tab had been fine since then.
-Dan
Problem With Verizon Galaxy Tab
i am having the exact same issue as well. Seams as anyhting you do, it just goes back to the way it was after a reboot.
dragonfire540 said:
i am having the exact same issue as well. Seams as anyhting you do, it just goes back to the way it was after a reboot.
Click to expand...
Click to collapse
So it seems to be a few of us. I guess I'm going back to best buy for a new one.
I ended up returning mine. Best Buy said they've never seen anything like this and there was def something wrong...lol. Really BB?
Editing,,,
Well, it worked flawlessly on my new tab so I guess it was just the defective one. Thanks guys.
OK. I rooted using Z4 I added Rom Manager and some other apps. I wanted to created a back and the tab when back to the original state, I unrooted and uninstall all the apps and rebooted the Gtab but now it bringing back to the with Rom manager FC.... any ideas?
I'm trying to do a hard reset by pressing vol up and power.... it goes into recovery and it stop about 20% I get the triangle imagen and reboots....
Can someone help me to do the right steps?
thanks
I had the issue where rebooting my tab caused everything to revert back to a previous state and giving me various force close messages. This was on a completely stock Verizon tab with no attempts at rooting. I did a full factory reset dozens of times, and every time it went back to a previous state. I posted on here about it a few weeks ago, and no one seemed familiar with the problem. I ended up returning the tab to Best Buy and exchanging it for a new one. No problems since then.
teardropcity said:
I had the issue where rebooting my tab caused everything to revert back to a previous state and giving me various force close messages. This was on a completely stock Verizon tab with no attempts at rooting. I did a full factory reset dozens of times, and every time it went back to a previous state. I posted on here about it a few weeks ago, and no one seemed familiar with the problem. I ended up returning the tab to Best Buy and exchanging it for a new one. No problems since then.
Click to expand...
Click to collapse
Exact same string of problems here. I too returned mine and no issues since.
I bought a refurbished TF101 about 6 months ago. I rooted the device and tried various ROMs until I settled upon "Revolver 4 by Gnufabio | 4.1.1 Stable". Life was good, no random reboots, no sleep of death just great. I then installed a game called "Dead Trigger" that came up recently on the Play store. The game did not load, crashed without a FC message and so I uninstalled it promptly. Then I started getting video corruption on my Live Wallpaper (Blue Skies). Random reboots soon followed. Time to start over.
I used CWM and wiped the tablet from there (data, cache and Dalvik) and reinstalled Revolver. It did not work. I used the EasyFlasher tool to return my tablet to Stock using the Asus provided firmware from their website (.24). It seemed to work well, as I started over with my "new" tablet and synced to my account, etc, etc, etc. But now I can't use it without it rebooting every 30secs to 1min. It will go into a Sleep of Death on a random basis also. I have not installed any programs on it, I tried not allowing a restore of my Google settings and cannot for the life of me figure out what is going on.
I am unaware of the SBK version, as their is no indication on the tablet of its serial. What vital step am I missing here to revive this tablet? Any help would be appreciated.
Thanks
StevieJake
steviejake said:
I bought a refurbished TF101 about 6 months ago. I rooted the device and tried various ROMs until I settled upon "Revolver 4 by Gnufabio | 4.1.1 Stable". Life was good, no random reboots, no sleep of death just great. I then installed a game called "Dead Trigger" that came up recently on the Play store. The game did not load, crashed without a FC message and so I uninstalled it promptly. Then I started getting video corruption on my Live Wallpaper (Blue Skies). Random reboots soon followed. Time to start over.
I used CWM and wiped the tablet from there (data, cache and Dalvik) and reinstalled Revolver. It did not work. I used the EasyFlasher tool to return my tablet to Stock using the Asus provided firmware from their website (.24). It seemed to work well, as I started over with my "new" tablet and synced to my account, etc, etc, etc. But now I can't use it without it rebooting every 30secs to 1min. It will go into a Sleep of Death on a random basis also. I have not installed any programs on it, I tried not allowing a restore of my Google settings and cannot for the life of me figure out what is going on.
I am unaware of the SBK version, as their is no indication on the tablet of its serial. What vital step am I missing here to revive this tablet? Any help would be appreciated.
Thanks
StevieJake
Click to expand...
Click to collapse
The RR and SoD come standard with asus stock FW for most people, there is a new .27 update you could try that apparently fixes things, but it made things worse for me
The serial number is generally on a sticker next to the charger port of the tablet half, B4O > B60 and some B7O are SBK1, after that are SBK2
If you are SBK1 you can use NVFLASH to clean install the OS
I decided on Stock FW Rooted and CWM with PERI, then Guevors Kernel
So far so good, stable for a couple days now
Thanks for the quick reply. I did try the .27 update OTA update after getting back to Stock. No help.
The sticker in question is missing. Unknown SBK. I used EasyFlasher using SBK Ver1 and it worked to install the Stock .24 OS fine.
I will give the Stock FW Rooted a shot and see if that works
StevieJake
steviejake said:
Thanks for the quick reply. I did try the .27 update OTA update after getting back to Stock. No help.
The sticker in question is missing. Unknown SBK. I used EasyFlasher using SBK Ver1 and it worked to install the Stock .24 OS fine.
I will give the Stock FW Rooted a shot and see if that works
StevieJake
Click to expand...
Click to collapse
If the flash worked with sbkv1, then more than likely the unit is sbkv1. Otherwise, it shouldn't have worked at all . As the other poster said, RR and SoD is pretty common with the stock Asus firmware for some people -- you might try returning to Revolver now that you've gone back to stock, and start on Revolver again with a clean slate.
I am also running the same setup as the previous poster, stock .27, rooted with guevor's kernel. Been that way for only a day right now, so I can't say much about it yet.
Okay, so here is what I have done. I first used NvFlash to flash Stock .24 successfully. I then extracted the ASUS .24 firmware file (zip only) to the MicroSD card which the system took as an update and installed over my good work. It works, albeit with reboots still. I at least got it working and will try some more ROMs (Stock .27 first) with the suggested kernel. I just wish I could get back to the stable Revolver I had earlier.
Thanks for the help and suggestions.
StevieJake
steviejake said:
Okay, so here is what I have done. I first used NvFlash to flash Stock .24 successfully. I then extracted the ASUS .24 firmware file (zip only) to the MicroSD card which the system took as an update and installed over my good work. It works, albeit with reboots still. I at least got it working and will try some more ROMs (Stock .27 first) with the suggested kernel. I just wish I could get back to the stable Revolver I had earlier.
Thanks for the help and suggestions.
StevieJake
Click to expand...
Click to collapse
If you used NVFLASH to get back to stock, you could have just let the FOTA update you to .27
Then you can root and so on after that
NVFLASH returns the tablet to factory settings, ie. as it was when you unwrapped it on day 1
Not good. My tablet seems to be in an internal storage hell. Every Rom I try to install will crash with moderate use after booting. I have tried NvFlash, EasyFlash, Wolfs Ultimate flash and downgrade, every variation of stock HoneyComb and ICS I can find. I cannot keep this thing stable beyond 5 minutes of use. I have tried multiple factory resets and wipes, run "Superwipe Full" multiple times and nothing seems to work. What can I do to recover this tablet before I just give up and send to ASUS (god help me) for assistance? Any help would be appreciated
Thanks StevieJ
Ouch. Sorry to hear about your troubles. Horror stories like this have prevented me from diving into the root and custom rom scene with my one and only tab. [I am leaning towards a Nexus 7 when it comes out, and will perhaps root etc when I get that. I feel like it's a safer endeavour with a non-locked bootloader]
I'm interested in finding out what may be causing all this, so I'll be subscribing to this thread. Sorry I can't provide anything more than good luck to you.
Sent from my Transformer TF101
Ouch is right! I have rooted every Android device I have ever owned and this the first I have ever had this much trouble with. I just wish I could say I did "X" to cause it to happen. Oh well, maybe somebody knows something I have overlooked.
Note: I have Rogue XM Recovery 1.5.0 (CWM-based Recovery v5.0.2.8) running fine on the rom and it reboots into recovery okay.
StevieJake
steviejake said:
Ouch is right! I have rooted every Android device I have ever owned and this the first I have ever had this much trouble with. I just wish I could say I did "X" to cause it to happen. Oh well, maybe somebody knows something I have overlooked.
Note: I have Rogue XM Recovery 1.5.0 (CWM-based Recovery v5.0.2.8) running fine on the rom and it reboots into recovery okay.
StevieJake
Click to expand...
Click to collapse
Have you tried running it without the WIFI on? I went to my folks place with mine and it rebooted all the time as soon as it started up. It turned out to be a WIFI issue with the Dynalink router my parents were running.
Cheers, Matt.
hairy1 said:
Have you tried running it without the WIFI on? I went to my folks place with mine and it rebooted all the time as soon as it started up. It turned out to be a WIFI issue with the Dynalink router my parents were running.
Cheers, Matt.
Click to expand...
Click to collapse
Funny you should ask that. I just NvFlashed 9.2.1.24 and was using the tab with no WiFi, no account information and everything worked just fine. I then enabled WiFi to see what would happen and it still worked, but I had not logged in with any account information yet. It still worked fine, as I was able to surf the web with no problems. I then tried to add my account information and started getting crashes using the Play Store, syncing my accounts, etc. It seems to be linked to updating account information and not just WiFi. I will investigate further
Thanks
StevieJake
Adding an account, even a new account, will bring down the tablet. It reboots until it is only a dark screen that requires APX mode (VolUp +Pwr) to rebuild the tablet. I can get into recovery and also factory reset mode (VolDwn + Pwr), but that is it. I'm so confused
I found a CWM backup I had from back in March. It restored fine, but still had problems that resulted in multiple crashes and eventual death again. Oh Bother!!
StevieJake
Fixed it!
Here is what I did. I was always to get the tablet into APX mode (Vol Up + Pwr) so I NvFlashed 9.2.1.24 from this site:
http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/. I did this 5 times, never letting the tablet fully reboot after I got the "success" message upon completion. I then did a data wipe (Vol Dwn +Pwr, then select Wipe Data and then Vol Up, Vol Up) 5 times. I then used the same NvFlash 5 more times and let the tablet fully reboot and entered my Google credentials. I had prepared a MicroSD card with the zip file extracted from the ASUS site that contained the latest firmware (.27) and placed in the root directory of the MicroSD card. The tablet recognized it as a system upgrade and installed the firmware grade with no problems. The tablet rebooted fine and showed the installed firmware. I then did a data wipe as described above 5 more times and then let the tablet reboot fully and once again entered my Google credentials. The tablet now runs all programs without faults, has no video artifacts on the live wallpaper I use (Blue Skies) and is running just great. I am able to update all apps with out errors from the Play Store which was also an issue.
I hope this helps someone to get their tablet back, as I used all the resources on this forum to bring this wacky method to restore my tablet. Thanks to all you unnamed posters for your help
StevieJake
I wouldn't expect flashing the same thing numerous times to have any more effect than the first flash, but if that's what it took for your tab to be re-born, so be it!
Congrats on the fix.
Sent from my Transformer TF101
Not so fast!
Although the tablet did last longer (almost 2 days), it ultimately failed again to an unbootable state. Its back to the drawing board again.........
StevieJake
rootblock said:
I wouldn't expect flashing the same thing numerous times to have any more effect than the first flash, but if that's what it took for your tab to be re-born, so be it!
Congrats on the fix.
Sent from my Transformer TF101
Click to expand...
Click to collapse
It may just be giving up, electronics are stupid sometimes and fail for no reason. I had a brand new HDD that worked for two days, I left the computer off for three weeks and when I turned it back on the HDD wouldn't even spin up :-/ Good luck buddy.
Okay, I'm done. Just got my RMA and am sending this puppy in. Thanks for all the help, I will try to post the results later when I get it back. Glad I made the impulse purchase for the Nexus 7, as I will not be totally without a tablet.
Thanks for all the help again
StevieJake
RMA and back from the Dead!
Well I got it back from ASUS after the RMA. It had a short visit in Texas, was returned promptly and appears to function normally. I never received any feedback from ASUS on receiving the tablet, what was wrong with it, what they did to it or when they shipped it. But its fixed. Running .27 latest firmware and seems to handle everything I can throw at it.
They did a bang up job so far and I am more than happy with their service.
StevieJake
Hello there xda.
I have a Samsung Galaxy Note 4 SM910F.
So what is happening to my phone is that whenever I am in any random app lets say reddit or even chrome for example. It will like freeze for a minute or two and then unfreeze.
In more extreme cases it will reboot.
So this happened randomly because I flashed a Stock unbloated 5.1.1 ROM from here back in december and everything was working smoothly and stuff. I had xposed installed and all my apps. Then in February it started with this random freeze/reboot. I had not installed anything else apart from what I had for the last 3 months.
So I restarted the phone, changed the battery and stuff to see whether that will fix it. However it didn't. So I formatted the phone (the soft type) just so I can install another ROM. So I tried another ROM, flashed the correct CP and BL and stuff and then just installed chrome and whatsapp. After an hour or two the same thing happened. So this time I factory reset he phone, like a complete wipe and I installed the unbloated ROM once again with few apps. Same thing happened...
So my last resort was to install Cyonagen Mod. After an hour or two same thing happened...
I don't know what is the problem. I read about some peoples phones emmc failing and thus the freezing, but I am not sure yet.
Please could you guys explain what I should do to fix this?
Thank in advance!
I have the same problem. Starting on mid january. I'm on stock 5.1.1 with root and twrp recovery
Tried backup and factory reset
I went back to stock after I factory reset the phone. And still had the same problems.
People say that its a hardware problem... So I guess I'll have to send it back to Samsung soon.
I think I tripped the knox. I just have to unroot and get it back once again to stock and send it back. I hope that they accept it.
i have the same problem. my model is SM-N910W8 and I bought it from 2nd hand, so no receipt and no prove of purchase.
can I still send it back to samsung to fix it?
same problem as you and now my phone died completely .
my phone was 4 months and he has not supported any longer he died naturally lol.
my operator gave me another free under warranty because the phone had a faulty motherboard and after several back galaxy note 4
This started happening to me a week or so ago and my phone just got stuck in a boot loop after it froze and rebooted. I'm on the latest stock firmware. Tried factory reset, reflashed stock firmware, nothing helps. It still reboots (sometimes it almost gets booted completely, other times it reboots after 2 seconds.
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
EclipseX said:
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
Click to expand...
Click to collapse
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
HXOY said:
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
Click to expand...
Click to collapse
EclipseX said:
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
Click to expand...
Click to collapse
Spoke too soon, it's started rebooting itself again.
Same problems here since 2 days. I was on original 5.1.1 software... Very strange all those people with the same problems
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Davids said:
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Click to expand...
Click to collapse
Still having the same issue around the same time everyone else started experiencing it.
I also was rooted and had xposed installed on 4.4.4 before the issue started happening.
Try the solution provided here & report back..
http://forum.xda-developers.com/note-4/help/note-4-sm-n910f-freeze-restart-issue-t3439111
Recently bought a new out-of-the box Galaxy S4 I337 from Amazon. Had i known how much trouble it would give me, i would have picked something else. When i first turned the device on, it was almost totally unusable due to lag and random reboots. Software version was 4.4.2. I used Odin to flash a rootable NB1 onto the device. Still had lag and random reboots. Upgraded to lollipop using this guide: https://forum.xda-developers.com/galaxy-s4-att/help/guide-att-samsung-galaxy-s4-sgh-i337-t3383078 and still have lag and random reboots. Also, the first time i upgraded to lollipop, i installed safestrap not knowing it wouldn't work on lollipop. Obviously, my recovery disappeared. When i figured out what was going on, i did a fresh install of lollipop. I got recovery back, but today when i tried to boot into recovery to wipe the cache, i discovered it had mysteriously stopped working again. If i attempt to boot into recovery, it just skips to the Samsung logo. I didn't install safestrap or any other custom recovery this time.
When i turn the phone on, either it hangs at the AT&T white splash logo and refuses to load at all, or advances to the lock screen. I have disabled animations and every widget i could on the lock screen and yet when i attempt to unlock the phone, it usually freezes. If i repeatedly swipe the phone for thirty seconds or so, it unlocks but it is still frozen and i have to continue swiping to prevent it from locking again. Eventually i'm able to navigate the phone normally, until it randomly reboots or freezes. Sometimes i see an error message that Touchwiz home, Process System, or SystemUI has stopped working or is not responding. This is always accompanied by a freeze. Also, choosing an option in the dialogue that comes up when i press the power button (shut down, reboot, etc) invariably causes the device to soft reboot. Other times a soft reboot happens totally at random, even if i'm not doing anything. Anybody have any idea what's going on or did Amazon just sell me a dud? All of these issues have been happening since before i rooted the device or upgraded it, except for the disappearing recovery mode.
Thanks in advance for your help.
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
StoneyJSG said:
Sounds like a data factory reset is in order. First you need recovery back so I would odin the latest firmware for the phone that can be flashed in odin. If it's still messing up then get Amazon to replace it.
Since you have safe strap though, try booting a TW based rom like Thor ROM or Golden eye ROM. That may fix some things.
Click to expand...
Click to collapse
Just wanted to bump this to thank you for your reply. Never got the phone to work but i was able to get it back to stock and return it. I got a refurbished S5 instead.
Hi all,
For the last 3/4 weeks my Moto X Style XT1572 has been randomly rebooting, usually this is when it is not in use and either in my pocket or desk.
I was running AICP and tried a couple of factory resets. This did not help.
I then factory reset and installed Dirty Unicorns (last weekly). Again this hasn't helped. No overclocking, undervolting, just stock kernels and I have tried handbag kernel.
Still rebooting.
Anything else I can try before throwing it in the bin?
Motorola are not interested in repairing due to unlocking the BL.
Thanks
rowlers said:
Hi all,
Anything else I can try before throwing it in the bin?
Motorola are not interested in repairing due to unlocking the BL.
Thanks
Click to expand...
Click to collapse
Flash the newest stock 6.0.1.
Without botloader, gpt, no oem commands(don't lock BL).
You need stock system to recognize: hardware or software problem.
I was going to say that my wife's MXPE has been doing the same thing with multiple random reboots and losing constantly losing all her Bluetooth pairings. But her phone is completely unrooted and OEM Marshmallow OS.
I seem to have resolved the issue by using the Chill governor. Fingers crossed, but I've not had a reboot for 2 days now...
radon222 said:
I was going to say that my wife's MXPE has been doing the same thing with multiple random reboots and losing constantly losing all her Bluetooth pairings. But her phone is completely unrooted and OEM Marshmallow OS.
Click to expand...
Click to collapse
Mine is doing the exact same: random reboots and it loses all Bluetooth pairings and have to redo them. Running TruePure ROM but nothing else so far.
I did a Dalvik/Cache wipe and it calmed down a bit now, it randomly reboots about 1-2 times a week (over it doing it 1-2 times a day) and when it does reboot, so far, it hasn't lost the Bluetooth pairings yet.
Gonna see if I can go back to stock and install the latest updates and then take it from there, when I get a chance to.
JustLok said:
Mine is doing the exact same: random reboots and it loses all Bluetooth pairings and have to redo them. Running TruePure ROM but nothing else so far.
I did a Dalvik/Cache wipe and it calmed down a bit now, it randomly reboots about 1-2 times a week (over it doing it 1-2 times a day) and when it does reboot, so far, it hasn't lost the Bluetooth pairings yet.
Gonna see if I can go back to stock and install the latest updates and then take it from there, when I get a chance to.
Click to expand...
Click to collapse
Moto X Style , Android 6.0 , Not rooted, pure stock, exact same symptoms as you guys with the random reboots while not in use , losing Bluetooth pairings... Did a factory reset, didn't change a thing. Sometimes, I can get 2 days without reboots, then have 2 in the same hour the next day. It sucks. I'm hoping the Nougat update will fix this, if it ever gets released for my version...
Got 1 doing the same stuff, all stock, gets warm, reboot itselfs, wrong date and time, and no bt pairing
Mine is still doing it too. Not as bad as it was but at least once per day, when idle, sleeping it just reboots for no apparent reason. Not ROM, Kernel and I have factory reset.