Database Users

What now?

First of all I just want to say WOW what an insightful and creative community you guys got going on around here. A lot of smart people on these boards. Thanks for the resources you guys provide to make having a cell phone into a hobby.
I have just successfully rooted my phone after hours of deduction and have flashed RC33 and a radio ending with 1.1. I've spent about 4 hours getting to this point and still feel behind the game. What motivated me to do this was the Official Hero Rom in the Android Development Thread and that is my ultimate goal insofar.
However, now that I've done this I don't want to take any unnecessary risks. I've used the dandy search feature and done hours of research as well as lurk on here since the launch of the G1 when I picked up the phone on launch day. I know about all of the informative links and they're great and I've reviewed them thoroughly but am still fuzzy on a few things.
I've read that there are different types of SPL's some brick and some don't. Please correct me if I'm wrong but my understanding of an SPL is that it is basically the update.zip file in my SD card. Currently that is a build of RC33 in my card along with recovery.img. For some reason I feel that this is not all as far as an SPL is concerned. If someone can concisely clarify this for me that would be great.
Also before I jump on Hero, what is a good cupcake ROM around here that is stable and not lacking many features that can easily be blinged out with one of the awesome themes you've got floating around here. I'm open to all enthusiastic suggestions. What tips do you guys have for me to move up to one of those?
I have not even begun to delve into App2SD or Nandroid but am getting a clearer image as to what they are and how they function. Any helpful tidbits on the two subjects would also be greatly appreciated, however they are not my main concern immediately.
Again thanks guys I've got work in about three hours now lol so I'm going to get some shut eye however I'll be back tomorrow. Soon, I hope to contribute to what you guys have got going on.

Unfortunately your hours of deduction did not lead you to this thread. Which has a link to this thread. Which has definitions, two I am posting here:
Bootloader – the SPL and IPL of a flash based device. See jashu’s description here.
SPL (Secondary Program Loader) - You get to the SPL by holding the camera button while powering on your phone. This is where you flash NBH images. See bootloader above.
Click to expand...
Click to collapse
Which links you to a greater explanation of what the SPL is.

