Develop Bugs

[Q]Is there a "true" factory restore for T-Mobile Galaxy S II?

We received our Samsung Galaxy II phones a few days ago.
My wife had a Swiftkey and Swiftkey X keyboard apps in her Amazon appstore account. She installed Swiftkey X, and she was presented with an "update" that showed Swiftkey (not the X; apparently this is an issue with Amazon appstore based on Swiftkey site). Thinking that it was an update to the Swiftkey X, she apparently applied it, and immediately there were number of FC notices (she remembers seeing TWLauncher among them) and a spontaneous reboot of the phone. Then, she couldn't get online either through WiFi or 4G. At that point she gave the phone to me to fix it
Comparing her phone side by side with mine it is very clear that there's an issue with network connectivity. While mine flies through the pages, market downloads, etc. either on WiFi or 4G, hers get stock for 3-5 seconds before opening pages or sometimes just displays a "webpage cannot be found" or "connection error".
I went ahead and did a factory restore, but that seems to only delete user account, personal files, etc. if I understand it correctly. Moreover, the issue is still there after the restore. So, is there a way to restore the system files to stock as well? Can it be done without rooting, or does it require loading a fresh ROM?
Sorry for the lengthy message and thanks in advance!

http://forum.xda-developers.com/showthread.php?p=27322
that's a full factory reset.
Sent from my SGH-T989 using Tapatalk

mikeyinid said:
http://forum.xda-developers.com/showthread.php?p=27322
that's a full factory reset.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. Could you double check the link? I get "No Thread specified. If you followed a valid link, please notify the administrator".
Thanks again!

tenderidol said:
Thanks for your reply. Could you double check the link? I get "No Thread specified. If you followed a valid link, please notify the administrator".
Thanks again!
Click to expand...
Click to collapse
if you look at the sticky threads at the top of this forum there is one called index by AllGamer. Its at the bottom of the first post. Make sure you grab the Tmobile one and not the telus one
Sent from my SGH-T989 using Tapatalk

Here: http://forum.xda-developers.com/showthread.php?t=1323878
Everything goes back to stock.
You need to either:
1. Root
2. Install CWM through ROM Manager
3. Flash this
Or:
1. ODIN flash CWM
2. Flash this

513263337 said:
Here: http://forum.xda-developers.com/showthread.php?t=1323878
Everything goes back to stock.
You need to either:
1. Root
2. Install CWM through ROM Manager
3. Flash this
Or:
1. ODIN flash CWM
2. Flash this
Click to expand...
Click to collapse
Dude. That's a half ass way, it doesn't take you to stock. First of all its deodexed.. Just a sec
This is the only proper way to go back to stock THIS IS IT RIGHT HERE
Sent from my SGH-T989 using Tapatalk

Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.

tenderidol said:
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
Click to expand...
Click to collapse
you dont have to root it to run the odin package

mikeyinid said:
you dont have to root it to run the odin package
Click to expand...
Click to collapse
Oh, sorry about that. I'm a newbie for the SII rooting/modding (did quite a bit with Nook Color), and I need to do some reading first.

Smart man!
Sent from my SGH-T989 using Tapatalk

voidthedroid said:
Smart man!
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Alright, I'm halfway through. The rooting process for the SII is little different than NC, but the principles are the same.
By the way, is it safe to assume that some conflict between SwiftKey and SwiftKey X caused the problem on her phone? The reason I ask is because I'd like to put SwiftKey X on my SII (it has multi-language support) and I dont want to deal with the same issue if it was the culprit.

I believe I did enough reading at this point
Since this doesn't involve rooting (now I understand it), I'd like to get an "OK" from the guru before proceeding with the following "as newbie as it gets" steps:
1. Install Odin (v1.85)
2. Install Kies for the recent GSII drivers
3. Make sure Windows recognizes the phone in ODIN (seeing <ID:0/004> Added!! in the message box)
4. Turn off the phone
5. Turn on the phone by holding both the Vol-up and Vol-down buttons and plug the USB cable in while still holding both buttons
6. Select volume up button to proceed to download mode
7. Start Odin
8. Check the PDA button in Odin and browse to “T989UVKID_HOME_SGH-T989user_CL594724_REV00.tar.md5” file
9. Click Start in Odin and let it flash
10. Once it completes and reboots…..
Is that it? At Step 10, it should boot into a 100% T-Mo stock, right? Just to be sure, I’ll perform a factory reset after that point and start all over with the user files, apps, etc.
Thanks in advance!

Sounds good. But if you look in the stickied threads top of this forum the drivers for our phone are posted. No need to install kies but that does work also
Sent from my SGH-T989 using Tapatalk

tenderidol said:
Thanks again for the replies. So, I'm going to have to root it and put a stock image back I gues... I was hoping that SII had a fail safe similar to Nook Color where you can easily go back to stock if something was not right.
Click to expand...
Click to collapse
The "factory reset" you used IS the fail safe. The parts that "factory reset" doesn't remove is the part that won't be messed up unless you are rooted. So I don't even know how you touched /system etc without rooting...

mikeyinid said:
Sounds good. But if you look in the stickied threads top of this forum the drivers for our phone are posted. No need to install kies but that does work also
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Thanks a lot!
Just finished flashing the stock image and everything worked as expected. This was also a good practice to learn how to restore it to stock in case something goes bad.

513263337 said:
The "factory reset" you used IS the fail safe. The parts that "factory reset" doesn't remove is the part that won't be messed up unless you are rooted. So I don't even know how you touched /system etc without rooting...
Click to expand...
Click to collapse
The issue was created after installing a 3rd party keyboard and -by accident- applying an update that was supposed to be for a slightly different version, which resulted in numerous force closes and random reboots immediately. I might be wrong here, but that indicates that more than just the user files were affected, since deleting just user files via factory reset didn't help the network problem. However, flashing the stock image -without rooting- took care of the problem.

[GUIDE]For Starters(Newbies)

