I used Oden to flash a Samsung Galaxy S II rom to it and now, it only shows the Samsung logo at bootup. No recovery menu. If I try to access the recovery menu, it kicks me out and reboots. Samsung galaxy player 5.0 All Touch Buttons including home.
If you can get into download mode by holding volume down at boot, you can just reflash stock.
Sent from my YP-G70 using Tapatalk
Um, okay, for future reference NEVER FLASH ANYTHING NOT SPECIFICALLY MADE FOR YOUR DEVICE! I learned that the hard way, so not saying your stupid, just think a little more before you try to flash a rom for a dual core phone that's only resemblence to a Galaxy player is the word Galaxy. I find that for some reason, each phone has to have a different strain of android, and their roms never, NEVER, mix. So, I am stating this just to warn others new to android, not to make you look bad (I made a similar mistake of trying to flash cwm that someone assured me couldn't possibly brick my device, what a noob I was!).
Yup... NEVER flash something not designed for your device unless you know EXACTLY what the hardware differences are and how to deal with them, or you've been given specific instructions on how to port firmwares to your device.
(I9100 ROMs are so easy to run on I777 that they can be autoported with a CWM-flashable package now, but that's because the I777 is 95% identical to I9100. There will be nothing that can be "hellraised" to the Players, except possibly being able to creat "common" ROMs that target both International and US with a small zip file containing the differences flashable in CWM.)
Mate, I'm in the same boat where you used to be. Just a little worse.
Long story short: flashed, by mistake, the entire i9000 rom, including boot loaders, through Odin. Got a "black screen", "no reaction" brick. Computer won't detect no matter what button combo I throw at it.
Samsung Galaxy Wi-Fi 5.0"
YP-GB70CWXAZ (8GB) brazilian edition
I need some details about jtag and the micro-usb port. Also, in the current state, can I try to format a sd card & see if the player recovers from it? Like the Samsung Development Board? When everything is screwed, the usb pins can be used as a jtag port to avoid opening the device, even though I already did it.
PS: I've already located the 12 pins (jtag) & another 4 points on the main board. Just don't know how to check if the second ones are also jtag. The blue coating is also scrapped & ready.
Thanks.
Peace.
You might want to try AdamOutler oneclickrecovery before messing with JTAG. You can find it here.
This will upload a bootloader so you can re-flash the device with odin.
I have tried to recover my YP-GB70 (32gb korean version) with AdamOutler tools with 80% success.
Anyway thanks a lot for the tool and your great help.
What I did:
under odin I flashed original YP-GB70 32gb PIT plus the provided "AdamOutler bootloader and the latest korean firmware (pb is the same with any earlier FW version)
The result i got is almost perfect, i passed SAMSUNG logo, the boot ring tone and went the GALAXY sky where it stay looping. (All wipes where done before.)
My questions are:
-What is missing in this Flash process?
-Is the bootloader specific for US version or device related?
-Any idea of what I should do to succeed?
You are welcome to expertize this issue because a solution will be a good tool for many imprudent guys like me.
attached picks of 3 diferent trials done lately.
best regards from France
Lolo9393
Related
Hi, I'm a bit stuck with a problem on my S2 HD LTE SHV-E120K. While once playing a game the phone heated up pretty much (the charger was connected). After that it rebooted. I thought that the stock ROM got corrupted so I changed the recovery from Tegrak (phone was rooted with this a while back) to CWM 6.0.3.6 and loaded CM10.2 (cm-10.2-20131027-NIGHTLY-dalikt). To my surprise its still rebooting. But when I disconnect the charger the phone reboots and at times when charging it also reboots. If the charger is not connected the phone does not boot up.
Can anyone say what or where the problem may be?:crying:
Sounds like USB board on the fritz. I don't know for certain if your specific variant uses the exact same boards as the I9100, but have a look at KeithRoss39's guide to replacing the USB board in General (search for 'replacing USB charger board').
You'll probably find Keith's how-to will hold true for your model as well (so far as following the same procedure goes), you just have to ensure you order the correct replacement part - and the way you do that is by removing the board currently in the phone, noting the revision or part number, and making sure you order the exact same part.
Wow! I did suspect this but never thought it could be the case. I'll look at that article. But anymore suggestions are welcome.
But if the battery is fully charged then the phone should boot up without a problem right? But it doesn't It needs the charger to be connected for it to boot.
When you say USB board would you be able to say if you mean the USB port specifically or some small chip on the USB board assembly?
The board has the port attached and is really cheap to replace (~US$10 or so), and quite replaceable by most people if you follow Keith's guide. When the board starts acting up, it often shows symptoms you're describing. And as it's a cheap/easy fix, that's what I'd be doing. Try a clean install of stock first (even if you've come from stock recently) to absolutely rule out a rom-side problem if you want to. I'd be surprised if it's still not the same though.
As to specifically what component on the board is causing the issue, no way to say for certain, and it's not really relevant here; the fix is still replacing the entire board given the modular design of phones these days & the low cost of doing so.
I saw Keith post to another thread in Q&A just now, I'm sure he'll also post to this thread & give you a bit more info (he's the resident expert on these things here).
Ok got you. I have not been able to find any links to stock rom downloads. Do you have any? Also, what recovery is to be used with the stock rom? My phone was bought from Korea on ebay. It displays ''Olleh'' in the boot image. Just to let you know so you may be able to figure out which stock rom this is.
I've checked Samfirmware, and they don't have firmware for your device specifically, so I have no idea (beyond Googling) where you might find stock firmware or if you can use firmware from other devices in the same 'SHV' family. I honestly don't know.
I gave you advice about the USB board because it's generic & quite likely the source of your problems, but I'm not even a little familiar with your device so I can't give you detailed/specific help with it.
Given how little traffic the S2 forums get these days & how few people here have SHV devices, your best bet (other than waiting, and it could be a very long wait) is to trawl through the forums here with XDA searches (or Google searches with XDA appended to your search terms, XDA search isn't the best at times) to find the info you need.
Would you know how to remove CWM recovery and get it back to stock recovery after I install the stock rom?
If you flash a stock rom, stock recovery will overwrite CWM. Everything will be stock (recovery, kernel, etc).
Edit - Assuming your phone is similar to the I9100 in having recovery baked into the kernel (unlike more recent Samsung phones which have the kernel & recovery in separate partitions).
Hello,
I know, my question is not new for the most of you and I think it is asked over 1000 times. I tried but I can't find the right working answer for me.
I have a problem, with my old Samsung Galaxy SIII GT- I9300 with T-Mobile branding.
Sorry for my english, but I did not found something useful on german websites but much useful in your forum, so I hope you may help.
The Phone is old, so I have no guarantee any more. I got it from a friend and for him it worked very well till now. It started with freezing on pages and the friend tried to recover the device and I think he did something wrong. The device ended up bricked.
Now, when I want to switch on the device it shows a white screen, with grey and black snow everywhere. Only thing I still can do is going in download mode, then it shows:
___________________________________________________________________
odin mode
Product name: GT-I9300
Custom binary download: No
Current Binary: Samsung Official
System Status: Custom
The robot picture
Downloading...
Do not turn off target !!
________________________________________________________________________
The friend who owned the phone said it is broken and buys a new phone.
I am new to modification phones and all things like that and I haven't got a clue what I'm doing, but I'm interested in learning and don't want to give up.
I read and read and read and looked at google and everywhere and the more I looked, the more different advices I found, but I don't know what will work for my device.
There is another problem, since I don't have a windows or Mac machine, I can't use odin. I work with linux, kubuntu 14.04 ( this is another project,I haven't a clue from, but I'm learning for fun) and I just managed to download JOdin3 Causal, working with heimdall-frontend 1.4.0-0.
I tried to flash firmware with one part and firmware with 3 parts, and I always get from Jodin: that the phone is connected, but there is no pit-file.
I added plenty of pit-files I found in the net, but Jodin said the pit-file was corrupt or broken or Jodin shows on top, left side: „running“ but nothing happens for hours.
Can someone help me. I think I need a firmware and the right pit-file for this firmware. What kind of firmware is not interesting for me, I just want to see the device come back to life again.
I found in the internet, that there is still hope, if the phone shows in odin mode a product name.
Because of this I think that my phone isn't scrap jet. Am I right?
Thanks in advance for your replay.
nina
No, your phone is dead. Try the dead boot recovery thread in general forum for a test but you will need a box.
Please, I hope somebody doesn't start berating me for not reading XDA posts about my Verizon Galaxy Note II more thoroughly. I have read many over recent years and been saved by quite a few during the hacking of my SCH-I605. Furthermore, I've been working in software development and network administration for decades now, so please don't somebody suggest I not mess with rooting my phone, custom recoveries, et cetera. I am here asking questions to make sure I don't hard brick my phone. Not asking resulted, about two months ago, in almost succeeding at Kobol's very interesting "short the tiny resistor" mode of getting out of a boot loop. I have a fully functioning phone now running rooted Kitkat and it's a sturdy platform, runs really great after I melted most of the bloatware and froze the rest (in case I ever need it), but I'd still like to move on to Lollipop and there is only one means for doing so which I know of (CyanogenMod), which I think may be problematic unless I am able to reflash an earlier ROM with unlocked bootloader.
The basic question I need verified is multi-part but basically boils down to this:
1. Is it or is it not true that if one is at baseband version I605VRUFND7, the bootloader is locked and one cannot install a custom recovery? (I think I read that in a few places anyhow.)
2. Is it or is it not possible to flash back to I605VRALJB from rooted I605VRUFND7?
3. Is flashing back to I605VRALJB, then installing TRWP or CWM, then using custom recovery to flash the latest CM12.x the best and only way to get from rooted Kitkat to rooted Lollipop?
4. I know there are some functional improvements in Lollipop but are they really that significant? I like the whole "material" thing which comes with Lollipop, but not at the price of loss of functionality.
Anyhow, here's my little sob story, which has a happy ending -- perhaps some of these details will elucidate my situation and lead to better answers:
I got tired of waiting around for Lollipop and had been unrooted by Kitkat for almost a year when I rooted again back in July 2015. I had wanted to go with the latest CyanogenMod Lollipop version, but ran into problems first using Heimdall (which refused to properly connect and write) and then trying Odin (against best advice post-root) to install a custom recovery (preferred TWRP but would go with CWM). Always led to that "unauthorized software" boot screen, which then necessitated reinstalling stock Kitkat and rerooting (I found the Ghettoroot .BAT file worked okay.) All was well, I was too busy to think about Lollipop but I woke up one morning about a month after I rooted Kitkat to find my Note II was stuck on red Verizon book splash-screen. Found a great article and YouTube showing all the keypress sequences which might exit a Note II from been stuck in boot -- but unfortunately not until after my further finagling just left me with a dead no-display-at-all device. I undertook Kobol's method, which requires partially reassembling the Note II's electronics outside its case and attempt to reboot with a very tiny screwdriver shorting a minute resistor on the motherboard right adjacent to the CPU -- I did in fact see the screen flash on briefly -- but I held my little screwdriver down too hard, accidentally gouged out the tiny resistor, and ended up buying a refurbished motherboard which very likely may have been scavenged from a stolen phone before going on sale on eBay. New motherboard worked great, I erased the original owner's info and data and proceeded to reinstall and root Kitkat. (Motherboard was already at I605VRUFND7) when I received it.
Anyhow, I also tried to install a custom recovery after I had new motherboard and rooted Kitkat. Using the TWRP Manager app put me back on the "unauthorized software" boot failure screen from Verizon, but I was able to Odin back Kitkat easily enough without losing my apps and configuration data. I believe I tried to use ROM Manager and Flashify as well -- but didn't find those apps very cooperative (though I didn't bother to upgrade to "pro" level on any of these in cast that matters). Unless I am mistaken, all these apps just place a zipped update file in the root of my internal SD card and then just hand it over to the Note II's stock recovery. I figured I just needed to stop and regroup later. That was a few weeks now.
Honestly, after the ordeal of having to replace a broken motherboard, and also -- after having looked at Verizon, Sprint and AT&T and the new Galaxy devices with no removable back and cracking the phone open necessary to replace the battery or upgrade the hidden microSD card and not liking that one would have to pay $600 over two years for a smartphone even further crippled at the cell carriers' requests -- it's even more important to me to be careful not to damage my Note II. (In fact, my Note II had turned out to be irreparable, I might even have even bought a refurbished unlocked Note 2 or 3 or 4 -- Samsung has made a real error on their latest generation of phones with their sealed backs and no user-accessible microSD reader.)
Yet, perhaps naively, I really do want to move on to Lollipop and even Marshmallow when CyanogenMod makes that available. So I really would appreciate it if you guys can verify whether what I intend to do (downgrading to pre-Kitkat in order to install custom recovery and then CM12.x) is workable? Or if there's a better solution? Or if I should just be content to have Kitkat rooted with all the fat cut off?
Many thanks. Hope my digression was not too long. Please don't anybody yell at me. XDA Developer's web forum is so full of very useful write-ups but unfortunately also some incorrect information and a lot of just plain useless posts -- it's really difficult sometimes to tell posts by guys who are actually experts from post by well-meaning folks with a lot of ideas but not so much expertise specific to SCH-I605 and VRUFND7. And I really need to get this right. (Granted that nobody on the forum can be held culpable should on mess up my phone based on their advice.)
Thanks once again!
This is my first post to a forum, so please bear with me...
So a few days ago, a friend of mine got a Verizon Samsung Galaxy S4 from someone, for free. He got it for free because the screen's glass is cracked a bit, and the phone is bricked; the previous owner didn't know what to do with it. I decided I would try to fix it, because if I do, I might be able to buy it off him and give it to my little sister, who currently has a dying iPhone 5C.
When I turn on the phone, it boots, showing the samsung logo, showing the red Verizon screen, and playing the boot tune. Then, just when you'd expect it to go to the OS, it shows a screen which at the top reads "Device memory damaged". Below that, it says "The data partition has been corrupted. You need to reset your phone to factory defaults. This will erase all your data." And below that is a button, which says "RESET PHONE". Tapping on it does nothing.
I have worked with android phones before (rooting, ROMs, locked bootloaders, bricked phones; even all these things on a Galaxy Gear smartwatch), and I know what the data partition is. I remembered that the recovery on samsung phones have an option to wipe the data partition. So I tried to access the recovery menu by holding Power, Home, and Vol+ when the phone is off. It doesn't work either . It shows the Andy robot laying on its back with a door open on its belly, with a warning icon popping out. So the recovery is dead...
I thought I could try to fix the recovery by flashing it with Odin :fingers-crossed:; Didn't work. It is blocked because the phone can't verify version . Then, after a little more research, I realized I might be able to fix the recovery by flashing a whole stock ROM. I don't know what firmware the phone is running, because I can't ask the previous owner. So I tried a few KitKat ones, and they were all rejected by the phone. Then I booted the phone back up, and I realized the RESET PHONE button acted like it was part of a Lollipop UI (There is a darker circle that extends from the part of the button where you tap). So I went back into download mode and tried to flash the 2 OTA versions of Lollipop (OC1 and OF1). The error this time was "SW REV. CHECK FAIL : fused : 8 , Binary : 6". This may or may not be the error I got before with the KitKat ROMs. I don't remember, and I'm not at my desktop to try the old ROMs.
After looking up this error, I found no exact results, but there were ones with a similar error. People said that it means a ROM is being flashed that is too old to pass the downgrade prevention system. I've been trying to flash what seems to be the latest firmware revision for this phone (OF1). Any ideas? Are the OSs I'm trying to flash somehow too new for the phone (even though I've tried all of the stock Lollipop ROMs. Should I give the phone back to my friend and tell him it's dead?
Thanks in advance!
I can't post images because I haven't posted here (or on any forum, for that matter) before.
Well, it seems really bad but you can try Samsung Smart Switch or Verizon Wireless Software Upgrade Assistant to repair the phone, else way JTag it's another option
Fuse 8 is OF1
Matthew M. said:
Fuse 8 is OF1
Click to expand...
Click to collapse
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
you probably needed to flash a lowship odin tar and repartition
Legitsu said:
you probably needed to flash a lowship odin tar and repartition
Click to expand...
Click to collapse
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
evanzolman said:
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
Click to expand...
Click to collapse
a normal odin tar will not fix a bad partition regardless of the .pit you need a tar that s a _user_Low_ship todo a full format odin was failing because the partitions where screwed and you weren't using the correct image
go to sammobile.com they have all the s4 all variants roms.
evanzolman said:
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
Click to expand...
Click to collapse
I am not aware of a definitive guide on the fuses. I found it by trial and error
Envoyé de mon SM-G903F en utilisant Tapatalk
Hi guys.
My uncle gave me his Galaxy S3 GT-i9300, asking me to fix it. The reason is that when turned on it is stuck at the Samsung Galaxy S3 logo, without booting to the system. I can boot to Download Mode, speaking about it later. I can boot to recovery, but it gives a lot of errors about can't mount partitions or directory and files not found (such as the photo below in the attachments). Searching a while I understood that these errors are caused by broken partitions. I've successfully booted in Download Mode, but I can't flash any file with odin. If using the .pit file to repartion the eMMC, it stucks to "Get Pit For Mapping" step or it fails with "Re-partition operation failed", it depends on the Odin version I use to do it. I've let the computer to his things with the "Get Pit For Mapping" for over a night, without success. Still stuck. I've tried to flash stock boot.img, stock recovery.img and various other single images from the Stock Firmware downloaded from Sammobile. I've also tried to flash twrp and cwm. No succes, all of them stock at a certain percentage. Boot and Recovery Image always fail at 2/3 of the operation with "Complete(Write) operation failed". Neither "Nand Erase all" option works, it also fails.
I've tried so many things, including booting from the SdCard short-circuiting a resistance ç(found a giude about it on xda), no success also with this. I can't neither flash bootloader or so.
Tried to flash change cable, change port or so. I've also changed computer, no success.
My idea was to boot into TWRP (my favourite custom recovery) to save at least the photos and the music, and then flash the stock firmware.
I actually can't resolve this. Can you please help me? All help will be appreciated.
P.S.: I could try to ADB Sideload the rom, but I couldn't find .zip packages of official OTA updates.
P.P.S.: Is there a way to pull out files through ADB Sideload? I couldn't find one...
Thanks, EmaMaker.
It really looks to me like the internal memory chip has failed.
audit13 said:
It really looks to me like the internal memory chip has failed.
Click to expand...
Click to collapse
Agreed. All options have been exhausted. It's dead.
As for the adb question, only if you have a working recovery that is adb enabled like twrp or cwm..
audit13 said:
It really looks to me like the internal memory chip has failed.
Click to expand...
Click to collapse
Oh come on, it can't be dead after a trivial recharge...
My s3's memory chip is still alive after 6 years and only the power button broke. And my new s3's main board (which was produced in 2012 as by written on the board) works perfectly.
Isn't there a way of completely erase the memory and reflash it, without problems?
I could make a friend change the emmc for me, replacing it with my old main board's one. Once an emmc is extracted and works as a stand-alone chip, can i try to recover files from it?
There are many s3 users whose phones are completely functional after many years of use but failed memory chips in any phone is possible.
I have a nexus 5, Samsung s4, and Samsung note 2 with defective internal memory chips. These were given to me by family and friends to use for parts. Before taking them apart, I tried everything I could to flash the phones without luck.
By normal means the phone is f00ked. Once you get to the point where it asks for pit file 9 times out of 10 the nand is corrupt. The problem is how sd memory works in the first place and its inherent flaws. That is why some phones work forever while others can die within days.
As the phones were built in many different factories using many differently sourced parts the chances of "Sudden Death Syndrome" is quite high. Some manufacturers actually purchase prebuilt cheap Chinese phones and rebrand them as their own.
If you wanted to change the nand I'm not sure if any of the chips are married to each other so that's a risk in itself. You can swap the board out with a salvage phone. You can try jtag. All of which could cost you the same as buying another s3. They are too cheap nowadays.
If you want a wierd example, my stock rooted s3 borked royally from turning off in the middle of the night due to no power. Turned it on and it puked a load of errors "e: unable to mount /****". I flashed the latest official cwm and then flashed the stock recovery and as I rebooted thinking that it was dead it booted to os!. All errors solved!. Lost root completely but at least I could flash it back to stock and start over.
That was when I started to see a pattern on the forums where twrp was the common denomination between the cases of borked phones so I googled it and there is documentation on twrp github which states the same but the cause is currently unknown. This is where I always state to be careful rooting your phone in the first place as twrp is the only recovery for nearly all phones, it has an inherent fault that no-one knows the cause of and it can lead to a dead phone. Where any other recovery is available I'd recommend that over twrp. I also noticed that the most common combo is twrp and custom roms as THE most likely to go tits up across all devices. If you must root keep it stock root.
Otherwise if twrp didn't kill it then its genuinely a dead nand, probably faulty at birth and it was a matter of time. I honestly think Samsung cheaped out on parts for the s3 and that is why so many fail.
shivadow said:
By normal means the phone is f00ked. Once you get to the point where it asks for pit file 9 times out of 10 the nand is corrupt. The problem is how sd memory works in the first place and its inherent flaws. That is why some phones work forever while others can die within days.
As the phones were built in many different factories using many differently sourced parts the chances of "Sudden Death Syndrome" is quite high. Some manufacturers actually purchase prebuilt cheap Chinese phones and rebrand them as their own.
If you wanted to change the nand I'm not sure if any of the chips are married to each other so that's a risk in itself. You can swap the board out with a salvage phone. You can try jtag. All of which could cost you the same as buying another s3. They are too cheap nowadays.
If you want a wierd example, my stock rooted s3 borked royally from turning off in the middle of the night due to no power. Turned it on and it puked a load of errors "e: unable to mount /****". I flashed the latest official cwm and then flashed the stock recovery and as I rebooted thinking that it was dead it booted to os!. All errors solved!. Lost root completely but at least I could flash it back to stock and start over.
That was when I started to see a pattern on the forums where twrp was the common denomination between the cases of borked phones so I googled it and there is documentation on twrp github which states the same but the cause is currently unknown. This is where I always state to be careful rooting your phone in the first place as twrp is the only recovery for nearly all phones, it has an inherent fault that no-one knows the cause of and it can lead to a dead phone. Where any other recovery is available I'd recommend that over twrp. I also noticed that the most common combo is twrp and custom roms as THE most likely to go tits up across all devices. If you must root keep it stock root.
Otherwise if twrp didn't kill it then its genuinely a dead nand, probably faulty at birth and it was a matter of time. I honestly think Samsung cheaped out on parts for the s3 and that is why so many fail.
Click to expand...
Click to collapse
Thanks for your exausting answer. I will search more about jtag in the next days. I tried to flash both twrp and cwm, none of them worked.