Related
Good Evening everyone. As the title says i need help.
I have had my phone rooted fine in the past but went ahead and did the .893 update wich is where something went screwy. It booted fine after doing the .893 update however after doing a reboot it would not boot. just stayed at the M dual core. I think something went wrong on the update because all my apps were still there when it did boot.
So i tried doing a return to stock using the RSD lite program..that fails right away no matter what i do.
So i went and tried to do the One click fastboot system restore program.
Now when i did that the INFOpreflash validation failure showed up however everything else went through fine. the phone reboots and everything works just not great the signal strenght is very low.
The version that got installed says 5.5.1_84_dbn-55. So i try Pete's root method and it go thru to step 2 but then fails at rebooting for the second time saying it could not get root via local.prop.
If anyone could please help me get back to normal stock it would be much appreciated
Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium
P.S. You are stock now.
Sent from my DROID BIONIC using xda premium
harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App
dubsx said:
harsh, but true...has nobody heard of google...?
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Or XDA?
Sent from my DROID BIONIC using xda premium
I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed
that too, haha...
Sent from my DROID BIONIC using XDA App
Sidewind75 said:
I did do the forever root and i did read that thread three times b4 i attempted it. I know i am stock. I checked the mount_ext3.sh file and those three lines are no longer there.
And i also have googled this but cannot find an answer hence why i am asking on here..all options i have found to try to reroot have failed
Click to expand...
Click to collapse
Well, you didn't list that in the OP.
At this point, I don't know. Here is all I got: enter stock recovery and wipe everything. Reboot. Cross your fingers.
Sent from my DROID BIONIC using xda premium
mistawolfe said:
Not to be a jerk, but did you READ any thread on here before you did this??
1) Unless you used p3droid's forever root method, you're done. No root.
2) Wrong forum - should be in general
3) RSD won't work.
4) I don't feel sorry for you. You should have researched more. If you would have taken the time to read a few threads, you would have known the answers before you did this.
Enjoy your new build - you'll be with it for awhile.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!
quentin0 said:
Not to be a jerk...(goes on to be a jerk)
I love when people preface their statements with stuff like "I'm not racist BUUUUTTT". It's like a contrition...but in reverse!
Click to expand...
Click to collapse
Sometimes the truth hurts. He messed up. Don't shoot the messenger.
Moderator Message
Breathe in, breathe out!!!!
I'll breathe when this .893 goes through and I keep root
There is also some very seriously contradictory info in the OP. While castigating him for being a noob did anyone notice that he claims to have flashed the update and then reverted to stock?
This is impossible from our current understanding of how the bootloader works.
More information about the exact steps followed and the exact results at each step would be very helpful to try and figure out what really happened.
OK?
Less heat and more light...
I just got a little frustrated, as every time I open XDA today I see the same/similar post.
Cell - I didn't see in the OP where he said he flashed back. I read where he tried, but I didn't see any mention of 896.
I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated.
Oh and i have also tried to unroot it..it also fails at adb not being able to gain root access
Sidewind75 said:
I could not get the .893 to boot after a reboot so i used the One-click fastboot restore and root which brought back to stock but also made it so that i can no longer root. It fails every time on the local.prop process saying adb could not get root access. I did try the stock recovery and still no go. I also tried the adb fix that was posted to remove local.prop but when i tried it says file not found. I have rooted and messed with many phones in the past from Droid 1 and up and this is the first problem that i couldnt solve so as i said any help would be appreciated
Click to expand...
Click to collapse
This isn't going to help your current issue, but how long did you let it sit (after installing 893) before you decided it wouldn't boot? I ask because the guy who was ballsy enough to do it here said the first boot takes about 7 minutes.
EDIT: Nevermind - mine booted in 2 minutes.
it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible
Sidewind75 said:
it was fully booted and operational. i just did a power off after a half our or so and power back on and it just sat at the M dual core screen...i dont know why it would not boot. I tried pulling the battery. taking out the sim card and all that. the only thing that would get it booted was the One-click fastboot restore and root program so I at least have a working phone but for some reason the signal strength is horrible
Click to expand...
Click to collapse
Try to do the fastboot again and root it through there. Or, if you did that already (root in fastboot restore) try rooting afterwards.
Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.
tghockey07 said:
Might sound dumb, but did you forget to save the chmod changes to the build file? It's a fairly easy mistake and it is the only thing I can think of.
Click to expand...
Click to collapse
yes I did and i checked it twice after making sure root explore was closed reopened and checked the file the chmods where there...but now they are not. and seeing as how i cant root i cannot get them back on it
Hi everyone
I'm a proud owner of a Galaxy Tablet. Also I'm very new to forums and tablets for that matter. Recently I got a message in my settings that there is an update available. This is my first tablet so I'm not very expérienced. My tablet is rooted. It crashed a couple of times but all in all seems to be working. My question is if it's safe to update. I read in the forums about phones being bricked and other problems with updating rooted phones and tablets. Is there anything I should do before installing the update to make sure it works?
Any advice is appriciated. Cheers.
Just do the update. I'm not going to guarantee that you won't have problems but this upgrade comes via official channels. I have not had any problems in upgrades with my Galaxy S and S2.
Having said that:
Backup what you can.
Refresh or check the stickies on how to reflash if necessary. So download odin and stock roms just in case. Not necessary but may come in handy.
Otherwise just do it ;-)
P.s this is where I insert disclaimer of having no liability
Sent from my GT-I9100 using xda premium
Just to make sure
Thank you very much indeed for your prompt reply. Dont get me wrong please but I'm so inexperienced that it makes me paranoid. So just to make sure that nothing goes wrong I'd like to verify that were talking about the same tablet. Samsung Galaxy P7310. IT'S ROOTED. (So I don't have to unroot it to update?)
I'll start reading into all this ODIN business since I've never done it. Probably shall have more questions then.
And if we are talking about the same update. Could you tell me your opinion on it please.
Stock ROM
And where could I get the stock ROM for my P7310 (XWKI2 if it's build specific ) please?
And I bought it through Amazon.fr if it's country specific. I already read too much stuff about tablets bought in Hong Kong.
Cheers.
I tried to search within xda forums using [stock][p7310] and there are some firmware models. You may want to try SAMMOBILE as well. As have not done, I cannot be any more specific.
Normally, you should be able to rely on the updates that get pushed through the system. I say 'normally' but you have rooted and 'may' cause some instability. I did notice in Kies that there is an emergency firmware recovery option which is also an option.
Chances are the update will only be 3.1 to 3.2 (am on 3.2 now and ICS may be around the corner). Also an update usually removes root.
Personally, I would not mess with root just yet if you are new. I only started messing around with root and roms on my Galaxy S as there were options to fix specific issues. It's a good learning curve but you spend a lot of time fiddling so make sure you backup.
Thank you very much indeed for your help. I shall be carefull with the root. Now the only programs that use it are Titanium Backup and Ad Hoc Enabler. And I never touch it by myself. Or at least not yet. Your clear answers calmed me down so as soon as I get a bit of time (All this backup/restore business sounds time consuming at least for the first time) I wll definitely update.
No problems. Main thing is to give the update time. Usually takes about 5-10 minutes or less but feels longer watching. I have soft bricked by being impatient during a flash and unplugged from Odin. Reflashing fixed. You shouldn't have these issues if normal update.
Sent from my GT-P7300 using xda premium
d.lavaman said:
Hi everyone
I'm a proud owner of a Galaxy Tablet. Also I'm very new to forums and tablets for that matter. Recently I got a message in my settings that there is an update available. This is my first tablet so I'm not very expérienced. My tablet is rooted. It crashed a couple of times but all in all seems to be working. My question is if it's safe to update. I read in the forums about phones being bricked and other problems with updating rooted phones and tablets. Is there anything I should do before installing the update to make sure it works?
Any advice is appriciated. Cheers.
Click to expand...
Click to collapse
You should update, i'll smoother,but for safety i think you should unroot, or you can use odin and flash rom manualy
http://forum.xda-developers.com/showthread.php?t=1406137
quangtrungh said:
You should update, i'll smoother,but for safety i think you should unroot, or you can use odin and flash rom manualy
http://forum.xda-developers.com/showthread.php?t=1406137
Click to expand...
Click to collapse
Thanks. So how couod I unroot then please?
d.lavaman said:
Thanks. So how couod I unroot then please?
Click to expand...
Click to collapse
It's in the link he just sent you...
the update
Hi everyone
Thanks for your support before.
It doesn't work though. I flashed CWM to create a back up. Did it. And then tried updating. It
downloads. Starts updating. Gets to 12% and then reboots with the message that the update failed
and I should try updating with Kies. Again I read some posts about bricking the tablet while updating with Kies. So I'm here looking for help. Could it be because of CWM. And if it is could I get rid of it just for the update and flash it back.
Cheers in advance.
update doesn't work
Hi everyone
Thanks for everyone's support before. It gave some confidance.
It doesn't work though. It's starts updating and then reboot with the message "Update failed, try using Kies, or go to Samsung service centre".
I removed root it didn't help. I got CWD flashed. Could that be a problem.
Could I get rid if it just to be able to uodate?
Need some help here. Kies seems dodgy judging by the posts.
Thanks in advance.
Hello everyone! As most of you may know, AT&T pushed out an update today for the MotoX. A few weeks ago, I so happened to root my MotoX using PwnMyMoto. I installed the OTA update, without knowing this would **** my phone up as I had read that if you update using OTA it will just undo the root. Now my phone is in a constant boot loop. I can't do anything. By the time the phone gets loaded up and connects to WiFi or anything it reboots.
I suppose I'm screwed? Thanks.
NicholasJohnson said:
Hello everyone! As most of you may know, AT&T pushed out an update today for the MotoX. A few weeks ago, I so happened to root my MotoX using PwnMyMoto. I installed the OTA update, without knowing this would **** my phone up as I had read that if you update using OTA it will just undo the root. Now my phone is in a constant boot loop. I can't do anything. By the time the phone gets loaded up and connects to WiFi or anything it reboots.
I suppose I'm screwed? Thanks.
Click to expand...
Click to collapse
So many threads already covering this issue. Search, read, and also post to Q&A forum if you have a question.
Sent from my XT1058 using Tapatalk 4
NicholasJohnson said:
Hello everyone! As most of you may know, AT&T pushed out an update today for the MotoX. A few weeks ago, I so happened to root my MotoX using PwnMyMoto. I installed the OTA update, without knowing this would **** my phone up as I had read that if you update using OTA it will just undo the root. Now my phone is in a constant boot loop. I can't do anything. By the time the phone gets loaded up and connects to WiFi or anything it reboots.
I suppose I'm screwed? Thanks.
Click to expand...
Click to collapse
So any luck with this? Im trying to figure out how to save the phone if possible myself. Couldn't find the threads mentioned by ^ post.
ronVnor said:
So any luck with this? Im trying to figure out how to save the phone if possible myself. Couldn't find the threads mentioned by ^ post.
Click to expand...
Click to collapse
Since your phone is now a useless brick can I buy it from you for $20?
Sent from my Moto X.
Please ignore people who are not considerate enough to link to a post when saying "please search" as if they have actually tried using the search to find information. Because if they had, they could have easily linked you to the corresponding topic, and the discussion would have been over, or they would have found (like i did) limited results on the matter.
Here's an image that should be flashable that includes OTA (cannot revert, or root afterwards at this point)
[URL="http://forum.xda-developers.com/showthread.php?t=2471975]http://forum.xda-developers.com/showthread.php?t=2471975[/URL]
I won't claim to know alot, especially about this device, i'm mainly researching because it is my next device I'm purchasing (very soon). Right now there's not alot of information, but there should be official flashable images available for the phone floating around on XDA or some of the other forums.
I wish i could do more to help you in this situation, the last time i bricked a device (HTC Incredible) i was lucky to find an original image to restore it. This is the best method because an unrooted working phone is better than no phone at all, if that AT&T OTA image doesn't flash, my best recommendation is to look for an original motorola firmware and flash it using fastboot, i don't own the device (yet) so i don't have any specific instructions to help you with.
Destreyf said:
Please ignore people who are not considerate enough to link to a post when saying "please search" as if they have actually tried using the search to find information. Because if they had, they could have easily linked you to the corresponding topic, and the discussion would have been over, or they would have found (like i did) limited results on the matter.
Here's an image that should be flashable that includes OTA (cannot revert, or root afterwards at this point)
[URL="http://forum.xda-developers.com/showthread.php?t=2471975]http://forum.xda-developers.com/showthread.php?t=2471975[/URL]
I won't claim to know alot, especially about this device, i'm mainly researching because it is my next device I'm purchasing (very soon). Right now there's not alot of information, but there should be official flashable images available for the phone floating around on XDA or some of the other forums.
I wish i could do more to help you in this situation, the last time i bricked a device (HTC Incredible) i was lucky to find an original image to restore it. This is the best method because an unrooted working phone is better than no phone at all, if that AT&T OTA image doesn't flash, my best recommendation is to look for an original motorola firmware and flash it using fastboot, i don't own the device (yet) so i don't have any specific instructions to help you with.
Click to expand...
Click to collapse
Teach a man to search and he will have near infinite knowledge. Give a man the answer and he will bug the **** out of you every time his brain farts. Jesus said something similar to that. Good stuff.
Lesson: XDA search sucks. Use Google to search XDA. For example use this search phrase: "moto x bootloop after update root site:forum.xda-developers.com"
Consequentially the first result is the one that would get the OP out of his infinite loop of sadness.
Dont cripple people by saying its ok to ask before searching. No one wins.
mentose457 said:
Teach a man to search and he will have near infinite knowledge. Give a man the answer and he will bug the **** out of you every time his brain farts. Jesus said something similar to that. Good stuff.
Lesson: XDA search sucks. Use Google to search XDA. For example use this search phrase: "moto x bootloop after update root site:forum.xda-developers.com"
Consequentially the first result is the one that would get the OP out of his infinite loop of sadness.
Dont cripple people by saying its ok to ask before searching. No one wins.
Click to expand...
Click to collapse
Well in this case as you said yourself, "XDA Search Sucks" even i didn't think of that (and i've been using XDA for several years now) so everyone can learn something by asking questions. (also thank you for the info because now i know a better way to search XDA)
mentose457 said:
Since your phone is now a useless brick can I buy it from you for $20?
Sent from my Moto X.
Click to expand...
Click to collapse
Psshhhh...I'll give you $50, OP.
Anyway, you need to delete the update from cache. If you can't stay booted long enough to do this from the system, you may have to do it from fastboot (use the command "fastboot erase cache" without the quotes).
This is my first post and I'm going to try my best to not break a rule. If I do, I apologize in advance.
Thread thread is a sort of, "This is how I updated my phone from 4.2.2 to 4.4.2 and rooted it but your mileage may vary."
First, thanks goes to Sunderwear for his directions on how to push KitKat to the Samsung S4 Active as well as ROOT it. I rooted my 4.2.2 phone a few months ago and didn't realize doing so would prevent OTA updates. I went to the AT&T store to have them put 4.4.2 on the phone only to be told that the store didn't have the image (or whatever they said) and couldn't put it on my phone. Instead, they put 4.3, which turned out to be great because the directions pretty much have you going back to 4.3 in order to root.
BTW, if you are uninitiated, you may want to read this glossary page.
After having root in 4.2, I knew I wanted it in 4.4.2!
For the most part, I've been hesitant to flash the phone. I tried like hell to flash my first Android (Samsung S2 Skyrocket) only to brick it. (FWIW, if you can tell me how to fix it, I'd be gracious! It buzzes once and then twice and repeats.)
Anyway, I started in the thread above only to find that I now needed to download Odin. This, surprisingly, was difficult. I found this site (http://odindownload.com/) which I am convinced is some sort of hacked version of Odin because when I tried to install from there, my Symantic warned me. When I disabled it, the file tried to install a bunch of bloatware/spyware. It EVENTUALLY gave me Odin.
FYI, this thread was of no use. No download links.
Later on, after searching for something unrelated, I got to a "better" site. Unlike the link above, this site has a zip file compared to the bloat-ridden executable.
I learned that I had to use Odin 3.07 and NOT Odin 3.09. Odin 3.09 did not have the PDA button that would be central to me flashing the ROM to the phone.
I started my journey on the thread for the Stock AT&T Firmware Collection. I learned that the thread uses the last three characters of the build name to identify the build. For example, 4.3's build name is I537UCUBML2 but was referred to as "ML2". This was a bit confusing but I got the hang of it. I then went over to the 4.4.2 rooting thread. It was there that I read Sunderwear says that you need to downgrade to 4.3 to root 4.4. I was grateful that AT&T only updated me to 4.3!
Sunderwear's second post described how to root 4.4.2 if you had a rooted 4.3. Since I hadn't done that yet, I proceeded back to the firmware collection and found the thread to root my 4.3 phone.
I downloaded the files and loaded up the first file to flash. I made the mistake of keeping my phone plugged in while trying to put it in download mode. It was when I stumbled upon this page that gave me the clue that my phone had to be disconnected first before going into download mode.
Once done, I clicked Start and Odin flashed my phone! It took about 2-3 minutes.
The next step was to do saferoot. The thread didn't link it so here it is.
SafeRoot requires your phone to be in USB debugging mode. Directions were found by googling. You go to Settings, About Device, and click Build Number until you get a message saying you have enabled developer mode. Then go back out one screen and go into Debugging options and enable USB debugging.
One installed I rebooted the phone and everything worked...except for wifi and "some other stuff". The thread warned you about this so I didn't worry. I flashed the next file and rebooted. Updated SuperSU and everything worked!!
I verified that I had root by installing Root Checker.
All was great with 4.3! Now for what turned out to be the more agonizing part: Upgrading to 4.4.2.
Going back to the 4.4.2 rooting thread, I learned that all I needed to do was install SafeTrap to update to KitKat and then flash a couple more files. I downloaded pwnedkitkat.zip (link in the thread) and then installed SafeTrap. I presume that SafeTrap is some sort of bootstraping method of updating the firmware.
I copied the SafeTrap apk file, along with pwnedkitkat and the updated superSU zip files to my external SD card. Once everything was copied, I installed SafeTrap and then opened it. SafeTrap then offered me the option to install Recovery Mode. Once done, I restarted my phone.
I noticed a new splash screen after the Samsung splashscreen. I clicked the Menu button (left of home) to start the recovery process. I clicked "Install" and pointed it to the pwnedkitkat.zip file. This took the longest. Probably took 15 minutes but felt like an eternity. I wasn't sure if my phone bricked when the screen turned off! But upon turning it back on, it was still going.
The bar moved very slowly. But remained patient. After a long 15-20 minutes, it updated! SafeTrap gave me the option to reboot there but I followed the directions and installed SuperSU from the SD card. It was a quick install.
I restarted the phone! I was done!! Right?
My phone got stuck on the AT&T splash screen! I started to panic! What did I do wrong?!
I missed Sunderwear's step five:
5.Put your phone in download mode and flash the 4.4.2 stock boot.tar.md5 kernel and your phone will boot after a few minutes with root access enabled.
Click to expand...
Click to collapse
Goes to show you to read everything. I missed it due to the line break. I downloaded the boot.tar.md5 file and put the phone back into download mode and push it via PDA in Odin (I presume PDA. It wasn't explicit.)
After a few hours of chewing my nails and wondering if I bricked it:
http://imgur.com/a/UFg6u#F5qFTdq
So thanks to everyone! Now if I could only unbrick my Skyrocket!
Outstanding instructions! Thank you for this. I wish all the instructions were as clear and detailed as this is.
:good:
I tried like hell to flash my first Android (Samsung S2 Skyrocket) only to brick it. (FWIW, if you can tell me how to fix it, I'd be gracious! It buzzes once and then twice and repeats.)
Click to expand...
Click to collapse
do you mean it vibrates every 2 seconds and doesn't turn on?
:good:
Great instructions and great story. Sounds like what most people like me go through every time we try to do something like this.
jimmietilt said:
do you mean it vibrates every 2 seconds and doesn't turn on?
Click to expand...
Click to collapse
Yup. The last time I looked into this was almost two years ago. It just sits in my drawer now.
dajabec said:
Great instructions and great story. Sounds like what most people like me go through every time we try to do something like this.
Click to expand...
Click to collapse
I think what got me was all the new terminology and unfamiliarity of flashing. Jailbreaking an iPhone (which I've done before I had an Android) is pretty simple. It's pretty much point and click. But ROMs, flashing...these all have definitions which can be a bit overwhelming, even to a technical person such as myself. I've compiled Linux kernels from scratch!
But there's something about making your phone unusable. Something that I cannot live without, especially as I'm searching for a job.
It's nerve-wracking and I especially got nervous when I was putting KitKat on since it took so long. But overall, I'm glad I did it.
Mike, I wish everyone's instructions were like yours. I am in a similar boat as you, currently on 4.2.2 rooted and unable to do an OTA. I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Agent. said:
Mike, I wish everyone's instructions were like yours. I am in a similar boat as you, currently on 4.2.2 rooted and unable to do an OTA. I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Click to expand...
Click to collapse
Backup using Samsung kies and go find the 4.3 Odin package. Hell I just use the Google backup feature which is good enough for me.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
rdh28 said:
Backup using Samsung kies and go find the 4.3 Odin package. Hell I just use the Google backup feature which is good enough for me.
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Agent. said:
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Click to expand...
Click to collapse
Not sure but if you really want to upgrade it's worth the thirty minutes it takes to reconfigure
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Agent. said:
I don't want to go through all of the trouble of reconfiguring all of my settings, restoring all of my app specific stuff, and just getting everything back the way I had it. Does Kies backup every little thing or just app data and contacts etc?
Click to expand...
Click to collapse
Use Titanium Backup. Just make sure you don't restore system apps and you'll be fine.
rdh28 said:
Not sure but if you really want to upgrade it's worth the thirty minutes it takes to reconfigure
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I know, I will probably do it this summer, I'm just really busy right now and can't afford to risk anything happen to my phone
Devo7v said:
Use Titanium Backup. Just make sure you don't restore system apps and you'll be fine.
Click to expand...
Click to collapse
The system apps are one of the primary issues as that is what needs to be reconfigured, other apps can be backed up and restored easily.
Agent. said:
I am not really sure what to do as I do not want my phone to be wiped. Did you bring your phone to an ATT store or a Device Support Center? And when they flashed 4.3 did your phone lose anything?
Click to expand...
Click to collapse
I took mine to the AT&T device support center. I called before going in and they pretty much told me it was going to be destructive. I had previously wiped my phone earlier that day in the hopes that it would receive the OTA update.
I'm not going to lie: it's nerve-wracking, but straight forward. I know sometimes it helps to have someone hold your hand while you do it. And for me, it was definitely in the camp of, "What am I going to do if my phone craps out on me?"
But like what someone else said: you can back up your settings within Keis. I didn't. I just did a wipe. I backed up my photos but that's about it. Everything else was in the cloud. The one thing I should have done was transfer my Authenticator keys to another device because I couldn't log into AWS (which does not give out backup codes like Google). I did end up switching to Authy (I can't link to it since I'm such a new user but you can find it in the Play Store) which allows you to have more than one device. It shares your secret key between devices so it's technically less secure. But I needed the flexibility in case my phone crapped out on me again.
Pro Tip: to install all your apps again, go to the Google play store on your device and click "My Apps". Long hold one of the apps and then select the check boxes of the apps you want to install.
And hey if you run into anything there's plenty of people who check this forum regularly. I've managed to root 4.2.2 , 4.3, and 4.4.2 while retaining full functionality, just from this forum...the information is out there good luck!!
Sent from my SAMSUNG-SGH-I537 using XDA Premium 4 mobile app
Agent. said:
I know, I will probably do it this summer, I'm just really busy right now and can't afford to risk anything happen to my phone
The system apps are one of the primary issues as that is what needs to be reconfigured, other apps can be backed up and restored easily.
Click to expand...
Click to collapse
What system apps need to be reconfigured? I can't really see that many that it would take you more than 15 to 20 minutes.
Thank you guys, I need to get my phone serviced anyway as there is a yellow dot in the top left of the screen that won't go away. So if AT&T sends me a new phone I can do all of the dirty work and then transfer everything side by side from the old device. If they won't for whatever reason I will do what you guys suggested. So just to be clear I should follow the instructions to Odin to 4.3, root, then follow the upgrade/root instructions to 4.4.2?
Agent. said:
So just to be clear I should follow the instructions to Odin to 4.3, root, then follow the upgrade/root instructions to 4.4.2?
Click to expand...
Click to collapse
I personally thing this is better since if you have 4.4.2 already, you have to downgrade to 4.3, root it and then put 4.4.2 on it.
I made a few judgement errors while playing with my phone one day (vzn android 4.4 rooted) and ended up getting stuck in a situation where I had to RSD back to stock. I started over, but now I am getting hung up on attempting to root. I am hoping it is just something totally stupid I am missing so I can get it solved and be on my way.
I am currently sitting on a fresh install of 4.2.2 (post camera). I have re-downloaded RockMyMoto and unzipped it. Completely fresh file. Everything is a clean install. On the first time of running it, I get this message:
System is not write protected...
Executing step 3...
Click to expand...
Click to collapse
I am not sure what is happening or why it is happening, but I am hoping someone else knows.
I've tried wiping data and cache, tried RSDing a couple of times.
This happens both when I am following the tutorial JCase posted and when I am using the moto toolbox.
Thank you in advance.
http://forum.xda-developers.com/moto-x/development/tool-moto-x-toolkit-v1-4-0-t2477132
So easy a caveman
I used 1.3.4 and was piece of cake.. just follow instructions. I was on 4.4 and clicked root with slap, maybe some peeps here can help you as to where you need to start now since you already began a process
edit, when you get to the download page the real download button is in the red circle... don't know why stillthisguy stillusesthissitetohosthisfile.. you get spammed like crazy but the toolkit works well
le Fix
http://forum.xda-developers.com/showpost.php?p=53896831&postcount=5
Fadelight said:
I made a few judgement errors while playing with my phone one day (vzn android 4.4 rooted) and ended up getting stuck in a situation where I had to RSD back to stock. I started over, but now I am getting hung up on attempting to root. I am hoping it is just something totally stupid I am missing so I can get it solved and be on my way.
I am currently sitting on a fresh install of 4.2.2 (post camera). I have re-downloaded RockMyMoto and unzipped it. Completely fresh file. Everything is a clean install. On the first time of running it, I get this message:
I am not sure what is happening or why it is happening, but I am hoping someone else knows.
I've tried wiping data and cache, tried RSDing a couple of times.
This happens both when I am following the tutorial JCase posted and when I am using the moto toolbox.
Thank you in advance.
Click to expand...
Click to collapse
doitinthedirt said:
http://forum.xda-developers.com/moto-x/development/tool-moto-x-toolkit-v1-4-0-t2477132
So easy a caveman
I used 1.3.4 and was piece of cake.. just follow instructions. I was on 4.4 and clicked root with slap, maybe some peeps here can help you as to where you need to start now since you already began a process
edit, when you get to the download page the real download button is in the red circle... don't know why stillthisguy stillusesthissitetohosthisfile.. you get spammed like crazy but the toolkit works well
Click to expand...
Click to collapse
I tried the toolbox. I got the same error. Otherwise, yeah, that toolbox is awesome.
When I rooted my phone the first time, that toolbox hadn't yet been updated, so I did it all manually, but Ive rooted a couple of other phones using his tool. He is an awesome guy for releasing that tool, for sure.
erecker1 said:
http://forum.xda-developers.com/showpost.php?p=53896831&postcount=5
Click to expand...
Click to collapse
This looks like exactly what I need. Thank you very much! Ill give it a go later. In the meantime, it appears your search was far better than mine, so I'll just let this thread die. lol.
Thanks again, guys.
EDIT: worked awesomely. I cant thank you enough, erecker1.
Perfect, glad to hear that got you going! Yes, it's a shame that JCASE has closed his rockmymoto thread so this cannot be posted there, AND xda-developers says I don't have enough 'points' or 'cred' or whatever to post this fix directly to the Developers forum. So here I am, randomly replying to people with this fix I made. Looks like this time, xda-developers got the hero they need, not the hero they want. lol
Anyways, cheers mate, enjoy!
Fadelight said:
I tried the toolbox. I got the same error. Otherwise, yeah, that toolbox is awesome.
When I rooted my phone the first time, that toolbox hadn't yet been updated, so I did it all manually, but Ive rooted a couple of other phones using his tool. He is an awesome guy for releasing that tool, for sure.
This looks like exactly what I need. Thank you very much! Ill give it a go later. In the meantime, it appears your search was far better than mine, so I'll just let this thread die. lol.
Thanks again, guys.
EDIT: worked awesomely. I cant thank you enough, erecker1.
Click to expand...
Click to collapse