NOTE: Noob is not a really good word. kinda discriminating. newbie better.
THIS will GUIDE how to get on foot if your just starting on Galaxy Y, most probably, ANDROID
1. First Things first. Know your Phone. before doing anything, just be on the stock for a while. Know all the things, settings, install some app and alike. This way, you'll know your way through. See apps like market, Maps and others, check bugs etc.
2. Second part is knowing a basic tweak of your phone, to be exact: BATTERY SAVINGS. Know your way from this apps. See how they handle your battery life. The purpose of this is to know the performance of your phone
3. So you feel much better knowing your phone, you can start rooting or installing some replacement apps Go, ADW, Pansi, Popups, keyboards its up to you. But i dont recommend instant rooting when your just getting on foot.
Rooting wont brick the phone, maybe but its in the least.
(I wont be giving links for many threads here are available already. Its hard just to give you everything when researching can't kill one)
WHAT IS ROOTING?
rooting gives you access to the system of your phone. thats it
Soft ROOT-stated in the above
Hard ROOT-gives you access to the commander of the system which allows you to access the device via shell extensions and ADBs
4. Same as step 1. See how does root work for you. Dont just access the system right away using an explorer. look for apps that can help you achieve your desired goal that requires root access. a good start would be RAM tweaks.
5. Removing apps that you dont need. Its the power of Rooting that grants you this. basically, it improves RAM usage and speed of the device especially when "app-example.apk" initiates on its own. ofcourse it increases the capacity of your device.
6. KITCHENS. for a start you can use the UOT kitchen which allows you to modify some parts of the device. as far as i know, mods like transparency, lockscreen and bootanimation wont work on stock dont ask why coz i dunno sorry. so using this kitchen can allow you to change statusbar appearance pull down notif bar, etc.
but, the MAIN concern of a KITCHEN is ROMS.
ROM is the thing that the device reads for it to run properly.
ROM development are for making a benefit that can help a device achieve its fullest performance. Speeding it up, etc.
You can see the Development Page for it
**EXTRAS:
FLASHING
Flashing is a way of updating or down-dating your device.
Odin is the tool used in it.
If KIES wont let u update. Flashing would be good but you just have to download the firmware you want.
PARTITIONING.
since SGY got a small memory for internal, u can use partitions in the SDcard to let it handle some memory for you.
BOOT recovery:
it is where you flash mini updates like rooting CWMod, UOT kitchen mods and others
**Clockworkmod recovery / CWM is a custom CWM it has additional features moreover see for yourself
i guess thats it ill just edit it if somethings new comes
THIS IS FOR NEWBIES, no noob persons exist: ONLY NEWBIES.
hoped this helps you can just PM me for assistance but for now please bear with this simple guide thanks
PS: im no dev but as soon as i got my laptop ill start im just using a netbook and my phone for learning. so thanks

good tutorial for newbies and i try to make a rom,but i dont if can i brick my phone from errors.I read many things before make a rom.
JuSt pReSs THANKS if i HeLLpeD yOu

Yap. Rom manager is not yet working for G-Y dont be afraid. Ive bricked my phone a dozen times alrready.
-- [email protected]

what happens if sm1 bricks his phone??

If soft, phone wouldnt boot properly though can go to download mode
Hard, cant open even boot recovery
-- [email protected]

nice post there man or rather master? hehehe ( you are now my master ) , i really think this thread should be sticky.
very informative for the newbies out there as a head start, keep on posting and helping here master
if they will be needing another moderator here i will surely vote for you

thanks you so much!

it would be nice to include how to make a hard bricked phone to soft brick

ronnieryan said:
it would be nice to include how to make a hard bricked phone to soft brick
Click to expand...
Click to collapse
Theres a thread already so i cant make one im just here for those who really want to get on their foot
-- [email protected]

[Guide Lines] HARD / SOFT BRICKS FOR GALAXY Y GT-S5360 MOBILE
musashihatred said:
Theres a thread already so i cant make one im just here for those who really want to get on their foot
-- [email protected]
Click to expand...
Click to collapse
ronnieryan said:
it would be nice to include how to make a hard bricked phone to soft brick
Click to expand...
Click to collapse
Guidelines for how to solve HARD / SOFT BRICKS problems FOR GALAXY Y GT-S5360 MOBILE
http://forum.xda-developers.com/showthread.php?t=1498327

musashihatred said:
FLASHING
Flashing is a way of updating or down-dating your device.
Odin is the tool used in it.
If KIES wont let u update. Flashing would be good but you just have to download the firmware you want.
Click to expand...
Click to collapse
can u make a tutorial(step by step) on how to flash using odin? and how to turn on download mode in galaxy y?

jayem123 said:
nice post there man or rather master? hehehe ( you are now my master ) , i really think this thread should be sticky.
very informative for the newbies out there as a head start, keep on posting and helping here master
if they will be needing another moderator here i will surely vote for you
Click to expand...
Click to collapse
aw ) my masteR!!!! long time! D hehe tnx. ^^

ronnieryan said:
can u make a tutorial(step by step) on how to flash using odin? and how to turn on download mode in galaxy y?
Click to expand...
Click to collapse
sure thing but it would be really better if you read some threads here. a lot of those stuffs are already here
1. download the rom you needed/wanted
2. download odin v1.85 w/ totoro.pit
3. turnoff phone remove sim + sdcard
4. open odin and put the files into:
boot
pda
csc
modem
something like that. put there the files you downloaded.
check if re partition etc are checked
then now get the data cable, and put the phone into DL-mode
(HOME+VOL-DOWN+POWER) hold till it boots into DL-Mode
pressing VOL UP- continue
VOL DOWN- Cancel
press the vol up so and youll be on DL mode
connect the cable wait for it to be recognized by the Odin, if ok pray and start.
just takes around a min to do so. the phone then reboots automatically. do a hard rest and boot again.
voila
since your a filipino you can check symbianize.com for infos. reading some guides there by our masters will surely help you
*so as the rules say here read threads first before asking though its ok for me. it would be nice if i'd helped you bro

ronnieryan said:
it would be nice to include how to make a hard bricked phone to soft brick
Click to expand...
Click to collapse
JTAG-ging is only solution to resurrect
a hard bricked phone..

