Don't know what I did. I now have a wierd boot screen problem. I can then hear, but not see, the Verizon sound and then it boots up, but my 3g does not work. I tried my usual reliable heimball restore to Verizon stock but the boot loader is still there?! I can't get into recovery using the holding the up-vol and power. Holding vol-down and power does get me to the download screen.
How do I fix it?
Can I use another rom that would bring the 3G back if I can't downgrade the boot loader (if that's even the problem)?
Please help.
EDIT: I think I messed it up by using some proteced bootloader from a rom
any thoughts are appreciated as my Tab has no 3G
now it's dead
Tried using roto restore for the sbl.bin and boot.bin (bootloaders) and all the zimage, param....etc
Went through successfully, now does not turn on after it tried to reboot. Nothing. Downlaod mode...nothing works
going to receive a replacement
Well, enough was enough. I called Verizon and they are sending me one next day delivery. I have to send the old one back. Remember the post about not flashing protected boot loaders!!!!!
Related
Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Difinitus said:
Hello, I am having some issues and I've tried all of the fixes on several different forums including this one.
I wanted to root my phone so I followed Amon's guide and successfully went from the Tmobile released 1.6 to the rooted 1.5 in the guide. I then wanted to update to the rooted 1.6 but was having issues with trying to install the update. While in the safe mood I asked it to extract update.zip about 3 times before it finally opened it and it extracted everything really quickly!
I then tried to reboot the phone but it stayed at the green MyTouch 3G splash screen without going anywhere. I've tried all the tricks of taking out my battery, unplugging the USB, any form of combination I could.
I'm told my phone isn't bricked, only stuck but my computer isn't picking up the phone either. It doesn't say it can't read the USB device and fastboot still says waiting for devices.
Can some one please help me with my problem?
Thank you,
Click to expand...
Click to collapse
What do you mean by safe mode? Which donut ROM are you trying to flash? Which recovery image do you have? How long was it stuck on the splash screen. You need to give more details for us to be able to help out. What radio and spl do you have?
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Difinitus said:
I meant safe mode by where you select the option to extract update.zip.
I was trying to flash Amon's 1.6 32A Rom. Even though my phone states 32B I followed his instructions on how to Root the Mytouch and he was using 32A stuff so I figured if it worked OK, I was now running on 32A instead of 32B.
I was using RAv1.2.0H.img from his original guide. I dont know what radio and spl I have. There wasn't really a guide on updating ROMs so I just tried the same basic steps.
I hope this is more helpful, I am doing my best to learn everything, I am still fairly new to modding a phone. (my last phone was a Blackberry 8100).
Click to expand...
Click to collapse
I'm not sure what you mean by extract update.zip. I think you are talking about fastboot there. Have you tried to flash the rom in the recovery image? you know, by pressing power and home to get to the recovery, then flashing it through there. go into fastboot by pressing power and back and it will tell you what radio and spl you have. once you have that, write that so we can further get a grasp as to your problem. if in fact you still have the 32A configuration, you might want to flash over the 32B radio and and try to flash a 32B rom.
That is my problem, I can't get past the "MyTouch 3G" green screen. I've tried the Home button, Back button, Vol Down button and holding them for several minutes with no result, it stays at the very first screen when it turns on.
I've tried flashbooting from adb but it says "waiting for devices" and my computer isn't picking up any kind of device.
I'm having the exact same problem except im stuck on the vodafone screen. I also tried flashboot form adb but "waiting for devices" is shown and pc wont detect the device.
Did this before.
If you can get into recovery mode, Hold Home button while powering on, you can restore a nandroid backup, if you took one, or put the sappimg.nbh file or the correct items to flash whatever rom.
I had a stock 1.5 Mytouch. I wanted to root and get the 1.6 version of cyanogen, forgot to flash the HTC_ADP_1.6_DRC83_rooted_base as part of the process and had got stuck in the neverending mytouch logo.
If you can get into recovery:
wipe, then put the update.zip files directly on the card.(use a SD adapter, ...)
Choose apply any update from SD
Choose the base files, then the rom if its a newer version
Once those two updates run, reboot the phone.
My never ending logo disappeared, and the phone booted. Newb mistake on my part.
Wait at least a minute or two once this is done.
since the phone is stuck on the original logo and isnt responding to buttons when loading up... do we manually remove and reinsert the battery while holding the home button?
I have tried getting into recovery mode, but it doesn't do anything past the splash screen. Holding the home button while trying to power on the device won't do much.
hey difinitus keep me updated if u somehow get it to work
Even when you take the battery out for a significant time it turns on immediately to the logo screen. Whats the longest you have left the phone sitting at the logo screen.
A small thought, since it was trying to load a rom you had on your memory card, try taking the battery out, and removing the memory card, and then turn it on and wait a bit and see if you get a different result. Its a thought.
If that doesnt work put the memory card back in and turn it on and once its on remove the memory card.
Perhaps the rom on your memory card is corrupt and it is unable to continue to load it, you could even try putting the rom on again using your memory card reader and your computer, thus erasing the existing one.
try plug usb in to phone
take battery out
prees and hold home button
re-insert battery while still holding button
let go after about 3-5 sec
have you tried getting into fastboot by holding back and powering on the phone once you took out the battery? cuz fastboot doesn't initialize after the splash screen, it just pops up as soon as you hit back and power
@Tech no boy; I have tried using several different update.zip and a .nbh and also tried reformatting.
@sitimber; have tried that before, the splash screen still pops up. It just vibrates once and goes to the logo, with any combination of buttons and steps.
@tazz9690; Yes, no matter what I do it still goes to the splash screen. I've been saying that for several posts now.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.
you might have a bricked phone then. call up t-mobile and get it returned under warranty. if you are 100% positive that you will not be able to get past your splash screen, then the return center will not be able to prove that you have modded your phone, and they will send you another phone.
Hello to everyone.
I was flashing a modified .tar file, but it got stuck at some point (invalid .tar or whatever, it was flashing factoryfs) and I rebooted the phone. The problem is, now the phone's dead and I can't even get it to show the charging logo.
I'm used to flash Kaiser ROM's, have been doing that for about two years now. Everytime something went wrong, all I had to do with my Kaiser was reboot, get back at bootloader and start the flashing process again. Why can't I get to that flash loader again with my phone? Damn!
Is there any way I can get that loader back, or...do I need to send it to the Samsung support service or to some sort of repairer?
Send it to Samsung Service
jsoar said:
Hello to everyone.
I was flashing a modified .tar file, but it got stuck at some point (invalid .tar or whatever, it was flashing factoryfs) and I rebooted the phone. The problem is, now the phone's dead and I can't even get it to show the charging logo.
I'm used to flash Kaiser ROM's, have been doing that for about two years now. Everytime something went wrong, all I had to do with my Kaiser was reboot, get back at bootloader and start the flashing process again. Why can't I get to that flash loader again with my phone? Damn!
Is there any way I can get that loader back, or...do I need to send it to the Samsung support
service or to some sort of repairer?
Click to expand...
Click to collapse
Try to remove the battery, VolUp + Home + On, and try again ?
Gsam101 said:
Try to remove the battery, VolUp + Home + On, and try again ?
Click to expand...
Click to collapse
Done that... still stuck (dead). It's in service now, should be ready monday
A message popped up from Samsung to install an update (I had been pressing cancel for the past week on this update). It says click OK to reboot and apply update (something along those lines) so I do. Now I am stuck with a tablet that won't boot. If I hold the power button it says "Samsung Galaxy 10.1" after about 12 seconds, but then it goes away and back to darkness. Nothing else. Holding power and volume up does nothing.
Someone know what is going on and have any idea how to resolve?
The best way is to restore any backup you have from cwm recovery. Else grab a stock firmware and flash it with ODIN or if zip than CWM recovery. For luck, try clearing cache and data in recovery, first!Perhaps it may work saving you all fuss of flashing a firmware.
I cannot even boot that far too get into recovery. And I just noticed that although I can't boot, the backlight is on (on a solid black screen).... wtf
You can't hold volume down and power button to enter recovery?
Nope. I plugged into my computer and for some reason with the USB connectd it let me enter recovery. Flashed a backup and rebooted, but now I have no wifi... im confused.
it occured once to me when i tried to overclock, it never worked except when installing a new rom... Try to root the device and then install a new rom
OK, was a helluva night messing with ROM and kernel installs... I have yet to go back to completely stock (that's next up tonight, unfortunately), but I installed Starburst ROM and the Wifi still didn't work so I then installed pershoot's kernel and now when I boot the screen is extremely distorted kind of like this: http://t1.gstatic.com/images?q=tbn:ANd9GcTsKa5IoQxnesGdUjykWDDggoQZ38yZ2VXSgPAQ09NOCnETzl9-
As a side note, when I say the wifi is not working, it still shows all networks and allows me to connect just like normal. However when connected no apps can access the network...
Can someone point me to a thread on how to revert EVERYTHING back to stock so I can start fresh? TIA!!
http://forum.xda-developers.com/showthread.php?t=1171089
Should have all the files you need. From where you are now I would flash the stock OTA 3.1 or TW then flash the stock recovery and do a factory reset from that recovery. That should get rid of the garbled screen.
Thanks buddy. On my way to grab the files now
I heard the update was pulled as it sometimes rewrites the bootloader improperly. You might need to send it in, unfortunately.
So as my wife tells it she received a text message then the phone shutdown and went to the bootloader screen. She was running Liberty2 v3? up until now.
The phone boots to the bootloader showing:
Boot Loader
D2.37
err:A5,69,55,00,27
Ready to program
USB
The standard bootloader schpeal.
Unfortunately I can't do anything to get beyond this. I have tried SBF to 2.3.20 and 2.3.4 both come back to the same screen. Cannot access recovery by holding X or the down volume button.
On boot the phone shows the Red Moto "M" logo then fails to the boot loader.
HALP!
You don't see the M logo when you go into boot loader. Hold the up arrow on the keyboard as you power on. Boot loader will be the first screen that you come to.
Don't know what to tell ya. I can't get into recovery no matter what keys I press. I get the "M" logo then it fails into the boot loader with the above error.
I can ONLY get to the bootloader no matter what I do. No SBF files seem to work and I cannot get to recovery to try and wipe data/cache to fix the bootloop. Basically I'm stuck at the bootloader and can't do anything to get past it.
twiceover said:
I can ONLY get to the bootloader no matter what I do. No SBF files seem to work and I cannot get to recovery to try and wipe data/cache to fix the bootloop. Basically I'm stuck at the bootloader and can't do anything to get past it.
Click to expand...
Click to collapse
I'm pretty much in the same situation.
Wish someone with better knowledge than I can pipe in.
Been stuck like this going on 2 weeks now.
There has to be an .sbf to flash that'll work.
phirewire110 said:
I'm pretty much in the same situation.
Wish someone with better knowledge than I can pipe in.
Been stuck like this going on 2 weeks now.
There has to be an .sbf to flash that'll work.
Click to expand...
Click to collapse
Yeah, today I'm in search of a DInc2 to replace it. Luckily I do have a Droid1 that uses the same battery so I can charge it and keep trying various things to get it working. Just sad that a phone that was perfectly good one second is toast in minutes. She could have at least dropped it and had it die that way...
Bricked D2
bump. D2 Bricked. Saw there was a sbf for D2 global, but those of us with bricked D2 seem to be out of luck for now. Oh well, I guess i don't need a phone for a while. . .
Did you guys take the newest Verizon Over the Air updates?
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'.