Hey
Some days ago I flashed my boot-logo (the picture what says Samsung Galaxy S6 edge + when I start my phone) on my SM-G928F via TWRP. I think the file was corrupted, because my phone doesn't start anymore. I can't boot in TWRP or system, because there's a never ending blackscreen. I can only boot into download-mode. I flashed samsung stock rom via Odin but that didn't help, because the logo.jpg won't be replaced.
I tried other stuff like adb sideload but it didn't worked.
I think the only possibility to get my phone alive is to flash the stock samsung boot picture via Odin but I don't know how... I need a tar or md5 file for this...
I hope somebody is able to help me in this f***ing situation :crying:
Best regards
DGB
Check the thread by me mentioned below.
Like my replies and threads, it encourages me ALOT.
https://forum.xda-developers.com/showthread.php?t=1936747&page=2
Related
Hi I hope someone can help me. I have searched this forum but could not find a similar situation to what I ended up in...
I tried to install a custom ROM on my Galaxy Tab 10.1 using the CWM/Odin.
This seemed succesful but was not, it did not start but was stuck in the Samsung logo.
So I tried entering the CWM and download and install an original Samsung ROM. I can get it into CWM, but CWM cannot enter the download mode only the other mode.
In this mode all options are available:
- reboot
- apply update from SD card
- wipe data/factory reset
- wipe cache partition
All options have been tried without any luck. In the update from SD card it only shows ...
or Error opening /data/media: no such file or directory
Any ideas how I could get this directory back or put a ROM on the Samsung in this situation.
Odin does see the Galaxy but as I cannot get it into Download mode I am unable to download anything to it.
All or any suggestions are very welcome!
1. CWM (Clockworkmod) =! Odin.
In the beginning, you don't have CWM installed. You install CWM, by flashing CWM on your Phone with odin.
Odin is the Windows Programm, that is used to flash Recoveries/ROM's/Kernels onto your device.
2. it seems, that you still have the default Samsung recovery installed, that meand CWM is not yet flashed on your device.
If the flashing process was succesful (I suppose it was done with odin), but you can't get past the Samsung logo, that means, you probably flashed a rom, that isn't made for your device(ex. a GTab 10.1v Rom).
If you DID flash a wrong rom, then you probably ****ed up the partition table and removed the Download Mode(Odin Mode). Strange thing is, that you still have the Stock recovery.
Could you please redirect us to the rom you downloaded?
Also, did you flash with a repartition on and/or a .pit file?
hi Kaukassus,
thanks for the reply.
OK I checked the files and what I did.
I think I totaly screwed this up. It was a theme I tried to install the AOSP_HC_v1.3_3G+KI1.
I rooted the Tab. So first when the Tab was still functioning installed it on the TAB via USB.
Than tried to install this via update from SD card.
This appeared to work initially. But hung at the start.
After that I tried (via Power Volume Up) wipe data/factory reset.
No luck.
After that I tried wipe cache partition followed by wipe data/factory reset.
And this is what I got now..
Bad news is the Tab was/is a X-mas present and I managed to screw it up even before I officially got it !-(
The valuable lesson you're learning is that you need to be aware exactly what things you're flashing and their compatibility with your device and the software it's running.
You haven't mentioned what specific device you're using or the specific things you've tried to flash (as kaukassus pointed out, direct links to threads where you got the files you tried to flash are best). Not sure if you're aware but not all GT 10.1's are equal; there are several models out there and each and every ROM is specific to a particular device. Verizon LTE GT 10.1's like mine can't take ROMs from any other device for example, it's likely that the new T-Mobile 4G one's wont be able to trade ROMs with Verizon ones . . you get the point.
When you say you installed via USB what exactly did you mean? If you simply copied a zip file via USB to the tab to flash in recovery mode that's not installing; the flashing from recovery may be but the file copy operation is not. If on the other hand you pushed things via ADB or you flash using Odin software then that's a different story.
Best thing to do at this point is to properly identify your device, look for a stock recovery image for Odin and flash that via Odin to your device. At that point you can start from scratch again to build what you want.
Thanks Muzzy996.
You are right. I was in a rush and should have taken more time.
However I am getting somewhere. Managed to get in download mode twice today, don't ask me how. This Tab just will not go into download mode!
However I did not have the stock ROM ready to be installed.
Will keep you updated.
i have the same problem. i just rooted my device was going to overclock. decided to save my rom with rom manager. saved it device went to reboot now the samsung galaxy 10.1 shows up screen goes dim then shuts off, and will cont. do this. i can get into download mode but recovery will not work. is there anyway to download my stock rom. im using verizion 4g 10.1 any help would be great, btw sorry to thread jack
Problem solved.
Managed to get it in download mode again and install stock rom via Odin.
Appeared to work fine. But kep switching off, even after full night of charging.
This morning Tab was dead after recharging whole night..
Got it back on by holding volume down and power button down.
i found a stock rom and im trying to upload it via odin, however odin does not find my tab? any ideas. btw congrats on getting ur tab back
I crashed both my I9000 (galaxy s) flashing custom roms and my tab 10.1 (editing some system files) both ended up just looping but managed to get both back. I purchased a small connector of ebay £1.59 that has just a resistor accross pins 4&5 331k I think anyway plugging this into most samsung devices boots them into download mode. Even before getting my resistor I managed to get things working I think that you'd have to be properly unlucky to really brick a samsung I've flashed both my devices with all sorts of crap with my little resistor I just reset them with ease.
Brian
h2bmess said:
i found a stock rom and im trying to upload it via odin, however odin does not find my tab? any ideas. btw congrats on getting ur tab back
Click to expand...
Click to collapse
did you ever resolve this issue? i am currently faced with the same issue.
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...
Hello , i have a problem with my samsung s3, i tried to flash with odin the custom recovery philz (6.0.0 and 6.48.4) and cwm(6.0.4.7 and 6.0.3.2) with Odin 1.83 and 3.07. Odin finish resets the phone but when i try to boot in the Recovery appears the dead droid with the No Command message and boots in the original recovery. Can anyone help me, please. Sorry for my bad english.
You have a stock firmware, which will restore recovery at each boot.
i understand this. can i fix`it ? last night i spend some good hours searching for some solutions but no luck...
Root your device: you get a modified kernel and cwm-recovery. Then you can replace cwm (by TWRP f.e. ).
so first of all i need to root the device . not to try to instal the recovery via odin directly. can you please tell me some names of what i need to get ?
Go read the sticky thread in general forum, all you need to know is there.
ok thank you very much:good:
I have previously installed TWRP and Cyanogenmod 13 on my Galaxy S4. I'm now attempting to port CyanogenMod to my brother's Galaxy J5. The recovery has built ok (i think) and I've compressed the image to a tar file using 7-zip. I then successfully flashed this recovery tar onto the phone using ODIN 3.07's PDA tab. The flash says PASS, but on attempting to boot to the recovery I get stuck at the "Samsung Galaxy J5" Splash screen, with the ODIN Download Mode text in the top-left, suggesting to me that the recovery has somehow crashed. The phone is not rooted so I cannot access the logs, and both Kingroot and Kingo Root failed to root the device. Has anyone encountered anything like this before? If so, can you help? I'm kind of stuck here - I created a forum account just to post this.
Thanks in advance.
PS: I can't post the link to the image because I haven't got 10 posts yet. If anyone can tell me how to attach it I'll be more than happy to.
I went to cf auto root to find a root file for my phone and like an idiot, downloaded a boot+recovery file instead of the rooting file So I accidentally flashed a recovery+boot tar file on my galaxy j5 prime (SM-G570F) and ever since that it keeps restarting after the very first (samsung galaxy j5 prime, Powered by android) page. I flashed twrp and that works, I can use downloading mode and flash other things, I've tried a number of different boot image files, the problem remains, so Ive decided to flash a copy of stock firmware (latest update) instead. Will that fix it? If not, can I fix it, and how? Also pls provide a stock boot image if you can, I want to try that again one last time. Also please reply fast, If my parents find out, they'll kill me