musashihatred said:
NOTE: Noob is not a really good word. kinda discriminating. newbie better.
THIS will GUIDE how to get on foot if your just starting on Galaxy Y, most probably, ANDROID
1. First Things first. Know your Phone. before doing anything, just be on the stock for a while. Know all the things, settings, install some app and alike. This way, you'll know your way through. See apps like market, Maps and others, check bugs etc.
2. Second part is knowing a basic tweak of your phone, to be exact: BATTERY SAVINGS. Know your way from this apps. See how they handle your battery life. The purpose of this is to know the performance of your phone
3. So you feel much better knowing your phone, you can start rooting or installing some replacement apps Go, ADW, Pansi, Popups, keyboards its up to you. But i dont recommend instant rooting when your just getting on foot.
Rooting wont brick the phone, maybe but its in the least.
(I wont be giving links for many threads here are available already. Its hard just to give you everything when researching can't kill one)
WHAT IS ROOTING?
rooting gives you access to the system of your phone. thats it
Soft ROOT-stated in the above
Hard ROOT-gives you access to the commander of the system which allows you to access the device via shell extensions and ADBs
4. Same as step 1. See how does root work for you. Dont just access the system right away using an explorer. look for apps that can help you achieve your desired goal that requires root access. a good start would be RAM tweaks.
5. Removing apps that you dont need. Its the power of Rooting that grants you this. basically, it improves RAM usage and speed of the device especially when "app-example.apk" initiates on its own. ofcourse it increases the capacity of your device.
6. KITCHENS. for a start you can use the UOT kitchen which allows you to modify some parts of the device. as far as i know, mods like transparency, lockscreen and bootanimation wont work on stock dont ask why coz i dunno sorry. so using this kitchen can allow you to change statusbar appearance pull down notif bar, etc.
but, the MAIN concern of a KITCHEN is ROMS.
ROM is the thing that the device reads for it to run properly.
ROM development are for making a benefit that can help a device achieve its fullest performance. Speeding it up, etc.
You can see the Development Page for it
**EXTRAS:
FLASHING
Flashing is a way of updating or down-dating your device.
Odin is the tool used in it.
If KIES wont let u update. Flashing would be good but you just have to download the firmware you want.
PARTITIONING.
since SGY got a small memory for internal, u can use partitions in the SDcard to let it handle some memory for you.
BOOT recovery:
it is where you flash mini updates like rooting CWMod, UOT kitchen mods and others
**Clockworkmod recovery / CWM is a custom CWM it has additional features moreover see for yourself
i guess thats it ill just edit it if somethings new comes
THIS IS FOR NEWBIES, no noob persons exist: ONLY NEWBIES.
hoped this helps you can just PM me for assistance but for now please bear with this simple guide thanks
PS: im no dev but as soon as i got my laptop ill start im just using a netbook and my phone for learning. so thanks
Click to expand...
Click to collapse
I always like this musashihatred guy.
Very active in SGY development issues.
Keep encourage us (the NEWBIES) to learn.
Sent from my GT-S5360 using Tapatalk

bydefault said:
I always like this musashihatred guy.
Very active in SGY development issues.
Keep encourage us (the NEWBIES) to learn.
Sent from my GT-S5360 using Tapatalk
Click to expand...
Click to collapse
THANKS MAN
i just dont like some here that, Hey not for noobs or what. not for this.
but ill be selling my phone in the ff day but i wont leave this forum. ill still develop galaxy y ill be getting galaxy s =="

Video tutorial
ronnieryan said:
can u make a tutorial(step by step) on how to flash using odin? and how to turn on download mode in galaxy y?
Click to expand...
Click to collapse
http://galaxyygaming.blogspot.in/2012/02/flashing-with-odin.html

Thanks.. really helpful..

I just sold my galaxy y.
i sold it earlier. but pls dont stop sending questions and some guides. ill always be free to answer. ill be getting M130k tom. but i will always be here :d

Rooting Gnex GSM/HSPDA v4.0.2 Optus Stock

Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)

Helmet321 said:
Hey guys!!,
Yet another of my noob questions BUT, this time I think I'm going to take the plunge and root my Gnex!!! *scared* haha
I'm just having to many frustrating things happening on my stock Gnex, low responsiveness to the touch, slow-ish and well, isnt this what its all about!! =)
So a quick one, if anyone can point me in the most normal, simple and customizable direction, what do I do? I have searched for a while now so I have an idea where i want to go, either, Cynagon or AOKP...I'm hearing great things about AOKP...there from the same devs yeah?? (a guess)
So, I have a Samsung updated Gnex, in Aus and with optus. I'm technical so I'm getting a grasp on whats what but still not to clear on Kernels and radios....bit worried about that. Clockwork I'm guessing is like a boot manager?? Just asking that while I was here...
So Odin? Wug? CF-Root? I'm just not sure...
Thanks soooo much in advance guys.... I already appreciate your help. =)=)
*Excited!!!*
Cheers!!
P.S. I'd also very much like to return to stock form later on if I want...like locked oem and restored stock rom... =)
Click to expand...
Click to collapse
Try my ToolKit in the dev forum. Its simple, straightforward, easy to understand, there is a 1-click option which will do everything and every step is explained in detail.
http://forum.xda-developers.com/showthread.php?t=1392310
You can also use my ToolKit to flash a Stock Google Rom if you ever want to in the future.
With regards to Roms there are lots available to try by very experienced developers that will make your phone better and plenty of kernels to make it run ALOT faster. I use bigxie's Rom and franco's kernel.
Mark.

Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)

