Bought streak with 1.5 firmware from local craigslist. Tried follow upgrade instructions but unable to put phone in fastboot mode with camera + power option. That gives me white screen with 20+ testing options, no fastboot option there.
Also tried QDL option, Getting following error on run:
Send Security mode success
ERROR[DP1]: Partition table differs, override will be accepted!
ERROR: Download fail!
Please remove the battery and try again.
Wait for modem set up ......
Download Fail! - 2011/01/19 02:25:54
Is there a method to update to latest firmware? Help is appreciated.
Thanks
do you still have the dell streak
Why did you revive a nearly year-old thread to ask that? PM him next time.
For the record, since the OP apparently never got an answer to his question, he has an engineering Streak. Can't install StreakMod on it and can't upgrade it unless wanting to brick it. The only value is in the Engineering ROM.
Related
Hey folks,
So i got my Atrix from RMA today, it has a new mainboard, had WLAN errors before. Tried to unlock it with ihop_bell.sbf, like last time, but it failed. Now it says failed to boot 1, the bootloader is still locked, because fastboot does not know oem unlock.
I can enter fastboot mode. If I start and press volume down it says something about nvflash for 0.5 secs and turns off. RSD detects it as SE Flash Olympus and I can start flashing, but it always fails at "Switching to BP Pass trough mode".
So what now, is it hardbricked?
Before flashing did you check your FW version (i.e. Build number/version) to see what type it was, sometimes after installing new parts they will turn it on and test it to see how it works and may hit update while at it to make sure it is ready to go out of the box
Should be the German Retail 2.3.4, did not check it though. Just made sure the WiFi Error is gone.
Uh, you might have wanted to check. You always want to ensure software revision numbers before attempting the unlock. Even some retail updates can have minor build changes that could result in your bootloader unlock bricking your phone.
So moto-fastboot is not responding to the CMD "oem unlock"? I am just going over all the info to see if I can help, I have had the "Failed to boot #" issue with a multitude of Moto's (CDMA and GSM, and my global Photon) I have also been able to fix them. Was your device fully charged before attempting the SBF flash? that will kill an SBF flash and possibly the phone.
---------- Post added at 01:29 PM ---------- Previous post was at 01:20 PM ----------
It would also appear that FTB 1 is related to not having atleast 50% charge available during the flash. You may want to get a battery charger for it and charger the phone and attempt a flash from there. This thread has a little info in it (if you read the on topic stuff) http://forum.xda-developers.com/showthread.php?t=1491788 . Good luck my friend, I know how it feels, If you have any questions let me know.
Edit: If you can get fastboot to atleast give you info on any bootloader variables (fastboot getvar <variable request>) then you may be able to find out if their was a software revision, i am unsure at this time
OMG!
After I tried flashing the international unlock like 5 times more again and the same error ocurred, I tried to unlock in fastboot after ur last post and IT WORKED
TBH I am a little bit confused, because 1 hour ago it(the unlock) did not work and really can not understand what was wrong before. Still on the same battery.
Now it is unlocked and the message is gone, I can enter e.g. the RSD mode or the recovery.
Maybe it had to do with battery indeed, I dont know, just happy that it works again. Thanks for posting mate!
Haha, That's good. Hope it stays going well for you. I hated when I flashed pudding and it failed then ran the OEM unlock code just to see if it would continue, sure enough it did. Glad to hear it is fixed
SO, i followed a guide the other day to get lollipop on my wind huawei mate 2.
but now i want to switch back to the original android that came with the phone because i want to unlock the phone, and the lollipop one on the guide i followed doesnt show the unlock code entry screen when i put in a different sim card.
the issue i am having?
when i flash the stock recovery file that i found on here, that boots fine, then when i try to install B128 wind firmware, it says a bunch of error codes along the size of
oemsbl write failed something or other then it also said update_vendor.app install failed - invalid package
i'm hoping someone can help me because my phone will not go past the huawei logo at this point.
i do have access to fastboot mode though thank god.
if anyone can help me with the proper files to download and such that would be great!
mikeogden1981 said:
SO, i followed a guide the other day to get lollipop on my wind huawei mate 2.
but now i want to switch back to the original android that came with the phone because i want to unlock the phone, and the lollipop one on the guide i followed doesnt show the unlock code entry screen when i put in a different sim card.
the issue i am having?
when i flash the stock recovery file that i found on here, that boots fine, then when i try to install B128 wind firmware, it says a bunch of error codes along the size of
oemsbl write failed something or other then it also said update_vendor.app install failed - invalid package
i'm hoping someone can help me because my phone will not go past the huawei logo at this point.
i do have access to fastboot mode though thank god.
if anyone can help me with the proper files to download and such that would be great!
Click to expand...
Click to collapse
With NO stock backup i doubt it.
Dear Esteemed XDA members,
I have spent literally days of testing and researching to try and unbrick my phone. Friends and family have seen my obsession with trying to fix this, some even offering to buy me a new phone!!!! But this ain't about money - this is about having control of my damn device!!! I'm usually pretty good with trying to solve this kind of stuff, but this time I'm truly stumped (and desperate, and obsessed!). I have come to the conclusion that it's directly related to ARM Trusted Firmware. Here are the details of my "journey" to date... please read it, and if you know how to fix it, please share!!! then I can get my life back!!!! Before I go any further, I am certain that my problem was initially triggered by doing an official update on a rooted phone. So to avoid experiencing the same problem I'm about to describe, it's best to unroot and relock your device before loading new official firmware.
I have a Huawei Honor 4x (Che2-UL00, with Kirin 620 chipset) with an unlocked bootloader. Recently, I tried to manually upgrade from Kitkat (emui3.0) to Lollipop (emui3.1), using the official update.app from huawei's website (image was good - I checked the hash). To load the update.app, I used the official huawei recovery. The progress bar went to roughly 90% and then hung. Upon restarting my phone, it went into rescue mode with the following error: Func NO : 15 (bl31 image) Error NO : 1 (security verify failed).
Interestingly, I looked closely at the fastboot.img files for kitkat Vs lollipop (I got the image files by using HuaweiUpdateExtractor). I noticed that only the lollipop fastboot image contains this error message text. Also, bl31 is related to ARM trusted firmware, for more info search for BL31 (Secure Monitor) on google, or see bl31_main.c in the Trusted Firmware source code. So it seems that the lollipop image is using the full ARM trusted firmware, an extra layer of security which is preventing the (unlocked) bootloader from allowing me to load into recovery. I think this is the core problem, and I think there is a way to solve it but I just don't have a deep enough understanding to get there. Below I'll explain each step I went though and provide some additional diagnostic info:
1. First step was to access recovery mode (Vol UP + power). This failed and resulted in same bl31 error message.
2. Second step was to try and update again using the three-button force update (Vol Up + Vol Down + Power). It vibrates once after a few seconds, and freezes with the logo screen with the red light flashing. As an experiment, I tried this without the SDCARD and noticed it vibrated almost instantly, which suggests that it does try to load something from the SDCARD when inserted. I didn't get any further in this mode.
3. Final step I tried was to load into fastboot (Vol Down + Power). This worked and I got into a special "Rescue&Fastboot" mode. First thing I tried was to manually downgrade to kitkat by flashing the kitkat images using the fastboot flash command. The images boot.img, system.img, recovery.img flashed successfully. cust.img simply failed. I desperately wanted to flash the kitkat fastboot.img which doesn't contain the trusted firmware bl31 image stuff, but fastboot replied: FAILED (remote: Command not allowed). In fact, many of the fastboot commands fail with this same error message, even though there is the "PHONE unlocked" writing in red on my phone screen. With the limited command set available (even fastboot oem device-info is not allowed!), here is the diagnostic info I was able to get:
a) fastboot oem check-rootinfo
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1452356543
I think this change from RISK to SAFE is the core of my problem. the change_time is from several days ago when I attempted to update. I think it reflects the trusted firmware state (I'm guessing here, as I can't find documentation for these commands).
b) fastboot oem backdoor info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
I think that FB LockState: LOCKED means that fastboot is locked (guessing again, can't find documentation!), which explains why many of the commands fail.
c) fastboot oem check-image
(bootloader) secure image verify successfully
I think this checks the recovery image, because when I flash a different recovery, this signature check fails
d) fastboot getvar rescue_phoneinfo
rescue_phoneinfo: Che2-UL00 V100R001CHNC00B365
This appears to be the ROM version at the time of purchase.
e) fastboot oem get-build-number
(bootloader): Che2-UL00 V100R001CHNC00B384
This actually corresponds to the build number of kitkat I was using just before the failed upgrade to lollipop.
f) fastboot oem relock mycode
FAILED (remote: root type not allowed).
I tried this just to see if it wold relock. I'm not sure what the error means, but I do not that this command failed with signature verify fail if i change the recovery image.
Here are the questions I want to ask:
1. Can I force the device to flash a new image? I can't get into recovery or have full access to fastboot commands due to the trusted firmware stuff. And as I mentioned earlier the three button trick fails with a freeze at the logo screen. It appears that I need to do this using a means other than fastboot. The only interface I have is Android Sooner ADB Interface. adb devices renders nothing. Only fastboot finds a device.
2. Can I somehow make the "security verify check" pass so that I don't get that bl31 error? I'm not sure exactly which images this bl31 thing is trying to verify! Perhaps some combination of images from the new lollipop stuff I tried to flash and the kitkat build I had running previously?
3. Can somehow disable all this Trusted Firmware stuff??
4. Any other suggestions???
This is driving me to the brink on insanity!!! Gotta figure it out!! Thanks for reading and trying to help!
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
prezident36 said:
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
Click to expand...
Click to collapse
I still find it hard to believe this problem absolutely cannot be solved. However, I took it to a Huawei service center and they weren't able to unbrick it either. They had to replace the mainboard, which seems like a complete waste. Cost around $50, so not the end of the world but still annoying.
Anyway, screw this whole "trusted firmware" rubbish. I'm the owner of the device, yet I'm not "trusted".
hello, i have exactly the same problem!
---------- Post added at 10:58 PM ---------- Previous post was at 10:41 PM ----------
Where do i get the replacement mainboard from?
Me too, upgrading kitkat to lollipop. Now facing that rescue error.
My Honor 4X is unlock bootloader and root before upgrading lollipop,
Hello everyone,
I tried to reset my XT1068 phone from Motorola to the original system from Cyanogen mod. When I got the phone, there was already Cyanogen mod installed, but I didn't bought it myself.
After some tries I finally used a Version 5 (?) Android image. All the steps with mfastboot (v2) succeeded - also locking the bootloader.
However after restarting the phone I got ( and still get ) "failed to validate system image. ( fastboot reason: Fall-through from normal boot mode )"
and also "Device is LOCKED".
Why did this happen? Did I flash the wrong image? How can I find the one which fits to my system and the current bootloader?
And the most important part: How can I restore the system to a working state?
I don't want to unlock it using a code from motorola, because if I need support, it would be probably bad, if I voided the warrenty this way.
Is there (any) another solution without requesting a unlock code from motorola or without unlocking the phone again?
Any advice would be highly appreciated.
Thank you very much.
Kind regards
Greetings all, I have come to ask for advice on how to debrick my lg v60 version V600TM20n. First, how I ended up in this situation.
To begin, I followed this guide to unlock bootloader and root my phone then I followed this guide in an attempt to install a custom rom however, i did not get too far.
I tried to remove vbmeta verity as per the requirements of the form and in doing so input this line into my bootloader fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img with the file provided by this form I think this is where the issue I have is comming from but moving on.
I then attempted to download lineage os following the guide but it did not work and I was fed up by this point to I began the process of reverting everything I did. I downloaded SuperSu to deroot my device. After derooting my device I went to the bootloader and typed in fastboot oem lock, locking my device and dooming me.
In my attempts to escape from the hell I am currently in I downloaded LGUP v1.16.03 and v1.14 (I tried them both deleting the previous one before installing the new one) yet each time I was stuck with the this error code Error Code = 0x2000, Invalid command response when the progress bar reach 9%.
The dll i used is version 0.0.3.23 and the one provided by LGUP v.1.16.03, and the firmware I attempted to download was V600TM20n_02_TMO_US_OP_0111.kdz on LGUP it says V600TM20n oh and also I did try UPPERCUT, no resuts
Currently on my phone's download mode screen at the bottom in red it says Modified / E / L / RO / id : 3(NA2_US) I have also tried LGUP Cmd but same results
I have tried LG bridge but it says connecting and then no device found :/
I wish i could say i tried lg flash tool but i have no idea on how to use it
Possibly another big mistake (idk what im doin) I used the QFIL and restore the abl_a and abl_b to their original versions after locking the bootloader.
Please tell me if there is anything else I can do or if I now own a $300 brick. If I do have a $300 brick is there any value I can get from it to fund my walmart flip phone that I will have to buy?
unregisteredhypercam said:
Greetings all, I have come to ask for advice on how to debrick my lg v60 version V600TM20n. First, how I ended up in this situation.
To begin, I followed this guide to unlock bootloader and root my phone then I followed this guide in an attempt to install a custom rom however, i did not get too far.
I tried to remove vbmeta verity as per the requirements of the form and in doing so input this line into my bootloader fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img with the file provided by this form I think this is where the issue I have is comming from but moving on.
I then attempted to download lineage os following the guide but it did not work and I was fed up by this point to I began the process of reverting everything I did. I downloaded SuperSu to deroot my device. After derooting my device I went to the bootloader and typed in fastboot oem lock, locking my device and dooming me.
In my attempts to escape from the hell I am currently in I downloaded LGUP v1.16.03 and v1.14 (I tried them both deleting the previous one before installing the new one) yet each time I was stuck with the this error code Error Code = 0x2000, Invalid command response when the progress bar reach 9%.
The dll i used is version 0.0.3.23 and the one provided by LGUP v.1.16.03, and the firmware I attempted to download was V600TM20n_02_TMO_US_OP_0111.kdz on LGUP it says V600TM20n oh and also I did try UPPERCUT, no resuts
Currently on my phone's download mode screen at the bottom in red it says Modified / E / L / RO / id : 3(NA2_US) I have also tried LGUP Cmd but same results
I have tried LG bridge but it says connecting and then no device found :/
I wish i could say i tried lg flash tool but i have no idea on how to use it
Possibly another big mistake (idk what im doin) I used the QFIL and restore the abl_a and abl_b to their original versions after locking the bootloader.
Please tell me if there is anything else I can do or if I now own a $300 brick. If I do have a $300 brick is there any value I can get from it to fund my walmart flip phone that I will have to buy?
Click to expand...
Click to collapse
Here,try this copy.Make sure you delete all previous versions of LGUP.