Database Develop

Need help going back to stock

I have a bionic that i system updated to 5.9.902 a couple days after i got it. Then i made the mistake of coming here and messing up my phone because i have no idea what I'm doing
I installed safestrap and did the whole noob step by step guide. Installed eclipse and a couple other roms. For some reason i wiped my internal and external storage. I have no backups of anything.
I've tried releasedroot, petes, rds lite with the 902 xml. I got stuck all the time with what seemed to be a driver issue.
I just want to return this thing to stock and stop messing with it
As of now when I press power i go straight to ap fast boot flash failure screen. I press power to power off and hold vol up and down to boot into recovery but just pick the normal boot option. Phone then boots into what seems to be my stock 902. I dont know if im rooted anymore.
If i could rid my phone of this flash failure and safestrap, i would be stupid happy
Anyone out there willing to help a total noob? If any more info is needed I'd be happy to provide
Sent from my DROID BIONIC using XDA

What error did you receive using rsdlite?
When you go into your phone settings..can you verify your on 902?

I'm at work now but it was some sort of usb failure. It got stuck on 1/22 mbm something.
Yes as of right now im on 902.
Is there a tutorial on how to completely remove usb drivers? Even though rsdlite says I'm connected, I don't see my phone drivers in device manager. That's where I think I'm going wrong but not really sure.
Sent from my DROID BIONIC using XDA

Cool. I'm at work too. When would you be available?

About 5pm est ... thanks alot dude
Sent from my DROID BIONIC using XDA

Send me a PM when your available.

I tried to pm you but xda force closed. I replied to, i believe, your hotmail
Sent from my DROID BIONIC using XDA

[Q] Bricked?

I was attempting to work through applying the .218 update to my droid 4. It was giving me a system validation error while when it was running in recovery. I found a thread that stated I needed to replace the apks and odex's as well as the build.prop. I didn't read it carefully enough as it said to replace *THE* problem ones. My validation error was on the build.prop file, I think.
In any case, I was using root explorer to copy *ALL* the files from a base zip file's app folder into the /system/app folder. Things were going along fine, until the phone app forced closed, then the phone rebooted.
Now I'm boot looping.
What can I do? I don't have any safe straps.

Can't access safestrap? Stock recovery? Adb services?
Sent from my DROID4 using Carrier Pigeons

The Magician Type 0 said:
Can't access safestrap? Stock recovery? Adb services?
Sent from my DROID4 using Carrier Pigeons
Click to expand...
Click to collapse
thanks for the reply...
I don't have safestrap installed on the device, and I've never used it. I don't think that's an option, unless you have something up your sleeve there
As for Stock recovery, I'd love to give it a try, but I don't know how that would work. I can't get to ADB because I can't boot the phone.
I *CAN* get into the bootloader. From there, I can get into recovery, AP Fastboot, BP SBF Flash BP boot... and others.
So, I'm hoping there's some kind of way to push to the device from one of the boot loader options. I've had a Droid 1, and a number of other android devices, but I've never gotten this far into a hole before.
again... thanks for whatever you got

It doesn't look good my friend, not without a SBF to flash. The only thing I can think of off the top of my head would be to try flashing the update again and cross your fingers that you got things in place before the bootloop. However I'm 99.9% sure that won't work. If I find anything else I'll let you now, but at this point you might be a sitting duck.
Sent from my DROID4 using Carrier Pigeons

The Magician Type 0 said:
It doesn't look good my friend, not without a SBF to flash. The only thing I can think of off the top of my head would be to try flashing the update again and cross your fingers that you got things in place before the bootloop. However I'm 99.9% sure that won't work. If I find anything else I'll let you now, but at this point you might be a sitting duck.
Sent from my DROID4 using Carrier Pigeons
Click to expand...
Click to collapse
I have the update on the SD Card, and nope, flashing it results in the same system validation error, and a bootloop.
thanks. Do you think that flashing the RAZR sbf's would get me a booting device? I only got the thing 14 days ago. Maybe I can exchange it