Helmet321 said:
Hi!!,
Thanks so much for your reply!
Funny as, I was JUST reading your guide. Awesome work man, very informative.=)=) and it would of taken some time to compile!. =/
Arm, I'm just wondering what file I need to backup to got back to the rom I'm on now? I want to be able to go back, if needed.
I don’t know what kernels are all about, and what do I need to do about Radios?? If I have the wrong one or something, does that mean I wont have signal?? Or bad call/signal reliability?
I'm looking at the build 23 of AOKP...I'm hearing its the go...and if i have a wrong kernal rom radio combo, what’s that going to do??, that’s if they correlate?? haha
Is security as issue?? Since these are built "freely" is there any exposure of private info?
I'm sorry for smashing you with all this, I'm just trying to get all the info before I do anything and to have a failsafe if I need to return for warranty.... =/
Thank you in advance!!! =)
Cheers.
P.S. Is Bigxie Apex?? I hear good things about that too!! haha. Its so hard, theres so many out there... Apex, Gummy, AOKP look great. I also really want a responsive, battery lasting, fast and importantly "stable" phone. So, not sure what you recommend. =)
Thanks already!! =)=)
Click to expand...
Click to collapse
If you goto settings, about phone then it will tell you all about your current rom build. If its a yakju build then its a stock google rom and can easily be found and reflashed via my ToolKit. If its been put on by your operator then you wont be able to obtain it online and you are best backing it up (unless you dont mind putting the google stock rom back on).
To do that you will need to set your drivers up first. This is important as nothing else can be done without this step. If you have Windows xp or 7 then its pretty easy, you can install the drivers automatically via the GNex ToolKit, then reboot your pc. Goto settings, developer options on your phone and tick 'usb debugging' then connect the usb cable to your phone (with it booted into Android). This should install adb drivers which are needed for communication when your phone is booted into Android. Start the ToolKit and select your current build version (which can be found in settings, about phone). At the top of the Main Menu you should see a serial number under adb mode which means your device is recognised in this mode. Select reboot options (19) in the ToolKit and Reboot phone to Fastboot (3). This is a bootloader mode for the phone outside of Android where you can flash and manipulate certain parts of your phone. As this mode is at a much lower level then the operating system it can be your saviour if your phone locks or wont start and you need to flash back to stock.
Once the phone has rebooted to fastboot mode the fastboot drivers should be installed on your pc. If nothing happens try unplugging and replugging the usb cable to initiate the drivers. If the drivers have installed before the ToolKit refreshes then you should now see the serial number at the top under fastboot mode this time. You NEED both fastboot and adb drivers installed on your pc for everything to work.
After the drivers have been set up you will need to Unlock the Bootloader to be able to have access to system areas on your phone. BE AWARE that unlocking the bootloader will erase EVERYTHING all data on your phone including the Internal Storage (virtual SD Card) so copy anything you need to from your Internal Storage accross to your pc and use the Backup option in the ToolKit to save any installed apps and associated user data that you want to keep. This is done in adb mode so your phone will need to be in Android.
If you want to back up your current Rom then Unlock the Bootloader, reboot your phone into Android, go through the setup quickly (as the phone will have been wiped), then goto settings developer options and enable usb debugging. Start the ToolKit and in the Main Menu select 19, 3 to reboot back to fastboot mode. Then you can BOOT into CWM Recovery without flashing it (9) and select backup/restore to backup your Rom/user data/boot image to a datestamped folder inside a folder called Clockworkmod on your Internal Storage. The rebooting into Android step after unlocking the Bootloader is important as cwm will not work properly without doing that.
Once that is all done you are ready to reboot into Android from cwm, get back to fastboot mode as before and select 1-click option (7). You will get a message on the unlock stage saying that your device is already unlocked but then it will just skip to the next stage. Be aware that when the device boots into Android the first time this is to let the user enable usb debugging for adb operations and if you have already done this then the ToolKit will wait for about 3 minutes before carrying on. Be patient as the ToolKit hasnt frozen, its just set to pause before carrying on.
Ok now thats all over with, on to your other questions lol. I would advise trying either romanbb's AOKP (build 24 should be up today) or bigxie's Apex 1.02 to start. Personally I use Apex as it has loads of customisation and runs very well but saying that I will be trying romanbb's new build when it is out.
Kernels are like the drivers of your phone. They set up how it works and what it can do. Custom Kernels can give better battery life and more power, performance, stability so its well worth trying them once you are rooted. They will tell you what builds they are compatable with but if you are thinking about the above Roms then you will be on Android build 4.0.3 and most new kernels work with that. I use franco's kernel but there are ALOT of established kernel developers working with the Nexus so you could try fugumod by nikademus or trinity by morfic. These are all flashed via cwm (download file, copy to Internal Memory, reboot to recovery mode once you have cwm flashed). You can enter cwm by rebooting to fastboot and using the volume buttons to select recovery, then press power to select, or from the reboot phone options in the ToolKit (19,4 in adb mode).
Bootloaders and Baseband/Radio updates are something to think about but not really needed if your phone is running fine. You wont notice any change if you update the bootloader as its just like updating your bios on a pc. Just gives some extra functionality or updates some deep down settings. Radios control the communication part of your phone and updating to a new one may improve battery, signal, wifi, gps lock. You can update them by either grabbing a premade zip and flashing via cwm or download the .img file and flash that via the ToolKit.
Dont worry about malware included in custom roms as long as its by an established developer. They would never put anything dangerous to the end user in one of their roms as it would harm their reputation and if anything was found by a user the rom would be taken down imediately by us mods to keep you safe.
I think thats everything you will ever need to know lol. Sorry theres alot I wanted to make sure you had all the ammunition you needed to continue and it took soo long to write I had lunch half way through
good luck.
Mark.

Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!

I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium

Helmet321 said:
Ohhh man, thank you sooo much. That’s a lot of info and I really appreciate you taking the time to explain that to me Mark. Thank you!!!!
Ok, I’ve been watching some videos, one off of GalaxyNexusRoot.com. I think its his YouTube chan… He's seems pretty cool. Shows you what to do. I sort of want to do it manually so I'm understanding it all?, if that makes sense? I like to know exactly what my device is doing, why and how? haha. I'm a bit pedantic like that.
Arm, only a couple of things....I'm draining your life here...haha
I have a Samsung updated Gnex, throwing that in FYI. =) Not sure if the warranty centre would realise, probably so I should back it up as it is...on this note quickly, I do want to have a yakju (Google) updated phone though...hehe.
When I back up, does it flash everything? the rom, kernels and radios? (Mostly for my Stock setup for reversion, and understanding...)
With roms, where can I get the G'apps from? (If needed) And or the SupUser/Root files? (Separately I mean, so I can do this manually...if I'm understanding it properly... =/ )
Also, do these apps and others update as normal? Or di i have to update the whole ROM to update them? Like Maps (Navigation more importantly), GTalk, MarketPlace etc...?
And finally....phew...haha arm, sorry....
I'm looking at doing this because currently my device just seems a little non-responsive, laggy-ish and its turned off once.. =/ Is this all normal?? I thought for a minute my screen was faulty, like touches don’t always respond...I mean 90% of the time they do...I know, I'm nuts but it just ruins it for me... I uninstalled Beautiful Widgets and it’s sort of been better…maybe some apps aren’t configured with ICS yet also…I'm thinking it just could be the build? What do you think??
It's kind of weird to think that an individual dev has made. and is making more progress than the developers of the phone/software?? hahah...Anyway, I hope I've made some sense and I really, really, really appreciate all this Mark, all your time and patience with me. =)
Thanks again!!!!
P.S.... This should be it I SWEAR!! haha....
Just wanted to put these here...these are "some" of the problems I've been having... =/
http://forum.xda-developers.com/showthread.php?t=1500545
http://forum.xda-developers.com/showthread.php?t=1490335
http://forum.xda-developers.com/showthread.php?t=1500236
http://forum.xda-developers.com/showthread.php?t=1487946
Thank you...again!!!
Click to expand...
Click to collapse
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.

