Database Users

help: trying to root via flashrec on g1

Hello there. trying to fast root with my G1
i have download latest versions of flashrec, but it says "Backup Failed, could not run command" on my g1 with 1.6 any ideas?
I am running T Mobile g1 with 1.6.

dont use flashrec. do it the old fashioned way. it takes all of 10 minutes.

i had to click directly to the left of the flash button (like at the end of the screen) for a asterisk to popup and even then it only worked after 50 tries.
fastboot flash recovery.img is prolli your best bet

thanks kusotare for answering me so quick. I will forget about flashrec. so i will take my g1 with with adb driver.
I am trying to install the latest Mod Cyanogen 5.0.7 test. but i need to now what is the first img or mod will choose after Alt-A . after the next step is to root user with recover an img from telnet. ( if i am wrong tell me i wont waste a precious time )
I know i need to spl to support the new mod, then to radio. than reboot.
thanks if you can leave me some comments.

themapleboy said:
i had to click directly to the left of the flash button (like at the end of the screen) for a asterisk to popup and even then it only worked after 50 tries.
fastboot flash recovery.img is prolli your best bet
Click to expand...
Click to collapse
oh didnt know about this option, which version have you used ?.

im not sure....... the one the cyanogen wiki told me to use
i'm still sticking by fastboot being the easiest solution if you can follow instructions

Un-rooting a rooted N1?

So I bought a N1 yesterday, cant wait till it gets here, The phone is rooted and has 2.2 on it, Is there anyway I can un root it and just be at the latest stock android? I just prefer to be at the normal stock updates, never really been big into rooting and ROMS etc unless I have too, anyway so yea thats my question and is it difficult?
Thanks in advance!

Take a look in the Development board, there is a sticky that shows you how to restore stock 2.1. Then it will prompt you to upgrade to Froyo.

solidkevin said:
So I bought a N1 yesterday, cant wait till it gets here, The phone is rooted and has 2.2 on it, Is there anyway I can un root it and just be at the latest stock android? I just prefer to be at the normal stock updates, never really been big into rooting and ROMS etc unless I have too, anyway so yea thats my question and is it difficult?
Thanks in advance!
Click to expand...
Click to collapse
Yeah, you can't re-lock the bootloader, but you can load up the stock ROM as the post above says. But since it's all already done, you might consider looking into a ROM which fits you. There are several which are "almost stock" but have nice enhancements, like the Enom rom.
I too am an unrooted stock ROM kinda guy, I don't have the time or patience to deal with fiddly stuff on my phone anymore, as I need to pull it out, see where my next meeting is, and get there. Not pull it out and realize it's in a Standby of Death or some other random problem. There are pluses and minuses to using a non-stock ROM, weigh them.. I'm starting to myself... I want a black notification bar and a handful of other small things, but to get them it requires a lot of work (unlock, flash new rom, set up all of my apps again, figure out new stuff in ROM, etc..)

Yeah you could also use modaco ROM. Those are stock ROMs with a few extras like super user access, which is a must have. Etc.

Is rooting similar or at least easy like the HD2? I had one of those and putting Custom ROMS was so simple!

Should be fairly simple if cyanogen is on it.
Sent from my Nexus One using XDA App at 35000 feet

uberamd said:
Take a look in the Development board, there is a sticky that shows you how to restore stock 2.1. Then it will prompt you to upgrade to Froyo.
Click to expand...
Click to collapse
Can you please link the thread, Ive looked and looked and I cant find a unrooting tutorial.

Nexus One Android Development -> Original Shipping - Tutotrial
The thread is stuck right at the top of the forum -_-

GldRush98 said:
Nexus One Android Development -> Original Shipping - Tutotrial
The thread is stuck right at the top of the forum -_-
Click to expand...
Click to collapse
WOW....I feel dumb....thanks lol

I am assuming you know how to use ADB and Fastboot
Hmm, Is there a thread explaining those 2 things?

solidkevin said:
I am assuming you know how to use ADB and Fastboot
Hmm, Is there a thread explaining those 2 things?
Click to expand...
Click to collapse
If all you want to do is flash stock rom, you don't even need to know what those two are. The stickied tutorials are dead simple.

