Database Develop

Help Getting Back To Stock - Guides aren't working for me.

I need some help please. I seem to be in a pickle, though I’m not bricked. (At least, not yet.) So I rooted my phone last night, using [GUIDE][NOOB]Step-By-Step Instructions for New Stock Bionic Owners. Everything went great, and I got root. I followed the guide to get the .901 update, which went fine. Tried the ROM suggested, and liked it. Thought I would try Eclipse v2.1. I installed it, but I like Visual Voicemail, so I decided to use my Nandroid that I did right after root and revert back. Here is where problems started.
After the restore, it wouldn’t boot. Passed the Moto Dual Core logo and hung up. Allowed 10 minutes and after nothing, I flashed back to the backup I made after installing Eclipse. It booted fine. So I decided to go back to stock rom, debloat it how I like it and just run the debloated stock. Here is where problems started. I can’t find a flashable copy of the stock. Just a couple of guides on using RSD Lite. This is for Bricked Bionic’s, but I decided to try it, since one of the guides said it works to get back to OTA.
Downloaded the RSD Lite and the full system file to flash. I put my phone into the mode to flash (Power + Volume Down), unpacked the file with RSD Lite and tried to flash. Got an error.
Failed flashing process. Failed flashing process. 1/15 flash cdt.bin"cdt.bin"-> Phone returned FAIL.; phone connected.
Now, when I reboot my phone, it goes back to the Fasboot Flash Mode screen saing (Failed). I can boot into recover (Volume Up + Volume Down + Power) and do a Normal Boot, and it boots fine.
I tried a Factory Reset, and it just reset’s on Eclipse v2.1.
I want to simply get back to stock. Rooted or unrooted, I don’t care. I’ll reroot if I need to.
I also tried to download the STOCK Deodexed files. The links are dead. Figured if I went back to one of those stock images, I could unroot and see if everything was ok.
Suggestions?

Hmm..I think your mistake was in safeboot when you tried to go back to original back up you were suppose to toggle safe system so that it would be disabled. From there you would've been able to restore your original system and boot up just fine. It was mentioned in the guide through some posts.
Sent from my DROID BIONIC using Tapatalk

ms0chez said:
Hmm..I think your mistake was in safeboot when you tried to go back to original back up you were suppose to toggle safe system so that it would be disabled. From there you would've been able to restore your original system and boot up just fine. It was mentioned in the guide through some posts.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
So I need to turn Safe Mode off in SafeStrap and flash? I had thought about that, but I was worried about totally bricking the phone. I'm pulling SafeBoot now, and will try the flash.
EDIT...
SafeMode is off, and rebooted. I'm back to .875 Stock Rooted. So far, so good.
I can either flash from here (haven't tried yet) or stay here. When I boot, I'm still booting into Fastbook with (Flash Failure). Any way to get that off, other than flashing back to stock and locked through RSD Lite?

Your mistake was trying to restore from the un safe system. You can toggle safe system and you'll be ok. Or, reinstall a ROM to your safe system.

To clarify: don't flash a ROM with safe system disabled. toggle back to safe mode, and then pickup my directions from the format /system step. You can try another ROM no problem then.
I bet you can find the visual voicemail APK and add it whichever ROM. Copy paste into system/app directory.

Thanks. I'm used to flashing with the Thunderbolt and the XOOM. Not used to safestrap, just normal CWM.
Any idea how to stop the phone from booting into Fastboot? Having to do it the long way still. I'd be happy staying this way, if I can get that resolved.

Actually the problem was you tried to restore to a backup of a pre .901 system which has different radios which flashing doesn't like.
As for the flash failure, get the fxz files and put them in a folder with adb and fastboot. Then run this command in a prompt:
fastboot flash device_tree.bin
When you get a flash failure you just need to flash something to fix it; flashing device_tree.bin won't affect anything.

Its one solid file with a weird extension. Is there a way to unpack it? I am out right now and don't know the extension by heart.

Its a zip, just extract it
Sent from my DROID BIONIC using XDA App

Now, I'm scratching my head. (Again) I've worked with ADB with my Xoom, so I'm not a noob at that part. ADB doesn't see my phone. My computer does, and the phone know's it's plugged in. However when I try to flash the file, it can't find the device. I checked "adb devices" and it's not on the list.
So I decided to go ahead and flash completely back to stock with RSD Lite. Still get's the same error message. (I did check the MD5 SUM on the file. It's correct.) Safe Mode is off in Safestrap. Here is what the Fastboot screen looks like on my phone.
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Since I've not seen the Fastboot screen on this phone until this started, I don't know if the (S) has meaning. Like, it thinks the phone's still in SafeMode?
I noticed one of the options in safestrap is to disable safestrap. Thought about trying that, but.... Unsure.

