Database Users

i REALLY need some help

Ok so i just found out today about the WM6 upgrade for the xv6700 so i decided to try it.
I have a Verizon XV6700 with bootloader v1.04
i used the rom from http://forum.ppcgeeks.com/showthread.php?t=7671
i downloaded the one that says Verizon not the Verizon with bootloader 1.02
I run a pc with windows vista
here is what i did step by step
I put the ppc into bootloader mode and then connected it to the pc via usb
then i opened the exe file from my desktop and followed the directions and then clicked install
it then popped up a little window saying checking the information on your device....please wait.... and below it it said dont disconnect your device until the update is complete...
i read that the update takes about 7 mins i allowed it to sit at this for 20 mins and it still did nothing...so i disconnected the usb and then tried to restart the phone and everytime i turn it on it goes straight back to the bootloader screen i cant get out of it...is there anyway for me to get my phone to work? did i brick it? If anyone can help me it would be greatly appreciated

geez, looks like i am not the only one messing up here. I regret this fancy roms by now... but search on PPCgeeks.com some article called "stuck on BL screen" or stuck on bootloader, there''s a little exe you run to get out of it. good luck
i got mine stuck too, but no on the BL.

hero won't boot, except for fastboot

hi there.
ive bought a refurbed hero from "3" uk, however it doesn't boot. it wont go into recovery either (home+pwr).
it will go into the fastboot though (pwr+back).
the phone connects to the pc, and the pc finds the phone using "fastboot devices" and "adb devices".
i tried flashing a custom RA recovery, however i received the message "failed remote not allow".
googling it, i found out it is because of the hboot being 1.76....... which needs flashrec to install a custom recovery. problem is i cant boot the phone to use flashrec.
basically is the phone screwed?
ive called 3 and they are sending a replacement on monday. i will then have to send the old one back to them myself, meaning ive got a few days to make sure the new one works etc, check condition.
thing is the one i have now is perfect and new looking. i could receive a slightly damaged working one on monday, so i want to see if there is anything i can do to fix it.
thanks for any help

What happens when you try to boot up normally? ... Anything?
How about without the SD in?... Does it make a difference?

when i boot up normally, it displays a thin "hero" logo, then after a while displays a htc logo with a green alien popping out.
a minute after that, it starts all over again until the battery is pulled.
tried with and without an sdcard, and no difference.

Flash a new official rru from HTC. If you can't do that you should be able to create a goldcard and flash a the rru that way. Check out parts of my guide and make up the rest.

i just got it sorted.
i downloaded the ruu, tried it while in fastboot mode. it didnt work, so i looked through your goldcard thread, and realised i hadnt got adb setup 100% (device manager had it down as android device or something, so did as instructed in the thread).
connected it up to the pc while in fastboot mode, then ran the ruu. it worked this time!
thanks alot for the help. its saved me alot of hassle sending the phone back.

[Q] Help!! I bricked it

Please help. Background. I rooted it and had it set up to work on Cricket. Well I like the latest rom so I attempted to update it to a different rom. First one wouldn't boot so I was able to get into Clockwork mod and load a saved original version back. Then i tried flashinf the Rumm rom and now when I start it it immediately goes to the Rumm screen and stays there. I can't figure out how to get into the Clockwork menu agiain and it wont boot up. I can press camera down volume and power and get it into the bootloader. But I have no idea what to do from there. I am new to the droid X but I was successful with the HTC Hero. but this is new.
Thanks for any help

Bigstew33 said:
Please help. Background. I rooted it and had it set up to work on Cricket. Well I like the latest rom so I attempted to update it to a different rom. First one wouldn't boot so I was able to get into Clockwork mod and load a saved original version back. Then i tried flashinf the Rumm rom and now when I start it it immediately goes to the Rumm screen and stays there. I can't figure out how to get into the Clockwork menu agiain and it wont boot up. I can press camera down volume and power and get it into the bootloader. But I have no idea what to do from there. I am new to the droid X but I was successful with the HTC Hero. but this is new.
Thanks for any help
Click to expand...
Click to collapse
Looks like you'll want to SBF the device. Google search on how to SBF the Droid X and you should come up with some really good guides. Make sure you flash to 2.3.320 if you want to use the latest and greatest that Team Defuse has to offer. I would post a link to one of the guides, but I'm away from my computer today.
Sent from my DROIDX using XDA App

The only way. Into clockwork is pull battery so he says.if not send me your email to [email protected] I have the links.or download
http: market_android_com search?q=pnamerg. teamblackhat.leakloader
Its an app on marketplace call teamblackhat downloader
Sent from my DROIDX using XDA App

