Develop Bugs

OTA

So I know the rule about never accepting otas but I was asked a question and couldn't remember. So if I accept an ota will it brick my phone or will it just update and unroot?
Sent from my Galaxy Nexus using xda premium

depends on what you did to your phone with root access.
are you on stock? ROM?

Yea stock rom just rooted
Sent from my Galaxy Nexus using xda premium

Well if you are on stock and you rooted, you will most likely lose your root (although some posts around here say that root aces is preserved during update in some rare cases).
If you are on a custom rom (e.g. if you installed an update using a custom recovery) and you are updating to a stock update then you will be likely screwing your phones system. depending on where you messed (or let a programmer mess using custom recovery or Rom managers) you could be bricking your phone as well since there are updates for boot and recovery in the stock updates to 4.0.2 and 4.0.4 (I don't count 4.0.3 since google pulled it off their site).
If you want a stock version of the newest android for your GN make it a manual patch by following this guide http://forum.xda-developers.com/showthread.php?t=1391881 make sure you do flash the boot, recovery and radio as well...
But before you do that check in with the forum thread or website were you got your custom rom or root method and ask them for advice, Yeah do that! It's the safest way to do something when you know how others got to the point where you wanna go!

Thx alot
Sent from my Galaxy Nexus using xda premium

Please let us know how things worked out for you.
Hint: after following the steps above you are on the official google builds. Nice thing about that is you get new android versions as updates on the very second they are released. And most things that come with root are already available in the unrooted system (except overclocking) so why bother about root and stuff when you as a non-developing user can acces more priveleges on stock while rom builders for other phones try to keep up with YOUR system?
Sent from my Galaxy Nexus using XDA

I'm completely stock right now just a rooted 4.0.2 I will probably stay like this until cm9 becomes stable or AokP next milestone comes out because he current one did not agree with my phone at all
Sent from my Galaxy Nexus using xda premium

[Q] what's the deal with 4.3?

- For android 4.3, there has been a lot of talk on the developer section, and from what I can see, the major bugs/issues have been fixed. Like the ROM not rebooting correctly. For those using 4.3, is this true?
- Also, from what I understand, this was due to the recoveries not being ready for 4.3, however CM released their own bare bone recovery to fix that issue. And then I've read that the TW recovery has also been updated to solve this problem.
-There is a lot of information in the development forums, but I have not seen any post on the steps on what to do in order to upgrade from 4.2 to 4.3.
-Right now I have CWM 5 recovery, because that's been working for me, and I never bothered changing (bad experience with trying to upgrade/change a recovery). Now from what I understand, I should be able to flash the newest touch recovery (via the goo app?), and then wipe and flash any 4.3 ROM. Any detail instructions would be a help, or if someone can create a tutorial post, that would be great.
Thanks in advance.

Here is a post I made yesterday about how I switched from 4.2 to 4.3
I hope it helps. I have been on hellybean 4.3 for two days and everything is running great.
http://forum.xda-developers.com/showpost.php?p=45021060&postcount=632

You could just install ROM Manager and update from there. It's super-easy (you need ROOT, but I presume you have that since you're flashing ROMs anyway). :good:

Sicily1918 said:
You could just install ROM Manager and update from there. It's super-easy (you need ROOT, but I presume you have that since you're flashing ROMs anyway). :good:
Click to expand...
Click to collapse
Many people have had bad experiences with ROM Manager. Especially in the Gingerbread days when its use was more common for this sort of thing.
Just my 2 cents.

monkeybuttons said:
Many people have had bad experiences with ROM Manager. Especially in the Gingerbread days when its use was more common for this sort of thing.
Just my 2 cents.
Click to expand...
Click to collapse
Interesting -- always been good to me, although I only use it to update the recovery; for the ROM itself I use Cyanogen's update util. I also use CWM, not TWRP, so there's that...