jbeazell said:
I have the update on the SD Card, and nope, flashing it results in the same system validation error, and a bootloop.
thanks. Do you think that flashing the RAZR sbf's would get me a booting device? I only got the thing 14 days ago. Maybe I can exchange it
Click to expand...
Click to collapse
If you're still in the 14 day return window I would try to return it. If it can't get past the bootloader than they won't know you rooted it. Just tell them you tried to do the update and it bootlooped. That's probably you're safest bet.

kwyrt said:
If you're still in the 14 day return window I would try to return it. If it can't get past the bootloader than they won't know you rooted it. Just tell them you tried to do the update and it bootlooped. That's probably you're safest bet.
Click to expand...
Click to collapse
I'm heading down there in a few minutes. Thanks for the help all ! I think I'm getting the razr maxx. My wife has one and the screen on that thing is incredible. I think it's worth losing the keyboard to get that screen... and the battery life. That part is also incredible.
again.. thanks.
BTW, you guys absolutely rock. You've helped me out of some serious holes with my OG Droid and other devices more often than I can count.

Sent from my DROID4 using Tapatalk 2

You can use bp tools to push over a clean system. I believe theres a tutorial somewhere that written for bionic. Just replace that with the droid 4 system. I would extract it from one of the stock roms available and push it thru bp tools.
Sent from my DROID4 using Tapatalk 2

Can you link that tutorial? I'm also trying to figure out how to use adb via stock recovery. Thanks!
Sent from my DROID4 using Carrier Pigeons

http://forum.xda-developers.com/showthread.php?t=1236465
Sent from my Galaxy Nexus using Tapatalk 2

Thanks!
Sent from my DROID4 using Carrier Pigeons

Let me know
Sent from my Galaxy Nexus using Tapatalk 2

It sounds like OP is going to exchange their phone, but could you really just replace the entire /system folder and have it work? (Nothing special with permissions, etc?)
If so, that is definitely something worth knowing...

Yes i believe so.
Sent from my DROID4 using Tapatalk 2

Has anyone else gotten this while rooting?

Hey guys. I ran into some trouble trying to root my note 3 and got this message. Now the phone won't turn on our connect to kies to try to repair it. I have the Samsung drivers installed and I believe I followed the directions closely. Can any of you tell me how to get back to factory settings or all the way through the root process. I'm stuck at this screen for now. Any help would be awesome.
Sent from my Nexus 7 using xda app-developers

Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.

Quickvic30 said:
Try using the one click oding to get back to the stock firmware. Put the phone in download mode and flash the first step of the root procedure and then stop and make sure your phone will work in stock form first before you try rooting it again.
Click to expand...
Click to collapse
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops

That's not good, maybe try a new download. Which firmware are you flashing? MI1 or MI9?

That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..

Same thing!
xavier6303 said:
That's actually what happened when I tried to root. It would sit forever and fail due to a timeout. What I did is after the failure..I left the phone in dl mode and connected and closed the odin..then relaunched odin and it worked the second time. That's my experience and your mileage may vary..
Click to expand...
Click to collapse
The exact same thing happened to me... I tried to install Kies 3 and add the drivers but to no avail. So from there on I just closed everything. Disconnected my note 3, reconnected it, and ran odin once more. It immeadiately passed and rooted my phone.

I have seen that in the past it is the sign of a brick you definitely have to Odin back to stock to fix that
Sent from my SAMSUNG-SM-N900A using xda app-developers app

Yes it happened to me too. I just figured it was my crappy computer so I continued to try and after the 4th try I was able to achieve root status. Like a previous commenter suggested, it's a timed out issue.

Yea. I must have tried a dozen times a dozen different ways and I was stuck. I just said eff it and got a new phone. Debating if I want to try again, but I don't feel like potentially going thru the same heart ache. Really the only reason I care to root this phone is to get rid of those damn bloat ware apps; especially My Magazine.
Sent from my SAMSUNG-SM-N900A using xda app-developers app

alpinesun said:
Instead of Pass in a green box, I get Failed in a red box and the progress bar on the phone stops
Click to expand...
Click to collapse
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app

