[Q] Please help SBF' to stock, wipe - update 2 latest & greatest - Motorola Droid 3

Hello all,
When the Droid 3 first came out psouza4 posted how to root and remove bloatware. Since then I've uninstalled the launcher once (big mistake by not paying attention) got it fixed but since then I've done nothing more.
The phone is still rooted. I don't know if the bloatware is still removed because I used the HDMI once and don't know if I ran the script with just the HDMI enabled (whatever HDMI is tied to that is) or the default script.
Reading thru the forums there is a wealth of information.
I'm not sure what direction to go. I have ADB installed still and it's updated, don't know if I'll need it.
The main problem is random reboots with the phone when going to take pictures or video. Sometimes I'll lock up for five minutes and finally cycle power. I started reading how to troubleshoot for this type of behavior when I realized I should just start over.
My goals are (and not in any logical order) to wipe the phone, wipe the internal memory, wipe the external memory, get the phone updated to the latest OTA from Verizon and Android operating system (if there is a newer ver avail for my model phone)
Phone stats:
Droid 3
5.5.959XT862 Verizon
ANDROID VER
2.3.4
BASEBAND
N_03.18.16P
KERNEL
2.6.35.7-g42f0276
[email protected] #1
BUILD
5.5.1_84_D3G-20_TA-9
ERI
5
PRL
52826
Click to expand...
Click to collapse
Thanks in advance for any input/help. If there is series of posts you recommend me to follow I can read them and do it that way.
Have a super Monday.
-Sc

Related

[Q] In what Heroic direction do I go?