bobiscool07 said:
- For android 4.3, there has been a lot of talk on the developer section, and from what I can see, the major bugs/issues have been fixed. Like the ROM not rebooting correctly. For those using 4.3, is this true?
- Also, from what I understand, this was due to the recoveries not being ready for 4.3, however CM released their own bare bone recovery to fix that issue. And then I've read that the TW recovery has also been updated to solve this problem.
-There is a lot of information in the development forums, but I have not seen any post on the steps on what to do in order to upgrade from 4.2 to 4.3.
-Right now I have CWM 5 recovery, because that's been working for me, and I never bothered changing (bad experience with trying to upgrade/change a recovery). Now from what I understand, I should be able to flash the newest touch recovery (via the goo app?), and then wipe and flash any 4.3 ROM. Any detail instructions would be a help, or if someone can create a tutorial post, that would be great.
Thanks in advance.
Click to expand...
Click to collapse
Ur best and safest approach would be to DL Odin and the drivers for ur phone, then go to techerrata.com/browse/twrp2/hercules and DL twrp2.6.0.4, this is the 4.3 compatible version, then put ur device in DL mode and connect to odin, load the tar file in PDA and click start, 30 sec and u have the latest and greatest twrp recovery, now go get hellybean 4.3 or beanstalk4.3 and flash it, watch the beauty take place...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

I updated my rom today like I usually do from the CMUpdater and it updated from 4.2 to 4.3. I didn't mean or want to do that, but it didn't tell me otherwise. Now I'm having issues left and right......the one time I don't back it up...grrr.
I'm having the most issues with Gapps. I downloaded the new one and installed it and Google Music and Youtube keeps crashing. I guess I'll be doing the full wipe now.

Did u update to 4 3 gapps? It won't do it automatically, even if u updated through goo it just looks at what version is installed and updates that version, 4.3 gapps can be found in any 4.3 thread
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

soupysoup said:
Ur best and safest approach would be to DL Odin and the drivers for ur phone, then go to techerrata.com/browse/twrp2/hercules and DL twrp2.6.0.4, this is the 4.3 compatible version, then put ur device in DL mode and connect to odin, load the tar file in PDA and click start, 30 sec and u have the latest and greatest twrp recovery, now go get hellybean 4.3 or beanstalk4.3 and flash it, watch the beauty take place...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Why do some of those files say hercules, and others sgh-t989? Aren't they the same phone?

[Q] Should I flash stock back after using cyanogen?

Hello all,
I just have a few questions regarding my note 2 sgh-i317 which I've just received from ebay on Thursday. As soon as I got it I rooted and flashed cymod 10.2 because up until this point I didn't want anything stock on my previous galaxies. Before I flashed though, I messed around with s-note and was highly dismayed that I'm not able to mount touchwiz apps. I tried changing apk permissions through es and move to system/app folder to no avail. Then I thought I would settle for Papyrus since thats what my wife has on her rooted/omni rommed note 10.1. I'm not happy with that app or the fact that there is not a 4.4.2 update for the note 2s yet. I'm thinking the only way to get s pen features to work with the good apps it was designed to work with, is to go back to stock.Any input or suggestions would be greatly appreciated as well as the thread link for the stable 4.3 stock rom download as TWRP didn't back it up right before flashing.
Thanks in advance
omen
Galaxy Note II-sgh-i317 Root/CyMod 10.2
Galaxy SIII-sgh-i747 Root/CyMod 10.3
iPhone 4S......wait no I did not just go there:silly:

I was on an aosp and flashed 4.3 alliancerom. Like it a lot. Because of the whole bootloader thing with 4.3 and that I didn't update mine my wifi didnt work as I was told it wouldn't. So I heard somewhere to flash a kernel called devil kernel and it made everything work like a charm not to mention the kernel is awesome. It has a app in the playstore to manage it. It also works on both touch wiz and aosp. The best thing is it also allows for dual boot between aosp and touchwiz. I have a backup that I access from cwm. I go back and forth between CyanogenMod and touchwiz all the time.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