alpinesun said:
It was MI9
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Just went thru this on my Note 3 - chances are youre using a vm on a mac arent you?
Make sure you use a dedicated *windows* machine and not a vm (or at lest not a fusion VM) That was my issue, I havent tried parallels. I grabbed a dedicated win 7 machine and it works perfectly.
I was going to return it of that failed, which luckily it didnt.
Cheers

Attempted to install new InsertCoin [Fail]

It gets to the end but shows install error 7 at the end, booted anyways, now just bootloops to eternity. No recovery is accessible only fastboot now.
Tried to install 3 recoveries through fastboot all passed but none bootup, factory resetted through fastboot, no go still. Not in anyway meant to steer people away from the ROM, others are reporting it is working fine for them. I can't and a few others it seems. Phones aren't done for, just temp out for the count.
Will clean up the thread and make things prettier but need to get to work, hopefully this gets some attention. Thanks for any help guys, I won't be able to trouble shoot for about 10 hours or more depending on work things.

Were you able to restore your backup, or perhaps adb push a new rom ?
If not, what is your fastboot getvar all output?

SaHiLzZ said:
Were you able to restore your backup, or perhaps adb push a new rom ?
If not, what is your fastboot getvar all output?
Click to expand...
Click to collapse
I can't access recovery. Others have posted they can get into recovery and revert back. I cannot get it to boot and stay in recovery for more then a second. I installed the latest cwm recovery before flashing all was fine. Any link to sideloading. Will try when I get home tonight, on a backup phone right now at work.
Sent from my LG-P999 using xda app-developers app

Also appears it is happening in the other 4.4 gpe rom. Reboots and such.
Sent from my LG-P999 using xda app-developers app

Time to RUU back!

SaHiLzZ said:
Time to RUU back!
Click to expand...
Click to collapse
That's what I figured, will have more fun tonight I guess and report back, thanks bud.
Sent from my LG-P999 using xda app-developers app

mt3g said:
That's what I figured, will have more fun tonight I guess and report back, thanks bud.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
So I tried it.
Got a boot loop to where i keep rebooting at the set up menu. -.-
I can't push via ADB for some reason, it says my HTC isnt found when the last time I tried, i removed all data, then adb pushed but that was dangerous .

sasaphrazz said:
So I tried it.
Got a boot loop to where i keep rebooting at the set up menu. -.-
I can't push via ADB for some reason, it says my HTC isnt found when the last time I tried, i removed all data, then adb pushed but that was dangerous .
Click to expand...
Click to collapse
So you side loaded and got it working now? Good news. Weird why its happening to some and not all. Dis you uncheck volume to wake option as well by chance? I'm just going to run the ruu when I get home later. Just need to read on how its done lol.
Sent from my LG-P999 using xda app-developers app

and im also on twrp 2633

To anyone that reads, me being stuck in an endless bootloop will a fastboot erase cache fix my issue? I've read that numerous times... thanks.
Sent from my LG-P999 using xda app-developers app

mt3g said:
So you side loaded and got it working now? Good news. Weird why its happening to some and not all. Dis you uncheck volume to wake option as well by chance? I'm just going to run the ruu when I get home later. Just need to read on how its done lol.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
I side loaded ARHD 31.0 HD fine.
what im probably gonna do is try sideloading it again, then S-OFFing my HTC. Idk why It wont let me s-off for some reason -.-
Tried without the volume thingy, still doesnt work btw.

Ok, cool. Did you check your download for md5 match. I didn't as the download size was correct, lazy and dumb move.
Sent from my LG-P999 using xda app-developers app

Okay now I need MAJOR help.
I deleted EVERYTHING off the sd.
I tried ADB sideloading and its not finding my device. I tried multiple drivers and still nothing. Im on Win 8.1

You should try it on windows 7

Ya I haven't read anything good about windows 8 and android. There is a thread around somewhere tho.
Sent from my LG-P999 using xda app-developers app

http://forum.xda-developers.com/showthread.php?t=2543300 pass this around please

sasaphrazz said:
http://forum.xda-developers.com/showthread.php?t=2543300 pass this around please
Click to expand...
Click to collapse
How about you try a different computer not on win8??
Sent from my LG-P999 using xda app-developers app