Personally, I don't think the Hero builds compare with Cyanogen's Scary Experimental builds. I believe you sacrafice a lot of speed to gain very little (if any) functionality. Don't let the misnomer of "Scary Experimental" throw you off. His latest 3.5.3 blows everything else away. It's within a build or two of being declared stable. And most of the tiny little issues with 3.5.3 can usually be fixed with instructions being posted in that thread.
Moving over to Cyanogen's 3.5.3 is braindead simple too. Don't rush, follow the recommended upgrade path, and you'll be set. It does all the work for you, and it doesn't require the sometimes dreaded new SPL (which, BTW, is not nearly as risky as some will lead you to believe ... you just have to properly follow the required steps). Still, will this being your first attempt at any of this, you'll find it much less taxing on your nerves by sticking with a more straightforward upgrade. Cyanogen's is a great way to get your feet wet. And in the end, you'll end up with a blazing fast phone with all the bells and whistles too. Your phone will impress the moment it first boots. There are themes available now, and more will be coming once it hits stable. Apps2SD are automatically done for you if you have your sdcard formatted correctly. There are a myraid of ways to get the correct partitions on the sdcard, so do that before anything else. It will increase your chances of making this successful on the first attempt. Remember that a wipe is not necessarily a bad thing, it's usually that a failure to wipe is what caused your problem in the first place. Wipe if it's recommended. Read the comments to determine when it required, when it's just a recommendation, or when it's not necessary.
Be methodic. Since this is your 1st attempt at this, you'll be doing yourself a huge favor if you grab everything you need all at once. Don't try to take any shortcuts, follow the steps or instructions to the t. Make sure you have the latest radio installed (and the new SPL should you pick a build that requires it). Although they usually list the latest builds in the 1st post of a particular topic, occasionally they will release in intermediate fix within the thread itself. Check the last few 10 or so pages of comments for your build of choice to see what build is recommended at the time. Usually, you'll want to grab the latest build, but that's not always the case. Bleeding edge is not always best (althought with C's Scary Experimental, I've eagerly awaited each and every update because it's only gotten better each time).
Since you've done your research, go back and outline the entire upgrade path. Write it down for reference. Make sure your Windows driver are up-to-date, have the latest ADB installed on your computer (it makes things much easier if you use ADB if possible), don't do anything until you can devote a couple of uninterrupted hours to the upgrade process, and I cannot emphasize enough to WIPE as necessary. Hell, don't install any programs or fiddle with any settings. WIPE each step along the way until you get the final build installed. If something doesn't seem right any step along the way, don't proceed to the next step. WIPE again and re-flash. See if that fixes your problem. If it does, the proceed. If it doesn't, see if it's an issue that fixed with the next build you'll be flashing. If so, proceed. If not, look for another solution. Proceeding at that point _might_ be okay, just be aware that you might get yourself into a situation that requires re-rooting your phone.
Make sure that before you do anything else that you have one of the modified recovery images flashed to your phone. They're modified for a good reason.
If things go bad, don't panic and start posting that you've "bricked" your phone. Chances are you haven't. Very few phones get "bricked" to a point you can't fix it yourself. When people around here see the term "bricked" as a subject in a post's topic, it's a red flag that becomes a red herring for you. You may get into a boot loop or something, but it's usually fixable with a WIPE and an update.
Also, keep DREAIMG.img in the root of your sdcard at all times. Don't move it, don't delete it, don't rename it. It can, and will, save your ass if any of this hits the crapper. Carry it with you at all times. If you have DREAIMG in the root directory, you'll always be able to get your phone back to an operating condition, wherever you are, whenever you might need it, without the need for a computer. Yes, it would be starting all over again, but it would give your phone basic functionality if all goes to hell and you're not near a computer or don't have a USB cable or something.
None of this requires a PH.D. It's actually quiet simple. Most people that run into problems have simply missed or skipped a step, or failed to wipe as required. Knowing recovery proceeds in advance will be helpful, but even that is pretty straightforward and easy to follow. I've done all these flashings, re-flashings, recoveries, etc., so much that I --think-- I have the terminal commands etched in my memory. And I do. But I still refer to the on-screen steps to make 100% sure I'm typing things correct. I hit enter only after I'm confident I didn't type a 0 when it should be O (hehe). I look at the screens during the whole process for indications of success or failure. And I make sure that I am not distracted by anything when I upgrade. Lock yourself in a room by yourself after you've emptied your bladder. If you do get interrupted or have to take a bathroom break, write down the next step. Don't assume you'll remember. And don't even think of making or taking phone calls until you've finished this whole thing.
Read in advance.
Search as necessary.
Ask, in the appropriate forum and thread, when all else fails.
You'll do fine.
Good luck.

Lost all hope...

It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.

Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
So where are you at right now. What rom and what exactly have you done to your tab.

Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD

shaun298 said:
So where are you at right now. What rom and what exactly have you done to your tab.
Click to expand...
Click to collapse
At this moment right now, my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.

Moscow Desire said:
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
Click to expand...
Click to collapse
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.

Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.

Mkami said:
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Click to expand...
Click to collapse
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD

cruise350 said:
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Click to expand...
Click to collapse
What do you mean by RUU? Also I've tried a couple of the OTA updates, when I first got the tab it was on 3.1 HC didn't even update it or anything, just had a custom ICS ROM on it. Do you think you can post the steps or anything on how to do this properly and go fresh? It would be sincerely appreciate buddy.

Moscow Desire said:
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
Click to expand...
Click to collapse
Hmmm....I'm not even sure what I am doing wrong but whatever it is, it seems to be not working. I looked for you post for the earlier person that you did, but don't know what it is under. By the way when I first bought the tab it was under 3.1 HC and after getting flexreaper it became to ICS 4.0.3...
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.

Mkami said:
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Click to expand...
Click to collapse
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.

im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire

lcd047 said:
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
Click to expand...
Click to collapse
You're right! I was able to fix it and boot up to the usual! Thanks mate!

chismay said:
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
Click to expand...
Click to collapse
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!

Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Mkami said:
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Click to expand...
Click to collapse

tkirton said:
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Click to expand...
Click to collapse
Hahaha! Good job on guessing all that! I just followed your order from step to step and I was about to boot up normally! Everything might be erased and stuff, but hey at least I have my tablet working again :good: Case solved!

[Q] KitKat on a rooted Note 3.

Hi Guys,
First, I beg of you not to say RTFM on similar questions here regarding this. I have read them, and read them in their entirety. The problem I have is that none of them list how to get me though my issues on my Galaxy Note 3 SM-N900A.
My problem is that I (as many others) really want to upgrade to the Kit Kat OTA released from AT&T a week or so ago. The thing is, I did root my device and as everyone know's this fails any OTA updates.
My question is two fold, but first I would like to explain that I rooted my device NOT for being able to install any custom ROM's. In fact I never had an interest in doing so as I actually like the stock OS's which right now I am still running 4.3. I rooted it specifically to be able to run network / packet sniffers on my own home network as a method to learn a little more about how things go over a network, seeing what I can learn and see if I can find any vulnerabilities. I also used it to try and clean bloat ware and other programs that with out root I can not uninstall or use, such as certain fast reboot apps. So, I really had no intention of using the Root to get me a custom ROM, as I wouldn't even know where to begin.
So my questions are this. Is there anyway that I can "un do" the root in order to let the device act as if it were never rooted? Or, is there anyway to force the OTA regardless of the device being rooted. My biggest fear is losing all the apps and files that I have on my device and I have never been able to get any kind of back up app to work, especially to restore anything from them.
I had read that one can use ODIN to flash the Kit Kat ROM, but while I have installed ODIN on my laptop, I am clueless on how to use it. I tried everything, but even with the USB drivers installed and working (I know this because plugged into the USB port, I am able to browse all the files on my device, yet ODIN continues to tell me that no device has been found.
Can someone please help me to understand what I need to do? Again, I don't care if I lose Root, I care that I don't lose all the stuff I spent months installing and getting my device where I want it. I really need someone to explain somethings to me as if I were a two year old, with out scalding me and making me feel like a complete idiot. I came here because everyone I have talked to told me that you guys would be the ones that could help me, and if you can't, then I am screwed and will have to just wipe the entire device and I just can't do that. I may wind up having to buy a new device and just transfer over what ever I can, however, in the mean time that is not an option.
To this end, I come begging for some serious help since I know you guys are the literal gods of Androids. If I must take some kind of custom ROM in order to get Kit Kat, I am somewhat willing, but I do not fully understand or know what ROM I would want to install as I have never in my life seen a custom ROM and what the benefits of having one are which is kind of why I really want to stick with the stock ROM and just keep getting the updates via OTA.
I have all the faith in the world you guys can help, I just don't know if anyone is willing to help since I know similar questions have been asked, but I do not know how to use what I learned for my particular device.
Thanks very much.
EU

Dardwizzle said:
Hi Guys,
First, I beg of you not to say RTFM on similar questions here regarding this. I have read them, and read them in their entirety. The problem I have is that none of them list how to get me though my issues on my Galaxy Note 3 SM-N900A.
My problem is that I (as many others) really want to upgrade to the Kit Kat OTA released from AT&T a week or so ago. The thing is, I did root my device and as everyone know's this fails any OTA updates.
My question is two fold, but first I would like to explain that I rooted my device NOT for being able to install any custom ROM's. In fact I never had an interest in doing so as I actually like the stock OS's which right now I am still running 4.3. I rooted it specifically to be able to run network / packet sniffers on my own home network as a method to learn a little more about how things go over a network, seeing what I can learn and see if I can find any vulnerabilities. I also used it to try and clean bloat ware and other programs that with out root I can not uninstall or use, such as certain fast reboot apps. So, I really had no intention of using the Root to get me a custom ROM, as I wouldn't even know where to begin.
So my questions are this. Is there anyway that I can "un do" the root in order to let the device act as if it were never rooted? Or, is there anyway to force the OTA regardless of the device being rooted. My biggest fear is losing all the apps and files that I have on my device and I have never been able to get any kind of back up app to work, especially to restore anything from them.
I had read that one can use ODIN to flash the Kit Kat ROM, but while I have installed ODIN on my laptop, I am clueless on how to use it. I tried everything, but even with the USB drivers installed and working (I know this because plugged into the USB port, I am able to browse all the files on my device, yet ODIN continues to tell me that no device has been found.
Can someone please help me to understand what I need to do? Again, I don't care if I lose Root, I care that I don't lose all the stuff I spent months installing and getting my device where I want it. I really need someone to explain somethings to me as if I were a two year old, with out scalding me and making me feel like a complete idiot. I came here because everyone I have talked to told me that you guys would be the ones that could help me, and if you can't, then I am screwed and will have to just wipe the entire device and I just can't do that. I may wind up having to buy a new device and just transfer over what ever I can, however, in the mean time that is not an option.
To this end, I come begging for some serious help since I know you guys are the literal gods of Androids. If I must take some kind of custom ROM in order to get Kit Kat, I am somewhat willing, but I do not fully understand or know what ROM I would want to install as I have never in my life seen a custom ROM and what the benefits of having one are which is kind of why I really want to stick with the stock ROM and just keep getting the updates via OTA.
I have all the faith in the world you guys can help, I just don't know if anyone is willing to help since I know similar questions have been asked, but I do not know how to use what I learned for my particular device.
Thanks very much.
EU
Click to expand...
Click to collapse
does ur kies run? if so turn it off.
USB debugging off? turn it on.
are u in download mode of ur phone? if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen.
after that u can plug in ur phone.
Sent from somewhere under the sky, at the corner of this rounded earth.

antique_sonic said:
does ur kies run? if so turn it off.
USB debugging off? turn it on.
are u in download mode of ur phone? if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen.
after that u can plug in ur phone.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Hi antique_sonic, I would just like to clarify a couple things as well as answer your questions.
>does ur kies run? if so turn it off. <--- If you mean is it installed on my laptop and work? Yes it is, and yes it does, however, I almost never use it. Mainly because I was told that once you root a Samsung Device, Kies is no longer able to be used.
>USB debugging off? turn it on. <--- It is and has been turned on in an effort to try to sideload KitKat, but that was a hug fail. But I will leave it on for this discussion.
>are u in download mode of ur phone? <---- I have gotten here before but don't exactly know what to do once I am there since I don't know where to get a Kit Kat ROM, where to put it once I have it, or how to use anything in d/l mode.
> if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen. after that u can plug in ur phone. <--- Are these instructions for wiping the device back to the factory default? Will I lose everything currently installed and loaded on my Note 3? Or does this some how fix / allow for the OTA update to install completely because it no longer can tell the device is rooted?
Again, I must apologize because this is so greek to me.I am just trying to understand at this point what infact the instructions you gave me do, and what they are intended for. Is this just to get the USB drives to work properly? Or is this something that will help me undo root so that I would be able to install KitKat via the AT&T OTA. If now the latter, where I can I get a complete Kit Kat ROM and use ODIN to flash the ROM? This outcome would suck because I believe that this will cause me to lose everything on my device I worked so hard to get where I wanted. I have just over looked the fact that in rooting my device I there by killed my ability to keep my device updated with the latest OTA releases / patches.
Again, I appreciate you reply, but sadly I am in need of a bit more info if you could please.
Thank you so very much. I hope one day to be able to pay it forward, passing along the knowledge you have shared with me,
Regards,
EU

Dardwizzle said:
Hi antique_sonic, I would just like to clarify a couple things as well as answer your questions.
>does ur kies run? if so turn it off. <--- If you mean is it installed on my laptop and work? Yes it is, and yes it does, however, I almost never use it. Mainly because I was told that once you root a Samsung Device, Kies is no longer able to be used.
Click to expand...
Click to collapse
do check, is it running in background ? check your task manager. if so, kill the process. Kies should not run together with ODIN. Otherwise sometimes will give problem to your ODIN process.
I normally only install the USB driver only, as this is the only thing needed to connect your phone to comp (as MTP, or as ODIN connection).
Dardwizzle said:
>are u in download mode of ur phone? <---- I have gotten here before but don't exactly know what to do once I am there since I don't know where to get a Kit Kat ROM, where to put it once I have it, or how to use anything in d/l mode.
Click to expand...
Click to collapse
ok, in a very simple word. download mode is basically a state whereby your phone is ready to download system files and install the system files on your device.
This is the only state possible to get a connection to your ODIN PC to flash stock firmware, recovery (in .tar/.md5 format).
How to get the KK ROM ?
1) identify your device. which model it is. N9005? N900T? N900A? N900 blablabla?
2) goto samfirmware.com (register there if you don't have account. it is free). after that you can just find your firmware by typing on the search device textbox your device model (e.g N9005), and it will come out the list of your device firmware (normally they will show for the latest firmware list)
3) choose the firmware that you want to download (if your device N9005 international 32 gb, try to avoid the Hongkong / Taiwan firmware, as they have different PIT partition).
4) once you have the downloaded zip file from samfirmware, extract the zip, and then you will get the (.tar/.md5) file. Now you can use to flash this one over ODIN.
Dardwizzle said:
> if not, switch off n wait till vibrate to make it really off. then press vol down + home + power. then follow instructions to press vol up once u inside warning screen. after that u can plug in ur phone. <--- Are these instructions for wiping the device back to the factory default? Will I lose everything currently installed and loaded on my Note 3? Or does this some how fix / allow for the OTA update to install completely because it no longer can tell the device is rooted?
Click to expand...
Click to collapse
no. no. no.
This is how to go into download mode in your device
Not yet talking about factory reset.
But yes, you have to backup your internal storage, as sometimes upgrading will cost you to do factory reset, and your internal storage will be gone.
Dardwizzle said:
Again, I must apologize because this is so greek to me.I am just trying to understand at this point what infact the instructions you gave me do, and what they are intended for. Is this just to get the USB drives to work properly? Or is this something that will help me undo root so that I would be able to install KitKat via the AT&T OTA. If now the latter, where I can I get a complete Kit Kat ROM and use ODIN to flash the ROM? This outcome would suck because I believe that this will cause me to lose everything on my device I worked so hard to get where I wanted. I have just over looked the fact that in rooting my device I there by killed my ability to keep my device updated with the latest OTA releases / patches.
Click to expand...
Click to collapse
up to this point, I just remembered that you have N900A (AT&T) version. hahaha.
I go check the samfirmware, no release of KK yet at the samfirmware.
I'm sorry, I own N9005, and I never explore too much on the N900A, so I won't know what is the latest release, and where to get it other from samfirmware.
Dardwizzle said:
Again, I appreciate you reply, but sadly I am in need of a bit more info if you could please.
Thank you so very much. I hope one day to be able to pay it forward, passing along the knowledge you have shared with me,
Regards,
EU
Click to expand...
Click to collapse
no problem. you just get your latest firmware first, once you have it, you let me know, i can give you step by step in detail, on how to flash to your device.