Jsouthernindiana said:
I was on an aosp and flashed 4.3 alliancerom. Like it a lot. Because of the whole bootloader thing with 4.3 and that I didn't update mine my wifi didnt work as I was told it wouldn't. So I heard somewhere to flash a kernel called devil kernel and it made everything work like a charm not to mention the kernel is awesome. It has a app in the playstore to manage it. It also works on both touch wiz and aosp. The best thing is it also allows for dual boot between aosp and touchwiz. I have a backup that I access from cwm. I go back and forth between CyanogenMod and touchwiz all the time.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
I can't get any other kernels too flash until I unlock the bootloader though right? Mine had the OTA and I'm still on the MK6 baseband. I found 2 UCUBMK6 Param tar files which are supposed to work but I'm still seeing and unchanged flash count and knox trip displayed while in download mode. I really want to go to alliance and just am not sure what my next step should be. Thanks for your previous input and devil kernel does sound sweet...hopefully I'll get to enjoy it soon:fingers-crossed::fingers-crossed:

omenbass said:
I can't get any other kernels too flash until I unlock the bootloader though right? Mine had the OTA and I'm still on the MK6 baseband. I found 2 UCUBMK6 Param tar files which are supposed to work but I'm still seeing and unchanged flash count and knox trip displayed while in download mode. I really want to go to alliance and just am not sure what my next step should be. Thanks for your previous input and devil kernel does sound sweet...hopefully I'll get to enjoy it soon:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Negatory. Flashing kernel and Alliance will work.
You're stuck on the MK6 bootloader, which is fine. DO NOT try to flash a bootloader !

4.3.1 rooted, how to go to 4.4.2 ?

Hi dudes,
I've got a used Nexus 7 (2013) on android 4.3.1 firmware but rooted ...
I'd like to go to the lastest firmware 4.4.2 I guess, so I wonder if I can do a upgrade using the wifi as an unrooted tab or not ?
My tab is rooted , is it a problem for upgrading ?
If so, I'd rather unroot it, I prefere tablet as brand new ...
is there a way to brick my tab using the official update (by wifi) ?
Thanks !

If you are not receiving the update, just unroot it, and return it to stock. You can use the Nexus Root Toolkit by Wugfresh. It's really simple to use, and the help section is really good. Goggle it.
Have you tried going into settings, and going into system updates? Just having the tablet rooted, should not prevent you from receiving updates. Now, if it's routed with a custom rom, that's a different story. Good luck
--=={BSnapp} ==--

