rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
If you have recovery, you should be fine. Just flash your favorite image and wipe your userdata.
DOD1 said:
rooted phone. went well Installed rom
not so well.
Holding home and power brings me to a "Android System recovery Utility"
I think what i did wrong was i installed two different types of roms on to my G1 unwittingly. So now all that happens is it stays on the G1 screen and doesn't change. Left it charging overnight and stayed on that screen
Is there a way to access and rectify via console option.
Please help
Click to expand...
Click to collapse
Holding Home + Power is supposed to take you into the recovery image.
At the bottom of your recovery image does it say Amon Ra 1.5.2 or 1.6.2 or something like that?
If your phones rooted then just wipe and reinstall you rom.
Like lets say your doing the new cyanmod
you apply zip
DR83
With out rebooting apply zip
Cyanmod-rom 1.4xxxx
If it boots back into Android System recovery Utility just hold home and back again.
Give it time to write its radio and its first time rebooting it says on the boot screen for a awhile some longer then others.
This site has always helped me its better to see the instructions rather then read them.
http://www.google.com/search?q=the+...s=org.mozilla:en-US:official&client=firefox-a
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 have a STOCK myTouch 4g, never ever been rooted or have had flashed roms on it.
It freezes at the "TMobile myTouch4g" logo.
I can get onto hboot with the power+volume down button but when i choose to "factory reset" it freezes.
And when i choose "recovery" it boots into recovery mode showing a phone with 2 green arrows circling around it for 5 secs ...
But then it cuts off and vibrates 7 times
PC wont detect the HTC drivers
Phone does charge and shows that there is USB connection but the PC wont popup the USB mass storage folder
I have gotten into bootloader ONCE. I cleared the cache and then tried to recover it by doing power+volume up
It started to recover but then it cut off again and vibrated 7 times
Q: Will I be able to recover by flashing the PD15IMG Glacier recovery?
Q: Is my phone completely useless at this point?
Your phone may be toast. Try flashing PD15IMG.zip. If it fails, you either have a corrupt bootloader or a failed eMMC. Either means the phone is done.
estallings15 said:
Your phone may be toast. Try flashing PD15IMG.zip. If it fails, you either have a corrupt bootloader or a failed eMMC. Either means the phone is done.
Click to expand...
Click to collapse
Thanks for your reply and information. Hope its repairable.
If you will have to twist the phone due to the fact that a memery chip becomes disconnected from the board bending the top right side and the bottom left side will reconnect and it should boot.
If that doesnt work go on htc dev site and unlock the bootloader then flash a recovery and flash the eng bootloader which can be done in the terminal of TWRp recovery
I'm pretty sure 7 vibrations means bricked. Or at least something like that
Sent from my myTouch 4g using xda app-developers app
That's the usual sign if your not getting that then its something else
Sent from my Amazon Kindle Fire using xda app-developers app
wizbo27 said:
If you will have to twist the phone due to the fact that a memery chip becomes disconnected from the board bending the top right side and the bottom left side will reconnect and it should boot.
If that doesnt work go on htc dev site and unlock the bootloader then flash a recovery and flash the eng bootloader which can be done in the terminal of TWRp recovery
Click to expand...
Click to collapse
The chip failure these phones experience is internal. Also, have you tried this bootloader flashing method on a myTouch 4G, because I'm skeptical?
Anyone can feel free to enlighten me if I'm wrong.
Edit: Just saw the thread where you are unable to flash anything successfully. This reinforces my skepticism.
I was in the same situation before and it work to flash the eng-boot for me.
im having problems flashing but i dont think he/she wants to flash anything but rather return to stock
take it apart, clean and put back together?
If you get to a point where you are adventurous, you may try disassembling the phone, cleaning it, and then reassemble. You may find that re-seating the connectors as I did during my story in the next paragraph may help. You'll need phillips #000 and torx 5 screw drivers. You can look up disassemble guides on YouTube.
I had a couple of this model phone. One with the symptom you described and another with a smashed screen. I pulled the screen/touch from the one that would not boot and paired it with the internals from the one with a smashed screen. That made a good unit. For fun, I reassembled the internals that had your same symptom with the lcd left over and I was able to get it to boot. I didn't have a touch screen any more so I couldn't fully examine the state.
This thing that got me out of the woods was 4ext recovery because you can wipe every partition instead of just the flash memory with cwm or twrp
Sent from my SGH-I997 using xda app-developers app
So i don't know exactly what has happened to get here. I have a new Verizon Galaxy S5 that I Towel Rooted and installed Safestrap. Things were going fine and I made a nandroid backup of my Stock slot. I decided to try Alliance rom in slot 1 which all went fine and i booted into Alliance. I was customizing my phone with colors and clock position etc. Some of the icons weren't there anymore so I decided to reboot to get everything loaded back in. Well when i hit reboot the screen went black and nothing came back on. Now when I turn it on I get the Galaxy S5 splash screen and blue words at the top saying "RECOVERY BOOTING...." then it shows the Android with it's chest door open and the globe spinning, then it goes to the Android laying down with a red triangle over its chest door, and then reboots. It just loops like this. Does this mean my bootloader is corrupt? Or can I Odin flash the stock firmware and PIT?
If your bootloader was corrupt, you'd either end up on the secondary bootloader page or have a nonresponsive, brick for a phone.
So corrupt bootloader was just your guess? Because I don't see any evidence for that yet. You've ended up on the Recovery mode page or at least that is what your description sounds like (a screenshot or photo would have been good). More than likely something is just messed up in your Safestrap or custom recovery configuration.
The most obvious options would be to either check and/or reinstall Safestrap /your custom recovery. Or if you prefer, revert to full stock, then proceed from there.
The last part that you wrote is unclear.. but you imply that you can't do a normal boot at this point? Can you boot to download mode then? Pull your phone battery for ten seconds.. then press and hold the volume down key, then the home key also and then the power key. You should boot to the black download screen that shows your Knox status. If this works, then you can flash a full stock firmware from there with Odin to stabilize your system.
.
Thanks fffft for your response.
As it turns out you are correct in that the bootloader is not corrupt because I can get to download mode. I tried flashing the stock firmware back on through Odin, but that didn't work, it still just looped. What finally did work is this thread http://forum.xda-developers.com/showthread.php?t=2784880 Thanks to Misterxtc. It must have needed the PIT as well.
Hello guys, after a extensive research I decided to post thia thread and ask for help.
I recieved this phone (i9505 international version) from my cousin after it was washed in a wash machine inside his pants pocket'.
He told me he had sent it to a repair shop to have it cleaned and repaired before he sent it to me.
I recieved it, charged it's battery on a externalismo charger, put it back and it turns on ok, but gets stuck on The boot screen with a little blue message on the top that says "recovery booting" and never changes from there.
So , i tried The obvious, downloaded a official ROM, and tried to flash it. Flash was sucessful but i still had the same problems with it getting stuck in The first boot screen with the little blue text at The top.
Then i tried flashing The ROM with a pit file to rebuild The partittions. Flash was sucessful again, no errors at all, but I still had the same problem getting stuck at The boot screen.
The I tried flashing a custom recovery.
Clockwork recovery got me a error screen after i flashed it saying something got wrong during flash ask me to flash again.
Reflashed The oficial ROM with the pit file, tried again, same error. Had to reflash again.
Then I tried twrp.
This time something went different. I was still stuck at The boot screen, but The blue text changed to a red/orange 3 line text saying something like "Recovery is not seandroid enforcing".
I've read that this hás something to do with a locked bootloader and knox security.
Also, I've read that some people had this problems when their /data partition got corrupted.
So, I could not clear or format the data partition because I can't get into the recovery. The pit file never touches /data, and I don't really know if flashing the oficial ROM is enough to fix any problems in /data.
I have no idea if the data on /EFS is still OK.
And I'm still stuck with this problem.
Does anyone have any idea what else I can try in order to unbrick this phone?
I think the 3 possible problems are:
Corruption on /data
Corruption on /EFS (still it should boot)
Something wrong with bootloader vs rom version or region or something with Knox security.
Oh, I Aldo tried flashing another modem/radio. Got the same "something went wrong while flashing, try again" error.
Any help would be greatly appreciated.
Sorry if you find any typos, I'm fighting my word corrector (which is in pt-br) as I type this from my phone (n7000).
PS: flashed Samsung 4.4.2 zto (brazil) to the i9505
Another possibility is that the volume rocker shorted and when holding power it is also holding volume. Therefore booting recovery. I would check this by removing the volume rocker ribbon from the board and powering on. I know it sounds silly but could be the problem
Sent from my SCH-I605 using XDA Free mobile app
I openned the phone a few minutes ago to check this. Acctualy the button is soldered into the mainboard. I wasn't able to disconnect it.
I get a new multimeter (mine broke a few weeks ago) and check the contacts, but I don't think this is the problem, because if it was just a problem with a key getting stuck it should still boot into the recovery and do something, but it's not the case, it gets stuck in the bootscreen before booting and never really enters the recovery.
and when I go into download mode, there is a screen that asks me to presse vol up to go into download mode or vol down to cancel, I acctually have to press vol up to enter download mode, so it's probably not the problem. Thanks for the sugestion tho'.