Hey guys, there's a ton of confusion going on because of partition tables and what not. The Galaxy Player 4.0 uses a BML partition table. The Galaxy Player 5.0 uses a MMC block partition table. I ran into problems with 8g versus 16g partition tables because the 8gig won't work on the 16gig and vice versa. We need a master list of PIT files. This is that master list.
International is the standard version. Because of copyright problems, US versions may be different.
PARTITION TABLES
Galaxy player 4.0 16gig thanks some korean site.
Galaxy Player 4.0 US 8gig thanks hyperrunner
Galaxy Player 4.0 International 8gig thanks zaclimon
Galaxy Player 5.0 16gig thanks ishish9
Galaxy Player 5.0 US 8gig thanks redpirate8
Galaxy Player 5.0 International 8gig thanks aillez
Please post your partition table and I will link it in the above. If you have one which is not in the list, let me know.
How to obtain your partition table
Download Heimdall Suite here: http://www.glassechidna.com.au/products/heimdall/
Open "heimdall-frontend"
if you encounter errors in windows, you need to install the zadig libusb driver. Remember to "show all" from the menu in the program.
Put your device in Download mode
Click the Utilities tab
select an output filename. The file should always end with a "pit" I'd recommend something descriptive. eg..
GalaxyPlayer4.0-16G.pit, or G70-GalaxyPlayer5.0-8gig.pit
upload that file to http://mediafire.com
I recommend Mediafire because they have no distracting adds, no 50 second wait time, no signup, and everything is straight forward as opposed to 99% of the other file hosting sites.
post the mediafire link here in the forum
Ok, first, I don't think there are 16gb versions, other than maybe one for korea?
Second, The main issue here is the international version vs. the U.S. version, I believe there is quite a bit of difference in the firmwares of these versions, so you should probably have sections for "U.S. 4.0, U.S 5.0, International 4.0, International 5.0"
You might get more positive results that way
I am needing the 4.0 U.S Pit, btw, so thank you for creating this thread!
Edit: also, didn't you say in your other thread that heindmall doesn't work with these?
Here you go,
DOWNLOAD
P.S. - I couldnt get it the way you asked me so i ran terminal and used this code.
dd if=/dev/block/bml2 of=/sdcard/part.pit
Also this is the Samsung Galaxy Player 4.0 U.S. 8GB Version
Thanks, but it still doesn't work!? Stuck at "set partition" forever!
Wonder y hmmm..
Hyperrunner said:
Wonder y hmmm..
Click to expand...
Click to collapse
You need to get the Heimdall partition. I observed the same behavior before. and I was thinking it was a fluke.. It looks like on this device the heimdall dump will set the partitions, a bml dump wont.
I'll remove that and we're back at square one.
We could really use some participation here. You'll be thankful if you brick your device. Currently there are no recovery options... This is part of creating the first one ever.
Yeah i have been trying that but Heindall says that libusb error 13 for some reason i would get it but i cant since the error. Do you got a solution for it. I would do it but i cant get pass that error? I've tried installing libusb.
Hyperrunner said:
Yeah i have been trying that but Heindall says that libusb error 13 for some reason i would get it but i cant since the error. Do you got a solution for it. I would do it but i cant get pass that error? I've tried installing libusb.
Click to expand...
Click to collapse
Try making sure you have the samsung usb drivers installed; http://forum.xda-developers.com/showthread.php?t=961956
and usb debugging enabled in /settings/applications/development. After that is enabled, just plug it into the pc, don't select connect to computer.
All that is installed, just cant seem to connect ive checked everything.
You are going into download mode, correct?
Edit: Do you have the proper package for your os?
Adamoutler, have any advice?
Edit2: Figured it out, go to "drivers" in the heindmall file, run the zadig.exe, select "list all devices" in options, then install "Samsung composite USB".
Worked for me!
Edit 3 : Thanks i got it, i guess win was'nt detecting it.
Download
look at my previous post I edited.
iJimaniac said:
Try making sure you have the samsung usb drivers installed; http://forum.xda-developers.com/showthread.php?t=961956
and usb debugging enabled in /settings/applications/development. After that is enabled, just plug it into the pc, don't select connect to computer.
Click to expand...
Click to collapse
Don't listen to this. He does not know what he is talking about.
Make sure you select all in zadig, and try rebooting.
Yup all done and posted. Hope it work, please keep me updated on it.
Hyperrunner said:
Yup all done and posted. Hope it work, please keep me updated on it.
Click to expand...
Click to collapse
EDIT:
Nevermind it doesn't work. DO NOT FLASH THIS PIT FILE. Now I get a bunch of E: failed to mount errors.
Now I'm bricked too. Need a valid PIT file to flash back to stock.
WAIT, ive seen some videos in which you flash it. Most of them the md5 or tar file contains more stuff other than factoryfs.rfs and zImage.
Or is that ok since its not a phone if it is not or there is a problem just tell me and give me the commands to retrieve these needed files and i will make a new Firmware.
EDIT 2 Look im trying my best i can. I have never used odin or kernal and all the other files md5 or commands so dont give me any crap. Ive been trying to help you guys from the start. Im trying to learn while doing this it is not simple. Other morons would not even get passed the commands on terminal. If you dont want my help well then you wont get it. Currently im the only one helping you guys. As i said in the post above me if you need any other files in the md5 just give me the commands and i will reupload them.
EDIT 3 NVM
Ok, I think I know what to do, but we should move to a new thread in "general" so we don't clutter up this thread
You start it. You really need to reply faster.
iJimaniac said:
Ok, I think I know what to do, but we should move to a new thread in "general" so we don't clutter up this thread
Click to expand...
Click to collapse
Go ahead and clutter it. As long as we get a complete list, were fin
Hyperrunner said:
Edit 3 : Thanks i got it, i guess win was'nt detecting it.
Download
Click to expand...
Click to collapse
This is a USA 4.0 correct?
Related
When I try to reinstall the firmware it will not work. I get a message update failed: (1). This is done in the recovery section. I have put the latest firmware in, but nothing happens other then the error message. When I turn on the Archos it just goes straight to the Archos A70S Recovery screen. I have totally reformatted the device several times. Any thoughts on this board? Thanks.
Aaron
Try to format the device and then install the firmware, also, make sure to have the right firmware so the archos stock .aos file and not the SDE firmware .aos file
have you tried redownloading the archos firmware again? maybe the download got corrupted?
Also try running the repair tools under recovery: specifically Check Disk?
do you have a (1) at the end of the aos file? "sdqsqdfkqsdomij(1).aos" like Firefox do, i had the same error like that
Thanks...but I think I have tried it all...no luck
Try using a different browser, like IE to download it.
I've got the same thing going on. Was trying to re-partition the app space and something didn't work for the 4th time. So I removed Android and the SDE and now I can't get it to boot. My problem is that I was running windows, not sure what you were using, and I changed the recovery location's format. So every time I go to load the file the archos will format the partition then windows says it will not read and formats the partition... I move the file and try to start the reload only to fail.
I'm going to run ADB hopefully tomorrow. I hardly know what I'm doing, but don't really care if I break it! Just playing around but if anyone has any ideas let me know!
If you removed sde and android, there is nothing to boot from.
You then have to go into the recovery, format the device from there and then restore the orginal Android by transfering the aos file from arcos.
Yeah, I might have done that 10 times. That is when the archos reformats itself to something and then windows can't read the drive.
After you have transfered the AOS File to the device and it installs the Archos Android
it reformats the device to something?
I think that the archos is formatting to ext3 but windows can't read it, so windows then formats to whatever and I move the file, then hit ok on archos and you get failed message.
I know that AOS files work because I have already used them once.
If any of you guys give up on trying to get life into your bricked gen8 devices, then shoot me a message... I might be interested in buying the device from you.
Have you tried tried to fully charge it before installing? I had that same problem and it got fixed by fully charging the device first.
Full charge and plugged in as we speak.
You now have 133 posts on xda and still are not able to post a complete detailed description of what you are doing and what is happening?
How should we help?
My suggestion if you get an Error, tell us what error exactly, as my crystal ball is on repair atm.
Ha! 393 posts and your only kind of a ****? Thanks!
All kidding aside It's not easy to describe whats going on, and I wasn't trying to hijack this thread but I think the original poster is way gone. I was only trying to say I had the same problem and was going to try a few things to get it working again, but this was only yesterday and I have not had luck. I never really even asked for help but appreciate everyones input.
So... Let me start again!
Archos 101.
Long ago I had Urik Droid 1.0 installed but it had since been removed. Before I messed everything up i had the latest Archos update and rooted. I was trying to create a large partition for apps and had just edited the init.rc and rebooted. Somewhere here I messed up! Boot loops start and I'm into recovery.
Recovery shows everything normal, but I'm unable to update archos via AOS file. So I totally reformat and remove SDE in an attempt to just start fresh. This is not the case and I figured it wouldn't be.
As I described before, using windows, in archos recovery this is what is displayed.
Archos A101IT Recovery
Would you like to recover system?
NO
REBOOT
UPDATE FIRMWARE
REPAIR SYSTEM
FORMAT SYSTEM
If you select updated firmware the archos will reformat to ext3. It then says USB connection: Press OK to disconnect. Windows then says that it is unable to use the disk and asks to re-format. I did, because I don't think I can do anything else, moved the AOS file over and hit ok. Update failed (1).
So today I installed linux in an attempt to move ext3 to ext3. I did get the file transfered and my archos even said plug into dc power. I did and waited... Update Failed (206). Not sure what this one is!
And that's really all I know. I can't even get the last thing I described to come up again. But I have all week on vacation.
And lastly I would like to thank you for the help
And I just got the AOS to install! Formated repair to Vfat, used repair option and moved AOS into archos. For whatever reason this time it worked. Rebooted and android just started up. Don't know if everything works yet but we will see!
Funny, you do the mistake and call others names.
fzelle said:
You now have 133 posts on xda and still are not able to post a complete detailed description of what you are doing and what is happening?
How should we help?
My suggestion if you get an Error, tell us what error exactly, as my crystal ball is on repair atm.
Click to expand...
Click to collapse
Let me make this clear...
I was kidding. Take a deep breath, relax and please try to help someone else if that is what you are on here to do.
I'm pretty sure what you said to me was worst then my little joke. It was hardly clever and I'm ok with it as it did make me laugh a little.
I didn't ask for your help.
I didn't need your help
You didn't help.
And I'm ok with it even if you are not.
I'm going fishing now. Good day everyone.
No, it was exactly what you needed, as before my message you didn't tell us what was happening on your side.
Please read what you have posted before and check yourself if you would be able to get any sence from that.
It is funny how some people handle kritik.
How do you calibrate the touchscreen in ics?
the calibration.ini trick does not seem to work
(I can't even find the TSCalibration program anywhere ...)
albright said:
How do you calibrate the touchscreen in ics?
the calibration.ini trick does not seem to work
(I can't even find the TSCalibration program anywhere ...)
Click to expand...
Click to collapse
Do the calibration through CWM. Run the "echo ..." command here after an "adb shell".
no such directory as /sys/devices/platform/tegra_touch on ics
albright said:
no such directory as /sys/devices/platform/tegra_touch on ics
Click to expand...
Click to collapse
I know. Which is why I suggested doing it using CWM. See post #2, above, again.
I *did* read that - but I have only the faintest conception
of what an adb shell is. I don't particularly want to go to
the trouble of installing the sdk for which I have no need.
That's why I *hoped* the simpler way in the original post
might work.
albright said:
I don't particularly want to go to
the trouble of installing the sdk for which I have no need.
Click to expand...
Click to collapse
FYI: I don't think you need to install the entire SDK just to run ADB. The adb executable (and, its libraries) alone should suffice--it does on Linux.
That's why I *hoped* the simpler way in the original post
might work.
Click to expand...
Click to collapse
There is a simpler method now. Go through that post again. I've got a zip file there which you can flash using CWM.
There is a simpler method now. Go through that post again. I've got a zip file there which you can flash using CWM.
Click to expand...
Click to collapse
that's great. There's a warning about which kernels work but
I assume that the kernel in ics is OK, right?
Edit: sorry, you meant the CWM kernel so that's OK
Edit2: and it works fine - many thanks
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
coby 1125 ics touch screen calibrate
Could any of you please help. I upgraded the coby from gb to ics using the various techniques listed. I was eventually successful, however, I can't really use it because the touchscreen seems to be backwards, and mirrored. If I'm not mistaken, it seems calibrated for the 8127, where mine is 1127 10" widescreen. the "about" displays it as Model# mid8127, o.s. ver 4.0.3. I can't use any aps to correct since no file manager is present, and it is next to impossible to type through get jar. I couldn't follow the directions on this thread keenly, so please explain step by step. Though I got ics to work, somehow, I'm a rookie, and don't understand tech stuff that much. I have access to ubuntu 12.04, and windows, so I can connect the tablet, which I have done, but I don't understand how to use abd, nor cwmmanger. I tried, but got confused, though I was on windows 7. Please give me the steps in plain terms how I may use ts_calibrate, or any other method to c orrect the touch issue. If there were a way to access the start menu or file responsible and edit that. Such was the case on another tablet of mine the wm mid8650, where a similair issue occured installing uberoid. I had to edit for the 8" screen vs the primary 7"
Thanks!
xyphoid said:
Could any of you please help. I upgraded the coby from gb to ics using the various techniques listed. I was eventually successful, however, I can't really use it because the touchscreen seems to be backwards, and mirrored.
Click to expand...
Click to collapse
You should talk to the guys who created the ICS for your tablet. They're the ones who'll be able to help you.
I couldn't follow the directions on this thread keenly, so please explain step by step.
Click to expand...
Click to collapse
The steps in this thread are specific to a) the Tegra 2 Harmony-based tablets manufactured by Malata (eg. the ViewSonic gTablet) and b) to the stock or stock-derived kernels for those tablets.
rajeevvp said:
You should talk to the guys who created the ICS for your tablet. They're the ones who'll be able to help you.
The steps in this thread are specific to a) the tablets manufactured by Malata (eg. the ViewSonic gTablet) and b) to stock, or stock-derived, kernels for those tablets.
Click to expand...
Click to collapse
I see, missed that. Thanks anyway, but the version is initially from coby germany i presume, but I may have picked mine up from a thread link, and since I've visited many souces, I'm not sure. I could contact coby germany, but not sure how forthcoming they would be. Thanks anyway! I think this needs to be done on sd card some how.
Thank you, rajeevvp!!!! Flashing the zip file through CWM has definitely made touch sensitivity miles better. Working great now!!!
Ok so I'm what you guys would call a newbie with Android, I've been an iPhone user for years (switched from Verizon to AT&T to get the iPhone because at the time it was an AT&T exclusive). However I'm a really big Google enthusiasts so I have followed Android from inception. Growing tired of how bad AT&T's reception was in my house I recently switched back to Verizon and I purchased the GS4. I'm very happy that I can make calls without the use of a Micro Cell, truthfully reliable coverage was the biggest reason why I switched carriers. Else I would probably got the GS4 or HTC 1 on AT&T.
Being a newbie I made some noob mistakes, however I'm glad to report non of my mistakes bricked my phone. My phone works flawless it's only the stock recovery that is jacked up. So to start off I naively though all S4's were 100% open when rooted, by that I thought I could simply install any ROM I wanted to as long as I was rooted. However it appears that Verizon made Samsung lock the firmware with the OTA updates, from what I gather now after reading is the initial firmware was ok but the subsequent OTA downloads introduced the locked boot. Which sucks for me because I willingly took both updates which put the ME7 and now the MI1 builds on my device.
When I started to root process I had the MI1 build and I performed the De LaVega root method (thank you Tomsgt for your videos)! At the time of root and right after the root I was still not aware of the difference with builds. At that point I attempted to install TWRP via GooManager, since I had the MI1 build it did not work. GooManager kept telling me there was no file for my phone or something similar.
Now this should have been huge red flag for me but I was persistent and I looked on TWRP's website and found the file for my phone along with the manual install instructions. I'm familiar with using a Linux command line so followed the instructions to write TWRP into /dev/block/mmcblk0p21 on my device.
After reboot my device failed to get into stock recovery mode, instead it goes back into download mode but has an extra line of text that says "Could not do normal boot". Since I originally hosed my stock recovery I have read up on the different builds and I have also successfully installed the clockmod recovery option. That all works fine it's just factory recovery is still hosed up and it's annoying me!
I know that was a bit long winded but wanted to give a little background. Now I hope I'm not the only guy/girl who has jacked up the stock recovery section. I was hoping someone had some instructions to fix. Heck I think (but I'm not 100% sure) that if I can get someone who still has stock recovery to copy/export what they have in /dev/block/mmcblk0p21, then I can download that file put on my sd card and then write that back into my system using the same dd input/output command I did before.
May not be that easy but that's what I'm hoping for, or maybe some suggestions. :fingers-crossed:
Thx,
Joe
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
kennyglass123 said:
Questions and help issues go in Q&A and Help section
Thread moved
Thanks
FNM
Click to expand...
Click to collapse
Thanks kennyglass123, sorry it was posted in the wrong area!
Again I don't know if this will work but it's worth a try. For anyone who has a rooted Verizon GS4 and can get into stock recovery with no issues can I have you copy and export what's in /dev/block/mmcblk0p21 to an external file? For those who may not be familiar with Linux I have a few commands you can run below.
1.) Using terminal emulate create a folder to store the file on external card, in my example below I named it "StockRecovery" but you can name it whatever you want.
2.) su
3.) mkdir -p /storage/extSdCard/StockRecovery
4.) dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/StockRecovery/mmcblk0p21
This should create a file named mmcblk0p21 under the StockRecovery folder of your external SD card. If you could then either attach that file here or maybe upload the file to a public dropbox, or even e-mail that file to me I would really appreciate it!
Not sure this will fix my problem but it's worth a shot!
Thx,
Joe
garzjoe said:
Thanks kennyglass123, sorry it was posted in the wrong area!
Again I don't know if this will work but it's worth a try. For anyone who has a rooted Verizon GS4 and can get into stock recovery with no issues can I have you copy and export what's in /dev/block/mmcblk0p21 to an external file? For those who may not be familiar with Linux I have a few commands you can run below.
1.) Using terminal emulate create a folder to store the file on external card, in my example below I named it "StockRecovery" but you can name it whatever you want.
2.) su
3.) mkdir -p /storage/extSdCard/StockRecovery
4.) dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/StockRecovery/mmcblk0p21
This should create a file named mmcblk0p21 under the StockRecovery folder of your external SD card. If you could then either attach that file here or maybe upload the file to a public dropbox, or even e-mail that file to me I would really appreciate it!
Not sure this will fix my problem but it's worth a shot!
Thx,
Joe
Click to expand...
Click to collapse
Bump....
Still hoping there is someone out there who can help me out.
garzjoe said:
Bump....
Still hoping there is someone out there who can help me out.
Click to expand...
Click to collapse
If your phone is bricked I would recommend the Verizon Repair Assistant.
THIS IS A LAST RESORT.
This will fully update your phone but it will fix any errors.
southpaw5271 said:
If your phone is bricked I would recommend the Verizon Repair Assistant.
THIS IS A LAST RESORT.
This will fully update your phone but it will fix any errors.
Click to expand...
Click to collapse
Hmm I can investigate that but my phone is not bricked. I'm using it now to reply to you. Stock recovery is hosed...so when I power off and then hold Vol+, Power, Home key and then let go of power and keep holding the other two buttons. That key sequence gets my phone into recovery mode. However I can't get into that with my phone anymore.
Thx,
Joe
Hi I've been reading through the forum here for about 2 years now and got a lot of helpful advice on rooting and flashing my Android devices but this is my first thread. Unfortunately I've messed up my USA Galaxy Player 5.0 and don't know what to do that I haven't already tried. Let me start at the beginning.
I rooted my player a while ago and everything was fine untill my micro-SD card wouldn't mount in other devices but sometimes it would in my player. So, I installed AParted on my Player and proceeded to format what I thought was the SD card. I found out when I rebooted my player hours later that it had wiped my Player rather than that SD card and my Player wouldn't boot but gave a bunch of errors.
I had flashed Samsung devices with odin 1.85 before and decided to try some of the rooted ROMs from this site. They all appeared to flash just fine in odin, however when the Player rebooted it stopped at the CWM recovery screen saying it could not mount the /cache. I went into mounts and storage and tried to format /cache and got this:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p15.
I also tried installing CWM recovery zip files and they installed way too fast and then didn't work. It seems like my Player cannot write all of the needed files. Any suggestions? I dual boot WinXP and Ubuntu. In Ubuntu I installed Heimdall 1.4 and the frontend but am not real sure how to use it. I did get Heimdall started ok with sudo heimdall-frontend.
Marty
What rom did you flash? Also heimdall frontend 1.4 is just weird lol. I use 1.1 instead.
Sent from my YP-G1 using xda app-developers app
obscuresword said:
What rom did you flash? Also heimdall frontend 1.4 is just weird lol. I use 1.1 instead.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
Well I tried a lot of ROMs that I'll list. The one I have a backup from a year ago (that's from my first Galaxy Player 5 that I hard bricked before I bought this 2nd one) uses Eryigit 3.5 USA ROM and also has CWM on it. That's what is on it now, though it only boots to CWM. These are the ROMs I tried that wouldn't boot:
Odin:
Eryigit 3.5 USA
Stock ROM with PIT UEKI8_MIN
CWM:
CM7.2.0-RC1
CM9-HWA-12.5.2012
Noisy Fox GB ROM ZKP9
Supermaster CM9
Chip 1.5-1
I honestly don't think it's a ROM problem since these have all worked for me on my previous Galaxy Player 5 USA model. I think AParted messed up the partitions when it formatted the device.
How do I fix the partitions? I thought that's what a PIT file did, but it seems to just get stuck on the PIT file in odin...how long should it take?
Marty
LinuxHippy said:
Well I tried a lot of ROMs that I'll list. The one I have a backup from a year ago (that's from my first Galaxy Player 5 that I hard bricked before I bought this 2nd one) uses Eryigit 3.5 USA ROM and also has CWM on it. That's what is on it now, though it only boots to CWM. These are the ROMs I tried that wouldn't boot:
Odin:
Eryigit 3.5 USA
Stock ROM with PIT UEKI8_MIN
CWM:
CM7.2.0-RC1
CM9-HWA-12.5.2012
Noisy Fox GB ROM ZKP9
Supermaster CM9
Chip 1.5-1
I honestly don't think it's a ROM problem since these have all worked for me on my previous Galaxy Player 5 USA model. I think AParted messed up the partitions when it formatted the device.
How do I fix the partitions? I thought that's what a PIT file did, but it seems to just get stuck on the PIT file in odin...how long should it take?
Marty
Click to expand...
Click to collapse
You need to check your partition table. flash Entrophy512's daily driver then in adb: fdisk -l /dev/block/mmcblk0
Compare output to image in this post http://forum.xda-developers.com/showpost.php?p=44626450&postcount=33
If it doesn't match exactly then read this entire thread: http://forum.xda-developers.com/showthread.php?t=2398120
EDIT: FYI - When you put a pit file in Odin, all it does is flash the PIT file to the PIT partition. If your partition table is jacked and the PIT Partition is missing...???
If you check "repartition" in Odin, then Odin reads the pit from the pit partition then reformats according to what the PIT says, but if your PIT Partition is missing...???
The galaxy player 5's PIT Partition is /dev/block/mmcblk0p6
Meticulus said:
You need to check your partition table. flash Entrophy512's daily driver then in adb: fdisk -l /dev/block/mmcblk0
Compare output to image in this post http://forum.xda-developers.com/showpost.php?p=44626450&postcount=33
If it doesn't match exactly then read this entire thread: http://forum.xda-developers.com/showthread.php?t=2398120
EDIT: FYI - When you put a pit file in Odin, all it does is flash the PIT file to the PIT partition. If your partition table is jacked and the PIT Partition is missing...???
If you check "repartition" in Odin, then Odin reads the pit from the pit partition then reformats according to what the PIT says, but if your PIT Partition is missing...???
The galaxy player 5's PIT Partition is /dev/block/mmcblk0p6
Click to expand...
Click to collapse
Good-then there is still hope...I thought I messed up a 2nd Galaxy Player. It boots to CWM now...can I flash Entropy´s kernel there or do I need to do that in odin?
Marty
LinuxHippy said:
Good-then there is still hope...I thought I messed up a 2nd Galaxy Player. It boots to CWM now...can I flash Entropy´s kernel there or do I need to do that in odin?
Marty
Click to expand...
Click to collapse
It doesn't matter how it gets flashed as long as it does...
Meticulus said:
It doesn't matter how it gets flashed as long as it does...
Click to expand...
Click to collapse
Well, I read over the threads u posted, got ADB working in Win XP, and then flashed my kernel so that it's using entropy512's kernel. All looked ok till is issued the fdisk command on the SGP and it couldn't find mmcblk0. What else would it call the root device? I issued a couple commands in the attached screenshot and it looks like I only have 376 MB rather than ~ 8 GB.
The screenshot file is attached to this post.
Marty
LinuxHippy said:
Well, I read over the threads u posted, got ADB working in Win XP, and then flashed my kernel so that it's using entropy512's kernel. All looked ok till is issued the fdisk command on the SGP and it couldn't find mmcblk0. What else would it call the root device? I issued a couple commands in the attached screenshot and it looks like I only have 376 MB rather than ~ 8 GB.
The screenshot file is attached to this post.
Marty
Click to expand...
Click to collapse
Its /dev/block/mmcblk0
Sent from my M470BSA using Tapatalk
That worked but the output didn't match yours at all. Besides there being no partitions (I was trying to format my SD card with a FAT32 filesystem) the device has 4 heads (yours had 1) and the units are cyclinder of 64 (you have 16). I attached another screenshot...I do still have 7944 MB, though!
So, with these differences should I proceed with repartitioning with fdisk??
Marty
I'm not root
LinuxHippy said:
That worked but the output didn't match yours at all. Besides there being no partitions (I was trying to format my SD card with a FAT32 filesystem) the device has 4 heads (yours had 1) and the units are cyclinder of 64 (you have 16). I attached another screenshot...I do still have 7944 MB, though!
So, with these differences should I proceed with repartitioning with fdisk??
Marty
Click to expand...
Click to collapse
I realized just now that I'm not root and when I try to change into root with su it cannot find that command because it doesn't have a /bin directory (in Ubuntu it's /bin/su). It may only display partitions to the root user and wouldn't let me create any without being root. Maybe it's running out of space and cannot create that directory? Could u put a link on here of the page for Entropy512's daily kernels? You had mentioned it, but the 1 I found is from 2012 and I'm not sure if it's daily.
Marty
I wrote my new partition table!
Well, I installed Entropy512's kernel from 01222012 and that gave me root. Then from ADB shell I was able to gain all the functions of fdisk. I still did not have any partitions. However, I could not follow your guide exactly because my Galaxy Player has 4 heads...this meant that each block was 32 bytes. So I had to use trial and error to try to get the Start and End blocks close to the number of blocks in each of your partitions. In fdisk I had to display the table after every new partition with P and if it wasn't the right number of blocks I would delete it with D and then try again keeping in mind that each block increased or decreased the size of the partition by 32 bytes.
I may be explaining this wrong and went about this the wrong way. I wrote the table and attached another screenshot. Before I wrote any ROMs to it, I wanted to make sure it looked good enough for ROMs to write to it.
Marty
Unpartitioned space
There is unpartitioned space at the end of this "drive".
Meticulus has 969728-969528=200
I have 242432-242373=59
This space is almost equal if u consider each head to use 50 and there are 4 heads...200. Each block takes 32 of these (bytes?).
I hope u can follow my reasoning since I don't know the units. If this space is unused, I'm wondering if 1 of these partitions could be increased by 32 bytes? If this space isn't used by a ROM, I could re-do this pretty easily to prevent my SGP from locking up again.
It looks like Samsung put out at least 2 USA geometries of their SGP5. Perhaps somebody else could post ADB outputs of fdisk -l /dev/blk/mmcblk0?
LinuxHippy said:
There is unpartitioned space at the end of this "drive".
Meticulus has 969728-969528=200
I have 242432-242373=59
This space is almost equal if u consider each head to use 50 and there are 4 heads...200. Each block takes 32 of these (bytes?).
I hope u can follow my reasoning since I don't know the units. If this space is unused, I'm wondering if 1 of these partitions could be increased by 32 bytes? If this space isn't used by a ROM, I could re-do this pretty easily to prevent my SGP from locking up again.
It looks like Samsung put out at least 2 USA geometries of their SGP5. Perhaps somebody else could post ADB outputs of fdisk -l /dev/blk/mmcblk0?
Click to expand...
Click to collapse
Please read the ENTIRE thread. Changing the heads is explained and you must change the head first. There is only one U.S.A "geometry".
Meticulus said:
Please read the ENTIRE thread. Changing the heads is explained and you must change the head first. There is only one U.S.A "geometry".
Click to expand...
Click to collapse
Oh, I missed something. I'll read the posted threads again (there are threads inside of threads here) later. It's good to know that Samsung only put out 1 version of their USA SGP5...I was gonna comb the web later for partition table screenshots and that woulda been a complete waste of time.
Can u post the EXACT posting that I should re-read?
Marty
LinuxHippy said:
Oh, I missed something. I'll read the posted threads again (there are threads inside of threads here) later. It's good to know that Samsung only put out 1 version of their USA SGP5...I was gonna comb the web later for partition table screenshots and that woulda been a complete waste of time.
Can u post the EXACT posting that I should re-read?
Marty
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=45458589&postcount=55
Have a better partition table!!
Meticulus said:
http://forum.xda-developers.com/showpost.php?p=45458589&postcount=55
Click to expand...
Click to collapse
OK, thanks for the last link...that was helpful! I hadn't read that & didn't know after 12 years of Linux use that there was an expert mode for fdisk...now I can fix my computer disk that I re-partitioned years ago and has 4 heads (that's working, though and like I've always been told, "if it aint broke, don't fix it!" I now re-did the partition table with 1 head and it ALMOST looks like your table. I attached a screenshot of your table and mine side by side so u can easily compare. What's on your table and missing from mine are 2 lines:
Omitting empty partition (18)
Partition 1 does not end on cylinder boundary
Are these important or am I ready to flash this puppy with the Low Level Russian ROM u suggested?
Marty
LinuxHippy said:
OK, thanks for the last link...that was helpful! I hadn't read that & didn't know after 12 years of Linux use that the was an expert mode for fdisk...now I can fix my computer disk that I re-partitioned years ago and has 4 heads (that's working, though and like I've always been told, "if it aint broke, don't fix it!" I now re-did the partition table with 1 head and it ALMOST looks like your table. I attached a screenshot of your table and mine side by side so u can easily compare. What's on your table and missing from mine are 2 lines:
Omitting empty partition (18)
Partition 1 does not end on cylinder boundary
Are these important or am I ready to flash this puppy with the Low Level Russian ROM u suggested?
Marty
Click to expand...
Click to collapse
Technically: fdisk in Entropy512's Daily Driver is the busybox version, which does not have "expert" mode but newer version of fdisk (not in busybox) do have an "expert" mode that you can select with the option "x" at the prompt. However the busybox fdisk does have the ability to change the heads which is in the "expert" mode in newer (non-busybox) versions of fdisk. But that isn't really relevant at this point. Just an FYI.
I don't know how relevant those 2 lines are...
All I can say is give it a go...:good:
All fixed
Well, I didn't have to flash another ROM after I had redone the partitions. Once I had shut down the SGP5 after doing the partitions, I left it on for a half hour or so and then shut it down. When I restarted the SGP5 it booted just fine into the last ROM I flashed. I think it's running Eryigit 3.5 but it may be another one. I'm gonna restore a backup in CWM that I made a year ago and that should be running Eryigit 3.5.
How can I find out which ROM it is running and any idea why there were 4 heads on the device? I bought it as a refurbished SGP5 so somebody else may have done it months ago or maybe the AParted app I was using to format an SD card did that.
Thanks for your help
Marty
LinuxHippy said:
Well, I didn't have to flash another ROM after I had redone the partitions. Once I had shut down the SGP5 after doing the partitions, I left it on for a half hour or so and then shut it down. When I restarted the SGP5 it booted just fine into the last ROM I flashed. I think it's running Eryigit 3.5 but it may be another one. I'm gonna restore a backup in CWM that I made a year ago and that should be running Eryigit 3.5.
How can I find out which ROM it is running and any idea why there were 4 heads on the device? I bought it as a refurbished SGP5 so somebody else may have done it months ago or maybe the AParted app I was using to format an SD card did that.
Thanks for your help
Marty
Click to expand...
Click to collapse
To find out what ROM your running, the best evidence is going to be in the "About Phone" area, or the build.prop. I think ( not really sure ) that there was a time that the "heads" property did represent the physical number of heads that the storage device had but with more modern forms of storage, it's just a number that part of an algorithm for organizing the space into units. I might be wrong there. It's just the impression that I get. Most likely it was a result of the way AParted partitions disks....
On a personal note, if you look @ the build.prop for Eryigit's rom, you'll probably see my name. "Meticulus". It's sort of an easter egg...:laugh:
Actually the backup I had wasn't working with google play so I wound up flashing with the LLF Russian ROM & then flashing a rooted stock gingerbread ROM and wiping data and caches. Then it was new and I had to login to google play. Now everything works.
Marty
Sent from my YP-G70 using xda app-developers app
Hi all,
to make it plain and short: I messed up.
I have a GT-S5830i which I unrooted according to the Sticky Note in the forum, installed CWM Recovery and then 'installed from ZIP' a CM9_cooperve_Beta_05.zip that I found in one of the posts in the forum. The installation went on without error message but since then the phone does not make it beyond the initial screen "Samsung Galaxy Ace GT-S5830i". I can start recovery mode and Download mode. In reovery mode I can format cache, data, sdcard, sd-ext but *not* system. Error Message: "E: format_volume: make_ext4fs failed on /dev/block/st19"
I have tried already several methods according to the forum, e.g.
1) 'install from ZIP' older Cyanogenmod
2) the tool ext4_formatter.zip
3) re-flash with ODIN with several tar-ROMs, all failed. Odin finds the phone (since I start Odin as Admin now), but after I hit 'start' it tries to establish a connection to the phone and ends after a while with 'Failed'
I'm basically lost now, don't know what else to do. Any advise is appreciated (it's my mom's phone, she is getting impatient )
Thx, cheers!
Xala
Hi @xalarsk , So you can't format your /system partition , which is required for installation of your rom ,, you need to try this method from here mate . Follow my instruction from the line @post#4 :"1. Download one of the newest ,,," to the end of the post and please do not use CM9 beta , because it is unstable and will wreak havoc with your system eventually . ( either cm7 or cm11 is the place you should go for CyanogenMod experience for cooperVe device ).
If you fail at any level please give us your logcat ( error massage ) for better support for your Odin process you mentioned .
Cygwin not working
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
xalarsk said:
Hi @ehsanotaku,
thank you for your quick reply, it's appreciated!
Unfortunately I couldn't get cygwin to install all necessary packets. The ZIP-test always failed. I have a Linux system running (Linux Mint 17) though, and hope that might help. In the meantime I tried to download the already split packages as described in another of your forum posts, but the website provides only exe-files instead of zip-files. Is there another location to download them?
#UPDATE: It seems there is a SplitFUS2 version for linux somewhere but couldn't find links to download. Anybody can help? I'll also PM Doky73
Cheers, Holger
Click to expand...
Click to collapse
Cygwin was meant for windows platform to get the native Linux environment/command line you already got there . You can create a virtual instance of the windows 7 inside virtualbox or any kind of apps you are preferring such as Vmware/Parallel etc etc to get the job done .
Splitfus2 only supports windows platform as far as i know mate,,, either vitalization as i said or the pre-made zip package ( which is clearly not .exe file ,, push the download now and get yourself a descent downland manager,, tested and zip packaged delivered ) from here is the feasible approach for your problem .
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
xalarsk said:
Ok, had all the files ready, just the Boot loader <DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.rar seems to be broken. I downloaded the link provided in your post #8 several times with several download managers, also uses 7-zip and several online unrar services..result always the same: The archive is broken. Is that possible? Would you mind to check yourself?
Click to expand...
Click to collapse
Another fellow had similar issue with my attachment that was corrected here @ post#27
Unbricked, SD card not recognized
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
xalarsk said:
Update: Phone has been unbricked, many thanks for that!
Currently I have still issues with the external SD card, which also holds the ZIP files. Phone won't recognize it, not even format it properly. Still working on that.
Cheers, Xala
Click to expand...
Click to collapse
Mostly this happened because of the bug inside CM9 beta you used . Study this topic mate i troubleshooted while ago for a sample of the symptoms external SD card would show after unstable ICS usage .
Also as an alternative to the method i instructed there , you can format/Re-partition your SD card by putting it inside card reader and using app such as free MiniTool Partition Wizard "Gparted" tool for Linux users Or "iPartiton" for Mac users etc etc ,, to get the job done . You can find several tutorials inside XDA for this matter mate.
Phone works with CM7.2, can I upgrade to CM9?
Hi again,
first of all, props to @ehsanotaku, I will hit the 'Thanks' buttons.
Now, this is a bit beyond the topic, but I'd like to ask anyway for recommendations of CM9 roms. The one I picked from a post inside this forum bricked my phone and made me start this thread, I don't want to go down this road again. So I'd be glad for any recommendation of a stable ROM that will put my phone beyond Android 4.0.
Cheers again,
Xala
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
hojnikb said:
So i have a similar issue. I used to have CM11 installed, but i figured thats too slow for me. Then i went back to stock rom (XXMJ2) which works fine. But now i have a problem.
Everytime i want to flash a stock based or cm7 based rom on my phone, it gets messed up. Today i wanted to flash this
http://forum.xda-developers.com/galaxy-ace/s5830i-develop/cm-7-2-kitkat-smart-r2-t3075267
i naturally downloaded clockwork mod recovery (5.0.2.6) and tried to flash it. Flashing was done pretty quickly (10 seconds or so) and when i rebooted, i obviously got stuck at sammy logo. Now booting back to the recovery (first e3 then cwm) i got bunch of error about partritions not being able to be mounted (happens the same if i want to manually mout them or format them)...
So, what to do ?
I have a suspicion, that flashing CM11 and the latest cwm recovery for it somehow messed up partritions.
Click to expand...
Click to collapse
ok not going to excruciating details of symptoms and explaining all of your errors for now just please read my advice @ post2 of this topic and follow the procedures accordingly and finished it with formatter tools and cm7 instructions you will find there ., after that you can install Kitkat Smart R2 like you are coming from another CM7 build instruction . btw some problem regarding super user privileges and play store 492-498 infamous bug was reported for this fairly new development .