hi, it is rooted with the official firmware 4.3.1 I Guess( is there a way to see if it's a custom or official firmware ?)
and I've got the notification of the 4.4.2 upgrade ...
?
In parameters here is what I've got :
band base version
DEB-G00_2.25.1_0802
kernel version
3.4.0-g9e52a21
[email protected]$1
so official one ?

I see that you have the LTE model (DEB.). If you could post a screenshot of your About Tablet screen, one of us should be able to help you.
Sent from my Nexus 7 using xda app-developers app

here is the picture
thanks

apparently, trying to do a recevory using the POWER and UP trick, it seemes the guy before me has installed clockworkmod recovery v6.0.4.4 so what should I do ?

You could flash a 4.4.2 ROM using Clockwork Mod recovery. NOTE: Please research and double check every step before flashing. The basics are: make sure that you have plenty of battery life; make a backup of your current ROM; do a factory reset in Clockwork Mod; select a 4.4.2 specific to your device, e.g., Paranoid Android for DEB; download a zip file of SuperSu 1.94; download Gapps; then flash the ROM, Gapps, & Supersu. Again: read, read, read through XDA before flashing anything. EDIT: Make sure that you have the most recent Clockwork Mod version for your device.
Sent from my Nexus 7 using xda app-developers app

well, I'm gonna uninstalle the whole thing (imean CWM and the root access)
Do you think this tuto is good ?
http://www.forum-generationmobiles....-en-stock-via-une-factory-image-root-17092013

I understand only English, so I don't know. I do know that as Bsnapp's post states, Wug's Nexus Toolkit works well for unrooting and flashing stock. Back up your files first.
Sent from my VS980 4G using xda app-developers app

ok
It sais that firt download the original rom on Google site, then juste write "flash-all.bat" (need SDK)
seems too simple no ?

alucard_xs said:
ok
It sais that firt download the original rom on Google site, then juste write "flash-all.bat" (need SDK)
seems too simple no ?
Click to expand...
Click to collapse
http://www.wugfresh.com/nrt/
Use this, you won't have any problems.

Stuck in reboot loop after CF-Auto-Root

Hi All,
I purchased my Note 4 from Swappa, it already came in with Knox 0x1 (4) but it was restored back to stock everything. I recently upgraded to 5.1.1 (via Official OTA) and Sprint has turned my phone into an Ad Beacon. I get all sorts of stuff get installed from Sprint Zone to Avatars for Voicemail and a ton of apps that I need out of my phone.
I decided to try the CF-Auto-Root method. This worked for me in the past with my Note II. Well, I was not so lucky this time. I booted to Download Mode, ran Odin, and PDA installed the autoroot TAR.
I got the red pirate droid screen, and then the phone rebooted. Since then it's been stuck in a reboot loop over and over.
Is my phone bricked? I realize I made a very dumb mistake by doing this now. Because I need my phone the next 2 days and I might have to call Sprint and have them re-activate one of my dumb phones if I can't figure this out.
Question is, is the phone done for? Or is there a way I can bring it back from the dead? I am currently download what I think is the stock FW for the Note 4 (5.1.1) from Sammobile. Its going at 200kb/s so It won't finish for another 2 hours. Only problem is. I have no idea what to do with this file once I get it.
If someone here can please point me in the right direction. I'd greatly appreciate it.

CF autoroot does not work on 5.1.1....odin stock sprint rom and then flash a custom rom with root baked in the rom...recommend Sprint HybridX ver3 as it has anything you could want in a rom and is very stable...you'll need to install custom recovery such as TWRP to flash the custom rom
Sent from my SM-N910P using Tapatalk

gdempsey1 said:
CF autoroot does not work on 5.1.1....odin stock sprint rom and then flash a custom rom with root baked in the rom...recommend Sprint HybridX ver3 as it has anything you could want in a rom and is very stable...you'll need to install custom recovery such as TWRP to flash the custom rom
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for the response. I'm currently flashing using:
ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar.md5.zip
It's doing it's thing at the moment.
I tried flashing TWRP earlier, but had no luck. Could you please point me at any resource that can help me get that? Assuming this stock I'm using will work.
EDIT: It finished, rebooted. Now stuck at the Sprint Spark screen for about 5 minutes now.
EDIT2: It's preparing device for first time use. Looks like the stock made it through.
Just need to know how to flash TWRP at this moment and if you can kindly point me to that HybridX ROM I'd be grateful!

Go to XDA developer (install app from playstore) and the go to sprint samsung galaxy note4 forum under android development and find sprint hybrid x rom thread...at the beginning of thread are all the file downloads you'll need and instructions to install....when you're done give @tx (the developer) a thank you...he's an awesome developer and creates the best roms out there for our devices.
Sent from my SM-N910P using Tapatalk

Thanks for the headsup. I managed to get TWRP working and I booted to it.
I'm just confused regarding Deodexed vs Nondeodexed roms. What's the difference? That's my last obstacle in my way.
Again, I appreciate your help.

Odexed is for performance and deodexed is for mods...deodexed alittle slower but highly customizable (themes..5way boot...etc.)...odexed is fast but can't customize.
Sent from my SM-N910P using Tapatalk

gdempsey1 said:
Odexed is for performance and deodexed is for mods...deodexed alittle slower but highly customizable (themes..5way boot...etc.)...odexed is fast but can't customize.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So unfortunately I rebooted from TWRP after testing that it works and I'm back to the boot loop.. I get the Sprint logo and it keeps rebooting....
When I was in TWRP, before I rebooted it asked it I wanted to installed SuperSU and I agreed. Could that have done it?
Does that mean I need to reflash again?

Possibly incompatible...you flashed a stock rom and tried to add SU without root....reflash stock...and then flash the Hybrid X rom if you want root and SU as they are baked into the rom so when you reboot you'll have everything you need...no need to add anything else.
Sent from my SM-N910P using Tapatalk
---------- Post added at 08:38 PM ---------- Previous post was at 08:32 PM ----------
After you install xda read some of the threads....you'll learn alot on the peculiarities of the new 5.1.1 update and OG5 problems and workarounds....much info in these threads...especially Hybrid X threads

gdempsey1 said:
After you install xda read some of the threads....you'll learn alot on the peculiarities of the new 5.1.1 update and OG5 problems and workarounds....much info in these threads...especially Hybrid X threads
Click to expand...
Click to collapse
Looks like I managed to boot into HybridX finally. My only worry at this point is it looks like I lost LTE. I only see 3G connection now.
I'm guess that's what you're referring to with OG5 problems?
EDIT: I can't really tell at this point. Whenever I reboot. I see the LTE logo. I ran the browser real quick managed to load a page fast. But lost the signal and went back to 3G. I'll have to give this a full day of testing before I judge it.
That being said, I got rid of all the Sprint junk and I think the phone runs a bit faster. So thank you for all your help!

You're welcome...and the lte/3g will switch back and forth depending on the available signals inorder to maintain the most stable data connection for your location....not to worry....you probably won't even notice the difference other than the icons
Sent from my SM-N910P using Tapatalk
---------- Post added at 10:21 PM ---------- Previous post was at 10:12 PM ----------
You're gonna love the battery usage...and all the bells and whistles like audio mods that @tx baked into the rom
Sent from my SM-N910P using Tapatalk

I had this same thing happen to me. My phone is stuck in a boot loop. Where do I get the file I need to flash to restore everything back to normal? I'm inexperienced in rooting so any help would be appreciated.

frenchiethefry94 said:
I had this same thing happen to me. My phone is stuck in a boot loop. Where do I get the file I need to flash to restore everything back to normal? I'm inexperienced in rooting so any help would be appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
You'll need Beastmode kernel and SuperSU zip links from that post. There's also notes that will help if you continue to experience boot loops.
Sent from my SM-N910P using Tapatalk

Hey guys I'm in the same boat using 910W8 Telus reboot loop. What do I need to do to unbrick this note 4 fairly new to this and bit off way more than I could chew lol please helppp

Easy Root for SM-G900T1 klte (Any Device) Lollipop 5.0-5.1.1 or CFAutoRoot btloop fix
Will work on any device. So I was having the same issue and had actually just wasted 2 whole days trying to root my S5 with the 5.1.1 and couldnt seem to find a working download link for the 4.4.2 Gingerbread so being the stubborn ass I am when it comes to hacking and finding faster alt. solutions by like editing script or binary persay. So out of irritation and many times flashing back to my previous firmware lol I had a crazy idea. I used the CF Auto Root and sure enough bootloop, but....then I thought well I need the TWRP recovery if I wanna try and maybe manually update or swap the boot.img or security protocol somehow so I flashed TWRP recovery and all I had to do to end the bootloop was install update from ext sdcard<SuperSU v1.65 update which it just so happens I coincidentally copied and pasted onto my sd card (via sd card adapter in laptop or the mass storage mode when hooked to usb) and boom it booted up and started perfect as if I didnt even have Lollipop 5.1.1 lol made my night/morning at 6 am previously frustrated and about to give up. So to sum it up....
1. Download/Install: Odin v3.10.6
2. Download/OdinFlash: CF Auto Root
3. Download/OdinFlash: openrecovery-twrp-2.7.0.0-klte
4. Download: SuperSU-v1.65-update
5. Recovery Reboot
6. Install Update: SuperSU-v1.65-update
slide to flash it, wipe Dalvik cache, reboot normally and wahlah you've now rooted you Galaxy S5 klte on Lollipop 5.1.1 and up (when they update the klte this method should still work guaranteed due to the fact its more of a technical loophole in the firmware than the exploit package itself)