[Q] 5.1.1 causing random restarts - Nexus 5 Q&A, Help & Troubleshooting

Hi all, im new to this forum
I just installed 5.1.1 on my Nexus 5 (clean: not rooted, no ram boomers or other things) and now it keeps restarting.
- After install and optimization everything went well for 30 mins, then it started restarting and failing to do so like 15 times before having success (vibration and first google display, then again and again)
- Every 1-2 mins, it does the same
- A couple of times it made a new optimization of the update (from 1 to 139 beats)
Never had problems with previous versions of Android.
Memory is 700 MB free.
I don't know what may be causing this and what could i do
Help pls
Thank you

Hey,
I had that problem too, try to install xTraSlim. You wont miss anything from Stock. In fact you dont gain anything from Stock. Exept the Sound Mod - it uses the Speaker on top thats meant for calls for any Sound or Music too. And its really loud and sounds very good.
Of course you have to root first, but that shouldnt be hard. Well, it maybe is because you got it unrooted, but I guess, or hope better to say that you got a custom recovery installed, so you can flash the newest SuperSu.
Here are the links:
xTraSmooth/xTraSlim Page
xTraSlim Download Link
SuperSU Beta 2.49 (Dont worry, there is no unstable root, either its rooted or not. Also it works fine for me)

xXDanielHDXx said:
Hey,
I had that problem too, try to install xTraSlim. You wont miss anything from Stock. In fact you dont gain anything from Stock. Exept the Sound Mod - it uses the Speaker on top thats meant for calls for any Sound or Music too. And its really loud and sounds very good.
Of course you have to root first, but that shouldnt be hard. Well, it maybe is because you got it unrooted, but I guess, or hope better to say that you got a custom recovery installed, so you can flash the newest SuperSu.
Here are the links:
xTraSmooth/xTraSlim Page
xTraSlim Download Link
SuperSU Beta 2.49 (Dont worry, there is no unstable root, either its rooted or not. Also it works fine for me)
Click to expand...
Click to collapse
I can't start it at all now. I cant even use the recovery mode. It seems like if the start button is being pressed again and again, when i manage to start the recovery mode i can't move up or down in time because it "presses" the start button

It isn't for me

@Arlecchin0

Related

[TUT][HOW TO] Netflix On Galaxy S 4G + Problems Encountered

You need to flash your device for it to work!
This is the Rom I used to get netflix working
http://forum.xda-developers.com/showthread.php?t=1131230
I recommend to use Titanium Backup, this Rom is Rooted but i can not get CWM working.
Netflix app used with the Rom:
http://forum.xda-developers.com/showthread.php?t=1076150
Use this one "com.netflix.mediaclient-1.apk is Netflix 1.2.2 (Released 6/15/11)"
About the Rom & App:
So far the Rom is perfect and great, The Rom has a nice style and is a little bit more faster than the old official stock Rom. Netflix works great on it and runs even better on 4G, Wifi is Great too. Netflix has been down for a while So if you get any errors saying the server can not respond on the login screen, try again later.
The 1005 Error should go away when you try and load the video, if you cant get past the login screen try the other Netflix app that says updated for those who cant get pass the login screen
Your Responsible For What Happens NOT Us!
Video Proof:
http://www.youtube.com/watch?v=6qt3wnJ_SJc
PROBLEMS I ENCOUNTERED & HOW I FIXED THEM:
1) Calls would not ring or ring for a second and the Phone app would crash, but you could still call people just they couldnt call you
FIX: You have To Wipe all system data when in recovery mode, If that doesnt work go back a wipe data and re-flash the Rom again
2) Status Bar Crashes
FIX: Wait A Couple of Seconds and It Should Pop Up, DONT FREAK OUT! good your done it happens sometimes but maybe estimate once a week max twice a week
3) Bootloop on the Red Fish (Fugu bootloop)
FIX: Now I dont know if this was suppose to happen but it stayed on it for like 10 mins and IF your not seeing the bootloop just your battery bootloop unplug the usb, Wait 10 mins Then Pull out the battery and go back to Download Mode
4)Galaxy S 4G Stuck On Boot Screen
FIX: Well I accidently downloaded the Nexus S CWM (Stupid Me CWM Doesnt work on this Flash & Not Even my Phone) But if that does, Take out the battery and Put the battery back in and Get it in download Mode Again and Re-Flash it
I Hope This Helps You So Please Click The Thanks Button If I Did
Won't be CWM support as long as the bootloaders are encrypted, which they are on this build. Prevents the ability to modify the recovery to support CWM. Unless someone cracks away and delivers non-encrypted bootloaders.
Always good to reference like you did, do this stuff at your own risk and always have backups, I have Titanium but also CWM backups from KD1 just in case.
Thanks still kinda new to the Rooting and Flashing thing but great to know
Added A Some Problems i encountered, mostly because they were my fault but i hope this Post helps u
Thanks for this! I already had the deodexed KF2. I just installed the recommended netflix apk and it works perfectly!
Sent from my SGH-T959V using Tapatalk
you do realize i cracked the gb boot loaders modfied them upped them with the rom and all hell broke loose on the phone some got it to work sometimes sometimes it would just give u funky screen because the kernel is also encryted to right Just hacking the sbl and boot file isnt enough need to crack the kernel or sign our own.

