I have 2 pre launch models I9505 with extremely old software (and a non-secure bootloader ! )
Could someone point me in the right direction on HOW to extract the partition layout and all firmware related files ?
both devices are on different software
1st device hasn't even got TouchWiz yet, it was delivered on Google software and looks like this:
2nd device has this in download mode:
Can someone help me ?
Obviously this is an effort to get a modded bootloader which will allow us to install the FULL I9505G firmware on our I9505 devices !!
karoolus said:
I have 2 pre launch models I9505 with extremely old software (and a non-secure bootloader ! )
Could someone point me in the right direction on HOW to extract the partition layout and all firmware related files ?
both devices are on different software
1st device hasn't even got TouchWiz yet, it was delivered on Google software and looks like this:
2nd device has this in download mode:
Can someone help me ?
Obviously this is an effort to get a modded bootloader which will allow us to install the FULL I9505G firmware on our I9505 devices !!
Click to expand...
Click to collapse
You must dd all of the things in /dev/block/ I.E.
dd if=/dev/block/mmcblk0p1 of=/sdcard/mmcblk0p1.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/mmcblk0p2.img
Etc...
Sent from my GT-I9505G
System status = Custom
I don't think you will receive OTA with this + are the specs even the same ??? the model is totally different.
Just try..
Sent from my HTC One using Tapatalk 4 Beta
MichelN said:
System status = Custom
I don't think you will receive OTA with this + are the specs even the same ??? the model is totally different.
Click to expand...
Click to collapse
I don't think he's worked about OTA, lol. His model reads GT-i9505. How is that different?
Sent from my GT-I9505G
Fenny said:
I don't think he's worked about OTA, lol. His model reads GT-i9505. How is that different?
Sent from my GT-I9505G
Click to expand...
Click to collapse
Look at the phone model, sammy might have used other chips for the pre-release.
MichelN said:
Look at the phone model, sammy might have used other chips for the pre-release.
Click to expand...
Click to collapse
You mean physically? Yeah engineering devices will often look different than the official release. But usually they have most of the same guts. In this case I am concerned that they would have used an unsigned bootloader and a blown (or not blown as the case may be) efuse. But if that bootloader is signed and insecure... Ooooh baby we could have some fun with that.
I'll try that as soon as i can, but the devices are at work.. so i guess it'll have to wait.. and the hardware is the same, those devices are used to test firmwares and applications
They look different because the design was still confidential
I know both devices will allow flashing the GED software, but i bricked 2 already it's a tricky flash procedure :/
Sent from my SM-T311 using xda app-developers app
karoolus said:
I'll try that as soon as i can, but the devices are at work.. so i guess it'll have to wait.. and the hardware is the same, those devices are used to test firmwares and applications
They look different because the design was still confidential
I know both devices will allow flashing the GED software, but i bricked 2 already it's a tricky flash procedure :/
Sent from my SM-T311 using xda app-developers app
Click to expand...
Click to collapse
Make backups of those partitions for us before you try any of this.
Next, Load the Google edition ROM.
So here would be my method for changing partition layout: boot to a custom recovery adb shell in. Copy the contents of /sbin/ to /system/sbin/. Make a backup using nandroid. Unmount /system/, use parted to resize system to the size in your pit. (You may have to mkfs ext2 before it will do this, if so, just mkfs ext4 after). Advanced restore your system backup to your now smaller partition. Now, dd all of the things after your system partition except the data partition to your sdcard or to your internal storage (risky, back these up to your computer just in case). Proceed to delete, readd, and dd restore all of the partitions until you get to the recovery partition, this is where it is tricky. Delete the partition before the recovery partition (noting the next available block.) Recreate the previous partition in the bounds of the recovery partition. DD the recovery image into that space. Recreate the previous partition again, where it should be. One of two things will happen here. Your pit will immediately take effect, overwriting the partition table, and you will have to boot to recovery, and DD restore your images and nandroid, or you it won't, and you will continue on. Now we need to be in normal mode again, so make sure your ROM is rooted. From the normal rom, delete the recovery partition, and move it to where it should be. Boot back to recovery now. Proceed to move the rest of the partitions, and restore your nandroid to restore the cache, etc.
Sent from my GT-I9505G
Could you please post dumps of the bootloader on the forum it could really help at the verizon s4 scene
Thanks!
You can get the pit by Heimdall. I suggest pulling this too because partitions for engineering devices could be different than release.
Sent from my SPH-L900 using Tapatalk 2
Could you post or pm me the links to the .pit and partitions
This will be amazing.. Hopefully we can get are much needed storage
Sent from my SGH-M919 using xda premium
rajat12345 said:
Could you post or pm me the links to the .pit and partitions
Click to expand...
Click to collapse
This THREAD have system dump wit pit included, also you can contact op of that thread as he stated that he is willing to provide any info.
cheers mate
That isn't the same file Is it?
Sent from my SGH-M919 using xda premium
Sent from my GT-I9505 using XDA Premium HD app
I have a i9505G and the bootloaders is still secure
the pic you sent look to be downloader mode
Send a pic of the screen when you do "adb reboot bootloader"
or hold both volup+voldwn during power up
when need to get that secure boot to disable
look at my Signature for how to dump your rom, that should help
since the partition layout may be different i would like to make sure.
btw are you sure you didn't just get a clone, there has been a few copies out know that look like the real thing.
warwolfx0 said:
I have a i9505G and the bootloaders is still secure
the pic you sent look to be downloader mode
Send a pic of the screen when you do "adb reboot bootloader"
or hold both volup+voldwn during power up
when need to get that secure boot to disable
look at my Signature for how to dump your rom, that should help
since the partition layout may be different i would like to make sure.
btw are you sure you didn't just get a clone, there has been a few copies out know that look like the real thing.
Click to expand...
Click to collapse
I'm sure that the partition layout between i9505 and i9505G are different, the pit files don't match!
I'll look into dumping the rom, although i have my hopes on some tool i found this weekend
and a clone ? dude, are you serious ? i've had these devices since somewhere in february..
karoolus said:
I'm sure that the partition layout between i9505 and i9505G are different, the pit files don't match!
I'll look into dumping the rom, although i have my hopes on some tool i found this weekend
and a clone ? dude, are you serious ? i've had these devices since somewhere in february..
Click to expand...
Click to collapse
Well i hope you can extract everything
karoolus said:
I'm sure that the partition layout between i9505 and i9505G are different, the pit files don't match!
I'll look into dumping the rom, although i have my hopes on some tool i found this weekend
and a clone ? dude, are you serious ? i've had these devices since somewhere in february..
Click to expand...
Click to collapse
Yes, get us some dd images by all means.
Sent from my GT-I9505G
Related
Hi,
I just realised that I'm going to post this, hopefully to get some help getting the frame buffer issue working. I'm not giving up on it, but it just doesnt seem fair to sit on this any longer since it works, besides the GUI glitches.
As i said before, the S7 kernel does not support framebuffering, which makes the GUI in the recovery a bitt messy. When you move up / down in the menu, it switches between selecting an item on top and an item on the bottom (you'll see 4 menus in total, but the ones on each horizontal line is a mirror).
This means that it starts by using the lower one, and it uses the top one next, then it goes back to the lower one. Boot it up and you'll probably see what I mean. This shouldnt cause any problems with the recoverys operation anyhow.
If you want to enter adb in linux you will have to get a copy of usb_modeswitch and run the following line in order to get adb to recognize the device:
sudo usb_modeswitch -W -v 12d1 -p 1031 -V 12d1 -P 1035 -M "5553424370ab71890600000080010a1106000000000000000 0000000000000" -s 20
This will switch the huawei s7 usb device into adb mode.
Also i take no responsibilites of bricks or other problems caused by using this recovery. Its truly for learning usage only.
My credit list would be to long if I where to include all forums that I've visited to get more information about this device, but if you feel like you deserve credit, let me know and i'll add you, otherwise, thanks to all people posting information about android devices, i could never have done it without you.
Ofcourse i have to thank the creators of clockwork mod, and also the people who wrote the repack-image.pl and unpack-image.pl scripts
Thanks to my wife who put up with me sitting and messing around with this for almost a week, giving her not the attention that she deserved, and thanks to all users of the S7 tablet out there.
h***://rapidshare.com/files/438781673/recovery.img.zip (not allowed to post links yet)
The shortcut key for entering recovery is menu + send, if anyone wonders.
Hope you'll enjoy it as much as I did.
Works great. Ill research a bit to see if i can help
Sent from my Ideos S7 using XDA App
Sorry for qwestion, but... How can i put it into device? Via fastboot on cmd, or somehow other?
Sent from my Ideos S7 using XDA App
I hope we can get a 2.2 rom
sorry, but it working not fully...
its have errors to open nandroid-mobile.sh
and its cant format SDcart to partitions ext2 and ext3...
or maybe i doing something wrong
GvoZdik said:
sorry, but it working not fully...
its have errors to open nandroid-mobile.sh
and its cant format SDcart to partitions ext2 and ext3...
or maybe i doing something wrong
Click to expand...
Click to collapse
You're right, I noticed now that I the wrong ramdisk in the image that was released. I have several of them for which I use to debug the framebuffer stuff, and I forgot to use my own build.
I'll upload the correct one sometime this weekend.
Sorry.
Sent from my HTC Desire using Android Tablet Forum App
thanx, thats a great work anyway...
Sent from my S7 using XDA App
thanks perivarlura for your support!
perivarlura said:
You're right, I noticed now that I the wrong ramdisk in the image that was released. I have several of them for which I use to debug the framebuffer stuff, and I forgot to use my own build.
I'll upload the correct one sometime this weekend.
Sorry.
Sent from my HTC Desire using Android Tablet Forum App
Click to expand...
Click to collapse
The ui glitches even more now that the misc partition handled and the nandroid script is running. I guess i need to get this fixed before i release it, or it will just be a mess.
I am at a loss, i am at a point where my phone is no longer bound by the laws of logic.
I was running Passion 13.1 ICS
two days ago for some reason i woke up and my phone was asking for a password to decrypt the phone, i though this was weird being that i didnt encrypt the phone.
so i setup ODIN and flashed back to Eugene's Froyo that doesn't brick pre rooted w/re-partition checked.
it passes and reboots after reboot i get
Code:
"E:Cant mount /dev/block/mmcblkop1 (or /dev/block/mmcblk0)
(no such file or directory)
but it will reboot into android
so i booted into android setup adb and copied over the fs tools (Parted, e2fsck, mke2fs, resize2fs tune2fs, and sdparted)
i found that in /dev/block/ the partition files were missing completely so i created them using
Code:
mknod /dev/block/mmcblk0 b 179 0
mknod /dev/block/mmcblk0p1 b 179 1
mknod /dev/block/mmcblk0p2 b 179 2
i can see them there but when i try to partition them using
Code:
parted /dev/block/mmcblk0 mkfs ext2
it returns
Code:
Error: Error opening /dev/block/mmcblk0: No such device or address
so i tried a shot in the dark i tried to write zero's to it
Code:
dd if=/dev/zero of=/dev/block/mmcblk0
it returns
Code:
/dev/block/mmcblk0: cannot open for write: No such device or address
so i rebooted my phone, when it came back up i opened an adb shell and to my surprise the fs tools and the files i created in /dev/block were gone it was like it factory reset it self on reboot.
were i am at now is hardware failure unless the collective minds here can see something that i missed?
i really really REALLY want to save her she has been an awesome phone.
any help would be appreciated
Dude that sucks. You are I think the 3rd or 4th person to have this happen to. I do also believe that most of whom this happened to (at least in our forum) were running Passion (different variants though). In the Cappy threads, it was CM9 or Doc's. Seems it is totally random when it happens, but I am seriously considering going back to something else unless I get another phone.
Might want to check here for a workable solution.
Sorry for your loss.
Instead of the froyo build, you should try 2.1 jfd odin package
Woodrube said:
Dude that sucks. You are I think the 3rd or 4th person to have this happen to. I do also believe that most of whom this happened to (at least in our forum) were running Passion (different variants though). In the Cappy threads, it was CM9 or Doc's. Seems it is totally random when it happens, but I am seriously considering going back to something else unless I get another phone.
Might want to check here for a workable solution.
Sorry for your loss.
Click to expand...
Click to collapse
I was thinking about doing this, but wouldn't it make my phone incredibly slow because of the sd latency?
Dougfresh said:
Instead of the froyo build, you should try 2.1 jfd odin package
Click to expand...
Click to collapse
i tried looking for this but i cant find it do you have a link or a copy of the files?
I'm sure it will slow down but it should boot up and you can load another ROM on there. You do lose your entire internal since it is essentially swapped out for the external. Can't hurt to try with a higher class card maybe.
It seems this is happening to everyone running ICS Passion.
Ya but on the Cappy threads it is happening to people on CM9 and Doc's too.
So I am wondering if anyone on AOKP builds are getting these. I posted in the other two threads about this (the one that you were helping that guy yesterday with and the other one) to see what ROMs/kernels they were running, JIC.
Might be a problem with the port of the AOSP code since it is essentially from NS and GNex, both Sammy products though. Anyone in your NS fora reporting this problem?
Nope, nobody. And I just flashed from 2.3.6 to 4.0.4 2 days ago
I flashed GBBOOT-T959UVJFD in an effort to fix my problem, but its just stuck in a boot loop now. is there a chance that the actual physical memory is damaged?
Chances are your internal is completely locked up and without the encryption "key" you won't be able to use it. Since you know ADB, you still might be able to pull some stuff off it and mount to your PC.
Looks to be that you may need to repartition your external in the thread I posted above.
What Bootloader were you on before this all started?
The file I sent you had GB bootloaders included. So to get into recovery Vol- and Power. To get into download Vol+ and Power.
Woodrube said:
Chances are your internal is completely locked up and without the encryption "key" you won't be able to use it. Since you know ADB, you still might be able to pull some stuff off it and mount to your PC.
Looks to be that you may need to repartition your external in the thread I posted above.
What Bootloader were you on before this all started?
The file I sent you had GB bootloaders included. So to get into recovery Vol- and Power. To get into download Vol+ and Power.
Click to expand...
Click to collapse
at this point i don't even care about recovering the internal partition i would like to just format it and start over clean.
It had a GB boot loader on it.
This is what is confusing me, in my mind if a partition is locked and i forget the key or in this case it encrypts itself shouldn't i be able to just fdisk or dd the partition back to cleanliness and format it?
When I installed some of the ICS roms (Cant remember which ones, Too many out now) I remember at the very beginning of the post flash setup screens that I needed to Agree to Googles update rules.
I have read that The galaxy nexus and the Nexus S is getting 4.0.? upgrades re-pushed to their phones as the First update in December had a major battery drain bug in it and was stopped.
I have also read that some members reported that They got a "Welcome to your new Nexus....." e-mails.
Could this be caused by an update being pushed to the phone and sense it is a vibrant and not a nexus it is causing these problems??
Big Dog KMc said:
When I installed some of the ICS roms (Cant remember which ones, Too many out now) I remember at the very beginning of the post flash setup screens that I needed to Agree to Googles update rules.
I have read that The galaxy nexus and the Nexus S is getting 4.0.? upgrades re-pushed to their phones as the First update in December had a major battery drain bug in it and was stopped.
I have also read that some members reported that They got a "Welcome to your new Nexus....." e-mails.
Could this be caused by an update being pushed to the phone and sense it is a vibrant and not a nexus it is causing these problems??
Click to expand...
Click to collapse
I thought the Nexus had ICS already, so i don't think that was what happened. plus i would think it would prompt the user to apply the update or restart the device.
at this point after reading this thread, i think its hardware failure in my case. otherwise why would it clear everything after a reboot?
TheGioDoodlesII said:
Flash the original stock rom , wipe cache and do a factory reset before and after flashing
Hope i helped :beer:
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
I tried that sans the beer LOL i think i am going to need something stronger.
Anythoughts on the SGS 2? HERE
or the NEXUS HERE
Disclaimers :
#i am no-developer.im just a geek xperian..like many of u.i have created this ,my first ever thread typing on my mob keypad.so forgive me for short words and untidy post.
#links included below is noway related to me.respective links are included as per my findings to support the main moto of this thread.im thankfull to all of them who have tried to scratch on this through their posts and threads
#with all do respect,this thread is intended for our devs who can take this as pre-requsites for development.
#its a humble request for devs to put there effort on this.
#i request all xperians...from devs to simple users...whoever thinks this post worth discussing/developing,ur valueable words on this are highly appreciated.
#and please no trollers
Click to expand...
Click to collapse
I was doodling around today,i got my eyes poped-up wen i encounterd this
[samsung kernel flashing from cwm zip] -> http://forum.xda-developers.com/showthread.php?t=1301756 and this
[samsung general cwm kernel updater] ->http://forum.xda-developers.com/showthread.php?t=2132208
It all began then when i had to be far from my pc.then flashing new kernls for new custom roms began to be a problem.i presume their are a lot of users like me who cant access pc with as ease as many can.or simply to them who dont want to connect to pc just to flash kernels.if this would be success,just imagine how ease it would be?
But before starting to dream lets put together what i have come across till now.
Then i started digging more...on google & found this Tutorial [many devs might be intrestd &could help xperia users& start to run xperiment in our xperia ] --> http://www.modaco.com/topic/360180-howto-build-and-update-kernel-using-cwm/
In my findings i did aknowledge that this matter has/have/had been left out in corner just for some taboos/nerms like our xperia doesnt ship with normal recovery partition or like our custm recovry doesnt support some disk formats.
But whatsoever, i was little arosed by above things....then came a point whereafter i was too excited,wen i found this in our very xperia forum,xperia p forum ->> http://forum.xda-developers.com/showthread.php?t=2409021
Here the dev has created a zip with updatr script writng the kernel image,which stays inside the boot.img file .i couldnt dig more on this zip,as it was not so popular thread.i dont even know for it works or not,all i know is there are devs wanting to build,which is the main moto of this thread to let devs rethink the possibilty.
And yes, its a convincing reason for acceptance that our xperia doesnt have recovry partition like as other vendors device..and what we get as a recovry is hard coded to ramdisk.but like as ,A xperia s user,i too want to question an enlightning point on this...like using recovry fota partition,wich gets blokd and remains unusable aftr bootloader unlockd....why not use that...if not what about repartitioning empty space in device for recovry usage partition... http://forum.xda-developers.com/showthread.php?t=2163643
i too presume, even though we dont have that heavy intrnl space,but i guess we have enough for just a recovry partition.i guess so.correct me.
FOTA partition :
The FOTAKernel partition is used by Sony to do FOTA updates when updating the boot image. Unlocked devices can't take Sony FOTA updates so using this partition for storing the recovery ramdisk seems like a good idea. Unlocked users aren't able to use this partition anyway and the FOTAKernel partition is effectively the "recovery" partition on Sony devices.
Kernel changes : extract_elf_ramdisk setup in kernel
if some body wants a detailed info it can be found here (( **thanks to @officiallysonyrebel ,for the supportive conversation.above words are his ** )) -- http://forum.xda-developers.com/showpost.php?p=38640389&postcount=2
*** Summing up in total ***
It may b a horizon-touching dream..but as a geek user, like me,we dream of it.
Our charming devs can unlock bootloaders/root/giv us custm roms/give us a taste with unimaginable upgrowing ever, android version updates in roms/ ports.these all would also be impossible without their immense hardwork/researchs/xperimnts...i do aknowledge its a lot to ask for this.but with all do respect i wish devs get ther hands on it.
I predict most of xda-ians might already know abt all this,if yes do enlighten us more...ur comments and findings are most needed thing currently.
but truely saying i really dream of using cwm @ its maximum capacity,as of its easeness,isnt it? Different vendors like samsung,zte,etc evn can get rooted simply from cwm only...even most htc can. So why cant our xperia?is it coz of less devs in our xperia?i humbly request all devs to put some work on this so that me,like users who cant access pc with ease/dont want to,can easily get the work done.i also presume there r a lot of xperians,who want this.it cant be more handy than this...can it?
Hope in near future ,we xperians could getwith like these features as others.(rootng/flashng kernels from cwm).
Cheers!!
Xperia-lover!!
Most Xperia kernels are probably including CWM by default in the boot image. About a month ago Dees_Troy submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that Dees_Troy wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed.and whole a lot possibilites
but my major concern is if after unlocking bootloader FOTA partition gets blocked then how can we access it ..
so, first we have to acess FOTA partion then we can start dreaming on
officiallysonyrebel said:
Most Xperia kernels are probably including CWM by default in the boot image. About a month ago Dees_Troy submitted some changes to the CyanogenMod repos that were accepted. Newer builds of CM include a special extract_elf_ramdisk utility that Dees_Troy wrote to read and extract a recovery ramdisk from the FOTAKernel partition instead of using the ramdisk that is included in the boot image. If the ramdisk in the FOTAKernel partition is a stock Sony ramdisk or not present, then the existing ramdisk in the boot image is used instead. This setup allows users to choose which recovery they want to keep installed.and whole a lot possibilites
but my major concern is if after unlocking bootloader FOTA partition gets blocked then how can we access it ..
so, first we have to acess FOTA partion then we can start dreaming on
Click to expand...
Click to collapse
Ya i had read in the link u dirctd...i got to know that aftr unlockng bootloadr, that partition becomes unusuable/inaccessble.if that could be attained...then we can hope...isnt it?if i undrstud... wish devs could wave their magicstick soon.
Sent from my Xperia Ray using xda premium
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
mihahn said:
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
we can't do it in /system basicially we have to do this thing using only FOTA partition ..but our main concern is when we unlock our bootloaders that partition becomes inaccesible for us...
if we somehow gets access to FOTApatition then script will do work..
mihahn said:
I'm not sure but what about installing the recovery in /system?
Then we could write a script that detects if the recovery is installed in /system and it will choose the /system recovery over the kernel recovery while booting in recovery. Then we could try mounting the kernel partition and flash the boot.img. Then you flash a zip to remove the /system recovery and boot the new kernel
Not sure if that's possible, and don't have any idea how to do that. It was just an idea :good:
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Nope...You are still using the same kernel....just booting from different ramdisk when "installed in /system"...
We need to boot from a "second" kernel which can be used to flash the primary kernel ...Most other phone can boot into two kernels ,one stock and one recovery ,hence they can be used to flash kernels via recovery and use flash_image to install recovery in system ...
The problem is not where kernel/recovery is installed
The problem is how to boot the secondary kernel after installation ...It's very difficult to do that ...
lets say I dd the recovery.img to /mmcblk0p4 which is the fourth partition in an SD card
How do I instruct the bootloader to boot the device from /mmcblk0p4(or fota 1 or whatever) instead of /boot ...Thats the problem ...
Okay that's sad
But what about checking the partitions and if we know which blocks contain the Fota partition, could we try to mount it?
The problem would be how to tell the bootloader to boot the recovery or the 2nd kernel right?
Sent from my Nexus 4 running Android 4.3
Still the same problem ,how to instruct the bootloader to boot from fota 1 instead of /boot !!
Check that. It's exactly the same what we want to do, right?
Okay not exactly but we could use that too. But I'm not sure if he is able to install another kernel in the recovery...
Sent from my Nexus 4 running Android 4.3
mihahn said:
Check that. It's exactly the same what we want to do, right?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Exactly ...we can use Multi partitioned SD card but thats extremely wishful thinking ...Also we need a lot of devices to brick :rofl:
Edit: He can use recovery to install kernels since ,the S1 boot boots LK from mmcblk0p4 (equivalent to /boot) which in turn gives an option to boot to fota1(which is recovery ) or the mmcblk016(which is the new place from which the system boots)
karandpr said:
Exactly ...we can use Multi partitioned SD card but thats extremely wishful thinking ...Also we need a lot of devices to brick :rofl:
Edit: He can use recovery to install kernels since ,the S1 boot boots LK from mmcblk0p4 (equivalent to /boot) which in turn gives an option to boot to fota1(which is recovery ) or the mmcblk016(which is the new place from which the system boots)
Click to expand...
Click to collapse
But later in OP they said it could be possible to reflash the stock rom to restore the partition table. So if we don't touch fastboot and flashmode partitions we should be able to recover the phone
I wrote the OP a PM if he could help us, let's see what happens
Sent from my Nexus 4 running Android 4.3
mihahn said:
But later in OP they said it could be possible to reflash the stock rom to restore the partition table. So if we don't touch fastboot and flashmode partitions we should be able to recover the phone
I wrote the OP a PM if he could help us, let's see what happens
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Unlike them we aren't modifying partitions ...we can use multi SD card but then we need to get SD card mounted by LK ...
There is a fundamental diffrence in two phones ,that they are using an emmc+ext4 and we are using a raw nand/yaffs device . i think the difference is night and day ...I dont think we can modify partitions easily ...
If however we get to mount SD card with LK then it's a different story ...
karandpr said:
Unlike them we aren't modifying partitions ...we can use multi SD card but then we need to get SD card mounted by LK ...
There is a fundamental diffrence in two phones ,that they are using an emmc+ext4 and we are using a raw nand/yaffs device . i think the difference is night and day ...I dont think we can modify partitions easily ...
If however we get to mount SD card with LK then it's a different story ...
Click to expand...
Click to collapse
So you mean we partition the sdcard and use a partition as the recovery partition?
I read about that with multiboot for xperia play (I guess). So maybe it could work for us too?
Sent from my Nexus 4 running Android 4.3
mihahn said:
So you mean we partition the sdcard and use a partition as the recovery partition?
I read about that with multiboot for xperia play (I guess). So maybe it could work for us too?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
it's more logical(and safer) than editing nand ...AFAIK ,the partition setup of nand is included in kernel ...we can partition SD card to whatever we want and is more feasible
karandpr said:
it's more logical(and safer) than editing nand ...AFAIK ,the partition setup of nand is included in kernel ...we can partition SD card to whatever we want and is more feasible
Click to expand...
Click to collapse
Okay so how to start? What could we do to get the project to a higher level?
We have to find out how to get the bootloader to boot the 2nd kernel/recovery partition, right?
Sent from my Nexus 4 running Android 4.3
mihahn said:
Okay so how to start? What could we do to get the project to a higher level?
We have to find out how to get the bootloader to boot the 2nd kernel/recovery partition, right?
Sent from my Nexus 4 running Android 4.3
Click to expand...
Click to collapse
Not really ....we can attempt/try/wish to do what the Xperia T folks did ,flash a bootloader at /boot instead of boot image ...
First thing we really need to know how actually LK works and can it be made to boot a kernel stored in a memory card ,
Editing a nand partition is currently out of question imo ,there is no free space for two kernels...
Edit : TBH ,We should look at HTC HD2 development more than anything since that section has "Android SD development" and Nand development ..
Even saying that we might just be scratching the surface :/
karandpr said:
Not really ....we can attempt/try/wish to do what the Xperia T folks did ,flash a bootloader at /boot instead of boot image ...
First thing we really need to know how actually LK works and can it be made to boot a kernel stored in a memory card ,
Editing a nand partition is currently out of question imo ,there is no free space for two kernels...
Edit : TBH ,We should look at HTC HD2 development more than anything since that section has "Android SD development" and Nand development ..
Even saying that we might just be scratching the surface :/
Click to expand...
Click to collapse
Yes the HTC HD2 has great development support and I already worked with a HD2 of a friend, but I have actually no idea how to use the method they are using for the HD2 for our devices. I think I will dive into it when I'm back at home from my vacation trip
Sent from my Nexus 4 running Android 4.3
maybe at deeper lok of possibiltes
i was searching on sd card booting nd found this
http://glasskeys.com/2011/06/27/how...-card-running-cyanogenmod-for-the-nook-color/
we need to make a seprate partition and kernel to use triggers to boot like we always do but it will call from SD card..
i think it may not work cause calling a kernel from SD card
officiallysonyrebel said:
maybe at deeper lok of possibiltes
i was searching on sd card booting nd found this
http://glasskeys.com/2011/06/27/how...-card-running-cyanogenmod-for-the-nook-color/
we need to make a seprate partition and kernel to use triggers to boot like we always do but it will call from SD card..
i think it may not work cause calling a kernel from SD card
Click to expand...
Click to collapse
Ehh...no it won't work ...the S1boot boots only from /boot...
The thread you cited is too old and worked probably due to an exploit in nook color ...
I think something like LK should work ,provided it waits for sd card to mount...
officiallysonyrebel said:
we can't do it in /system basicially we have to do this thing using only FOTA partition ..but our main concern is when we unlock our bootloaders that partition becomes inaccesible for us...
if we somehow gets access to FOTApatition then script will do work..
Click to expand...
Click to collapse
Correct me if i m wrong.its a noobish thought.
Can we access fota partition before bootloader is unlocked?if we can so what r we waiting for?
lets rehearse for the magick show,do what u have thought of.
(I presume when device is still locked....or if we revert back to locked state from unlocked... we could acces that partition.. .we get space for secondry kernel...if still quesn is letting bootloader know we want to boot from that,then again we r far behind)
Sent from my Xperia Ray using xda premium
So I am stuck in a bootloop and no obvious way out.
US Galaxy Player 4.0
Rooted and been on custom roms for a year now. Problem started after upgraded to latest CM. Tried going back to stock but no luck in resolution. I am able to get into recovery and download mode and flash with odin. I can run adb shell. Just won't boot. The error message I get is as follows:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
In my adb shell I can see that there is no "mmcblk0..." files at all.
I have tried to go through the full stock recovery and used the PIT files and the stock rom through odin. I get the same boot loop and cant get the data to wipe due to the same error. I can flash anything through Odin easily without fail but everything is stuck in boot loop. I just don't seem to have /data to wipe.
There are some other posts around which indicate the Partition may be screwed but I am not sure what it is supposed to look like or the command line syntax to use to correct.
http://forum.xda-developers.com/showthread.php?t=1468213&highlight=wipe+data+shell
I have several nandroid backups on an external location but now I can't get the external card to recognize in CWM so haven't been able to try to revert backwards that way. I have backup of efs and all other stuff just can't seem to get to it.
Anybody with Ideas or direct help are greatly appreciated
map1122 said:
So I am stuck in a bootloop and no obvious way out.
US Galaxy Player 4.0
Rooted and been on custom roms for a year now. Problem started after upgraded to latest CM. Tried going back to stock but no luck in resolution. I am able to get into recovery and download mode and flash with odin. I can run adb shell. Just won't boot. The error message I get is as follows:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
In my adb shell I can see that there is no "mmcblk0..." files at all.
I have tried to go through the full stock recovery and used the PIT files and the stock rom through odin. I get the same boot loop and cant get the data to wipe due to the same error. I can flash anything through Odin easily without fail but everything is stuck in boot loop. I just don't seem to have /data to wipe.
There are some other posts around which indicate the Partition may be screwed but I am not sure what it is supposed to look like or the command line syntax to use to correct.
http://forum.xda-developers.com/showthread.php?t=1468213&highlight=wipe+data+shell
I have several nandroid backups on an external location but now I can't get the external card to recognize in CWM so haven't been able to try to revert backwards that way. I have backup of efs and all other stuff just can't seem to get to it.
Anybody with Ideas or direct help are greatly appreciated
Click to expand...
Click to collapse
This is how we fix that with the Player 5 : http://forum.xda-developers.com/showthread.php?t=2398120&page=4 (read the whole thread from page 4 on)
You'll need to do pretty much the same thing but you need an image from the Player 4.:good:
recrtora above
Thank you Meticulus. I see that you were involved in the thread I referenced too and this is where I figured I needed to go. However this is where I get tripped up. The main issue being that I don't have an image from a 4.0 US player. The thread I linked to had the Intl Player shown... There were even a few requests for the US version later on in the thread.
So- Anyone want to share their US player working partition table?
Is this information contained in the .PIT files somehow?
anyway to retrieve this?
map1122 said:
Thank you Meticulus. I see that you were involved in the thread I referenced too and this is where I figured I needed to go. However this is where I get tripped up. The main issue being that I don't have an image from a 4.0 US player. The thread I linked to had the Intl Player shown... There were even a few requests for the US version later on in the thread.
So- Anyone want to share their US player working partition table?
Is this information contained in the .PIT files somehow?
anyway to retrieve this?
Click to expand...
Click to collapse
As far as I know that's the only way to do it is with the picture.... Be patient, I'm sure someone will post an image...
@zaclimon ???
Needed: out put of fdisk on mmcblk0
Code:
adb root
adb shell
fdisk -l /dev/block/mmcblk0
Then post a screenshot, or just the output.:highfive:
Meticulus said:
As far as I know that's the only way to do it is with the picture.... Be patient, I'm sure someone will post an image...
@zaclimon ???
Needed: out put of fdisk on mmcblk0
Code:
adb root
adb shell
fdisk -l /dev/block/mmcblk0
Then post a screenshot, or just the output.:highfive:
Click to expand...
Click to collapse
Here it is, do note that it's a intl device though too.
zaclimon said:
Here it is, do note that it's a intl device though too.
Click to expand...
Click to collapse
That's definately not what I expected... to see from the 4.0's partition table...
Meticulus said:
That's definately not what I expected... to see from the 4.0's partition table...
Click to expand...
Click to collapse
We only have mmc blocks for the actual storage of the device. The system partition and others are pure raw nand (which is why we use mtd and yaffs2)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
zaclimon said:
We only have mmc blocks for the actual storage of the device. The system partition and others are pure raw nand (which is why we use mtd and yaffs2)
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Click to expand...
Click to collapse
So then, will recreating these partitions solve the OP problem?
Meticulus said:
So then, will recreating these partitions solve the OP problem?
Click to expand...
Click to collapse
Most probably because it will only touch /data and internal storage. Actually this is the first time I see a problem like this for the 4.0.
Envoyé depuis mon Nexus 7 avec Tapatalk 4
So any confidence in the international vs the US version being the same?
Now the next thing is I used the command fdisk to start trying to recreate the partitions using the post instructions you recommended. I did not get an option for "new". I attached the output from the shell command. Tried looking up shell command references on fdisk but is not helping me here. Is it because there is not mmcblk0 at all? I don't seem to be getting into the command mode of the fdisk command.
If I use fdisk -l /dev/block/mmcblk0 I get "no such file or directory"
map1122 said:
So any confidence in the international vs the US version being the same?
Now the next thing is I used the command fdisk to start trying to recreate the partitions using the post instructions you recommended. I did not get an option for "new". I attached the output from the shell command. Tried looking up shell command references on fdisk but is not helping me here. Is it because there is not mmcblk0 at all? I don't seem to be getting into the command mode of the fdisk command.
If I use fdisk -l /dev/block/mmcblk0 I get "no such file or directory"
Click to expand...
Click to collapse
Hmm... Can post a list of /dev/block ?
Code:
adb shell
ls /dev/block
Here you go.
map1122 said:
Here you go.
Click to expand...
Click to collapse
Hmmmmm .... see if you can get here: /sys/bus/platform/devices/s3c-sdhci.0 and post the output
Like so?
map1122 said:
Like so?
Click to expand...
Click to collapse
yes.... I'm not sure what's wrong but id recommend installing a full odin flashable rom...
Not sure what that would be for the 4.0..
Here is another place you can check /sys/bus/platform/devices/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0
Here is the output of that. No further.
I am already on fresh Odin flash. Several attempts actually. I have been able to flash back to Stock (and use PIT) files, access stock recovery. I did this first to think I could restore to OEM. Then flash the Terra-Silent kernel to obtain CWM and the IcyFusion Rom (did this again this morning so I could get adb to link). These are the only Odin flashable that I am aware of for the 4.0. Obviously nothing boots because the issues discussed here.
Thank you.
what does "partition SD Card" in the Advanced and Debugging menu in CWM do?
map1122 said:
Here is the output of that. No further.
I am already on fresh Odin flash. Several attempts actually. I have been able to flash back to Stock (and use PIT) files, access stock recovery. I did this first to think I could restore to OEM. Then flash the Terra-Silent kernel to obtain CWM and the IcyFusion Rom (did this again this morning so I could get adb to link). These are the only Odin flashable that I am aware of for the 4.0. Obviously nothing boots because the issues discussed here.
Thank you.
Click to expand...
Click to collapse
I don't know if those are "full" odin flashable roms.
Try here: http://forum.xda-developers.com/showthread.php?t=1531850
Yes, that is the one I am using to revert to stock and additional PIT. I checked MD5 sums too.
Would this kind of thing be backed up in a nandroid?
map1122 said:
Yes, that is the one I am using to revert to stock and additional PIT. I checked MD5 sums too.
Would this kind of thing be backed up in a nandroid?
Click to expand...
Click to collapse
No, It wouldn't be backed up in android...
I'm betting that the U.S. Odin ROM on that page is not a "full" recovery rom either... I'm downloading right now to check. If it isn't, we need to find out how safe it is to flash an INT version first then flash a USA over it.
On the 5.0, we can do that... and everything is OK but don't know about 4.0...
EDIT: Seem like the only difference is that INT has bootloaders and USA does not. That doesn't help us...
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