Tried everything I know (which admittedly, isn't a ton). I picked this P7510 up on eBay. The guy said it was locked by a virus. I'd never heard of that but I figured if i could get into Odin mode i could fix it.
It boots into Odin just fine. Once the drivers are installed, Odin sees it and I can flash anything I want. Passes every time.
When Odin sends the re-boot command the device hangs. No splash screen. Nothing. It won't boot into recovery.
I can always get into Odin mode, so I tried flashing different recoveries (CWM, etc). Odin passes it every time, but I still can't boot into recovery, even using the buttons. If I try to do it from the two choices on screen when you hold vol down and power, I get a blank screen.
I hate to give up. Any ideas?
ender1962 said:
Tried everything I know (which admittedly, isn't a ton). I picked this P7510 up on eBay. The guy said it was locked by a virus. I'd never heard of that but I figured if i could get into Odin mode i could fix it.
It boots into Odin just fine. Once the drivers are installed, Odin sees it and I can flash anything I want. Passes every time.
When Odin sends the re-boot command the device hangs. No splash screen. Nothing. It won't boot into recovery.
I can always get into Odin mode, so I tried flashing different recoveries (CWM, etc). Odin passes it every time, but I still can't boot into recovery, even using the buttons. If I try to do it from the two choices on screen when you hold vol down and power, I get a blank screen.
I hate to give up. Any ideas?
Click to expand...
Click to collapse
What happens when you try to turn on the device normally, without trying to boot into recovery or Odin mode?
Prashramani12 said:
What happens when you try to turn on the device normally, without trying to boot into recovery or Odin mode?
Click to expand...
Click to collapse
Boot loop at Samsung screen.
Interesting...
Have you tried flashing ICS (4.0.4) through Odin? maybe that'll do the trick.
Outside of that, I can't really think of a solution.
Prashramani12 said:
Interesting...
Have you tried flashing ICS (4.0.4) through Odin? maybe that'll do the trick.
Outside of that, I can't really think of a solution.
Click to expand...
Click to collapse
Obviously something does not allow it to boot into recovery. So I also suggest trying to get it to boot normally first by flashing ICS through Odin. After booting, then you can try rooting it. For all you know the device may not have been rooted already.
Cheers!
Sent from my GT-P7500 using xda app-developers app
John Kester said:
Obviously something does not allow it to boot into recovery. So I also suggest trying to get it to boot normally first by flashing ICS through Odin. After booting, then you can try rooting it. For all you know the device may not have been rooted already.
Cheers!
Sent from my GT-P7500 using xda app-developers app
Click to expand...
Click to collapse
Thanks guys. That was my first step. I tried flashing the stock ICS through Odin. Odin green-lighted the flash, but still no boot. I sold the thing. This was the first time a tablet beat me. Oh well.
Related
So a friend of mine has an atrix and I have an inspire, and tonight I did the same things as he did. Ruined our phones.
Background
We both have rooted phones upon flashing a different rom to my phone it "bricked" it (i use that term loosely) Well upon boot up it would stay on the custom boot image that I installed. His was doing the same thing not going past the boot nor going into Clockwork.
Well upon looking around the inspire forums I found a PD98IMG file that took my phone back to the original setting like it was out of the box. I just had to do the normal power+volume down button it and it located the file and extracted everything. Now my inspire works like it was (thank god for backups of previous roms prior to flashing LOL)
Now the question and the reason I am posting in this forum. Is there something like what I used to help my friend get his Atrix working again? I was thinking this would work but not sure. http://forum.xda-developers.com/showthread.php?t=1163009 and this http://forum.xda-developers.com/showthread.php?t=1125944 would this work to get his phone past the boot so he can get his phone working again?
Provide more info on his problem please...
allowance said:
Provide more info on his problem please...
Click to expand...
Click to collapse
his is the same as mine was. power on and it stays on the main boot screen. according to him he cant get past the boot screen nor into his bootloader same issue I had.
Sounds like a boot loop. Read on it.
allowance said:
Sounds like a boot loop. Read on it.
Click to expand...
Click to collapse
That's not a boot loop if it just stays on the screen and doesn't reboot over and over.
Is his bootloader unlocked?
What ROM is he running?
Custom kernel?
Any text on the boot logo screen?
How was new ROM flashed? (Fastboot, CWM, SBF, etc.)
Can CWM be accessed by holding the volume down button as the phone powers on?
Don't flash anything via RSD.
CaelanT said:
That's not a boot loop if it just stays on the screen and doesn't reboot over and over.
Is his bootloader unlocked?
What ROM is he running?
Custom kernel?
Any text on the boot logo screen?
How was new ROM flashed? (Fastboot, CWM, SBF, etc.)
Can CWM be accessed by holding the volume down button as the phone powers on?
Don't flash anything via RSD.
Click to expand...
Click to collapse
Yes
Not 100% sure but he said he was changing it to some alien thingy when this happened
Whatever came with his rom (cant say as I did not ask what his was
Failed to boot 4 Starting RSD mode and stays there
CWM
No
He doesnt have unlocked bootloader
Sent from my MB860 using Tapatalk
mraxido said:
He doesnt have unlocked bootloader
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Have him try to flash the SBF again, plugging the USB cable into one of the "back" ports on the computer. Also make sure the battery has a good charge before hand.
Also using another computer may help. Sometimes it's as simple as the USB port you/he was using.
failed to boot 4
I was reflashing back to stock firmware gingerbread 2.3.6 from eryigits due to its massive slowdown from its initial install. But then after flashing the stock firmware it boot looped so i thought maybe there was something wrong with the partitions and loaded what I got from another thread. But then the progress bar in Odin wasn't moving at all so I terminated odin and opened another instance similarly it didn't progressed. I plugged off my ygp and rebooted only meet a cellphone logo and a computer logo with an exclamation mark unpleasantly called black screen of death. Is this what they call a brick? Should I follow the guide on hardbrick recovery ie http://forum.xda-developers.com/showthread.php?t=1496360?
Yeah use the unbrickable reserector
Sent from my YP-G70 using xda app-developers app
atcq28 said:
Yeah use the unbrickable reserector
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
I see thanks then.
avid_reader said:
I was reflashing back to stock firmware gingerbread 2.3.6 from eryigits due to its massive slowdown from its initial install. But then after flashing the stock firmware it boot looped so i thought maybe there was something wrong with the partitions and loaded what I got from another thread. But then the progress bar in Odin wasn't moving at all so I terminated odin and opened another instance similarly it didn't progressed. I plugged off my ygp and rebooted only meet a cellphone logo and a computer logo with an exclamation mark unpleasantly called black screen of death. Is this what they call a brick? Should I follow the guide on hardbrick recovery ie http://forum.xda-developers.com/showthread.php?t=1496360?
Click to expand...
Click to collapse
No, this screen is the forced download mode also called lucky brick. So while you are on this screen the player should be detected as it is in download mode. So you should be able to flash your rom.
Just flash the rom in odin again see post above me
if it bootloops again format the device in recovery mode
There is a way to fix this.
I was flashing STOCK GB 2.3.6, because i didn't like Erygit's rom, and i got the bootloop too.
The bootloop was caused by the fact i didnt do a Factory data reset, and when i did it, i rebooted from Recovery and the Stock ROM booted.
Just do a factory reset from recovery, it should work.
Thanks for the swift replies and sorry for my late reply as well! Thanks alot for your recommendations. I haven't been able to touch my ygp for awhile due to school. But I'll surely try out everything suggested. Btw I kind of already reflashed the stock gb rom it bootlooped after so I pretty much didn't have a cwm recovery. But I'll try flashing it in a while! Thanks again! ^_^
I have a TF201 and I have it rooted and unlocked. I tried installing CWM Recovery using some method I found online using fastboot. It seemed to work but whenever I tried to boot into recovery it would just say "Booting recovery kernel image" and stay there. So I restarted the device and went to the playstore and downloaded CWM and flashed it from there. Same thing happened. So I installed TWRP via fastboot and yet again I couldn't boot into recovery. Take in mind I'm a noob so I probably did something wrong. I then went to wipe the data to retry and of course it said the same message. I waited awhile then restarted the device. Now I'm stuck on the Asus splash screen and if I turn it off it just restarts again. Please help me! I clearly did something stupid, I didn't think it would be this much trouble to load a ROM. Thanks!
So can you access fastboot?
Sent from my Galaxy Nexus using xda premium
Makrilli said:
So can you access fastboot?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Nope. No matter what I do I go back to that screen. I let it die and turned it back on, same thing. Upon further research I've come to the conclusion that it's hard bricked so I guess I'll be sending it in. But for future reference, what steps should I take to root, unlock, and install CM10 on it? Because there's so many guides that approach these things in so many ways which is what caused me to mess up. I learned my lesson at least.
was installing the hyperdrive Rom using clockwork recovery mod, it says it installed sucessfully but when i go to reboot the device it just going into reboot loop, i can get back into recovery mod but when i try to factory reset and try it again it just does the same thing again, tried installing a different rom and still same thing, what am i doing wrong?
im having the same problem. i cant boot into recovery. is there anything i can do. i was on cm10.1 before this and it worked fine. i flashed hyperdrive using OUDHS and it installed and everything. i let it sit for 10 minutes like it said to then i continued to reboot... and now its stuck on the custom padlock screen and im cant boot into recovery for some reason...
OMsupp said:
im having the same problem. i cant boot into recovery. is there anything i can do. i was on cm10.1 before this and it worked fine. i flashed hyperdrive using OUDHS and it installed and everything. i let it sit for 10 minutes like it said to then i continued to reboot... and now its stuck on the custom padlock screen and im cant boot into recovery for some reason...
Click to expand...
Click to collapse
Try to get in to Odin mode. If you can flash the Stock Image and go from there.
RLS7 Verizon S4 continuous reboot loop
galaxyfans said:
was installing the hyperdrive Rom using clockwork recovery mod, it says it installed sucessfully but when i go to reboot the device it just going into reboot loop, i can get back into recovery mod but when i try to factory reset and try it again it just does the same thing again, tried installing a different rom and still same thing, what am i doing wrong?
Click to expand...
Click to collapse
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
abalgir66 said:
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
Click to expand...
Click to collapse
dont install any audio mod and also dont install any of the music players just the samsung one !
before you go through all the trouble of ODIN, which seems to be everyones answer now a days, it is a kernel issue, flash a verizon loki kernel. It should boot.
abalgir66 said:
Hi I have the exact same pb, I flashed several times my S4 (I was on RLS4 before) following the instructions, no way to get out from the endless reboot loop.
There is a suggestion using ODIN, I am not very familiar on how to do that, any help?
Thanks
Click to expand...
Click to collapse
First, if you have a back up, restore just the system partition (this will also format your current /system) Then do a factory reset and reboot. Now I if that doesn't work, Odin is your best bet.
Sent from my SCH-I545 using xda app-developers app
FOR anyone installing Hyperdrive, the most probable cause of boot loop in the Walkman Music App. Don't choose it in Aroma!!!
If you already have, the only way to fix the boot loop is to ODIN back to stock, as Dark Menace suggested.
He can PM you the stock image, which you will have to flash in ODIN to successfully boot up again.
hey I do plenty of flashing, and from time to time get into trouble... But ODIN is not the first choice to fix... Please read the forums:cyclops:
Sent a few PM's to see if that helps. You can try the kernels first then go from there.
Sent from my SCH-I545 using xda premium
fix
I had the same problem had to go back in odin mode and reflash a old stock. If that does not work reset data and cache and install a new rom. Worked for me
DarkMenace said:
Sent a few PM's to see if that helps. You can try the kernels first then go from there.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
I will try again without selecting the music app. I was always selecting the Sony one. I will try this afternoon and keep you informed.
Thanks
abalgir66 said:
I will try again without selecting the music app. I was always selecting the Sony one. I will try this afternoon and keep you informed.
Thanks
Click to expand...
Click to collapse
It worked perfectly if we do not select any music app. Thanks
Device gets stuck at S4 logo with blue font RECOVERY BOOTING, even after Odin, any ideas??
I'm so stuck!
TheAxman said:
before you go through all the trouble of ODIN, which seems to be everyones answer now a days, it is a kernel issue, flash a verizon loki kernel. It should boot.
Click to expand...
Click to collapse
I can't get my phone to see the the SD card in recovery. My Verizon Galaxy S4 is stuck in a boot loop thanks to Hyperdrive RLS12 and Odin fails every time I try it. Any help would be greatly appreciated!!
Surge1223 said:
First, if you have a back up, restore just the system partition (this will also format your current /system) Then do a factory reset and reboot. Now I if that doesn't work, Odin is your best bet.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I am trying hyperdrive on Baseband I545VRUEMJ7 and build JSS15J.I545VRUEMJ7 (4.3). I am able to root and install safestrap. Even hyperdrive/dirty unicorns (i tired both) installs fine, but ends up in reboot loop. am i missing anything here?.
Here goes, hopefully someone can help!
Ive installed a fair few roms on my phone and never had any issue, maybe this explains the complacency.
After updating to CWM recovery -6.0.4.7 I get stuck on my bootscreen, only seeing "Samsung galaxy I9100P" , ive been putting I9100 roms on it and losing NFC functionality for a while.
I went to update to the newest CM-11 nightly and read I needed to update CWM-recovery first. So did that, rebooted phone as instructed after installing new CWMr and nothing. Just stuck on I9100 screen.
No way to get into recovery mode, the only bright side I have found is I can boot into ODIN download mode. So what would be my next steps anyone?
Flash stock rom. or flash a kernel to get a working recovery bk with odin.
Sent from my GT-I9300 using xda premium
andrewwright said:
Flash stock rom. or flash a kernel to get a working recovery bk with odin.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
From a dig through the forums it sounds like NAND rw corruption?
I wouldn't be calling it that just yet. Unless you'd like to pay for a motherboard replacement ? Most of these are recoverable.
Used ODIN and flashed a new kernel, still on the boot screen, except now I have the yellow exclamation mark. Now to, Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.. this day is not going well..
Fingers crossed, flashed 3 or 4 kernels before one worked and allowed me into recovery mode. Trying to restore back to my backup from this morning. Heres hoping! :good:
Worked perfectly, the first thing I did was retry the initial task which was what got me stuck, currently waiting on CM-11's initial boot up after a successful install Thanks for the calming responses!