stuck on boot loop after 4.1.2 update

update wouldnt install the stock way so decided to force it with odin first it just failed in odin on the last step, so i found the cf auto root method ran that and now i cant even get back to download mode help!!! thanks.
edit was able to get back into download mode figured out i was pressing the button the wrong way. anyway tried reflashing the 4.1.2 build i found and after flashing it says "fail" at the modem stage, so i restarted download mode and flashed the cf auto root again, it started to "update apps for 4.1.2" and kept rebooting itself where it left off, now when booting it said "starting apps" and just reboot again and now just keeps rebooting.
any help would be greatly appreciated.

Have you done a reset since flashing?
Sent from my GT-N8000 using Tapatalk HD

RavenY2K3 said:
Have you done a reset since flashing?
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
What kind of reset? (cant factory reset dont have a recovery to do that with) i've tried taking battery out and putting it back in and it just boot loops after installing the cf autoroot file. so i than tried flashing the 4.1.2 file and it fails again, like a vicious cycle. downloading the stock image now i just want the camera to boot again i shouldnt have bothered with the update lol.
edit: installed stock image get same fail message at modem part, so ran the cf autoroot again it than restarted and "upgraded" all the apps went all the way through this to to finishing boot and now is boot looping again!!!!!!!!!! errrrrr i should have never even bothered with all this.

don't you have at least a stock recovery?
holding zoom+ while turning on my galaxy camera boots it into a simple recovery mode.
4th option is "wipe data/factory reset"
the stock recovery doesn't have as much options as cwm or twrp, but it's enough for a reset.
for recovery or download mode you always have to power down your camera completely, if quick startup is enabled it goes into standby instead so you may have to pull the battery first.

dragonfly1113 said:
What kind of reset? (cant factory reset dont have a recovery to do that with) i've tried taking battery out and putting it back in and it just boot loops after installing the cf autoroot file. so i than tried flashing the 4.1.2 file and it fails again, like a vicious cycle. downloading the stock image now i just want the camera to boot again i shouldnt have bothered with the update lol.
edit: installed stock image get same fail message at modem part, so ran the cf autoroot again it than restarted and "upgraded" all the apps went all the way through this to to finishing boot and now is boot looping again!!!!!!!!!! errrrrr i should have never even bothered with all this.
Click to expand...
Click to collapse
See here for details on how to enter recovery.
http://forum.xda-developers.com/showthread.php?t=2080675
Sent from my GT-N8000 using Tapatalk HD

RavenY2K3 said:
See here for details on how to enter recovery.
http://forum.xda-developers.com/showthread.php?t=2080675
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
Thanks so much worked at least it boots now i think ill just stick with 4.1.1 and a working device thanks for all your help.

Moto X bricked after OTA UPDATE HELP

My moto x got bricked after OTA update
it had root with pwnmymoto and xposedframeowrk
now reboots after 15 seconds, and i can't even turn it off
what can i do guys?
already installed root and apps, yet i can't fix it
help me please