What does stock stand for?

udmbrian said:
What does stock stand for?
Click to expand...
Click to collapse
It means the version that the manufacturer put on the phone before it was shipped or a version that is supplied by the manufacturer. Unaltered by developers.
Mark.

mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App

Helmet321 said:
Thanks again!!!!
Ok cool. So when new versions of the apps come out on the market, I wont be able to update them normally will I? Which is ok but just wondering how that is going to go down. Haha.
Lastly, sorry man, I'm almost there. Haha. CWM doesn't backup kernel? Like my stock one?
So it basically makes a "phone" image, ExtPartition and all? Or can you choose these options?
Right, I'm so close now I reckon, today will be the day... I can feel it!!! Haha.
Thank you again!!!!!!!!!
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes of course you can update google apps via the market as normal.
Cwm will back up your boot image which contains the kernel. So yes it does back up the kernel.
You can not choose which options to back up but you can choose which parts you want to restore via the advanced restore option in cwm.
Let me know how it all goes
Mark.

El Daddy said:
I just want to thank the OP for asking the right questions and taking the time to figure out how "hack" his/her phone correctly instead of jumping in blind.
I hope other beginners follow the OP's lead.
That is all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey El Daddy,
Thanks man. I try to reframe from being a pain in butt.... not sure how I've gone with that but, Haha. I appreciate what your saying. I just want to be sure what I'm doing and to have, as Mark said, all the "ammo" I need.
Cheers.
Sent from my Galaxy Nexus using XDA App

Great questions and answers from both of you. Just got this phone and trying to figure out where to start. Briefly read the toolkit instructions. Just haven't had the time to sit down and plow through it. Thanks both of you.

mskip said:
A cwm backup will back up system, data, boot, recovery and cache but it will not back up your radio image so check your version in the about phone screen first so you know what you need.
The latest gapps flashable zip can be found in the development forum. Did the youtube channel not give a link to the root files? If not then I have attached the 2 files you need to push. Make sure to set their permissions too after pushing.
Without knowing exactly what you have put on your phone its hard to comment about responsiveness but as stock roms dont have all the optimisations that custom roms have they are definitely slower. A custom rom and kernel will surely sort out your problems
Mark.
Click to expand...
Click to collapse
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....

Helmet321 said:
Thanks so much again Mark...This is Great!!
Ok, just before I do this...I'm like right here at the PC...ready! haha...
I understand all of it now, well. in theory...
Thank you for the DL link to the root.zip...
I DL'd the android SDK Kit zip also, but there’s no fastboot.exe??? Or anything like what I need?? haha, I may just be missing something here...
One of you links on you manual guide is broken...I think, that’s where you had it...I didnt want to harass you again but just some final things. =)
I'm really after all of what I need to this manually...for knowledge etc?? Hope you understand... You made this wicked awesome Kit, and I'm stupid and not using it...hahah...
So as far as I can see, I need:
- Samsung Drivers - which I have and that bits done... =)
- fasboot.exe etc (Android SDK Gear)
- Latest CWM.zip
- **Rom of my choice, which I'm going to take your advice and go with Apex. =) Latest 1.02 yeah??
- Franco Kernel, I'll try stock, but my feeling on it is that that’s probably been my major issue, or the cause of most of them... =)
Phew....I think that’s it...am I on the right track??
I cant thank you enough with all this Mark....seriously...your a very patience man. haha
Cheers. =)
**Update**
P.S. I have attached a file. Mark can you check it out and see if that what I need in regards to Android SDK stuff? I just got this now after I posted the above....
Thanks again... =)
***Update...again....haha***
Arm, just looking at these files, whats the boot.img? does that get copied over to the phone? Or is it just a command? The su & Superuser files in this zip are like a different size and modified later than your ones (newer??? =/)....I'm not sure what that would really mean...probably has nothing to do with anything but just thought I'd check with you....
Click to expand...
Click to collapse
Looks like everything in that zip is ok for what you want to do. The superuser.apk is a different size but im sure it doesnt matter.
In order to push the 2 files across to your phone you need to have booted into Android using an insecure boot image. This is a stock boot.img that has has some simple text changes to allow temporary root access (otherwise the files wouldnt copy across) Using fastboot you boot the boot.img file and then once you are in Android you push the files across and set their permissions. When you reboot your phone your original boot image will be used and you should have permanent root via the files.
Looks like you are all set
MArk.

Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)