Can somoene confirm Im gonna be doing this correctly.
Step 1. Disable backup my settings under privacy settings.
Step 2. unzip the original shipping ROM and put it somewhere you can find.
Step 3. Plug in Nexus One with USB to computer (enable usb and debug modes)
Step 4. adb reboot bootloader (which will boot into the bootloader)
Step 5. Confirm fastboot connection fastboot devices
Step 6*. fastboot erase userdata
Step 7*. fastboot erase cache
*If step 6 and 7 does not work, and if you have Amon_RA's recovery installed, you can do a factory data wipe from there.
Alternately, you can also do a factory data wipe within Android. Settings => Privacy Settings => Factory Data Reset.
Thanks to Brian and setzer715.
Step 8. Go to the directory that you stored your unzipped files.
Step 9. fastboot flash userdata userdata.img
Step 10. fastboot flash boot boot.img
Step 11. fastboot flash system system.img
Step 12. Skip to step 13 if you want to keep recovery (assuming you have a modified recovery such as Amon_RA's recovery). If not fastboot flash recovery recovery.img
Step 13. fastboot reboot
Step 14. After the system boots up and while setting up skip setting up with the google account and you can setup accounts later. This will prevent the phone from pulling down the previous settings (downloaded apps, wallpaper etc) from google.
Step 15. You are done. Enjoy.
Ok so I downloaded, installed and updated Android SDK, it seems to be all set, now when I follow those steps, I connect the phone first then for instance step 4 I should start "adb" then type in reboot bootloader, and for step 5 I should start up "fastboot" then type devices, etc etc? Is that correct?
thanks in advance.

Anyone? Please.

solidkevin said:
Anyone? Please.
Click to expand...
Click to collapse
look here to learn how to setup adb
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/

fender Splash Image Thanks to K'tag

credits to K'tag
http://forum.xda-developers.com/showpost.php?p=11205300&postcount=284
i tried to flash it and wow it worked but its a wrong dimension it has a black bar on both sides.. so i tried the other one you post.
but a little blury... so i did some adjustments and now its kinda more like the default splash... thanks bro....
newei
heres the file
http://www.mediafire.com/?urkjhzcugs0wex8
thank you so much bro

ardeldotcom said:
credits to K'tag
http://forum.xda-developers.com/showpost.php?p=11205300&postcount=284
i tried to flash it and wow it worked but its a wrong dimension it has a black bar on both sides.. so i tried the other one you post.
but a little blury... so i did some adjustments and now its kinda more like the default splash... thanks bro....
newei
heres the file
http://www.mediafire.com/?urkjhzcugs0wex8
thank you so much bro
Click to expand...
Click to collapse
how do i get this on my phone?

Nice work aldeldotcom!
Of course, before I saw this, I cleaned up the resized image a bit, so I may as well link to it.
http://www.mediafire.com/?ts7q2t2q7bovao1
I actually haven't gotten it onto my phone yet. I lost root with the OTA and haven't managed to get it back yet, (I haven't tried too hard either... yet) but it should look pretty good.
Of course, the REAL file would still be better...

"Fender" splash screen AND stock recovery
So I made it work.... I have this splash screen, root, AND stock recovery. (Ya know, in case I want more OTAs...)
Here's my story. And I'm stickin' to it.
You will need root. SuperOneClick worked for me. I did have to follow his instructions about toggling USB debugging on and off when it went into a loop. I also had a snag in that SuperUser.apk didn't actually load onto the phone, even though it was rooted. Apparently it's a lack of memory problem. There's a simple fix though; after rooting, copy the superuser.apk file from the SuperOneClick folder onto you SD card. Open it with ASTRO and install it like any other non-market app. You're good to go.
After getting root, here's what I did.
I flashed the 2010 SPL from the thread below by putting the zip on my sdcard and flashing it from Amon's recovery. There were some nervous moments, but it worked fine for me.
BE CAREFUL!!!! THIS IS WHERE YOU CAN BRICK YOUR PHONE. BE CAREFUL! (did I say to be careful?)
http://forum.xda-developers.com/showthread.php?t=794447
This is the link to the actual SPL I used: http://rapidshare.com/files/267475618/update.Engineering-SPL-HBOOT-1.33.2010-signed.zip
Next, I renamed the splash screen splash.rgb565 and put it in the same folder as my fastboot tool and followed the unlockrs instructions here:
http://theunlockr.com/2010/04/15/ho...for-all-320-x-480-resolution-android-devices/
Read their directions throughly, but here are the commands you need from fastboot:
fastboot flash splash1 splash.rgb565
fastboot reboot
Click to expand...
Click to collapse
And finally I reflashed the stock SPL through fastboot as instructed here:
http://forum.cyanogenmod.com/index.php?/topic/644-mytouch-12-tutorial/
This link: http://www.megaupload.com/?d=9Z7K1PAL
has the stock radio and SPL. I just put the SPL in the folder with fastboot and followed their instructions
AGAIN, BE CAREFUL!!! FLASHING SPLs CAN BE DANGEROUS.
PLEASE, read the instructions carefully and multiple times, but, here are the commands you'll need:
fastboot flash hboot hboot.nb0 (that's a zero at the end)
fastboot reboot-bootloader
Click to expand...
Click to collapse
Then I finally reflashed the stock recovery from a terminal emulator on the phone using DonJaun's instructions from here:
http://forum.xda-developers.com/showpost.php?p=11136815&postcount=266
The recovery file is here: http://forum.xda-developers.com/attachment.php?attachmentid=509115&d=1296862264
Here's his quote:
DonJuan692006 said:
Download the attached "Flash_image.zip", unzip the file, and put in on the root of your SD card. Then open up terminal on the phone and type the following hitting enter at the end of each line:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/*name of recovery*.img
reboot recovery
Click to expand...
Click to collapse
So that's where I'm at. As close to stock as I'm probably going to get, but still with root!
KT
BTW: I had the OTA on my phone before I did all this, but if I were still on 1.6, I would go in the same order and not try and apply the OTA first, if for no other reason than getting root on 1.6 is easy. Use UniversalAndRoot. Done. Then:
flash engineering SPL from recovery,
flash splash screen and original SPL from fastboot (in that order), and finally
flash stock recovery from terminal.
Then I would probably UNROOT before applying the OTA. I was unrooted when I got it, and I think I might be the only person not having trouble with it. Just my 2 cents..

I updated my post to include the actual flash_image command argument needed for my little guide.
As for applying the update. I would do it manually. You can download the update file from here, rename it to update.zip, put it on your SD card, and flash it from recovery. Before flashing it, make sure you do a "Wipe data/factory reset". For my myTouch 1.2 the update ran like crap, until I went it and did a wipe. It seems the update doesn't do a very good job of cleaning up the system cache before updating, which leads to ridiculous lag. A full wipe will help it run a million times better.

on the last part when you re-flash the stock hboot and recovery..
i flashed the hboot first according the guide then when i tried to flash the recovery it failed.. so i reflash the eng spl again then flash the stock recovery after that i re-reflashed the stock spl.. and it works... iam now left with "close to stock" fender??
about the stock recovery, is it the one when it onl shows you triangle with exclamation mark?

yes thats stock recovery. anywei
if you like you can do manual update if you want to update to froyo thats what i did.. after doing what i stated above.. now im on my stock froyo fender running smooth..
Sent from my T-Mobile myTouch 3G my fender using Tapatalk

ardeldotcom said:
yes thats stock recovery. anywei
if you like you can do manual update if you want to update to froyo thats what i did.. after doing what i stated above.. now im on my stock froyo fender running smooth..
Sent from my T-Mobile myTouch 3G my fender using Tapatalk
Click to expand...
Click to collapse
yes but i after that i put the update.zip in the MMC but it did not read it.

Just putting the word out...
There are people who have the original image who have visited the forum and are willing to donate their original Splash image if there is someone who can post direction on how to get it off the phone.

did you check if its update.zip ( no wrong spelling) and if your pc showing file extension because if not maybe you have it spelled as update.zip.zip...
Sent from my T-Mobile myTouch 3G using Tapatalk

i hope someone can post it on how to. but for now maybe you could try the splash imges we posted.. its almost close to the origial..
Sent from my T-Mobile myTouch 3G using Tapatalk

I'm fine, thanks.
I don't really need to change my splash screen. People are certainly welcome to use the one that's been synthesized. I'm just hoping for about as complete a restore for the Fender as we can get and that image would really seal the deal. Getting it off just seems to be the challenge.
Also working on a clean and usable 2.2.1 image in the event one should want to go there if they happen to release this rumoured fix or try it with an overclocked kernel. Hopefully we will see some targeted at the 1.2/Fender owners with some encouragement. Work so far impressed a T-Mobile rep who was a fan of the phone when I went in to pay for a data plan. It's getting pretty clean and snappy as is.

In the efforts of bringing this to a successful close I have created the following thread. http://forum.xda-developers.com/showthread.php?p=11341358
Seems the splash image and the entire original ROM can be fetched and reconstructed.

update stuck
so i did the whole process and i ended up with "stock" Fender Edition, i did a system update, it downloaded the update so i installed it but after it's done reseting it's just stuck at the splash screen, and now i cant boot to the system anymore...
help please?

Questions...
Can you boot your phone into Recovery, Fastboot/HBoot? Have you tried asking for help in the OTA thread? http://forum.xda-developers.com/showthread.php?t=906006 More super smart android people seem to be watching that one and may be able to help.

WoefulDerelict said:
Can you boot your phone into Recovery, Fastboot/HBoot? Have you tried asking for help in the OTA thread? http://forum.xda-developers.com/showthread.php?t=906006 More super smart android people seem to be watching that one and may be able to help.
Click to expand...
Click to collapse
i can boot into fast/h-boot and i am able to boot to the recovery screen(the one with the ! mark, and also the 2e)
but i cannot do anything, fastboot gets remote not allow, tried to flash the eng SPL is also failed

danxtian said:
i can boot into fast/h-boot and i am able to boot to the recovery screen(the one with the ! mark, and also the 2e)
but i cannot do anything, fastboot gets remote not allow, tried to flash the eng SPL is also failed
Click to expand...
Click to collapse
Going to have to goldcard root. There's a guide in my sig.
Sent from my LG-P500 using Tapatalk

DonJuan692006 said:
Going to have to goldcard root. There's a guide in my sig.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
but i can't access my phone to turn the USB debugging on, is there anyway to make the goldcard?

danxtian said:
but i can't access my phone to turn the USB debugging on, is there anyway to make the goldcard?
Click to expand...
Click to collapse
Use a friends phone that has Android on it.
Sent from my LG-P500 using Tapatalk

DonJuan692006 said:
Use a friends phone that has Android on it.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
hmm... will it work if i use HD2 running android on it?

[Q] Atrix Special "Brick" Problem with touchpad - reset

So, guys...here's a real challenge for all of you.
I taught my friend how to enable multitouch on Atrix 4G and I did mine correctly, but he tried editing the touchpad.cfg file using the Atrix, removed the READ permissions of file and restarted the phone. Obviously, the phone can't read the touchpad.cfg anymore and touchpad is not working at all.
Gladly (yeah, this is sarcasm), the Android won't let he do a factory reset because the Froyo version needs an extra step of TOUCHING the screen to complete the recovery command.
I tried accessing it via ADB too, but it requires you to TOUCH the screen and choose your USB connection type.
So, touch is out of question. Is there any way to access this cell phone and make the files readable again (or replace the files, whatever makes it working). The phone has USB Debugging enabled, if it helps.
p.s: sorry if it's been posted before, but I search the forum A LOT and could only find two similar posts that were unanswered. (Please, let's not make this one be the third. We don't need that.)

Have you tried fastboot? try turning off the phone and holding power + volume down until you see the word Fastboot then press volume up. You should be able to do whatever from adb now. Try that or an official update.
this should be in Q&A btw
Sent from my MB860 using XDA App

Hey, Tayshun, thanks for the reply
I tried using Fastboot, but the device still can't be found by ADB shell. If you can point me some direction of what I may be doing wrong it would be great.
And I don't really understand when you say "that or an official update". How was I suppose to update the phone without touching it at all? Via Recovery Menu too? What is the option?
Thanks in advance

chapter81 said:
Hey, Tayshun, thanks for the reply
I tried using Fastboot, but the device still can't be found by ADB shell. If you can point me some direction of what I may be doing wrong it would be great.
And I don't really understand when you say "that or an official update". How was I suppose to update the phone without touching it at all? Via Recovery Menu too? What is the option?
Thanks in advance
Click to expand...
Click to collapse
if you can't access ADB to push a file, and you can't get recovery to work to reflash a fruitcake, then you're only choice is to sbf flash a 2.3.4 gingerbread sbf. either that, or the pudding sbf if you wish to stay unlocked.
it will give you a fresh, stock state of the phone. if he is on Gingerbread though, you can ONLY flash those two sbf's, any others will hard brick your phone.
EDIT: I just thought of something, it's a long run but you might be able to fix permissions in Recovery mode, i don't know whether it'll work or not though.

Alcapone263 said:
if you can't access ADB to push a file, and you can't get recovery to work to reflash a fruitcake, then you're only choice is to sbf flash a 2.3.4 gingerbread sbf. either that, or the pudding sbf if you wish to stay unlocked.
it will give you a fresh, stock state of the phone. if he is on Gingerbread though, you can ONLY flash those two sbf's, any others will hard brick your phone.
Click to expand...
Click to collapse
Well, he's running Froyo 2.2, so I guess this option is not available for us to try. Even though because I'm not really sure I can go throught all these steps.
Alcapone263 said:
EDIT: I just thought of something, it's a long run but you might be able to fix permissions in Recovery mode, i don't know whether it'll work or not though.
Click to expand...
Click to collapse
Can you please explain me this idea of yours in more details? I think that all I need is to be able to communicate with the device without using touch. I read somewhere that using Fastboot, I could do anything via ABD, but even putting the phone on this mode, I still get "device not found" on ADB console. Maybe I'm missing some extra step. But again, if you could please explain me about this permission thing in Recovery Mode, it would be great, Alcapone. Thanks!!!

Flash a pudding 2.2 sbf

[Q] Fastboot Reason: Sticky bit factory_fastboot?

I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.

Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app

skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.

OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app

You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y

skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.

cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?

Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!

More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.

Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.

Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful

Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!

Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432

ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:

Edit : Sorry I asked stupid question!

Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.

Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!

cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick