Related
So, the only thing holding me back was voiding the warranty and the fact I have a rogers phone (build EPE54B).... so I think I have to flash the build to the one that matches the update?
Sooooo if anyone wants to point me in the safest, easiest direction... I would appreciate it... and dos and don't would be appreciated as well. I am new to the phone an android, so feel free to dumb it down.
Does the build actually mean anything? What happens once I change it... and official updates come out? I am going to cut the grass... and then root, so help me out (preferably someone that is on rogers and has done this)
thx in advance! Froyo or Brick, here I come!
had a long day with chores and family day.... but I am back at it, first tutorial down and it seems solid...
Uploaded with ImageShack.us
onward!
Let me know how you make out. I'm on Rogers as well and am debating rooting.
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Let me know how it goes for you.
I am on Rogers and experienced EXTREME instability the moment I flashed the Froyo radio. My phone would crash randomly and frequently.
I suspect it was a problem with my hardware and have returned the phone and am waiting for a new one.
Jack_R1 said:
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Click to expand...
Click to collapse
thx jack, I appreciate it.... sorry for the thread... but in my experience... it is easier having your hand held by someone experienced.... then assuming I am following the right one, lol.... so I follow that entire thread to go from rogers to whatever build I need? heh
I will try this in approx 2 hours.... when the yard work is done!
early quick question, when I go to "CyanogenMod"
it takes me to a thread, but I do not see the download, what am I not seeing? heh
I am at this part
Type: fastboot flash recovery recovery-RA-nexus-v1.7.0.img
it says cannot load image recovery? thx
well everything was working great up until this point, tried it 100 times, heh... so now I sit and wait for guidance? thx
Mr.Kakarot, have you put the .img in the same folder as fastboot? Or, alternatively, if fastboot is in your PATH, you won't have this problem.
i renamed the image to recovery.img and that seemed to work? I will continue after supper!
Jack_R1 said:
Just looking at the stickies in General section would save you from opening yet another thread on the subject
Follow this until rooted:
http://forum.xda-developers.com/showthread.php?t=636795
Follow the guide for rooted N1s from here:
http://forum.xda-developers.com/showthread.php?t=686326
Click to expand...
Click to collapse
followed that first thread to a T and it worked out... had 2 minor stalls but I got through it... I am doing this stuff off and on, thx for that thread... this is going to be a STUPID question I am sure... but following that first thread, what have I done? unlocked, rooted and installed google add ons? phone looks awesome, I will do the rest after supper!
hmmm, got it, lol
done, running 2.2.... so tomorrow at work, i guess I will see if I have any issues....
now that this is done, can I re install that sense ui? What should I do or try now that I have done those 2 tutorials? thx
first off there are no 2.2 froyo/sense roms available as of yet.. so if you want to use a desire rom youre more than likely going to want to downgrade to the latest 2.1 radio that works well with your carrier/area, as froyo has its own radio and needs it to run properly.. once you downgrade.. nandroid>wipe>flash
yea, I did not know it would put me back to 2.1, lol.... went back and then back again to 2.2, lol... sense sure looked good!
Any ideas, suggestions, tips for 2.2? I installed flash! thx
How stable is your phone with the Froyo radio? Any unexplained reboots yet?
well it was quite late by the time I did it, I was playing with it, went to a few flash websites.... and no reboots or shutdowns, I also just woke up.... so I will know today after a full day work/playing, thx
one of the bugs is my camera does not work for video... so I have to update the radio, any suggestions! thx
Nope thats pretty much what you need to do is update the radio
thanks, but I am not gonna lie... still not sure which are radios, roms, senses, lol.... could you point me to the one I need.... or does it matter? thx, I just do not want to brick, obviously!
Also, I did not do this step.... is this what I need to do, or is it unrelated?
11) You should still have root, but if you want BusyBox (or lost root somehow), Cyanogen has done it again! Go back into Recovery and flash froyo-rooter-signed.zip. Then Titanium Backup will work once again.
does not sound like something I need or use, so I did not do it....
as far as stability... my 3g signal looked low all day... but I never had a dropped call, instability or any reboots/crashes.... all is well! thx
go here:
http://forum.xda-developers.com/showpost.php?p=6734240&postcount=9532
havent had problems with the older one, but am going to try the new one just to see.
anyone around?
I tried these 3 things
Step_One_Froyo_Radio_Update.zip
step-two-RoDrIgUeZsTyLe-FroYo-MCR-R16-MOD-V1.8-FIX.zip
and then i ran
2.6.34_AVS-925mV_CFS_1113Mhz_061210.zip
anytime I run setcpu, I get this error
the application process com.mhuang.overclocking has stopped unexpectedly, please try again?
"uninstalled and reinstalled, worked. thx"
Hi All,
My droid stopped making and receiving calls, and 3g is usually out. Tried a bunch of different roms including going back to one I know it was always working with, so I don't think it's a software issue.
I also upgraded to basebane C_01.43.01P and that didn't help either. I found a thread on here about returning to stock for the milestone, but I couldn't find info on what I'd need to do so for a droid on verizon.
Any pointers would be great. Ideally, I'd like to do it on linux (as it's all I've got), but from what I've read it seems windows is required.
Cheers,
Alan.
its the same process for the droid as for the milestone. get the original sbf and flash it with RSDlite.
Thanks Daria. Where can I find the original sbf and the current stock rom? Google hasn't been my friend with the rom, I've not yet tried googling for the sbf.
Thanks,
Alan.
skyphyr said:
Thanks Daria. Where can I find the original sbf and the current stock rom? Google hasn't been my friend with the rom, I've not yet tried googling for the sbf.
Thanks,
Alan.
Click to expand...
Click to collapse
http://and-developers.com/sbf:droid
Sent from my Milestone using Tapatalk
Thanks An email to vzw got things fixed, so I haven't needed to downgrade yet, but I've got it ready to verify it's not a rom issue.
The page won't load for me... I'm trying to reach the Milestone archive. Is there any mirror available?
Thanks.
Nordiques said:
The page won't load for me... I'm trying to reach the Milestone archive. Is there any mirror available?
Thanks.
Click to expand...
Click to collapse
http://and-developers.com/sbf:milestone221
Looks like site is down ATM.
Sent from my Milestone using Tapatalk
Thanks, looks like I wasn't the only one. I ended up doing the update thru Motorola's updater...
And I now have a nice 599$ brick.
Fvck.
what happened?
What's your phone model?
A853 (Telus Canada).
It updated successfully, at the end of the process it asked me to unplug, reboot, replug.
So I unplugged it, and from now on... nothing. Power button doesn't do anything, and plugging it doesn't either.
If you are talking about Motorola software update, you don't need to manually reboot. It should reboot on its own. I don't know what went wrong there.
I dont have a telus sbf, but i have a SEA sbf. You can flash that and use OR to apply telus baseband to get your 3g working. Interested?
I never had to uplug it before, but it had been stuck on the Motorola logo for 25 minutes... a couple minutes is usual after an update, 25 isn't.
I'd like to be able to flash it, however now it just won't power up. Power button doesn't do anything, and same for plugging it.
(OP, sorry for the hijack, considering it's solved I hope you don't mind...)
Remove battery. Plugin phone to charger without battery. Does it show battery icon with ? in the middle?
No, nothing...
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv
Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.
Redownload?
Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?
I would redownload everything and try agian
littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?
I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.
Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.
i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721
I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!
i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.
How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).
i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop
Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.
re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used
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