Helmet321 said:
Oh ok. So it doesn't stay on the phone?, its temporary??
So if this file say, is corrupted or malicious, (not really possible probably byt...) I'm in trouble? haha
Sorry, I have everything I think now, I grabbed the SDK of the Android website and I'm comfortable with that cause its "legit" I suppose. It doesn't have a boot.img file though. Can I make one myself so I know where its coming from? And where does this normally come from?
Silly stuff I know but, I told you, I'm CRAZY!! haha....
One very last thing...the permissions, whats that part all about...
Other than that, I'm pretty sure I'm sweet now...I also grabbed the latest CWM zip off the website too...so I'm cool with that.
......geez.... I'm killing you aren't I....I think you deserve (need) at LEAST 1 beer after all this....haha...
Thanks x 1,000,000...seriously.... =)
Click to expand...
Click to collapse
Its perfectly possible to make your own boot image but to be honest you might take another day or 2 to get all the required components and research what you need to do lol
If you go to your settings, about phone screen and tell me the build version (4.0.1, 4.0.2) and whether its a gsm or lte device (im assuming gsm as lte is america/canada) then I will attach the boot image I made for that device so it will definitely be right and safe. You can also use the su and superuser.apk files I attached earlier if you are unsure about them.
I dont mind all the questions as long as you end up feeling confident enough to get your phone rooted mate I would rather people ask too many (but the right) questions than just go blindly into something have no understanding about and end up in trouble.
Mark.

Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up (so to get all the rom, including the auto restore recovery??)
-Set SU perms...with su.zip or su+superuser.apk... (if I'm right also, this step only if you want root perms on stock?, not sure what you would do with it though, only if you want to remain this way I suppose... =/ )
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)

Helmet321 said:
Your a legend Mark, I swear!!....haha
Ok, well, its a GSM, 4.0.2 Samsung updated Nexus....I think... I can attach some images. =)
The end of the line here...haha, arm, I just watched a video that completely skipped the boot.img part...weird...anyway, with the "su" part, I have 2 files there, as you've kindly provided, but in that step doesnt it need to be a su.zip sort of configuration? Just running it by you before I do this...
P.S....again....haha, arm, if I'm thinking about this right, does the step with "fastboot boot boot.img" will that affect the stock image?? As I think, if I'm right you have to do that "before" you flash your recovery?? In my mind would it be right in assuming....
-Unlock bootloader
-Flash recovery
-Make a Back up
-Set SU perms...with su.zip or su+superuser.apk...
Is this right??
I was reading your "manual" post and I'm a little confused...as in, you cant reboot into Android after flashing recovery (to back up) as it will delete it, but to do so, you need to reboot into Android to delete the auto recovery flash file?? And you need su perms yeah?? Am I right here, I'm probably going crazy-ier...haha cause I've been at this for 2 days...haha...
Seems the boot.img step is the same as if you would flash a su.zip...(which I dont have, only the su file (no extension) and the su.apk...) not sure if thats the same...just getting my head around it here.... =)
Maybe I'm thinking CWM will "back up" the su perms etc and affect the "stock rom"...if you back it up with the perms, wouldnt that be included?? Maybe thats were I'm getting it wrong...haha.
Finally...........serious.....
If and when you delete the auto recovery file (if that really does delete it completly, I'm probably wrong about that too...) how does it restore??
Thanks mate. =)=)
I think thats it...when I have my head around these final things...and the last couple of files...Its time.... =)=)
Click to expand...
Click to collapse
There are 2 ways of rooting your phone. The easier (and non learning way) is to flash cwm recovery and flash the superuser.zip straight to the phone. If this is what you watched then tbh you might as well be using my ToolKit as you wont learn anything from the experience. The other way is the method my ToolKit uses which is to boot the phone with the insecure boot image to gain temporary root, then using adb to push the 2 files that I sent to your phone and set their permissions, then rebooting to complete the root procedure. The 2nd method is the one I thought you was gearing up towards and the best way if you want to actually learn something, otherwise as I said you may as well use the ToolKit.
I have attached every file you will need for the 2nd method and if yo uread below these are the instructions you will need to follow to root your phone. Extract the attached files to a folder on your pc, browse to this folder then HOLD the Shift button on your pc while right clicking on a blank area of the Windows Explorer. Select 'Open command window here' which will open a command prompt in the correct folder where your adb and fastboot files are.
These instructions are for after you have installed drivers:
fastboot-toolkit devices
Click to expand...
Click to collapse
this will return a serial number if your drivers are installed.
fastboot-toolkit oem unlock
Click to expand...
Click to collapse
and follow the instructions on the phone to unlock your bootloader.
Now if you boot into Android RIGHT after unlocking the bootloader it will restart the boot half way through so you want to do this normally BEFORE using your insecure boot or the reboot half way through will lose your insecure access (if you get me)
fastboot-toolkit reboot
Click to expand...
Click to collapse
to get your first boot in. Once the phone has booted up and you have gone through the setup wizard, go to settings, developer tools and select 'usb debugging' to enable adb control.
adb-toolkit devices
Click to expand...
Click to collapse
should return a serial number if your adb drivers are installed.
adb-toolkit reboot bootloader
Click to expand...
Click to collapse
to get back into fastboot so you can boot from the insecure boot image
fastboot-toolkit boot boot_gsm_ICL53F_insecure.img
Click to expand...
Click to collapse
to boot your phone into Android from the insecrure boot image. Once your phone has booted into the lockscreen you can carry on with
adb-toolkit root
adb-toolkit remount
Click to expand...
Click to collapse
to mount your /system folder for root access.
adb-toolkit push su /system/bin
adb-toolkit push Superuser.apk /system/app
Click to expand...
Click to collapse
pushes the 2 files across to the correct folders on your phone.
adb-toolkit shell chmod 06755 /system/bin/su
adb-toolkit shell chmod 06755 /system/app/Superuser.apk
Click to expand...
Click to collapse
sets their correct permissions.
Lastly if you are flashing cwm then you will need to rename the recovery restore file if you are on a samsung rom. If this file is present on your phone and cwm is flashed, then on the next reboot the stock recovery will be restored and you will lose cwm. To get back to stock recovery in the future you just flash a stock recovery image.
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
Click to expand...
Click to collapse
will rename the file is it is present.
Thats it! Reboot your phone and you should have root You can check this by downloading root checker from the market or just download a root app such as adfree or setcpu.
Mark.

I see you are replying to my thread already as I was making some changes so re-read the instructions as I rearranged them a bit to make more sense lol.
MArk.

I love my Note - Trying to get back to 5.1.1