just bricked mine too
This rom just bricked my htc one one too. i can't get to recovery no more... now im stuck on the fast boot and dont even know what to do next...can anyone help here plz...
mt3g said:
It gets to the end but shows install error 7 at the end, booted anyways, now just bootloops to eternity. No recovery is accessible only fastboot now.
Tried to install 3 recoveries through fastboot all passed but none bootup, factory resetted through fastboot, no go still. Not in anyway meant to steer people away from the ROM, others are reporting it is working fine for them. I can't and a few others it seems. Phones aren't done for, just temp out for the count.
Will clean up the thread and make things prettier but need to get to work, hopefully this gets some attention. Thanks for any help guys, I won't be able to trouble shoot for about 10 hours or more depending on work things.
Click to expand...
Click to collapse
---------- Post added at 08:35 AM ---------- Previous post was at 08:28 AM ----------
how to troubleshoot htc one from the fast boot btw...?
arso120120 said:
This rom just bricked my htc one one too. i can't get to recovery no more... now im stuck on the fast boot and dont even know what to do next...can anyone help here plz...
Click to expand...
Click to collapse

I just ran the ruu for my device, did it last night and all is good. What carrier and software do you have?
Sent from my HTC One using XDA Premium 4 mobile app

Good to know OP! Lucky you had a RUU to go back to!

Broken out of the box?

Hey guys, I do no not own this phone (just picked up a Nexus 5) but, my dad does. He has been waiting for MONTHS to get his hands on this. It is his first Android device and he was able to ditch his work iPhone for it. However, he has been having an absolutely horrible experience:
I was remotely walking him through setup (moto transfer with iCloud to gmail account, etc etc).
- He turned on his phone, set up wifi, entered account credentials, played around for a minute or two.
- After this, he was prompted for an update, I told him to accept it
- After he accepted it, the phone WILL NOT TURN on. It boots to the homescreen, says it is "activating" the device, then it needs to restart.
- When it restarts, he sees the following attached screenshot.
I am assuming this was the Kit Kat update. I know tons of people have had problems with this (yes, I read the forums before posting, even though it is not my device). However, everyone with problems seemed to be rooted/not on stock. He is COMPLETELY stock.
If he chooses to reboot normally, he gets the homescreen, activation, then, it turns off and goes back to the attached screen.
If he chooses recovery, it goes back to this screen.
I'm not sure how an OTA could jack a phone up that was completely stock.. But it has happened.
Is there anything I can do remotely to help him start using his new phone? As I said, he has been excited for months for this phone and now just wants to throw it against the wall.
Is this screenshot the fastboot screen? If so, can I use the "fastboot erase cache" command?
Any *detailed* answers would be greatly appreciated... I'd love to get this working for him ASAP.
Thanks everyone!
View attachment 2415287

This is a pretty horrible out of box experience for something he was so excited about. I'm hoping this is something I can just do while remotely controlling his PC... I feel bad for the guy

fastboot erase cache
and then flash a stock recovery
Enviado desde mi XT1052 usando Tapatalk

waiflih said:
fastboot erase cache
and then flash a stock recovery
Enviado desde mi XT1052 usando Tapatalk
Click to expand...
Click to collapse
Not having this phone myself, how do I flash a recovery if I can't access current recovery or boot? Can I flash with a locked bootloader? Is the screen my dad is seeing the fastboot screen?
Any ideas how a stock out of the box phone would encounter this?
Thanks!
Sorry it's just hard to not have a device and jump into this when there are a million threads and it is completely different than any device I've owned (also I have no hands on time with it).
Thanks again. The more details the better so that I can do this remotely.
Sent from my Nexus 5 using XDA Premium 4 mobile app

yes that screen is fastboot mode, so u can download the files for ur rom here
http://sbf.droid-developers.org/ghost/list.php
and use fastboot to flash only recovery
Enviado desde mi XT1052 usando Tapatalk

Ok. I will have to figure out how to flash sbfs via fastboot then. I'm assuming it is a simple set of commands. I will try and find a tutorial when I am not driving. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app

