Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.
This means you are on the leaked version now and there is nothing that can be done as of right now.
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.
sounds like you got a bad pb001.img file.
ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?
nevermind addressed my issue
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.
af man...seriously!
out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!
Related
Apologies for this stupid question resulting from a stupid mistake. Hoping somebody will be able to walk me through getting out of this.
I successfully rooted my sprint hero, then loaded modaco 3.0 (yes now I know that was bad). On reboot, the phone hangs on the black htc screen, and will respond to nothing.
The only thing I've been able to do is remove the battery, then turn it on in recovery mode. There, I did a wipe data/restore factory setting. Then I rebooted - and got the same boot screen, same problem.
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
When I try to restore, I get these:
(bart) error: run bart via adb
(nandroid) can't open file
Please help! I am out of ideas. Thanks very much in advance.
you'll probably have to take it back to the very beginning......
Get the Sprint RUU stock rom (a couple of posts below this one) and run that
then re-root your hero
Flash one of the roms ON THIS BOARD ONLY!!! Any other Hero rom is meant for the GSM version so it will give you the same headache again.
thanks
Thanks for the quick response! I'll try that.
Hmm, not looking good here. When I tried to install the stock hero RUU I got this error:
no signature
verification failed
which I presume is related to the htc sync requirement for that rom in the unrooting procedure that I did earlier.
Any idea for working around that?
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
david.danaan said:
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
Click to expand...
Click to collapse
Don't use 1.1, grab a later one.
Which recovery? 1.5.x won't let you go back to the main menu without disabling USB-MS again... I don't remember what 1.2.3 did. If worse comes to worst, reboot the phone after copying the file.
gu1dry said:
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
Click to expand...
Click to collapse
Yes, that's the one.
Using recovery 1.5.1. I can try a later rom, see if that works. I think I downloaded 1.3.
So first off yes, you aren't booting past the HTC screen because you flashed the wrong rom. However you aren't bricked. It's almost impossible to do once you're rooted and have RA's recovery installed unless you flash radios and stuff which you shouldn't.
Explanations for your other problems:
1. RUU doesn't work on the phones that are coming from the factory with 1.56. http://geekfor.me/news/sprint-ruu-fails/
There is a possible work-around but it's pretty detailed and I haven't gotten it to work. But you don't need to RUU if you can get in to RA.
2) (nandroid) can't open file is likely caused by RA 1.5.1. It had a bug that corrupted the backups. 1.5.2 is out. But for now don't worry about that cause your backup already sounds corrupted, nothing you can do.
3) can't open /sdcard/update.zip (bad). To me that sounds like your update was just corrupted.
How to fix it:
1. Boot in to recovery. With phone powered off hold your home button and then power.
2. Download fresh rom from http://geekfor.me/new-release/fresh-rom-1-0/ (what can I say... I'm partial. )
3. Within RA enable USB toggle and copy fresh rom to the root of your sdcard. Don't worry about renaming it to update.zip
4. Disable usb toggle. Go to flash zip from SD and choose fresh. That should be it. If you get the error saying the zip is bad then compare your downloaded copy with the md5 hash check on the download page (google it if you aren't sure how). If it matches then it's possible you have a bad sdcard. If it doesn't match then your downloads are crappy.
working!
Got it working by flashing the modaco v1.3a - must have been a bad update.zip before like you said. Thank you so much for the help and clear explanations, I was really worried I had bricked it.
David, now that it is working, I would recommend updating your recovery to 1.5.2.
I just want to thank everyone that posted to this reply I honestly thought that I bricked my phone and thank to you guys I was able to revive it. Thank you again.
Dont see this posted before...Mods please merge with any existing thread as you see fit.
If youre like me and want to install the update RIGHT NOW, then there are instructions at:
http://androidnetwork.org/forum/viewtopic.php?f=62&t=209
Download this file:
[link removed. please follow the original link above]
Then save on to your sd card, not in any folders, and rename it update.zip (windows users just rename it update, the .zip will come by itself)
1) Turn off your phone.
2) Turn on by holding down Power and the Trackball
3)Select Bootloader (Selection instructions on the top of screen)
4)Select recovery
5)An Android-Bot will come standing next to an open box
6)Press down Power and Volume Up
7)Select apply update.zip
8) Enjoy!
Click to expand...
Click to collapse
+
Only thing differnet was that on step 5, I got the android robot standing next to an "Exclamation mark in a triangle" (caution) icon. Simply pressed Power and Volume Up and got the option to install the update. click on update.zip. The phone will restart once and you will see the android outside a box, dont press anything.
Installed fine.]
Heres a thread in the Dev section:
http://forum.xda-developers.com/showthread.php?t=627533
Test results:
-Found that the total internal (app) memory is still 196MB and RAM is still 212MB, makes sense as the kernel is still .29, Have to wait for the next update I guess.
-No problems with any existing apps. (I did an Astro backup earlier anyway). Phone works fine too. (ATT EDGE)
-Multi touch works fine in the Maps app
-Looks like the Launcher2 FC bug is fixed, I could not reproduce the bug. (does not mean I'm leaving Home++ though )
Code:
Firmware version: 2.1-update1
Baseband version: 32.24.00.22U_4.03.00.21_2
Kernel Version: 2.6.29.01117-g4bc62c2
Build Number: ERE27
Thank You! Worked perfectly!
Worked great, thanks a lot! Does anyone know where to find the full changelog of this update? I can't seem to find one for the life of me. :s Thanks.
I didn't find one either.
Signature Verification Failed
I have a rooted Nexus One but no custom ROM installed on it. I pushed the Cyanogen Browser to gain Multi-Touch before the update came out. I downloaded the correct file and changed the name to update.zip on the top level of my SD card. I go into the booloader, then go to recovery, i get the android standing next to the exclamation mark and hit the buttom combination required. I select the update through SD card option and it starts then gives me a "signature verification failed" message. Any clue as to what I could do to apply the update?
ChrisM0678 said:
I have a rooted Nexus One but no custom ROM installed on it. I pushed the Cyanogen Browser to gain Multi-Touch before the update came out. I downloaded the correct file and changed the name to update.zip on the top level of my SD card. I go into the booloader, then go to recovery, i get the android standing next to the exclamation mark and hit the buttom combination required. I select the update through SD card option and it starts then gives me a "signature verification failed" message. Any clue as to what I could do to apply the update?
Click to expand...
Click to collapse
There are many threads in the dev section dealing with rooted phones.
http://forum.xda-developers.com/forumdisplay.php?f=559
I've updated this topic title to indicate its for stock ROMS only.
I get the same error with a brand new phone.
britoso said:
There are many threads in the dev section dealing with rooted phones.
http://forum.xda-developers.com/forumdisplay.php?f=559
I've updated this topic title to indicate its for stock ROMS only.
Click to expand...
Click to collapse
You seemed to indicate that his phone was rooted because he got that error. I have the same exact error and my phone is hours old with no root. Any suggestions?
Thanks
I have the same error, I can't seem to get the update installed.
alphonz said:
I have the same error, I can't seem to get the update installed.
Click to expand...
Click to collapse
Did you get the file from http://androidnetwork.org/forum/viewtopic.php?f=62&t=209 ?
Thats the one that I used.
Im having the worst time in the world trying to get this froyo for my evo. I have it in the root of the sd card, "O:" and removed known file extensions just to make sure its update.zip and not update.zip.zip.
everything is what it should be according to every post ive looked at. Yet no matter what I do, i still get signature verification failed, installation aborted.
Any ideas?!
I could the same thing last night. But what I had to do was to update to 1.47 then go in and update it another time name the file update and that is it. And it should work.
Sent from my PC36100 using XDA App
This is how it's done.
Follow the step by step directions I copied from androidpolice below. When you get to step 8, you will most likely see the red triangle with exclamation point. Don't worry. Just hold the up volume button and press the power key. This will activate the menu where you will see "apply update.zip". Proceed with step 8. It takes care of the rest.
We’ve provided some simple instructions for installing the update:
1. Download the update file and rename it to update.zip.
Note #1: DO NOT UNZIP THIS FILE
Note #2: Make sure you didn’t rename this to update.zip.zip by accident, if your Windows is configured to not show file extensions.
2. Place in the root of your SD card (connect via USB and mount as a drive, transfer via bluetooth, download directly on the phone – pick your poison).
3. Reboot into recovery mode (hold the Volume Up button while your phone is booting).
4. You will be presented with the boot loader. The Volume Up/Down buttons navigate the menu, and the Power button selects.
Note: you may see the red exclamation (!) point at this stage. Try mashing the up/down/power buttons and wait for 10-15 seconds. The recovery should eventually come up.
5. Select Bootloader.
6. Scroll down to Recovery and select it.
7. The phone will reboot again, this time into recovery.
8. Select “apply update.zip” or “install from .zip” (depending on your recovery image).
9. The installation process will take 15-20 minutes and a few reboots.
10. Enjoy!
i can get to that point just fine, its the install that fails due to signature verification failure, i have followed all the steps to prevent any mishaps, but still cannot get past it.
I think I had the same issue with the file after I renamed it update.zip (it was hidden and already there). I renamed it but did not help.
I would recommend deleting it from the card and downloading a fresh copy of the update. Copy it to the SD card and try again.
This is the source I used and it worked.
herehttp://www.megaupload.com/?d=LCONCXF1
xcodesterox said:
i can get to that point just fine, its the install that fails due to signature verification failure, i have followed all the steps to prevent any mishaps, but still cannot get past it.
Click to expand...
Click to collapse
You are probably going to need to download a different file, as a lot of the mirrors here are corrupted. If your file size is 70 something, that is corrupt. The correct file size is 80 something (sorry, I'm on my phone).
Look for a different mirror to download from.
Did everything and nothing, not even the (!) thing, everytime I scroll down to recovery it just takes me back to the main menu (bootloader) and nothing seems to work, am I doing something wrong?
yeah ive only downloaded the 84mb ones, i even had the original from HTC with no results. my evo refuses to evolve lol
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
fsuwade said:
I could the same thing last night. But what I had to do was to update to 1.47 then go in and update it another time name the file update and that is it. And it should work.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Im Hoping thats what the case is, I'm installing 1.47 now, if this doesnt work then im at a loss
well, no luck. i guess i have to wait till the 3rd
I had to remove all the excess files from my sd card root for it to finally work correctly. I think the only thing i had left on my sd card root were folders and the froyo renamed to update.zip
If you are rooted why not boot into recovery and install update from zip. Note that this option will un-root your phone in the process. There are also post on the forum with the stock Rom for non rooted phones, if you are not rooted. You can try using that file rather than the one you got. This may get u on 2.2 b4 u know it.
http://WWW.rootznculture.com
Kornsaq said:
I had to remove all the excess files from my sd card root for it to finally work correctly. I think the only thing i had left on my sd card root were folders and the froyo renamed to update.zip
Click to expand...
Click to collapse
I have many folders and I cleaned up the excess files, still though, no result.
thanks for the tip though, i got really excited to try that,.
jahnile said:
If you are rooted why not boot into recovery and install update from zip. Note that this option will un-root your phone in the process. There are also post on the forum with the stock Rom for non rooted phones, if you are not rooted. You can try using that file rather than the one you got. This may get u on 2.2 b4 u know it.
http://WWW.rootznculture.com
Click to expand...
Click to collapse
Im rooted, i tried being rooted, and unrooted. Ive been going at it since it released when i was at the movies.
thanks for the tip
Same problem
Hey xcodesterox.
I had the exact same issue and even download the linked file from ckombo.
I was finally able to get it to work.
What was happening for me was, I would download the file and my Mac is set to unzip a downloaded file from Safari, I would then just zip it myself after this. This was not working so I switched to Firefox, where I do not have it set to autoextract, and therefore I did not have to re-zip. THAT time it worked.
I hope you had the same issue.
Ok so you said right now you are in rooted. You should try removing all zip files that are current on the root of your SD card. U can back it up to your pc. Then use the file/ method found in this post. http://forum.xda-developers.com/showthread.php?t=740319
http://WWW.rootznculture.com
1:42am day two and im finally enjoying my fozen yogurt.
if anyone cares, i had to use the rooted version of this update, so its still a mystery as to why it wouldnt install. thanks for everything
I had some problems workign so i did this
1.did factory reset(backup date)
2.did the ruu 1.47 update
3.copy zip file to sd (drag and drop in windows, just dont drop into esisting file and dont unzip)
4.name the file update windows will add the .zip checkby right clicking on the file going to preferances then details tab (in win7 anyway)
5.power down phone
6.reboor by holding vol down and power wait for it to read you card
7.might get a cant open cache error, didnt prevent my update
8. using vol keys nav down to recovery, hit power button to select
9.vol down to highlight the update.zip file and powr to select
i was running 1.17 firmware so i had to update from that to 1.32 then 32-47 so check your version and update accourding, is it worth it? my bat life does seem a lil better flash is smother than the flash update i ran in 2.1, and browsign does seem smother, also landscape mode works in both left and right!
Where did you found this rooted version? I have the same problem...
How do I root this thing I've tried just about every tutorial I've seen they all fail either because of permission errors or update failed in the stock bootloader menu.
This is a brand new Evo that just came back into stock today.
Hardware 003
Software: 1.47.651.1
Build: 1.47.651.1
Baseband: 2.05.00.06.10
I just got this replacement due to my old phone being defective but no root methods seem to work correctly. Any ideas?
Just did it last night with my replacement.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=706411
Download your favorite ROM to your SD card.
Then follow this guide under recovery instructions: http://forum.xda-developers.com/showthread.php?t=690762
When you load it up, flash your rom you downloaded on your SD card.
Enjoy!
UrbanMuppet said:
Just did it last night with my replacement.
Follow this guide: link removed since I can't post them.
Download your favorite ROM to your SD card.
When you load it up, flash your rom you downloaded on your SD card.
Enjoy!
Click to expand...
Click to collapse
Tried that multiple times, it was the first method I used it copies the PC36IMG file then when it goes to check it it gives me a "Main version is older Update failed!" error, if I try to manually copy and do it by hand like I'm used to I get the same problem.
I don't get it.... Redownload it again, maybe corrupt/old? Make sure your version matches?
Download Simple Root, run the .exe and make sure your phone is in USB Debugging. It does it all for you. Once it's done you have a half-ass rooted stock rom. At that point power down and boot into recovery and run recovery-windows.bat and it loads a temp recovery. Use that to install whatever rom (Wipe first) and then use rom manger to install clockwork and enjoy.
UrbanMuppet said:
I don't get it.... Redownload it again, maybe corrupt/old? Make sure your version matches?
Download Simple Root, run the .exe and make sure your phone is in USB Debugging. It does it all for you. Once it's done you have a half-ass rooted stock rom. At that point power down and boot into recovery and run recovery-windows.bat and it loads a temp recovery. Use that to install whatever rom (Wipe first) and then use rom manger to install clockwork and enjoy.
Click to expand...
Click to collapse
You can't get past part one in simple root again when it copies the zip file from the simple root folder in adb (this is done automatically) and it attempts to scan the file in the stock bootloader I end up with a "Main version is older, Update Fail" error message, you cannot get past that at this point my only options are to either reboot or shutdown. Again it does not install the zip file like it's suppose to,I've rooted my old Evo countless times without the need for this simple root GUI stuff I'm perfectly capable of root in adb but again both give me the same error.
My guess is that you're trying to use the same PC3IMG in both parts and that's why you're getting the "Main version is older" error. You have to use the engineering PC3IMG in the second part, not the PC3IMG used in the first part (of toast's tutorial). You have to remove that one and rename the engineering version to PC3IMG and then run that.
Basically, read the tutorial and follow it exactly.
ultron said:
My guess is that you're trying to use the same PC3IMG in both parts and that's why you're getting the "Main version is older" error. You have to use the engineering PC3IMG in the second part, not the PC3IMG used in the first part (of toast's tutorial). You have to remove that one and rename the engineering version to PC3IMG and then run that.
Basically, read the tutorial and follow it exactly.
Click to expand...
Click to collapse
Nope wrong, I never got to part two since I never got part one to finish how could I use it twice if I couldn't even use it once? I knew exactly what was wrong the problem is I didn't know how to fix it. At least until I found this gem:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7410421
The fix is in the link above in case anyone has the same problem, note that this only really happens with the newer batches of Evos that have been patched to 1.47 by Sprint and you'll have to trick the phone into downgrading from 1.47 back to 1.32 and then back to 1.47 rooted again.
Hi fellow streak users. Hopefully I'm asking questions in the right place.
Background:
I have read a fair amount of threads on upgrading the streak. I had 1.6, GUASBA111100 (build 6267? from memory), and received the dell 2.2 update notification. Downloaded the update and selected it when it downloaded. The phone re-booted, then sat at a black screen. There it sat for many hours. I tried re-downloading the update many times, but it does the same thing.
I got sick of this and started digging on the web. A simple method seemed to be to rename the file Update.pkg and put it on the root of the sdcard. It then sits at the dell logo. Forever. I have downloaded more images, roms, recoveries than I want to admit. I have attempted following fastboot instructions. They all fail on the reboot.
Currently the phone will not start up at all. Is it really possible to brick the phone?
What I'm trying to do.
Given all the bad publicity I have read about the current 2.2 from dell, I am hoping to install steve's latest version. I am hoping someone has some time and patience to explain how to do this. (commands and which files to use) (as the phone does not seem to respond to all the methods flooding multiple forums).
If you need further information, please ask.
Try flashing the stock recovery for the 1.6 build you have then it should boot as normal. Make sure all the other versions you have are not in the "fastboot" c:/ folder.
OK, here's the update. It's a bit jumbled and random, but I have been up for at least 18 hours fiddling...
I was unable to find the stock recovery for the 1.6 build I had. Probably lots of mismatched files were flashed unnecessarily. Nothing would touch the 'carrier unlocked US version' I had. That is until I tried QDL tool upgrade M 2.7.4.8 Now I suspect it is a beta version of 2.2 that it puts on the phone. It's slow and featureless. But it was the only thing that worked. From there I managed to make clockwork recovery work, and worked my way from steve's 1.4.6 to 1.5.1 to 1.5.2 Somewhere here the phone chucked a spaz and I discovered my phone had been booted off the network (showed no signal coverage). I began to suspect something to do with the imei being blocked (Another streak I was playing with is locked to O2, but came with a rebelsim installed - apparently illegal in australia). I checked the IMEI and it had mysteriously changed. (I suspect it had somehow been put to all zeroes, and something somewhere had given it a 'different' one.) Anyway, I used the QDL tool again, and the original one came back.
Finally what worked for me: QDL tool to flash 2.2, flashthe new amss.mbn, flash clockwork recovery, put steves 1.4.6 on SDcard and flash, then flash 1.5.3
(I couldn't tell you where I downloaded the files that worked. Your results (people who are still seeking action to try and upgrade their software) may vary. All I can say is that now I have downloaded half the internet and installed all the computer drivers, I have hit on a combination that works for me on this computer).
Steve, Thankyou! It's fast, snappy. It has those settings I love to twiddle.
Thank you to everyone else that has either directly or indirectly helped me with your description of how you got yours working.
Thank you for the hosting of the ROMS. I like that you don't have to wait 45 seconds and/or join to download.
A few comments:
I downloaded so many roms and files that it wasn't funny. The problem is that they are all named Update.zip, amss.mbn etc. When they are all in the download folder... Some people just provided the files, others packaged them with a batch file to automate the process. If I was to download them all again, I would download them into folders labelling them...
There seems to be a wide variety of situations/variables that dictate 'what you need to do and how you need to do it' to change roms in the phone. There are half a dozen comprehensive guides on the net, yet all different. I was quite confused. It almost needs some sort of chart where you can pick where you are at the moment, where you want to be, then follow those instructions.
I was also bamboozled with the different tools. QDL, flashboot, ADB etc. I have a bit of an idea, but I'm sure others are equally confused. I know the information is 'out there' but to have it all in one place. What do some of the files do. Why might you need to flash them. Which files are erased by the stock ROM if you don't do anything with them. What does it do when you flash a recovery? How long does it stay on the phone?
There are several parts of the phone that get upgraded. Not sure I have it right, but QDLtool upgrades the modem software (amongst other things) Other things you change is the baseband, SDcard contents etc. (Trying to connect what software files go to what places to what hardware in the phone.)
I do have several questions that have arisen.
1. Am I right in thinking you must flash steves 1.4.6 before you can flash the latest 1.5.3?
2. QDLtools: In theory is it possible to replace the files somehow so it puts steve's latest ROM straight on?
3. Rebelsim: (The small amount of information I have suggests it is illegal in australia) Does it block or change the imei? Can the carrier tell if you are using one?? (not that I use one, apparently they don't work on 2.2)
(that's all for the moment.)
i have been having problems with doing my streak aswell and still am but
ato answer one of your questions that i found out while downloading the whole internet is that the QDL tool can be used to put steves on
here is the instructions i just copied off the qdl page i would of posted a link but i am a new member so i cant post inks yet
Beyond QDLTool
Using QDLTool will get you to a pre-release of v2.2. From here, you’ll want to upgrade to a newer release. The two options that people tend to choose from are to either go up to the official v2.2 ROM from Dell, or install DJ_Steve’s latest ROM.
Official ROM
If you want to go to the latest official ROM from Dell, simply set up your wifi connection, then go to Settings -> About Phone -> System updates. The latest update can then be downloaded and installed, updating your Streak.
Latest Streakdroid ROM
If you want to upgrade to the latest Streakdroid ROM (1.5.3), either from the QDLTool install or from the latest official build, you can follow these steps:
1.Go to the downloads section and grab StreakMod Recovery, the latest 1.5.3 Update and the AMSS for 1.5.1+ (the update and amss are under Roms, StreakMod Recovery is under Recovery)
2.Copy the update-1.5.3.zip file onto the root of your SD card.
3.Extract recovery.img from the StreakMod recovery and place it, along with amss.mbn, into the same directory as QDLTool (QDLTool has a copy of fastboot)
4.Shut down your Streak, then hold down the camera button (all the way) as you turn it back on.
5.The screen should turn white; press ‘Fastboot’ in the top right hand of the screen.
6.Plug in the USB cable – the Streak should now display ‘FASTBOOT_MODE’ at the bottom of the screen.
7.Open a command window and use ‘cd’ to change to the same directory as qdltool.
8.Run: fastboot -i 0x413c flash recovery recovery.img
9.Run: fastboot -i 0x413c flash amss amss.mbn
10.Run: fastboot -i 0x413c reboot
11.As the Streak starts to reboot, hold down both volume buttons.
12.The recovery menu should come up; select option 2 (Upgrade)
13.A Dell logo and an exclamation mark should appear; press power or menu to open StreakMod’s main menu
14.Select ‘apply sdcard:update.zip’ then ‘chose zip on sd card’
15.Find the update-1.5.3.zip file, select it and apply the zip.
16.When the update finishes, press back a couple of times then select the option to reboot your Streak.
17.The Streak will restart. It will take about 5 minutes to complete, but you are now on the latest v1.5.3
at moment i am following the qdl guide to getting the steve rom on my phone so will let you know how it has gone but with that guide the installation at moment seemed seemless now got to see if it goes off the dell logo after a while if not got to recovery but lets hope
no luck so far
stuck on the logo screen but asked for help now its a waiting game
Cheers for that!
Sent from my Dell Streak using XDA App
Is it necessary to use QDLTool to get to the pre-release 2.2 if I am on 1.6 or can I just follow steps 1-17?
The reason I ask is that QDLTool for me just stops at "Check version ... " so I have not been able to complete running it.
i dont know if it is necessary
are all the drivers installed?
i used to have a prob where it kept failing me but all i had to do was change usb port
and got it working but i was running 2.1 stock at the time but that was buggy and crap UI
have you tried just puting 2.1 or 2.2 on your SD card and updating that way
i finally got my streak sorted
i started from scratch
first i installed clockwork mod using fastboot
then installed very version of steves roms in order starting with 1.1.1
and worked my way down and when i installed 1.5.0 i then ran flashed the amss that is required if you want to get the newer versions then installed the rest of the updates and when i got to 1.5.3 i also installed the camera fix
i found it best to put all steves rom zip files onto your SD card at once then it saves having to keep putting one of after another
also after every update leave the phone for a few mins because it does take a lil time to sort the updates out
THE ROM UPDATES (at top also has the AMSS that need flashing)
http://streakdroid.com/?page_id=15&category=1
Camera fix and the comandlines for the AMSS update
http://forum.xda-developers.com/showthread.php?t=802405
clockwork
http://streakdroid.com/?page_id=15&did=9
I don't know if all the drivers are installed. Is there a way to check? I cannot even get into FASTBOOT (POWER + CAMERA) mode and the Streak is just in an infinite reset loop.
Just a note, the older StreakFlash QDLTool completes completely but the newer one in Repairtool just sits infinitely at "Check Version ... "
what operating system you using on your computer
rahbone said:
what operating system you using on your computer
Click to expand...
Click to collapse
Nice of you to ask, as indirectly that was the issue. I outlined it over at the forum mydellmini dot com. Sorry, cannot post hyperlinks as yet. Issue has been resolved. Looking now to load 1.5.3
why not spam a few more posts on here then u can do links when u want 2 in future
you just need 3 more posts i believe the you can do links