I love my Note 4 so much that I tried for about 2 weeks to fix it's constant rebooting issue. Went to ATT & Samsung repair center and they couldn't get it to flash. However, it stills turns on, I just generally need to pull the battery for a few minutes to get it to boot.
With that said, I'm not incredibly knowledgeable in this area. I've downloaded ODIN and found lots of resources for the exact steps to follow, however, I'm not sure where I can locate a version of 5.1.1 for ATT. To me, this seems like my only fix for my phone. I've tried clearing cache and factory resets etc. My phone is unlocked. Am I missing anything that you can think of? Can someone link me to a reputable source for the appropriate files?
You seriously cannot imagine how happy I'd be if I can get this thing working again. Thank you!
PS, if you think there is a more stable version than 5.1.1, I'm open to that too.

Bump. Any help is greatly appreciated. Thanks!

Google is your friend...
http://rapidgator.net/file/2ab3e0dc...om/att-galaxy-note-4-sm-n910a-stock-firmware/

Punker1234 said:
I love my Note 4 so much that I tried for about 2 weeks to fix it's constant rebooting issue. Went to ATT & Samsung repair center and they couldn't get it to flash. However, it stills turns on, I just generally need to pull the battery for a few minutes to get it to boot.
With that said, I'm not incredibly knowledgeable in this area. I've downloaded ODIN and found lots of resources for the exact steps to follow, however, I'm not sure where I can locate a version of 5.1.1 for ATT. To me, this seems like my only fix for my phone. I've tried clearing cache and factory resets etc. My phone is unlocked. Am I missing anything that you can think of? Can someone link me to a reputable source for the appropriate files?
You seriously cannot imagine how happy I'd be if I can get this thing working again. Thank you!
PS, if you think there is a more stable version than 5.1.1, I'm open to that too.
Click to expand...
Click to collapse
What is your Baseband? Maybe you can't go back.

Heya guys.
Thank you for the link! I seriously googled and browsed forums for days looking for it. I even went to the Android website with a slew of different version but they did not have the ATT versions. Anyway, I'm going to give this a go but still pretty green to it. I was going to follow the instructions from this post - should work right? https://forum.xda-developers.com/note-4-att/general/expert-phone-trashed-t3573110
And Norbarb, I have no idea what my Baseband version is. I did a quick google to see if I can locate it somewhere but couldn't figure it out. How can I check?
I do appreciate your help.

Punker1234 said:
Heya guys.
Thank you for the link! I seriously googled and browsed forums for days looking for it. I even went to the Android website with a slew of different version but they did not have the ATT versions. Anyway, I'm going to give this a go but still pretty green to it. I was going to follow the instructions from this post - should work right? https://forum.xda-developers.com/note-4-att/general/expert-phone-trashed-t3573110
And Norbarb, I have no idea what my Baseband version is. I did a quick google to see if I can locate it somewhere but couldn't figure it out. How can I check?
I do appreciate your help.
Click to expand...
Click to collapse
Can you reboot to recovery?? There's some info there regarding your current setup

Ironically, now I can't even get the phone to turn on. I bought a battery charger for the Note battery to see if that is the issue. I can't get the battery to charge even when it's plugged in. That arrives Monday so I'll update shortly.

Quick update:
Baseband is N910AUCS2EPK3. I'm not sure if that means I can or can't roll back to Lollipop.

Popped in the charged battery from my new charger and it came right on. Had it on for a little bit just messing around with things. After rebooting it myself a few times, it now is reverting back to it not even turning on, even with a charged battery. I pull the battery 10-20 times, hold the power button without the battery to clearly out any remaining electricity and still no go. I have 2 batteries and neither work. So I'm going to let it sit and if I can get it to come on, install Wake Lock.
Does anyone know if I can revert back to 5.1? I'm not sure how my Baseband effects that. Thank you for all of your help! If I can't get this, I think I may go back to my S3 vs a Pixel.

Punker1234 said:
Quick update:
Baseband is N910AUCS2EPK3. I'm not sure if that means I can or can't roll back to Lollipop.
Click to expand...
Click to collapse
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.

ljjehl said:
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.
Click to expand...
Click to collapse
Holy crap, awesome man. Thank you. At this point, I can't even get the phone to turn on with 2 different batteries. Tried holding the power button down for awhile and letting it sit for hours and still nothing. Not sure what the deal is with this thing. I'll keep attempting.

Punker1234 said:
Holy crap, awesome man. Thank you. At this point, I can't even get the phone to turn on with 2 different batteries. Tried holding the power button down for awhile and letting it sit for hours and still nothing. Not sure what the deal is with this thing. I'll keep attempting.
Click to expand...
Click to collapse
Try holding power button, home button and volume up all at the same time while its powered off. If you can get to Recovery screen here, then you just may be getting somewhere. I would then wipe data/factory reset, then reboot again. If this doesn't work, you can then try holding power botton, home button and Volume down at the same time. This gets you in bootloader mode. Once you get there, only way out at this point is pulling battery (to start over) or get started on Odin flashing.
At least I have kept OTA from working, with this debloater from this link: https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294

ljjehl said:
Try holding power button, home button and volume up all at the same time while its powered off. If you can get to Recovery screen here, then you just may be getting somewhere. I would then wipe data/factory reset, then reboot again. If this doesn't work, you can then try holding power botton, home button and Volume down at the same time. This gets you in bootloader mode. Once you get there, only way out at this point is pulling battery (to start over) or get started on Odin flashing.
At least I have kept OTA from working, with this debloater from this link: https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Click to expand...
Click to collapse
Thanks. Yea i can't get into recovery or the download mode. I bought a battery charger just thinking my phone wasn't charging them. The first time it started up perfect. Now I can't get it to come up at all. As mentioned, I'll keep trying. Wondering if something else has gone wrong, or if it's software related still.

ljjehl said:
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.
Click to expand...
Click to collapse
Got the phone to turn back on. Quick question. In your post, you mention 4 ODIN files. I only have an MD5 file and a PT file. Is there something I'm missing? I downloaded the stock rom from the top of my post. Thank you!

Punker1234 said:
Got the phone to turn back on. Quick question. In your post, you mention 4 ODIN files. I only have an MD5 file and a PT file. Is there something I'm missing? I downloaded the stock rom from the top of my post. Thank you!
Click to expand...
Click to collapse
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
There should be a zip in here that you have to extract four files to a folder. You will use the Odin exe program to look for those files. Just follow my howto notes I wrote in the link I posted. This is to the Marshmallow stuff. Forget the MD5 and pit file unless you know what you are doing. Since I don't know where that came from, I won't even suggest those 2.

