So I wiped my phone and applied a TMO 1.6 rooted rom (http://db.androidspin.com/android_b...droid_developer_id=&NumberOfReleases=10&go=go). I then applied The expansion pack then rebooted with home+back. When the phone rebooted it cannot get passed an image of a package and an arrow towards a phone. When I remove the battery then replace it the phone turns off. When I plug the battery back it it wakes up and tries to resume the install process. I feel like I could fix the problem if the phone was not stuck at the install screen, but it is.
I tried booting with camera held down and dreaimg.nbh on the sd card but I get the same results.
What can I do about this?
Did you try to boot into recovery (Home + On)? From here it should be possible to apply the rom again.
mevets said:
So I wiped my phone and applied a TMO 1.6 rooted rom (http://db.androidspin.com/android_b...droid_developer_id=&NumberOfReleases=10&go=go). I then applied The expansion pack then rebooted with home+back. When the phone rebooted it cannot get passed an image of a package and an arrow towards a phone. When I remove the battery then replace it the phone turns off. When I plug the battery back it it wakes up and tries to resume the install process. I feel like I could fix the problem if the phone was not stuck at the install screen, but it is.
I tried booting with camera held down and dreaimg.nbh on the sd card but I get the same results.
What can I do about this?
Click to expand...
Click to collapse
Seems like you lost root access and might even have a brickm, but anyway is fastboot working for you? Maybe you can get adb working if recovery or fastboot are working.
Recovery mode and fast boot both do not work. Everytime I turn the phone on it remembers that it was installing a rom and stalls at some point.
Is it worth the time to figure out how to setup adb or do those two signs above show that even adb wont work?
Hiya all, I am quite desperate for help, I consider myself intermediate when it comes to dealing with android devices but I am well and truly stumped on this one.
I received a second hand streak from eBay yesterday, turned on first time and booted fine, running Steakdroid 1.9.0 by DJ Steve. I had a few issues with it reboot randomly or crashing, as it had Streakmod Recovery installed I did a full wipe all areas, reinstalled the Rom 1.9.0 and bit a factory reset on reboot from the Dell recovery menu.
All the device does now is reboot in bootloop on the dell logo it stall when it goes as far as booting or trying to load the Rom.
I ran the test in fastboot to test the internal drive as this is known to fail and both that and my SD memory passed the test.
I used fastboot and CMD to flash 4399 recovery image the OEM recovery image for the Rom Streak_104_4399_21.pkg I renamed this to update.pkg and rebooted the device into recovery where I then went to restore the original firmware (1.6) but as soon as I pressed the camera button to proceed I was greeted with a lovely black screen.
I left the device for about 2 minutes where it reset itself and just keep rebooting on the dell logo the restore did not seem to work, just to check fastboot and CMD was working as it should I went to reinstall the Streakmod Recovery image and sure enough it worked I managed to boot the device back into streakmod.
Unfortunately every time I try to install a custom rom they just do not seem to load the device simply stalls on the Dell logo because I cant seem to restore the original recovery image for the stock rom I cannot factory restore and nor will any custom rom boot.
All I have is access to fastboot and Streakmod recovery aaaah!!
If anyone can help me in the slightest I would well very, very, very much appreciate it!
As you have fastboot working, go to the wiki and download the recovery.img for the latest 360 rom, put the corresponding rom on your sd card named update.pkg and try to do a recovery by powering on device holding down volume up and down.
Flash then do a factory reset and you should be fine.
Streakmod is a great tool for flashing custom roms, not too many problems using custom roms, but you must use Streakmod with care, never use the factory reset option from within streakmod itself, this can render your phone a brick.
(InsertNameHere) said:
As you have fastboot working, go to the wiki and download the recovery.img for the latest 360 rom, put the corresponding rom on your sd card named update.pkg and try to do a recovery by powering on device holding down volume up and down.
Flash then do a factory reset and you should be fine.
Streakmod is a great tool for flashing custom roms, not too many problems using custom roms, but you must use Streakmod with care, never use the factory reset option from within streakmod itself, this can render your phone a brick.
Click to expand...
Click to collapse
Thanks for the reply here's my progress so far:
Flashed recovery image and loaded rom to SD card..... Booted into dell recovery and this is what happened
Finding update package
Opening update package
Verifying update package
Yellow bar 25%ish at this point
flashing lights
Installing Update
33%ish lights flash again
Yellow bar jumps 3/4 then fills screen, streaks screen goes blank/ off
Doesn't reboot/ cant turn on so I remove battery and switch back on and I am back to Dell logo then I get a picture of an android and another small progress bar that slowly fills and the device and it again reboots
Streak reboots again about 3 times like it is stuck in bootloop, I leave it and keep my fingers crossed I then get an animation of the Dell logo and glowing lights behind it.
Keep fingers crossed and sure enough it boots into the lock screen, I go to unlock it but it freezes and I get the flashing lights syndrome and the screen goes blank
Remove battery and switch on again, dell logo bootloop after about 8 or 9 bootloops it boots back up into the ROM above but then crashes once again...
Is it fair to say this streak has given up the ghost?
Flashing lights could mean baseband mismatch.
Try again, but be certain to use the correct recovery.img for the rom you are flashing, get the 351, 354 or 360 recovery.img that matches your choice of rom.
Make sure there is only 1 update.pkg on your microsd card, the one you want to flash, move all others, rename them or delete them. The Dell recovery always looks for update.pkg, nothing else.
Flashing lights could be something more major, but i still think its a baseband mismatch.
(InsertNameHere) said:
Flashing lights could mean baseband mismatch.
Click to expand...
Click to collapse
Honestly thats what I wanted to hear but what worries me is I downloaded the recovery and image from Wiki both relating to 360 will try flashing again I really do hope it can be fixed! Seems today is not a good day for me today many things going up the creek!
I am 75% certain if you flash it with the right update.pkg, that is a renamed 360 pkg you downloaded, you will have success.
When you flashed Streak_104_4399_21.pkg you were trying to revert to Android 1.6.
You may have to use the QDLTool to fix the Streak. I am not sure what problems trying an 1.6 build over an Android 2.2 build can cause. You may want to wait for some more feedback.
Start here for more info and try the links in my signature.
I dont believe you can downgrade directly from 2.2.x -> 1.6.
2.2.x -> 2.1 -> 1.6 might work but why are you doing this in the first place?
Just directly install 360 or the like
teaganravetta,
Does this sum up your situation?
1) you bought a used phone and it had StreakDroid 1.9.0 on it
2) because of issues with SD 1.9.0, you tried to flash Streak_104_4399_21.pkg, not realizing that SD is based on a newer stock rom
3) you then tried flashing bb 360
3) Now you are having issues with boot loops and phone won't boot?
marvin02 said:
teaganravetta,
Does this sum up your situation?
1) you bought a used phone and it had StreakDroid 1.9.0 on it
2) because of issues with SD 1.9.0, you tried to flash Streak_104_4399_21.pkg, not realizing that SD is based on a newer stock rom
3) you then tried flashing bb 360
3) Now you are having issues with boot loops and phone won't boot?
Click to expand...
Click to collapse
Yes thats exactly what happened and in that exact order I am guessing this means the worse, am going to try for the 3rd time now reflashing 360 so fingers crossed
teaganravetta said:
Yes thats exactly what happened and in that exact order I am guessing this means the worse, am going to try for the 3rd time now reflashing 360 so fingers crossed
Click to expand...
Click to collapse
I'm not going to tell you anything different than anyone else, however I am going to give you links to the exact files you need so there is no confusion.
Download this:
http://mirror2.streakdroid.com/manii/360/recovery.img
This is the recovery image for 360. Save it in the folder on your computer that has fastboot.
Now download this:
http://mirror2.streakdroid.com/manii/Streak_360_17397_00.pkg
Rename this to Update.pkg and place in the root of your SD Card. (ensure there is no other Update.pkg on your card)
Power off the phone, if not done already.
Hold the power and camera button down until you get a white screen. Click on fastboot on your phone. Wait 10 seconds.
Plug it into your computer with the usb cable.
Wait for it to say fastboot ready (or something similar).
Now flash the recovery.img using the following command (This command assumes a Windows PC):
fastboot.exe -i 0x413 flash recovery recovery.img
When both your computer and the phone says it was successful, complete, or whatever, pull the battery.
Replace the battery, hold both volume buttons along with the power button.
In the menu that opens, choose the second option. Let us know your results.
I only added this post in case their was confusion over which files were actually needed. No need for a separate baseband, dsp1, or anything else. These are all included in the pkg file.
many thanks for all the help, so far I have downloaded "QDLTool3rd_20101022_GAUSB1A130500" turned off driver signing as I am x64 all ADB drivers fine and COM ports okay have restored via this tool according to the log successfully.
Phone rebooted a few times it has paused on the Dell logo for a moment but the guide did say anything up to 10minutes for first boot so I am holding for the moment to see if this has cured it otherwise I will report back and re download the above files and try that!
It takes me a while because I am out in the sticks I only have a 60kbps download speed (yikes) I know!!
Because your first attempt at flashing a stock ROM was the Android 1.6 version I am not sure you can just flash 360 at this point. I think you have to use the QDLTool (repairtool), but I am not sure. Try searching for the procedures that were used to upgrade from 1.6.
Edit to use the QDLTool:
In this post DL under commonly downloaded tools get Fastboot/ADB utils + drivers for Streak 5/7 and Venue and QDL Tool.
Then download qdltool-tutorial.zip from this page. unzip the tutorial and open it with a browser that supports flash or other flash viewer.
After using the QDLTool let the Streak boot and then flash the 360 recovery file and the 360 ROM. You must not let the phone boot completely after flashing a different recovery or the phone will restore the one that came with the ROM currently on the phone. Read this.
You can find more info about QDLTool by searching. As I said I think that is what you need to do.
lordmorphous said:
I'm not going to tell you anything different than anyone else, however I am going to give you links to the exact files you need so there is no confusion.
Download this:
http://mirror2.streakdroid.com/manii/360/recovery.img
This is the recovery image for 360. Save it in the folder on your computer that has fastboot.
Now download this:
http://mirror2.streakdroid.com/manii/Streak_360_17397_00.pkg
Rename this to Update.pkg and place in the root of your SD Card. (ensure there is no other Update.pkg on your card)
Power off the phone, if not done already.
Hold the power and camera button down until you get a white screen. Click on fastboot on your phone. Wait 10 seconds.
Plug it into your computer with the usb cable.
Wait for it to say fastboot ready (or something similar).
Now flash the recovery.img using the following command (This command assumes a Windows PC):
fastboot.exe -i 0x413 flash recovery recovery.img
When both your computer and the phone says it was successful, complete, or whatever, pull the battery.
Replace the battery, hold both volume buttons along with the power button.
In the menu that opens, choose the second option. Let us know your results.
I only added this post in case their was confusion over which files were actually needed. No need for a separate baseband, dsp1, or anything else. These are all included in the pkg file.
Click to expand...
Click to collapse
Thanks, this got my problem solved (endless boot logo issue with Simple Droid rom), however I am left with a no cell tower reception ?
I flashed the official stock unlocked retail rom ? still no tower reception ?
Try Simple Streak 1.2 , as i had this problem yestrday , but for simple streak 1.2 everything Worked Fine , just goto its thread and follow its instructions and u wll hve 2.2.2 in 15minutes , hit thnx if this helps
I just partitioned my SD card and flashed a new rom (RunnyBliss HybriD) tonight. Everything was working fine, I just reinstalled all of my apps and everything was perfect. I went to unplug my phone from the computer (which was on charge only) and just unplugged it. After that, all of the apps I downloaded were gone and the home screen pages that I just setup were gone. I decided to reboot and see what happens and to my surprise it wouldnt boot back up. It is stuck at the white "htc evo 4g" screen. I tried to boot into recovery and it vibrates 3 times and then does nothing. I assume that the phone was actually in USB mode and I corrupted the usb by removing it without ejecting it. Long story short, I have an Evo that doesn't work and I dont know what to do. My computer wont recognize it so I cant access the SD card. Please help.
Correction: If I press volume down I can get into hboot. What do I do from here?
try to install a recovery via the bootloader
How would I do this?
npreisler08 said:
Correction: If I press volume down I can get into hboot. What do I do from here?
Click to expand...
Click to collapse
I'm kind of new to this but, in HBOOT there should be a recovery option, select that and recover the latest backup.
EDIT: If Recovery doesn't load then I'm at a lose, sorry.
I figured it out. I got a new micro usb and placed AmonRA on it and then booted into recovery, then went to usb mode and dropped a new rom on it and flashed. Big bam all fixed
I have an A500 that was originally purchased in Thailand. I contacted Acer Thailand and they provided me a recovery package to install. I put this on a FAT32 formatted Micro SD card and it installs, but when the tablet reboots itself it gets suck on the screen with the silver "android" logo.
I've gone also some of the advice in this thread as well: http://forum.xda-developers.com/showthread.php?t=1874345.
So far I've tried 3/4 recovery zips provided (41-124-01, 41-125-03, 41-203-01) with the same results. Rather than simply trying to load recovery ROMs at random hoping one magically fixes the problem, what I'd like to do what I would like to do is completely erase the flash on the device, and then try reloading the recovery ROM.
Is there a NON-acer recovery tool I can use to blow away everything that is on there now (and presumably, the corrupted bits?)
bassmosphere said:
I have an A500 that was originally purchased in Thailand. I contacted Acer Thailand and they provided me a recovery package to install. I put this on a FAT32 formatted Micro SD card and it installs, but when the tablet reboots itself it gets suck on the screen with the silver "android" logo.
I've gone also some of the advice in this thread as well: http://forum.xda-developers.com/showthread.php?t=1874345.
So far I've tried 3/4 recovery zips provided (41-124-01, 41-125-03, 41-203-01) with the same results. Rather than simply trying to load recovery ROMs at random hoping one magically fixes the problem, what I'd like to do what I would like to do is completely erase the flash on the device, and then try reloading the recovery ROM.
Is there a NON-acer recovery tool I can use to blow away everything that is on there now (and presumably, the corrupted bits?)
Click to expand...
Click to collapse
I ended up getting it booting up into Jellybean. First I tried restoring as mentioned above with the SD card.
This next part, I believe is the key as the device revived after this step. I put it into a bootloader restore mode by powering on with volume down and flicking the screen lock switch once the device vibrated. After this, it continued with the tablet setup mode and booted into Jellybean.
I flashed xposed framework. It booted a few times crashed and then I could still get to recovery twrp. I then flashed the original rom I was using it booted up and started completely but again crashed. So I booted recovery and flashed the original rapture 5.1.1 rom and it booted completely but after a few minutes it also crashed.
After that I was in a bootloop. In a weird way I'd have to take out the battery wait a few minutes then the power button would work (on battery). It'd try to boot vibrate, show the samsung note 4 letters and then shutdown.
Weird part is if I plug the wall charger in it just vibrates and tries to boot indefinitely. If I long hold the power button nothing happens. If I pull the usb cable out it cuts power even though I have a fully charged battery.
I've flashed twrp reovery via odin first, no luck. I've flashed the original cod6 firmware without luck. Then the original kernel and recovery. Nothing seems to work. Is my power button dead. My problems are similar to this also but it worked fine before I flashed xposed framework wanam.
http://forums.androidcentral.com/sa...battery-then-turns-off-after-two-seconds.html
The reason I think it might not be the power switch is if I take out the battery wait 15 and plug it back in the phone does not auto restart itself. I have to hold the power button to start it. After Odin flash of COD6 firmware I only get to recovery img message at the top and then it turns off.
Very similar to this problem
http://forums.androidcentral.com/sa...k-recovery-booting-screen-how-can-i-past.html
flash stock recovery, twrp, cwm recovery and still can't get to it. Only thing I haven't flashed it the modem.
Thanks for any replies
Sounds like a hardware r
Problem if odin is not flashing correctly and it has done correctly in the past. I had similar but could boot into download mode and flash nut it failed flashing . Had to reflash root, then reflash a stock rom which boot looped, then root, then flash recovery, then flashed a custom rom cmw2.1 which worked. Then to male sure I reflashed origianl 5.0 rom which then worked. Then started again rooting recovery and flash cm12.1 and all is fine. As long as u have download mode there should be a way to fix it try my method as I thought I had a paper weight for about 3 hours while I figured out the above.
Thanks
Steve
Digipro said:
Sounds like a hardware r
Problem if odin is not flashing correctly and it has done correctly in the past. I had similar but could boot into download mode and flash nut it failed flashing . Had to reflash root, then reflash a stock rom which boot looped, then root, then flash recovery, then flashed a custom rom cmw2.1 which worked. Then to male sure I reflashed origianl 5.0 rom which then worked. Then started again rooting recovery and flash cm12.1 and all is fine. As long as u have download mode there should be a way to fix it try my method as I thought I had a paper weight for about 3 hours while I figured out the above.
Thanks
Steve
Click to expand...
Click to collapse
Thanks I will try, I've tried everything odin cod6, cog2, bootloader, baseband, rom, kernel, flash reports good now but still bootloop, even tried Kies3, it completely said everything is good rebooted and just booted at the top left saying recovery... booting then shuts off.
Really weird part is as soon plug power to micro usb port it starts booting without me pressing any buttons?
First thing I do if it goes wrong is reflash original stock rom to create a clean sheet. I always find the simplest solution is usually the best, f
Aching modems, kernels, well u know what windows is like with registry errors cross link .dll files. Like with windows keep backups and reload and start afresh sometimes going too deep to fix something can make it worse :s
Yea it shouldn't boot just from inserting power cable it should goto charge screen.. If charge screen is corrupt then that could explain why It boots to go to charge screen but can't so hence the behavior. Makes sense to me .
Thanks
Steve