Dear All,
I have a Streak that originally dead by fastboot erase command, and after I found someone who can do JTAG for me, now I got a dell start to dell logo.
After I use streakflash(older version QDL) successful, I continue to repairtool and after everything go through successful without any error, my dell is still stuck at DELL blinking logo.
Any one have any idea on this.
One more issue, when I hold Camera + Power, it take me to a white screen with word "Touch Calibration", "fastboot" and a dialpad, but something straing is that there is a read line say "Default NV checked #3" and the screen actually is not touchable. Is all of your device got the same or just mind.
Please advise me some idea I may get my dell back to life.
Regards,
Possibly a bad internal Sd Card?
From the Streakdroid QDLTool faq:
Q: I’ve just flashed my Streak via QDLTool from repairtool.zip and now its stuck at the Dell logo. What could be wrong?
A: This could be the sign of a bad flash, or even a hardware issue. You can try performing a factory reset, in case its something simple. You can also try reflashing via QDLTool, in case it is a bad flash.
Alternatively it could be a sign of a hardware issue. There have been reports of a batch of Streaks that were released with internal SD card issues that start to fail when upgrading to v2.2. If you want to test to see if this is the case, you can do the following to test the internal sd card via the onboard diagnostics:
1. Turn off your Streak
2. Hold down the camera button all the way, as you turn on your Streak
3. At the white screen, dial in the code “*#301#” – This will open the engineering mode that allows you to run individual tests.
4. Dial in ’10? then press ‘Enter’ to run the ‘SD & SIM’ test
5. The “Internal SD” test should pass, and it should show “permanent write-nonprotect”.
Click to expand...
Click to collapse
That could be 1 of the reason.
This morning I try to do the *#301# and number 10, it show:
-CMD/Clock Test:FAIL
-CMD/Data Test:FAIL
-permanent write-nonprotect
But other issue, when I first enter to the white screen of Fastboot (the screen with the dialpad), there a RED line below the screen say "Default NV checked #3", and the screen is not touchable until I press VOL-UP or VOL-DOWN to calibrate the screen. It's happen every time I go there, I have to press VOL-up, VOL-Down and wait to see a new green word "PASS" below the word "Touch calibration" on the top left of the screen.
Do anybody got the same problem?
The new syndrome of my Streak after JTAG is the RED line in both FASTBOOT screen or RECOVERY screen. Is that happen to all that have been JTAG?
Regards,
I'm no expert, but it sounds like your internal SD card is somehow faulty and not keeping the setting when you calibrate.
Only other thing I may suggest is booting into DELL recovery mode, do a factory reset a couple of times and see if it will boot up.
You could also try to flash the ROM again
Haha, finally I got my DELL to work, and actually my internal SD is not fault, but it's MISSING, someone has take it out.
On the other hand, the same problem ask others who has JTAG their phone, the SIM card is not recognized anymore. We only can use PDA and luckily the Wifi is still work.
Thanks to all.
I too have same problem !!!!!!!
I got my dead phone JTAG after erasing files just like you.
I got it working after streakflash & QDL but I still get the RED LINE on white screen of FASTBOOT and I still have my phone locked with NO SIM CARD Message. It's been more than a month now for me.
It's because of the Service Tag # which is stored in BIOS has turned to 00000 after JTAG.I think the IMIE Number and Service Tag number both together somehow get the phone unlocked. If I put it to Android 2.1 it says more than 10 attemts have been enter unlock code and it can't be unlocked now. Except that WIFI/Bluetooth/SD Card everything else is working fine.
There is a RIFF BOX Support forum on GSM Hosting page where people are putting pressure on the RIFF guyz to release a new set of Pin outs for Dell Streak. Please post your comments there so that more number of people build more pressure on them.
QDL tool don't always work first time, i have had use it 3 times in a row before now to get a working phone
Related
Hi
When I turn on my phone all it shows is red, green, blue and white stripes across the screen with the following text:
ROSE100
SPL-1.54.0000
MicroP-Rose (LED) v10
MicroP-Rose (key) v5
PCBID 0x80
RID 0x0
At the bottom of the screen it also says "Serial", but displays no actual serial. Please see attached pic.
Please help guys. Problem initially started when phone collected dew on cold morning (camping).
Thanks!!!
You seem to be in the "flash screen".. I did that on my phone by accident, pressing power and one of the volume buttons.. Try pulling the battery out, put it back and see if it starts normally.
I have the exact same problem. Mine happened all of a sudden for no reason after turning my phone off and trying to turn it back on. Please post if you find a solution
Well, you can try to reflash your ROM. Many official ROMs can be found here.
Hi, I got the roms, but where can I read how to put the new one on my phone using my computer?
Ok, I got it I just run the .exe file to update my rom. However, there is just one problem, it says you should connect activesync to your phone. How tf do I connect activesync as my phone does not load any OS?! I tried without activesync but it doesnt work - it freezes on 0% update and after a while it runs some kind of recovery steps. So how do I get pass the activesync thing? Thanks
You can't upgrade ROM via activesync if u don't have acces to windows mobile, you can do it only from SD card.
Here http://www.megaupload.com/?d=M7OEOF2N (pass: xda) you find a Rose service manual and at the page 45 you find "ROM Image upgrade thru SD card" ...it's not complicated, read carrefuly.
Ok I read it but when I press the power button for the second time it says "No image file". I renamed the file to RoseIMG.NBH. What am I doing wrong?
I don't know what are you doing wrong ...try to rename the file to "ROSEIMG.nbh". Where did you download the ROM? ...I recomend you to put the same ROM you have on device because you don't have installed HardSPL (and I don't know if you can install it from SD card). Here http://forum.xda-developers.com/showthread.php?t=599520 are the officials roms for S740.
PS: I never tried this method on S740, I do it once on tytn II and works perfectly.
Here is how I got it to work:
Left it in the boot mode with the colorful screen until the battery is decharged enough, then tried to put it on again and it automatically turns off. So I put the USB cable in it and walla it started loading the battery and it turned on automatically and loaded WM. However, I still can not flush my ROM even through activesync.. but I am glad I can use it again.
something many forget with this fault, and I have seen quite a few is it is often not a rom issue but a hardware problem... in this case it may be a faulty up volume button, or maybe the plastic cap has shifted keeping the button held down, does the button still click ok?
The monet was a swine for the camera button giving up the ghost and doing nothing but dropping to boot loader......
Please help me, I played around with BBs yesterday and lost radio, so installed a stock FW with FlashTool, and got radio back again, but on some 4x BB.. Wanted the new 58 BB, and found out that a .. ..0.16 FW would give me that, so installed the polish one (found no other), and after that no response when touching the screen!
xRecovery is of course gone after "stocking" (also rooting?), but I have tried a number of FWs for FlashTool, and even FW directly from S-E using Update Service, but still my phone is next to bricked.. I am n00b and could very well have done something wrong unknowingly, and/or overlooked something, but what might that be, and what are my options?
Sounds like corrupted FW. Not a big deal cause without a cracked Bootloader, you realy can't screw the phone up.
Turn phone completely off.
Pop Battery - SIM card - Micro-SD card out.
Let it sit for a few minutes.
While your letting it sit, take your Micro SD card and Format it using your PC.
"not saying this is your issue but I have had the phone lock up and appear to be unresponsive due to a corrupt file on the SD Card and it fails to mount and gets stuck." If you have any files you want to save, copy them to your PC Hard Drive.
Reinsert your SD Card - Sim Card.
Plug your USB cord into your phone " LEAVE THE BATTERY OUT "
Start up SEUS " Sony Erricson Update Service ".
While holding the back button, reinsert the battery.
Follow the instructions and restore the phone to factory settings.
I hope this works for you as this should elliminate any problems that could have or would be occuring prior. If it doesn't, shoot me a mail and I will get with you on messenger for trouble shooting.
_-_- Press Thanks if its useful-_-_
Nope, didn't do it, touched the thanks-bottom anyway, because on my PC I can...
PM'ed xKrisx, but everybody are welcome with suggestions as I'm completely lost without my phone!
Edit while waiting, hoping:
Followed instructions above several times now, except
xKrisx said:
.. .. .. and restore the phone to factory settings.
Click to expand...
Click to collapse
no such option, wouldn't that be S-E-Android 1.6 ? In fact I see no other options in SEUS than accepting (or not) uneditable choices towards an update -and done-, so I suppose that's what was meant(?)!
Have tried a number of slight variations including SEUS update without sim and SD at all (was actually allowed that), but most noticeable difference was that first boot pre-choose English instead of Danish (my language), and still no response from touch screen, so can't select anything at all!
My phone shows evidence of "moderate physical pressure" (bought second hand with one corner missing), so I can't totally reject the possibility of a sudden HW digitizer breakdown though I think that would more likely have occurred while phone in use than while sitting on my mouse-pad.. No matter what, I would really like to exclude any SW related errors before moving to torx-driver surgery! Plz help guys!
Hi seek4
Did you ever find a solution for your touchscreen?
I have a Dell Streak which is on O2 (UK). Sometimes it will boot up and randomly turn off, and other times it reaches the O2 logo and then reboots. The battery works fine in another Dell Streak, so it's definitely a handset problem.
I tried updating the software (still on version 1, says version 2 is available), but it takes me to Dell's site and then tries to load Google's terms and has "%locale%" in the middle of the URL, which suggests to me the device doesn't know its own locale. I tried replacing %locale% with 'GB' and sure enough it loaded the page.
I have tried holding both volume buttons and powering it on, selected Factory Reset, which then shows the temporary white screen and tries to reboot, but then I just get a blank screen constantly.
Is the next step trying a reflash via USB? If so, is there any way I can flash it to O2 UK to retain the warranty?
blastcomms said:
I have a Dell Streak which is on O2 (UK). Sometimes it will boot up and randomly turn off, and other times it reaches the O2 logo and then reboots. The battery works fine in another Dell Streak, so it's definitely a handset problem.
I tried updating the software (still on version 1, says version 2 is available), but it takes me to Dell's site and then tries to load Google's terms and has "%locale%" in the middle of the URL, which suggests to me the device doesn't know its own locale. I tried replacing %locale% with 'GB' and sure enough it loaded the page.
I have tried holding both volume buttons and powering it on, selected Factory Reset, which then shows the temporary white screen and tries to reboot, but then I just get a blank screen constantly.
Is the next step trying a reflash via USB? If so, is there any way I can flash it to O2 UK to retain the warranty?
Click to expand...
Click to collapse
We have no way of telling you if it's under warranty withouth knowing when you bought it and what you have done to it.
But you need to flash the baseband files for your region then download the correct updated package for the baseband files you flashed, flash the ROM package and you should be good to go if you don't have a hardware problem. If you don't understand any of that, then you still have hours of reading to do
The only joy I've had is installing the O2 recovery image that was first released. That allowed the phone to boot up again, which hasn't happened in the past few days.
Then, halfway through downloading the official update, it rebooted.
I get the feeling the only way I'll get this working is if the phone stays on long enough to install the update, which is proving to be difficult.
Still having issues!
Every time I try to install Update.pkg, the LEDs flash for a few seconds, then the phone cuts out.
I've read that this means the baseband doesn't match -- but I've installed the O2 recovery.img?
Any ideas where I might be going wrong?
blastcomms said:
Still having issues!
Every time I try to install Update.pkg, the LEDs flash for a few seconds, then the phone cuts out.
I've read that this means the baseband doesn't match -- but I've installed the O2 recovery.img?
Any ideas where I might be going wrong?
Click to expand...
Click to collapse
OK, you have flashed the o2 recovery image, so are you sure that you are trying to flash the 319 ROM because that's the latest 02 as far as I can tell
I've flashed various recovery files and today I managed to keep the phone on long enough to realise the phone's build number is 3883 (it's still on 1.6 software).
So I put build 3883's recovery image on the phone and 3883's update.pkg on the memory card.
The phone starts flashing the update pkg and then turns off! I literally cannot flash this phone via memory card.
I've also tried other build versions to see if they'll flash (including the latest), but no joy.
Does this baseband make any difference? It's GAUSB1A110421-EU
The intermittent nature of this device in unreal -- I can only assume it's hardware failure as it went from turning off intermittently, to not booting at all, and now it won't turn on whatsoever, even into fastboot mode.
I officially give up and I'm sending the unit to Dell!
I have acquired a number of these streaks. problem is all are stuck at a lock menu asking for a password which i dont have. or they get stuck at the dell screen and wont boot. im currently running windows 8.1 and seem to have an issue with the devices being reconigezed not sure if its the phone itself or issues with drivers. i have tried multiplue drivers from dell and other various sites with no luck. ive tried factory resets on i have also tried to get it to boot from the extrenal sd card with no luck. can anyone help shed some light on this? the whole purpose of this is have a phone when i go to korea and for a OBD2 reader/tuner.
You're lucky. I occasionally check the Streak forums, but it's a dead device now as virtually everyone has moved on to something more capable.
Regarding the units requiring a password at the lockscreen, assuming this is the standard Android lockscreen, a factory reset should eliminate the password (hold volume+ and volume-, press and hold power). If it doesn't, flashing a stock ROM should definitely fix it. From what I remember, the drivers don't work properly on Windows 8 and later, meaning you'll have to find a machine with XP, Vista, or 7 to flash stock ROMs on any of these units, assuming the units frozen at the boot screen didn't have their storage spaces cleared with the fastboot -erase command. Fastboot -erase is pretty much a death sentence for the Streak, due to a bug. The storage areas get wiped, and then locked into a read-only state, with no way to correct it.
Share that info about an OBDII reader/tuner?
Hello guys,
I am really in need of help. For reason that does not matter any more I have tried to root my phone and now it is unable to start. I followed the steps listed in the below tutorial:
bbs.elephone.hk/thread-9919-1-1.html
However after following some steps, video tutorials and further confusions I ended up trying to "Firmaware Upgrade" my phone with SPFlash Tool, but unfortunately the process was ended prematurely and my phone is not able to start at all (black screen and no reaction from any button). I understand that everyone must take responsibility for the consequences followed by rooting a phone, but I wanted to ask you guys if I am able to recover the phone or I would need to buy a new one.
Here is more detailed information of what I tried and what is the problem I am experiencing:
- Error that I see when I try to "Format & Download" (or any other option / action that SPFlash tool has):
BROOM ERROR : STATUS_PRELOADER_INVALID (-1073545212)
[HINT]:
- What I tried:
1. Reinstalling the drivers because I tought that they are incorrect. Every downloaded dirver results to the same error and I believe that the issue is not related to the dirvers at all (I use Windows 7 Ultimate with the SP_Driver_v2.0).
2. Tried using different versions for SPFlash Tool, but it appears that only the latest ones works with the scatter file that I have (MT6755_Android_scatter.txt). Versions that I tried are - v5.1552; v5.1524; v5.1620; and after trying evrything I believe that the issue is not related to the used tool nor scatter file.
My conclusion is that somewhere along the way I re-formatted my phone, but since the processes ended prematurely this may have disrupted the correct format of the internal storage.
Is is possible to recover from this and if it is what steps / actions should I take to do so. I would really appreciated some help of you guys and will be glad if the phone is working back (promise to stop being a "hacker").
Best Regards,
A fellow that need helps or a new phone
I just wanted to add that I was able to recover my phone. YEY!!!!
For those of your who ran to the same problem here is what I did to restore the phone from the boot loop:
1. Remove the battery - this is quite a tricky part, but if you follow the steps and be careful there should not be any problems:
- Remove the back from the phone - since it is no meant to be easily removed you could use a plastic card and start from the top of the phone (where the ear jack is located).
- After that you would need to remove the top plastic cover - it is placed to protect the main board and all modules. You would need a small "Philips" screwdriver in order to remove all screws. Note that there is one hidden screw that is placed on the middle bottom part of the plastic cover. You could recognize it by the elephone logo placed on top of it.
- Once the plastic cover is removed you will see the connector of the battery. Remove so that the device is actually turned off.
2. Download a STOCK ROM for your device:
- The STOCK ROM for Elephone P9000Lite was downloaded from here:
4pda.ru/forum/index.php?showtopic=697579&st=20#entry47838700
All required images along with the scatter.txt file should present inside the downloaded archive.
3. Flash the ROM by using SPFlash tool:
- What I did here is to follow a tutorial that is specifically for hard bricked devices:
devs-lab.com/how-to-unbrick-mediatek-device.html
In my case I had to use the Format + Download option in SPFlash tool and select all images to be flashed. The important part was that the phone's battery had to be disconnected, all images selected by clicking the "Format + Download" option and finally hit the "Download" button. Once this is done you can connect the battery again and connect the device to your computer.
After the process is completed the device can be powered on and it should start booting.
I hope that I can help someone with these steps and that you do not give up on your phone.
Best Regards,
Happy fellow that resurrected his pone
I've bricked my other devices before and all i had to do to fix it, was remove the battery and format & download the original software. As you meantioned, with P9000 (same as with the Lite version), the problem is non-removable back cover and battery. Thank you for this tutorial, but it'd be better is somebody make a video tutorial or just add any media at all as many people might not want to do it, because of fear to break something under the back cover
Thanks for this, I am currently in the same position you were. I've cracked open the phone and am just trying to work out which connector feeds the power from the battery. I was pretty sure my problem was repairable so wasn't too stressed, but I hadn't thought to attempt to open the phone up like you did. It was surprisingly easy, and I don't think I'll have done any permanent damage. I'm hoping I can get the phone going again without any data loss, I was trying to flash recovery when I bricked it so hopefully I simply flash TWRP and she boots again.
awedxz said:
I just wanted to add that I was able to recover my phone. YEY!!!!
For those of your who ran to the same problem here is what I did to restore the phone from the boot loop:
1. Remove the battery - this is quite a tricky part, but if you follow the steps and be careful there should not be any problems:
- Remove the back from the phone - since it is no meant to be easily removed you could use a plastic card and start from the top of the phone (where the ear jack is located).
- After that you would need to remove the top plastic cover - it is placed to protect the main board and all modules. You would need a small "Philips" screwdriver in order to remove all screws. Note that there is one hidden screw that is placed on the middle bottom part of the plastic cover. You could recognize it by the elephone logo placed on top of it.
- Once the plastic cover is removed you will see the connector of the battery. Remove so that the device is actually turned off.
2. Download a STOCK ROM for your device:
- The STOCK ROM for Elephone P9000Lite was downloaded from here:
4pda.ru/forum/index.php?showtopic=697579&st=20#entry47838700
All required images along with the scatter.txt file should present inside the downloaded archive.
3. Flash the ROM by using SPFlash tool:
- What I did here is to follow a tutorial that is specifically for hard bricked devices:
devs-lab.com/how-to-unbrick-mediatek-device.html
In my case I had to use the Format + Download option in SPFlash tool and select all images to be flashed. The important part was that the phone's battery had to be disconnected, all images selected by clicking the "Format + Download" option and finally hit the "Download" button. Once this is done you can connect the battery again and connect the device to your computer.
After the process is completed the device can be powered on and it should start booting.
I hope that I can help someone with these steps and that you do not give up on your phone.
Best Regards,
Happy fellow that resurrected his pone
Click to expand...
Click to collapse
Hello all. I softbricked my phone while attempting to flash TWRP, and ended up with a phone that wouldn't present anything on screen. So I've located an old XP computer to rule out any driver issues, and using the battery removal mentioned above I was able to flash the factory 20160422 firmware which is what I believe my phone had before I started tinkering. I unticked the userdata box as I flashed it, and left the recovery box ticked which I thought would fix any corrupt recovery that my tinkering caused. The flash took some time, but I got the green tick indicating that it went well. However I still get nothing on screen, the only time I get anything is when I plug it into charge, I get a green battery charge icon for a few seconds before it fades away. If I leave it plugged in for a while, the screens starts to faintly flash sporadically. Does anyone have any advise for me? @awedxz, could you please confirm that the battery connection is on the far left, a shiny copper ribbon with a small silver rectangle plug that clicks into the board?
jiddahidda said:
Hello all. I softbricked my phone while attempting to flash TWRP, and ended up with a phone that wouldn't present anything on screen. So I've located an old XP computer to rule out any driver issues, and using the battery removal mentioned above I was able to flash the factory 20160422 firmware which is what I believe my phone had before I started tinkering. I unticked the userdata box as I flashed it, and left the recovery box ticked which I thought would fix any corrupt recovery that my tinkering caused. The flash took some time, but I got the green tick indicating that it went well. However I still get nothing on screen, the only time I get anything is when I plug it into charge, I get a green battery charge icon for a few seconds before it fades away. If I leave it plugged in for a while, the screens starts to faintly flash sporadically. Does anyone have any advise for me? @awedxz, could you please confirm that the battery connection is on the far left, a shiny copper ribbon with a small silver rectangle plug that clicks into the board?
Click to expand...
Click to collapse
Let it to charge more time
Thanks mate, this advise was spot on. It must have had 0% battery after fixing it! It's now alive and charging up. How neat that Mediatek devices can be unbricked so easily, although I'll have to be a bit more careful in future I think! My previous devices have been Motorola, HTC and Samsung devices, each with different tools and flashing techniques. Haven't bricked any of them in the past, but it's nice knowing this device will be hard to permanently brick.
chtsarts said:
Let it to charge more time
Click to expand...
Click to collapse
Had the same problem, a small cable that goes from the power button was disconnected. Connect the cable and it should run just fine
Just to chime in, I soft bricked my phone as well.
I managed to get it back to life, without taking the phone apart, so that is not a necessity.
Here's what happened: I had CM13 installed on the phone and wanted to go back to stock, so I flashed it according to the guides, also overwriting the preloader.
After that, the phone was dead, as in unable to turn on, no charger detection etc.
As is already known, this phone has an "emergency" line / device, that will turn on once you connect it to the computer and press the VOL+ button (the device will show up for a couple seconds in the Windows device manager).
So what I tried was to flash it again and again, to no avail; sp_flashtool reported the following error after trying to flash the preloader: "BROM ERROR - STATUS_EXT_RAM_EXCEPTION (-1073414139)"
Finally I tried different stock roms, from the Elephone forum.
The one that did the trick for me was the 20160304 - I loaded the scatter file into sp_flash tool and only flashed the preloader. After that, Windows suddenly recognized the phone as the preloader device, the screen turned on showing the charging image and the notification led lit up. I was able to flash the phone without errors again.
After that I flashed the rest of the stock firmware - without the preloader.
I then let the phone charge a little bit and it turned back on.
If that version of the preloader does not do the trick for you, try different ones.
No need to take the phone apart.
Good luck everyone!
For everyone's else information having this problem. I also bricked my P9000 whilst flashing TWRP and getting the RAM error. I tried every options possible but the only one that worked was to disconnect the battery. It is actually a very easy process as described as above. The battery connector is the small connector nearest to the volume buttons with the bronze coloured connector cable. It simply lifts up and your battery is disconnect. I changed the settings in SP FLASH to without battery and my phone flashed without any problems. Before this, it had been dead for over a week and all other methods failed to wake it up. Hope this helps.
---------- Post added at 11:36 AM ---------- Previous post was at 11:07 AM ----------
This video may help also
https://www.youtube.com/watch?v=irDOXh1QoKE
Hi everyone! I had the same problem (bricked phone not recognised by flash tool ecc ecc) and disconnecting the battery did the trick, but I may have messed up with some
The screen connectors and now the screen lits up but stays black. Sounds and touch screen work (I can unlock the screen because I hear the unlock sound), but the screen stays black... If I have damaged the connector (I think it's the one on the upper left, the thinner one that doesn't really click when inserted) there is not much to do, but I just wanted to know If anyone had the same issue and eventually resolved it.