ljjehl said:
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
There should be a zip in here that you have to extract four files to a folder. You will use the Odin exe program to look for those files. Just follow my howto notes I wrote in the link I posted. This is to the Marshmallow stuff. Forget the MD5 and pit file unless you know what you are doing. Since I don't know where that came from, I won't even suggest those 2.
Click to expand...
Click to collapse
Ironically I'm looking to get rid of Marshmallow because I think 6.0.1 screwed up my phone. It was working great prior to that. So the LP files I have are the MD5 and pit, supplied in the 3rd post. Is there somewhere I should look for LP files? And to be clear, are there "regular" rom files for general use, and then ODIN specific files? ie, you could have a "regular" 5.1.1 file, and then ODIN specific 5.1.1?

Punker1234 said:
Ironically I'm looking to get rid of Marshmallow because I think 6.0.1 screwed up my phone. It was working great prior to that. So the LP files I have are the MD5 and pit, supplied in the 3rd post. Is there somewhere I should look for LP files? And to be clear, are there "regular" rom files for general use, and then ODIN specific files? ie, you could have a "regular" 5.1.1 file, and then ODIN specific 5.1.1?
Click to expand...
Click to collapse
Well, I have the 5.1.1 Odin files also, but will have to zip it and upload, unless someone else has a link faster

ljjehl said:
Well, I have the 5.1.1 Odin files also, but will have to zip it and upload, unless someone else has a link faster
Click to expand...
Click to collapse
Is there a way to use the files that I have? Not using ODIN? Or is that not recommended?

Punker1234 said:
Is there a way to use the files that I have? Not using ODIN? Or is that not recommended?
Click to expand...
Click to collapse
With the mess you have, I would think you want to Odin flash a whole new setup. You don't know what's wrong and a partition could be corrupted. If it's hardware, nothing you really could do about it anyways

ljjehl said:
With the mess you have, I would think you want to Odin flash a whole new setup. You don't know what's wrong and a partition could be corrupted. If it's hardware, nothing you really could do about it anyways
Click to expand...
Click to collapse
Got it. I looked around and cannot find the files for ATT. I see them for others I think, but ATT is a ghost. Would you mind uploading if you can? If not I understand. I appreciate all of your help! Crossing my fingers that my Note 4 is still alive and well.

Pixel 2 xl bricked i think so..

Hey guys i have a serious problem..i tried to unlock bootloader and install another rom but my phone i think so its dead... :crying: I unlocked it succesfully,installed twrp,then rom by recovery mode,i made reboot the device,and the rom wasnt installed,so i made again reboot device in twrp by the tool https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 and then it was like everything was deleted..no partitions nowhere,like everything had gone..and now i cant even reboot on twrp just on fastboot and i can only lock/unlock my bootloader.When i lock i take the message "Cant find vaild operating system,The device will not start....:crying: The case is that i didnt made any kind of wipe...how its possible this to happen?Can any professional guy help me here because i tried so much to bring it back to the normal condition but i dont see any solution anymore..

You have a Pixel/Nexus device. Download and flash the factory image the correct way from Google and start over.

Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..

Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Good instructions at top of this page, then the download for your phone model is below.
If you do not understand any step, Google it, then read and understand completely
before proceeding. Be sure you have most current version of Android Tools.
https://developers.google.com/android/images#taimen

Don't panic and make it worse. Make sure you have adb/fastboot environment and drivers on your computer and follow the directions for reinstalling stock.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418

Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!

Yeah as others above have said, don't panic. I've been flashing/ rooting/modding since the way back and one thing I've learned is, it's VERY hard to brick a phone completely. Especially with newer ones, there's almost always a way to recover your phone, and especially since you have fastboot, you're not bricked either. Flash the stock rom through fastboot and you should be all set!

also make sure that your cable is good. i had major problems with many cables. finally one cable actually worked. took me hours to realize tha the cables were the culprits.

I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.

mac796 said:
I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.
Click to expand...
Click to collapse
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!

thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
Az Biker said:
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!
Click to expand...
Click to collapse
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)

Jinthegodstyle said:
thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)
Click to expand...
Click to collapse
Dude. Start from scratch. Can you get in fastboot and is your bootloader unlocked? Are you doing this all with a tool or are you manually putting in commands It's hard to tell you what to do without all the info.
Edit.... Just saw you used a tool.... I don't care for tools. because of stuff like this. The tool should have installed the adb folder on your computer. Find that folder and open it. Download the Google zip file with stock os and Unzip into your adb foldee or SDK folder . Open the file from Google. While in there open a terminal. Have phone in fastboot mode and plugged in. Type "fastboot devices"
If it shows a number, you are connected.
Now run the bat file and it should install the os
Read all the way through then reread it .
Carefully follow steps. Forget about twrp for now.
https://developers.google.com/android/images
Don't forget to open terminal as administrator

Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!

Jinthegodstyle said:
Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!
Click to expand...
Click to collapse
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches ?

Badger50 said:
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches
Click to expand...
Click to collapse
Thx for advice mate!! Finally after yesterdays adventure with my new toy,today i flashed without any issues in 5 minutes the rom i wanted and it was more easy than i imagined..you see after many xiaomi phones i was confused and couldnt imagine how easy could be on google phones..Now i wont touch nothing since evertything works preety good!! Thx again!!

CyberpodS2 said:
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!
Click to expand...
Click to collapse
when rma'ing it, one should defo go with locking bootloader though, i reckon.

xflowy said:
when rma'ing it, one should defo go with locking bootloader though, i reckon.
Click to expand...
Click to collapse
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?

I always always always make sure the device boots before i ever lock the bootloader. I've read to many horror stories.

With this kind of phone, i think anyone should refrain from using any kind of so called "tool", aside from the basic adb n fastboot itself.

Badger50 said:
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?
Click to expand...
Click to collapse
does this also apply to the critical unlock method or do i, at least, have to lock critical?