Related
Hi people. thinking of unlocking, but afraid of brick. my tablet is funny.
every update that came through, never auto installed. Had to do it manually.
ALSO, voodoo never worked.
stock Rom, locked, jelly bean.
thinking of unlocking to regain root.
i miss it!
Thanks
redheadplantguy said:
Hi people. thinking of unlocking, but afraid of brick. my tablet is funny.
every update that came through, never auto installed. Had to do it manually.
ALSO, voodoo never worked.
stock Rom, locked, jelly bean.
thinking of unlocking to regain root.
i miss it!
Thanks
Click to expand...
Click to collapse
You don't need to unlock to get root back. Since your OS is iffy, I suggest to should do a clean flash and put everything back to normal.
Yes. i heard only way to root was to unlock JB was downgrade, then reroot. but, i don't know if voodoo would work after update. it's failed 3 times
redheadplantguy said:
Yes. i heard only way to root was to unlock JB was downgrade, then reroot. but, i don't know if voodoo would work after update. it's failed 3 times
Click to expand...
Click to collapse
I will make it work for you. Downgrade back to .30, re root, now here is the trick part, after you root, you should have superuser on your device, open up superuser(keep it open), then download rootcheck from the market to verify that you have root, now download superSU from the market, open it up, it will do the update.Now download Voodoo OTA root keeper, open it up and verify that all the boxes does have check mark to it except one, when you click save button the last box will be checked and now you have the option to "temp" unroot, click on this to save root. Go back to your notification, then click update to JB. Your device will shutdown and do the upgrade. Once it's done, open up OTA root keeper and click restore, bam you have root back.
Cool. how do i downgrade without unlocking
redheadplantguy said:
Cool. how do i downgrade without unlocking
Click to expand...
Click to collapse
Very simple:
Download .30 from Asus website, unzip it, now you have a zip file called EP201_768_SDUPDATE
Copy this to the root of your external sdcard, put it back to your device.
Turn off your tab. Hold down volumedown+powerbutton to get to stock recovery and once you see the white text displayed,let go both buttons, it automatic downgrade for you.
If you copy the file to the root of your internal sdcard then you just reboot and it will install for you.
thank you. gonna try this right now. I'll let you know in a bit.
buhohitr said:
Very simple:
Download .30 from Asus website, unzip it, now you have a zip file called EP201_768_SDUPDATE
Copy this to the root of your external sdcard, put it back to your device.
Turn off your tab. Hold down volumedown+powerbutton to get to stock recovery and once you see the white text displayed,let go both buttons, it automatic downgrade for you.
If you copy the file to the root of your internal sdcard then you just reboot and it will install for you.
Click to expand...
Click to collapse
Didn't work. Unzipped file was named something else, I renamed it to what you said. White letters came up, I let go, and there was 4 tiles on screen. One said rck, one Android, one USB, one wipe data.
Tried again with original filename. Downgrading now.
(hopeful)
redheadplantguy said:
Didn't work. Unzipped file was named something else, I renamed it to what you said. White letters came up, I let go, and there was 4 tiles on screen. One said rck, one Android, one USB, one wipe data.
Tried again with original filename. Downgrading now.
(hopeful)
Click to expand...
Click to collapse
Wait, when you download the zip from Asus web site the file name should be US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip right? and when you unziped it should be this EP201_768_SDUPDATE.zip? So what is the file name when you unziped?
buhohitr said:
Wait, when you download the zip from Asus web site the file name should be US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip right? and when you unziped it should be this EP201_768_SDUPDATE.zip? So what is the file name when you unziped?
Click to expand...
Click to collapse
Us_epad-user-.9.4.5.30
It downgraded wiped all data too. Rooted and getting ready to try your advice about updating. I never heard i had to temp unroot first. Good luck to me. I'll let you know
buhohitr said:
Wait, when you download the zip from Asus web site the file name should be US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip right? and when you unziped it should be this EP201_768_SDUPDATE.zip? So what is the file name when you unziped?
Click to expand...
Click to collapse
Crap. Lost root when updated back to jelly bean. Tried twice. Voodoo has no checkmark by protected copy available. Might take it to best buy. I have 2 year plan on it.
Tried a 3 rd time cause I thought manually updating many have been a problem, but "check for update" still shows none. Anytime firmware came through, never auto updated. They always failed.
Thinking of just returning it and have them get me another
redheadplantguy said:
Crap. Lost root when updated back to jelly bean. Tried twice. Voodoo has no checkmark by protected copy available. Might take it to best buy. I have 2 year plan on it.
Tried a 3 rd time cause I thought manually updating many have been a problem, but "check for update" still shows none. Anytime firmware came through, never auto updated. They always failed.
Thinking of just returning it and have them get me another
Click to expand...
Click to collapse
You only can do manual downgrade to .30, but you must do OTA update from .30 to JB to preserve root. If you manually upgraded, it will wipe everything before upgrade. After you finished manual upgrad with .30 and when the os came up, and you connect it to the internet it should automatically download JB to your device and prompt you to upgrade, this is not happening??
buhohitr said:
You only can do manual downgrade to .30, but you must do OTA update from .30 to JB to preserve root. If you manually upgraded, it will wipe everything before upgrade. After you finished manual upgrad with .30 and when the os came up, and you connect it to the internet it should automatically download JB to your device and prompt you to upgrade, this is not happening??
Click to expand...
Click to collapse
No. Every firmware, .26 .30 and JB, would download but fail installation. Now, I'm clicking " check for update" but it says none available
Rooted and back to ICS, but really miss JB too.
buhohitr said:
I will make it work for you. Downgrade back to .30, re root, now here is the trick part, after you root, you should have superuser on your device, open up superuser(keep it open), then download rootcheck from the market to verify that you have root, now download superSU from the market, open it up, it will do the update.Now download Voodoo OTA root keeper, open it up and verify that all the boxes does have check mark to it except one, when you click save button the last box will be checked and now you have the option to "temp" unroot, click on this to save root. Go back to your notification, then click update to JB. Your device will shutdown and do the upgrade. Once it's done, open up OTA root keeper and click restore, bam you have root back.
Click to expand...
Click to collapse
I wanted to thank you. The first tablet overheated and suffered a meltdown. This worked on the replacement.
Thanks a bunch. I have rooted JB now
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
go to the root of your external sd card and delete all the zip file(s), you probably left it there when you downgrade. Also delete file from internal sdcard in /cache/recover if any. Once you unlocked you shouldn't receive anymore OTA.
redheadplantguy said:
I finally got the nerve to unlock. I had to downgrade doing it.
Click to expand...
Click to collapse
Strange, many people said the unlock tool works fine on JB.
redheadplantguy said:
Now, I heard after unlocking, an ota will brick tablet.
Click to expand...
Click to collapse
Where?
I don't say it cannot brick your tablet, but I am not aware of any reports that it does.
redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
MartyHulskemper said:
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
Click to expand...
Click to collapse
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
redheadplantguy said:
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
Click to expand...
Click to collapse
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
buhohitr said:
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
Click to expand...
Click to collapse
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
redheadplantguy said:
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
Click to expand...
Click to collapse
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
buhohitr said:
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
Click to expand...
Click to collapse
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
redheadplantguy said:
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
Click to expand...
Click to collapse
That does sound like it actually flashed something (at least partly). I would run that unlock tool another time just to be sure I wouldn't get into trouble down the road (Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on. Flashing over stock, well... minor nuisance, but it would be majorly inconvenient to have to flash root and stuff all the time.)
MartyHulskemper said:
Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on.
Click to expand...
Click to collapse
No, it just doesn't work. The updater-script inside the OTA package compares the checksums of the system apps to be patched, and aborts as soon as one doesn't match the previous stock ROM.
The only potential danger I see is the communication with the bootloader which kernel to boot - the OTA downloader (DMClient) somehow has to instruct the bootloader to load the recovery kernel to install the dlpkgfile from /cache, and if that process is still not understood by custom recovery creators (there were some problems apparently, I don't know if they are solved), you might end up with a device that only boots into the recovery and not into Android.
Thanks. I will.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2
I bought my S3 used and it was already unlocked but from what I can tell still had the stock ROM (base version says it is I535VRLF2 but DEVICE STATUS says it is modified). When it powers up, I do not get a CWM or TWMP screen -- it goes directly to the normal startup so I am not sure what the previous owner loaded/did. I do not see any folders in the root folder (using ES FIle Explorer) for CWM and nothing in DATA/BACKUP (EDIT: just saw build number is VRALG7)...
Today I got a notice about an OTA upgrade (to HE) and got help on how to freeze it (as I did not want to lose root and all the customization I did to some files) but now I am wondering what changes were made from F2 to HE. I did find a post that talks about the HE upgrade.
Was F2 the previous OTA for the S3, or did my phone miss other OTAs? And if so, I am missing out on some important changes where I should let the OTA happen and then go and unlock the phone again? I read a number of threads about 'the new radio' which I assume is software to improve the phone or WIFI. Am I missing out?
Thanks
Frank
Michigan
I don't think you are missing out on anything to be honest. I did update mine and reroot without any issues, but can't really tell a difference. I would still do it so I can have the latest update on my phone since this one doesn't lock anything that we can't get back into.
Sent from my SCH-I535 using xda premium
There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.
sfobrien said:
There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.
Click to expand...
Click to collapse
Thanks for the reply. Will that break either my root or unlock (actually, I am not sure what state this phone is at since I did not do it -- I do find SuperSU in APPS, and have granted SuperUser to programs like Titanium Pro but there is nothing for CWM or other ROM managers...)?
Frank
If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.
sfobrien said:
If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.
Click to expand...
Click to collapse
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank
FMinMI said:
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank
Click to expand...
Click to collapse
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.
I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?
andimanium said:
I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?
Click to expand...
Click to collapse
The only way to get stock HE currently is OTA.
sfobrien said:
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.
Click to expand...
Click to collapse
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank
FMinMI said:
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank
Click to expand...
Click to collapse
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
Thanks forgot about GooManager.
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247
Click to expand...
Click to collapse
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank
prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank
FMinMI said:
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank
Click to expand...
Click to collapse
It is personal choice. I have not had any problems with it and have been running since device was released for pre-order. I run whatever recovery seems to be most stable for the device. CWM for Tbolt. Amon Ra for Rezound. And now TWRP for S3. Have seen more bricks and failed flashes contributed to CWM so I stick with TWRP.
help
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse
FMinMI said:
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank
Click to expand...
Click to collapse
The OTA installed with a custom recovery installed? Interesting. Usually OTA's fail if anything but stock recovery is installed. I only lost root but restored root with OTA Rootkeeper with stock recovery. Good to know that custom recovery can be installed and still get OTAs!
masonjb said:
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse
Boot loader is locked.
Click to expand...
Click to collapse
prdog1 said:
masonjb said:
Boot loader is locked.
Click to expand...
Click to collapse
OK, I used EZ Unlock 1.2 and it said "unlocked" is there a way to know for sure before flashing if it is unlocked?
Thanks!
Click to expand...
Click to collapse
Hi guys.
So I purchased 2 of the Droid Minis for my kids. They are both on 12.15.15 (camera update) 4.2.2 and started bugging them to take the update to 4.4
Before letting them take the update, I wanted to root them both so I could install tracking software on them, so I followed the thread here: http://forum.xda-developers.com/showthread.php?t=2509590
(for RockMyMoto)
PwnMyMoto never did anything but error, so I figured it was because of the camera update.
I successfully rooted BOTH XT1030 phones following the RockMyMoto OP, verified by installing SuperSU and double verified by installing TiBU from my license. Both phones are truly rooted as both asked me to grant or deny root access, and I've even checked via RootManager and it does indeed allow access.
So after following the link above and successfully rooting both phones, I started the 4.4 update on the first one and waited for it, but it just rebooted over and over, which made me stop in my tracks on the second phone.
Right now, the phone that was supposed to be taking the 4.4 update will boot all the way to a usable homescreen, but it reboots after about 20 seconds of having hit the homescreen. It's been doing this for about an hour now.
I've gotten enough time to get into Settings > About and check, and it's still on 4.2.2 (12.15.15), and even allows to check for updates before rebooting again (if I'm quick, I can even push the button to check for updates, but the device only lasts for 20 seconds before it automatically reboots.
I've tried booting into Recovery, but it just reboots into normal mode, lasts 20 seconds and reboots again.
I'm stuck, and would appreciate some help here. I'm not new to flashing, having been a crackflasher since the OG D1. Although, I have to say that these Droid Mini's are significantly harder to work with than my Note3, S4 and any of my previous phones...
help PLEASE?!
Obviously, my daughter has a bunch of games on her phone after having it since Christmas, and I'd definitely prefer not to lose her data. I had the foresight to make a TiBU backup before moving forward with the 4.4 update, but in it's current state of rebooting, it won't stay on long enough for me to copy the TiBU folder to my computer.
If I knew how to fastboot, perhaps I could fastboot the files for 4.2.2 back to the phone without losing her data - at least so I could transfer the TiBU folder over in case the phone has to be RSD'd back to stock...
If this is an option, please help me out with the exact commands that I might need. Thanks in advance!!
EDIT: I read how to fastboot (hadn't done it for a couple years) and found the correct files for the xt1030 here: http://sbf.droid-developers.org/phone.php?device=2
I downloaded and unzipped the 12.15.15 file.
I then used fastboot to push boot.img, motoimg.img, recovery.img successfully (although there is NO recovery no matter how I try to boot into it)
BUT, when I fastboot flash system.img, it comes up with several errors and fails, so I'm sure that the problem actually exists in the system image on the phone.
*** I DID NOT erase anything, only dirty flashed. I did this because I need to back up the user data before anything happens to it.
If I do erase system on the phone, will I lose her data? What about the other images that are still on the phone??
**EDIT: I found that I needed to use mfastboot instead of the standard fastboot to flash the system.img because it's apparently too big - mfastboot breaks it into smaller chunks and pushes them correctly, however, the phone still reboots.
This isn't considered a bootloop, it will boot all the way into the homescreen, stay active and live for around 20 seconds and then reboot.
I'm already going to be in trouble when she finds out she can't use her phone in the morning... PLEASE help a brother out!
Hope that info helps someone to help me better!
Unfortunately the Droid Mini and Max has yet to get their own device forums. So, I have moved the post to this forum in hopes some folks can help as the Ultra may share some characteristics as it's a relatively new device getting the 4.4 update as well.
MD
Moscow Desire said:
Unfortunately the Droid Mini and Max has yet to get their own device forums. So, I have moved the post to this forum in hopes some folks can help as the Ultra may share some characteristics as it's a relatively new device getting the 4.4 update as well.
MD
Click to expand...
Click to collapse
Thanks MD.
I just now figured it out on my own.
I hope that this thread will serve to help anyone that may stumble across a similar problem on their XT1030 device - perhaps even other Moto devices.
WHAT I FOUND:
While fastbooting and mfastbooting files to the phone, I realized that it wasn't working because I was missing something somewhere, so I opened the XML file in the original 12.15.15 zip and went through it line by line.
The one thing that I had neglected to do while in fastboot was to ERASE CACHE.
Once I had erased cache via fastboot (and obviously after pushing all the proper img files), it all worked correctly after reboot - the phone no longer reboots on it's own and immediately started the download of the OTA 4.4.
I hope that this post helps anyone else that happens across this problem.
Psychlone said:
Thanks MD.
I just now figured it out on my own.
I hope that this thread will serve to help anyone that may stumble across a similar problem on their XT1030 device - perhaps even other Moto devices.
WHAT I FOUND:
While fastbooting and mfastbooting files to the phone, I realized that it wasn't working because I was missing something somewhere, so I opened the XML file in the original 12.15.15 zip and went through it line by line.
The one thing that I had neglected to do while in fastboot was to ERASE CACHE.
Once I had erased cache via fastboot (and obviously after pushing all the proper img files), it all worked correctly after reboot - the phone no longer reboots on it's own and immediately started the download of the OTA 4.4.
I hope that this post helps anyone else that happens across this problem.
Click to expand...
Click to collapse
Glad you solved it. Yeah, cleaning cache is always a good thing.. Sure your daughters will be happy now!
You have to follow this guide here http://forum.xda-developers.com/showthread.php?t=2603358 to gain root after 4.4 Update.
Hatary said:
You have to follow this guide here http://forum.xda-developers.com/showthread.php?t=2603358 to gain root after 4.4 Update.
Click to expand...
Click to collapse
Incorrect. That will not work for his device.
Topsnake said:
Incorrect. That will not work for his device.
Click to expand...
Click to collapse
I have a Droid Mini too and followed this guide. Now i have a rooted Droid Mini with Kitkat.
If he is already on Kitkat, then you are right of course!He forgot to disable write-protection (http://forum.xda-developers.com/showthread.php?t=2551113) and flashing back to the camera update (12.5.5) and using SlapMyMoto (http://forum.xda-developers.com/showthread.php?t=2538896) before the Kitkat update.
Hatary said:
I have a Droid Mini too and followed this guide. Now i have a rooted Droid Mini with Kitkat.
Click to expand...
Click to collapse
I don't see how, seeing as we cannot downgrade from 4.4 to 4.2.2
Maxx'd out Kit Kat
Topsnake said:
I don't see how, seeing as we cannot downgrade from 4.4 to 4.2.2
Maxx'd out Kit Kat
Click to expand...
Click to collapse
Sorry i edited my post before! Of course it doesn't work when he updated already to 4.4
Hatary said:
Sorry i edited my post before! Of course it doesn't work when he updated already to 4.4
Click to expand...
Click to collapse
I see. At any rate, ive streamlined the process for our phones here
http://forum.xda-developers.com/showthread.php?t=2616104
Maxx'd out Kit Kat
Never take a ota update while rooted
Same thing happened to me but i learned the hard way that you should never take a OTA update while rooted because it screws things up and the phone is not stable enough to run Android OS without crashing and rebooting again. So what i did is i used RSD lite to reset to stock and after making sure root was gone i took the OTA update and now my DROID ultra is working fine . and FYI if you still want root when running KitKat use slapmymoto to keep root it requires you to have 4.2.2 already installed and then follow some steps so you can keep root in KitKat hope it helps!
What version of RSD Lite for XT1030?
droidusr2014 said:
Same thing happened to me but i learned the hard way that you should never take a OTA update while rooted because it screws things up and the phone is not stable enough to run Android OS without crashing and rebooting again. So what i did is i used RSD lite to reset to stock and after making sure root was gone i took the OTA update and now my DROID ultra is working fine . and FYI if you still want root when running KitKat use slapmymoto to keep root it requires you to have 4.2.2 already installed and then follow some steps so you can keep root in KitKat hope it helps!
Click to expand...
Click to collapse
What version of RSD Lite did you use? I've tried 5.6, 6.4, 6.5, with different USB cables including the one that comes with the phone but I cannot get RSD Lite to recognize my device. I tried fastboot as well but it keeps giving me an error about missing XML files when I try to flash.
MINI root
Hatary said:
I have a Droid Mini too and followed this guide. Now i have a rooted Droid Mini with Kitkat.
If he is already on Kitkat, then you are right of course!He forgot to disable write-protection (http://forum.xda-developers.com/showthread.php?t=2551113) and flashing back to the camera update (12.5.5) and using SlapMyMoto (http://forum.xda-developers.com/showthread.php?t=2538896) before the Kitkat update.
Click to expand...
Click to collapse
Hi, I have MINI with factory 4.4
How can I root it and have custom recovery ( TWRP )
I cannot find guide for XT1030...
THANKS
zsebob said:
Hi, I have MINI with factory 4.4
How can I root it and have custom recovery ( TWRP )
I cannot find guide for XT1030...
THANKS
Click to expand...
Click to collapse
you can't root 4.4. You are stuck until (hopefully) someone releases a root exploit for 4.4
---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------
mschwartz33 said:
What version of RSD Lite did you use? I've tried 5.6, 6.4, 6.5, with different USB cables including the one that comes with the phone but I cannot get RSD Lite to recognize my device. I tried fastboot as well but it keeps giving me an error about missing XML files when I try to flash.
Click to expand...
Click to collapse
can you post a screen shot/picture of the error you are getting and also the cmd window where you are entering the fastboot commands?
BladeRunner said:
you can't root 4.4. You are stuck until (hopefully) someone releases a root exploit for 4.4
---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------
can you post a screen shot/picture of the error you are getting and also the cmd window where you are entering the fastboot commands?
Click to expand...
Click to collapse
Thanks! The downgrade to JB and root and update to 4.4 not working on Mini?
zsebob said:
Thanks! The downgrade to JB and root and update to 4.4 not working on Mini?
Click to expand...
Click to collapse
downgrading isn't possible
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Andyw2100 said:
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Click to expand...
Click to collapse
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Andyw2100 said:
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Click to expand...
Click to collapse
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
berndblb said:
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
Click to expand...
Click to collapse
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Andyw2100 said:
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it. Though you should already have this on your computer or SD Card.
Edit: I believe there is an even easier way, just have never done it/tried it so I don't wanna lie and act like I know what to do.
The Stig 04 said:
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it.
Click to expand...
Click to collapse
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Thanks to both of you.
I don't believe I removed any bloatware, so I think the OTA update should work.
How do I flash the stock recovery in fastboot?
Again, many thanks!
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
berndblb said:
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Click to expand...
Click to collapse
Sorry I thought fastboot and ADB was kinda that same thing seeing as it was refereed to as "fastboot/adb directory"? If not my bad! Also this is the method I always use to take OTA's and have never ever had a problem.
Andyw2100 said:
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
Click to expand...
Click to collapse
Put the recovery image into the same folder with your fastboot.exe
Open a command prompt from that folder (shift + right click > open cmd window here)
check connection with
Code:
fastboot devices
if successful
Code:
fastboot flash recovery <name of recovery>.img
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
mumbles202 said:
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
No. You will lose root after the ota so it doesn't matter but you can always get it back as long as you are S-OFF by flashing a custom recovery like TWRP and then flashing SuperSu.
Well, I have run into a snag right off the bat.
While the command "ADB Devices" sees the phone, "Fastboot Devices" does not.
Any ideas as to how to rectify this?
Thanks!
I did some googling, and this problem I solved on my own.
I had to use adb to get into fastboot USB mode or something with adb reboot bootloader, and then fastboot devices worked.
I'm now continuing on.
Well, so much for this being easy.
I believe I successfully flashed my stock recovery.
But apparently I no longer have the OTA update ready to install, as at some point I tried to run it again just to get TWRP up, and now it's not showing as available. And when I try to check for updates in Settings/Software update/Check new I get an error message that says Download Unsuccessful. We were not able to download this update.
For now I guess I'll wait and see if Verizon tries to send me the update again, or if it works if I check for it myself some other time. (Or if anyone here has any suggestions.)
Also, I still seem to have root access. I thought that I wouldn't, since I believe I have replaced TWRP with the stock recovery.
I'm also now getting a constant error message about Google Play Services having stopped. And my wi-fi doesn't seem to be connecting properly.
I'm really wondering just what the heck I've done.
Well, for anyone still following my saga...
Things are somewhat better, but not totally resolved.
I kept checking, and eventually I was able to download the OTA update to 4.4.4. I did, I updated, and all went smoothly. I then was able to flash TWRP and then install Super SU and I have root access again. So on that front, all is well.
The problems that remain, though, are that I still am having issues with Google Play Services quitting and my Wi Fi not connecting. Could these things be related somehow? I've tried clearing the cache and then actually all data from Google Play services, but that has not helped. I have deleted my networks, and then tried reconnecting to them, but that also has not helped. It shows my networks in range as "saved" or "disabled" but won't connect to any of them.
Any ideas for me?
Thanks.
And thanks for the help in getting the 4.4.4 OTA update. At least that worked!
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Andyw2100 said:
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Click to expand...
Click to collapse
Not sure why I stopped receiving notifications from your thread. But at least you got your phone in working order! lol