EmperorX said:
Ok. I will have to figure out how to flash sbfs via fastboot then. I'm assuming it is a simple set of commands. I will try and find a tutorial when I am not driving. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which model/carrier of phone does your dad have?

Xatt said:
Which model/carrier of phone does your dad have?
Click to expand...
Click to collapse
He's on Verizon, 16gb.
So confused as to how this happens fresh out of the box. Don't know how it's possible. I'm determined to fix it for him today though so he doesn't have to wait even longer
Sent from my Nexus 5 using XDA Premium 4 mobile app

If he just bought it, why are you messing around with this? Take it back to the retailer you bought it from and tell then what happened... Get a new phone...
AT&T Moto X rocking rooted 4.4

theraffman said:
If he just bought it, why are you messing around with this? Take it back to the retailer you bought it from and tell then what happened... Get a new phone...
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app

waiflih said:
yes that screen is fastboot mode, so u can download the files for ur rom here
http://sbf.droid-developers.org/ghost/list.php
and use fastboot to flash only recovery
Enviado desde mi XT1052 usando Tapatalk
Click to expand...
Click to collapse
I'm assuming I can use any of the builds from verizon there? I'd like to get him to update OTA and see if it works this time or not... Was thinking about flashing one of the three 4.2.2 ones

EmperorX said:
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
EmperorX I work for Moto. If you wouldn't mind providing the IMEI I'll get our engineers to take a look. You can PM me. Thanks!

I found this toolkit:
However, i'm assuming the fastboot menu will not work to just flash stock as you need to be in "Android or hboot"
The fastboot screen I took the picture of is not the same thing as hboot correct?

They are interchangeable terms. Hboot refers typically to an HTC bootloader

gunnyman said:
They are interchangeable terms. Hboot refers typically to an HTC bootloader
Click to expand...
Click to collapse
Awesome, looks like I may be able to fix this for him after all. Just need to remotely get androidsdk and adb setup on his computer with RSDlite as backup if this toolkit doesn't work and I *should* be able to make this happen. I think i've got enough info to do this now. Thanks guys!

EmperorX said:
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gotcha, makes sense not to want to go through all that. Sorry this happened to your dad. First I've heard of an issue this big on the moto x.
AT&T Moto X rocking rooted 4.4

theraffman said:
Gotcha, makes sense not to want to go through all that. Sorry this happened to your dad. First I've heard of an issue this big on the moto x.
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
He was on the phone with Motorola "tier 2" support this morning for 3 hours. Their solution was to order a new phone and expedite shipping and return the old one when it gets here. I'm going to try this way first. They said this happens to "1 in 10,000" people. Lol, he's a lucky guy!

Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-

EmperorX said:
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
Click to expand...
Click to collapse
Sounds like the phone's partitions are all jacked up. Get a new phone is the solution.

EmperorX said:
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
Click to expand...
Click to collapse
what probably happened was your dad never activated the phone then tried to take an ota or something like that and it got all jacked up. Alternatively, he could have (for some reason) gotten the 4.4 OTA even though the phone was on original stock FW. This could have f'd the phone up if it skipped the 4.2.2 OTA. If you need to help you dad out, download teamviewer or logmein (remote computer access programs) and just guide him through when to plug the phone in etc.
Not sure about the error you are getting but it could be because you are flashing the wrong FW for the phone, possibly an older FW or an updated FW and the order you are flashing it could be causing the error. You can fix this relatively easily if you were more familiar with fastboot. I can try and walk you through some stuff as well on gchat if you need some help. I could also remote into your dads computer and do everything that needs to be done (he could then remove my ability to remote in clearly). All that being said Im fairly busy so just answering some questions for you would be easier but more time consuming for your dad. For starters, you probably should be flashing the 4.2.2 FW found on sbf. it is the middle fw for verizon on the list. You also can probably just use rsdlite since he hasn't set the phone up. It is super easy. Just go to the thread for rsd lite back to 100% stock and you will be good to go. Then make sure he activates and sets the phone up and everything before he takes the OTA this time.