fellhound said:
My moto x got bricked after OTA update
it had root with pwnmymoto and xposedframeowrk
now reboots after 15 seconds, and i can't even turn it off
what can i do guys?
already installed root and apps, yet i can't fix it
help me please
Click to expand...
Click to collapse
Fastboot erase cache

shane1 said:
Fastboot erase cache
Click to expand...
Click to collapse
i tried to install stock but i can't with "adb reboot fastloader" beacuse it restarts every 10-20 seconds"
and according to http://forum.xda-developers.com/showthread.php?t=2444957
We have two (ok more but were not going into that) boot modes. First is normal, which boots regular Android, and in this case boots with system write protected. Second is recovery mode, normally it boots recovery without write protection. Our exploit will hijack recovery bootmode and boot Android without write protection.
After running this exploit, if you boot normally /system will be write protected. If you boot to "recovery", Android will boot without write protection. If you wish to edit system, you must boot into "recovery" to do so, any changes made will stick and will work in either bootmode. My suggestion is to make your changes in "recovery" and run the device day to day in normal mode, until we are certain "recovery" mode will be 100% stable for day to day use.
there is not a single drop of help with fastloader
edit: i managed to enable usb depuration by clicking several times on status/kernel version
i can run the command now, moto x responds and just Fast reboot, does not enter into fastloader
reached a dead end, now im desperated

Just put you phone into fast boot mode, power and volume down, open adb, connect your phone and type in fastboot erase cache as stated in the second post. Your phone is not bricked but its trying to flash the ota automatically. You've rooted with jcases method and that installs a custom recovery which is not recognized by the ota, you need stock recovery for it to flash.
Sent on my Moto X

flashallthetime said:
Just put you phone into fast boot mode, power and volume down, open adb, connect your phone and type in fastboot erase cache as stated in the second post. Your phone is not bricked but its trying to flash the ota automatically. You've rooted with jcases method and that installs a custom recovery which is not recognized by the ota, you need stock recovery for it to flash.
Sent on my Moto X
Click to expand...
Click to collapse
wow, finally, i was dying, now it does not reset itself.
How can i know if i have custom recovery? i though it was the normal one, wasn't aware pwnmymoto install custom recovery..
should i install stock rom anyways?
now i am downloading OTA again, now that i don't have root and pwnmymoto installed maybe it will work
will report results in 5 minutes
Thanks for the help guise
EDIT: lel no, after redownloading OTA update, it's still halfbricking with reboots.
I have recovered it again cleaning cache, but i wish to get OTA
Any ideas?
P.D all this trouble just to put 2 files into /system/ to enable Playstation mobile geez ;_;

fellhound said:
bump
Click to expand...
Click to collapse
I specifically know very little about pwnmymoto root method, my boot loader is unlocked, so I rooted the old fashion way. I know pwnmymoto hijacks the stick recovery. You may want to rsdlite back to stock, I believe there's a fxz with the latest update and root with jcases new method. Unless someone with more experience with pwnmymoto replies
Sent on my Moto X

You need to either flash the stock recovery and system through fastboot, or just RSD the whole thing (which deletes all your data). That's the only way you'll get it to accept the OTA update. Without the stock recovery, it will keep boot looping when you try to install the OTA.

Yes. Restore to stock. Threads galore. Once you boot you'll get an OTA prompt that'll work no problem.
Sent from my XT1060 using Tapatalk

http://forum.xda-developers.com/moto-x/general/moto-x-unbrick-ota-update-loader-v30-t3153725

[Q] Sprint OTA 4.4 on rooted (locked) 4.2.2 - Now reboots every 30 secs