I have rsd lite and SHADO_X6_2.3.34_SYSTEM-ONLY.sbf I open the RSD and choose the sbf file but RSD doesn't find the phone. there are drivers loaded says Motorola Flash Interface v. 3.2.5.0. I have it in the bootloader says ok to program transfer mode usb. Thoughts
Thanks

Windows 7 64bit pro gives some difficulty with recognizing the phone. I suggest removing the motorola drivers and downloading them again.
I got it to work by plugging my phone in, then installing the drivers immediately after. It is screwy sometimes though.
Also RSD has device ID options. change that and see if it recognizes it. I also find that sometimes if I plug in my phone after RSD is open it finds it.

wow this has been a long process. after not able to get the phone to get recognized on Win7 I moved everything to my win xp comp. while it was in the provess of creating the image file ( took like an hour) the battery on my phone died. So I am charging the phone still. it's still creating a image file. Hope I can resume once phone is charged. I am not sure why the phone doesn't chrge while plugged into the USB port but ok. Thanks for the ideas so far. Will update later

Bigstew33 said:
wow this has been a long process. after not able to get the phone to get recognized on Win7 I moved everything to my win xp comp. while it was in the provess of creating the image file ( took like an hour) the battery on my phone died. So I am charging the phone still. it's still creating a image file. Hope I can resume once phone is charged. I am not sure why the phone doesn't chrge while plugged into the USB port but ok. Thanks for the ideas so far. Will update later
Click to expand...
Click to collapse
FYI it shouldn't take over an hour to create image. I flashed the .320 SBF 2 days ago and the whole process from start to finish was under 10 minutes.
Also, I don't believe it charges when in bootloader mode. You could power it via USB if necessary (involves stripping a USB cable). I've never done it but there are various tutorials. I'll look around.

http://www.droidforums.net/forum/droid-x-hacks/68222-unbricking-your-droid-x.html
See code corrupt error section.
The easiest option is to charge your battery in another X.

amasse said:
FYI it shouldn't take over an hour to create image. I flashed the .320 SBF 2 days ago and the whole process from start to finish was under 10 minutes.
Also, I don't believe it charges when in bootloader mode. You could power it via USB if necessary (involves stripping a USB cable). I've never done it but there are various tutorials. I'll look around.
Click to expand...
Click to collapse
yes I charged the phone to 100% and tried again and again the battery died before it finished. the sbf file I have is 280 Mb. If there is a smaller one then maybe it will work

It's more likely that the SBF file you have is bad or there is still some sort of USB driver issue going on. Try downloading it again from wherever you got it.
The phone should not go from 100% to dead in an hour. Also the SBF flash shouldn't take nearly that long.

for now I am stuck. I can't get the phone to charge the battery any more. When I plug the phone into the wall it just goes to the bootloader screen by its self and has an error number and a message that the battery is low. So I ordered some batteries with a wall charger. Once those arrive I will try again. thanks for all the help you guys are giving me. update later date

R2D2 - Bootlooping, SBF failed 0x70BE

