My Scenario - Dell Streak 7, running rooted 2.2, worked fine - until it didn't it was hooked to the car charger, functioning as a GPS. I looked down at it and it was a black screen. Power light off although hooked to a charger. Three buttons down right side illuminated when on power.
Computer sees it as APX device - I have used nvflash previously to downgrade from Honeystreak back to rooted stock ROM so drivers are installed on my system. When I try to reflash as before, it seems to load the bootloader, then delivers the message in the post header - specifically:
failed executing command 31 NvError 0x12002
command failure: writedeviceraw (bad data)
Mind these are the same files I have used for previous successful flash, and re-downloaded files on another computer yield identical results. So, problem is with the device. Searching on the error finds a few different tablets with the symptoms, but no solution I have found, other than "Send it back to Dell". Since I bought this one through eBay, it's not easy or even possible to do that. So would like to fix it.
Any ideas?
same problem here, first it was running the stock android 2.2.2 then i tried to flash Honeystreak, it gave the same error and leave my DS7 stuck on apx mode, then i tried to restore it through NVFlash and gave me the same error but is no longer stuck on apx mode, when i boot gets stuck on dell logo and i can boot on recovery mode and fastboot.
have you found a solution? or, did you managed to send it back to dell?
Maybe you should ask the dev himself on the official thread?
i tried that... but they don't let me post in those forums yet, because i'm a noob
Hi Guys
Some one can find a solucion to this??
Can you get into Fastboot mode?
illdill said:
Can you get into Fastboot mode?
Click to expand...
Click to collapse
Hi I can't go to fastboot mode only apx mode with 3 ligths on and black screen no more
Once a failed command executes in APX mode, the connection is terminated. Reset (power off) the device using the pinhole and disconnect from the computer. Then plug back in to the computer while holding down the Volume Up & Down.
illdill said:
Once a failed command executes in APX mode, the connection is terminated. Reset (power off) the device using the pinhole and disconnect from the computer. Then plug back in to the computer while holding down the Volume Up & Down.
Click to expand...
Click to collapse
If I tried that several times, but it took more than a year looking for solution to this but no answer only errors every time I try a method disttinto I can not return to dell because I'm not in USA I'm from Ecuador
I'm also having the same issue with an employee's Streak 7. Only thing I'm able to get into is the APX mode. Attempting fastboot still results in APX mode after a period of time.
I have confirmed it NOT to be the laptop, as I have another Streak 7 in front of me that I have just now successfully flashed using the restore.bat method. Definitely narrowed down to this one device. I'd rather not send it back to Dell, as I don't really have time to deal with them right now with my workload at the office.
Same here
mine too. only APX mode. DJ steves nvflash not working. Illdill's nvflash not working. Bootloader has error. Mine is Tmo DS7. I cant return it because im not in USA. Please help us.
Did somebody find solution for this problem?
I can't believe that no one don't have any solution for this error. Is this software related or hardware related error?
Does anybody manage to deal with this error? For example did someone replace main board or some parts on main board (and what parts). Or are there any commands that can help with this type of error (31 NvError 0x12002).
Please give me some solution because my friend have this device with this error (blank screen, 3 buttons are lighting, don't want charge) for long time.
Thank You!
Best regards.
Same here...
is it really hard to solve? im stuck at blackscreen and 3 button light for 1 year. still no solution. please help us!
Could be a read-only error which can only be fixed by Dell. I've tried talking to Dell tech's about what they do about this, but they won't tell.
FIXED for me...
I Flashed "Streakdroid HD7-2.0R2-wifionly" I had sitting in an old folder on my pc i had and IT WORKED!!! It booted up to honeycomb... so now on to Jellybean!.. so, for all of you who are dead in thew water, find, and install streakdroid from HERE:
Hopefully this works for you as well.
My error:
sending file: system.img
| 89587712/352321536 bytes sentdata send failed NvError 0x120002
command failure: create failed (bad data)
White Screen
After two days reading the differents forums I found this http://forum.xda-developers.com/showthread.php?t=831086&page=5 and after doing some experiments when i use the original files of nvflash from this forum http://forum.xda-developers.com/showthread.php?t=1018809 and change flash.cfg the first tree lines to
[device]
type=hsmmc
instance=0
and use this command in nvflash
"nvflash.exe" --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x8b0c0011 --create --go
@set /p batuserinput=Press enter to continue:
I get a White Screen and no the 31 NVerror 0x12002 only geta error in the partition, some know how to correct this or get a original flash.bct for the stcok unit I thing this is a error form make a correctly partition
"Streakdroid HD7-2.0R2-wifionly" didn't any help to me, Same thing happens.
Sigh, if you don't know what you are doing...DON"T DO IT.
Same Problem
I am trying to fix a TMO Streak 7 that has the same problem when I try to NVFLASH anything. The only sign of life it displays is the back-lights for the bezel buttons and it being stuck in APX mode. Charge light and display never even flicker. I have read all the forums on the subject and all attempts to NVFLASH end with the same titled error "nvflash failed executing command 31..."
I cannot go to fastboot, recovery, or any other mode other than APX. Has anyone overcome this issue and how? I am technically inclined so I am open to attempting replacing internal "sd memory" chip if the consensus is faulty memory.
Thanks for any assistance anyone can provide.
Related
Well firstly my warmest greetings to all, after this I tell you that after trying everything to apx exit without finding any answer, and most tragic is that I can not go back to Dell because I'm not in USA
I wonder if anyone knows how to get the number SBK injured in a command NVFLASH thanks for the attention and if anyone has any other suggestions that can help me to use the Tablet again would thank all my life greetings from Ecuador
Have you tried flashing it?
stuck in apx mode? for how long? how is that possible? you've tried pinhole reset?
try reflashing NVFLASH 2.2.2
shouldnt have waited until warranty was up... send it to Dell and tell them.."I dont know what happened I just hooked it up to Dell Sync UP software on my PC"....
chrisrotolo said:
stuck in apx mode? for how long? how is that possible? you've tried pinhole reset?
try reflashing NVFLASH 2.2.2
shouldnt have waited until warranty was up... send it to Dell and tell them.."I dont know what happened I just hooked it up to Dell Sync UP software on my PC"....
Click to expand...
Click to collapse
I am stuck in apx mode for one year, and i try everything thats include flashing nvflash 2.2 and the warranty its not possible form my because i am not living in USA
I would try PM'ing TheManii. NVFLASH should get you back.. have you researched how to use NVFLASH? there are other commands that may be helpful. What happens when you try to use NVFLASH??
and when did this originally occur? more information please..
did you do something like disconnect device or lose power in the middle of a NVFLASH.. that might cause this.. but even that should be repairable.
I think TheManii may be able to offer some assistance as long you are patient and respectful. And try to do some research on NVFLASH and APX mode, it will help.
also what OS computer are you running Windows 7 (32bit or 64)? are you sure you have correct drivers installed? what does it say in your device manager on PC?
also what is specific error you get when trying to NVFLASH?
it also may be your version of NVFLASH, you can try another version.
also do you have adb installed? can you try running cmd>adb devices [enter]
make sure you have all the correct files in root of NVFlash folder, and run as administrator.
chrisrotolo said:
I would try PM'ing TheManii. NVFLASH should get you back.. have you researched how to use NVFLASH? there are other commands that may be helpful. What happens when you try to use NVFLASH??
and when did this originally occur? more information please..
Click to expand...
Click to collapse
everything about NVFLASH is that everything is directly related to bringing the system. The error occurs to me is nvflash failed executing command 31 NvError 0x12002 which is an error that gives me moment start writing the images like said in this post http://forum.xda-developers.com/showthread.php?t=1018809
also trying to format_all imagens in the tablet but that no is possible because nvflash give me other error I thinks this its relations with the bootloader thats the reason I try with many differents bootloader I find here in the forum but never give me out to apx mode.
chrisrotolo said:
did you do something like disconnect device or lose power in the middle of a NVFLASH.. that might cause this.. but even that should be repairable.
Click to expand...
Click to collapse
When my tablet enter in apx mode only i am using that with a teamviewer app when suddenly its happend to me, in that moment I think its only out of energy and I connect that to the power, but the next day when i trying to turn on the tablet only the three buttons down right side illuminated.
chrisrotolo said:
I think TheManii may be able to offer some assistance as long you are patient and respectful. And try to do some research on NVFLASH and APX mode, it will help.
Click to expand...
Click to collapse
O really thats amazing and thanks for give me a light to revive my tablet
chrisrotolo said:
also what OS computer are you running Windows 7 (33bit or 64)? are you sure you have correct drivers installed? what does it say in your device manager on PC?
also what is specific error you get when trying to NVFLASH?
it also may be your version of NVFLASH, you can try another version.
also do you have adb installed? can you try running cmd>adb devices [enter]
make sure you have all the correct files in root of NVFlash folder, and run as administrator.
Click to expand...
Click to collapse
I have Windows 7 Ultimate 32 bit, but thinking that that was what made me try it also failure by Ubuntu 11.04 and debian to see what happens but always gives the same error, the version which is not NVFLASH but I was using linux if the last that exists in web development official of tegra the only I dont try is the cmd>adb because my tablet its only in apx mode and no more.
thanks for all
flashing other bootloaders is a bad idea..
find the link for the froyo nvflash and try redownloading.. just in case the one you have now is corrupted..
how does device show up in windows device manager, APX device OK?
I dont have much experience with linux and debian..
I will try to find the link to the nvflash package and any other nvflash commands that may help in your situation.
my internet is a little slow at the moment, will be back up to speed in a day or so.. but..
you have a wi-fi only streak? if you were trying to flash a tmobile nvflash on wi-fi you could very well have problems..
chrisrotolo said:
flashing other bootloaders is a bad idea..
find the link for the froyo nvflash and try redownloading.. just in case the one you have now is corrupted..
how does device show up in windows device manager, APX device OK?
I dont have much experience with linux and debian..
I will try to find the link to the nvflash package and any other nvflash commands that may help in your situation.
my internet is a little slow at the moment, will be back up to speed in a day or so.. but..
you have a wi-fi only streak? if you were trying to flash a tmobile nvflash on wi-fi you could very well have problems..
Click to expand...
Click to collapse
Yes I have install the drivers of apx mode in windows and thats said ok and my dell is t-mobile streak 7 with wifi and 4g jejej thats for your ansewe
and are you trying to use the wifi only restore nvflash files?
try this thread.. reinstall nvflash, ang all images p2-p14 and extract so you have p#.img files in root directory of nvflash folder. also a good idea to have nvflash at root of your c: drive.
chrisrotolo said:
and are you trying to use the wifi only restore nvflash files?
try this thread.. reinstall nvflash, ang all images p2-p14 and extract so you have p#.img files in root directory of nvflash folder. also a good idea to have nvflash at root of your c: drive.
Click to expand...
Click to collapse
ThanksIn the afternoon I try this I said to you the results
my internet is still flakey. Also, rename restore.bat to restore.txt and paste the text here please to be sure it is running proper command. Thanks.
chrisrotolo said:
my internet is still flakey. Also, rename restore.bat to restore.txt and paste the text here please to be sure it is running proper command. Thanks.
Click to expand...
Click to collapse
Sorry for not writing but I have not spent at home but the other day I was trying and researching a little more than NVFLASH qeu so I got the NVFLASH own developers had a bootloader but nothing happened similarly displayed an error I just hung there.
I think what is wrong is the bootloader and not allowed to perform any action within the NVFLASH to deal with others but do not know where to find them??
thanks again for answering
the bootloader should be named "bootloader.bin" or something similiar and you may need to specify it.. or the restore.bat command may need to specify it in order to flash anything. for example c:>nvflash --bootloader.bin (references good working bootloader.bin file in root of you nvflash directory with same name i.e. bootloader.bin) then actual command such as rawdevicewrite 1234567 p3.img
for example have you ever used apktool? in order to decompile some .apks, you need to reference a framework, in case the program cant read what is on the device it uses the on in you working directory.
Have you tried re-downloading and reflashing and getting same error?
maybe we should just try bootloader.bin first to see..
I think TheManii would be the guy to contact on this, but I will research it now . It is also quite likely you device is just plain broken beyond our repair. But I do not like to give up easily.
DO NOT TRY ANY OTHER BOOTLOADERS OTHER THAN THE ONES FOR YOUR DEVICE..AND ONLY THE BOOTLOADER OF THE ROM YOU ARE TRYING TO FLASH TO.
Im quite sure this "The error occurs to me is nvflash failed executing command 31 NvError 0x12002" means it would like you to specify a bootloader.bin after the nvflash command... almost positive..
try to upload the restore.bat or restore.txt or paste it here for us to see.
I think this is a common nvflash error not specifying --bootloader.bin switch although should say "(no bootloader specified)"
If I didnt ask already, can you get into recovery (vol. up and power with more than 50% battery) or fastboot mode (volume down and power)?? maybe we could flash a stock recovery and put a update.pkg on externalsd?? in hopes of some of your partitions are good and a stock update would have enough to boot you up.
also this: "number SBK injured in a command NVFLASH" from 1st post.. SBK is SecureBootKey ..more info here.. http://androidroot.mobi/?page_id=106
does it say your SBK was injured?? maybe We can ask dell to release their SBK? bwahhahahahahhahaha. j/k.
I dont have deep knowledge of nvflash, but usually if a device has SBK enabled you need the key to do even basic stuff on the device. As this is clearly not the case on the s7 I really dont believe it's relevent for the s7.
From what I learned in my discussions with dj_steve at least loading a bl via nvflash (note the 'loading' and not 'flashing') it shouldnt cause damage if you load the wrong one. It might simply malfuction/not do anything until you hit the reset pin
The only commands you really ever need are read and write, since flashing images are the only thing ever really needed
NVflash is one of those things you need to learn how to use to be able to use it correctly. The entire fiasco with the cloned service tags (as an example) is due to users blindly using nvflash without knowing what exactly it does.
Though I dont really know why it's stuck in apx mode, i'd need to know what happened exactly and attempt to walk though reflashing it manually.
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x________________
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
This is an example off my s10 as that was what i had handy, note the sbk burned: false, which is what i recall the s7 also having
for the heck of it, have your tried nvflashing honeycomb R2?
have you tried erasing all partitions? might help..
chrisrotolo said:
for the heck of it, have your tried nvflashing honeycomb R2?
have you tried erasing all partitions? might help..
Click to expand...
Click to collapse
I go to try this thanks
try what? flashing HC HD7-R2? good idea..
or you mean trying to format all partitions? I would try HC NVflash first..
if that doesnt work.. we can see about formatting them all.. of you would like.
I have same here. i bricked my DS7. i can get into APX mode. but nothin other. no fastboot, no startup, nothing other than APX mode. i used nvflash. but error was:
.................................................. ............
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
42000 (0x37042000) flags: 0
Press any key to continue . . .
It stops like this. Can you help me please. my DS is not starting up, no boot, no CWM i cant use anything other than nvflash. please help me?
I keep on trying to flash ANYTHING to my bionic(stuck in ap fastboot with boot failure) and every time I go to flash something it keeps on shifting to "FAILED<remote: battery low>
I am at my wits end, I tried the fxz, and it failed, I tried the r3l3as3droot fix and it fails.... Can someone PLEASE help soon?
You've got to charge the battery. There are ways to do it by cutting off the end of a spare usb cable, and you can find that here somewhere.... I just don't remember where.
Try flashing via RSD lite. See if that works.
http://rootzwiki.com/topic/13105-a-easier-way-back-to-the-update-path/
Sent using xda premium
RSD fails almost immediately. I dont knwo what else to do. I think I officially bricked myself.
htcdesirezgeorge said:
RSD fails almost immediately. I dont knwo what else to do. I think I officially bricked myself.
Click to expand...
Click to collapse
Did you even read sreven.rn's post. You need to charge your battery. Fastboot/rsd will do nothing until you get that battery charged.
This post has the answer you seek
http://www.droidforums.net/forum/droid-x-tech-support/189467-need-help-dead-battery-trick.html
Sent from my DROID BIONIC using xda premium
That is a great tip dellenrules! I'll have to keep this one in mind.
Anyone know if the battery will charge in this FlashBoot mode?
I am on Battery Low, can't boot to phone screwed myself earlier with all the flashing. Not stuck at Flash Failed, can't RSD, can't flash via Flashboot because of low battery.
Wonder if I leave it there will it charge
smilepak said:
Anyone know if the battery will charge in this FlashBoot mode?
I am on Battery Low, can't boot to phone screwed myself earlier with all the flashing. Not stuck at Flash Failed, can't RSD, can't flash via Flashboot because of low battery.
Wonder if I leave it there will it charge
Click to expand...
Click to collapse
I'm 99% positive it will not charge in fastboot mode.
Crap. Was there like a USB hack somewhere that will get this to work? I can't remember. I am screwed!
HOW TO FIX A TOTALLY BRICKED BIONIC (& HOW TO McGUYVER CHARGE A DEAD BATTERY too)
I have prepared an uber zip file that contains all you need.
Wish I had it last night! I was up until 3am, worked on this for about 6 hours, and then this finally worked. I tried everything. fastboot, one click this, sd lite, etc. none of it worked.
You will praise me.
this worked - Got my phone back!
of course, I tried every solution in the world and was profoundly frustrated for hours and ran out of battery. but this WORKED. NOTHING else did.
I also had to do the McGuyver thing with an old blackberry usb charger.
snip the end off, strip the red and black wires, insert the red to positive on your battery (battery out of the phone!) insert black to negative, THEN plug in the charger. let it go for at least 1/2 hour.
my uper zip file - UNZIP THIS file to a FOLDER on YOUR DESKTOP.
http://dl.dropbox.com/u/12759680/fastboot.zip
also Manually copy files (update893 and update901) to your SD card!!!!!
(take out the micro sd, load the files onto it using an adapter.)
1. Put phone in Fastboot mode, connect to computer [hopefully you have the drivers installed. if not, search for Motorola_End_User_Driver_Installation_5.2.0_32bit or the 64 bit if that's your operating system
whenever there is a command, I copied it and pasted it in the command window (ctrl v does not work to paste, you must right click and then paste) dont copy the friggin quotation marks
2. Open a command terminal and go to the Stock folder ("cd C:\Documents and Settings\YOUR NAME\Desktop\fastboot")
3) type these commands in the terminal window and wait for the flashing to finish before going to the next line.
----> "moto-fastboot.exe flash webtop grfs.img" (This file will be flashed in 4 parts)
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
Then reboot into stock recovery (volume up+down and power; then select recovery then volume up)
When in recovery, hit both volume up+down, then go to wipe data
then flash update893.zip
If you come upon the triangle with the exclamation point and the android man, dont freak out, hit the power button, down volume, both volume at once, and eventually you will be in recovery.
you will so do a dance.
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
wait a day. then, If you're feeling adventurous, reboot into stock recovery and flash 901!
I'm no maven, but I got my phone back and then to 901.
havent rooted again but I'm waiting for the developers to catch up to 901, which I downloaded and flashed after getting the damn phone back.
No dice for me
failed at flashing Web Top Frfs.img
Load_file: could not allocate xxxx
Pass preinstall.img
Failed system.img
Writing system .... INFOPreflash Validation Failure
FAILED (remote: )
Reboot phone...
Invalid Flash mode (s) (Boot Failed)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG Version (CG: boot)
is where I am at now
finally got these two installed
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
once reboot, did wipe cache and wipe data
update 893, failed during verify data....
crap..
Ok, here is the deal. It is IMPOSSIBLE to revive your phone from the process that I did. UNDER NO CIRCUMSTANCES SHOULD YOU FLASH 5.5.901 AND THEN DO A FACTORY RESTORE OR RECOVER IN TO A CUSTOM ROM. DO NOT ATTEMPT OR YOU WILL IRREPARABLE BRICK YOUR PHONE!
htcdesirezgeorge said:
Ok, here is the deal. It is IMPOSSIBLE to revive your phone from the process that I did. UNDER NO CIRCUMSTANCES SHOULD YOU FLASH 5.5.901 AND THEN DO A FACTORY RESTORE OR RECOVER IN TO A CUSTOM ROM. DO NOT ATTEMPT OR YOU WILL IRREPARABLE BRICK YOUR PHONE!
Click to expand...
Click to collapse
What are you talking about when you say factory restore? Are you talking about doing a factory data reset?
Because many have done FDR's without a problem.
Have you tried the one click script that P3Droid and the guys at rootzwiki came up with to get everybody back on the upgrade path?
That's weird.
I returned to stock from 901 using the method in the first link I posted without a hitch.
FYI
Sent from my DROID BIONIC using xda premium
I believe the second post was the answer to your problem.. now second option is to cut a usb cable and connect the negative and positive cables to your battery and leave it for an hour or so to charge..
Sent from my DROID BIONIC using XDA App
This guy obviously doesn't want any help.
He pops in once in a while with a frantic nonsensical post and doesn't bother to read our posts that can help him.
nateohio said:
This guy obviously doesn't want any help.
He pops in once in a while with a frantic nonsensical post and doesn't bother to read our posts that can help him.
Click to expand...
Click to collapse
Oh no, I definitely wanted help BUT I was dumb and used my bionic as my sole internet connection. I have my insurance replacement now($100 down the drain). I had tried ALL of the fixes but non even remotely succeeded. What ended up happening was that I somehow made it where it would not even begin to flash files. I purchased an extended battery but yyyyyeeeeaaaaahhhhh lol, so now I have shiney new supplied for my new phone lol.
Oh wells, you win some and lose some.
Fails for me on first line
idivorceyou said:
I have prepared an uber zip file that contains all you need.
Wish I had it last night! I was up until 3am, worked on this for about 6 hours, and then this finally worked. I tried everything. fastboot, one click this, sd lite, etc. none of it worked.
You will praise me.
this worked - Got my phone back!
of course, I tried every solution in the world and was profoundly frustrated for hours and ran out of battery. but this WORKED. NOTHING else did.
I also had to do the McGuyver thing with an old blackberry usb charger.
snip the end off, strip the red and black wires, insert the red to positive on your battery (battery out of the phone!) insert black to negative, THEN plug in the charger. let it go for at least 1/2 hour.
my uper zip file - UNZIP THIS file to a FOLDER on YOUR DESKTOP.
http://dl.dropbox.com/u/12759680/fastboot.zip
also Manually copy files (update893 and update901) to your SD card!!!!!
(take out the micro sd, load the files onto it using an adapter.)
1. Put phone in Fastboot mode, connect to computer [hopefully you have the drivers installed. if not, search for Motorola_End_User_Driver_Installation_5.2.0_32bit or the 64 bit if that's your operating system
whenever there is a command, I copied it and pasted it in the command window (ctrl v does not work to paste, you must right click and then paste) dont copy the friggin quotation marks
2. Open a command terminal and go to the Stock folder ("cd C:\Documents and Settings\YOUR NAME\Desktop\fastboot")
3) type these commands in the terminal window and wait for the flashing to finish before going to the next line.
----> "moto-fastboot.exe flash webtop grfs.img" (This file will be flashed in 4 parts)
----> "moto-fastboot.exe flash preinstall preinstall.img"
----> "moto-fastboot.exe flash system system.img" (This file will be flashed in 2 parts)
----> "moto-fastboot.exe reboot"
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
Then reboot into stock recovery (volume up+down and power; then select recovery then volume up)
When in recovery, hit both volume up+down, then go to wipe data
then flash update893.zip
If you come upon the triangle with the exclamation point and the android man, dont freak out, hit the power button, down volume, both volume at once, and eventually you will be in recovery.
you will so do a dance.
be patient. some of these steps take a while and you think nothing is happening.
then you see some action in the command prompt box.
wait a day. then, If you're feeling adventurous, reboot into stock recovery and flash 901!
I'm no maven, but I got my phone back and then to 901.
havent rooted again but I'm waiting for the developers to catch up to 901, which I downloaded and flashed after getting the damn phone back.
Click to expand...
Click to collapse
My phone goes strait to AP Fastboot Flash Mode (S)(Invalid CDT) at power up.
When I enter the first line of these instructions "moto-fastboot.exe flash webtop grfs.img" I get an error that states
load_file: could not allocate 1397489664 bytes
error: cannot load 'grfs.img'
Any ideas?
Yesterday I had a received a phone call from a friend and upon ending the call I could not hang up. The screen had locked on the call screen. I waited and tried to use the power button to turn the screen off and then on to see if that would clear it but to no avail, so I had to do a battery pull.
I restarted the phone and first thing I noticed was that it was now telling me that I had 5% of my battery remaining, where the phone had been around 80% before the battery pull. Then pretty much everything started force closing, and it rebooted on its own. Upon restart it came up with the dialog box stating that "UIDs on system are inconsistent" and that I should wipe data, and has a button stating "I am feeling lucky". Then it’s endless pop ups of force closes. I finally get it to a point where I can try a factory reset via "Privacy" in settings but nothing changes.
I go into recovery and wipe data and cache partitions and it says it does so successfully, but when you reboot it has not. The phone goes into my "normal" home screen and settings, nothing has been restored back to outta the box state, and it does not prompt you to go through setup.
Other than I used Petes One Click root about 4 months ago the phone is stock, with no new apps installed just before this issue.
If you try to remove any applications, it says they are removed successfully, but when you reboot the phone they are all back as if nothing had happened.
Plug the phone into any computer and it is recognized, but the phone does not seem to know it is plugged into a PC... no "charging" or "mount SD" info.
I tried to do a factory image restore via RSDLite 5.6.4 using
cdma_solana-user 2.3.4 5.5.1_84_D3G-55 110812
It gets to step 3/18 and then tells me:
"Failed Flashing Process: 3/18 flash mbmloader "mbmloader.bin" Phone returned Fail"
I've used RSDL for flashing my OG, D2 and Dx's before with no issues.
RSDL's Flash error log shows:
Line 1041
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlasthThread.cpp
Device ID:0
03/13/12 00:48:51 New Log Started For Software Download.
03/13/12 00:54:21 00001db8 Phone.cpp 1750 0 ERROR GetTechnology failed: ERROR.
03/13/12 00:54:46 The FlashLog key is turned off.
03/13/12 00:54:52 Multi upgrade started for 1 phones
03/13/12 00:54:57 [Device ID: 0] 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin"
03/13/12 00:54:58 [Device ID: 0] 2/18 reboot-bootloader
03/13/12 00:55:03 [Device ID: 0] 3/18 flash mbmloader "mbmloader.bin"
03/13/12 00:55:04 ERROR: 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL. - on device ID 0.
03/13/12 00:55:04 [Device ID: 0] 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL.
03/13/12 00:55:04 ERROR: Failed flashing process. - on device ID 0.
03/13/12 00:55:04 Multi upgrade finished.
03/13/12 00:55:04 00001db8 Phone.cpp 514 0 ERROR Generic failure when sending command.
03/13/12 00:55:04 00001db8 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
03/13/12 00:55:04 00001db8 Phone.cpp 514 0 ERROR Generic failure when sending command.
03/13/12 00:55:04 00001db8 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
I then try Petes "One Click" easy unbrick and the command lines go through fine, all stating OK, and then it reboots the phone as it should. However instead of rebooting to the screen with the software box and the android with the yellow install bar, it goes to the white triangle with the exclamation point and little android. It will not go any further from that.
You can reboot the phone and it boots to the home screen, no set up, no removed programs...it looks as it did a few days ago before the issues started. However you will still get the force closes in a matter of minutes, the UID errors, and all the other issues.
Going to phone info shows the following.
System - 5.6.890
Baseband - N03.18.29P
Build - 5.5.1_84_D3G-55
I even tried to flash CM recovery and it will not do it. If you flash CWR through ROM Manager it will say it downloads and flashes successfully but it does not.
It seems as if the system has become unformat/flash/wipeable.
Suggestions? Clues!?
So you're on .890?
I'd try this first:
http://forum.xda-developers.com/showthread.php?t=1339816
File mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
DoubleYouPee said:
So you're on .890?
I'd try this first:
http://forum.xda-developers.com/showthread.php?t=1339816
File mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Click to expand...
Click to collapse
That has already been tried, as noted above.
Ianscape said:
That has already been tried, as noted above.
Click to expand...
Click to collapse
It says you used RSDlite
DoubleYouPee said:
It says you used RSDlite
Click to expand...
Click to collapse
And then after it says I did the Fast/Easy unbrick
Ianscape said:
...I tried to do a factory image restore via RSDLite 5.6.4 using
....
I then try Petes "One Click" easy unbrick...
Click to expand...
Click to collapse
Did you try removing the ones that give you error from the .bat?
did you started in the correct flash mode?
power + M
ap fastboot??
Use the one in my signature, its also psouza but is different (the one in psouza thread never worked for me)
this one (post by chaoticweaponry file by roots wiki) works in the mode i ssaid
the multiupload link is dead i think, but in the last posts there is a dropbox
http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Pete's One Click Easy Unbrick sounds like a mash-up of his root tool and the quick unbricking script. Just to clarify, it was the MS DOS looking window that comes up after clicking "CLICK HERE TO FLASH etc."?
Hold "X" and power. When u get the triangle press both volume up and volume down @ the same time. Wipe data a couple times followed by wipe cache a couple times. Pull the battery, then use the easy unbrick method in fastboot. You will want to find a way to have a good if not full charge before you unbrick. Should do the trick.
~SU!C!D3~ \,,/.(*_*).\,,/
Sent from my UnLocked XT862 Droid 3 with full XT883 2.3.6 on Straight Talk GSM
I have bricked my phone numerous times recently and have found a very simple way to recover from it, without even having to plug it in to the computer. The OTA leak found here: http://forum.xda-developers.com/showthread.php?p=23223061 can be put on the root of your SD card and installed using the stock recovery. Power + x followed by volume up/down, wipe data, wipe cache, install zip from sd and selecting the OTA zip. I have recovered several times with this and it is pretty handy to be able to do it where ever you happen to be. Of course you will still have to root and reinstall your other goodies, but it works.
Side note: This OTA leak can NOT be rooted with the standard D3 root methods. You must use the D4 root method to gain root privileges.
gierso said:
did you started in the correct flash mode?
power + M
ap fastboot??
Use the one in my signature, its also psouza but is different (the one in psouza thread never worked for me)
this one (post by chaoticweaponry file by roots wiki) works in the mode i ssaid
the multiupload link is dead i think, but in the last posts there is a dropbox
http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Click to expand...
Click to collapse
Yes it was in ap fastboot. I will give the one in your sig a shot, as I have been using psouza's original zip. Maybe it will work *crossfingers*
redsox958 said:
Pete's One Click Easy Unbrick sounds like a mash-up of his root tool and the quick unbricking script. Just to clarify, it was the MS DOS looking window that comes up after clicking "CLICK HERE TO FLASH etc."?
Click to expand...
Click to collapse
Yes, it' the psouza Fast/Easy unbrick, using the moto-fastboot files, etc.
queberican351 said:
Hold "X" and power. When u get the triangle press both volume up and volume down @ the same time. Wipe data a couple times followed by wipe cache a couple times. Pull the battery, then use the easy unbrick method in fastboot. You will want to find a way to have a good if not full charge before you unbrick. Should do the trick.
Click to expand...
Click to collapse
That has been done several times, with no changes to the system. While Recovery states that it completes the wipe, it does not appear to wipe anything. I'm going to try the link gierso posted to see if this helps.
mikedyk43 said:
I have bricked my phone numerous times recently and have found a very simple way to recover from it, without even having to plug it in to the computer. The OTA leak found here: http://forum.xda-developers.com/show...php?p=23223061 can be put on the root of your SD card and installed using the stock recovery. Power + x followed by volume up/down, wipe data, wipe cache, install zip from sd and selecting the OTA zip. I have recovered several times with this and it is pretty handy to be able to do it where ever you happen to be. Of course you will still have to root and reinstall your other goodies, but it works.
Side note: This OTA leak can NOT be rooted with the standard D3 root methods. You must use the D4 root method to gain root privileges.
Click to expand...
Click to collapse
Good to know that you can try it from the SD. I may give that a shot as well. I have bricked my D2 over and over F'ing with it and have always been able to recover from it easily...figures that the first time my D3 does it and it tells me to go pound sand.
Thanks on the D4 note.
-
I'm setting this thing down for a day I need to take a step back so I can try the other file that gierso posted without throwing this thing against a wall.
Had this happen to my wife's Droid 3 and saw 1 post on another forum about a user it has happened to. After conversing with Motorola regarding my "Groundhog Day" issue (ie - no matter what you do, nothing changes on the phone... kinda like the movie Groundhog Day starring Bill Murray), the tech support reps came to the conclusion that somehow the NAND because write-protected. Neither RSD nor the Fast-FBZ nor Safe Mode would let me alter the phone in any way. I had to have the handset exchanged out under manufacturer's warranty...
Try on "AP Fastboot" mode
moto-fastboot -w
moto-fastboot erase system
moto-fastboot erase preinstall
moto-fastboot erase cache
moto-fastboot reboot-bootloader
now use the Psouza Fast/Easy unbrick.
If this does not help. than it would be better to go for a replacement.
Anyone!!!
Please help me, i'm entirely in despair now with my HTC N1 phone.
This place or people from XDA are my only hope, and I wish was in the right place.
Here's my concern, At the first place my POWER BUTTON is not working.
I Installed CM7.2 on my phone and it went great, I decided to install a semi-transparent status bar so I flash a .zip in it. After it reboots, it was stuck at the "X" screen.
The only thing I can do is to have a battery shock on my phone while holding the track ball, and it sends me to a white screen with skating androids.
From there I tried using the Fastboot commands but I got an error saying "FAILED <remote: not allowed>"
I'm pretty sure that "USB Debugging" is checked. And I can even erase the cache from there, but when i tried the "fastboot flash recovery file.img" or any related command like that it says "FAILED <remote: not allowed>".
When using ADB commands my phone wasn't detected. I tried all kinds of USB drivers and trick already, but got me nowhere.
Also I've seen that you cannot use ADB on a white screen, how am I going to get to a non white screen if my power button is not working?
I'm entirely helpless right not. I already went to different best cell repair shop all over our country to fix my power button, since it was the root cause of my misery but even them can't help me with that.
Please help me everyone, I'm a complete noob or even a moron on this.
I'm completely helpless right now.
I'll do anything for someone who'll help me. PLEASE!! :crying:
emeryreme said:
Anyone!!!
Please help me, i'm entirely in despair now with my HTC N1 phone.
This place or people from XDA are my only hope, and I wish was in the right place.
Here's my concern, At the first place my POWER BUTTON is not working.
I Installed CM7.2 on my phone and it went great, I decided to install a semi-transparent status bar so I flash a .zip in it. After it reboots, it was stuck at the "X" screen.
The only thing I can do is to have a battery shock on my phone while holding the track ball, and it sends me to a white screen with skating androids.
From there I tried using the Fastboot commands but I got an error saying "FAILED <remote: not allowed>"
I'm pretty sure that "USB Debugging" is checked. And I can even erase the cache from there, but when i tried the "fastboot flash recovery file.img" or any related command like that it says "FAILED <remote: not allowed>".
When using ADB commands my phone wasn't detected. I tried all kinds of USB drivers and trick already, but got me nowhere.
Also I've seen that you cannot use ADB on a white screen, how am I going to get to a non white screen if my power button is not working?
I'm entirely helpless right not. I already went to different best cell repair shop all over our country to fix my power button, since it was the root cause of my misery but even them can't help me with that.
Please help me everyone, I'm a complete noob or even a moron on this.
I'm completely helpless right now.
I'll do anything for someone who'll help me. PLEASE!! :crying:
Click to expand...
Click to collapse
You don't need to flash the recovery in this situation. Try to reboot the phone via fastboot command and issue these commands in fastboot:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase cache
Once complete, just reflash the CM 7.2 ROM again.
Hi everyone, I tried to root my phone last night and despite following the instructions it is stuck on the green and white loading screen (all night long). I thought I would try resetting it and giving it another go, but I am getting beyond frustrated now. Right now the phone is in fastboot mode (bootloader unlocked) connected to my pc. I have opened CMD and executed the following command:
C:\Users\MyPc\Desktop\Razer\aura-p-global-3110>flash_all
the following lines of code appeared
C:\Users\MyPc\Desktop\Razer\aura-p-global-3110>set fastboot_cmd=fastboot
C:\Users\MyPc\Desktop\Razer\aura-p-global-3110>fastboot flash partition:0 gpt_both0.bin
and now my CMD is doing nothing, I cannot input anything and the cursor is just flashing... been like this for about 20 minutes now. Can someone tell me what I am doing wrong? I currently have a brick of a phone and it's kinda inconvenient.
Thanks
PyroVee said:
Hi everyone, I tried to root my phone last night and despite following the instructions it is stuck on the green and white loading screen (all night long). I thought I would try resetting it and giving it another go, but I am getting beyond frustrated now. Right now the phone is in fastboot mode (bootloader unlocked) connected to my pc. I have opened CMD and executed the following command:
C:\Users\MyPc\Desktop\Razer\aura-p-global-3110>flash_all
the following lines of code appeared
C:\Users\MyPc\Desktop\Razer\aura-p-global-3110>set fastboot_cmd=fastboot
C:\Users\MyPc\Desktop\Razer\aura-p-global-3110>fastboot flash partition:0 gpt_both0.bin
and now my CMD is doing nothing, I cannot input anything and the cursor is just flashing... been like this for about 20 minutes now. Can someone tell me what I am doing wrong? I currently have a brick of a phone and it's kinda inconvenient.
Thanks
Click to expand...
Click to collapse
Have you got this solved yet?
I've never attempted to use CMD to flash my RP2 but since you're in fastboot that's where you need to be as long as you can type fastboot devices and get your phones id to appear. If so then all you need to do is have the image extracted and I placed mine in my fastboot directory and just double click the flash_all.bat file..golden! It'll flash everything and then reboot after installing ?