Related
Hi all, first time poster here.
I need some help with my phone. I was trying to update my phone from build 347 which it came with, to build 351. I went with the method where you go into fastboot and flash the 351 recovery image onto the phone and then download and rename the update.pkg onto my sd card.
So now I start the phone up in recovery mode and choose the option to update via sd card. It goes through the whole process of verifying and installing. The phone restarts and asks if I would like to restore/recover my phone to 351, not sure if this is what's supposed to happen. I go ahead and it does it's thing. The phone reboots and now it hangs on the Dell logo so I pull the battery and restart. It tells me it's going to "start emergency recovery copy..." and I guess it tries to recover back to 347 because that's what it says.
I've gone through that about three times now. I try to go into fastboot and flash the 351 recovery.img again but now when I type the command, it gives me the error Remote: partition not found.
How do I get my phone up and running again?? Any help would be GREATLY appreciated.
edit: went and did a factory reset and now am able to flash recover via fastboot again. Still no luck starting the phone back up.
I was in the same situation. Had to install streakdroid to get my phone back.
Posted with StreakZilla, using XDA App.
Thanks, that's what I'm trying right now....
Hi,
recently i bought a retail dell streak.
it came with android 2.2.2 (stock).
i want to try streakdriod2.0, so i installed it.
i'm not satisfied with the performance, so i want to revert it back to stock(android 2.2.2).
I'm able to flash the dell recovery(351), then i'm downloaded 351 retail rom, from dell website.
After flashing the 351 ROM, it struck at dell boot logo, believe me i waited whole night in that screen.
Then i removed and reinserted the battery, then it shows a message like 'emergency recovery copy' then it will get restarted .
After that it will automatically takes me to the recovery. But the it will shows the recovery version as 347 ( i think it is reverting back to original (stock) recovery).Using the 347 recovery i flashed 351 rom, but the same things are happening again.
i've tried with all recoverys and roms, in xda form. none of them are working.
i've searched for 347 rom(which is the one i'm assuming as stock for me), but i'm not able to find any link for that.
Now i'm installed streakdriod 1.9 .
Is there any way for me to go back to stock os(android 2.2.2 ).
Sorry for my english.
Pls help me to get out of this problem.
This is an update to the post , as im describing the steps ive followed.
My device came with 347 (android 2.2.2) stock rom.(im not sure about this).
Currently i'm running streakDriod 1.9 ROM and StreakMod Recovery.
I'm trying to get back to stock ROM. These are the steps i followed.
1)Entered into fast boot, flashed amss.bin, DSP1.bin, and recovery for 351 official rom. And rebooted the phone.
2)When it reboots by pressing volume up and down at the same time, entered into recovery screen.
3)In recovery screen selected 'install update from SD Card'. It took me into the next screen.
4)Here it asked me to confirm the installation by pressing the camera shutter button. One more thing here is , i can see my recovery version as 351, which is good. Bcz installed 351 recovery via fastboot.
5)It will find the update package(351 official rom ) in SDcard and installs it successfully and reboots. Until now everything is working good as expected.
6)After reboot it will get struck at Dell Logo.
7)I removed the battery and reinserted. Once i turn on the phone, it will show a message 'Emergency recovery copy' and reboots. To stop this happening i tried to enter fast boot and recovery none them wont work.
8)After reboot it will directly takes me to the recovery second screen, where we need to press camera shutter button to confirm installation of update.zip like step 4.
Here i can see recover version as 347.That means device recovery got reverted back to stock 347.
9)if i install update(351 ROM) again here, it will install , reboots ,will struck at dell logo, we need to remove the battery, after inserting the battery it will show' emergency recovery copy' and reboots. Again i will come to the step 4.
It is like a cycle.
10)i tried with all versions of recovery copies and roms, which are shown in multirecovery thread.
11)I'm not able to find stock 347 rom, so i didn't tried with 347 ROM.
I think now i'm clear enough , so that everyone can understand my problem.
So what should i do. Help me.
my procedure is exactly like in this video, but the change is my device wont boot up, after installation.
http://www.youtube.com/watch?v=6Onq3qZaPF0
themaskofwraith said:
Hi,
recently i bought a retail dell streak.
it came with android 2.2.2 (stock).
i want to try streakdriod2.0, so i installed it.
i'm not satisfied with the performance, so i want to revert it back to stock(android 2.2.2).
I'm able to flash the dell recovery(351), then i'm downloaded 351 retail rom, from dell website.
After flashing the 351 ROM, it struck at dell boot logo, believe me i waited whole night in that screen.
Then i removed and reinserted the battery, then it shows a message like 'emergency recovery copy' then it will get restarted .
After that it will automatically takes me to the recovery. But the it will shows the recovery version as 347 ( i think it is reverting back to original (stock) recovery).Using the 347 recovery i flashed 351 rom, but the same things are happening again.
i've tried with all recoverys and roms, in xda form. none of them are working.
i've searched for 347 rom(which is the one i'm assuming as stock for me), but i'm not able to find any link for that.
Now i'm installed streakdriod 1.9 .
Is there any way for me to go back to stock os(android 2.2.2 ).
Sorry for my english.
Pls help me to get out of this problem.
Click to expand...
Click to collapse
Hi Mate,
Seems like you are stuck here. But don't worry the situation is not so bad it can be taken care of!!
I assume you already have the PKG of the 351 ROM which you tried installing.
Download the corresponding amss.mbn, DSP1.mbn and stock recovery.img
Once the download is done
Head to fastboot
Copy update.pkg to the root of SD (Make sure that the downloaded file is not corrupt it can also cause this issue)
Open Command Prompt with elevated permission
Set your phone into fastboot mode (Camera + Power Button) Tap on Fast Boot
Plug the USB cable into the system.
In command prompt go to the Fastboot folder
fastboot -i 0x413c flash amss amss.mbn
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash recovery 351recovery.img
fastboot -i 0x413c reboot
When the phone is rebooting immediately hold the Volume Up + Down keys to enter the RECOVERY
Select Software Update option and then at the Update screen press the Shutter Button to Start the Update
If everything is done as it is written, you will be back to stock
CHEERS MATE!!
GZSammy
Don't forget to hit the thanks button that's a lot of writing there!! LOL
@GZSammy Thanks for your reply
i'm gonna try your procedure.
I think flashing amss.bin and dsp1.bin will do the trick.
hi, can please give me any download link for amss.bin and dsp1.bin. im not really sure which version of them , i should flash.
i got the link for 351 file
im just posting them, bcz someone might need them.
http-://-mirror2.streakdroid.com-/manii/351/
remove - symbols
im struck again.
i'm happy that you are trying to help. i followed your procedure, but flashing amss.bin and dsp1.bin changed nothing.
i'm stuck at dell logo again and when i restarted my phone ishows' emergency recovery copy' and it will get restarted.
then it will take me to the emergency recovery tool , but i can i see that recovery version became 347 again.
Any better ideas ?
geo.samuel said:
Hi Mate,
Seems like you are stuck here. But don't worry the situation is not so bad it can be taken care of!!
I assume you already have the PKG of the 351 ROM which you tried installing.
Download the corresponding amss.mbn, DSP1.mbn and stock recovery.img
Once the download is done
Head to fastboot
Copy update.pkg to the root of SD (Make sure that the downloaded file is not corrupt it can also cause this issue)
Open Command Prompt with elevated permission
Set your phone into fastboot mode (Camera + Power Button) Tap on Fast Boot
Plug the USB cable into the system.
In command prompt go to the Fastboot folder
fastboot -i 0x413c flash amss amss.mbn
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash recovery 351recovery.img
fastboot -i 0x413c reboot
When the phone is rebooting immediately hold the Volume Up + Down keys to enter the RECOVERY
Select Software Update option and then at the Update screen press the Shutter Button to Start the Update
If everything is done as it is written, you will be back to stock
CHEERS MATE!!
GZSammy
Don't forget to hit the thanks button that's a lot of writing there!! LOL
Click to expand...
Click to collapse
Bruv,
Once you are done with the flashing of the amss and the dsp1 then the recovery, enter recovery and select the pkg to install... then it will state somethjng about the emergency software recovery press the shutter or the power button (dont remember which one) to start the installation.... happened with me in my earlier days i was sitting at that screen for hours and then i thought that it is screwed so attempted emergency recover... and the phone restarted with no changes... next run i was at the same screen and i discovered that after selecting the pkg we need to press power or i guess shutter button to initiate the installation... i guess u r facing the same issue..
If you are not sure which button to press, then press the opposite button stated for emergency recovery.
Eg. If it says press camera button for emergency software recovery then press power
And if power is written then press camera button.
And it will initiate the installation....
Sent from my Dell Streak while I was away from my Alienware
The only thing that I see missing is that when you finally try to reboot, no matter what you have flashed you need to do a Factory Reset, if not the Streak will not want to boot.
Thats also a good point..
Sent from my Dell Streak while away from alienware
steps i followed and making clear that what im facing.
My device came with 347 (android 2.2.2) stock rom.(im not sure about this).
Currently i'm running streakDriod 1.9 ROM and StreakMod Recovery.
I'm trying to get back to stock ROM. These are the steps i followed.
1)Entered into fast boot, flashed amss.bin, DSP1.bin, and recovery for 351 official rom. And rebooted the phone.
2)When it reboots by pressing volume up and down at the same time, entered into recovery screen.
3)In recovery screen selected 'install update from SD Card'. It took me into the next screen.
4)Here it asked me to confirm the installation by pressing the camera shutter button. One more thing here is , i can see my recovery version as 351, which is good. Bcz installed 351 recovery via fastboot.
5)It will find the update package(351 official rom ) in SDcard and installs it successfully and reboots. Until now everything is working good as expected.
6)After reboot it will get struck at Dell Logo.
7)I removed the battery and reinserted. Once i turn on the phone, it will show a message 'Emergency recovery copy' and reboots. To stop this happening i tried to enter fast boot and recovery none them wont work.
8)After reboot it will directly takes me to the recovery second screen, where we need to press camera shutter button to confirm installation of update.zip like step 4.
Here i can see recover version as 347.That means device recovery got reverted back to stock 347.
9)if i install update(351 ROM) again here, it will install , reboots ,will struck at dell logo, we need to remove the battery, after inserting the battery it will show' emergency recovery copy' and reboots. Again i will come to the step 4.
It is like a cycle.
10)i tried with all versions of recovery copies and roms, which are shown in multirecovery thread.
11)I'm not able to find stock 347 rom, so i didn't tried with 347 ROM.
I think now i'm clear enough , so that everyone can understand my problem.
So what should i do. Help me.
hi,
im explained the complete procedure above. can u tell me what im doing wrong .
and i think ur assuming that im not pressing the camera button in recovery screen. im doing it and im able to install the update package, but the problem starts after installation.
themaskofwraith said:
My device came with 347 (android 2.2.2) stock rom.(im not sure about this).
Currently i'm running streakDriod 1.9 ROM and StreakMod Recovery.
I'm trying to get back to stock ROM. These are the steps i followed.
1)Entered into fast boot, flashed amss.bin, DSP1.bin, and recovery for 351 official rom. And rebooted the phone.
2)When it reboots by pressing volume up and down at the same time, entered into recovery screen.
3)In recovery screen selected 'install update from SD Card'. It took me into the next screen.
4)Here it asked me to confirm the installation by pressing the camera shutter button. One more thing here is , i can see my recovery version as 351, which is good. Bcz installed 351 recovery via fastboot.
5)It will find the update package(351 official rom ) in SDcard and installs it successfully and reboots. Until now everything is working good as expected.
6)After reboot it will get struck at Dell Logo.
7)I removed the battery and reinserted. Once i turn on the phone, it will show a message 'Emergency recovery copy' and reboots. To stop this happening i tried to enter fast boot and recovery none them wont work.
8)After reboot it will directly takes me to the recovery second screen, where we need to press camera shutter button to confirm installation of update.zip like step 4.
Here i can see recover version as 347.That means device recovery got reverted back to stock 347.
9)if i install update(351 ROM) again here, it will install , reboots ,will struck at dell logo, we need to remove the battery, after inserting the battery it will show' emergency recovery copy' and reboots. Again i will come to the step 4.
It is like a cycle.
10)i tried with all versions of recovery copies and roms, which are shown in multirecovery thread.
11)I'm not able to find stock 347 rom, so i didn't tried with 347 ROM.
I think now i'm clear enough , so that everyone can understand my problem.
So what should i do. Help me.
Click to expand...
Click to collapse
At step 5, i would recommend once it reboots, press and hold the vol+ and vol- button again to go into recovery mode, then select option 1 to do a Factory Reset. Please do a backup just in case.
Another thing to try is, if you are back to StreakMod Recovery, boot into the recovery, do a wipe dalvik cache and wipe cache partition before flashing the stock recovery and rom. Again, please do a backup in case.
thanks for reply
maximoz said:
At step 5, i would recommend once it reboots, press and hold the vol+ and vol- button again to go into recovery mode, then select option 1 to do a Factory Reset. Please do a backup just in case.
Another thing to try is, if you are back to StreakMod Recovery, boot into the recovery, do a wipe dalvik cache and wipe cache partition before flashing the stock recovery and rom. Again, please do a backup in case.
Click to expand...
Click to collapse
i 've tried doing factory reset after step5, but it didn't help.
Is there anything else. i think i have two solutions.
1)Removing factory recovery (347)completely from the system. it may or may not solve the problem.
2)I need to find stock 347 rom, i think it will work.
I'm searched everywhere, but i couldnt find 347 rom.
is there any thing i can do for this problem.
themaskofwraith said:
i 've tried doing factory reset after step5, but it didn't help.
Is there anything else. i think i have two solutions.
1)Removing factory recovery (347)completely from the system. it may or may not solve the problem.
2)I need to find stock 347 rom, i think it will work.
I'm searched everywhere, but i couldnt find 347 rom.
is there any thing i can do for this problem.
Click to expand...
Click to collapse
finding a stock rom 347 is something which I guess you wont be able to do.
second option we already tried...i dont know why it is not working..
What i think is this that you need a Nandroid backup of a stock 351 0r 354 rom and you can restore the same from the streak mod recovery which i guess is already installed on your device...
Search in the forums I remember a guy asking for a nandroid backup files and someone uploaded it on a share....
Just check
If not then i will try to get you a nandroid image which I have but dont know where to upload...
geo.samuel said:
finding a stock rom 347 is something which I guess you wont be able to do.
second option we already tried...i dont know why it is not working..
What i think is this that you need a Nandroid backup of a stock 351 0r 354 rom and you can restore the same from the streak mod recovery which i guess is already installed on your device...
Search in the forums I remember a guy asking for a nandroid backup files and someone uploaded it on a share....
Just check
If not then i will try to get you a nandroid image which I have but dont know where to upload...
Click to expand...
Click to collapse
What else you an try is this that try any other retail dell rom probably 318 or any other build and if it flashes correctly and phone is able to boot, then try to install the later ones....my point is to get rid of any customization in the recovery......
I agree with geo.samuel, you have to get rid of custom recovery and make sure you are using the stock DELL recovery image so that you can flash an update.PKG instead of an update.ZIP.
It seems you are knowledgeable enough to get into fastboot, so go to the DELL Streak WIKI at this link
http://forum.xda-developers.com/wiki/index.php?title=Fileell_Streak.png
and download the recovery image and PKG of your choice (rename the .PKG file to "update.pkg"), I would suggest 354 or 351.
Flash the recovery image from fastboot (now I have a question, when you are in fastboot, do your commands take or are you just taking for granted that your computer is pushing the command?) I have to ask that, sometimes it won't take. If so, then execute the reboot command from the command terminal also.
As geo and others have said, when you see the DELL logo come up, push both camera buttons to get into recovery mode. Choose option 2 to find the update.PKG file you have placed on the ROOT of your SD card. Now at this point, if it allows you to choose the "update.pkg" file you downloaded. If it's asking for an "update.zip" file, then something in fastboot didn't succeed and you need to check your drivers and start with that process all over again.
Now, once you have gotten it to take the flash of the "update.pkg" file on your SD card it will reboot, now give it a few minutes, even if all was successful, it could take up to 15 minutes for it to get beyond the DELL logo. If it stays stuck there, then do a battery pull at least once more before trying to do a factory reset from the stock recovery.
Why is the OP not using MultiRecovery Flasher to flash his recovery image? He'd have a far easier time using that than manually issuing the fastboot commands. Plus it includes all the recovery images that are on the wiki.
Strephon Alkhalikoi said:
Why is the OP not using MultiRecovery Flasher to flash his recovery image? He'd have a far easier time using that than manually issuing the fastboot commands. Plus it includes all the recovery images that are on the wiki.
Click to expand...
Click to collapse
+1
Sent from my Dell Streak while away from alienware
geo.samuel said:
+1
Sent from my Dell Streak while away from alienware
Click to expand...
Click to collapse
for ur information im already using the multirecovery and im mentioned that. Ive tried using all roms and recoverys which are available in wiki.
themaskofwraith said:
Hi,
recently i bought a retail dell streak.
it came with android 2.2.2 (stock).
i want to try streakdriod2.0, so i installed it.
i'm not satisfied with the performance, so i want to revert it back to stock(android 2.2.2).
I'm able to flash the dell recovery(351), then i'm downloaded 351 retail rom, from dell website.
After flashing the 351 ROM, it struck at dell boot logo, believe me i waited whole night in that screen.
Then i removed and reinserted the battery, then it shows a message like 'emergency recovery copy' then it will get restarted .
After that it will automatically takes me to the recovery. But the it will shows the recovery version as 347 ( i think it is reverting back to original (stock) recovery).Using the 347 recovery i flashed 351 rom, but the same things are happening again.
i've tried with all recoverys and roms, in xda form. none of them are working.
i've searched for 347 rom(which is the one i'm assuming as stock for me), but i'm not able to find any link for that.
Now i'm installed streakdriod 1.9 .
Is there any way for me to go back to stock os(android 2.2.2 ).
Sorry for my english.
Pls help me to get out of this problem.
Click to expand...
Click to collapse
I don't see any mention of MultiRecovery Flasher here. In any event, when you flashed the recovery image did you boot back into StreakDroid, download the ROM, then go back into recovery?
What you should have done, at least according to Radimus' Guide to Flashing the Streak, is to have the update.pkg on the SD Card before flashing the recovery.img. That way, once the image is on the Streak you can simply hold down volume up and volume down while the Streak reboots. From there, you restore the ROM.
Check your drivers. Reinstall the drivers if necessary, and then follow the instructions in the guide.
Hello,
I recently tried to install custom firmware for my dell streak, However, my device
is android 2.2.2, and I tried to install superboot ver 2.1 (Cuz a misleading
comment on a web site mentioned its ok to root the system by it), my dell
suddenly rebooted in an infinite loop. I tried to enter the recovery menu by
holding the volume buttons and then choosing recovery. Also, I downloaded
Streak_309_11548_00.pkg and hoped this would work, but a stupid error
had occurred, bad, just bad file at the middle of verification process.
Anyway, I cant install clockworkmod because there is no way to root the
device, besides I dont have any back-up image of the streak.
please forum help me, the phone is almost new ( 2 tweeks of use only)
and I will pay if your solution work.
Regards and dont flame me, Im a new android user.
tried an older update, new error
Status 2???!!!
You do not have to be rooted to install a custom recovery. You do have to 'catch' the phone as it reboots by holding the volume up and volume down buttons as it reboots after the fastboot reboot command. If you let it boot into a stock rom the stock recovery will overwrite the custom ROM.
Use StreakMod Recovery if you want a custom Rom.
You need to slow down and do some reading before you go any further.
Suggestions;
Streak Wiki
Universal instructions for flashing any ROM and FAQ
Making a custom recovery stick
Using StreakMod Recovery
Do you know what baseband is on your phone? If you do DL the rom from the Streak WiKi, rename it update.pkg and put in on your SD Card, do not put it into a folder. Start recovery and select to install the update.pkg. You probably got the error when you attempted to use BB 309 because the recovery and the rom you attempted to flash did not match. They need to match so keep trying until you get the correct rom for the version of the recovery that is on your phone.
You could also use fastboot to install StreakMod Recovery, use the fastboot command to rebot the Streak, As soon as the reboot process starts hold down both volume buttons to get to StreakMod. If you use StreakMod you could install SimpleStreak or StreakDroid 1.9.1.
There are links to useful references in my signature.
Good luck.
PS - your Streak is not bricked as long as you can get into recovery, fastboot or your can connect to your computer and the QDLTool will see it.
Im in recovery menu now and If I click
Software upgrade via Update.pkg
the screen goes blank and then just nothing.
K clockworkmod works now
tell me what to do next.
I tried to install streakdroid 2 and its works WOW, thanx to you.
one last question how to install the latest baseband from the following link.
http://forum.xda-developers.com/showthread.php?t=1091236
sadly the link isnt available.
Don't worry about the latest baseband. If it boots up for you, I would stop there for now. If you were on 2.2.2, then you have either 351-354. Any of those will work for you.
tenorntex said:
Don't worry about the latest baseband. If it boots up for you, I would stop there for now. If you were on 2.2.2, then you have either 351-354. Any of those will work for you.
Click to expand...
Click to collapse
First, I would like to thank you and the forum for your help.
I have experienced a low graphical performance, and Im thinking to roll back
to the latest DJ_steave's custom firmware (2.2.2), However, I can access to
clockworkmod by pressing both volume buttons and then choose the recovery
option, thats weird since almost all tutorials mention that if you want to access
that mod, you have to press the volume up button along the power button.
For now Im waiting for a response whether to downgrade the firmware or
keeping the streakdroid 2.
Regards.
if everything is working then i suggest before trying anything else. do a nandroid backup first, (by going into recovery then advanced and then you see a nandroid backup option)
And i feel streakroid recovery package is preferred for streak as it is designed for streak only and works great.
lesson = homework
HI
I have read many of the Forums and seen Various Videos on how to install new ROMS onto the dell streak.There are dedicated members who contribute to these forums.i THANK THEM FOR THEIR TIME..I have a couple of questions ?
I have updated my streak from PKG 351 to 360 and this was straight forward and I did not need to change the recovery as I am from region 00
1.I followed all instructions and loaded Fastboot with Dell drivers but when I updated the recovery file there was no indication that this was carred out.
2.I know the next step is to update the PKG but I am not sure if the recovery was loaded.I looked at the information on the phone and its still E.U
3.I want to install Latest Olleh rom
Thanks
In recovery mode after you select "update from sd" it will show the version of the recovery.
You may try to flash over existing recovery even if its not 350, it will just fail. But it will no harm to your prone
Hi
I have used this as my guide
http://forum.pocketables.net/showthread.php?t=9694 ( I used XP before and could not get it to work.I am on windows 7 now and I got fastboot to work
Recovery IMG and PKG file is on SD card
1.Recovery file is run as and update Pakage ?
1. Verfy version of recovery - boot in recovery mode and choose "software update via update.pkg on sd card" (I've already flashed to 407 olleh, so I cant say what id got 350 recovery. You may ask someone who still got 350 recovery, or wrote it down)
2. If version is correct - flash.
Again - you may flash on any recovery, but success is guarantied only on 350.
Don't forget - YOU WILL LOSE ALL DATA EXEPT FILES ON SD CARD AFTER UPGRADE
By the way that guide is exhaustive
Hi
My issue was that I downloaded the IMG but did not run it as update.
I am running on 407.I wll see how this ROM functions and it might be time to add some custom Roms ;-)
It was easier using Windows seven when using Fastboot.
Thanks
Sent from my Dell Streak using XDA App
Trouble with update.pkg
I've tried 5 times to flash the 407 rom. I flashed the 350 recovery in fastboot. I put the 407 pkg on the root of my streak sd card,renamed it to update.pkg.Then booted into recovery and opted to apply update.pkg from sd. It says the update is applied, but just stays on Dell screen. The only thing I have done different from the guide is I havent been rebooting through fastboot, just pulling battery after recovery is flashed. Any ideas?
thomascw said:
I've tried 5 times to flash the 407 rom. I flashed the 350 recovery in fastboot. I put the 407 pkg on the root of my streak sd card,renamed it to update.pkg.Then booted into recovery and opted to apply update.pkg from sd. It says the update is applied, but just stays on Dell screen. The only thing I have done different from the guide is I havent been rebooting through fastboot, just pulling battery after recovery is flashed. Any ideas?
Click to expand...
Click to collapse
reboot via fastboot (fastboot reboot) and go directly into recovery by holding the volume up and volume down buttons.
If that doesn't work flash the 407 recovery instead, reboot using fastboot directly into recovery and install the update.pkg from there.
You mean the 407.pkg? I couldnt find the 407 recovery img
Marvin,thanks, apparently that last step(rebooting via fastboot and going directly to update was critical). I'm actually running Longhorn 2.1 v2 now and am liking it so far. I'll run it for a while.
thomascw said:
You mean the 407.pkg? I couldnt find the 407 recovery img
Click to expand...
Click to collapse
Nope - I meant the recovery. You can find it here.
thomascw said:
Marvin,thanks, apparently that last step(rebooting via fastboot and going directly to update was critical). I'm actually running Longhorn 2.1 v2 now and am liking it so far. I'll run it for a while.
Click to expand...
Click to collapse
Glad you got it sorted. FYI - when you want to thank someone for a useful post click on the thanks button for that post.
Trying the 407 recovery now, the 350 didnt work even when rebooting via fastboot. Im sure the proper recovery is being flashed as they ended in 35014 and 40714 just before flashing update.pkg. Still on dell logo, going to wait 5 more minutes. Does my phone being rooted affect anything?
finally got there, probably took 20 attempts. Was going from custom gb rom via streakdroid recovery. flashed streakdroid 1.9.1,then recovery 350 and 407 update.pkg,then factory reset . I do have flashing lights , so going to try reflashing bb
Problems in update
I have downloaded 407 and moved to my sd. I have then reboot to update the pkg. But I might unable to download any recovery both 350 and 407. Says content is not supported by this phone. The I have version 355 version. Pls help
I have got a stock 2.2 ROM, so I decided to update the PKG and recovery using Fastboot. I did the recovery bit fine but it's taking its sweet old time with the update.pkg, is this normal?
Btw, I'm in the UK so I got the latest O2 version 319, build 12792 which matches what it says in the about phone section.
Could be because I'm updating with the same pkg that it's not got anything to update, if that makes sense!?
If so, how do I know I have streakmod installed then? Can I remove the pkg file from the SD Card and try accessing the boot menu then going to option 2?
EDIT- It hasn't updated because when I try and update it again when there is no pkg file on the SD card, I get a blue message from Dell Update Utilty or something.
When I did try to update it, I had left it running for 30 mins but there was simply a black screen. The guide from-
http://forum.pocketables.net/showthread.php?t=9694
says it should take around 10-15 minutes though, so is this normal?
I rolled back from MMROM to NOTTACHTRIX Today and now my phone is stuck in CWM. (Cold Boot Android by selecting Boot Anroid NO BP option doesnt work either).
I have flashed MROM, Neutrino, NOTTACHTRIX, CM10.120120720 and all ended up into clockwork mod recovery. Kindly tell me an alternative -.- I am stuck with this from past 12 hours and no luck.
Update
I have managed to boot into android using Cold Boot without BP (i-e GSM radio will be disabled). I am recharging my phone battery and experimenting.
Before flashing NOTTACHTRIX, my phone had SKT version of 2.3.5 v167. I directly went for unlocking bootloader blabla recovery to get the NOTTACHTRIX working (thats like 4 months ago when I bought this phone)
So I tried going back to a version near 2.3.5 or higher. So going for 141 AT&T version didnt seem a problem for me except the .91 version bricks the device if u downgrade from 2.3.5 or above.
RSD Lite gave me 0x703e error and I couldn't flash the stop sbf.
Second resort I did was flashing 2.3.5 and 2.3.6 fruitcakes and still ended up in recovery.
I can only coldboot into android with Neutrino ROM other roms give me rebootloop when I choose coldboot.
I am suspecting a corrupted system or some kind of corrupt script in boot which keeps me in a loop into recovery. I did try adb script for ASUS TF101 to exit recovery bootloop but to no luck.
Also, I tried exitrecovery.zip flashable and still couldnt get into regular android OS.
This device is a headache for me now -.- and seemingly no one bothers to reply or to help me solve this issue >_>
Thanks for reading atleast
Update 3
Fixed it myself.
I downloaded fastboot, 2.3.6 fruitcake (system and boot), the older clockwork mod recovery, the one comes with Bootloader unlocking not some 5.0 version.
All I did was erased RECOVERY from fastboot, then boot and system. Frasled boot and system. Rooted with the bootloader unlocker package. Installed the old recovery and flashed NOTTACHTRIX.
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
mynonama said:
Did all rom u flash succesfull..or fail mount?
Can u mount/unmount system..data etc..
If no..then yr cwm was not fr yr models..try another version
Yr detail on process but without the error msg..if flash ok then should be boot if not it must giv aome error while falshing even its completed
Sent from my e2001v21_v89_jbl1a698_2g using xda app-developers app
Click to expand...
Click to collapse
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Please help...recovery bootloop
dark_prince said:
It was the bug of rebooting into CWM recovery and yes I was using right recovery for my Atrix i-e Rom Racers. Right now I am 4.x recovery and that works 100% to my needs on NOTTACHTRIX
And I flashed the fruitcake using fastboot. No flashing of stock sbf
Click to expand...
Click to collapse
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
noobButStudying said:
I have the same problem and tried several CWMs, and TWRP.
I can only boot to recovery, unless I try to boot with the BP HW Diag & Boot AP. Then I can cold-boot into Android, but with no USB support (so no ADB or charging capabilities).
I should have left my phone alone...I was running Nottachtrix just fine. Tried to flash CM 7 and then encountered this problem.
I have tried to restore, flashed new Roms, flashed new recoveries, flashed new boot.img, etc. No luck yet.
Tried the exitrecovery.zip, scripts to reset boot flags, full wipe and reload nottachtrix, flash radio, etc.
Still no luck.
Tried CWM version 4.xxx following instruction above, flashed fruitcake, rooted...still no luck.
Anyone have any advice?
Thanks in advance.
Click to expand...
Click to collapse
did you try the updated and usually standardly used CWM, 5.0.2.6?
palmbeach05 said:
did you try the updated and usually standardly used CWM, 5.0.2.6?
Click to expand...
Click to collapse
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
noobButStudying said:
Yes, thanks for the reply. I tried this one, and the CWM touch version advertised as designed for this phone model. No luck.
Aaaand.....I got impatient and tried to flash an sbf. Stupid, I know. Now, I have a shiny new brick.
Oh well, I ordered a new one from ebay, and I will spend my free time learning about possible ways to unbrick a phone.
Click to expand...
Click to collapse
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Resolved!
palmbeach05 said:
What's the msg that your brick is giving you? did you try flashing the pudding sbf and then trying to flash a custom ROM?
Click to expand...
Click to collapse
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
noobButStudying said:
So here's the full story:
It would boot up and say "failed to boot 1"
It would not boot into fastboot(power on while pressing vol down). When I tried to boot into RSD(power on while pressing vol up), it would give the same error and say "PWR REASON PWR KEY PRESS" and then say Fastboot Protocol Support.
Using RSD, it would recognize the phone as being in fastboot mode, and any flashes would fail...including pudding.
Using fastboot, it would connect but give errors if I tried to flash or erase anything, like it was locked. When I tried to unlock again, it would say " OEM unlock not implemented."
This is why I figured it was bricked...the bootloader seemed hosed. Couldn't use RSD, and fastboot was useless.
But...after screwing around with it (battery pulled and re-inserted while holding various buttons) while connected to RSD, I noticed that the same error was there but somehow RSD recognized it! (I think the magic combo was to hold power and vol up while actually inserting the battery.)
So I flashed pudding, and it worked! Re-rooted, loaded CWM (using auto unlock 4.2), and the phone booted to stock config. It was still acting flaky (I don't think the sbf had loaded right), and it was unable to boot back into recovery, but I flashed CWM again using rom manager and was able to do a full recovery!
Yay!! I am ridiculously happy right now!
Anyway, when my ordered phone comes in, I will have a spare to play with. This one is staying as is from now on. (until I get bored again)
Click to expand...
Click to collapse
The RSD issue and not being able to do anything. you are the 4rd person that i've dealt with to have that issue. we had a guy on here a few wks ago that me and andresrivas were trying to help. he wasn't getting the bootloop you were getting, but he had a very similar issue and had the RSD issue. like a wk later, i ended up having the RSD issue as well. Andresrivas also has experienced this issue. All i know is flashing that pudding is what saved us as well.
Idk what ROM you're going to put on there, but i would definitely keep that spare around. if your digitizer dies, you have a backup digitizer