Related
Okay, so I have used RSD Lite before with no problem. I need to flash my entire device back to stock before tomorrow, but the program is not reading my phone. Motorola Device Manager is installed, same setup I had last time I had to flash after soft bricking...I can't figure it out. Any help would be very appreciated. Thank you.
Moto Q stock with Arrrghhh's kernel v.0.10
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
No Go in Fastboot AP
huatz84 said:
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, totally know what to do, and what order to do it in, only RSD Lite will not acknowledge my device! Crazy, cause I just flashed stock image ASA 14 about 3 weeks ago, no problems.
Nevermind... hehe
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
Are you in Windows? I find Windows pretty annoying when it comes to certain drivers. You might have a look in Device Manager while your phone is plugged in(maybe check with the phone is fastboot mode too), and see if there are any Moto related drivers that have a yellow exclamation point. If so, perhaps reinstalling Device Manager will fix it? Good luck
yogi2010 said:
Nevermind... hehe
---------- Post added at 09:25 PM ---------- Previous post was at 09:10 PM ----------
Are you in Windows? I find Windows pretty annoying when it comes to certain drivers. You might have a look in Device Manager while your phone is plugged in(maybe check with the phone is fastboot mode too), and see if there are any Moto related drivers that have a yellow exclamation point. If so, perhaps reinstalling Device Manager will fix it? Good luck
Click to expand...
Click to collapse
Tried uninstalling and reinstalling Moto Device Manager 3 times...no. Tried RSD Lite versions 5.7 through 6.1...nothing. Is there an actual driver pack I can install that would have the appropriate drivers?
(I have a dual boot laptop, Ubuntu and Win 7, using Windows)
Moto Q stock with Arrrghhh's kernel v.0.10
galacticservant said:
Tried uninstalling and reinstalling Moto Device Manager 3 times...no. Tried RSD Lite versions 5.7 through 6.1...nothing. Is there an actual driver pack I can install that would have the appropriate drivers?
(I have a dual boot laptop, Ubuntu and Win 7, using Windows)
Moto Q stock with Arrrghhh's kernel v.0.10
Click to expand...
Click to collapse
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
yogi2010 said:
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
Click to expand...
Click to collapse
Yeah, I'm sure somehow that I will...thanks for the files, I'll try that now. Oh, by the way, you should check out the Dev Host site (google it), they provide free file uploading and sharing for, well, developers (or anyone for that matter). Only 500 MBs worth of storage is provided for free, but that really is all I need. Anyway, I'll try your advice and let ya know.
***by the way, I need drivers for 32 bit, not 64***
Moto Q stock with Arrrghhh's kernel v.0.10
yogi2010 said:
I do have a driver installer downloaded on my computer, but I don't know if it would help you. I will attach it here just in case.
I had this issue a month back, but Moto Device Manager ended up being the solution for me. I have RSD Lite 6.1.5, and it sill recognizes my device in fastboot mode.
edit: the site wouldn't let upload the files for some reason, so I used Dropbox. here is the driver installer I have, but i'm not sure, it might not have solved the issue for me. also, here is RSD Lite 6.1.5 in case you don't have it and wanna try it:
https://dl.dropboxusercontent.com/u/18474790/USB_Drivers_64_bit_4.6.5.zip
https://dl.dropboxusercontent.com/u/18474790/RSDLite6.1.5.zip
hope you get it working,,, i'm sure you will somehow..
Click to expand...
Click to collapse
No dice, RSD still not reading device...no freaking clue
galacticservant said:
No dice, RSD still not reading device...no freaking clue
Click to expand...
Click to collapse
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
yogi2010 said:
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
Click to expand...
Click to collapse
Yup, used moto-fastboot.exe to push files FZB fles to device. All was okay until trying to flash system.img.ext4. Had error message. My battery was okay though, but said there was problem with multiflash...any ideas
Sent from my SPH-M930 using xda app-developers app
Try another SD-Card, I had problems with my 32GB Samsung SD-Card.
Loader009 said:
Try another SD-Card, I had problems with my 32GB Samsung SD-Card.
Click to expand...
Click to collapse
RSD Lite will have a hard time reading device due to a SD card?
Sent from my SPH-M930 using xda app-developers app
Sorry, I was thinking about nandroid and TWRP, not of RSD Lite...
My mistake.
Entering AP Fastboot
huatz84 said:
Have you entered AP Fastboot mode? Hold both volume button and power. You'll see bootmenu. And navigate using volume down and select AP Fastboot using volume up.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
You can also hold power and the camera button to enter bootloader, then choose AP Fastboot (just saying for users who may not know).
Loader009 said:
Sorry, I was thinking about nandroid and TWRP, not of RSD Lite...
My mistake.
Click to expand...
Click to collapse
Yeah, I have no problem using TWRP or flashing stuff from Internal or External SD
yogi2010 said:
damn, that sucks! did you ever check Device Manager in the Control Panel. i remember seeing a missing Moto driver there, but then again, that led me on a driver search, which led me to Moto Device Manager. did you completely uninstall it first before reinstalling it?
i dunno, just throwing out ideas here lol. otherwise, you might be able to just fastboot flash the necessary components from the FXZ file to get your setup back to stock. or else use a stock TWRP backup, then reflash stock recovery. hope you get it
Click to expand...
Click to collapse
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
galacticservant said:
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
Click to expand...
Click to collapse
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
yogi2010 said:
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
Click to expand...
Click to collapse
I think the problem is with the cdrom...my phone keeps booting into AP fastboot automatically like I said...and I was never able to get RSD Lite to recognize my device, so I only used fastboot and TWRP. RSD Lite is sadly not an option for me at this point...
Oh, the image that I previously restored with RSD was odexed and purely stock, ASA 14-15 Sprint. Now it wont read in RSD...
Sent from my XT897 using xda app-developers app
yogi2010 said:
hmm ok, that's good you made some progress, not sure what's up there. which file did you restore with RSD? i tried restoring the asa14 one last night and got an error immediately, but i'm not sure if i edited the xml properly.
so what i ended up doing was restoring this one: http://forum.xda-developers.com/showpost.php?p=33942232&postcount=12. it will restore everything to the original factory firmware that came with the phone.... except for the system. but i had already restored the stock system with a TWRP backup posted by rangerbry, so it was ok. then i had to run the 2 OTA updates on the phone to get up to the most recent official release. it's a bit convoluted, but it's an option, hehe.
Click to expand...
Click to collapse
Something else that I totally overlooked...the red Motorola ripple boot animation doesn't even play anymore! It goes right to the sprint_bootanimation...something's not quite right in Moto Land!
Sent from my XT897 using xda app-developers app
galacticservant said:
Okay, now this is weird! I have my system back up and running, but I can only load it by starting the bootloader and choosing "normal startup"; otherwise my device boots into fastboot automatically every time I power down. Seems like I can't utilize stock recovery either when I flash it (otherwise I am using TWRP). My entire purpose behind unrooting and going back to stock was to update to JB as I participated in Moto's soak test. I am still stumped...?
System Up, Stock Recovery Down
Guess I'll try re-flashing the bootloader? or a version from a different/newer image?
Click to expand...
Click to collapse
Stock recovery still not functioning, but phone doesn't auto load fastboot anymore. Still can only load system from bootloader. But also TWRP doesn't disappear after reboot. I flashed cdrom, but is what is the extension? Is it a .img, or is it supposed to be? In details it just said "file".
Sent from my XT897 using xda app-developers app
So I took the Droid Maxx update, while I had PwnMyMoto installed. After the reboot I got a message that read "system update failed". However if I go into settings>about phone and check my version of the software, it's the same as the update.
Also there was a Google Play update for the camera app that was not available to me before the software update. Can anyone provide any insight into what might be going on?
Sent from my XT1080 using Tapatalk
blue26 said:
So I took the Droid Maxx update, while I had PwnMyMoto installed. After the reboot I got a message that read "system update failed". However if I go into settings>about phone and check my version of the software, it's the same as the update.
Also there was a Google Play update for the camera app that was not available to me before the software update. Can anyone provide any insight into what might be going on?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
I had the same issue, but now my phone is power cycling and I can't get it to stop. My fault for not unrooting, I know, but if anyone has insight on how to fix this, it'd be appreciated.
gamerman623 said:
I had the same issue, but now my phone is power cycling and I can't get it to stop. My fault for not unrooting, I know, but if anyone has insight on how to fix this, it'd be appreciated.
Click to expand...
Click to collapse
You may have to FXZ via means of HouseofMoto
It'll bring you back to stock though, but sometimes you can keep data
HouseofMoto
Kickbut101 said:
You may have to FXZ via means of HouseofMoto
It'll bring you back to stock though, but sometimes you can keep data
Click to expand...
Click to collapse
Thank you so much! Problem resolved! I used HouseofMoto and kept all my data. Worked like a charm. You're my hero.
Yeah I was working and it auto updated didn't give me an option and bam power cycles non stop, doing the House of Moto deal now, hopefully I can fix it. Rather annoying.
... And bootloops for all!
My wife and I have Maxxs. We both received the update overnight and, like dummies, went for it without unrooting. Now it's bootloop city for both of us.
Time to head on down to HouseofMoto for some help. D'oh!
---------- Post added at 05:24 AM ---------- Previous post was at 05:08 AM ----------
chewybang said:
My wife and I have Maxxs. We both received the update overnight and, like dummies, went for it without unrooting. Now it's bootloop city for both of us.
Time to head on down to HouseofMoto for some help. D'oh!
Click to expand...
Click to collapse
Can someone post the HouseofMoto files here or private msg me a link to them? I can't seem to register to HouseofMoto right now (already tried twice)
Thanks in advance!
What's the word on having root after the November update? Broken? Have to reinstall Pwn?
fat-fingered and Maxx-ed out.
Luckily I happened to glance down at my phone and see that it was downloading (I was driving home from work). I threw it into airplane mode, got home, and after some poking around on here, froze Updater and MotorolaOTA which stopped it (still shows "downloading" within the System Updates menu).
Now to wait a few days to see if there's an easy method to take the OTA, keep root while not somehow causing the death of small children or worse, me having to flash this thing completely and lose all my settings, etc.
TacticalFats said:
Luckily I happened to glance down at my phone and see that it was downloading (I was driving home from work). I threw it into airplane mode, got home, and after some poking around on here, froze Updater and MotorolaOTA which stopped it (still shows "downloading" within the System Updates menu).
Now to wait a few days to see if there's an easy method to take the OTA, keep root while not somehow causing the death of small children or worse, me having to flash this thing completely and lose all my settings, etc.
Click to expand...
Click to collapse
Your wait is over.
HouseofMoto will allow you to flash FXZ, keep settings and data and if you DL pwnmymoto BEFORE you accept the OTA, you can install it after the OTA. I haven't done the pwnmymoto trick but I hear it works and is easier than the rockmymoto process.
redddog said:
Your wait is over.
HouseofMoto will allow you to flash FXZ, keep settings and data and if you DL pwnmymoto BEFORE you accept the OTA, you can install it after the OTA. I haven't done the pwnmymoto trick but I hear it works and is easier than the rockmymoto process.
Click to expand...
Click to collapse
Thanks!
Reboot Cycle
Yeah, I ran into the same issue as I was rooted and accepted the OTA update which caused the reboot cycle. I didn't have Titanium Backup (like an idiot) but, through a number of reset cycles, I was able to download and install it in the 20 or so seconds I had before restart. I finally got back in and was able to disable/delete the OTA apk.
Hey guys, running a stock build on my Droid Ultra (Mini).
Performed this root method on my droid (http://forum.xda-developers.com/showthread.php?t=2442585)
Had become aware that an OTA update was underway so I unrooted (chose the unroot option in SuperSU ) and left it to charge on the QI charger.
Just woke up to find it constantly restarting and (of course what woke me up is the initial vibrate startup.) What's going on? And where did I go wrong .
Nickrick2641 said:
Hey guys, running a stock build on my Droid Ultra (Mini).
Performed this root method on my droid (http://forum.xda-developers.com/showthread.php?t=2442585)
Had become aware that an OTA update was underway so I unrooted (chose the unroot option in SuperSU ) and left it to charge on the QI charger.
Just woke up to find it constantly restarting and (of course what woke me up is the initial vibrate startup.) What's going on? And where did I go wrong .
Click to expand...
Click to collapse
It may have to do with using the unroot method you chose...you can return to stock using RSD Lite or I believe there is another method by the name of houseofmoto or something similar
Sent from my XT1080 using Tapatalk
ahjee said:
It may have to do with using the unroot method you chose...you can return to stock using RSD Lite or I believe there is another method by the name of houseofmoto or something similar
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
RSD Lite fails multiple times, to my disadvantage. But the weird thing is that it fully boots onto Android, and within 35 seconds the "shutting down" prompt comes up (the OTA update is trying I guess... ) But how can i cancel the OTA ? it just lets it boot up then shut down , but it hasn't damaged anything in terms of the OS itself or the boot sectors as far as I can tell.
Your phone is boot looping. It's easier to get help if you know the term.
Look at the houseofmoto thread. It will help you flash back to stock, but save your data and apps.
Samurai, the developer of the app, has been helping people stuck in a boot loop. The guy deserves a medal.
---------- Post added at 05:46 PM ---------- Previous post was at 05:43 PM ----------
Oops, forgot the link.
http://forum.xda-developers.com/showthread.php?t=2450702
Nickrick2641 said:
RSD Lite fails multiple times, to my disadvantage. But the weird thing is that it fully boots onto Android, and within 35 seconds the "shutting down" prompt comes up (the OTA update is trying I guess... ) But how can i cancel the OTA ? it just lets it boot up then shut down , but it hasn't damaged anything in terms of the OS itself or the boot sectors as far as I can tell.
Click to expand...
Click to collapse
if RSD Lite fails...it could be because you are not editing the xml file within the zip you download in order to restore the stock firmware.
You should use this site here http://sbf.droid-developers.org/obake/list.php and download the stock file. The first and third files are the two stock firmwares for the Ultra and the second for the Maxx. The first file is the original out of the box firmware and the third is the first OTA we received neither is the latest firmware.
Anyway, once you download the firmware of your choice you have to extract it and then find the xml file within, edit the xml file, you must remove the gevtar line within the xml, just delete the whole line of text that has the word gevtar in it, after that just save the file as is.
Now you can go to RSDLite, chose the edited XML file, boot your phone into fastboot and plug it in
At this point all should be ready and gucci, just hit start and the process will take care of the rest, once your phone reboots you will have stock unrooted firmware. You'll get an ota, accept it, reboot, you'll get the latest OTA, accept it. Then, if you want, you can reroot your phone and have some real fun again.
Hope that helps you, if not, try houseofmoto which i am unfamiliar with cause i use RSDLite all the time. (yeah i've used it alot cause i play around with my phone and i am not scared to experiment and honestly sometimes i feel after removing and editing a bunch of files it's best to restore to stock to get a fully stable and solid rom working.)
Fixed with HouseofMoto
ahjee said:
if RSD Lite fails...it could......
Click to expand...
Click to collapse
Fixed it with HouseofMoto, definitely worthwhile to have not returned it the day I got my replacement, now I can gladly send it, even though its working now :silly:
Nickrick2641 said:
Fixed it with HouseofMoto, definitely worthwhile to have not returned it the day I got my replacement, now I can gladly send it, even though its working now :silly:
Click to expand...
Click to collapse
glad its working...
Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.
ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).
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