Related
My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...
Darius, I'm stuck with a brick galaxy player. I can try to flash with a galaxy 3 firmware if you want
Do you know how to make a dump of your device so you can share with me the original firmware?
http://forum.xda-developers.com/showthread.php?p=14493414
I don't know...but I'll try to find
Thanks!
I tried the firmware of galaxy 3, but didn't work
I dont think that its possible, first of all, despite being an android device, it doesnt have radio features, gsm 3g etc, only wifi, there are features that our phone does not support
Anyone found a solution for this yet? Not being able to test this device to it's full potential is really frustrating. Games are laggy and apps just do not run smooth on this one.
Has anyone tried z4root on this? I did and it freezes at "acquiring root shell".
@fedeff: how did you brick it?
Darius_AWS said:
My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...
Click to expand...
Click to collapse
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.
arunmcops said:
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.
Click to expand...
Click to collapse
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?
anon3524 said:
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?
Click to expand...
Click to collapse
factoryfs.rfs is ur firmware backup....
@arunmcops: Thanks for the instructions. If someone try this and upload it'd be great for me.
@anon3524: I accidentally reseted the device to factory, trying to fix a problem with wifi (it suddenly stopped working one day).
arunmcops said:
factoryfs.rfs is ur firmware backup....
Click to expand...
Click to collapse
Ok, I am down to do this process you just explained as long as you or anyone explains to me how to recover the device with this "factoryfs.rfs" in case it gets bricked. You'd have to explain with detail how to grab this file and what to do with it etc. Also, if you could give further details on the initial process, that'd be great since a few things are unclear (to a brave noob like me).
Other than that, I am willing to try it to see the results.
BRING IT OON! *warface*
@arunmcops - I've got one of these, so have uploaded the file you wanted here - sorry, not allowed to post links yet:
dl.dropbox.com/u/6491656/Samsung/factoryfs.tar.gz (please don't flash this, its not a full rom)
I haven't made any changes to the base firmware other than renaming a couple of the phone.apk's to .old (cell standby was eating battery, and this device doesn't have a sim).
For fun, i've also uploaded a dmesg log
dl.dropbox.com/u/6491656/Samsung/dmesg.log
One other thing, i think the partition layout might be slightly different on this (might be wrong, don't have the phone) in that the internal sd card is mounted as /sdcard and the external one is /sdcard/sd.
Hope this helps!
Chris
@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?
fedeff said:
@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?
Click to expand...
Click to collapse
Hi...thats probably because it isn't intended as a flashable rom. Its just a dump of the stock firmware so that arunmcops asked to see to see if it had any resemblance of the galaxy 3 f/w, to see what we'd have to do to get a working custom ROM on this device..
Please don't attack it with any kind of Norse God ...especially until there is a confirmed route back to stock. All thats contained in the files is what you have on your device already - so there is also absolutely no point (for now).
If your having trouble with your device now, you could try doing a factory reset or playing about in Kies - i've fixed my device once after I got curious and flashed a custom ROM on here (which fyi completely messed it up - something like E:multi_csc: error: open /efs/imei/mps_code.dat because we dont have an IMEI code on this device) and then got it back working again - unfortunately i can't remember exactly what I did. Otherwise if this doesn't work I'll see if i can make a working stock package for Odin.
@ctaylr, yes I'm having problems with my device. It got soft bricked. I couldn't make it work using Kies. The only thing I can do is to start it in Download mode. If you can make a working package for oding that'd be great
This might help
http://forum.xda-developers.com/showpost.php?p=9515709&postcount=14
Thanks!
@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks
ctaylr said:
@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks
Click to expand...
Click to collapse
1) I have the 8gb version
2) By doing "wipe data/factory reset" is how I got it soft bricked. (the device wifi suddenly stopped working, and I thought that would help) After that it kept entering in the recovery mode. Then I tried to flash it with odin, now the only thing I can do is enter the download mode
Thanks again for helping me!
News?
Hi! I also like the others I am interested because my Galaxy player has 50 brick and I need someone to do dump the firmware so I can flash through odin! Please would you be my salvation and many other who have this player and would like to fix without waiting for the assistance of a month
Waiting for an answer I greet and thank all users who want to help me
sorry if English is not correct, but I'm using google translator (I'm Italian)
EDIT:
listen to me: http://forum.xda-developers.com/showthread.php?t=726673 This is the guide on how to get the dump of your fimrware if someone kindly did this process with its galaxy player 50 and then upload the file . tar obtained would help all
I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.
ctaylr said:
I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.
Click to expand...
Click to collapse
ok then I'm sorry I read the topic in a hurry and did not realize that you can not do what I say but re-reading now I understand!
ctaylr what do you advise me to do then? wanted to try an get into recovery and restore but I think the 3 keys are disabled enters only download ..
Google traductor sorry
Hi there. I got me a samsung galaxy 550 from virgin mobile canada yesterday, and well, I kinda like it despite being a slow piece of hardware with a 320x240 screen but until I can get enough money to buy something better, I'm fine with this (the phone I had before was a nokia n95, so that's a step up.)
The problem is, I want to try out the official 2.2.1 rom from samsung, and the only way I can do that is to update via odin. actually, that's not the problem, but I want to make a backup of all the apps I've downloaded already, and I just can't get it rooted. at all. z4root, universal androot, superoneclick; they just don't work. the one that was the closest to getting it rooted was superoneclick, and even then it can't finish the job, so I'm stuck with superuser on an unrooted phone, and titanium backup won't work either, so I'm kinda stuck here.
What else could I do?
anyone? please?
6 days later...
You may have noticed this is a "development and hacking" forum. Your problem reads more like a user error than a development one.
I do not mean to say this thread does not belong. It is just that "they just don't work" is something like what a Windows-using grandmother would say.
What are the exact errors you are getting? Preferably, they should be copied and pasted from the terminal itself.
Jason_25 said:
You may have noticed this is a "development and hacking" forum. Your problem reads more like a user error than a development one.
I do not mean to say this thread does not belong. It is just that "they just don't work" is something like what a Windows-using grandmother would say.
What are the exact errors you are getting? Preferably, they should be copied and pasted from the terminal itself.
Click to expand...
Click to collapse
Well, z4root doesn't do anything after it says "running exploit", superoneclick gets stuck on "waiting for device", and the only time it managed to get superuser onto it, it couldn't root the device no matter if I updated it or not; universal androot says "FAILED NO FU GOO", both odin and heimdall fails to connect to the device, and ADB doesn't even see the phone no matter what mode it is. I can't seem to find how to boot into recovery mode (I only ever get instructions to boot into download mode).
ok now in odin I get "cannot open the usb serial port. code: 2". sometimes it's code 5.
Go to madteam.co...dedicated for G5 users,you will get help there at no time
Sent from my blek krupuk
First problem is ADB not seeing the phone. ADB is pretty necessary if you want to debug something. You will need to download LG's Windows driver for your phone if you use Windows. I will include the one I use for my Optimus V here.
On many LG phones it is impossible to boot into recovery or fastboot mode without modification.
Try zergRush from here first:
https://github.com/revolutionary
If not working, try GingerBreak from here:
http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
You may want or need to compile these first which is going to add another level of complexity. Be patient.
The general idea is:
1.setup your drivers
2.get comfortable working with ADB
3.run temporary root
4.immediately flash recovery
5.immediately Nandroid backup everything in several places for safety
6.test Nandroid backup
7.make whatever modifications you like, including permanent root
That's not a lg phone.
Ok so I managed to install cyanogemod and everything's fine. now, I just wanna know, is there any way to enable multitouch on this thing? it's got a capacitive screen, but no multitouch. can that be fixed or is it really just a hardware issue?
Multitouch is not possible,a fake dual touch is possible.
Sent from my blek krupuk
lexobys said:
Multitouch is not possible,a fake dual touch is possible.
Sent from my blek krupuk
Click to expand...
Click to collapse
fake dual-touch?
Hello guys,
a few days ago I dared to root my Xperia X10 Mini Pro with SuperOneClick and flashed a Cyanogenmod 7 Android 2.3.3 ROM. All in all, it worked pretty well.
After doing some apps installation stuff I rebooted in the Recovery (Clockworkmod which obviously came along with the ROM) and made a backup, just for the case. Afterwards, I selected "power off" in the CWM menu because I wanted to go to bed.
Then, immediately, CWM said something like "Error - This recovery seems to be bad" and something with a "risk". I managed however to power off. Can't remember if that worked via CWM or if I pushed the power off hardbutton or removed the battery.
Yet - the ROM seems to work. Now I'm a bit anxious because of the CWM error.
Is there really a risk? I planned to dare unlocking the bootloader soon. Is it dangerous to do this with a "bad recovery" or doesn't that matter at all?
Is there a possibility to repair CWM? Can I just install a new CWM? If yes - how?
Sorry - pretty noobish questions, I know.
Can you help me anyway?
Thanks a lot!
deleted post
Thank you for your help! I already thought that no one would answer because the thread disappered on page 3 of this forum
I've never heard from Odin before and therefore googled it. It only occured in connection with Samsung devices. Are you sure it is compatible to my Sony Ericsson?
Anyway, can I also install a new CWM via ROM Manager or wouldn't you recommend this?
Warning: I'm a noob. Take my advice at your own risk!
From what I understand, flashing CWM via Rom Manager is exactly the same as manual flashing (perhaps better, since the Rom Manager presumably keeps up to date). So I think you should be able to do so and make another recovery (without going through any of that manual flashing stuff). You should get a second opinion just because I'm so noobish, but I think this is the case.
However, from my limited understanding, I don't think the recovery will make any difference when dealing with the bootloader. The bootloader is, more or less, the very first set of instructions executed when the phone turns on. If you mess that up, your phone won't even be able to get into recovery mode. Also, the recovery images are stored on your sd card, which is wiped upon unlocking. Once again, I could be wrong.
deleted post
Dude, what are you talking about? You can't use ODIN on a non-Samsung phone.
trich025 said:
don't use rom manager just use the odin for your safety, you can bet that samsung users are the one benefiting on odin but as you can see erricson and samsung are both android phones and if you examine them both device have similar programs, and one thing, always keep in mind that you have to back up your current rom for emergency uses so you can still get back to were you started in case something went wrong.
if i helped you with this problem you could click the thanks button >>>>
Click to expand...
Click to collapse
OK now this is flat out wrong. Each Android device has a different program used. Samsung has Odin, HTC has an RUU. Not sure about SE. But never use a software made for one device on another unless you want a brick. Just because they both use android doesn't mean they are the same.
Thanks to everyone, especially Product F(RED)!
No offence, trich025, but I guess you were wrong.
Can I destroy something by re-installing or updating CWM via ROM-Manager just in case my CWM has a bug?
First of all, let me introduce myself. My name's Rafael and this is my 1st post in this forum. I hope humbly that you can to help me with the problem that I'll show you then:
Well. To begin, the issue is this... I am working with a telephone that's not mine. Somebody sent it to me to fix it, they said me that the phone doesn't download more apps because of "full memory". When I checked it, apparently it had the internal memory partitioned incorrectly, it said it was 16gb total storage with 7 GB available, but when I was installing some apps and went back to see the memory, it showed the Available Storage Memory with a large negative number, and it wasn't letting me install more apps. Some of the features of the phone are the following (according to MTK Droid Tools):
MTK6589 <---------(Actually it's MTK6571)
Model Name: Galaxy S5
Android Version: 4.4.4 <---------(Questionable)
Model Number: SM-G900H
Base Band: G900HXXU1ANCE
Then, to see if I could make some change, I decided to install a custom ROM, apparently for MTK6589 (at that time I didn't suspect about the horrible phone's falsehood). I wanted to see if this ROM brought the partition configured correctly. I tried to carry out the installation by the CWM Recovery from SD card. It turned out that the installation did not exceed 10% and it froze there. Then I removed the battery of the phone and inserted it again. When I try to turn it back on, it stays on the screen Mediatek. And from there, it does absolutely nothing more.
I've tried to flash back the backup that I made to the phone with MTK Droid Tools, both version 5 of SP Flash Tool as version 3, but I'm still not achieving positive results, always it throws me errors errors and more errors . I've searched all over the web, compatible ROMs for this phone, but apparently there is not anything. The only way in which (at least) it begins to flash from SPFT v5, is loading a ROM MTK6571; if not, it only throws errors. However, I've already tried, but it gave me error. It appears when the yellow bar that says Download Flash reaches 3%, and then it throws the error.
The only possible solution I see is to make a ROM (from the backup I made to the phone with MTK Droid Tools before to **** it up) installable from recovery (CWM) that is the only thing that works relatively well. And I have not reached that conclusion alone, but in bilateral agreement with an expert from another forum with who I have almost a month discussing the issue.
I really need help buddies. I am desperate because I'm a bit under pressure because I have almost a month with the phone without achieving the desired results. :crying:
Greetings and thanks in advance to any of you who want to help me.
PD: Sorry for my bad English if I committed mistakes.
Post removed
Killwish said:
Download stock firmware from http://samsung-updates.com or http://sammobile.com
And flash it via odin...
Good luck
Click to expand...
Click to collapse
Do NOT do this. None of them will work.
Your issue is that 99% of the time clones dont not have the software they claim and are never made by the company they claim they are. You could try porting a rom over that has the same chip but ill be honest. XDA doesnt really do anything with cheap knock off devices. Most people avoid them like the plague.
Sorry for my previous post..... I didn't read carefully. It's not s5 its clone....
Another way...
zelendel said:
Do NOT do this. None of them will work.
Your issue is that 99% of the time clones dont not have the software they claim and are never made by the company they claim they are. You could try porting a rom over that has the same chip but ill be honest. XDA doesnt really do anything with cheap knock off devices. Most people avoid them like the plague.
Click to expand...
Click to collapse
I was thinking about to take system.ubifs.tar and boot.img from the backup, to turn it into a bootable (installable) ROM from the recovery. Is it somehow possible?
06rafagar94d said:
I was thinking about to take system.ubifs.tar and boot.img from the backup, to turn it into a bootable (installable) ROM from the recovery. Is it somehow possible?
Click to expand...
Click to collapse
Best advise is that you can try. Like I said we dont deal with clones at all really.
Worst thing that will happen is that it wont work and you learned a lesson about clone devices.
This is absolutely unfathomable.
I find it nearly improbable that in order to create a FULL backup of a phone, you must root it, first.
With the possibility existing that an attempt to do exactly that, may well brick it.
And then we don't need a backup. We need a new phone. :silly:
But, an actual backup would have us able to re-start and try again (and again, and again, ad infinitum).
In hand, one bricked handset (ZTE N9132, and not actually via failed rooting). Let's call it TARGET.
And, luckily, one un-bricked handset of same (ain't eBay great). Let's call it SOURCE. They are running under version 5.1.1
Yes, I know, swap the SIM, change IMEI with carrier, back in business ... er, SOURCE broken glass and just ugly condition notwithstanding. BUT, as a learning experience for me, and a wish-I-had-done-that re-do for others with a similar brick, here's my desire.
I've been all over the web and just when something sounds promising you read, "this next step requires a rooted phone" .
So, here is a working SOURCE phone. stock. just as received from vendor. not setup. factory reset. no SIM.
I want to create a COPY/BACKUP/ROM (correct my wording, please) of this SOURCE phone. Wait... format requirement coming.
Then need to PUSH/SIDELOAD/UPDATE that SOURCE image onto TARGET, and we must note for record that TARGET only boots in recovery mode (i.e., not recognized by PC). That pretty much leaves the "from SDcard" option.
ADB, fastboot, FTM, something else? ... any and all NOT requiring "root".
Because both phones are wiped/reset, user data, settings, etc. are immaterial.
We would be only concerned with creating the minimum image from SOURCE possible to allow TARGET to "snap out of it".
How about it guys ?
Can this actually be done WITHOUT ROOT?
Thanks in Advance
Hi !
I wish you would post a little bit less fancy because some of us aren`t native English speakers , like me ... anyway , let me tell you what I`ve understood so far
You have 2 devices which are the same (note that "same" doesn`t mean same brand but exactly same brand VARIANT as same brand may have multiple variants)
You want to transfer a nandroid backup from one to another directly using a PC when both connected to the same PC
First , that`s impossible
Second , even if would be , one of them isn`t recognized by PC due to "brick" status
So , disconnect them both , get a coffee , pull the backup from the working one , save it on the PC , keep on drinking coffee and find a way to un-brick the other device
When done ... hum ... well , if the bricked device gets back to life , no need to restore any backup , right ?
I understand what you want , you think that pushing a backup from a working device onto a bricked one may fix it , nope , it won`t work
How to unbrick your device , as I couldn`t find any support here on XDA for it , can be posted here https://forum.xda-developers.com/android/help
And to make a nandroid you don`t actually need root , you need an unlocked bootloader which allows you to flash a custom recovery which has this function
Here is an interesting tool
Good luck !
xanthrax said:
Hi !
I wish you would post a little bit less fancy because some of us aren`t native English speakers , like me ... anyway , let me tell you what I`ve understood so far
Click to expand...
Click to collapse
Mulțumesc, camarad. Dar nu e problema mea. Sunt Ucraina, BTW.
xanthrax said:
You have 2 devices which are the same (note that "same" doesn`t mean same brand but exactly same brand VARIANT as same brand may have multiple variants)
Click to expand...
Click to collapse
SOURCE Model=N9132, HW= cvzA, s/n = 329xxxxxxxxx
TARGET Model=N9132, HW= cvzA, s/n = 323xxxxxxxxx
both running Android 5.1.1
in MY book, that's pretty INvariant, but, hey, bits could differ
xanthrax said:
... deleted ...
I understand what you want , you think that pushing a backup from a working device onto a bricked one may fix it , nope , it won`t work
Click to expand...
Click to collapse
YES! That's exactly what I want.
And "IT WON'T WORK" is the part that blows my mind.
Exactly the situation when you restore a dorked device from a bad/failed upgrade via recent backup.
But, in this case, WHY doesn't that work?
xanthrax said:
How to unbrick your device , as I couldn`t find any support here on XDA for it , can be posted here https://forum.xda-developers.com/android/help
Good luck !
Click to expand...
Click to collapse
Thanks, Xanthrax
New posting coming to /help
The process of writing the partitions is not just a simply copy /paste (it's above my understanding especially on Samsung devices...) connect to Odin and you'll see how many processes are used in
Follow that tutorial and also post there you're findings or concerns, I'm sure more skilled people will be able to offer help, Haraso camarad! ?
Sent from my Darkside of Oneplus 3T