So I had a rooted Sprint 4.2.2 (not unlocked, just rooted) and I got the OTA alert.
I accidentally installed it and it failed and now when it restarts, it gets to android for about 30 secs and then does the "powering off" bit and restarts... over and over.
In that 30 secs I can get to the settings and see that the version is still 4.2.2 so it didn't take. But it almost seems like it in stuck in that mode where it thinks it is doing the upgrade.
I tried killing memory resident stuff to prevent the restart to no avail.
I cannot get into any kind of stock recovery, it just reboots to normal mode
My only option is to go into Bootloader which does work.
But when I try to use RSD Lite and flash back to that last stock image, it shows
Failed flashing process 2/17 flash partition "gpt.bin"
I read that this may be due to the phone not allowing me to downgrade to a version lower than I currently have? Also read it could be the battery needs to be charged more.
Thoughts?

Can you get to the factory reset in that thirty seconds?
Sent from my XT1056 using xda app-developers app

If you can get to boot loader, will it go into recovery? If so, try restoring a backup. Likely you will have to do THIS, and I recommend doing this, the ota, then reroot.
Edit: if it boots to ROM for 30sec, try wiping cache and dalvik, then fix permissions, then reboot.

Ok so after reading around and doing some of my own playing around, I figured out how to fix it with some ideas from this thread
First off, the moto x rooting process actually REMOVES the recovery.img file from your phone, so what seems to be happening is that the upgrade downloads and starts to install... it attempts to load the recovery to flash the image, but since it doesn't exist, it just restarts the phone. When the phone restarts, the upgrade process still thinks it needs to run the upgrade, so it powers down.. this is where it gets stuck in the loop.
The solution is actually simple. Get into Bootloader mode (Power + Vol Down) which was slightly tricky since the phone always rebooted and never actually powered down. So I had to catch it at the end of the power off cycle, before it restarted. Once I was in bootloader mode I could use the following command:
Code:
fastboot erase cache
That seems to remove the downloaded update files as the phone stopped rebooting over and over.
But now I get Mobile IP Registration Error 67 (MIP) which basically means my registration data got wiped.. not sure I understand why that would happen.. but it basically means I need my MSL and have to enter the code to reset registration which will force a wipe of all data. At least I have the opportunity to back everything up over wifi now that I've stopped the looping.
The second part of this fix I haven't tried, but based on an educated guess, to actually GET the update correctly, I would need to flash the stock recovery image back using:
Code:
fastboot flash recovery recovery.img
where the recovery.img file comes from the zip file for the moto x stock image from the sbf repo:
http://sbf.droid-developers.org/phone.php?device=0
That of course needs to be done before I call Sprint to get my MSL and perform the reset.
All in all, a minor setback overall... better than a paperweight Perhaps instead of doing the erase cache step and just flashing recovery may have saved my MIP data
---- EDIT-----
Ah, gokart2, I see you had a similar process. Cheers

Turns out the Mobile 67 error was because my friend changed her service back to her old phone.... I should add that this wasn't my phone by my friend's phone.

[Q] Stuck in bootloop after attempted upgrade

I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.

jggrnaut said:
I just recently got my TF701T. I unlocked the boot loader with the Asus unlock tool and then attempted to upgrade to version 11.4.1.17 so that I could install Cromi-X 7 on it. I placed the file UL-K00C-US-11.4.1.17-user.zip on the root of the tablet and rebooted. Once the OS booted back up I was alerted that an update file had been found and I clicked it to begin installing.
The tablet rebooted and appeared to be upgrading but now all I see is a robot on his back with a red exclamation point. After a while the tablet will reboot and again show the Asus splash screen and then the upgrading robot then immediately go to the robot on its back.
I can get to fastboot by pressing power and volume down. I see "the device is unlocked" at the top of the Asus splash screen then I see a screen with the following. Android macallan-user bootloader (1.00 e) released by "US_epad-10.14.1.47-20131022" Choosing RCK, Android or Wipe Data do nothing to help the situation.
I thought I had found a solution in this thread http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1 but the link for drgravy's recovery.img is not working.
I would appreciate any help recovering this tablet. Thank you.
Click to expand...
Click to collapse
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....