Pushing Recovery on 3.2.6

Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way

[Q] Issues with A701 upgrade to 4.1.1

Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
misteral1970 said:
Hi All,
Really sorry to post a new thread about this, but I am unable to add a post here: http://forum.xda-developers.com/showthread.php?t=1911437
So, followed Member - OPs guide to manually update my A701 to JB.
Simply put, the patch would not install (failed with a permissions error)
Put JB on anyway (just to see) and this won't let me get past the choice of language and location (Also, at this stage, SuperUser tells me system is requesting SuperUser access and whatever I do, it accepts)
So, used CWM to put the 4.0.4 build back, and that worked fine - though according to About Tablet I am actually on 4.1.1
I see improved UI speed and responsiveness, it's all looking great.
But Play Store won't run. Tried adding the latest version, still 'unfortunately stops' Also Nova refuses to run.
Has anyone run into any of these issues (Patch not installing, Play Store failing) and have any ideas what I can do to fix them?
Really sorry again for making a new thread in the wrong forum, I didn't see a choice (other than waiting!)
Thanks in advance,
Al
Click to expand...
Click to collapse
Mate, it doesn't sound good.
What I would do, at this point, is Fastboot the 4.1 image again.. And stay the heck out of CWM. If you Fastbooted the 4.0.4 image, and you still have it showing 4.1, then you have a serious issue. So boot to fastboot, and try it again. Clearly, whatever you did with CWM, didn't work,
Installing a rom from CWM, requires certain things to be done, either in the install script, or via CWM.
Most notably, Formatting User data, cache, dalvik, system, and data. If any of these do not get done, chances are, the rom install will not go good. The basic install script, generally only formats System and Flexrom. This is because Acer distributes a full rom with the understanding there is nothing on it. Most rom modders know this, which is why they give extra instructions via cwm.
The big thing, is when you boot your tablet, is if it says which bootloader you are on. So you have to look,. You want to be on the JB bootloader.
MD
Thanks for the response MD,
A tiny bit unsure how to proceed. I understand everything that you said (well, I think I understood correctly!)
I have in fact tried to fastboot the 4.1.1 image again, and again I am stuck on the language and location screen (did this last night before giving up for the day)
I have read and understood "Stay away from CWM" (and I know that it is in this case only - have used CWM on my Gnex without issue)
Please forgive me if what I am about to write is ridiculous - this is kind of where we'll see whether I understood correctly or not.
I'm thinking that if the various areas were not wiped, and that could be the reason for the snafu, then it would be worth going into CWM (which I have been warned to stay away from, and which I would stay away from except for this one thing) and formatting the user data, system, dalvik etc, then applying either the 4.1 or 4.0.4 to result in a working tablet.
Or possibly flashing the bootloader to make sure it is JB
Or going back to the weird 4.0.4/4.1.1 hybrid which works but doesn't allow Play Store and finding a way around that issue.
Mate, I'm not sure which way to go at this point!
Fastbooting 4.1 is a dead end at the moment (but could that be a bootloader issue....)
Fastbooting 4.0.4 gives me the hybrid (though I can check this again tonight)
BTW, the only CWM Rom work I have tried to do has been with the patched update (second downloadable file I think) - everything else has been done via ADB
So.....CWM to wipe/format caches? (I'm thinking 'NO! DID YOU NOT HEAR WHAT I SAID ABOUT STAYING AWAY FROM CWM????' but I'm asking anyway!)
Flash a new bootloader on? If so, any idea where I would find it (will obviously search here and Google)
Thanks anyway, and thanks in advance if you have any more advice. I really do appreciate the support!
Al
Well Al,
This is perplexing to say the least. Clearly fastbooting the 411 results in frozen at the wizard. My question, when you have the unlocked bootloader, does it say JBxxxxxxxx unlock mode when you boot the tab? Because it should. If it doesn't, then you're still on ICS bootloader. And will have to do the CWM thing to get JB installed. The 411 image flash, is to get a rooted version.
And this is the point. Personally, I do not trust the CWM's at this point. That's just me (already bricked 1 tab 3 months ago with a faulty CWM) I know the folks with ICS are using Pawitp's CWM, and haven't reported issues. But I don't know if they are doing wipes or not.
As with the 404 image, well, why playstore doesn't work is perplexing. You could try reinstalling the playstore via manual method (root required). Which is to delete the vending.apk, install a new vending.apk (making sure permissions are the same as the other files), then reboot. Go to settings, wipe the playstore cache's. Then try Playstore again. This was an old method we used with market issues in HC.
Personally, I feel the issue is with the wipes before running the patch. But I would hate you do the wipes and formats, then discover the emmc chip bricked. So it's 50/50.
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
Wish I could give you a definitive answer, but these processes are too new.
MD
Keep warranty
Moscow Desire said:
But heck, you have warranty. Just install some update.zip, and it resets your bootloader so service doesn't complain
MD
Click to expand...
Click to collapse
Can you make a short tut how to replace the old unlocked Bootloader?
My Tab has some Problems with the Display so it need a service ...
witch cwm to use?
witch update.zip?
remove cwm and su if necessary
Android Version: 4.0.4
Baseband: 11.810.922.00
Kernal:2.6.39.4+
Image:ACER_AV043_A701_RV08RC02_EMEA_DE
Build: ACER_AV043_A701_1.017.00_EMEA_DE
Hi MD,
Thanks for such a speedy and useful response!
Warranty: nope! I'm in China, bought the tablet in Shanghai (now way down south in Shenzhen) and it was a dodgy deal to say the least. I suspect they were being lifted from the factory. No complaints from me about this, or about any difficulties caused by rooting/flashing/CWM. My choice of action all the way along and I am aware of the risks
Just flashed 404 again and it is fine so far, again very nice and smooth. Going to look at the Play Store and see how it behaves, see what I can do as far as vending.apk is concerned (although I'm lost when it comes to permissions. Obviously I know what permissions are in tech terms, but no idea where they would be set, how to change them, what to use as a reference) I figure this is the path of least resistance for right now.
Then I'm going to see if I can apply the standard A701 update to JB (which I won't be able to because of rooting/unlocking but I will fiddle around) and see if I have any joy.
Got my keen eyed gf to check the message on boot, you were right that with the 411 image applied it still had an ICS bootloader, so that's good to know if I want to try going back to the flashed JB image. However, I have no idea how to flash the JB bootloader/kernel, and the CWM process for the patched update fails each time (despite editing the first line of the necessary file in META-INF/Google/Android)
So, I will keep you up to date with progress. Fingers crossed!!!
Al
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
misteral1970 said:
Quick update.
Play Store seemed fine for quite a long time (although I didn't download anything, I was able to browse no problem)
Went to install my back up of Nova, and of course had to tick 'Unknown Sources'
As soon as I did that, allowing installation of apps not downloaded from the play store, I got the 'Unfortunately Play Store has stopped working' message. Before I installed anything else, immediately I ticked that box.
Unticked it, but still not working - installed Nova, not working.
So....
Click to expand...
Click to collapse
Well, seems like Nova is the culprit. I assume you are talking about nova launcher? Or nova the game?
Hi MD
Yes, Nova launcher but no, it's not the culprit. At least I don't think so.
The play store stopped as soon as I ticked 'Install from unknown sources', before I installed Nova.
Very odd.
Quick questions:
1) Any advice/links/downloads for changing to JB bootloader if I apply the 4.1.1 again? Given that I cannot run the patched update/flash from CWM, I am guessing I would need to directly install/flash the bootloader from ADB...
2) Don't kill me for asking this. I know to stay away from CWM, I have seen you post it a good few times here, I heed the warning....BUT.....
Given that I have CWM installed and it's working ok (apart from failing to apply updates) - I have 6.0.1.4 - many of the guides to updating the 701 say it needs 6.0.1.1. Would the slightly more recent version of CWM make a difference in terms of success or failure of the update? Update is failing with a 'set_perm:some changes failed' very early in the update.
Seriously, I am being extremely wary of CWM, it's just that currently I have a slightly disabled tablet and it would be great to get this sorted.
Thanks, once again, for all your help,
Al
Update again, put 404 back on (after issue with play store and unknown sources)
Opened play store, downloaded Apex launcher - all good.
Ran Apex, all good....then suddenly Play Store stops, Apex stops, never to return.
With 404 img on, About Tablet still says 4.1.1
The saga continues!!
Aaaand that's the end of that!
Put 4.1.1 back on, pushed the boot.img from the official update.
Now no CWM, so it seems no recovery mode....if I try to get there by volume down and power on, it goes into update mode.
And of course neither the official update nor the 'patched' one will apply.
Can boot to the first start screen (language/location) but can't get any further.
Maybe I can find a service center here in Shenzhen who can sort it out.....as I said before, no harm no foul, I knew the risks!
Thanks one more time MD for all your support and advice )
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
misteral1970 said:
Or is it......?
Didn't give up, didn't surrender. Found out how to get into fastboot using frantic waggling of the rotation lock.
Just flashed 404 on again, waiting for boot to finish. Might still have a semi-usable tablet! Then I just wait till a 100% working JB manual update surfaces!
Click to expand...
Click to collapse
HA HA, you found the User Data wipe.... Yeah, a little known secret from the 500 forums.
MD
It's so strange....so now I'm back to having flashed 404 but the tablet thinks it's 411.
Play store was fine for about 40 minutes, I quickly got chrome, currents and BBC news.
I turned off the Acer ring and play store died...
But here I am, typing to you on the tablet and it's fine. And what a change in performance. It's most noticeable in currents..the increase in speed and smoothness when scrolling between pages makes it at least ten times better than before.
But the last flash was 404....weird....
I'll leave it like this for now. No market but at least it's not semi bricked!
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
misteral1970 said:
Super Quick update - in lieu of finding a sparkly copy of vending.apk, I tried wiping data and uninstalling Play Store (reverting to factory)
It duly downloaded a new version, and worked fine.
Then I popped Apex on, the GPS got busy, and Apex and Play Store died.
The wipe/uninstall worked again for Play Store so to be honest, I am currently quite happy. Ok, it's not perfect, but if I can quickly reinstate Play any time it fouls up, I can still build up a decent amount of apps to make the thing useful.
And seriously, whatever changes are there (considering the weird 404/411 hybrid) the performance is incredibly enhanced. All the faffing has been worth it, it is finally the tablet that it should have been from the start.
Click to expand...
Click to collapse
Well, good news then. I think it's an interesting set-up. Hybrid. Still not sure though, why it pulls 411 from the build.prop as it should have been changed when you flashed the 404image. But honestly, after reading the OP's steps, I believe he references going back to 404 via CWM, and not fastboot. This of course would mean installing a full 404 original rom. I'll have to look over my JB system dump and see where the other prop would be. Maybe something changed in JB.
So if you can live with it, it's probably better to leave it be till we come up with something more definitive.
MD
"So if you can live with it, it's probably better to leave it be till we come up with something more definitive"
Yeah, totally agree.
Mate, seriously, thanks for the support and advice on this. It makes a big difference. Even as I sat there last night with what seemed to be an unusable tablet, being able to chat to you about it meant that at least I didn't feel completely adrift!
Big big thanks

