I was being a total dumbf**k yesterday and screwing with my Galaxy Player 5.0 to install Lollipop. I installed it, but I couldn't install Gapps, so I used ODIN tonight to attempt to restore it. Problem was, I installed the kernel in the Bootloader section, not the PDA section. I finally ended up installing it, however the boot animation is endless now. It only plays the sound at first bootup, then it shows the normal boot screen endlessly. Anyone help me as a stupid guy doing stupid things?
EDIT: I just installed Entropy's Daily kernel over it, however that did nothing. Also, I can not get to recovery AT ALL. In fact, I'm holding the button combo right now!
Can you access the Bootloader Menu on your YP - G70 ('DOWNLOAD Mode')?
superblox02 said:
I was being a total dumbf**k yesterday and screwing with my Galaxy Player 5.0 to install Lollipop. I installed it, but I couldn't install Gapps, so I used ODIN tonight to attempt to restore it. Problem was, I installed the kernel in the Bootloader section, not the PDA section. I finally ended up installing it, however the boot animation is endless now. It only plays the sound at first bootup, then it shows the normal boot screen endlessly. Anyone help me as a stupid guy doing stupid things?
EDIT: I just installed Entropy's Daily kernel over it, however that did nothing. Also, I can not get to recovery AT ALL. In fact, I'm holding the button combo right now!
Click to expand...
Click to collapse
Hey, did you manged to fix your galaxy player? because i'm trying to fix mine, we are basically in the same situation
Lollipop, then flashed the stock rom, and then nothing
superblox02 said:
I was being a total dumbf**k yesterday and screwing with my Galaxy Player 5.0 to install Lollipop. I installed it, but I couldn't install Gapps, so I used ODIN tonight to attempt to restore it. Problem was, I installed the kernel in the Bootloader section, not the PDA section. I finally ended up installing it, however the boot animation is endless now. It only plays the sound at first bootup, then it shows the normal boot screen endlessly. Anyone help me as a stupid guy doing stupid things?
EDIT: I just installed Entropy's Daily kernel over it, however that did nothing. Also, I can not get to recovery AT ALL. In fact, I'm holding the button combo right now!
Click to expand...
Click to collapse
You need to boot into download mode then flash the stock ROM with odin.
Then boot into recovery mode and do a factory data reset and cache wipe.
If it still does not work try flashing the stock ROM with the pit file.
Both the ROM and pit file can be found here:
http://forum.xda-developers.com/showthread.php?t=2192488
Androprise said:
You need to boot into download mode then flash the stock ROM with odin.
Then boot into recovery mode and do a factory data reset and cache wipe.
If it still does not work try flashing the stock ROM with the pit file.
Both the ROM and pit file can be found here:
http://forum.xda-developers.com/showthread.php?t=2192488
Click to expand...
Click to collapse
Thanks, but I realized how stupid I was being and got it resolved relatively quickly
edoardog said:
Hey, did you manged to fix your galaxy player? because i'm trying to fix mine, we are basically in the same situation
Lollipop, then flashed the stock rom, and then nothing
Click to expand...
Click to collapse
When you flash the stock ROM, wait until you get to endless boot, then power off your device. Hold Up+Power until you see the Samsung logo. Go to Wipe data/factory reset, wipe, then restart your device. It's because the partitions aren't formatted, so no temporary data can be stored on the /data partition until you factory reset and it formats /data and /cache.
Related
Nevermind, I just flashed CMW recovery with odin and I was able to get into recovery mode and do a hard reset. It booted fine now. Phew.
Hi guys,
Is there any hope for my tab (Wifi US ver)?
Long story short, I thought my tab was soft bricked so I tried to flash a stock rom with Odin and it's now looping in the "manual mode: copying common apks", it would freeze there then the Samsung logo would load and it would go back to manual mode and the whole thing loops like this.
I can still get into download mode, but recovery mode loops with the copying apk thing.
Any help or input would be much appreciated. Thanks!
If you can still get into download mode, then find a proper firmware (my advice is www.sammobile.com), and give it another go.. Then root, cwm and try to restore the android again, though it might be corrupted so that's why you got into problems... Anyway, if download mode works it's ok!
EDIT: imo, maybe it should be best to flash with a pit file, so that everything, including /sdcard will be wiped, but you will loose everything (photos, music, etc).
Sent from my amazing 10.1 galaxy tab
A pit file and repartitioning was actually an option I looked into while doing some research, but I'm not sure where I would find a pit file.
I did do a factory reset+clean wipe and flashed a new rom and everything appears to be fine. I think the problem may have been due to Pershoot's new kernal for ICS considering my tab froze after I flashed it, and the ROM flashed after also had a similar kernal as well, and that also froze my tab at boot animation.
But yeah, I'll definitely find a pit file just in case this happens again. Thanks
Ohai!
I have a Galaxy Player 5.0 USA (YP-G70), and a few days ago I installed Entropy512's kernel via the `dd` method. Everything worked nicely, until I decided to boot into ClockworkMod Recovery by holding the volume up key while booting. It booted into the recovery menu, and everything worked nice, but when I hit 'reboot' or 'shutdown', it booted right back into recovery (after seeing the SAMSUNG screen for about 5 seconds).
I've done pretty much everything I can think of. I've reflashed the kernel, flashed CM7 and CM9, and I tried flashing a stock ROM that I found. Flashing the kernel from the stock ROM causes my device to instead go into "Android System Recovery" rather than ClockworkMod Recovery, but I'm able to get back into CWM by flashing Entropy's kernel with heimdall.
I'm capable of getting root access with `adb shell`. I've wiped almost everything on the device (used the 'wipe data/factory reset' option and 'wipe cache partition' option) but still continues to boot into CWM recovery.
I'm not too interested in simply fixing the device so it's back to stock, as I *really* want CM9. I have a Droid X to keep me busy for now, so I found that my Galaxy Player has been just sitting there, collecting dust. If I can get it to run CM9, I'd have more use for it.
I apologize if I left out some important information. Any help would be appreciated!
Thanks in advance,
- Ben
Just an update, I tried an exitrecovery.zip, which did not help. I also extracted the exitrecovery.sh from the zip and executed the one command it had inside it manually in a root shell. Still stuck. Is my device bricked in some form? I'm pretty sure there is some bootflag that tells it to boot into recovery, even if everything is fine.
I would suggest to go ahead and flash CM9, because your problem may be caused by formatting/corrupting /system (the kernel has nothing to load, so it drops you into recovery).
Once you flash cm9, however, do not flash Entropy's kernel again.
Sent from my YP-G70
East gsstert
Mevordel said:
I would suggest to go ahead and flash CM9, because your problem may be caused by formatting/corrupting /system (the kernel has nothing to load, so it drops you into recovery).
Once you flash cm9, however, do not flash Entropy's kernel again.
Sent from my YP-G70
Click to expand...
Click to collapse
Thanks for the reply. I actually ended up trying so, and CM7 as well, to no avail. I also tried flashing stock, as I said in the post (I think, maybe I forgot to mention it) and it failed. (I used heimdall to flash stock)
I ended up giving up and replacing the device since it was under warranty, but I regret doing such as I *really* wanted to know why this happened in the first place. I'm anxious to get CM9 on it. Should I just put the device into download mode and use heimdall to flash CM9?
No. The safest way (and easiest, IMO) I think is to root it while on stock, install Entropy's kernel (extract the zip and dd it), and use CWM to wipe your device and install CM9, plus back up stock if you want to.
Sent from my 5.0 US with ICS
Mevordel said:
No. The safest way (and easiest, IMO) I think is to root it while on stock, install Entropy's kernel (extract the zip and dd it), and use CWM to wipe your device and install CM9, plus back up stock if you want to.
Sent from my 5.0 US with ICS
Click to expand...
Click to collapse
Apologies for the late reply.
That is what I did last time. I actually got stuck in CWM before even trying to flash CM9 or anything. I just booted into recovery, and then instantly clicked on 'reboot'.
Hmmm... that's really interesting. Although I still have no idea why it would have this problem (I've never had it on Entropy's kernel - which version are you using?), I think I know what the problem is. When you tell android to "reboot recovery", it puts a file in the boot partition that the kernel sees after the reboot and tells it to enter recovery mode. Logically, that file gets deleted so the system boots normally next time. It seems that in your case that failed to happen. But I still am wondering why...
Sent from my 5.0 US with ICS
Mevordel said:
Hmmm... that's really interesting. Although I still have no idea why it would have this problem (I've never had it on Entropy's kernel - which version are you using?), I think I know what the problem is. When you tell android to "reboot recovery", it puts a file in the boot partition that the kernel sees after the reboot and tells it to enter recovery mode. Logically, that file gets deleted so the system boots normally next time. It seems that in your case that failed to happen. But I still am wondering why...
Sent from my 5.0 US with ICS
Click to expand...
Click to collapse
Yeah, seems to be probably what happened. I actually ended up trying again on the new Galaxy Player, and things went swimmingly. I am now happily running CM9 on this device. However, I am scared to even think about booting into recovery again. (I only went into recovery to flash the kernel, and wipe the data partition)
Hi Everyone! just a rookie here in need of a bit of advice.
I'm a Galaxy S II I9100 owner and have my phone rooted and all setup with custom roms and been comfortable with flashing for some time now. My ROM of choice recently was Vanilla Rootbox and have to say the ROM has been fantastic with very few bugs to report. Last night i recieved the OTA update via Goo Manager for Vanilla Rootbox 3.4. I downloaded the full update over wifi and flashed with all wipes no worries. Next step was to flash the latest GAPPS and i figured there would be nothing wrong with flashing the GAPPS zip i had on my sd card that i had downloaded the last time i was notified of a GAPPS update via Goo manager as well. After flashing, wiping everything and rebooting again. My phone then booted up to a series of dialog boxes indicating that many google processes had stopped functioning. apps.google.com etc etc. A similar error has been reported in the Vanilla Rootbox thread by another user but i wasnt able to report this bug their either because my post count is too low to post in a development forum. So after seeing this error i rebooted into recovery to flash my last backup but CWM recovery came back with an error messaging stating it couldnt mount either ext or int sdcard. i did a factory reset which made no difference to the problem whatsoever. I then downloaded ODIN and the latest stock ICS Rom and flashed it via ODIN with no reported errors. My phone now boots through the optus boot animation and is stuck at the Galaxy S 2 screen with the flashing red and yellow animation over the S. If i turn off the phone with the power button, the phone turns off and immediately starts again and gets stuck at the flashing s screen. I've taken the battery sim and ext sd card out and put it all back in only for the problem to persist.
If anyone could help me there's a donation and my thanks in it!
Much appreciated
Nick
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
gastonw said:
tried to re flash another stock ROM?
If so, tried factory reset the phone after the flash?
As long as you can get to DL mode, you are good to keep on flashing till you are up & running.
And then you got this
Remember to update your kies and make sure you close it all up before flashing with odin. If you are in 4.0.4 beware of the brick bug.
Click to expand...
Click to collapse
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
darkstar117 said:
Kies has never been installed on this computer but i did use the usb drivers mentioned in the soft brick recovery guide you linked. I used some information from the guide to flash this stock rom but i couldnt flash or wipe the partition because im unsure where to get the .PIT file required? i cant get past the boot animation so no factory reset possible and yes i can still get into download mode!
Click to expand...
Click to collapse
wow wow, leave pit files alone for now, they are nasty.
What stock ROM did you flash? 4.0.4 or 4.0.3?
You can factory reset via recovery mode.
Try installing kies anyway, it can't never hurt. Just make sure all applications are closed before you re-flash.
here's jb leak, might help:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
darkstar117 said:
Right so i flashed I9100XWLP8 stock rom (4.0.3). Just then i flashed Siyah Kernel and attempted to use the factory reset function in recovery there, i get a message down the bottom mentioning that it can't mount my internal SD.
Click to expand...
Click to collapse
Tell me your:
Model
Firmware
Country
Carrier
Always mention this
try flashing jb leak (ROM, modem & kernel package).
Hey guys!
Since I tried building Firefox OS -Boot2Gecko- on my Samsung Galaxy S2 (i9100) (FYI: I followed this walkthrough) , I'm having quite a hard time making my phone boot on any ROM I try to install. I still have an access to CWM Recovery and to the Download mode
* After failing to flash B2G's Gaia on my phone, I tried to flash the kernel back to the original one and to restore the CM 10.1 NIGHTLY backup I made before doing all this mess. No changes: stuck at CM's boot screen.
* Tried to get back to a stock firmware and ROM, stucks at boot screen ("Samsung Galaxy S II GT-I9100" screen), even after a wipe data/factory reset, wipe cache and wipe dalvik cache.
(In fact, I achieved to boot on a stock ROM once, but after some other manipulations to get my CM 10.1 back, I now can't get it to boot on any of them anymore.)
* I tried to follow the rooting + CyanogenMod walkthrough on CM's wiki, but the same happens: stucks on boot screen. However, after a wipe data, I reach CM's boot animation, which runs indefinitely.
* Right now I tried flashing with Siyah's Kernel, since the flash counter is not any of my concerns anymore. Whatever I try, I can't get anything to get past the "Booting the primary ROM" message.
However, I installed a stable CM9 on the secondary ROM and... it actually works. But even when cloning 2nd ROM to the 1st ROM, can't get the first to boot anyway.
I am not an expert in Android OS architecture, but could it be related to some kind of modifications made by B2G's build & flashing? Maybe some files in the /data or /system partitions have been altered and are not replaced when fllashing, leading to ROMs not loading up?
Any advice on this is welcome.
PS: English is not my main language, sorry if things aren't explained clearly. Tell me if you need any clarifications about it!
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
Sakujou_Kei said:
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Click to expand...
Click to collapse
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
TheATHEiST said:
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Click to expand...
Click to collapse
This one http://forum.xda-developers.com/showthread.php?t=1363738 (Kernel) and this one http://forum.xda-developers.com/showthread.php?t=2100558&highlight=script (ROM) ?
Ok so I tried the cleaning scripts I linked on my previous message, no changes. I can still boot on Siyah's second ROM, but can't get past the "Booting primary ROM" message.
Ideas anyone?
Hi there,
I hope there ist somebody here who could help me.
I was about to install the lates CyanogenMod on my Tablet and kind of screwed up.
My tablet was rooted, but had some problems installing a Recovery-Image. So I installed the stock Rom (3.0.1) and tried to flash CyanogenMod again. Installting everything via Odin works fine, but when I try to boot into recovery it won't work. So I tried to install the recovery image from the CyanogenMod-Wiki via fastboot. At this point the Tablet schows following error:
Code:
Failed to process command getvar: partition-type : recovery error (0x2)
I had the problem before, when my tablet was rooted, that I could not install the recovery via the Rom Manager...
So I thougt that I might have screwed up my partitions at some point. I went on a hunt for the Pit file and then to install stock Rim with the Pit file again. Well I did find a Pit file which is supposed to work for my tablet. But now everything is screwed up. It will not start anymore at all. Either it ist stuck on the Samsung boot screen or it shows an Android with the exclamation mark and doesn't do anything anymore...
This ist the Pit file which ist supposed to work:
Code:
android_fastboot_emmc_full_p4_16G_32G.zip
Has anyone got a working Pit file für the P7100?
Does the Pit file even fix my partition problem?
Is there a way to manually partition the tab and if yes has anyone got a guide?
I hope there ist someone here that can help me. I would really appreciate it! I know I screwed up badly on this one :crying:
Thanks to everyone taking time to help me in advance.
You might try doing stock image to open if you can get to the recovery and just do a full wipe. ....or try opening your stock recovery if you can and just do a factory reset wipe everything
Sent from my SPH-L900 using xda premium
iallmost said:
You might try doing stock image to open if you can get to the recovery and just do a full wipe. ....or try opening your stock recovery if you can and just do a factory reset wipe everything
Click to expand...
Click to collapse
Thanks for your quick response.
On rare occasion I do get into the recovery and did a full wipe of erverything. I even tried to format all the partitions. On some partitions it just said, that it can not format them. I also reinstalled the stock rom a couple of times as well.
Nothing of this worked so far. I am always stuck on the boot screen or the android with the exclamation mark (after I factory reset ist or reinstalled the stock rom)
Edit: When I boot (not flash) the recovery via fastboot I can get into the downloaded recovery from CyanogenMod.
I tried a little more yesterday to revive my tab...
When I flash the stock rom in download mode via odin, it starts afterwards to a screen with the android and the exclamation mark. At this screen I can press the power and volume + button a couple times and then I am in the stock recovery. Tried every option in there, but it just wont helpt. Afterwards it ist stuck on tying to boot into recovery.
When I don't press the power and volume + button and just wait after flashing stock rom, the tab will reboot after a while and gets into a boot loop with the samsung boot screen...
Tried flashing a recovery rom from clockwork as well, but afterwards I am not able to boot into it. My guess is, that the partitions are screwed up and therefore the tab can not boot... Is there a way to manually partition my tab? Can anyone post the partition table for the P7100 (Galaxy Tab 10.1v)?
Oh yeah... Everything started after I flashed the last nightly from CyanogenMod. That was the first time the tab got stuck on the boot screen and ever since can not get past it.
I scared that I completely broke my tab now and wont be able to get it back :crying:
If your thread name is correct you have a 10.1v if I am correct the code name for it is P3 but the Odin file you posted I assume is for the P4 because of its naming. If it is so the you have flashed the wrong stock firmware image for your tab. You have used 10.1 Wifi and 3G model firmware on a 10.1v. Your tablet could be seriously screwed up but there is still hope if you can get into download mode.
Sent from my HTC One using Tapatalk 4 beta
**Press the thanks button if I have helped you.
WildfireDEV said:
If your thread name is correct you have a 10.1v if I am correct the code name for it is P3 but the Odin file you posted I assume is for the P4 because of its naming. If it is so the you have flashed the wrong stock firmware image for your tab. You have used 10.1 Wifi and 3G model firmware on a 10.1v. Your tablet could be seriously screwed up but there is still hope if you can get into download mode.
Click to expand...
Click to collapse
You are right. I have the P3 and flashed the P4 PIT-file. I have read on a couple sites, that the P4 ist as well the right one for the P3 and haven't found another PIT-file just for the P3.
I only started using the PIT file after my bootloop problem started, which was directly after flashing CyanogenMod (nightly). The version I downloaded was supposed to work all right on my tab, but did screw it up. Do you have any idea which part of my tab could be screwed up and what I could try?
I think it is the partitions and I flashed the stock rom for the 10.1v (3.0.1) a couple times (with and without the P4 file)...
I am getting all right into download mode, but can only get into the recovery directly after flashing the stock rom. After one mor restart I can't access the recovery anymore...