berndblb said:
Do you have the Asus drivers and adb/fastboot installed on your PC?
If you have fastboot access, it would be as easy as:
Download CWM 6.0.4.7 from here http://droidbasement.com/db-blog/?p=3207
I know it says you have to be on 10.26.1.18 for this, but since you will use it only to flash the latest bootloader, you should be fine.
Put the recovery.img into your fastboot folder and flash it (if you need help here, let me know).
Then fastboot reboot
Your tablet should boot up normally now
Part 2:
Head here http://forum.xda-developers.com/transformer-tf701/development/rom-nov-24-t2951032 and grab the 11.4.1.27 bootloader/CWM 6.0.5.1 package
Flash it in your existing CWM
Reboot
Part 3:
Boot to recovery
Make a nandroid of your stock rom
Go back to home
Wipe data, cache and Dalvik
Flash the rom (which you have loaded onto your microSD)
All done.
Don't forget to delete the (probably corrupted) firmware file
EDIT: BTW, when you reboot to system from CWM you will always get the question if you want to fix root. Choose NO - it's a bug....
Click to expand...
Click to collapse
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?

jggrnaut said:
Thanks for the reply. I do have the drivers and adb/fastboot setup on PC.
After I could not find anywhere to download the version of CWM that was supposed to be for my firmware version I was afraid to proceed.
When I get home I will try the steps you have listed above and report back how it turned out.
One question, In part one after I flash recovery CWM 6.0.4.7 do I reboot to recovery or let the tablet reboot to the OS?
Click to expand...
Click to collapse
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.

berndblb said:
Shouldn't matter. When you flash recovery or bootloader, you flash it to the staging partition. The actual installation happens during the next boot - you'll see a brief blue progress bar under the Asus logo.
Booting a recovery for the first time I always reboot to system after the flash, then power down and enter the new recovery from the bootloader. Probably booting straight to recovery or bootloader is ok, but I have not tested it.
Click to expand...
Click to collapse
Well it has gotten worse and I think I have lost fastboot now. I downloaded the CWM from part 1 above and flashed it in fastboot. I typed fastboot reboot and now I am stuck in a bootloop still. It says "The device is unlocked" at top of Asus splash screen for about 15 seconds, screen turns black and the goes back to Asus splash screen.
I tried holding power and volume key to get back to fastboot but no luck. Any ideas?

Wow! You are really having some bad luck there!!
First the failed firmware update and now this.... Please post the commands you used to flash CWM.
I have no explanantion for this since you did not even boot into CWM.......
Unless..... the bad firmware flash left a command behind calling the stock recovery to do something (which in your case did not work anyway since it just looped) and now the bootloader tries to execute the command which is not "understood" by CWM. But that still does not explain why you cannot boot into the BL anymore......
Can you turn it off by long pressing power? Try every which way to get into fastboot. Without it there is not much you can do I'm afraid.
Try the restart pin hole (I believe it's on the left side of the tablet near the top) in conjunction with Volume Down, try leaving it alone for a while, try timing the button press somewhat differently - anything to get you into the BL again...
I feel very sorry for you, mate!!

Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.

jggrnaut said:
Thanks for helping even if it didnt turn out great.
I typed fastboot flash recovery recovery.img after I had downloaded 6.0.4.5 and put it in my fastboot folder. I got confirmation that it transferred successfully.
Then fastboot reboot The tablet rebooted but still would not boot into OS. It still boot looped but did not show the dead android icon anymore.
I got back into fastboot and selected RCK but it would not boot into recovery. Finally I got back into fastboot and selected wipe data and that is what got me to current situation. Now the only thing I get is when I long press power and volume up my PC picks up an unknown device that says apx.
Click to expand...
Click to collapse
I don't know what happened before - maybe you were doomed since the bad firmware flash - but that last step sealed the coffin.
Using Wipe Data from the bootloader with a custom recovery installed is asking for trouble. Never ever do that.... Sorry, it's a brick. [emoji24]