Hey there!
My beloved Droid R2D2 seems to be ailing in the form of being bricked. Nothing happened to it, it just decided that today (really three days ago) was a good day to get stuck in Bootloader on infinite loop. The battery is fully charged, whenever I turn on the phone it goes to:
Bootloader
D2.37
Battery OK
OK to Program
Connect USB
Data Cable
I can get into both Recovery and Bootloader the normal way (I've tried wiping my cache and setting it back to factory settings already) but can't seem to get to anything else.
I tried SBFing it using RSDLite v5.6 with the most recent drivers installed and the SBF file from the lovely droid developers site (specifically the 2.3.4 version). It gets to 100%, the phone restarts, but then I'm presented with the message:
Error switching phone to BP Pass through mode (0x70BE); phone connected
and a big FAIL in the Result box.
I've been looking all over for solutions so I wouldn't have to post this, but it seems everyone else has errors or corrupted codes with their bootloader, whereas mine seems to think it's okay.
I absolutely adore this phone and am by no means ready to give it up (they've even stopped producing them so any new phone would have to be a plain old regular Droid2...), so any help would be unbelievably appreciated!

http://droid.koumakan.jp/wiki/SBF
Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally.
Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, refer to Android Recovery.
Click to expand...
Click to collapse
if you still no luck, to ezSBF
http://www.droidforums.net/forum/droid-2-hacks/161849-tool-ezsbf.html

Ah! ezSBF worked! This is both wonderful and unfortunate (I ordered a droid 4 to replace my phone deciding it really was dead so now I have to figure out whether to switch to the 4 or send it back for a few more months in the hopes that its price goes down a bit more...) but mostly really good to see old R2 alive and well again. Thanks!

ezsbf has helped a lot of people
Sent from my MB870 using xda premium

so i have a questions. i got mine rooted and deleted something i shouldnt have deleted. so i sbf back to stock. its says that the flash was successful but my r2d2 keeps bootlooping. any ideas

Which sbf did you flash?
Sent from my DROID2 using Tapatalk 2

did you try wiping cache or data?

delete this

jwagman1 said:
delete this
Click to expand...
Click to collapse
you decide to to read the thread? like 4 posts up

[CLOSED] Help! Nexus 10 stuck on Google logo after Rooting attempt

Hey guys, looking for some assistance here as I am at a complete loss.
Decided tonight to root my 4.2.2 Nexus 10 using the Nexus Rootkit v1.6.3 and the aid of a YouTube video. All went swimmingly up until the TWRP wipe. The video I followed failed the wipe attempt and the guy showed how to get the N10 out of the bootloop and do a 'wipe data/factory reset' via Recovery Mode in the Bootloader and then restart.
Problem is, my wipe never failed like his did in the video (great I thought!) and so I restarted after that and now I find my N10 booting up to the Google Logo (with the padlock at the bottom) and it just sits there. Doesn't even get to the 'X' logo which should come after.
I've tried a few things including the manual wipe data/factory reset from the bootloader and restart but everytime it gets stuck at the Google Logo. I am also now at the point where my N10 doesn't show in Device Manager as it did before. It now shows under 'Portable Devices' as a 'MTP USB Device'.
I am really at a loss here and searching various solutions is just confusing me even more and would appreciate it if someone could help me out, even just getting back to stock for now. That's if it isn't goosed?
Thanks in advance

Have you tried using a different usb port on the PC, and rebooting the PC?

bigmatty said:
Have you tried using a different usb port on the PC, and rebooting the PC?
Click to expand...
Click to collapse
I have yeah. Left my PC off overnight and went back to it again this morning and same issue.
Plug it into the PC (this time using a USB port on the back) and it initially comes up 'installing device driver software' quickly followed by 'device driver software was not installed successfully', quickly followed by 'installing device driver software' again and that's when it shows up in Device Manager as 'MTP USB Device' under Portable Devices, whereas before during the root attempt it was show as 'Nexus 10'.

When I first read the subject line I thought it was "another one of these" where OP hadn't searched on the existing boards. But when I read OP I see you did try "the usual suggestions". Hoping a more seasoned pro jumps in here to help...
I can say that on the handful of "really bad" posts like this that I've seen they usually end with the person saying something like "well I don't know what happened I just kept trying all the power button / charge recommendations and finally it worked" - so don't underestimate the effectiveness of repeatedly trying it like a mad man!
Some random suggestions I have that may help:
-Can you leave it on, on the Google screen, to where the battery 100% drains, maybe this could act as a "battery pull"
-Try a different USB cord
-Try rebooting it via the power buttons while the device is plugged into the wall charger
-Download the Android SDK, then use its "update manager" to update its USB drivers to today's definitions
-Try another PC
Good luck!

Thanks for the suggestions bigmatty, I'll certainly give them a go when I get in later.
I think my biggest concern is that there doesn't seem to be any OS on it, possibly to do with the wipe during TWRP and then I rebooted - was I supposed to reboot at that stage? That's where I got into this loop. And now it doesn't detect it as 'Nexus 10' in my Device Manager on my main PC. Only this MTP USB Device - sometimes showing a conflict warning triangle, sometimes not and no longer showing as a storage device in My Computer.
I did connect it to my Netbook (Running XP) earlier and it detected it as an 'Android Device' under Other Devices in Device Manager. Tried installing it with the naked drivers on the Android SDK and it now lists it under 'Android Device' in my Netbook's Device Manager as a 'ADB Device' (I think, would need to double check as I'm not on it at the moment.)
I just want to find some way of getting it back to factory settings and stock OS if possible and then take it from there again. Don't fancy at £319 paperweight! I'm usually alright with these things too.
Thanks again (And if anybody else has any other input in the meantime I would be grateful - I'll try anything at this stage!)

I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm

bigmatty said:
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
Can't really get into much on the Tablet itself. It boots up, gets to the Google logo (with the padlock symbol at the bottom suggest it has been partially rooted (?)). I can get into the Bootloader by holding down the Power + 2 vol buttons. Once in the Bootloader I have the options of Start/Power Off/Recovery Mode/Restart Bootloader.
When I go into Recovery Mode I can get access to the blue menu where I get the options to restart/something about adb/wipe data/factory reset/delete cache partition (paraphrasing here).
Don't know how many times I've tried the wipe data/factory reset option and reboot but always get sent back to the same loop.
I'll give you're other idea a shot as well later. Thanks again.

bigmatty said:
I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:

Scotman57 said:
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:
Click to expand...
Click to collapse
Awesome! Glad it worked out