Help choosing ROM and Recovery

Hi everyone.
I rooted my Note Pro 12.2 (wifi) a while back and installed a basic rooted ROM, not CW12.
I honestly don't remember which ROM I flashed. I believe it was just a stock de-bloated ROM, and if it's the one I think it is, in the thread it says that ROM was faulty and dev has stopped for it. I see the kernel version and build in the "about" section under settings but I'm not sure if that number would tell me which ROM it is, or just the ROM and kernal that it was built on top of.
I basically wanted a stock style ROM with the ability to change things as I wanted. I'm still noticing a TON of lag. Scrolling on pages, loading apps, screen lag between touch and actual input of characters when using on screen keyboard, etc etc. I've frozen a bunch of bloatware and other things and it helped a little, but it's still pretty bad.
Audio latency with recording and MIDI apps is very bad, but I know that's improved with lollipop.
Aside from lag, it seems that GPS won't lock on no matter how long Iet it look for a signal (hard to tell if it's the ROM, but my Note 4 has found GPS very easily). Also, my Note 4 (unrooted and stock at this point) is waaaaay smoother and faster than this tablet. I realize we're talking about lollipop vs kitkat, and that the Note 4 version I have is the snapdragon one. But it still seems like performance should be better on this tablet.
So I'm wondering if anyone can suggest a good ROM for me to flash until lollipop comes out for the wifi version of this tablet. I want the stock multi-window functions (4 at a time plus floating windows), so CW12 is not an option. I want to use some of the Samsung apps like s note and Hancom office. I use the s-pen from time to time with the pen apps like write-on-screen.
The "rooted" features I want to access are turning off the camera sound (adding the switch to the settings menu in the camera app, not just replacing the sound file with a dummy file) Changing PPI of apps (xposed module) and full access read/write on micro SD cards and really important is the ability to add any app to the multi-window apps list and force orientation. I've been able to do all this with xposed modules.
Other than that, stock would be fine if it wasn't so laggy. The main reason I want to try another ROM is the lag. On screen keyboard has a lot of lag, but even my Logitech k810 bluetooth keyboard is laggy.
I'm also currently travelling and don't have a PC with me. So I'm hoping I can flash the ROM without ODIN, or perhaps I can use one of the ODIN-for-android type things on my Note 4 to flash a ROM to the Note Pro 12.2. Also I have the stock recovey, and would like suggestions on which recovery to use instead. Again, no computer with me to flash a new recovery. Ido have an OTG cable and USB flash drive so Ican back up my files before flashing the new ROM, as well as a miscro SD card.
Any recommendations for a smooth, fast ROM? Any tips on flashing it without a PC? I know I can copy the ZIP to the tablet and flash it from recovery...but it is the stock recovery...is this going to be sufficient?
THANKS!
The hyperdrive rom by sbreen (in the dev section) works great. Isnt there an internet cafe in the vicinity? Ask them for assistance flashing the beast. I love twrp. Good luck!
I tried to find an easy root apk thingy so you dont need a computer, couldnt find anything (but maybe kinguser or something like it will work)
Link to twrp with explanation
https://twrp.me/devices/samsunggalaxynotepro122exynoswifi.html
Thanks! TWRP is I think what's on my Note II back home. My tablet is rooted already of course. For the Hyperdrive ROM, one thing I'm a little confused about is if I have to FIRST install a stock ROM and THEN flash the custom ROM. I'm a little confused about why exactly but I see that in the forums from time to time. It's recommended for certain ROMs. I don't know if flashing the stock ROM updates some other firmware/hardware driver type stuff that's needed for the new kernal to work or what.
There might be an internet cafe. I'm flying from Vienna to Lithuania today. Trying to explain to them that I want them to download and install ODIN might be tough knowing only English and Spanish haha.
Sorry for the noob question but is clicking the thumbs-up icon what generates "thanks" or do I do that somewhere else?
spaceturd3000 said:
Thanks! TWRP is I think what's on my Note II back home. My tablet is rooted already of course. For the Hyperdrive ROM, one thing I'm a little confused about is if I have to FIRST install a stock ROM and THEN flash the custom ROM. I'm a little confused about why exactly but I see that in the forums from time to time. It's recommended for certain ROMs. I don't know if flashing the stock ROM updates some other firmware/hardware driver type stuff that's needed for the new kernal to work or what.
There might be an internet cafe. I'm flying from Vienna to Lithuania today. Trying to explain to them that I want them to download and install ODIN might be tough knowing only English and Spanish haha.
Sorry for the noob question but is clicking the thumbs-up icon what generates "thanks" or do I do that somewhere else?
Click to expand...
Click to collapse
If its rooted you can install twrp without computer (see my link) use twrp manager fromthe play store for that
You only have to flash the custom rom
(Make sure you backup on an ext sd or something, then delete everything in twrp, install custom rom, restart and done) I also always backup the launcher settings, if you backup the apps with titanium restoring is very easy afterwards)
Lemme know if this works for you!
goenieg said:
If its rooted you can install twrp without computer (see my link) use twrp manager fromthe play store for that
You only have to flash the custom rom
(Make sure you backup on an ext sd or something, then delete everything in twrp, install custom rom, restart and done) I also always backup the launcher settings, if you backup the apps with titanium restoring is very easy afterwards)
Lemme know if this works for you!
Click to expand...
Click to collapse
I'm already having trouble installing TWRP. I can't do it from the app, as my device isn't listed. I downloaded the zip file of the correct version of TWRP and tried to flash it using the stock recovery. But when I boot into recovery mode, it still just goes to the stock recovery. Then I downloaded and installed ROM manager from the play store and it shows TWRP as being installed, but whenever I boot into recovery I just get the stock recovery.
I'm back home now and I guess I'll just try to do all this with ODIN.
Is there any reason I can't just install the custom ROM using the stock recovery? That's what I did last time.
Ok So I got TWRP installed via ODIN then I used it to clean wipe and flash Hyperdrive ROM but gmail app won't even open, just crashes immediately, and it's one of the main apps I need so...probably gonna look for another ROM...or most likely gonna flash the stock ROM, unroot and sell the tablet and get a Dell Venue 11 Pro. Might wait till the end of July though, the supposed release date for lollipop on this device.
Had the same problem. Install hyperdrive without the gmail app option. Afterwards install itmvia the play store.
And if you want lollipop give cyanogen a try. I love it (but its a personal thing).
Ad make sure to read the Venue reviews, they are not very positive.
goenieg said:
Had the same problem. Install hyperdrive without the gmail app option. Afterwards install itmvia the play store.
And if you want lollipop give cyanogen a try. I love it (but its a personal thing).
Ad make sure to read the Venue reviews, they are not very positive.
Click to expand...
Click to collapse
I wanted to try lollipop because I use it for music, and latency is much better with lollipop. My Note 4 is running lollipop and I get way better performance from MIDI keyboards and guitar amp modelling. I really like the multi window functions on the stock and hyperdrive ROMs though, 4 at once, floating, etc. I'm sure as soon as lollipop is officially out for this device, someone will release a rooted version.
Thanks for the tip on gmail, fortunately I read it before getting too deep and just reflashed without gmail it and then installed the gmail app as you suggested and it does work. There still seems to be a bit of delay when using the on screen keyboard, not as fast as I had hoped. But it's up and running.
I was considering the Dell after trying a bunch of different audio and video editing apps for android and realizing that I just need full photoshop, premiere, and Reaper with all my VST plugins, so I need windows. Perhaps Surface Pro is a better choice but I like the Venue's chassis better, fanless, rounded corners. Also new tablets might be coming out with Windows 10 so another reason to wait...
My laptop is great but it's really big and I like a touch interface for on screen mixers and instruments. So I figured a tablet PC might work best for me. But the problem is GUI scaling. with the Windows legacy apps like Premiere and Photoshop, the buttons and menus don't scale, and on an 11" 1080 display they are quite small.
Just wait for win 10 and while waiting fine tune your 12" beast did you try system tuner pro already? You should be able to get less latency from that.
(And did someone mention "buy a Mac" already?
I am surprised, because after testing dozen ROMs I found stock ROM fastest one. Just root and debloat it.
Not so any lag or problems, but with custom ROMS I had a lot of problems.
tin2404 said:
I am surprised, because after testing dozen ROMs I found stock ROM fastest one. Just root and debloat it.
Not so any lag or problems, but with custom ROMS I had a lot of problems.
Click to expand...
Click to collapse
Indeed, cyanogen requires a lot of tuning (but its what I like about Android, I am more tinkering with it than actually using it I believe
goenieg said:
Just wait for win 10 and while waiting fine tune your 12" beast did you try system tuner pro already? You should be able to get less latency from that.
(And did someone mention "buy a Mac" already?
Click to expand...
Click to collapse
I checked out system tuner pro (didn't buy it yet just read the description) What exactly would I adjust to get lower audio latency? Just clock the CPU higher? OR does it have audio-specific settings not mentioned in the description?
Hold yer horses
http://www.sammobile.com/firmwares/download/49414/P900XXU0BOF2_P900OXA0BOF2_PHN/
Looks like Samsung official lollipop (I read that it has way better latency) is finally coming to your tablet.
---------- Post added at 10:02 PM ---------- Previous post was at 09:51 PM ----------
Better link https://drive.google.com/file/d/0B4ccvyxgge4kaUktYWtPUl9QSW8/view?pli=1
WHAAAAAAAT?!?!?!?!?!!? I've been checking sammobile EVERY day for the lost couple weeks waiting for this! OMG OMG I'm hoping I'll be able to use the Samsung Audio stuff with this, their DAW and amplitube and all that...plus I'll get Hancom office back...Thanks for the heads-up. I'm glad I've been using CM12.1 though So I can compare the experience.
Looking forward to the rooted version of stock lollipop making its way to xda as well! Now... to figure out the best way to back up my current installation...

Since Android 8.0 its lagging

Hey guys. Two days before i updated my phone manually via ODIN on a german version G930FDBT2ERG2_DBT.
So i just let Google and Samsung restore all my stuff. Then i installed TWRP and root via the no-verity-opt-encrypt-6.0.zip and magisk v16.0.
After that i installed XPosed via the XPosed Installer app. I think since i did that or maybe before, every app needs hours to start and lags.
e.g. opening of Snapchat. Like it's closing so hard in background, that all services need to restart.
Instagram and OneDrive are shown many time as stopped working and i don't know why. Maybe Instagram caused by XInsta?
Okay i recognized OneDrive isn't even working anymore. Was already on Android 7 a problem. Does not seem to be compatible to something else.
You have any ideas or need any information? Let me know
try a factory reset. Personally, I use a modified stock rom (light rom) and it is very stale and very fast.
achour7 said:
try a factory reset. Personally, I use a modified stock rom (light rom) and it is very stale and very fast.
Click to expand...
Click to collapse
Antutu Benchmark gives me 164336 points, so it seems literally to be normally, but i know all loading times of Snapchat and Instagram and so on are so much longer.
I will try to flash it again and to start clean. Just the copying of the WhatsApp folder needs so much time.
So I'm asking again. Nobody else got problems? I still dont get the data mount error fixed, because when I install Magisk it's broke again and my whole phone seems to lag. I dont know if it's because of my Xposed modules or Magisk modules. But for example with the update everythings goes slower even if Antutu says something else. Snapchat needs years to start. Is it cause of dual messenger? But I don't think so. Or when i'm in the car and using Google Maps and Poweramp and tapping skip on my car radio for skipping in bluetooth there is a delay of 20 seconds sometimes so wtf.
Any speedups for S7 or Android 8 on S7???
CptDayDreamer said:
So I'm asking again. Nobody else got problems? I still dont get the data mount error fixed, because when I install Magisk it's broke again and my whole phone seems to lag. I dont know if it's because of my Xposed modules or Magisk modules. But for example with the update everythings goes slower even if Antutu says something else. Snapchat needs years to start. Is it cause of dual messenger? But I don't think so. Or when i'm in the car and using Google Maps and Poweramp and tapping skip on my car radio for skipping in bluetooth there is a delay of 20 seconds sometimes so wtf.
Any speedups for S7 or Android 8 on S7???
Click to expand...
Click to collapse
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.
achour7 said:
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.
Click to expand...
Click to collapse
I like TouchWiz. Is there any ROM that is similar? And never heard of another kernel to fix that. Is that kernel better? Last time i changed kernel and stuff was with my Galaxy S3
CptDayDreamer said:
I like TouchWiz. Is there any ROM that is similar? And never heard of another kernel to fix that. Is that kernel better? Last time i changed kernel and stuff was with my Galaxy S3
Click to expand...
Click to collapse
Tgp kernel gives a good battery life ans smooth UI.
If you didn't flashed a kernel, you need to wipe data partition by writing ''yes''
And you will Lost all you data, so you need to save you data on external storage, hard Drive or computer.
achour7 said:
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.
Click to expand...
Click to collapse
achour7 said:
Tgp kernel gives a good battery life ans smooth UI.
If you didn't flashed a kernel, you need to wipe data partition by writing ''yes''
And you will Lost all you data, so you need to save you data on external storage, hard Drive or computer.
Click to expand...
Click to collapse
Works it without problems? Bro do i just need the kernel or also like I found out this THE GALAXY PROJECT ROM ? It looks like TouchWiz ha?
I have stock phone without root and my phone is getting really extremely hot since it was updated to Oreo.
Even by doing something like being here in the forum is getting so hot that is uncomfortable on my hand
CptDayDreamer said:
Hey guys. Two days before i updated my phone manually via ODIN on a german version G930FDBT2ERG2_DBT... After that i installed XPosed via the XPosed Installer app. I think since i did that or maybe before, every app needs hours to start and lags...
Click to expand...
Click to collapse
If on stock then resources being consumed with bloat. If issues began around installation of xposed wouldn't it make sense to uninstall modules and xposed and see if improved over the next day? Restoring apps and data and rooting and moding is a lot of stress on device all at once, then it gets so warm it starts to go glitch. I've been there too. Best thing is to let it sit 30-60 min after set up finishes to cool off. Reboot too once restored data completes.
Almost makes me miss the rip out and replace with cool fully charged battery days of my S4 [emoji91]
Sent from my SM-G930W8 using Tapatalk

Categories

Resources