Hi guys... I have a few questions for you about my Hero. Forgive me for not yet having the same level of knowledge that many of you guys have. I am certain that I can contribute in some way, as well. My phone details:
Firmware version: 1.5
Baseband version: 1.04.01.09.21
Kernel version: 2.6.27-533ce29d
Build number: 1.56.651.2 CL5027
Software version: 1.56.651.2
Hardware version: 0002
1. I've read several stories where a number of phones were returned because they couldn't be updated when the new update was released. Is this an absolute fact, that it can't be updated, or is there an error in code somewhere that made it reject the update and there is a known workaround? The answer to this question obviously dictates my forward motion.
I have the typical problem apps, and am getting no joy from youtube. Presently, I'm surfing with good speeds, but market is non-existent.
I like having Sprint tv, when I'm having to sit and wait somewhere.
I have time today and tomorrow to get things ironed out, but will be extrmemly busy after that, like 20 hours a day studying. I'm hoping to get some direction that will give me complete functionality, but will require the least setup. I am quite computer savy, and repaired this phone, to this point, in a day or 2, without asking a single question of anyone. I traced down problems, and solved issues. Seen APN, and TCP errors (don't believe it completely, since I can authenticate on the web). Know that some issues are url problems, etc.
The following questions are based upon the answer to question number 1.
2. Can this phone be updated?
2a. If yes, What do you recommend... 2.1? What rom do you suggest, for full stock-like functionality? Will I lose Sprint tv? Pointers/direction? (pancake??, superhero??)
2b. If no, What rom do you suggest, for full stock-like functionality? Will I lose Sprint tv? Pointers/direction?
Before repairing the phone, I actually tried to update it from my computer, but it was rejected. I turned off my security software and tried again. I noticed that while using XP sp2, a windows program that was incorporated starting with sp2, DEP (data execution prevention) didn't like the actions that the update was taking, and arrested it very shortly after starting (yet the window cycled forever). I assume that many people wouldn't be this observative, and recognize that this was happening. It was halting an HTC file that utilized storage memory (similar to buffer overrun exploits - the reason DEP halted it), for temporary storage of the files to be used for the update. That file was as follows:
C:\Program Files\HTC\HTC Sync\Mobile Phone Monitor\FsyncServer.exe
And the way to prevent it from continuing to do so is:
1. Click Start
2. Select Control Panel
3. Select System
4. Click the Advanced tab
5. In the Performance region select Settings
6. Click the Data Execute tab in the dialog box that opens
7. Select Turn on DEP for all programs and services except for those I select
8. Click Add.
9. The open dialog box will open. Browse and select your application.
10. Click Open
11. Click Apply
12. Click Ok
I guess what I'm sort of suggesting, is that this might be why anyone ever had problems updating, with the exception that OTA also said there wasn't an update.
So, back to the original question. Is it true that some Heros can't be updated? I don't want to force something, and brick, if you know what I mean. I completed the setting that will allow it to go forward (listed above), but haven't tried to update since. I felt that I really needed to ask you guys first, before I made a mistake that I'd regret. Should I try again? Before I started working on the phone I did try OTA and it said there wasn't an update. Now I don't have that option anymore. After repairing the phone, I've lost updates. Am I stuck with 1.5? With my run of the mill phone desires (except that it be fully functional), should I keep 1.5?
I did see gmail 2.3 apk, but is that compatible with 1.5? This looks like is would solve the market issue, if I could use it.
I did read about gscript and addressing mms (although I'm sure that's very old news to you guys), but if in fact I can't update this phone, it might be one of my only alternatives. If that is my only choice, are their also additional scripts to address everything I need to fix (all the normal issues)?
Additionally, it seems that many apps register with the phone/user. So, when you are using a used phone, many apps are still registered as functional. Does flashing a new rom affect the OS and apps? Will I loose the already registered/functioning apps? With a complete upgrade, will I gain functionality of some key features, but lose all other previously enabled apps? In other words, will I gain update, and market, and lose sprint tv?
I have read a lot. With things the way they should be, I've not been able to quite determine what I need to do. With all this being said, How do I go forward and achieve a fully functioning phone? What is the best choice of path's to take for me?
Rooting? I have seen the one-click, and think I'd be correct in that I need something containing Sense UI. Forgive me for asking a stupid question... but the rom is only the menu accessibility, correct? Is there something straight out of the box setup, or do all roms contain configuration notes?
I'm satisfied with stock features, if they work, and adding other useful things like tethering. Since I'll be so busy, I'll have little time to do much else. But don't get me wrong. I have 10 PC's in my house, with only 2 people living here. I'd love to customize the crap out of it. It's just not going to happen any time soon, due to my brutal study schedule. So for now, I just want it to work like it should, on a B mvno.
Do I go north, south, east, or west????
Could someone chime in that can give me direction, based on everything I've stated. Your response is so graciously appreciated.
Cheers!
Umm well I'm not sure why you're having problems with any update, someone who's far more experienced can maybe tell you but as far as roms I think it depends on whether you like sense or wanna go froyo. Cyanogen mod 6.1 stable (2.2) is nice & highly customizable however there's also AOSP roms (2.2) that some people feel is quicker than cyanogen however they aren't as customizable as cyanogen, in addition there are tons of GREAT themes for both. Also we've had a ton of work on an odex AOSP gingerbread rom (2.3) not yet stable but works good for most & on that note a great themer also put together a themed AOSP gingerbread rom (2.3) that looks good & about stability I'm not so sure on but I would recommend those roms. Although with these roms YES you will lose sprint apps like TV & vvm etc. However people have posted these apks in the theme thread section to work on roms like cyanogen & AOSP. If you do like sense roms there's a couple that are still live in the development section like nfinite & nfx I believe. Hope some of that info helps
Thanks so much for your response. So Cyanogen mod 6.1 stable (2.2) is highly customizable... That's good.
So let me get this straight. I need to:
root (is one-click OS version specific? Can it be used on 1.5?)
backup
save to pc
update to 2.1 (if I can, and it needs to be the rootable version found here)
re-root
and flash Cyanogen
and setup
Is this correct?
inkblots said:
Thanks so much for your response. So Cyanogen mod 6.1 stable (2.2) is highly customizable... That's good.
So let me get this straight. I need to:
root (is one-click OS version specific? Can it be used on 1.5?)
backup
save to pc
update to 2.1 (if I can, and it needs to be the rootable version found here)
re-root
and flash Cyanogen
and setup
Is this correct?
Click to expand...
Click to collapse
Sort of. I can't remember which version I was at when I rooted but I remember I downgraded to do it. But if you go in the development section you will find a thread that shows & gives you what you need to root. So you should root. Then flash a recovery image such as clockwork mod or amon ra. When I rooted I used the recovery from the downloadable app (Rom manager) in the market & that one was clockdwork mod. It's worked great for me so I've been using it ever since. Then backup whatever you are running currently. Then flash whatever rom you want. I'm about to see if I can link you to a root thread then once you do so I can give you a dl link to cm 6.1 stable. Will you be able to root on 1.5?? I don't completely know...
Edit: Ok this is the way I rooted mine, hopefully this will work for you
http://theunlockr.com/2010/09/27/how-to-root-the-htc-hero-androot-method/

What IS the scoop on "check for update is not available"?