antique_sonic said:
up to this point, I just remembered that you have N900A (AT&T) version. hahaha.
I go check the samfirmware, no release of KK yet at the samfirmware.
I'm sorry, I own N9005, and I never explore too much on the N900A, so I won't know what is the latest release, and where to get it other from samfirmware.
no problem. you just get your latest firmware first, once you have it, you let me know, i can give you step by step in detail, on how to flash to your device.
Click to expand...
Click to collapse
Sure sure, just laugh at me why don't ya!! LOL I will continue to try to find the appropriate firmware. I guess if I learned one valuable lesson in all this, it is just don't root your device if you don't plan on using custom ROM's. I had no idea that there would be no way to "unroot" your device once it's rooted. I was really hoping that you could just undo what ever is done to actually root the device, this way the OTA's will just start working again. Or that there would be a way to just force the OTA regardless of whether the device is rooted. I am not sure I truly understand why the OTA just won't install just because the device is rooted.I mean sure it adds SU to the device, and unlocks (I think) the boot partition or the boot loader, which ever, but regardless, why should the OTA package care and fail to install just because of that change?
Anyway, that's probably a discussion for another thread. I actually did find a Kit Kat zip that is like 150MB's it has a boot.img inside the zip, but it has nothing with an extension that ODIN can recognize. I would love to show you the zip, but it's too large to attach or email. The file name is 2400258.zip, but I forgot where I downloaded it from. It may be what I need to do the job, but with out someone seeing the zip I have no way of knowing if it's the files I need. I was not about to find any files with in it that are in txt readable format for me to say exactly what it is. It does have subfolders names Google and Android and the like but I am sure that is pretty useless with out seeing the full zip.
I will keep my eye on this thread and when I find something I can work with, or if you guys find anything I can work with I will come back and see where we can go next.
Thanks again bud!

Dardwizzle said:
Sure sure, just laugh at me why don't ya!! LOL I will continue to try to find the appropriate firmware. I guess if I learned one valuable lesson in all this, it is just don't root your device if you don't plan on using custom ROM's. I had no idea that there would be no way to "unroot" your device once it's rooted. I was really hoping that you could just undo what ever is done to actually root the device, this way the OTA's will just start working again. Or that there would be a way to just force the OTA regardless of whether the device is rooted. I am not sure I truly understand why the OTA just won't install just because the device is rooted.I mean sure it adds SU to the device, and unlocks (I think) the boot partition or the boot loader, which ever, but regardless, why should the OTA package care and fail to install just because of that change?
Anyway, that's probably a discussion for another thread. I actually did find a Kit Kat zip that is like 150MB's it has a boot.img inside the zip, but it has nothing with an extension that ODIN can recognize. I would love to show you the zip, but it's too large to attach or email. The file name is 2400258.zip, but I forgot where I downloaded it from. It may be what I need to do the job, but with out someone seeing the zip I have no way of knowing if it's the files I need. I was not about to find any files with in it that are in txt readable format for me to say exactly what it is. It does have subfolders names Google and Android and the like but I am sure that is pretty useless with out seeing the full zip.
I will keep my eye on this thread and when I find something I can work with, or if you guys find anything I can work with I will come back and see where we can go next.
Thanks again bud!
Click to expand...
Click to collapse
I don't like spoonfeeding too much actually.
but I find u r quite funny. no offence.
I have no idea this will work or not, but I found this as the 1st search result on Google.
http://www.droidviews.com/install-android-4-4-2-kitkat-ota-on-att-galaxy-note-3-sm-900a/
just have a look first nd don't do anything till u understand the article.
Sent from somewhere under the sky, at the corner of this rounded earth.

