Related
I have CWM 6.0.1.0 on my nexus 7. I was rooted but running the stock ROM. I wanted to flash CM10. I booted into recovery, wiped cache, dalvik, and factory reset. I then flashed the .zip file. When I rebooted the device it never got out of the CM boot screen. That circle just kept spinning. I tried the toolkit but the drivers aren't really working on my computer (crappy old XP laptop). I have formatted the system and SD card out of desperation which was honestly a stupid thing to do. So, where I am at now. I have no way to boot into android. Everything is wiped and formatted. Toolkit, adb, nor fastboot will work. I thought fastboot would save me but I can't get it work. Not even on my wife's mac. So what are my options? Please let me know if there is something important I am leaving out.
It can take a while to get a new rom up and running. How much time did you give CM to install before you interrupted it?
Visa Declined said:
It can take a while to get a new rom up and running. How much time did you give CM to install before you interrupted it?
Click to expand...
Click to collapse
I let it go for at least 30 minutes. I finally got adb to push a ROM to the device. Problem solved. Thanks though.
agroan05 said:
I let it go for at least 30 minutes. I finally got adb to push a ROM to the device. Problem solved. Thanks though.
Click to expand...
Click to collapse
maybe it was a bad download?
It can stand a spell to get a new rom up and jetting. How some instant did you utilize CM to install before you broken it?
redundant409 said:
maybe it was a bad download?
Click to expand...
Click to collapse
Thats possible. I tried re-flashing it numerous times but they all got stuck in boot. I am now up and running with SmoothROM. I might have to re-download CM10 sometime and try again.
Hey guys I now has a similar problem. I flashed a bad copy of my Rom and when it failed to boot I too wiped everything in desperation. I know I'm an idiot! Now I need to push both a Rom an kernal to my root directory but I'm not clear on how to install my kernal. Once I push my Rom I can use my recovery to install the Rom. But how do I install the kernel? I'm using cleanrom which comes zipped with the kernal. I can't fastboot flash it because I cannot turn on USB debugging. Gary
Sent from my HTC PH39100 using Xparent Red Tapatalk 2
kelnhofer said:
Hey guys I now has a similar problem. I flashed a bad copy of my Rom and when it failed to boot I too wiped everything in desperation. I know I'm an idiot! Now I need to push both a Rom an kernal to my root directory but I'm not clear on how to install my kernal. Once I push my Rom I can use my recovery to install the Rom. But how do I install the kernel? I'm using cleanrom which comes zipped with the kernal. I can't fastboot flash it because I cannot turn on USB debugging. Gary
Sent from my HTC PH39100 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
To use fastboot you don't need to have switched on USB debugging, it's sufficient to go to bootloader mode and connect your PC to it.
(If you have already installed the correct drivers on your PC.)
Sent from my Nexus 7 using xda app-developers app
Hey guys,
Regardless of my low post count, I'm not a noob when it comes to rooting\unlocking\flashing. With that being said, I've run into a few problems with my Nexus 4. I was making a nandroid backup of my most recent CM 10.1 nightly and decided to flash back to stock rooted in order to fix my bluetooth issues. When attempting to restore, I received an error stating that my MD5 sum didn't match. This happened to all but one of my backups and it would old restore part of my data before failing on the "working" backup. It would boot just fine, but it was basically a factory image and none of my downloaded applications restored execpt the icons. I realized that this image was pretty unstable so I took it one step further..... I decided to restore to factory stock by flashing the factory images from google (I snagged a copy before google pulled them). I ran the flash-all.bat and it restored everything with no issues.....but now it gets stuck on the nexus "X" during boot. I left it for about an hour and it's still on the "X". At this point, I decided to relock the bootloader and call google.
I realized that something is probably corrupt so I called Google and got an RMA but I won't get a new phone until LG makes more Nexus 4's (Nexi?, lol).
Does anyone have any ideas what could have happened? ANy ideas on how to fix this? I'd much rather fix this damn thing instead of going thru the RMA process.
Boot into stock recovery, clear cache and factory reset. You'll be up and running.
Sent from my Nexus 7 using xda premium
Maybe I'm more of a newb than I realize, lol.
How do I do that via stock rocovery? I just have the red triangle. I know how to do that in Team Win and CWM, but not in stock.
Boot into the bootloader by holding volume down and power.
Use the volume key to toggle to recovery and press power to select.
When you see the exclamation. Press volume up and power to open the recovery menu.
Then clear cache and factory reset.
Sent from my Nexus 7 using xda premium
El Daddy said:
Boot into the bootloader by holding volume down and power.
Use the volume key to toggle to recovery and press power to select.
When you see the exclamation. Press volume up and power to open the recovery menu.
Then clear cache and factory reset.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I went ahead and unlocked the bootloader again and flashed CWM touch in the meantime. I cleared cache and reset. Same result. It's just hanging on boot.
No you need to do this in the stock recovery.
Sent from my Nexus 7 using xda premium
El Daddy said:
No you need to do this in the stock recovery.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If I knew who you were......i'd kiss ya. Thanks man. It's fixed.
Now, just out of curiousity, why does that only work in stock recovery instead of a custom recovery?
Not entirely sure. The stock recovery wipe clears everything including data/media/
There also seems to be an issue with the bootloader not properly wiping the device. Hopefully they can fix the bug in a future update.
No kiss needed. Just a thanks and a virtual high five will do.
Sent from my Nexus 7 using xda premium
El Daddy said:
Not entirely sure. The stock recovery wipe clears everything including data/media/
There also seems to be an issue with the bootloader not properly wiping the device. Hopefully they can fix the bug in a future update.
No kiss needed. Just a thanks and a virtual high five will do.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I see what you mean about not wiping everything.....after all the wiping and flashing, it still had my same custom wallpaper from my CM 10.1 ROM when it booted. Weird.
Thanks again.
That's not because of something not getting wiped.
Its because your wallpaper syncs to Google. It's auto downloaded and applied when signing in for the first time.
Sent from my Nexus 7 using xda premium
I just used an automated program to root my phone. I was sick of running into websites on a daily basis that used flash, and hated every other browser out there so I rooted my Nexus 4 to get the stock browser from the Gnex. I am new at this though, and didn't realize rooting my phone could potentially interfere with OTA updates. How can I check to see if the automatic rooting tool I used kept the stock recovery, or changed it to a custom one?
This is exactly why I hate these toolkits...
Boot into recovery, check what it says. If it only shows you an android with a triangle, it's probably stock. If it's anything else (eg TWRP or Clockwork Recovery) then it's a custom.
You can be on Stock Rom with No Mods Unlocked Rooted with a Custom Recovery and you will get the ota update and it will install fine.
The ota update link will be posted here before you get on your device so it's good to have a custom recovery so you can just flash it. It will also protect you from losing root and your custom recovery
To check if you have a custom recovery with the phone off press and hold power and volume down then when in bootloader press volume down till you see recovery press power button if you get a android laying down that's stock recovery
Sent from my Nexus 4
ryfly65 said:
I just used an automated program to root my phone. I was sick of running into websites on a daily basis that used flash, and hated every other browser out there so I rooted my Nexus 4 to get the stock browser from the Gnex. I am new at this though, and didn't realize rooting my phone could potentially interfere with OTA updates. How can I check to see if the automatic rooting tool I used kept the stock recovery, or changed it to a custom one?
Click to expand...
Click to collapse
Rooting doesn't interfere with OTA updates. You are still able to update even with a custom recovery, and it actually makes things easier because you don't have to flash a custom recovery and then root after each update if you have a custom recovery. Custom recoveries offer many more options than regular as well.
For your original question, just power down your phone and turn it back on by holding both volume up and down while holding the power button. This will bring you to the bootloader. From there, navigate to recovery using the arrow keys and push power. If it's a custom recovery you'll know, and if it's stock, you'll just see an android.
It's recommended not to use automated programs to root because you don't learn anything, by the way, although it makes things much easier.
Sent from my Nexus 4 using xda app-developers app
^^^^^ that's what I said
Sent from my Nexus 4
spaceman860 said:
^^^^^ that's what I said
Sent from my Nexus 4
Click to expand...
Click to collapse
Haha, I thought I was the first reply
You need to hold volume up and down along with the power button to boot into the bootloader with this phone though
Sent from my Nexus 4 using xda app-developers app
hoponpop said:
Haha, I thought I was the first reply
You need to hold volume up and down along with the power button to boot into the bootloader with this phone though
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No you don't that's for galaxy nexus for the n4 its just the down button
Sent from my Nexus 4
spaceman860 said:
No you don't that's for galaxy nexus for the n4 its just the down button
Sent from my Nexus 4
Click to expand...
Click to collapse
You're right. My bad, lol
Sent from my Nexus 4 using xda app-developers app
I went into Recovery Mode and it is showing a dead Android with a red triangle. I'm not quite sure what that means.
ryfly65 said:
I went into Recovery Mode and it is showing a dead Android with a red triangle. I'm not quite sure what that means.
Click to expand...
Click to collapse
That's the stock recovery. You have to press volume up and power to see the menu.
El Daddy said:
That's the stock recovery. You have to press volume up and power to see the menu.
Click to expand...
Click to collapse
Do you mean when it shows the dead Android with the triangle? Or before that?
ryfly65 said:
Do you mean when it shows the dead Android with the triangle? Or before that?
Click to expand...
Click to collapse
When it is showing. You can't do much with stock recovery though. Wipe data, clear cache, adb sideload. That's about it.
El Daddy said:
When it is showing. You can't do much with stock recovery though. Wipe data, clear cache, adb sideload. That's about it.
Click to expand...
Click to collapse
Ah, okay gotcha. The reason I asked if I have stock is because I read an article that not having the stock recovery, or altering files in the /system folder may interfere with OTA updates if the checksum fails. I did change the browser in the /system folder though. I renamed two files to get the stock browser in there and working. I just hope that won't affect the OTAs.
ryfly65 said:
Ah, okay gotcha. The reason I asked if I have stock is because I read an article that not having the stock recovery, or altering files in the /system folder may interfere with OTA updates if the checksum fails. I did change the browser in the /system folder though. I renamed two files to get the stock browser in there and working. I just hope that won't affect the OTAs.
Click to expand...
Click to collapse
That will definitely affect OTA's. Anything modified in /system will abort the OTA. You can read more info in my OTA help-desk thread in my signature.
El Daddy said:
That will definitely affect OTA's. Anything modified in /system will abort the OTA. You can read more info in my OTA help-desk thread in my signature.
Click to expand...
Click to collapse
I am completely stock with stock recovery; unlocked, and rooted. The only two things I did was put browser.apk, and ChromeBookmarksSyncAdapter.apk into the /systems folder, and then I renamed BrowserProviderProxy.apk, and BrowserProviderProxy.odex. I just just put a "1" in front of both names. It was part of the instructions to install the stock browser from the Galaxy Nexus phone onto my Nexus 4.
In order to receive the update, would I just have to name those two apps back to their original name? Or would I also have to remove the apps I put in there as well?
ryfly65 said:
So I am completely stock with stock recovery, unlocked, and rooted. The only two things I did was put browser.apk, and ChromeBookmarksSyncAdapter.apk into the /systems folder, and then I renamed BrowserProviderProxy.apk, and BrowserProviderProxy.odex. I just just put a "1" in front of both names. It was part of the instructions to install the stock browser from the Galaxy Nexus phone onto my Nexus 4.
In order to receive the update, would I just have to name those two apps back to their original name? Or would I also have to remove the apps I put in there as well?
Click to expand...
Click to collapse
You should be OK just changing them back. Additions to /system are fine too. If it does end up falling you can just flash the system image with fastboot
Sent from my Nexus 10 using Tapatalk 4 Beta
Hey guys
I thought I'd just let you all know that my ambition to get 4.3 and lack of knowledge, led to my phone getting bricked today. I'm so devastated. I was following efrant's guide and flashed everything correctly and then as usual I lost half my storage and I followed the other guide to restoring the lost storage, once again i followed everything but i didn't get the storage back, then i did some cmd commands like the guide did. Next thing you know I may have done something wrong and I was at the bootloader screen and I couldn't reboot or go to recovery. Read and read nothing helped, called Google and they couldn't help me. I am now getting a replacement. SO there you go guys, just the greed of getting 4.3 caused me to brick my phone as well as my lack of knowledge I guess. Can't complain. Thought I'd share this with you all.
Div
P.S Moderators if this isn't suitable you guys can delete it no harsh feelings
Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta
Just flash the stock android image again, after all you have access to the bootloader, everything is fine
teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
fabrizziop said:
Just flash the stock android image again, after all you have access to the bootloader, everything is fine
Click to expand...
Click to collapse
This. You're totally not bricked.
Please follow the instructions in this thread:
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus⁴ using Tapatalk 4 Beta
Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?
Fataldesain said:
Hey don't feel bad we all learn the hard way at some point. 4.3 is a minor update not worth it.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
it's totally worth it
nqk said:
Yeah, Nexus is hard to brick.
What is the best way to brick the Nexus 4? Maybe trying to flash HTC bootloader on it?
Click to expand...
Click to collapse
Perhaps
Code:
# dd if=/dev/zero of=/dev/block/mmcblk0
Thats not greedy, your just too excited for 4.3
teambestyrandy said:
If you can still access bootlader just download the toolkit and download the 4.2.2 image and flash it back to stock via toolkit...
Click to expand...
Click to collapse
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....
Dvash27 said:
So I tried doing this but, in the command prompt window that opens up with the toolkit when unrooting and going to stock it says
Archive not found recovery.sig
Archive not found system.sig etc.
and it fails....
Click to expand...
Click to collapse
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.
miniAndroidian said:
In this particular situation i wont recommend you using a toolkit. Is much esier with a good guide if it fails with the toolkit (btw while i flashed 4.3 factory image the cmd told me also about "missing recovery and system.sig" but now ive got a fully working 4.3 ROM on my N4.
You can do it via ADB. You just setup ADB on your computer. And put all the files from the factory image in the "platform-tools" adb folder. If your phone is in the bootloader menu and its recognized by your computer you just run a file that is called "flash-all.bat" and it should flash the 4.2/4.3 image on your phone. Thats how i did it a few hours ago.
Have a look at this guide: http://forum.xda-developers.com/showthread.php?t=1907796
But remember all the files in this guide are for the Nexus 7 so use the N4 factory images and the proper commands for your device (i mean the last step of this guide which shows various commands. you shouldnt use them becuz they are for the N7 and the proper commands for the N4 are written in the "flash-all.sh" use those commands or use the "flash-all.bat" which is included in the 4.3 factory image [i dont know if its included in the 4.2. f.i.]. All those files have to be in the "platform-tools" folder in order to let the .batch file do its job.
I hope u understood what i wrote. If not let me know.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone
Dvash27 said:
THANK YOU SO MUCH!!! It WORKED! I realised that I didn't flash the zip, I was flashing the the individual images in the zip and that wasn't working. THANK YOU, I couldn't even sleep knowing I potentially bricked my phone
Click to expand...
Click to collapse
Glad to know that it helped you mate
What about content on phone
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta
TToivanen said:
Is your bootloader unlocked? Was your phone 100% stock before updating? How did you update? Can you reach bootloader by holding power and volume down button?
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
---------- Post added at 10:45 AM ---------- Previous post was at 09:46 AM ----------
leiftorem said:
My phone was stock, it is locked in all mathers I can reach the bootloader...
And I have ADB installed....
Click to expand...
Click to collapse
I can see my phone listet under "Advanced Utility, but I cannot seem to pull the files from my phone!
I am getting really frustrated here now!
Anyone??
leiftorem said:
I have also a phone that is dead after the upgrade. It was just "looping" on the "Updating Apps" screen, so I turned it off, now it won't start. When the "Nexus X" apperas, it just loops on this screen and nothing happens...
I would very much like to keep pictures and texts before resetting the phone! Can I do that in any way??
Click to expand...
Click to collapse
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.
Mr. Kostik said:
Flash ClockworkMod or TWRP and using one of them wipe cache, dalvik cache and data (not storage). Apps and settings will be gone, but your music and pictures will still be there.
Click to expand...
Click to collapse
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)
leiftorem said:
This sounds GREAT! Where can I download them! And, will my texts be gone?? (That is not the worst thing, still annoying...)
Click to expand...
Click to collapse
Oh well you should look in one of those threads on how to root and so on, flashing a recovery using a toolkit should also work. Texts will be gone.
Or from this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
Click to expand...
Click to collapse
But at some point you'd need a custom recovery anyway.
Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks
mgoldenberg said:
Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks
Click to expand...
Click to collapse
I am in the same predicament. I hope there is a way out
mgoldenberg said:
Hi everyone,
My phone cannot get into recovery and I need to factory reset. Is it possible to do this using fastboot from the console?
My phone keeps going back to the fastboot screen and this is what it says:
Invalid Flash Mode (S)
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
This comes up after I hold down the both volume buttons and the power button and try to load Recovery. I get the dead android with the red traingle.
If I start up normally I get the dead android with the red triangle again, and then it eventually goes back to fastboot, saying the reason is Flash Failure
Any help is gratefully appreciated
Thanks
Click to expand...
Click to collapse
when you get to Android Andy what happens when you hold volume down and tap volume up?
If you get in there I would wipe the cache partition as well... tho either of these may not help the issue... what were you doing prior to this happening? were you updating and get this upon its restart? Did it die and power up to this?... did it just randomly shut off and power up to this?
Sent from my XT907 using xda app-developers app
ezknives said:
when you get to Android Andy what happens when you hold volume down and tap volume up?
If you get in there I would wipe the cache partition as well... tho either of these may not help the issue... what were you doing prior to this happening? were you updating and get this upon its restart? Did it die and power up to this?... did it just randomly shut off and power up to this?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
When I got to android andy the android system recovery 3e menu popped up. I wiped the cache partition and did a factory reset, then rebooted but I'm still going in circles between the dead android and fastboot. Prior to this I had tried using safestrap to set up a recovery, but when I rebooted, I got stuck at fastboot. There was one point when I got to what I think was the fastboot menu and from there I tried flashing cyanogenmod, which I'm pretty sure was a mistake. Now I cant figure out how to get back to that menu.
mgoldenberg said:
When I got to android andy the android system recovery 3e menu popped up. I wiped the cache partition and did a factory reset, then rebooted but I'm still going in circles between the dead android and fastboot. Prior to this I had tried using safestrap to set up a recovery, but when I rebooted, I got stuck at fastboot. There was one point when I got to what I think was the fastboot menu and from there I tried flashing cyanogenmod, which I'm pretty sure was a mistake. Now I cant figure out how to get back to that menu.
Click to expand...
Click to collapse
OK...
First, what do you mean by "set up a recovery"?
I noticed your bootloader is locked. That means no custom recoveries can be flashed, so that's probably your problem.
If you tried to fastboot the Cyanogenmod zip (!?) that definitely didn't help.
What exactly are you trying to accomplish? Are you trying to reset to sell or return or something? Also, what system version did you have (or, if you don't know that, when did you get the phone and have you taken any OTA updates)? And were you previously rooted?
It sounds like you had a bad flash. Give me that info and I'll try to help you unbrick it...
Sent from my Nexus 7 using Tapatalk 4
From the fastboot details it looks like the most recent ota
mgoldenberg said:
10.9B(*) (sha-le9f557, 2013-05-24 14:49:34)
eMMC Info: Size 8GB
Click to expand...
Click to collapse
I say rsd the recent firmware....
Sent from my XT907 using xda app-developers app
sloosecannon said:
OK...
First, what do you mean by "set up a recovery"?
I noticed your bootloader is locked. That means no custom recoveries can be flashed, so that's probably your problem.
If you tried to fastboot the Cyanogenmod zip (!?) that definitely didn't help.
What exactly are you trying to accomplish? Are you trying to reset to sell or return or something? Also, what system version did you have (or, if you don't know that, when did you get the phone and have you taken any OTA updates)? And were you previously rooted?
It sounds like you had a bad flash. Give me that info and I'll try to help you unbrick it...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...
mgoldenberg said:
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...
Click to expand...
Click to collapse
Try this
I was stuck on the same screen all day
http://www.droidrzr.com/index.php/topic/28162-house-of-moto/
mgoldenberg said:
Yeah I'm still a noob at this, sorry. By set up a recovery I mean manually installing safestrap because clockworkmod doesn't support xt907, and I couldn't flash it manually from my computer, probably because of what you said about my bootloader being locked. Really all I want to do is get my old OS back, just the stock android that I got when I bought it. I had version 4.1.2 which I got from an OTA update, and I have not been previously rooted. Thanks for being patient with me by the way, I understand people like me probably make you want to rip your hair out...
Click to expand...
Click to collapse
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Oh ok, thanks for explaining. I'm not sure when I updated, but I know for sure it was OTA, so I can't downgrade. And do I need to unlock to fix this whole thing? Because for now I just want my phone back... I'm not exactly worried about flashing or rooting or anything.
mgoldenberg said:
Oh ok, thanks for explaining. I'm not sure when I updated, but I know for sure it was OTA, so I can't downgrade. And do I need to unlock to fix this whole thing? Because for now I just want my phone back... I'm not exactly worried about flashing or rooting or anything.
Click to expand...
Click to collapse
Did you try the link I provided? I was stuck on the same screen, took me all day to figure it out.
Sent from my XT907 using xda app-developers app
zombolt said:
Did you try the link I provided? I was stuck on the same screen, took me all day to figure it out.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
So this might be a stupid question... but which option do I choose after typing in my phone model? RSD, Fastboot [snapdragon] or moto-fastboot [omap]?
sloosecannon said:
Ah OK. That clarifies a lot.
So, I'll explain a few things here since you seem a little lost
1: safestrap is not the same as clockworkmod. It's based off of TWRP, but it's not technically even a custom recovery, just a bootstrap hijack.
2. Yeah, you can't flash safestrap. It's actually installed via an app, and you do need root to use it.
3. When did you update? If you did the latest OTA, you unfortunately can't downgrade... If you didn't, we can help you unlock the bootloader, then you can downgrade at will.
4. If you do unlock, you can install clockworkmod or any other recovery. If you can unlock, I strongly advise you do it.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Also, I tried unlocking my bootloader. I used this thing called motopocalype and it should have worked, but apparently it didn't Im sort of hesitant about running it again.
Here's the link: http://www.droidrzr.com/index.php/t...k-your-bootloader-atrix-hdrazr-hdrazr-m-only/
Did you get your phone back up?... if your on system version .3 or .78 you cannot unlock your boot loader build date 5/2013..
Sent from my XT907 using xda app-developers app
mgoldenberg said:
Also, I tried unlocking my bootloader. I used this thing called motopocalype and it should have worked, but apparently it didn't Im sort of hesitant about running it again.
Here's the link: http://www.droidrzr.com/index.php/t...k-your-bootloader-atrix-hdrazr-hdrazr-m-only/
Click to expand...
Click to collapse
If it didn't work, you're probably already updated. Looks like you can't unlock unfortunately
Sent from my XT907 using Tapatalk 4
mgoldenberg said:
So this might be a stupid question... but which option do I choose after typing in my phone model? RSD, Fastboot [snapdragon] or moto-fastboot [omap]?
Click to expand...
Click to collapse
Rsd. From that point you should be able to choose whether you want to erase everything or save it. Worked like a charm for me, took about 10min
Sent from my XT907 using xda app-developers app