I was running streakdroid 1.8.1, and was having the wifi/3g problem, and after trying the below suggestion (which was posted in the dev section of the 1.8.1 thread post#367 link=http://forum.xda-developers.com/showpost.php?p=11869560&postcount=367):
--------------------------------------------------------------------------
Originally Posted by strvmarv
This put me on baseband GAUSB1A134031-US and appears to have cleared up the Data that wouldn't enable without a reboot, so far:
1. extracted the decoded ATT 2.2 340 pkg from here...it's the dropbox link BTW! (dropbox link)
2. grabbed the amss.mbn and dsp1.mbn (if you don't want to do step 1 then get the already extracted files here)
3. went into fastboot and flashed both of them
Dumb question, anyone know if it's possible to lose your carrier unlock when doing such things?
--------------------------------------------------------------------------
Now my streak doesn't boot, can't get to fastboot (pwr+camera), or recovery (vol+,vol-, pwr). Sometimes all three led's light up, and stay on and nothing happens, and sometimes the LED's stay off and nothing happens.
I tried using qdltool (vol+, usb connection to PC) , and it timesout after reboot ok message after I click RUN in qdltool. I installed both the qualcomm and dell fastboot drivers as per instructions, and I don't have a yellow ! in device manager.
Would appreciate any suggestions on what I should try next.
jfvidalc said:
I was running streakdroid 1.8.1, and was having the wifi/3g problem, and after trying the below suggestion (which was posted in the dev section of the 1.8.1 thread post#367 link=http://forum.xda-developers.com/showpost.php?p=11869560&postcount=367):
--------------------------------------------------------------------------
Originally Posted by strvmarv
This put me on baseband GAUSB1A134031-US and appears to have cleared up the Data that wouldn't enable without a reboot, so far:
1. extracted the decoded ATT 2.2 340 pkg from here...it's the dropbox link BTW! (dropbox link)
2. grabbed the amss.mbn and dsp1.mbn (if you don't want to do step 1 then get the already extracted files here)
3. went into fastboot and flashed both of them
Dumb question, anyone know if it's possible to lose your carrier unlock when doing such things?
--------------------------------------------------------------------------
Now my streak doesn't boot, can't get to fastboot (pwr+camera), or recovery (vol+,vol-, pwr). Sometimes all three led's light up, and stay on and nothing happens, and sometimes the LED's stay off and nothing happens.
I tried using qdltool (vol+, usb connection to PC) , and it timesout after reboot ok message after I click RUN in qdltool. I installed both the qualcomm and dell fastboot drivers as per instructions, and I don't have a yellow ! in device manager.
Would appreciate any suggestions on what I should try next.
Click to expand...
Click to collapse
search for the QDL tool, follow instructions and you will be in business again.
I tried QDL tool, and it fails with a fastboot timeout error:
"wait ADB fastboot mode timeout!"
That means you dont have the fastboot driver loaded right.
First is the qualcom driver which you made through... after the small stuff loads. It then pops over to fastboot driver.
Try another driver or pc
Sent from my Dell Streak using Tapatalk
I download and successfully installed the Dell R288920 drivers.
Is there some other driver that works better?
i would remove fastboot drivers... reboot, use reinstall drivers and use a different usb...
are you running x64 windows by chance?
I have both a 64bit Win7 and a 32bit WinVista. I followed instructions on streakdroid.com to install qdl tool on 64bit, as well as trying it on 32bit, and they both fail in the same place.
Here's the tail end of the qdl tool log file:
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device .........
ERROR[D2]: wait ADB fastboot mode timeout!
Please check that device is exist and driver is properly installed.
Download Fail! - 2011/03/06 23:34:45
Elapsed Time: 30.55 sec
It may be the drivers or it may be the Streak. I have a Streak that isnt recognized as a USB device when plugged in and will not boot into fastboot mode (black screen) with the camera+power buttons. I have tried on 3 PC's(2 windows 7, 1 linux) and none will talk to it via ADB. However they will talk to my other working Streak so I know it isnt the driver.
I suspect it is corrupt NAND memory and have come to the conclusion that the only way to fix it is to get someone to JTAG reprogram it or swap out the mainboard. I would love it if someone can prove me wrong though...
BTW i bought this Streak in this condition so I dont know for sure how it got in this state.
your missing something.. def a driver issue says so itself.
do you get fastboot to work at all outside the qdl tool? if so can you follow the following guide?
http://forum.pocketables.net/showthread.php?t=8285
That's just it, the streak won't power up (pwr+camera), which would allow me to do fastboot outside of qdl tool.
Before I bricked it, I was able to run fastboot outside of qdltool all the time without any problems.
its not bricked... there is an issue with the timing of the driver kicking in or something driver related.. try another pc.
this is a pc issue.. not a streak issue. This part was always the biggest pain in my ass.. took me hours to get my system working right for this stuff.. the streak.. no issues....
i think the streak is unbrickable like the galaxy s phones.
I've tried both my PC's (desktop Win7 64, laptop WinVista 32), and both get the same error.
I've also tried different usb ports. When I first tried fastboot a couple of months ago, I was able to install the correct driver because I was able to start the streak in fastboot mode which then allowed me to install the driver on the desktop ( called android something if I recall correctly).
The problem I had with the QDL tool was the ADB driver also. The instructions I watched didn't include installing it, but did include downloading the folder that had it. If you are following the visual tutorial from the streakdroid website, go into all the folders you downloaded in the process. Somewhere in there is your specifc ADB driver. I was getting the ADB fail also until I found my driver and it installed. Good luck.
Sent from my Dell Streak using XDA App
I agree with the above post. You havent updated the correct driver. I noticed that when i searched through the recovery folders i notoced that the qcuser driver or whatever it was called, was in multiple folders....i experienced the same ADB error you did but i just kept switching with qcuser driver until i found the correct one. Go have a second look or third look....im sure ull find the right one.
Sent from my Dell Streak using XDA App
I've tried all three qcser,qcusb and qcmdm in the repairtool (qdltool) driver subdirectory for 32bit windows in winvista and wnet, with no luck.
Did any of you have problems putting the streak in fastboot mode independent of the PC, because that's not working for me. It used to work for me by pressing pwr + camera buttons.
I believe the ADB drivers were in the other folder you downloaded per the directions.
Also, I was able to get into fastboot prior to the QDL tool, but I don't believe that matters at all. The QDL tool is halfway there at the point it errors on you. You just need that correct ADB driver. You are so close, don't give up. Try the faq section of streakdroid.com
Furthermore, if you have access to an XP machine use it. You are almost back to Streakville.
Sent from my Dell Streak using XDA App
see if this helps:
http://forum.pocketables.net/showthread.php?t=8214
EUREKA!!!!.
Looks like the flashboot image on the streak was corrupt, so I was able to use streakflash to recover it.
Running nandroid restore as I type this. so hopefully I can get back in business.
Thanks to all of you guys for your suggestions.
I'll let you know if the nandroid restore is successful.
jfvidalc said:
EUREKA!!!!.
Looks like the flashboot image on the streak was corrupt, so I was able to use streakflash to recover it.
Running nandroid restore as I type this. so hopefully I can get back in business.
Thanks to all of you guys for your suggestions.
I'll let you know if the nandroid restore is successful.
Click to expand...
Click to collapse
What is streakflash? a new tool? like QDL?
Krad said:
What is streakflash? a new tool? like QDL?
Click to expand...
Click to collapse
See this page - it is a version of QDLTool that only flashes some files. I believe that it is used to repair the boot.img.
From this page:
Q: I’m trying to flash my Streak with the QDLTool but it keeps coming up with Error D2 ADB Timeout
A: This can be for a number of reasons. Firstly, look at what is displayed on the screen of the Streak:
Nothing / Screen is blank: This could be a sign of a corrupted fastboot image. Download streakflash.zip from the Downloads section and use the version of QDLTool it contains to reinstall the base images. You can then retry using QDLTool from repairtool.zip
Black screen, says “DT is in FASTBOOT_MODE”: This can be the sign of a driver issue – Try reloading the Fastboot/ADB drivers
White screen, says “FASTBOOT_MODE”: Go through the process again, this time using a different USB port.
Click to expand...
Click to collapse
Nandroid restore of streakdroid 1.6.0 successful.
I've been trying to upgrade to the more recent versions, but none of them (at least in my case) are as stable as 1.6.0.
1.6.1 with it's builtin perfmod is unstable.
Both 1.7.x and 1.8.1 are stable, but they suffer from the wifi/3g problem. Both wifi and 3g work, but I usually have to reboot to switch from one to the other, which is a hassle.
Yes, I've tried factory resets on all of them, but eventually, I either have random reboots, or FC's galore.
I know other people have gotten 1.6.1, 1.7.x, and 1.8.x to run stable, but I've had no such luck.
So for now, I'm sticking with 1.6.0 ( I get quadrant scores in the 1600-1700 range, which is pretty good).
Anyway, thanks again for all your help.
Related
Pretty sure the phone is toast, but wanted to confirm. I was erasing each of the partitions (boot, system, recovery, etc.) in order to write the latest Dell 2.2 packages, and after I erased each parition, my dog knocked my phone off the table, and the battery flew out.
Now it will not boot in any form (obviously because I blew everything away). I assume there is nothing I can do at this point, is that right?
Guess I will be sending it back to Dell.
Fixed it
I was able to follow steps found at whirlpool.net.au wiki dellstreak22 to correct the problem and get running again.
i'm in the same situation, no boot, fastboot or recovery. It remain with a black screen. I tried to use the guide but the Streak doesn't respond. Please give me an help
try that
whirlpool.net.au/wiki/dellstreak22
No luck
freepal08 said:
try that
whirlpool.net.au/wiki/dellstreak22
Click to expand...
Click to collapse
I have same problem.
I tried the thread above but when I try to install the Qualcomm driver on my x64 system (I followed certificate advice) I get an error message, the Qualcomm with ! mark changes to a com port with a ! mark in the device manager on the pc so I am not able to use the QDL. Get an error message that this driver is not for my system.
Can somebody please advice.....
Kind regards,
Pascal
freepal08 said:
try that
whirlpool.net.au/wiki/dellstreak22
Click to expand...
Click to collapse
the baseband upgraded correctly but my streak doen't go in fastboot mode it remain with the black screen. I think that is definitely bricked
since i somehow managed to lose the ability to connect via fastboot..
is there another way for me to install zips?
phone rooted with 1 click..
also open to ideas as to why fast boot only says < waiting for device > now?
no conflicts in dev mgr, have uninstalled and reinstalled the sync and driver..
removed from dev mgr..
updated while in fastboot mode etc..
no dice..
318-us
official 2.2 rom
att unlocked.
Black
can i convert a zip to a pkg and rename it update.pkg?
right now all i have is the pkg option when i hold the vol buttons and power.
i recently flashed to the new update which had fixes and newer baseband etc..
that went fine but the the steve 1.5 came out and i want to switch back.
as stated above thats not possible now since fastboot refuses to see my device.
Can someone put it in a pkg format for me maybe?
I dont like this official release...
its slow..it has lame apps, etc..
lil help?
dont really want to formate my laptop to fix a usb driver issue..
especially when the mass storage and sync work just fine..
+1
cant use fastboot after update to 318
rooted by super one click
black
unlock 00
there is a way of flashing custom recovery via terminal emulator. DEVICE NEEDS TO BE ROOT'D
save .img on to SDcard and rename to recovery.img
then open terminal emulator and type
su (press enter)
flash_image recovery /sdcard/recovery.img (press enter)
reboot (press enter)
I had the waiting for device problem. I read a few tips saying to try...
Type "adb devices" to see if its recognised there.
Make sure streak is the only device plugged in usb.
If using a hub try a different slot or direct into pc.
Turn streak off and into fastboot while still connected to pc (after pc loads drivers)
Reboot pc.
I swapped usb soccets and that fixed it for me
Hope one of these tips works for you too.
Thank you. I actually tried all of those things...before i posted.
wondering if maybe the 318 isn't compatible..
it says its in fastboot mode..
everything else works..sync, sd card shows in explorer etc etc..
just no fastboot.
luckily the recovery still allows me to do .pkg but i need zips too
very annoying..
I ordered a M11XR2 and will try with that when it arrives..
tina333 said:
I had the waiting for device problem. I read a few tips saying to try...
Type "adb devices" to see if its recognised there.
Make sure streak is the only device plugged in usb.
If using a hub try a different slot or direct into pc.
Turn streak off and into fastboot while still connected to pc (after pc loads drivers)
Reboot pc.
I swapped usb soccets and that fixed it for me
Hope one of these tips works for you too.
Click to expand...
Click to collapse
I have 318 and fastboot works for me.
I only had to reconnect the adb bootloader interface driver again (just like I had to the very first time).
It is just fine now...
http://forum.pocketables.net/showthread.php?t=8285
I've not had any issues with fastbooting, after installing 318, I've managed to flash clockworkmod aswell as the new Streakmod recoveries with my Windows 7 64bit.
reconnect the adb bootloader???
what do you mean?
you mean you plugged the usb cable in and ran fastboot?
lol
yeah..thats helpful
Radimus said:
I only had to reconnect the adb bootloader interface driver again (just like I had to the very first time).
It is just fine now...
http://forum.pocketables.net/showthread.php?t=8285
Click to expand...
Click to collapse
bigfoots1 said:
reconnect the adb bootloader???
what do you mean?
you mean you plugged the usb cable in and ran fastboot?
lol
yeah..thats helpful
Click to expand...
Click to collapse
NO....
The streak wasn't recognized on the PC in fastboot mode, so I went back to device manager and found the unrecognized android device and set it to use the bootloader driver... The same proceedure as was done the first time the streak was connected to a PC to setup fastboot.
Took almost 30 seconds to fix
as i said though.. i have no conflicts...
I can even remove it from the device mgr...put eh phone in fastboot mode where it is waiting for usb coinnection..plug the phone in.. iot installs the drivers then the phone sees this and shows fast boot...
so you would expect it to work right? wrong... it says waiting for device...
I have tried everything I can think of..
i got a good deal on a new m11xr2 with win 7 so i will have a fresh slate and will see what results i can get.
in the mean time.. how can i convert this steve 1.5.zip to a .pkg?
or even install it with some other sokution or method?
i have it rooted via one click...
i have root explorer...
what now? lol
there has to be a better way..
Radimus said:
NO....
The streak wasn't recognized on the PC in fastboot mode, so I went back to device manager and found the unrecognized android device and set it to use the bootloader driver... The same proceedure as was done the first time the streak was connected to a PC to setup fastboot.
Took almost 30 seconds to fix
Click to expand...
Click to collapse
Its easy to miss bits when its all going wrong so do check the sticky look here first for streak, I had to refer to it a few times. You definitely need clockworkmod or streakmod to flash updates. I believe you can do it via a terminal app with su privileges. There's a thread from a few hrs ago saying. I will find for you if you can't
Can zip be extracted and converted to .pkg?
Hell I would be content with just a way to install the performance tweaks...thats the main issue really...
Sent from my Dell Streak using Tapatalk
bigfoots1 said:
Can zip be extracted and converted to .pkg?
Hell I would be content with just a way to install the performance tweaks...thats the main issue really...
Sent from my Dell Streak using Tapatalk
Click to expand...
Click to collapse
I know Steve mentions "if you haven't flashed official dell update" blah blah... so im guessing you don't loose performance unless you manually downgrade? Have you seen the thread I mentioned? The OP claims he changed the dell .pkg to .zip and successfully flashed via clockwork..
http://forum.xda-developers.com/showthread.php?t=869076
how does that help me?
when i power up holding the vol up and down buttons i only get the install Update.pkg option and when i choose it it takes me to the blue text screen when i choose to either update via pkg or reboot. its the Android system recovery utility GAUSB1A131800
there is no option or way to get an option to install zip.
I would like to be able to install the performance fix for 2.2 zip or steves 1.5zip
so do you understand now?
I cant get fastboot to work to install clockwork.
I only have the recovery utility...
tina333 said:
I know Steve mentions "if you haven't flashed official dell update" blah blah... so im guessing you don't loose performance unless you manually downgrade? Have you seen the thread I mentioned? The OP claims he changed the dell .pkg to .zip and successfully flashed via clockwork..
http://forum.xda-developers.com/showthread.php?t=869076
Click to expand...
Click to collapse
it seems like i remember a thread about converting zip to pkg..
I cant seem to find it though..
if you just rename it in root explorer you get a signing validation error when you try to install it..
so I'm still stuck on stock 2.2
The initial thread is irrelevant, Have you not flashed a clockworkmod or streakmod previously? I would guess its possible to store a recovery.img on sd then flash via terminal app, i cant see why not? You could also probably use adb (if you cant connect to that the theres apps to do it wirelessly)
yes, i have flashed many times...
I flashed to 309 recovery in order to install the latest dell Update.pkg which went just fine. then when i went back to flash clockwork i could no longer connect via fastboot.
and thats where im at now..
cannot get fastboot to flash clockwork so i can install zips..
hence im asking for a way to do it without clockwork/fastboot until i get that sorted..
tina333 said:
The initial thread is irrelevant, Have you not flashed a clockworkmod or streakmod previously? I would guess its possible to store a recovery.img on sd then flash via terminal app, i cant see why not? You could also probably use adb (if you cant connect to that the theres apps to do it wirelessly)
Click to expand...
Click to collapse
an I still believe the issue is that you do not have the correct bootloader driver installed on your PC as described here:
http://forum.xda-developers.com/attachment.php?attachmentid=397078&d=1283901727
The issue is your PC, not the Streak (most likely)
Just got my streak yesterday, only had it a few hours and i've somehow managed to brick it already !
Started on the official 1.6, upgraded to official 2.2, rooted it, installed clockwork recovery. All was fine up until this point, i then went to install the performance fix http://forum.xda-developers.com/showthread.php?t=848487 but after doing so my streak stopped booting, since then its just hanging at the dell logo.
First thing i tried was restoring to the default recovery rom by holding power + volume buttons and option 2. This didnt work so i then tried this http://android.modaco.com/content/d...2-1-downloads-how-tos-rom-superboot-recovery/ and still no luck.
I've been at it for hours and its late so im giving up for now, i just hope the xda community can help me out.
Edit: I should add that the recovery image (option 2) is going through fine without errors, its only that when it boots it hangs at the dell logo. Also, fastboot is working so hopefully its not completely bricked. Is there anything i can do ?
get qdl tool and see if u can get to 305 stock
GET QDL TOOL HERE
Turn phone completely off, hold volume up and plug phone to computer
Open QDL Tool
if you have the correct driver, it will recognize ur phone
if not, the driver is included but u have to search how to install it
Hit Run and wait about 3-5 minutes
When its done it will reboot and be on stock 305 and then u can try again with ur update
Thanks just had a go at QDL but cant seem to get it to work. I got it to detect my phone as the Qualcomm HS-USB Diagnostics 9002 but after clicking run it just errors.
###QDLTool: M 2.7.4.8, build ID: 1.301.20101022, time stamp: Thu Apr 28 02:21:41 2011
Check image DBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dbl.mbn ...
Check image FSBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\fsbl.mbn ...
Check image OSBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\osbl.mbn ...
Check image AMSS: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\amss.mbn ...
Check image DSP1: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\dsp1.mbn ...
Check image APPSBL: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\appsboot.mbn ...
Check image DT: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\DT.img ...
Check image boot.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\boot.img ...
Check image system.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\system.img ...
Check image userdata.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\userdata.img ...
Check image recovery.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\recovery.img ...
Check image logfilter.img: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\logfilter.img ...
Check image Region: C:\Users\Mark\Downloads\repairtool\QDLTool3rd_20101022_GAUSB1A130500\images\RC_us.img ...
Check images: Partition Dbl Fsbl Osbl Amss Dsp1 DT Appsbl Boot System Userdata Recovery LogFilter RCFile
Check images ok
Download in speedup way
Open COM port success
OSBL version: 12-5035-AUSB1AM-09
osbl.mbn version:
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Baseband image version: M8650BAUSB1AM5035SIGN
Check device and image is Austin
Open COM port success
Check Secure Boot is enabled
#Set Fast Boot Flag success
Open COM port success
Test communication success
Check Secure Boot is enabled
#DBL to DDR success
#FSBL to DDR success
#OSBL to DDR success
#DT to DDR success
#backup FSBL to DDR success
Run HEX success
ERROR[D14]: Streaming hello Failed!
ERROR: Download fail!
Please remove the battery and try again.
Wait for modem set up ......
Download Fail! - 2011/04/28 02:22:01
Elapsed Time: 19.70 sec
After countless hours of going insane i have managed to get my streak working again using the o2 package (build 8105) found here http://android.modaco.com/content/d...2-1-downloads-how-tos-rom-superboot-recovery/
I couldnt get QDL to work for some reason so in the end i just downloaded the above package, copied to sd, renamed to update.pkg, powered on with volume buttons and chose option 2.
Its working now so thats the main thing, i was worried i might have bricked it for good ! Now i just need to get back to the official dell rom
If I wre doing this, I would get the multi_recovery tool. I would put the 351 package on your SD card
Flash the 351 recovery with the tool. Do not boot up go right into the recovery and point it to the 351 package. Make sure the 351 package has been renamed to the proper name. Either update.pkg or update.zip.
Worked like a champ for me.
Sent from my Dell Streak using XDA App
alperin1 said:
If I wre doing this, I would get the multi_recovery tool. I would put the 351 package on your SD card
Flash the 351 recovery with the tool. Do not boot up go right into the recovery and point it to the 351 package. Make sure the 351 package has been renamed to the proper name. Either update.pkg or update.zip.
Worked like a champ for me.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
That's the method that just broke my phone.
ducehlmg said:
get qdl tool and see if u can get to 305 stock
GET QDL TOOL HERE
Turn phone completely off, hold volume up and plug phone to computer
Open QDL Tool
if you have the correct driver, it will recognize ur phone
if not, the driver is included but u have to search how to install it
Hit Run and wait about 3-5 minutes
When its done it will reboot and be on stock 305 and then u can try again with ur update
Click to expand...
Click to collapse
Sorry but bug in but I'm having the same issue. I finally got QDL to work but after it finishes, the phone shows a screen with "Andriod system recovery utility
Press the shutter button to start emergency software recovery
Warning all data will be erased
Press the Volume up button to power off without recovering".
After I press shutter the it loads the update.pkg and then sits on the dell logo, and sits, and sits.
I'm now back on the official dell 2.2, in the end i had to flash the 351 recovery image to get the rom pkg to work.
I flashed the above recovery in fastboot mode since i cant get QDL to work, checked my drivers countless times, tried windows 7 64 bit and 32 bit, aswell as windows xp 32 bit. 64 bit always gives me the d14 error and 32 bit is the d2 error so i just cant understand why it wont work, surely it cant be a driver issue since fastboot works flawlessly and i've spent hours checking the driver now. Also i've followed the guide on streakdroid to the book so im pretty certain my setup is perfect.
Anyway, im happy with the official 2.2 for a while now but at some point i would like to try a custom rom through qdl, etc.
drkdeath5000 said:
After countless hours of going insane i have managed to get my streak working again using the o2 package (build 8105) found here http://android.modaco.com/content/d...2-1-downloads-how-tos-rom-superboot-recovery/
I couldnt get QDL to work for some reason so in the end i just downloaded the above package, copied to sd, renamed to update.pkg, powered on with volume buttons and chose option 2.
Its working now so thats the main thing, i was worried i might have bricked it for good ! Now i just need to get back to the official dell rom
Click to expand...
Click to collapse
That's it? WHen I installed the recovery from your link, after it said recovery install done(something along those lines) the phone didn't restart like it has with my previous recovery installs. I waited a few minutes, pulled the battery, and restarted into recovery, hit update and it has been a blank screen since.
I think I'm out of luck. I had the phone plugged into the charger all night and I'm trying to flash it now and the battery is at 0%. Can't charge it or anything. Time to call dell.
I'm having a problem using the following guide, and I can't seem to find anyone asking the same question...
http://forum.xda-developers.com/showthread.php?t=1622425
Following all the instructions, at step 3 in the directions, I get all the info from checking my SBK number, however the last two lines read: file not found bootloader.img, command failure bootloader download failed.
As there was no bootloader.img and I couldn't find any info on such a file, I pushed ahead, thinking this was common.
I can get into APX mode without issue, its the following steps where I seem to have a problem.
Using the first method listed in step 6, I am never prompted with a "press any key to continue", it just launches straight into attempting the install, and freezes installing (I forget the exact file name but I believe it's the bootloader, it is right in the beginning) it stalls at 131702/78908 (I think those numbers are right)
Using blackthun3r's tool renders the same result. I've tried everything can't figure it out.
I am on a stock 033.00_PA_CUS1 rooted using blackthun3r's tool, which worked perfectly...
Also, I never see the tab entering download mode when in APX it just sits with a black screen.
Anyone have any clue where I'm going wrong here?
Are APX/Download mode drivers installed properly
killdevilfalls said:
I'm having a problem using the following guide, and I can't seem to find anyone asking the same question...
http://forum.xda-developers.com/showthread.php?t=1622425
Following all the instructions, at step 3 in the directions, I get all the info from checking my SBK number, however the last two lines read: file not found bootloader.img, command failure bootloader download failed.
Click to expand...
Click to collapse
the most important thing at step 3 is having the tool "see your uid" the rest...dont worry about.....
I can get into APX mode without issue................
............Also, I never see the tab entering download mode when in APX it just sits with a black screen.
Click to expand...
Click to collapse
ok, you must ensure the apx/download mode drivers are installed.
For your tab to enter download mode it needs the apx drivers...you should see the windows new hardware wizard installing them, and check out the guide again there's a picture of where to look for them in Device Manager....
Yes APX mode is a black screen AND the white led is lit on the power button.
with the apx flash tool, did you install the .apx files from the guide?
thats about all i can offer, dont know anything about step 6.
just make sure u have the boot/recovery aka apx aka download mode drivers installed and installed correctly...good luck
Right Driver
The driver listed when I connect the device in ATX mode is "Acer USB Boot-recovery driver"... is this the correct ATX driver or is there another, as the image shows "Acer Picasso USB-Boot-recovery driver"
killdevilfalls said:
The driver listed when I connect the device in ATX mode is "Acer USB Boot-recovery driver"... is this the correct ATX driver or is there another, as the image shows "Acer Picasso USB-Boot-recovery driver"
Click to expand...
Click to collapse
That, is a very good question!!! I dont know whether there is a dedicated APX driver or whether its a generic term for the 'Picasso' drivers as seen in the image.
All I know is that if these 'boot/recovery' Drivers are not installed then the flash wont work. Keep in mind too, that these nvflash methods are fairly new to most of us, so we're all on a steep learning curve -
I'd suggest going thru the process again, write out each step in your own words if you need to, and take your time - it can be difficult relating the instructions your eyes see on screen with what your fingers are tapping out on the keyboard AND having your head trying to make sense of it all!!! Pick one of the methods, it doesn;t matter which, and stick with it - switvhing between 2 or more can make things even more confusing....
I;m about to go on try civs method now, will let u know how i go
***************************************
UPDATE
steps 1-2-3 check
on getting into apx mode noticed driverrs didnt install
but checked dev man and they were listed as Acer not picasso
ran nvflash
entered 1
entered sbk
command window says nvflash starting.......
that was it couldnt get any further....no entering download mode on tab
uh-oh -
***************************************
Yes- there is a dedicated APX Driver
***************SUCCESS***********
What a mish!!!! Got it going on the 5th time.....flashing r14 as i write...woohoo!
If I knew how to post images then I would...took screenies all the way thru.
Reinstalled all drivers after the first fail.
On next start found new hardware wizard wanted to install drivers for APX!!!!
I have never seen that before
After poking around a bit got them installed with...wait for it...under adb???
They installed as Acer "FastBoot Interface".....
It never showed in my system tray or as Picasso USB etc....in dev man
my next try failed again....waiting for tab to enter download mode......
For my last go at for the nite I bbutton comb'ed to APX first a
nd connected cable 2nd.....within a minute or two Acer Logo on tab
followed by :"entering download mode....within 10 mins I was good to go......
All I can tell you is to keep trying till u get it!!!!!
Probelm installing v3 bootloader/recovery
I have the same problem tried everything your not the only one.
shenny585 said:
I have the same problem tried everything your not the only one.
Click to expand...
Click to collapse
Driverz reinstall them......each time u attempt a flash and it fails at some point, you must reinstall them.
After poking around a bit got them installed with...wait for it...under adb??? They installed as Acer "FastBoot Interface"..... It never showed in my system tray or as Picasso USB etc....in dev man my next try failed again....waiting for tab to enter download mode...... For my last go at for the nite I bbutton comb'ed to APX first a nd connected cable 2nd.....within a minute or two Acer Logo on tab followed by :"entering download mode....within 10 mins I was good to go....
Click to expand...
Click to collapse
If they don't show up in either device manager (under adb/apx or USB controllers) or the system tray "safely remove h/ware then they are not installed, if u continue with flash and it fails then u have to reinstall Acer drivers again!!!
install a500 boot manager u can check for a proper connection with this tool....
See link in my sig for a pictorial showing step by step instructions for using apxflash tool
If this still does not work then post back with the following:
What rom and bootloader u have now or began with
What rom u installed at step 4
R u rooted and do u have a custom recovery installed
On validating yr sbk, at step 3, the most important thing here is to see the system info in the command window,
Boot.img errors u see at the end IS A NORMAL PART OF THE VALIDATION in other words its what you're supposed to see. Correct me if I'm wrong but at that command window aren't u supposed to type: go
I'd installed TWRP and was playing with some ROMs/Kernels when I hit a boot loop. I then used Flashtool ("Emma") to restore to factory. I haven't been able to send Fastboot commands since. I was wondering if anyone here might be able to point me in the right direction to help me sort this out.
When I connect the phone while holding volume up I still get a blue LED, but when I try to send a fastboot command besides "help", I get "waiting for any device" on Windows. On Mac, Terminal just hangs. I've been able to get the Mac to return the device ID using the "devices" command, but this is intermittent. Normally even this command causes Terminal to hang.
ADB debugging is "on". Flashtool works. ADB commands work. The phone can boot without issue. I can successfully get "fastboot help" to work.
What I've tried:
wiping the Mac HD, installing a fresh OS and installing the latest version of Fastboot from the SDK
Installing the Windows drivers directly from Sony and the latest Platform Tools directly from Google
Running "sudo fastboot" from Terminal on the Mac
Using various usb ports on both machines
Rebooting both machines between steps
Reflashing both Marshmallow and Nouget using Flashtool.
The USB cable I'm using is the one included with the phone. I could issue fast boot commands over this cable a few days ago.
Anyone got any ideas about what I've done wrong here? I'm really confused and I'd like to get rooted again if at all possible.
Try flashing stock firmware with Flashtool from Androxyde, not Emma if that may help.
ondrejvaroscak said:
Try flashing stock firmware with Flashtool from Androxyde, not Emma if that may help.
Click to expand...
Click to collapse
Thanks for trying to help me out!
So I tried flashing an Xperifirm stock ROM using Flashtool from Androxyde like you recommended. Unfortunately I get the error:
ERROR - Processing of system.sin finished with errors.
After this the phone will no longer boot. When trying to boot I receive the error message:
The software update failed. Make sure that your phone is connected to the computer and try again.
I've read that it may be a good idea to try multiple different images built from Xperifirm downloads, so I'll do that and report back what happens.
I got that error last time I updated, and was puzzled but tried to leave the phone in flash mode (green led) and flash it again. (I did not unplug the phone so I did not see the result of the first flash) This did leave flashtool without the initial phone info, checking for root and all that but this time the firmware flashed. I did include the fsc file into the ftf, I have no idea if it was a fluke or something but second flash with the phone already in flash mode worked. I know it sounds crazy but It might be worth a shot. Other than that it sounds like a bad cable with the inconsistent fastboot behavior but then again you could flash with Emma, which in turn should not affect fastboot. Odd.
88% said:
Thanks for trying to help me out!
So I tried flashing an Xperifirm stock ROM using Flashtool from Androxyde like you recommended. Unfortunately I get the error:
ERROR - Processing of system.sin finished with errors.
After this the phone will no longer boot. When trying to boot I receive the error message:
The software update failed. Make sure that your phone is connected to the computer and try again.
I've read that it may be a good idea to try multiple different images built from Xperifirm downloads, so I'll do that and report back what happens.
Click to expand...
Click to collapse
I would definitely try diferrent cable!
The Software update error means there is inconsistency in flash memory and bootloader fails to load initial image after flash. Also what may help, try to download firmware using Flashtool built-in Xperifirm, that is is called "Internal - Service Exchange Unit" and flash it first in Flashtool flashmode. Then let it boot and when it work, flash your desired version of firmware..
So I tried a number of images built from Xperifirm downloads and finally got one of them to flash properly. I'm not sure if this was due to the specific image or if I just got lucky, but my phone can boot again!
ondrejvaroscak said:
I would definitely try diferrent cable!
Also what may help, try to download firmware using Flashtool built-in Xperifirm, that is is called "Internal - Service Exchange Unit" and flash it first in Flashtool flashmode.
Click to expand...
Click to collapse
OK, I can try that. Just to confirm, is this a step that I should still take given that I can boot now? While I can boot, I still can't get into Fastboot through Terminal. I was successfully able to get a device ID using the "fastboot devices" command once, but running this command a second time caused a full system freeze on my desktop.
I've been able to use Fastboot again!!!
In case anyone else is unfortunate enough to come across this issue, it seems the solution was to reset the phone through Settings. (I have no idea why resetting the phone through settings would be any different than choosing to wipe via Flashtool though)
Thanks so much to everyone who helped with this! I think there's a good chance I'd still be stuck if I hadn't flashed the new image using Flashtool from Androxyde.
edit: I ran into this issue again and noticed that I missed a step in my original reply. In order to get Fastboot working again, I needed to connect using adb and tell the phone to remember my computer on the prompt.
88% said:
I've been able to use Fastboot again!!!
In case anyone else is unfortunate enough to come across this issue, it seems the solution was to reset the phone through Settings. (I have no idea why resetting the phone through settings would be any different than choosing to wipe via Flashtool though)
Thanks so much to everyone who helped with this! I think there's a good chance I'd still be stuck if I hadn't flashed the new image using Flashtool from Androxyde.
Click to expand...
Click to collapse
thanks for posting the cause/what you did to fix it.
it might help others, which is what the community is about.