antique_sonic said:
I don't like spoonfeeding too much actually.
but I find u r quite funny. no offence.
I have no idea this will work or not, but I found this as the 1st search result on Google.
(I had to remove the link as the website thought I was adding it and gave me a no no warning that I can't post outside links cause I be a newbie!) BAH!!!
just have a look first nd don't do anything till u understand the article.
Sent from somewhere under the sky, at the corner of this rounded earth.
Click to expand...
Click to collapse
Hey antique_sonic, no offence taken my friend, I am a giant goof ball, but I am also someone who doesn't mind working out my own problems. It's just sometimes with things like this where I am clueless and need a little hand holding. It's nice to know that there are people like you around to help out the dopes like me My apologies for not getting back to you sooner, and I will be looking into the link you sent tonight. I haven't been feeling well lately, I have two herniated disks in my back and I have End Stage Liver disease and I am only 39, so I sometimes get a bit under the weather and am down for the count for a few days. So I do appreciate your patience with me and all the help and direction you are giving me. I try never to abuse the help as that is no way to learn, and learning is actually one of favorite hobbies! Weird huh.... So, I am off to go read the link you provided me and update the stock on my website and hope I make some more sales so I can get some money to buy a new phone when I brick this one! LMAO! Thanks again Sonic, I really appreciate everything!

Dardwizzle said:
Hey antique_sonic, no offence taken my friend, I am a giant goof ball, but I am also someone who doesn't mind working out my own problems. It's just sometimes with things like this where I am clueless and need a little hand holding.
Click to expand...
Click to collapse
No worries and yeah you should try to find first. by this way, you will learn faster, compare if someone do the spoonfeed.
Dardwizzle said:
It's nice to know that there are people like you around to help out the dopes like me My apologies for not getting back to you sooner, and I will be looking into the link you sent tonight.
Click to expand...
Click to collapse
My pleasure to help. And no worries for late reply, as I will do the same when I busy with my real life job.
Dardwizzle said:
I haven't been feeling well lately, I have two herniated disks in my back and I have End Stage Liver disease and I am only 39, so I sometimes get a bit under the weather and am down for the count for a few days. So I do appreciate your patience with me and all the help and direction you are giving me.
Click to expand...
Click to collapse
you are welcome mate. I'm sorry to read the news about your conditions. I can't say anything about this, but wish you all the best. Don't ever feel down in whichever state you are, just do the best in life, and we will never regret that 1 more day has passed.
Dardwizzle said:
I try never to abuse the help as that is no way to learn, and learning is actually one of favorite hobbies! Weird huh.... So, I am off to go read the link you provided me and update the stock on my website and hope I make some more sales so I can get some money to buy a new phone when I brick this one! LMAO! Thanks again Sonic, I really appreciate everything!
Click to expand...
Click to collapse
GOOD !!!
go and grab sales, rather than you brick the phone.
Once again, u r welcome mate.

[SUPERGUIDE][P51xxP31xx] Installation Troubleshoot Guide

The SUPER Custom Rom Guide and Troubleshoot​
There came a new version, your droid got old school and there is no support from Samsung cause they have forgotten about you.
Service centers you looked upon, and to mention exorbitant fees plus service tax came along. Thank You ma'am. will see you around.
Your droid is lagging and hanging and Lo, stops working suddenly. Now you just want to try something new, cause you can't sell them or buy new.
You search on google,
find on Youtube,
Read between surveys and blogs,
tried it yourself,
sometimes got lucky sometimes got thorny.
Now you come to the XDA community. there is too much to absorb and you're kind a new, welcome to all of you.
Click to expand...
Click to collapse
Dealing with most of the trouble making bugs and useful insight into cornering them like a rat
1. Tab is Stuck on Charging Screen. Tab is not turning On, battery completely depleted/Not charging, Nothing is Working
2. Stuck On Samsung Logo Screen.
3. Stuck in a Boot Loop.
4. Stuck On Firmware Upgrade Encountered an Issue.
5. Bricked.​Explained in Post number 2
Well that would sum up for me and most of the users will agree that these are the cases that really needs attention and no cussing about how your droid lags and hangs, doesn't makes it to the lists So, by the end of this guide, I would hope and expect at least so much from users to at least have a better knowledge and general idea of how things work here. so users don't just go on saying HELP HELP I am a NooB, Please read and understand first, dude. Thank you I will try to make it simple even if you're not so cool.
A few words about me if you're interested
OH!! you clicked!! wow. well what should I say here. ahem, hello gorgeous. I am Sam So, unlikely,
So guys, I wasn't lucky enough to get everything organised at one thread and spend a lot of time finding a perfect place for everything I would want to, so I thought this would be worth a share. It took me almost a month to write this stuff. yeah I was bored to the core, so put in some fun stuff
along with most of my learning experience and knowledge gained here on XDA in this Guide over the span of 3 years, I would just read and experiment it myself, kind of guy, I wouldn't have dared to put up this guide sooner, but now after successfully solving most of the cases even other people hard bricks and trivial issues that I get to see everyday and keeping myself safe from hard bricks with still not knocked out by one. all thanks to this community this is my gift that I would like to give in return, and I am just someone who likes to get to the edge of the world, exactly, on a round globe. Thank You
Android Broken into 5 parts, Worth a Look
Well not exactly broken but explained in 5 parts ( There are more but I choose not to, thank me for that)
1. Boot section(bootloaders/kernel)
This is droid's heart(accept it), responsible for the droid's birth and keeping it alive, sleeping, waking up, slowdown and speedup, overall working of the system, it has impact on every part of the droid. mess up things here, and droid won't start up at all and will stop beating and malfunction. then you will need a pacemaker and CPR(J-TAG) to revive it or it will keep the brain in coma. yes pretty much like our heart.
2. System section
This is a droid's mind, Its the place where all main work and processes are happening, with rooting and flashing you get a licence to open that mind and analyse, read logs, stats. that brain, heart and all your body is producing, you can see it all and make changes in it, put few things from outside. clean it, format it, wipe it, make amend(patches). So, imagine all that happening in your mind and the idea of cleaning your brains for once, wiping the mind, giving new and fresh experiences(newer and updated files) new interface(new UI), affecting the overall performance and changing to a whole new perspective with which you look at things.
So Clear your mind about this and remove your bad experiences and upgrade it with new stable ones. err not the custom beta and alpha ones, cause then you will give your headaches and put them in depression.
3. Data
This place is the memories part, and everything is stored up here. Everything. some would be overtly stored(on sdcard) and some deep inside you(under system/data/data). now overtly ones are not a concern here but deeper ones are hard to forget and lingers in your system, these won't go well if your heart and mind changed or aren't supposed to be the same, or in trouble will they? (i know I am good at explaining this)
4. Cache
Well, this one is the dreams part. damn I am right just admit it now. they come from your memories, keep it or forget about it, that's unto you. sometimes it can interfere with your old memories when you get new ones. so if unknown problem persist, with your heart and mind working nicely please clear your dreams and look into some of the memories. otherwise get the mind checked first.
5. Recovery
This is the soul part, whenever your heart or mind or data or dreams are feeling lost, you connect to it and revive them accordingly, or contact ODIN.
I hope you had some fun in the above part and a very clear and better understanding, So now you know where things are going wrong​
The Beginning
Ensure your Charging Adapter, USB ports and your USB cable, are in good shape and working in accordance, Never depend on USB hubs or any USB port that is a faulty or slow performer, use original cables, or buy new ones, the cable does create problems in some cases. if you're sure that these are fine, then let it in charging for few hours to even a day. depending upon how fast the droid recovers.
So what do you do, when you have to go the custom way or solve your problems?
i. Press Power and Volume Up(right button) or
ii. Press Power and Volume Down(left button) or
iii.Press Power and Hold touch screen combinations.
iv. Press nicely and hold it for good few seconds there, no hurry, really.
v. Long press the power button, release the power button and, when you see a logo appear during boot-up, hold down both the volume up and volume down buttons. Continue holding the two buttons until the droid boots up with a safe mode indicator at the bottom-left corner of its screen.
vi. Plug it in PC with the USB.
vii. Remove the Battery blow air on it and pat a little and put it back inside.
So what happens after doing what I said above?
i. (a). The tab goes into download mode
ii (b). The tab goes into recovery mode
iii(c). the tab switch off/on again.
iv (d). Now the Combinations worked properly, beware cause many a times on droids this could be a seriously tricky part.
v (e). The tab goes into safe mode.
I know you got tired there holding the buttons and No you didn't had to press it so hard
vi (f). Your droid and PC responds and connects.
yeah, I know Nothing much of a Help, but it will make sense when it doesn't
vii(g).
this is an age old trick of which there is no proof of success, but it has been working since ages.
As long as you can enter download mode or recovery or safe mode you can walk the path of going custom and troubleshoot along the way. Piece of cake. Most of the ways including how to root, upgrades, lag free and better performance starts here
[if you're ready to take the plunge, remember there is no backing out.]
Click to expand...
Click to collapse
Choose your steps wisely here now, if possible just read the main points and see if you have done all those first. that will save your data in some case and in some save you from getting all messed up.
CORA, (CODE OF RECOVERING ANDROID)
For NON-ROOT USERS
Safe mode
Stock recovery
Download Mode
FOR ROOTED USERS
Custom recovery,
Nandroid BACKUP,
Download mode
Safe mode
Click to expand...
Click to collapse
WITHOUT MODIFYING SYSTEM FOR HARDCORE STOCK USER
1. SAFE MODE
This mode generally helps when the problem is arising from 3rd party apps and is making your droid reboot again and again, lagging, hanging issues, so whatever is causing problem, if you can reach here, you can uninstall them clear their data and cache, and yes, free up some internal space too and backup your data from settings-backup as well. then factory reset if you want to.
2. STOCK RECOVERY WAY
You have never rooted your droid and you don't want to root and you don't want to move away from stock, well pressing the Power and Volume Down(left button) will take you there.
try to clear cache/data factory reset(will lose you data stored on internal droid) and yes it does solve few of the cases, even if it doesn't look so promising, it has solved, and will solve quiet a few issues. no chance of getting that data stored on internal., phone book, messages, chats.
3. THE DOWNLOAD MODE WAY
Flash a stock firmware Explained in post the download way.​
Code:
Now if you are already Rooted or want to Root to have a better option of saving your data, or reviving your droid
it's like performing a surgery on your body by yourself.
So be careful, you have been warned, Samsung voids the warranty,
and I don't give any Guarantees that these Instructions will work for all.
MODIFYING FOR PEOPLE WHO RISK IT
1. Getting Rooted
2. Custom recovery Way and (post number 4)
3. Download mode Way. (post number 5)
AND FOR THOSE WHO WILL BLAME ME
Seriously?
The most important and most essential part here is GETTING/HAVING a NANDROID BACKUP, the very FIRST THING that you MUST HAVE DID/DONE upon getting ROOTED. Make a Stable Clone guys.
You will need to get rooted and custom recovery to do that, not to forget enabling the USB Debugging Option from Settings->about device-> Build number-> press 7 times->back->developer->Enable USB Debugging and that's the beginning my friend.
Click to expand...
Click to collapse
Other threads with good post for the tab 2 series about rooting guides, containing firmware links, recoveries, Roms list, kernels, pretty much everything.
All about P51xx
All about P31xx
Latest Roms, Recoveries updated by Android-andi, the best developer around here
other droid users please look it up under your device thread tree, they will surely have a way, tailored and to the point.
Click to expand...
Click to collapse
Getting Rooted is only advised if you're going to stay on stock rom, debloating the system and making changes yourself.
if you're going to install a custom rom, which would be generally rooted, so you can skip to getting a custom recovery first.
CF auto Root are better option for any device to get rooted rather than other options
CFauto-root GT-P3100
CF auto root for GT-P51xx
or you can visit the chainfire homepage for your device which contains the root file for almost every device.
ROOT FROM DEVICE WITHOUT PC
in cases where you can't use ODIN for rooting or you want root your droid and there is still no method explained for Root on XDA then using framaroot, towel root, baidu, kingo or any other app(they can root some sets of droid) is advised, without ODIN or in case you couldn't connect your tab to the PC with the USB, only then these apps are good ways to get root. after that you can use flashify app or other apps for same purpose that has the feature to flash .img files, you can also use Mobile Odin app which can pretty much work when you can't use Odin from Pc.
then you can download a copy of the custom recovery image.(recovery.img) browse in the app and let it do the installation for you. this is useful for droids which doesn't have that much support like we and others have here
Click to expand...
Click to collapse

Common Issues faced
If you have read about my explanation of android's partitions in the OP(Original Post above), you would know where exactly to look for the problems. Moving on,
For other Geeks
Please remind me if I missed few things, you see I have put up this Guide mostly of the files I have in my system partition,I might have missed few that were stored in data or cache partition
1. Tab is Stuck on Charging Screen. Tab is not turning On, battery completely depleted/Not charging, Nothing is Working​
Possibilities
* if the tab doesn't feels warm even after charging for a whole day,
F1. Battery dead,
F2. Circuit/Motherboard blown,
F3. Bad Charger/charging point
F4. No electricity
if it's getting warm and still not turning on
F5. Hardware buttons not working
F6. Motherboard needs replacement.
F7. Flashed a bootloader/kernel(along with a Rom/firmware), or something not meant for your device, which is the hard brick in this category please refer to case number 5. (process on post 2)
F8. Some Custom Roms have bugs that won't Charge, stay stuck on the battery icon, unless you remove the plug and turn on. always read before flashing a Rom, if there are no info, better ask the developer before you go flashing or post your Question in related thread where they would get noticed.
2. Stuck On Samsung Logo Screen.​
This could be from various reasons generally not so serious ones mostly recoverable issues of which, some are
Flashed a incompatible Custom Rom zip or any other flashable zip containing files not meant for the exact device.
Flashed a kernel/ bootloader incompatible with the Rom, wrong kernel modules, messed up system lib files, (lucky enough to still not be in hard bricked section.)
Formatted system partition and there is no OS installed. (one of the silliest mistakes I have done)
Some other that I maybe forgetting just like I completely forgot about the above
Possible Solutions
Go to the stock recovery and wipe data/factory reset (this will make your precious data that you stored vanish, except data stored on SDcard) (explained further in post 3)
Get a working stable compatible kernel/Rom or flash stock firmware. (explained in post 2 and 3)
Download from a different source cause chances are the file got corrupted or infected while downloading or transferring. (post 3)
Find the file that is stopping the device from booting up, starting from the kernel, to the system files. duh?
Go to the custom recovery way.
Go to the download way
3. Stuck in a Boot Loop.​
Boot Loops are crazy and they will make you mad, they can hit you anytime for even little of tasks, Root or not root, either you are testing a new app, modifying/copying/editing/deleting/overwriting files in the system or data that don't even look so dangerous, just flashing some mod, GAPPS, or just updates rolled out by devs(nothing against them) this will surely hit you, no matter how focused and diligently you work. boot loops will make you do hula hoops.
Boot Loop is generally solved by
Hello? whatever you did that I mentioned above, just roll it back.
if you can't figure it out, well then
Remember the CORA order Quoted above in the first post? Read on
Safe Mode?
Go to recovery and clear cache then reboot.
Clear data/factory reset from stock recovery(data stored will be lost) (root users can skip this and directly go to 7)
No, Recovery?, You sure pressed the button nicely?
Flash a custom recovery image(recovery.tar) from Odin
Repeat from 1-3
Backup/Restore from Nandroid backup
Don't sit for the next exams without memorizing your lesson.
Cleared cache/dalvik cache?
Flash a Compatible Custom kernel
Find the stock replacement of the file/app you messed up from a firmware or a custom Rom, put it in a flashable zip and flash it (advance users)
Clear/data factory reset either from custom recovery. (*loses data)
Flash the Custom Rom, first dirty flash then clean flash.
Flash a Stock firmware from Odin. (loses data)
4. Stuck On Firmware Upgrade Encountered an Issue.​
Well this problems hits non-root users and root users too? why? because we wanted an update.
it was trying to upgrade and something got in between to make it stop
Battery/Power/Electricity - for non root users, the most common culprit would be the battery, seriously guys, please keep the battery in mind always. it's a very common mistake that cost many of users. For ODIN users, please see you have a uninterrupted supply of power to your device and you are using latest version along with Hi speed USB ports.
kies!!! I hate that thing and majority of others will support me here. I got rid of it the day I installed that thing on my PC.
interruption from the user side while the device was taking an upgrade. removed battery? fell down on the floor? no?
hardware issue, unlikely, rare I would say, in case the device did came out with a weak emmc card.
Bad/wrong firmware downloaded files.
In case you had a custom recovery and its still working, check the custom recovery way
I Know 1st didn't helped you,
Refer to the Download Mode way and get a custom recovery
Don't forget to clear cache, you do know that's where the device keeps the downloaded/image firmware file, and that's where it is installing/extracting from. the dream partition, no wonder you got errors. you got a nightmare now
try the download mode way
probably it's best that you either forget about the mobile, or give it to a service center for a J-TAG and get it repaired.
I knew you would look here, there is indeed a last ray of hope, explained at the last thing to do in download mode way
5. Bricked.​
There are 3 types of Bricks, Soft Hard and The Brick, That's it.
Soft brick
well you are safe and sound, you can even recover from custom recovery mode.
Hard brick
skynet has fallen, just like it infected the droid Arnold Schwarzenegger of the terminator version 3.0, the codes were injected into his heart making the brain dis balance and resulting in partial heart seizure and a coma, but he still had the cache and data part intact along with recovery, so it went there, restored a nandroid backup and went online again. BAM!! so easy. but why? I mean ours droid having reached version 6.0 can't recover from the same way? Where only hope here is a CPR or getting J-TAGGED? not to mention, which should be done by expert surgeons who would charge exorbitant . So, don't waste time with a jig or any other miracle to happen and please don't go on the droid with a shocking therapy. I am more of a practical guy and prefer professionalism.
The Brick
err, that's the solid one, put that on your heart, and forget about this droid and shell out money for a new one. : that's what the company wants to tell you here and that's the reason it doesn't want to put the nandroid on the stock recovery cause they want the blame on you and not them. shhh, keep it hidden, don't say I told you their secret
General Overview of the Next Options we have.
a. The Download Mode Way
Before going this way I would suggest you see the recovery mode way, if it's not working for you, then go ahead here.
You have four things that you can do (other's I never needed to venture upon)
1. Flash a Recovery -
In case you want to change or update a Recovery or fix/access a Recovery again, to root, complete backup from recovery(nandroid), install new custom Rom, install stock Rom, plenty of options here. Probably the safest option here cause you don't lose your data unless you do something wrong here as to format it. whether you root your tablet or not, install a custom Rom or stay on stock, everyone MUST have a custom recovery, I don't understand why Stock recovery can't have this option as well?
2. Flash a stock firmware package -
in case you are on stock recovery never rooted,
can't reach or can't flash anything using custom recovery,
bootloops(applied in all cases), want to revert back to stock factory state. tab system is behaving weirdly, virus and Trojans attacked or you just want to upgrade or change your droid firmware.
Note Using this method, will result in the loss of all your data stored on the device internal card.
3. Flashing a Bootloader
Generally these are included in every stock firmware pack. if you had a ICS(4.0.4) stock Rom, and the device got an Official JB(4.2.2) update. you must update to that firmware first before flashing any later custom Roms[from kk to M(6.0)], the version which never got released officially. flashing this part separately is very risky and done with utmost care, remember it's your droid heart. don't fool around with it.
3. Flash firmware with pit file -
Warning : this is some high level flashing, it will re partition your device along with the stock firmware. in cases where NOTHING ELSE on the whole Internet worked for you, and you have tried almost everything, only then choose this path with clear mind. make mistake in this, and your tab will virtually turn into a paperweight. if you're not sure you could handle it, please send it for the service centers. this is going to flash every part of the droid's body
4. Flash the 4 files with pit
This is the secret way, where miracles can happen even when there was no hope of recovering yourself.
b. The Recovery Mode Way
Stock recovery - Here You can clear cache, there is nothing much happening in clearing cache, just clearing some temporary files and making you feel like you have got some space cleared out. it's just files that you most probably already used.
data/factory reset and reboot. Easy and simple solution . that does solve some of the problems you face without modifying your device much. so those of you who are afraid to flashing things and ending up on some bigger mistake, you can give this a try, but keep in mind, you will lose all your data stored in the device.
there is apply update from recovery, but that seldom has use in an average android user's life nothing much of a recovery.
Go to download mode way of flashing a custom recovery
or
If you have rooted your tab somehow using framaroot, towel root, baidu or any other app, without ODIN in case you can't connect your tab to the PC with the USB, then you can use flashify app or Kernel Adiutor(the latest one) or any other apps that has the feature to flash img from inside the device OS. you can download a copy of the custom recovery image.(recovery.img) browse in the app and let it do the installation for you.
Custom recovery - Here you have many things that you can do depending upon which recovery and which version you choose. CWM is past, philz is ok, TWRP is awesome. most of the options are common in these 3, but some are really better and fast than the previous ones. we will discuss only one, my favorite TWRP(Respect for the legend CWM though), the process is common on all but twrp is more feature rich.
Click to expand...
Click to collapse
Important files you must have NANDROID BACKUP, STOCK FIRMWARE, PIT FILE, and 4 FILES FIRMWARE PACKAGE, GET them even before you need to search for them
Click to expand...
Click to collapse

Setting Up Everything
Before proceeding Always keep device battery fully charged and NEVER go flashing on low battery. Very Risky. Don't forget.
Always check the files that you are going to flash on your device. generally files will have device model mentioned in their filename.
Be Sure that you don't lose electricity or laptop on low battery while working. the device takes time to update.
Click to expand...
Click to collapse
Things you need to Set up a 'Flashing Environment'
No, I am not going to talk about a flashy party setup ​
i. PC running Windows 7 and 8 (with 10 I haven't flashed anything yet, but it works.)
ii. A working data cable(some cables are bad and will not detect your device if you see unknown device better get a new one)
iii. Samsung USB Drivers it's much better than having samsung kies on your pc. I would personally suggest from my experience along with many people who have suffered from samsung kies, it's not worth the hassle. ODIN and KIES don't work alongside, so you will have to close.
iv. ODIN 3.10 (download plus instructions as well I used 1.85, 3.07, 3.09 All worked, and so will 3.10. if not, try different ones from Odin 1-85 to 3.07. these links have more step by step and detailed covering what I have left.
v. 7Zip better download this cause it can unpack most of the files.
Press and hold Power and Volume Up(right) button on your device for few good minutes until you see a download mode screen
Connect your USB cable to PC and press Up to Continue. sometimes there could be problem with the USB ports, you should check in all the ports available. avoid USB hubs or the front panel USB in case of PC, don't let a faulty port ruin this for you.
Problem/Failed with Odin? Refer to this thread Good Points here as well.
Click to expand...
Click to collapse
DOWNLOADING AND READING FILES
Believe it, this a very big problem that people tend to overlook
The file you need will look something like these
"P5100XXDMD1_P5100OJVDME1_P5100XXDLL2_EUR.tar.7z"
where
P5100 - Generally the first 5 letters/numbers means a device model number.
XXDMD1 this is PDA which will be 5 letters(much older devices)-6 letters denoting firmware build version.
OJVDME1 is CSC version these just contains regional wise APN, nothing much.
XXDLL2 is Modem version.
EUR is Country Code.
.7z means you need 7zip to extract this file.
Now see these 2 examples here
"S7562XXALJ4_S7562OXXALJ3_S7562XXLJ3_HUN.tar" and "S7562CZNUAMI2_S7562CCHUAMI2_CHU zip"
Sure it's S7562 device but wait the other one is S7562C !!! totally different device firmware. make mistake here and you are sure going to lose.
I Hope you can make out the difference now for every device now.
Now the real file that you need will always be inside a zip/tar/7z the correct format is "P5100XXDMD1_P5100OJVDME1_P5100XXDLL2.tar.md5 "
Remember to extract it and get the md5 file.
Click to expand...
Click to collapse
These are the known best sources
Enter and Download device model on sammobile
P5100 sammobile
P5110 sammobile
P5113 sammobile
P3100 sammobile
P3113 sammobile
*Bump Download firmwares available smart-gsm.net
Download firmwares available easy-firmware.com​The Only reason I am putting this here is while I was searching for genuine websites, I had a very hard time finding through sites that looks nothing else than scams and fakes and rarely had files that I needed and password protected. this websites has ads, but looks organized and for tab series, it had at-least all the firmwares downloading.
PHP:
Yes so, it will take time and require a good internet speed, there are other sites, but I don't recommend them unless they are from good source or sometimes the only option. Options are also available from GSMhosting site as well, its another good community but I feel XDA is much better. still if you have no options. you have to get it somehow. just stay away from the survey sites and bogus ones. specially the blogspot ones.

Recovery Mode Way
Recovering from a custom recovery
Important Part​Creating Nandroid Backup - This is the most important thing that you will ever need, and will always regret not having it when you chose this path, should be the first priority.
Getting Inside
Switch off the device
Let it completely shutdown
Hold Power and Volume Down(left button)
This is how it looks saw that backup button? yes that is where you tap first (other recoveries will have different looks, but same "backup" and
This is where you do it . by tapping again or navigating through the volume up and down button in case of older recoveries this would not at all be same, this is the most latest feature rich recovery.
Those Running CWM older builds, won't find the options to select boot, system cache and data and instead there will be just "backup" and backup to external.
CWM by default will Backup boot, system, data, cache partitions. Philz will also do it. But TWRP has better features. although they do the same. You just select system, boot, data and cache. that would be all to recover using nandroid backup.
Now here it depends on what you are trying to do and what would you like to recover from, also depends on what you are comfortable with doing and how much space you can spare. if you have a lot, I would say skip this step and backup all for once.
Click to expand...
Click to collapse
Not Noob Friendly
if you have that same custom Rom zip that you would like to restore the backup of, then there is no need to copy/backup /system partition again, it will save you some space. so you can skip it in that case for TWRP.
if you're only going to modify device kernel - backup boot. or just data if you already have the custom Rom with kernel.
other than that twrp offers what CWM lacked, skip md5 generation during backup well this is a good option and saves some time while backup, on restoring you can also enable or disable it. the purpose of this is simple, md5 is like a security/seal on your backup file, so you don't mess up anything while restoring it on your device. after all you never know when a virus might attack or you might put the wrong files on it. if you are sure about your talents, you can skip it or else it's better to let it generate and verify while restore. CWM has this setup as default.
Now you have one? GREAT! GENIUS!! Now whenever you encounter a problem make sure you can use it like a BOSS.
Restore Nandroid Backup​
Enter recovery mode by Pressing Power and Volume Down(left button),
you reach the main screen,
you see a "restore" option and tap it,
you will see folders name starting with the date you made a nandroid backup,
you recognize which one you want by the date and information listed there, and select it. CWM only offered dates, but twrp even offers more detailed info including OS version and Rom name. one more reason I suggest you to use twrp.
In case you want only data to be restored, then you choose advanced restore and check the data and restore. but before doing this part make sure you are not restoring conflicting data or system or kernel with incompatible versions.
you can't restore a data backup from a Jellybean Rom and put it on a custom Rom based on Lollipop, neither a kernel from Lollipop to jellybean.
Data should only be recovered on the same Rom you took the backup from.
In case the custom Rom developer rolls an update of the same fixing issues,(not some major changes) then you can in some cases think of getting this worked out smoothly. This is called a "dirty flash". which is the reason why sometimes users experience problems running certain Roms, even when they are good and stable Roms. So before complaining to devs make sure you follow the clean install method.
Note: System and data most of the times will cause problems. Kernels are not meant at all to play with. they are the biggest source of bricks.
Click to expand...
Click to collapse
​
Wiping Part - Steer Clear the problems away
this is where wipe takes place[PIC]
here are the wipes options on a custom recovery
Factory reset - Wipes cache, dalvik, data/ excluding your media part on the internal drive.(your pics, videos are safe)
this will generally clear you problems if they are not some big issues. but you will lose the apps and contacts messages stored.
Advanced wipe - Format system
you can try to do this first if you don't want to lose your data while troubleshooting.
format system if you're facing issues with the files on system partition, but remember to install the same Rom you had earlier. if you had stock, you will need a stock Rom zip not to forget keeping the file ready beforehand on the external SD card.
Beware while navigating in advance wipe menu, never wipe in a hurry, never drink and wipe, never take eyes off here, cause you might end up touching external SD card, USB-OTG, internal storage and lose your precious data
Format data - this wipes the data partition
problems arising from the data partition side could be solved here, but you lose your precious data on the internal and get rid of the bad, virus, trojans, trouble making apps.​
How to perform A CLEAN INSTALL when you are going to update to a new Rom?
Factory Reset and Format System, Format CACHE
or
Format /System, Format /Data, Format /Cache, WIPE Dalvik Cache, Factory Reset.
This will Surely Solve Some Great & Average Problems of Day to Day Flashing.[/B]
Click to expand...
Click to collapse
What's a Dirty Flash then?
Format System, without Deleting Data partition. before doing this, please do a nandroid backup in case you mess things up. if not, format system again and flash the Rom that was initially running with that data.
Click to expand...
Click to collapse
Now Comes the Installing part
Installing Menu​
You download a copy of a custom Rom or stock Rom, after following the developer's thread, reading through it's bugs and reviews. you don't want a unstable or alpha Roms.
There would be installing process explained on that thread follow it and always make sure that inside the zip file it contains a meta-inf and system folder with boot.img) always look inside before going to flash, don't trust me, don't trust anyone. although
if you tried to flash a firmware zip file containing a .img file, without Meta-Inf folder, it won't flash. cause the custom recovery needs instructions from updater-script. Now, I know this was mostly going on like this before, but now with latest custom recoveries, (twrp) you can even flash .img files without needing a zip.
You perform a Clean Install wipe stated in the wipe section above
Reboot to Recovery(Don't select reboot to system, there is no system after clean wipe)
You browse through the files list and external storage,
Find that zip file and
Swipe or press or touch to flash it.
You wait for it to complete the process then
You can wipe/cache/dalvik and reboot or you just reboot. depends on what you choose "clean install" or "dirty install".
You want to report any errors while flashing? you are free to do so on the Rom thread, don't expect me to solve those cases.
If all went well, reboot to system and your tab should be up running again. if not refer to the Download mode Way.

The Download Mode Way
The Download Mode Way
1. FLASH A CUSTOM RECOVERY
Find the recoveries in their respective threads. For P51xx and P31xx Recovery thread others can look in their respective device sections, XDA has development thread of most of the Samsung devices and people do post there.
it should look like this on your address bar
"http forum.xda-developers.com / galaxy-tab-2 / general"
xda website /__ (devicename)/ (sub-forum)
(development) OR (/general) section
You can always google it too.
remember you will need a recovery.md5 that will be inside a zip file extract from it.
Always check whats in the archive then go the recovery mode way, it should be .md5
Sorry I have not put up detailed step by step process here because my guide is covering a lot of things already and this is something each device specific, refer to this For General step by step instructions with pictures, this has very detailed process.
Click to expand...
Click to collapse
​
2 FLASH A STOCK FIRMWARE
These package contains files needed to update or revert to the same position where it was shipped to your country along with your android device. you can find all Samsung device firmwares released from all parts of the world, and yes, you can flash firmwares of other country/regions from the sammobile site just stay away from the carrier specific firmwares(unless you are on one) that should be used for the same specific carriers device only they are married to the carrier company and probably won't let you have your own ways with others.
You should also remember not to downgrade a stock firmware once you have upgraded, that will surely create problems​
Run Odin as administrator
Browse PDA/AP and find the firmware .md5 file
This is how you should see on your ODIN screen. always be very very careful to uncheck the Re-partition. it's unchecked by default.
Click to expand...
Click to collapse
Code:
The yellow column/(Blue for other versions) means
your device is detected by the PC.
If it's not lit, you have messed up USB drivers
still not uninstalled kies Completely or
not connected the device properly.
try changing to different USB Ports.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Press Start
Wait for the process to complete and let the device reboot from download mode
Remove cable when you see PASS written with green above the Yellow/Blue com port.
PHP:
Most Problems are solved here when you see success/PASS.
Except one The emmc bug. Replace the internal emmc, or J-TAG or
mysteriously something else done by professionals.
[*]if it shows failed, see if you can go to recovery mode and clear data, check Mount/Unmount System, data
Click to expand...
Click to collapse
if it still says failed, the downloaded file is corrupted, wrong Odin version(try with different Odin versions) you have flashed wrong device files which has messed up the partition table of your device. refer to other ways.
Threads with good post for the tab 2 series these contains firmware links, guides, recoveries, Roms list, kernels pretty much everything.
All about P51xx
All about P31xx
Click to expand...
Click to collapse
3. FLASH A BOOTLOADER
First ask yourself why you would want to do this?
Be extra careful with this part, if you have already flashed a updated firmware, you don't need this part.
Those who are using old stock firmware, please flash a stock last updated firmware. you won't need to do this.
Those who did not follow the above two, so it's now unto you, this a risky thing, you have been advised you are going further yourself
Those who are experiencing problems that are not solved even after most of my other instructions here, then it's onto you to decide you want to try this too or not. this could solve problems when device is in serious condition, after all it's the heart partition and remember no downgrades in this once you upgrade. thats it. this could seriously create problems, including bringing back the emmc issue as well.
Refer to this DETAILS AND INSTRUCTIONS to FLASH A BOOTLOADER for SAMSUNG TAB 2 SERIES follow safely by @Joery360 other users please be careful with these files and don't go on flashing others files? okay. Great!
Click to expand...
Click to collapse
4. FLASH FIRMWARE WITH PIT FILE
Wait!! You are sure that you want to try this part? this is the point of no return. Whatever happens to your device by following this guide, good or bad, it's your own responsibility. You can't blame me for it. so be sensible, if you're not sure please let this be done by someone who has the experience of dealing with this kind of stuff.
Now pit files are some serious files, they contain information about your device partition and they help flash erase and rewrite files on their correct partition, so better not take a wrong file, sometimes you have the same device but different internal space, so don't end up choosing a pit file for a 8 GB variant on your 16 GB variant of device, in that case your device will end up using 8gb only, or worse if it's other device, it might never boot up again.
Always remember don't flash pit files ever without a firmware file in place.
Download Pit files for Samsung tab 2 p51xx p31xx series
Click to expand...
Click to collapse
Run Odin as administrator
Browse PDA and find the firmware .md5 file
Browse Pit and select the pit file (reminder : file confirmed?)
Make Sure Re-partition is checked cause we are using Pit File to re partition again
Never flash a Pit file without a firmware placed in PDA/AP
Click to expand...
Click to collapse
Press Start
Wait for the process to complete and let the device reboot from download mode
Remove cable when you see PASS written with green above the Yellow/Blue com port.
Click to expand...
Click to collapse
if it shows failed while flashing, you did used correct files, right? after this if there is still a download mode running on your device. try the special case files.
this has happened with me on a unknown MTK device, the pit file was slightly different from the original one on device, so it failed, but that was at the start before it could flash. I did somehow managed to flash that different pit file, just lost some disk space. cause I used a lower variant pit but it got the device running up again.
The device takes a long time to boot while it's updating firmware, so you are required to have sufficiently charged battery, Take no chances here.
if even after a successful flash with Odin, you face problems, then that's a emmc bug case. motherboard replacement or emmc replacement, or tab replacement. nothing else.
5. FLASH PIT WITH 4 FILES FIRMWARE
Find the repair firmware files at this Website
it has the 4 files for most of the devices including the Tab 2 series
Instructions for using these 4 files, however please note that the only difference would be the ODIN versions, cause device needs specific ODIN version, some can flash all.
this is the only way, that I have seen working for numerous devices and it is most successful one among all options to recover an almost bricked device, on which you have tried everything.
For other devices
Find them here
​
Click to expand...
Click to collapse

you'll find these buttons on every post.
it's better to notify a user when you're asking that user a question or use @username of the user for mentioning in your post, that will give in a notification for you.

I think there could be more, i know it's already lengthy but who knows?

ZTE Axon 7 USA Bootloader/TWRP/Update Help

So here's my story,
I bought this Zte phone off someone on craigslist a couple of weeks ago, and I've loved it every since. In fact, I have yet to turn it off, I've kept it on the entire time. Today the new update 29 came out for the US, and I tried downloading. To my dismay when the phone restarted I was greeted with a bootloader screen, and then a TWRP screen. I freaked out and panicked and emailed the guy I bought the phone from since I heard that unlocking bootloader on your phone voids the warranty. He told me he had done it in such a way OTA framework that it didn't void the warranty and also I can always relock the phone but be careful because I might brick it. I'm not a very tech savvy person and have no idea what to do to relock the phone so I can download this new update. Could someone please help me out and walk it out with me step by step so I know what to do. Thanks so much guys!

Look in the section rooms, recoveries,etc... look for one the says roms update stock DrakenFX

Since you are not tech savvy, you could just keep it unlocked and use those twrp flashable files to update B29.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
credit: @DrakenFX
However If you will wish to restore to locked state without twrp, I will be happy to guide you but you'll have many more steps to do.

Nik2424 said:
Since you are not tech savvy, you could just keep it unlocked and use those twrp flashable files to update B29.
http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
credit: @DrakenFX
However If you will wish to restore to locked state without twrp, I will be happy to guide you but you'll have many more steps to do.
Click to expand...
Click to collapse
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?

ctran1996 said:
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/axon-7/how-to/b20-factory-image-posted-t3492552 click the link in this post. It will take you to the ZTE site with the official B20 firnware. You flash this in stock recovery and you will have a fully locked Axon 7.

tabletalker7 said:
http://forum.xda-developers.com/axon-7/how-to/b20-factory-image-posted-t3492552 click the link in this post. It will take you to the ZTE site with the official B20 firnware. You flash this in stock recovery and you will have a fully locked Axon 7.
Click to expand...
Click to collapse
How do I flash to stock recovery with teamwin keeps popping up and restarting and not allowing me to flash it?

ctran1996 said:
I would much rather just restore to locked state without twrp so I don't have to worry about this situation again. I don't need bootloader or twrp and just wanna remove both. Would you please guide me through this?
Click to expand...
Click to collapse
If you're not tech savvy, you probably don't want to do this. It's not simple and for whatever reason, some people (who would consider themselves more tech savvy) have had some issues.
Your best bet is to copy all of your data from internal memory (just in case), flash a new copy of TWRP (recovery only, you don't need to do boot) using tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), then follow the steps in DrakenFX's thread to get B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I'm happy to write you a guide for getting back to bone stock, but I'm not going to do it until next week when I have time at work and as I said earlier, some folks have had issues. For what it's worth, you likely won't hard brick the phone. So far, we've only seen soft bricks AFAIK.

rczrider said:
if you're not tech savvy, you probably don't want to do this. It's not simple and for whatever reason, some people (who would consider themselves more tech savvy) have had some issues.
Your best bet is to copy all of your data from internal memory (just in case), flash a new copy of TWRP (recovery only, you don't need to do boot) using tenfar's tool (http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), then follow the steps in DrakenFX's thread to get B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
I'm happy to write you a guide for getting back to bone stock, but I'm not going to do it until next week when I have time at work and as I said earlier, some folks have had issues. For what it's worth, you likely won't hard brick the phone. So far, we've only seen soft bricks AFAIK.
Click to expand...
Click to collapse
Are they really hard to follow?? I mean my guides?
If I could I love to redo Tenfar tool guide ,but don't think he will allow me recreate that thread in a more clean way (guide wise)

ctran1996 said:
How do I flash to stock recovery with teamwin keeps popping up and restarting and not allowing me to flash it?
Click to expand...
Click to collapse
http://www.mediafire.com/file/1jw9b24glt5fd7t/recovery.img put this on your SD card
Boot to TWRP
Push Install (top left)
Push Install Image (bottom right)
find the recovery.img and push it - TWRP will install it for you.
Then reboot into recovery.
You will now be in stock recovery and can use it to install update from SD card and install the B20 firmware from ZTE
BE WARNED - THIS WILL FACTORY RESET YOUR PHONE WHEN YOU ARE DONE!!!!!

DrakenFX said:
Are they really hard to follow?? I mean my guides?
If I could I love to redo Tenfar tool guide ,but don't think he will allow me recreate that thread in a more clean way (guide wise)
Click to expand...
Click to collapse
Hah, no, your guides are not hard to follow. They're great
I think the bigger problem is that there are a lot of threads to wade through and there are various posts within in each thread that address specific issues users have run into. If someone who claims not to be "tech savvy" doesn't understand something in your thread (not because it's unclear but because they have zero experience with this and need some hand-holding) and then happens to read something else in the thread and tries that, it can get messy.

rczrider said:
Hah, no, your guides are not hard to follow. They're great
I think the bigger problem is that there are a lot of threads to wade through and there are various posts within in each thread that address specific issues users have run into. If someone who claims not to be "tech savvy" doesn't understand something in your thread (not because it's unclear but because they have zero experience with this and need some hand-holding) and then happens to read something else in the thread and tries that, it can get messy.
Click to expand...
Click to collapse
That is my problem entirely! I AM tech savvy as I have worked as a Microsoft/VMware Systems engineer for over 20 years and when I try to make heads or tails of doing some of the things necessary to flash a ROM, or root, or unlock the bootloader.... after my eyes glaze over I just stick with Nova Prime and hope the original manufacturers get everything worked out. What's really needed is a well written manual detailing step-by-step basics on what all these various things do as well as how to do them. Then more specific guides on a per phone basis. I know, it's asking too much! LOL :silly:

ctran1996 said:
So here's my story,
I bought this Zte phone off someone on craigslist a couple of weeks ago, and I've loved it every since. In fact, I have yet to turn it off, I've kept it on the entire time. Today the new update 29 came out for the US, and I tried downloading. To my dismay when the phone restarted I was greeted with a bootloader screen, and then a TWRP screen. I freaked out and panicked and emailed the guy I bought the phone from since I heard that unlocking bootloader on your phone voids the warranty. He told me he had done it in such a way OTA framework that it didn't void the warranty and also I can always relock the phone but be careful because I might brick it. I'm not a very tech savvy person and have no idea what to do to relock the phone so I can download this new update. Could someone please help me out and walk it out with me step by step so I know what to do. Thanks so much guys!
Click to expand...
Click to collapse
OK. Step by Step to get it back to B20
1) Move anything you want to save off your internal storage to your sd card or computer.
2) Download B20 image button.
3) Save file to SD card
4) Boot into Recovery by shutting it down and then push Volume Up Button+Power Button
5) When screen comes up boot into Recovery
6) in TWRP click Install, choose Select Storage, Choose Micro SDCard, Locate your update.zip file and click it
7) Swipe to confirm flash
WARNING: This will clean out your phone and turn it to B20. @DrakenFX can tell you how to not wipe the internal storage if you want to edit the update.zip file.
Hope this helps.

Thank you this is exactly what I was looking for. However, when I tried this the other day, it reset my phone as planned, but TWRP and bootloader were still on there. Any way of getting them off?
swehes said:
OK. Step by Step to get it back to B20
1) Move anything you want to save off your internal storage to your sd card or computer.
2) Download B20 image button.
3) Save file to SD card
4) Boot into Recovery by shutting it down and then push Volume Up Button+Power Button
5) When screen comes up boot into Recovery
6) in TWRP click Install, choose Select Storage, Choose Micro SDCard, Locate your update.zip file and click it
7) Swipe to confirm flash
WARNING: This will clean out your phone and turn it to B20. @DrakenFX can tell you how to not wipe the internal storage if you want to edit the update.zip file.
Hope this helps.
Click to expand...
Click to collapse