Droid 4 running OTA GB 2.3.6 here in W. San Jose, CA
I get "check for update is not available at this time.". For many days now. LTE and Wifi (LTE is almost instant and Wifi takes 5 seconds or so).
I've looked at a zillion posts about "check for update is not available" and none have a definitive explanation. -- and all of them are from a couple of months ago or earlier. Didn't find anything recent.
I understand that the intended meaning of the message is that you can't connect to the update server.
I've read dozens of "solutions" but each one of them didn't work for somebody else so I've got to assume it was just coincidence -- resetting the phone, factory reset, renaming files, and so on. I *have* network connectivity. Data works great. Apparently I'm not able to connect to the update server? That shouldn't have anything to do with rooted or not, frozen or deleted apps, safestrap, etc. Fail to update once you get the download, sure. But I am expecting to be able to connect to the server.
Anybody know for sure?
I could imagine that the connect request might contain info identifying my particular phone model or ESN (would expect software version checks to be exchanged after connecting though). Something like that.
How does VZW roll out the updates? is it strictly by geographic region? or blocks of ESN? or what?
I have the "official" OTA download from here but figured if I side loaded it I might get out of sync or cut off from future OTAs? Failed to find a definitive answer on that too .
#eliot# from dialer then restart and try again... let us know
Sent from my DROID4 using xda app-developers app
---------- Post added at 01:33 AM ---------- Previous post was at 01:29 AM ----------
dbreezy187 said:
#eliot# from dialer then restart and try again... let us know
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
That will check in with Motorola's server btw kinda busy sorry for no further info
Sent from my DROID4 using xda app-developers app
Nope.
That's one of the myriad ones I read about (didn't recognize it right away though 'cause the post I saw it in had it in numbers instead of letters). One guy said it worked for him and the next guy said it didn't.
If you haven't tried it, as soon as you type in the final '#' you get a popup that says "Log Checkin initiated". So it does *something*but it didn't change my Check for update is not available... maybe whatever it is supposed to do never got into the server either.
lol, reminded me that I used to have a comprehensive list of all those codes for my Treo. Now I got yet another mission
[edit] dahaha, "there's an app for that". https://play.google.com/store/apps/details?id=cx.makaveli.androidsecretcodes&hl=en
Other then that Matt had to push the up date to them.. I believe on one post he actually said to get back to stock 100% wipe cache partition then he pushed the ota to said device... he was really nice about the being rooted over there... the forum is closed now so I can't check for more info.. id post over at Motorola owners forum
Sent from my DROID4 using xda app-developers app
I'll give it a bit more soak time I guess. I will try side loading the update before resetting/wiping. Reset/wipe will be my last resort. First choice is OTA.
Part of what prompted my post is that I'm unclear if the phased rollout is complete.
Is it the case that EVERYONE with a Verizon Droid 4 who is going to get the notification should have gotten it by now? Or is VZW still in the middle of the phased roll out for the Droid 4's? Got to wondering since googling for the Unavailable message only returned results that were at least a couple of months old. I figured it's possible that server access was/is part of the phasing mechanism but, then again, expected to find constant posting about that if it was. It seems that the mechanism of the roll out and the schedule is also a well kept super secret.
are you rooted? I had that same problem for days before I realized unrooting will fix that. Despite what a lot of trusted posters have said here and other forums, having root and no other changes will cause that. I used voodoo ota rootkeeper (free on market) to unroot and I had the OTA installed within 10 minutes (downloaded over wifi). it is recommended you update your binaries in your superuser app before using rootkeeper.
if you're not rooted then this doesn't apply.
---------- Post added at 02:57 PM ---------- Previous post was at 02:50 PM ----------
one more note, the stock recovery on the D4 after ICS update now tracks whether you are or you were rooted. Unrooting your phone no longer hides the fact that you were at some point rooted if a service rep goes into the stock recovery screens. this has been reported on other phones earlier in the year, now also true for D4.
No effect.
I've tried all combinations.
I've used the D4 utility only to root and install safestrap ( and used safestrap only to do a backup. nothing else)
Routine goes like this:
- in safestrap: uninstall recovery
- in settings->applications->manage applications: safestrap -> force close, clear data, uninstall
- in ES File Explorer: delete /system/bin/logwrapper
- in ES File Explorer: rename /system/bin/logwrapper.bin -> /system/bin/logwrapper
- power off, reboot
- in Titanium Backup: clear filters (ALL)
- in Titanium Backup: unfreeze all user and system apps
(the only "system" bloatware I've removed was uninstallable through the normal settings->applications -- I did not use TI for that)
- in OTA Rootkeeper: delete su backup
- in superuser: update su binary
- in OTA Rootkeeper: Protect root
- in OTA Rootkeeper: temp un-root
- power off, reboot
Try to check for updates with 4G LTE (i have great reception) - fails in a second or less
Try to check for updates with WiFi - fails but it takes 5 seconds or a little longer for a response/popup
Since you installed Safestrap you can't install the OTA update anyway, so not much of a bother that you can't get it pushed to you It'd fail trying to install as OTA updates require the stock recovery.
Root does not affect it. My wife's Droid 4 was rooted (by me) and many system apps frozen and the OTA was pushed to her the same day the SOAK testers were scheduled to get it (she was not part of the SOAK test, though I was). My sisters Droid 4 was rooted as well and she got the OTA pushed to her and installed a week or so later,
You'll have to uninstall the recovery Safestrap installs, and uninstall Safestrap. You'll also have to edit some files (logwrapper.bin or something like that).
for the ota
sbf 217 4.0.4 with rsd
SBF
http://sbf.droid-developers.org/cdma_maserati/VRZ_XT894_6.7.2-180_DR4-16_M2-37_1FF.xml.zip
rsd
http://forum.xda-developers.com/showthread.php?t=1348587
dont forget to install the motorola driver first and enable debugging mode in development in your settings
i think they are here https://motorola-global-portal.cust...e-can-i-obtain-the-usb-drivers-for-my-device?
UPDATE: (lengthy with fairy tale ending)
Management summary: I am now on the OTA ICS (acquired over the air). following a wipe/factory reset
Called *611 tech support yesterday afternoon.
Got someone that sounded like they were located on this continent AND proficient. Always a good sign when they ask what the problem is right after getting your name instead of insisting on the 5 minute scripted generic question and answer form. Stated my problem was related to the system update for my Droid 4 and that I had been getting "check for update is not available..." for a few days now. My questions were "is that expected/normal?", "I understand roll outs are phased. What is the date the roll out is expected to be complete? -- last group has been notified or can pull it?", "If the persistent 'check unavailable' message is indicative of a problem then do they have possible fixes/known problem?".
He checked for the dates and said they expect to have completed the roll out by the end of September -- all Droid 4s should have it or have it available to them by the end of September. That the "check unavailable" did not necessarily indicate a problem but that it was not "normally expected" and more likely indicative of a problem on my end since it was persistent over that length of time. I said I felt better knowing they were still in the phased roll out and maybe I should just wait a while. We tried a soft reset (vol- and power) with no effect. He said he was afraid the next step would be to try a factory reset and advised I wait a while to see if the condition cleared. Went on to say that one effect/risk of the factory reset was that, if there was a software/system problem with GB preventing the OTA check it might also effect the factory reset -- if the phone had a problem coming up it might just pull the ICS update in order to come up from the reset. (Nice! he didn't just assume I would be OK with that following a reset). That I decided to wait I should definitely call back if it didn't resolve in 2 weeks. -- OK, that was a pleasantly refreshing encounter with tech support.
So I figured, fine, I haven't really tested a restore/recovery with Titanium backup and I've never gone through a factory reset so maybe now was the time. Had 2 alternatives. I could try using the D4 utility recovery using the official (same as the OTA) zip I have on my sd card or try the wipe/factory reset and see if OTA started working.
My thoughts (due to lack of any knowledge):
- Apparently once you get on ICS there is no reversion to GB (at least the actual kernel).
- Likely they have history at Galactic Headquarters of OTA and/or physical upgrades at factory or service centers for a particular phone.
- Obviously they check the phone's system version when you connect to the OTA server. Have to in order to determine if you even need an update. Additionally they would probably check if the version the phone reports is the version they expect it to be on -- I would, for technical and support reasons.
- So maybe if I went to ICS myself it might remove me from the OTA path for future updates. Not a big deal in my mind but, heh, why eliminate alternatives if you don't have to.
* reinstall safestrap and do a backup
* uninstall safestrap (uninstall recovery, uninstall safestrap apk, delete logwrapper and rename logwrapper.bin to logwrapper)
* unfreeze everything with Ti
* batch backup all user apps with Ti
* batch backup (green and yellow) system data with Ti
* temp un-root with Voodoo
* wipe/factory reset
It comes up in GB
(lot of activity follows which I didn't write down and can't quite remember)
Basically I waited for some market activity and whatnot to die down and tried update. Immediately said update available!
Cancelled that, got Ti (pro) back from the market, batch restored missing apps.
I have eset security (i don't know... I have it on my PCs so I figured I'd stick it on my phone too. Not that I think there is much in the way of virus for android yet). Eset has an urgent notification that it wants to be added as an administrator for the device so it can protect itself from installation of counterfeit Eset. I understand that but I'm wondering if maybe Eset maybe had something to do with my fail to connect to OTA. Probably not but that's the only thing that presented itself after the reset that looked like it could have been related.
OTA again to download the update -- deferred update after download.
Oh wait, forgot to batch restore system data. Did that, checked for sms messages. All good so I triggered the update.
Holy crap!!! I forgot to temp un-root! Figured the worst thing I could do was try to abort anything and just let it run and expect the update to fail.
It didn't fail. It completed just fine?
I go through the new phone screens far enough to sign into my google account.
Bunch of market update activity.
Restore missing apps with Ti
Restore system data with Ti
Then it strikes me that, sure enough, I'm still rooted. I did not restore root anywhere after the update.
I was rooted before the update (by accident) and still rooted after the update... Whats up with that?
So at the moment I'm a happy camper.
All my apps seem to have been effortlessly restored.
All my app settings seem to be intact.
All my system data seems to be intact with no migration issues.
I'm still (magically) rooted without doing anything.
standard101 said:
[/COLOR]one more note, the stock recovery on the D4 after ICS update now tracks whether you are or you were rooted. Unrooting your phone no longer hides the fact that you were at some point rooted if a service rep goes into the stock recovery screens. this has been reported on other phones earlier in the year, now also true for D4.
Click to expand...
Click to collapse
I am going to have to disagree with this. I was rooted and flashed. Ran the download and the install failed. I then did a factory reset (lost my flash and root as expected) and immediately ran the download. Install went off without a hitch. I even had a support rep from verizon and motorola on the phone during the install when i was doing it because i was so mad about the slow download. They were watching the install once it was done because they both stated that everything on my phone "looked good".
YeeP said:
I am going to have to disagree with this. I was rooted and flashed. Ran the download and the install failed. I then did a factory reset (lost my flash and root as expected) and immediately ran the download. Install went off without a hitch. I even had a support rep from verizon and motorola on the phone during the install when i was doing it because i was so mad about the slow download. They were watching the install once it was done because they both stated that everything on my phone "looked good".
Click to expand...
Click to collapse
I don't think that's what he was saying.
After you go to ICS it tracks (displayed in the recovery screen) if you are or were rooted.
Go into recovery and you will see a yellow "qe 0/0" left of the android.
ge 0/0 -- are not rooted/never been rooted
ge 0/1 -- are not rooted/been rooted sometime prior
ge 1/1 -- are rooted/been rooted
No idea if this was tracked before but not displayed in recovery. I suspect it was. On GB they were checking system files on boot and logging differences (I think I read they were comparing system file CRCs?). The list was getting logged to a qer...something log file (I forgot the file name and where it's at). I verified that. On my rooted GB there were mostly /xbin files and a couple of others listed in the log.
Now on ICS my recovery screen shows "qe 1/1".
Oddly enough I did a factory reset, forgot to temp un-root and my root persisted through the OTA update just fine. No idea why.
Since my root persisted through the update I was not able to check before re-rooting to see if it displayed "qe 0/0". My guess is this was always logged/stored and they just added the display to the recovery screen. I would find it almost inconceivable this information (and other) was not written to NVRAM since day one. Basic support/diagnosis information.

Just purchased a Verizon droid 4

I just purchased a droid 4 from Verizon, have wiped it a few times, but my front facing camera, keyboard, soft key lights are not working. I have searched online for fixes, Motorola said i could pay 150.00 in order to get it replaced. I figured i would come here first to see if anyone had a suggestion or a link to where i could wipe it before it took the 4.4 patch to where it seems to have totally messed it up according to other online sources .
timothy_pierce said:
I just purchased a droid 4 from Verizon, have wiped it a few times, but my front facing camera, keyboard, soft key lights are not working. I have searched online for fixes, Motorola said i could pay 150.00 in order to get it replaced. I figured i would come here first to see if anyone had a suggestion or a link to where i could wipe it before it took the 4.4 patch to where it seems to have totally messed it up according to other online sources .
Click to expand...
Click to collapse
Are you running with the stock rom?
Have you tried a custom rom?
I mean do you know if it't software issue or hardware issue?
Sent from my XT894 using Tapatalk
dom2319 said:
Are you running with the stock rom?
Have you tried a custom rom?
I mean do you know if it't software issue or hardware issue?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
I am running the latest version of android for that series of phone, believe its 4.4 from verizon, i have not rooted it yet, i am trying to figure out how to get it back to the original state before the updates. As it seems since the update many consumers have had these same issues with out being able to fix them, i have tried fixes that i obtained from the Motorola forums and the lighting situation did not work. Am not sure its hardware due to the keyboard being functional. I appreciate any and all help.
ok found a video on how to bypass the non sim set up panel and here are the versions of android i am running.
98.72.188.xt984.Verizon.en.US
Android version 4.1.2 sorry i messed up the version earlier.
timothy_pierce said:
ok found a video on how to bypass the non sim set up panel and here are the versions of android i am running.
98.72.188.xt984.Verizon.en.US
Android version 4.1.2 sorry i messed up the version earlier.
Click to expand...
Click to collapse
Hi Timothy,
OK you're running Android JellyBean, AFAIK Verizon never released a Kit-Kat (Android 4.4) update for the device.
Personally, given that AFAIK it's not possible to roll back to a previous version of Android (you can only reinstall the previous version), I would suggest you root it, install SafeStrap and do a quick install of something like Cyanogen (not the best ROM for Droid 4 IMHO but will quickly do the job). At least those can be rolled back.
Rooting and installing SafeStrap is SO utterly easy on this device that it should be made harder
For a start, everything you'll need, if you want, can be grabbed from my Google Drive
h t t p s://drive.google.com/folderview?id=0B3MTT4jOK738fmdLLURMQVBGWkVpTDBMTmg1UGFUd3JWNDNlcUVzQWZFQXBpT3dCMFJhdTg&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M
If you don't have any file manager yet (as you'll need one), ES File Explorer is a great one, as you'll most certainly need it.
Rooting:
Get Towel root from:
h t t p s://drive.google.com/folderview?id=0B0EWnwDplBc0fi1KMVVIRmQteDhFYWcwSGFselpXWmpfV29LWlZlZVVHdlU0b0FBQnYtNkk&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M#list
install it and root your Droid4
Installing SafeStrap:
Check out this page for info about SafeStrap
h t t p://blog.hash-of-codes.com/how-to-safestrap/
Once your device is rooted, you can install SafeStrap
Again you can grab a copy from my Google drive:
h t t p s://drive.google.com/folderview?id=0B0EWnwDplBc0fk5aeUhFSjlQMzZ2TXNYM0lsWVRDWklLOU1nYkUybzU1emJDV1IwS0tkazg&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M
Installing a custom rom:
Once you have installed SafeStrap
You can download CM11 which I've tested from:
h t t p s://drive.google.com/folderview?id=0B0EWnwDplBc0fnJJd0s1ZV85aEE1YkF0TjNzM28tcmxfOVkzZVJ0OUVhLThrR29sb19vVW8&usp=drive_web&tid=0B0EWnwDplBc0fnBGbDg3ZmdZNC1ET1JZeVRWdE8tZ2p1Um41OThLeTZ2WWtRNE9TUXJpS2M
- Copy the file to your SDcard0 (usually named MOT)
- Boot into SafeStrap, create a small partition (1000 MB for data is enough) in Slot1
- install CM 11 and see if the problem is fixed in CM11 and report back to me
Take care
Dominique
or just see [INDEX] Motorola Droid 4

Note 4 problems after marshmallow and tmobile update, am trying to root/problems

My note 4 was bought used, no warranty. When I bought it, it was rooted, but no custom rom, worked great. Once lollipop came out, I wiped and returned to non-root and was able to get the update through tmobile. Didn't bother rerooting as things were ok. Marshmallow udpate came, and I noticed a lot of screen lag. Less than a week ago, tmobile did some sort of update and now, the phone shuts off and restarts on it's own, has very slow screen response (nothing, and then tries to do the same function 10 times in a row, messaging is very slow, types the same words several times over). I did a factory re-set twice. Once, I reloaded all my favorite apps, etc. still bad, so then I did factory reset but did not add anything or bring in my contacts, etc. I am planning on buying the note 7 in a 3-4 months, but in the meantime, would like to continue to use my note 4. I tried doing the rooting method using odin, it appeared to work ok (got the successful notice), triggered the knox thing, but..when I use a root checker, it says phone is not rooted. I am hoping that by rooting and putting a new rom on there I can fix this thing in the interim. So..suggestions on what to do next? Let me know what additional information you need. Could it be the phone itself and not the software? Suggestions on a cheap interim phone? links to relevant threads also appreciated. Is there a better way to wipe everything and start new that I am did not do? I did a factory reset. I have two batteries, which I changed out intermittently to see if it as a bad battery. Android version 6.0.1, security patch level july 1, 2016 Kernel 3.10.40-7804088
Knox version 2.6
You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?
more info
goosa23 said:
You need to give more information on what you did to root. What version is your phone, what files did you odin, and did you flash SuperSU?
Click to expand...
Click to collapse
No to supersu? it's sm N910t, I think what finally worked what odin 3.9 version and flashed the stock that is meant to go with this particular phone to downgrade it down to lollipop. The first few times, I got fail with Odin, but realized that I had marked the option on the phone to keep it from being wiped/flashed if someone found it, once I got that off, I got a successful message. I used the following link and did all of the things mentioned on a link that I am too newbie to be allowed to post, apparently.
but it goes with 3.7 odin, flash the stock firmware from the phone model, and get to the reset button, if successul and then supersu appears.
I got as far as step 8, with odin showing the green 'reset'. But when I went back to the phone, I did not have supersu.
I've tried to do it again, but I get 'fail'
Try out the toolkit that is in the forum. https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app
The link takes me to a 404 page not found, is part of it missing?
send me the link by private message so i can see what you are doing?

Samsung Galaxy Note 3 Sm-n900a best rooting option?? Need current info.

Hello guys and Gals, this will be my first time posting so please bear with me. I have been trying to find the best option to root my Samsung Galaxy Note 3 Sm-n900a for a while now, seems to be one of the harder phones to root... this will be my first time attempting to root a device, so I want to make sure I do everything correctly. I have watched multiple videos and read a lot of threads on the subject but it is hard to find anything that is current and has the proper links to be files needed. if anybody has a good step-by-step walkthrough or video and the time to help me I would greatly appreciate it, if you do respond to the thread please dumb it down I am still learning terminology. I am determined to get this done come hell or high water. so if anybody has a good step-by-step walkthrough or video and the time to help me I would greatly appreciate it. Thank you for helping me put a nail in this coffin i I have been trying to do this far too long.
I just did this over the course of hours. I can't say I'm pleased with any of the explanations on xda-developers or found by Google. Unfortunately, writing up a good, full explanation is beyond me right now.
I did this from the Android 5.0.1? Lollipop "OC3" version (seen as the last 3 characters of the "Baseband version" under Settings -> General -> About device). Apparently this version cannot be rooted, however, you can downgrade your version of Android to one that you can root: Android 4.4.2 KitKat ("N900AUCUCNC2"). Apparently you can do something to stay rooted while manually updating to Android 5.0 Lollipop "OC1," but updating to the current AT&T version "OC3" revokes your root access.
I followed the process listed at https://forum.xda-developers.com/note-3-att/general/root-att-note-3-android-5-0-t3318130/post65467618, but if you are satisfied with having rooted Kitkat 4.4.2, you don't need to do steps 11 and 12. If you want the more recent Android 5.0 OC1, then do steps 11 & 12.
One thing I can do is help you understand some of the things I never saw explained. In the list of instructions you will see some programs you will need. A brief summary of each:
Odin - A program that runs on Windows that will manage some low-level aspects of your phone over a connected USB cable. It is used to install an OS (Kitkat 4.4.2 in this example) after your phone has been Wiped from the boot loader menu (gotten to by turning your phone on holding down VolumeUp + Home buttons). It is nice to have a MicroSD card onto which you can move various things before wiping the phone. (You never need to wipe your MicroSD card. Make sure you don't wipe it when using the Wipe feature in SafeStrap).
Towelroot - This is actual program that roots your phone using a known problem in the phone. After running the program, tap the only button there is to do it. I think this is a safe operation—as in, I think it will tell you if it can't rather than scrozzle your OS.
SuperSU - A program that manages which apps on your phone have root access. After it is installed, when you run a newly installed program that requires root access, SuperSU will pop up a dialog asking you if you want to grant it root access. I saw no indication you can get by without it, even if you don't need to "manage" app root access.
SafeStrap - This is a program that does various things, most importantly installing other operating systems that you previously loaded onto your phone as a file and then letting you choose which one you want to boot to whenever your phone boots up. It installs like a normal program, however from within the program you can "Install Recovery" or "Uninstall Recovery." "Recovery" is a bit of software it inserts into the phone boot process. While booting, if you want to use that software, you tap "Recovery" in the lower left. Tap "Continue" if you just want to boot with the currently active OS (chosen from within the Recovery software under the "Boot" options). With Recovery, you create a new slot for an OS, MAKE IT THE ACTIVE OS, Wipe it (Advanced, NOT format), then can back up a menu and install an OS from your MicroSD card. The purpose of all these shenanigans is so you don't have to lose your working Android install while installing something else.
Titanium Backup - A software backup program that requires root access to work. It also has a ton of other features loosely related to backing up. It is the simplest way to prevent AT&T from updating your version of Android to the unrooted current version. Having said that, it is anything but simple because of the user interface. You might investigate alternative methods for preventing auto-updating.
Be aware that whatever software (e.g., file manager) you use to hunt down files and folders on your phone is probably not going to be showing you everything. There are hundreds of programs that your phone uses, some of which are hidden. Titanium Backup does appear to be capable of showing a true full list of apps (including system apps). This is pertinent, because the AT&T Software Update program is hidden very well.
Potential costs:
$10-20 US approximately for a MicroSD card. There's fast ones that are in that price range. Google for reviews.
$5.99 for Titanium Backup from the Google Play store.
GregJ7 said:
I just did this over the course of hours. I can't say I'm pleased with any of the explanations on xda-developers or found by Google. Unfortunately, writing up a good, full explanation is beyond me right now.
I did this from the Android 5.0.1? Lollipop "OC3" version (seen as the last 3 characters of the "Baseband version" under Settings -> General -> About device). Apparently this version cannot be rooted, however, you can downgrade your version of Android to one that you can root: Android 4.4.2 KitKat ("N900AUCUCNC2"). Apparently you can do something to stay rooted while manually updating to Android 5.0 Lollipop "OC1," but updating to the current AT&T version "OC3" revokes your root access.
I followed the process listed at https://forum.xda-developers.com/no...att-note-3-android-5-0-t3318130/post65467618, but if you are satisfied with having rooted Kitkat 4.4.2, you don't need to do steps 11 and 12. If you want the more recent Android 5.0 OC1, then do steps 11 & 12.
One thing I can do is help you understand some of the things I never saw explained. In the list of instructions you will see some programs you will need. A brief summary of each:
Odin - A program that runs on Windows that will manage some low-level aspects of your phone over a connected USB cable. It is used to install an OS (Kitkat 4.4.2 in this example) after your phone has been Wiped from the boot loader menu (gotten to by turning your phone on holding down VolumeUp + Home buttons). It is nice to have a MicroSD card onto which you can move various things before wiping the phone. (You never need to wipe your MicroSD card. Make sure you don't wipe it when using the Wipe feature in SafeStrap).
Towelroot - This is actual program that roots your phone using a known problem in the phone. After running the program, tap the only button there is to do it. I think this is a safe operation—as in, I think it will tell you if it can't rather than scrozzle your OS.
SuperSU - A program that manages which apps on your phone have root access. After it is installed, when you run a newly installed program that requires root access, SuperSU will pop up a dialog asking you if you want to grant it root access. I saw no indication you can get by without it, even if you don't need to "manage" app root access.
SafeStrap - This is a program that does various things, most importantly installing other operating systems that you previously loaded onto your phone as a file and then letting you choose which one you want to boot to whenever your phone boots up. It installs like a normal program, however from within the program you can "Install Recovery" or "Uninstall Recovery." "Recovery" is a bit of software it inserts into the phone boot process. While booting, if you want to use that software, you tap "Recovery" in the lower left. Tap "Continue" if you just want to boot with the currently active OS (chosen from within the Recovery software under the "Boot" options). With Recovery, you create a new slot for an OS, MAKE IT THE ACTIVE OS, Wipe it (Advanced, NOT format), then can back up a menu and install an OS from your MicroSD card. The purpose of all these shenanigans is so you don't have to lose your working Android install while installing something else.
Titanium Backup - A software backup program that requires root access to work. It also has a ton of other features loosely related to backing up. It is the simplest way to prevent AT&T from updating your version of Android to the unrooted current version. Having said that, it is anything but simple because of the user interface. You might investigate alternative methods for preventing auto-updating.
Be aware that whatever software (e.g., file manager) you use to hunt down files and folders on your phone is probably not going to be showing you everything. There are hundreds of programs that your phone uses, some of which are hidden. Titanium Backup does appear to be capable of showing a true full list of apps (including system apps). This is pertinent, because the AT&T Software Update program is hidden very well.
Potential costs:
$10-20 US approximately for a MicroSD card. There's fast ones that are in that price range. Google for reviews.
$5.99 for Titanium Backup from the Google Play store.
Click to expand...
Click to collapse
Life got pretty busy there for a minute... I was able to get Titanium Backup I have had a good SD card for a while now safestrap SuperSU towelroot everything that I need. But this being my first time and not really ever using the software, it's giving me a little bit of anxiety. Before trying process the root I had a couple of questions that I definitely would like to get a solid answer on they might sound stupid but I'd rather sound stupid then not have a phone and ask lol. Okay how about we know I have a Note 3 SM n910a AT&T original carrier swapped over to Metro PCS I'm on one of their $50 plans which I think is unlimited everything but no tether so I have been using PDA and foxfi tethering from my phone to my computer... my roommate has a hotspot but he is rarely home. I need to know if it is possible to complete the root in that situation also the person from the thread that you sent me to confused me as far as making sure you have the ROM pre-downloaded. It just confused me I'm to the point I want to have somebody jump on TeamViewer with me and just make sure I don't screw up too bad.. I did go look at them custom robs as well if anybody would like to share their favorites or what they think is a good easy ROM to be able to play around with it and not mess it up too bad I would love any suggestions from anybody
XxLightxX said:
Life got pretty busy there for a minute... I was able to get Titanium Backup I have had a good SD card for a while now safestrap SuperSU towelroot everything that I need. But this being my first time and not really ever using the software, it's giving me a little bit of anxiety. Before trying process the root I had a couple of questions that I definitely would like to get a solid answer on they might sound stupid but I'd rather sound stupid then not have a phone and ask lol. Okay how about we know I have a Note 3 SM n910a AT&T original carrier swapped over to Metro PCS I'm on one of their $50 plans which I think is unlimited everything but no tether so I have been using PDA and foxfi tethering from my phone to my computer... my roommate has a hotspot but he is rarely home. I need to know if it is possible to complete the root in that situation also the person from the thread that you sent me to confused me as far as making sure you have the ROM pre-downloaded. It just confused me I'm to the point I want to have somebody jump on TeamViewer with me and just make sure I don't screw up too bad.. I did go look at them custom robs as well if anybody would like to share their favorites or what they think is a good easy ROM to be able to play around with it and not mess it up too bad I would love any suggestions from anybody
Click to expand...
Click to collapse
I just ended up stayin on kk rooted on mine. Everytime i goto lolipop i brick it. Its almost a hassle to try. I would odin the kk firmware and use towel root. Install xposed and some root apps. If ures is anything like mine dont debloat it. I debloat lightly. And next reboot get all kinds of spen and other force closes. The note 3 in general seem unstable. But i need to restore m8ne back stock now as its keeps force closing. I will be starting mine over for the 100th time it feels like. Dont let my ramblings discourage you. It is a awsome device and having a lgg5 iphone 5 and a few others my note 3s outer glass is destroyed. Got it like that. I would take the note 3 over the rest if i could get it to run rite more than 2 or 3 days at a time. Ive. Always set all my devices the same way. Debloated them the same but this one is really touchy.... Im on here a lot if u gots any ?s just hollar at me.
If you're still interested in an easy way to root, use Wondershare Dr Phone. It worked for me on stock OC1 and then the just used Flashfire to flash whatever I wanted.

Categories

Resources