Okay before anyone starts to flame or start saying "Oh God" to the screen, this isnt the typical "When are we going to get Android to boot from HD2" question.
I know we all boot Android from our SDCard, but I went looking to see if there was any google pages on why the sd card? Being that we have an HD2 and it has alot of space (My phone says 768mb free internal storage), would it slow Android and the experience down if we had the "Android" folder copied to our phone instead? I know currently it probably wouldnt work, but being that the avg Android folder is 230mb to 260mb thats more then enough space to put the folder in, and possibly change maybe the daily useage or app installations onto the sdcard. If this was just a general rule of thumb that it was decided to be put on an sdcard across the board because not all phone had the room then is there no way to change that now since most phones are coming out to have larger internal space opposed to older ones?
And again, would it be slower to run this way or not?
AngelDeath said:
Okay before anyone starts to flame or start saying "Oh God" to the screen, this isnt the typical "When are we going to get Android to boot from HD2" question.
I know we all boot Android from our SDCard, but I went looking to see if there was any google pages on why the sd card? Being that we have an HD2 and it has alot of space (My phone says 768mb free internal storage), would it slow Android and the experience down if we had the "Android" folder copied to our phone instead? I know currently it probably wouldnt work, but being that the avg Android folder is 230mb to 260mb thats more then enough space to put the folder in, and possibly change maybe the daily useage or app installations onto the sdcard. If this was just a general rule of thumb that it was decided to be put on an sdcard across the board because not all phone had the room then is there no way to change that now since most phones are coming out to have larger internal space opposed to older ones?
And again, would it be slower to run this way or not?
Click to expand...
Click to collapse
hi
Haret cannot currently read from NAND, its code reads and searches for Data IMG and Rootfs and kernal in SD ONLY .....
hence NAND is so very different from HARET.
well Magldr is what would do the trick
I'm assuming your talking about nand as to boot from the phone like as if you are powering it up and windows loads, Im not actually talking about that. I'm actually talking about how it currently loads, except, instead of placing the Android folder on the SDCard and running clrcad and haret, instead placing the folder into the root directory of the phone and running clrcad and haret from there, same exact way we are running it now, except changing the location of the folder from card to phone.
AngelDeath said:
I'm assuming your talking about nand as to boot from the phone like as if you are powering it up and windows loads, Im not actually talking about that. I'm actually talking about how it currently loads, except, instead of placing the Android folder on the SDCard and running clrcad and haret, instead placing the folder into the root directory of the phone and running clrcad and haret from there, same exact way we are running it now, except changing the location of the folder from card to phone.
Click to expand...
Click to collapse
hi
Well firstly NAND does not necessarly mean booting from start, NAND= Internal memory, in fact cotulla's MAGLDR can boot android of the SD straight from power up whilst having WIN MO on NAND.
So to answer your question again,
HARET CANNOT READ NAND (INTERNAL MEMORY), it always looks for SD for everything , in some cases RAM, as in the new RAM builds that are popping up by devs.
the code for HARET cannot handle NAND at the moment and i dont thing it will ever be implemented.
I'm neither a dev or a hacker, this is just what i ahve understood from reading, i'm open to corrections,
best regds
I have to admit, this idea is very cool.. If haret could "see" the nand memory after WinMo is loaded, then all you need is a WinMo rom stripped down to the maximum and Android folder burned in it (at least the system part). if if if i am not sure, if its technicaly impossible for haret to see the nand memory after booting WinMo or if its impossible at all..
greg17477 said:
I have to admit, this idea is very cool.. If haret could "see" the nand memory after WinMo is loaded, then all you need is a WinMo rom stripped down to the maximum and Android folder burned in it (at least the system part). if if if i am not sure, if its technicaly impossible for haret to see the nand memory after booting WinMo or if its impossible at all..
Click to expand...
Click to collapse
guys remeber HARET is a bootloader for LINUX, its crazy enough its helping us boot android from SD, I think the possible reason HARET is not designed for reading NAND is the potential damage it could do to SPL leading to a BRICK, now we dont want a brick do we ?
mally2 said:
guys remeber HARET is a bootloader for LINUX, its crazy enough its helping us boot android from SD, I think the possible reason HARET is not designed for reading NAND is the potential damage it could do to SPL leading to a BRICK, now we dont want a brick do we ?
Click to expand...
Click to collapse
never say never and expect the unexpected, thats what life teached me
phone wouldnt get bricked if you just read nand, but writing into it could do damage, i agree on this.
OK, so when I first read the OP, I thought he meant booting Haret from the phone's internal storage memory, not NAND.
Though the NAND Haret idea is really not bad, I couldn't see it corrupting the bootloader as long as it behaves the same way as it does from the sd. I mean, the phone is already booted WinMo, so HaRet and Android have no need to touch the bootloader, just as when running from sd. It would be more or less a startup.txt change/ rel_path = NAND/Android (not exact, but general idea). Seems alot different to me from MAGLDR, maybe there is just confusion about this
But if the NAND idea is not workable, wouldn't it be possible to run HaRet Android from the phone's internal storage memory, yielding a performance speed increase and less wear on the sd?
Clearly we couldn't do like I have now, a ton of builds with exceller, all running from internal storage, obviously we don't have 16gb internal. But what about just loading our daily driver from internal, and testing/less commonly builds from sd?
I like the idea because it could mean less wear on the sd, and possibly performance increase
BTW 300th post
Thats exactly what I meant, once WinMo is loaded, we normally go into the sd card thru file explorer and then go to android and then run clrcad and haret, winMo is already loaded and doesnt corrupt winmo, but if we could run the core system from the phones storage space, (Putting the android folder into the main directory, and then running clrcad and haret, this way the core system would load and any user installable files would just end up on the storage card, cause obviously we wouldnt be able to load all our apks into the phone (Some might, others like us go nuts).
But the concept is not a bad one, especially if there was a way when installing the apk's it asked for the location to add.
AngelDeath said:
Thats exactly what I meant, once WinMo is loaded, we normally go into the sd card thru file explorer and then go to android and then run clrcad and haret, winMo is already loaded and doesnt corrupt winmo, but if we could run the core system from the phones storage space, (Putting the android folder into the main directory, and then running clrcad and haret, this way the core system would load and any user installable files would just end up on the storage card, cause obviously we wouldnt be able to load all our apks into the phone (Some might, others like us go nuts).
But the concept is not a bad one, especially if there was a way when installing the apk's it asked for the location to add.
Click to expand...
Click to collapse
I would say that if HaRet was pointed to the correct place correspondingly, either NAND or storage would work as I previously mentioned. I am unsure about any performance gains to be had, but it would surely save on sd card wear.
People say that going from NAND would corrupt bootloader, but since WM is already booted using HaRet, there is no reason that the bootloader is touched, even if it is all stored to NAND. MagLDR is different, that is going for a cold-boot of Android, no WM involved at all. HaRet and MAGLDR work different and I think that if Haret was made to look for /Android in NAND, it could work just the same as if off of sdcard.
And booting from the phone's storage memory would be even safer, as no far-fetched idea of HaRet corrupting the bootloader is even conceivable, as NAND would never even be touched at all.
I honestly believe though that if a version of Haret was released that looked to NAND memory for /Android, that WM chefs could bake lite version WM ROMs with popular Android builds already built into NAND, maybe in the \Windows directory. The chef could even cook in a modified version of Exceller's Android loader which would look to \Windows for the Android folder.
Since Android development is so far along, and there are so many builds that are 100% or near 100% stable, I do think that going this route is a viable option, I mean there are already WM builds that will install an Android build to the sd card all by themselves after you boot them up the first time. This seems a natural progression of that concept to me.
Maybe somebody could contact Netripper, and ask him more about this idea, and see if he would be kind enough to build a HaRet version to look to NaND memory, and another to look to internal storage space, the rest could be done by the end user, as there are WM kitchens available, and most ppl here could make a .cab to install \Android to internal.
That's my $0.02
huggs said:
I would say that if HaRet was pointed to the correct place correspondingly, either NAND or storage would work as I previously mentioned. I am unsure about any performance gains to be had, but it would surely save on sd card wear.
People say that going from NAND would corrupt bootloader, but since WM is already booted using HaRet, there is no reason that the bootloader is touched, even if it is all stored to NAND. MagLDR is different, that is going for a cold-boot of Android, no WM involved at all. HaRet and MAGLDR work different and I think that if Haret was made to look for /Android in NAND, it could work just the same as if off of sdcard.
And booting from the phone's storage memory would be even safer, as no far-fetched idea of HaRet corrupting the bootloader is even conceivable, as NAND would never even be touched at all.
I honestly believe though that if a version of Haret was released that looked to NAND memory for /Android, that WM chefs could bake lite version WM ROMs with popular Android builds already built into NAND, maybe in the \Windows directory. The chef could even cook in a modified version of Exceller's Android loader which would look to \Windows for the Android folder.
Since Android development is so far along, and there are so many builds that are 100% or near 100% stable, I do think that going this route is a viable option, I mean there are already WM builds that will install an Android build to the sd card all by themselves after you boot them up the first time. This seems a natural progression of that concept to me.
Maybe somebody could contact Netripper, and ask him more about this idea, and see if he would be kind enough to build a HaRet version to look to NaND memory, and another to look to internal storage space, the rest could be done by the end user, as there are WM kitchens available, and most ppl here could make a .cab to install \Android to internal.
That's my $0.02
Click to expand...
Click to collapse
Very possible,
Haret needs to be modified for that,
not sure who can do it.
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers
greg17477 said:
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers
Click to expand...
Click to collapse
spot on
NAND = Internal memory
greg17477 said:
Guys as far as i know, on hd2 is nand memory the same as internal phone memory.There is no built in sd card. I am not 100% sure, but there is 512mb nand memory (internal memory). I mean, we install winmo roms into the nand. So if your winmo rom is about 200mb, you will be left with soemthing like 300mb internal phone memory. Correct me, if i am wrong..
cheers
Click to expand...
Click to collapse
Well true except the TMOUS, which is 1024 mb, so it should be plenty then to run Android this way right?
Even with just 300 left after WM ROM, Android could still be done conservatively, without much apps installed, or with some kind of a2sd functionality, Froyo has inbuilt app to sd functionality, albeit not as good as a2sd ext2 or ext3 setup.
Guys I think you are missing the point, If this was possible, viable or worth it, it would have probably already been tried and tested and released along time ago.
The fact that this hasnt been done already tells me that its been thought about and rejected for good reason.
PS. NAND ..IS.. Internal memory guys so the running loading of kernel and files from internel memory instead of nand is a moot point.
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
hmmm,
well in that case, kernel could be programed to create Data IMG on SD, if you have been following the Rhodium Nand Project , you will see what i mean, a few components are on NAND and a few on SD
dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
Its not about putting the whole Android folder into nand, but for example only the system partition, just like in the RAM builds. All data and user stuff goes to sd.
Btw what do you mean by "...*could* be possible to put Android on internal storage(NOT NAND)." ? nand is the internal storage (memory). Or you guys are using different terms do you mean by "nand" the reseverd space where roms are stored and by "internal storage" the free space left (still in nand)?
TheATHEiST said:
Guys I think you are missing the point, If this was possible, viable or worth it, it would have probably already been tried and tested and released along time ago.
The fact that this hasnt been done already tells me that its been thought about and rejected for good reason.
PS. NAND ..IS.. Internal memory guys so the running loading of kernel and files from internel memory instead of nand is a moot point.
Click to expand...
Click to collapse
Actually your part right, it was tested and released in the initial phases of the Rapheal (aka Fuze) and ran smoothly from what I read, yes there were hiccups, but that was due to the build being still in the alpha stages.
dharvey4651 said:
Here's a question for you guys thinking it *could* be possible to put Android on internal storage(NOT NAND) instead of SD...
What do you think will happen after your device creates the data.img and tries to place it in the Android folder on Internal Storage? I for one think my device(1024 TMOUS Leo) would run out of memory and throw error after error about internal storage being critically low until I did something about it.
To top it off, what about the 100 some odd folders that Android creates on the SD card now? Where are you going to put all of that on internal storage?
To sum it all up folks, until we're running from nand and have dedicated internal storage(W/O WM), it's not likely to EVER happen due to sheer lack of space, even if haret was reprogrammed to allow booting from internal storage.
Click to expand...
Click to collapse
This is where your part wrong as well. if you use a pre-set data.img file, yes for the most part you cant use anything larger then possibly 512mb on a TMous, 256 on others, definitely could not use the 1gb img file thats for sure, but the other part of this your missing is that if you dont put a pre-set data.img file, during the initial loading of android, android will create the file itself, and IF I am right the file will be sort of dynamic, dynamic in the sense it will expand as needed, I seriously doubt it shrinks. And on top of this you would then use the function a2sd, which in then would install your apk's to sd card. As of right now how much bigger is your 1gb data.img file that everyone added to their SDCards? Bet still the same size.
mally2 said:
hmmm,
well in that case, kernel could be programed to create Data IMG on SD, if you have been following the Rhodium Nand Project , you will see what i mean, a few components are on NAND and a few on SD
Click to expand...
Click to collapse
Actually after doing some reading, neither the kernel (if I read correctly) nor is haret.exe the cause of pointing the boot location. I did some searching (Mind you I am NOT a LINUX person), but reading some of the files, I am guessing that the key file which controls the loading of Android, is located in the "init" file in the rootfs.img file. I mounted this file in windows to look thru it and view files, and that file seems to have a major role in it, how it works I dont know yet.
To All, please I am not trying to cause a stir here, I am merely looking at possibilities, and unfortunately I cant test them out since I dont have a spare SDCard as of yet (Will ina couple of days, 32GB SDCard for $40, woohoo), and then I have nothing to loose to try, cant brick the phone, since winmo is the default loading OS anyway. One of the reason it might not have been put on the phone as I said, could be speed, I dont know how much faster internal phone storage would be opposed to sd, but another reason why could be cause then the installation would put folders on the root file system of the stroage card and make it messy. Also alot of people constantly flash new builds, this would also hamper your android install being on the phones storage. And remember our normal HD2 roms are between 225 and 250mb stock or custom, where lite versions or stripped down version would be considered better for taking up less space.
One thing to keep note, during all this, I have an HTC Aria (Liberty) as well that I just recently got as an upgrade to one of my ATT lines, and I checked the internal storage of that phone, its stock with ATT's build of Android, and it has ONLY 168mb of storage available, and it came with a 2gb sd card. Now think about that when saying that the files would get to big, obviously the HTC Aria doesnt have anywhere near the capacity of the HD2.
And again to anyone else, let's be clear, yes the phones storage is a NAND, but just to make clear, we aren't talking about doing a cold boot of android, I know how sometimes that can get confusing.
Sorry guys, yes internal storage is NAND memory, the reason I drew a distinction was to make a distinction between loading from internal storage and ROM space. I only meant to illustrate the difference between the two and demonstrate my opinion that both are possible. I think with further investigation and testing, advantages of booting this way will begin to emerge. For example we will be able to remove the sd card while Android runs, not a great benifit, but you get the idea. But yeah, I should have used the term 'ROM Space' instead of NAND, I only meant to show difference between the 2 places to boot from.
Sorry if i caused any confusion.
Sent from my... whatever
Hello Everyone,
I like most people upgraded my Bell i9000m from Kies to Froyo, only to have it bricked with the "can't mount /dev/block/mmcblk0" error at the recovery screen during boot-up. I upgraded it last week, where it took the firmware from JL8 to I believe JK3 or JL8 (not sure at this point).
Unfortunately I bought my phone from some guy on Kijiji using it on Rogers, so I doubt Bell is going to handle the return or give me any love
Anyways, I spent many days long days trying to get it back working, and I found a work-around that requires using an external SD card. and going back to Android 2.1 ECLAIR
Steps (This is what I did):
1. Install JK3 stock ROM via Odin (with re-partition at the pit on samfirmware.com, didn't update boot loader)
2. Install K13c speedmod kernel via Odin
3. Insert 16GB External SD card
3. Boot phone to Froyo
4. Reboot to recovery console and wipe data/everything
5. Install JL8 stock ROM via Odin (no re-partition, didn't update boot loader)
6. Phone will boot-up into recovery mode and automatically do wipe data
7. Phone will boot into ECLAIR
8. You will see internal storage of 1.85GB free.
9. Install Market apps - I installed twitter
10. If you remove external SD card, twitter will crash.
11. If you reboot phone without external SD card, you will get rebooting logo
12. If you put external SD card back it, phone boots!
This wasn't a fluke - I was able to reproduce if I flashed other ROMS (XXJPY or similar) instead of JK3.
Background:
Even though the phone can't boot with stock ROM, if I install JK3 ROM + speedmod K13b speedmod kernel, I can get the phone to boot to Froyo, but there is no internal storage (it shows up as 0 bytes available). So you can't install Market apps, and therefore is useless. I can't even mount the external SD card under the Settings app!
So I tried to log in the Froyo device using adb shell, and what I found is that internal SD card is no longer showing up under linux, and the OS thinks that the external SD card is the internal one. This is probably why the external SD card can no longer be mounted.
I figured out that the external SD card shows up as /dev/block/mmcblk0!!! WHich is the same block device as the internal SD card...so I'm thinking if I reboot into recovery and format SD card, how come it's not working? I even tried to partition the external SD card with android partitions, but still nothing!
I think Froyo is 'smarter' in that it knows the external SD card is not internal (whether it's grepping the device-info for manufacture data, don't know).
But if I go to JL8 Eclair, the Android 2.1 is 'dumb' enough that is doesn't see the difference between internal and external, so formats the external to look like internal.
Once I boot to ECLAIR, the external SD card is greyed out under Settings app, but I get 1.85GB internal storage!! OK I can't access the whole 16GB of the card, but at least my phone is not toast.
I can go ahead an install apps, which will install to the external SD card. But if you remove the external SD card, the phone will no longer boot. If I remove the card and apps are running, apps will crash (case in point: I tried twitter).
It will be nice if others can re-produce my findings. But for now my Samsung Galaxy S has been saved!
Kashif Shaikh
this sounds promising, can some more people confirm this solution to use External SD to imitate internal SD?
It worked for me as well! I have i9000M version, with internal SD failure. I'm also using 8GB external microSD card. I tried several 2.2 Android firmwares - specifically I9000XXJPY, I9000XXJPU. With update to speedmod-kernel I'm able to load device, but it doesn't see neither internal nor external SD card. So I couldn't install any applications, upload data or even shot with camera.
Based on this thread, on top of XXJPY with speedmod kernel I uploaded I9000XWJM8 firmware (Android 2.1) with Odin 1.7, no repartitioning. It worked right away - device loaded and I can see ~2GB of program storage (assume they storage is located on my external card). Both internal and external cards are shown as "Not available" in settings. I can install applications now, which made "brick" a bit better then it was before. Unfortunately, I still can't upload any data, i.e. a book for FB2Reader. And can't make a photo with my camera. And it's now Android 2.1, which looks slower.
First of all - thanks for the advice! It would be good to have this topic "sticked" and distributed - there might be other guys with no chance to repair phone under warranty.
Secondly - if someone can do a "hack" for Android 2.2 firmware so it can use external SD card for program storage specifically for I9000M device? And it would be terrific, if the remaining part of SD card (or at least some fixed size, like 4 GB) can be mounted as storage, so the data like music or photo or books can be uploaded.
I'm able to connect to the phone using adb tool, but I can't find a folder on the device where I can upload (push) a file to. I'd like to upload a book to the device so I can finally use it as a reader. I tried all "root" folders (adb shell -> ls) and all don't work. It says "No such file or directory" or "Permission denied".
Is there a folder on the device which I can push file to using adb tool? Maybe somewhere where applications are installed to, i.e. Program Storage location. Please help!
Anyone else following this thread with I9000M with internal card dead?
This isn't much of a fix. This will only work with phones with slightly corrupted (and not fully corrupt) sdcards; eventually your phone will probably stop booting with this "fix" as well. You're going to eventually loose some of the other partitions such as stl10 to corruption, and then you're screwed.
The OP's phone is corrupt in a specific way that allows this - and there are various procedures that will get your phone to a semi-bootable state if you only have a partially dead sdcard. Like the OP said - just installing speedmod kernel with an external SD in will allow your phone to boot, for example (I got my dead sd i9000m to boot froyo with the speedmod kernel, and others had reported the same as well). Then if you're technical enough you can switch around your mount configs and get it to work without the internal mmc device.
It doesn't matter if you bought your phone off kijiji or craigslist 2nd hand; send it back to samsung (or go thru futuretel or a similar provider). No receipt is going to be required (if they ask... just say you can't find it). Products like this will always be repaired under warranty based on manufacture date code.
Send your phone back; don't try to fix it - it's a hardware problem with the mmc connection.
Unfortunately, I'm 10 thousand miles away from Canada with no chance getting there. If I had option to send it back for repair I would do it right away. So I'm searhing an option to use this semi-brick as much as possible.
My i9000M phone has totally corrupted internal SD card - it failed two months ago and I tried all options for it reformatting / remounting / whatever. With speedmod kernel it loads even without external sd card. It just allows loading without internal storage - not use external card to mimic internal. Unfortunately, it doesn't see any storage then - no internal, no program, no external card. So it just loads.
With Android 2.1 and external card it loads _and_ see 2GB of program storage (on external card). It doesn't see any other storage - so I can't upload any file. But at least I can install applications.
I'll try this solution after buy a Microsd card. My i9000M internal sdcard dead in two days ago after fixlag use ext2 partitions.
hi all. i didn't find JL8 stock ROM for sumfireware.com.where can find it ?
i flash my phone step by step as top post.
but after flash 2.1 rom with insert SD card , my Phone still cannot boot into ECLAIR .
who can help me? thanks. my phone can boot to 2.2 system without internal card.
SHINE.YANG said:
hi all. i didn't find JL8 stock ROM for sumfireware.com.where can find it ?
i flash my phone step by step as top post.
but after flash 2.1 rom with insert SD card , my Phone still cannot boot into ECLAIR .
who can help me? thanks. my phone can boot to 2.2 system without internal card.
Click to expand...
Click to collapse
Samsung or bell can help you. Send your phone in for repair....
for same reason .i cannot send my phone to bell. so i very want to know find JL8 rom to let me phone canbe use . please help.
HI guys . thanks for your help.
actually ,every I9000 2.1 rom CAN use this solution. just need your external SD same as your phone internal SD size. if you are 8G internal SD , you must use 8G external SD card with 2.1 ROM . you can get 1.85G system space.
I've just tried XWJVB firmware - stock Android 2.3.3 - and it also works! Phone loads without flashing custom kernel.
I wonder, if there is a way to upload any file to the phone - so I can put there a book and read it.
does this mean this workaround still can't recover the files that were originally in my internal sd?
Nope. the internal sd is gone, probably forever.
workaround allows running the phone and having 2GB out of microsd card available for programs storage. it allows downloading and installing application from app market. still, you don't have other storage - can't upload a file or even make a photo with camera.
very wierd. if anyone would suggest a workaround to upload file to the device - even using any hacked way, like from abd or whatever
I flashed custom Kernel (CF-Root-XW_XEE_JVB-v3.1-CWM3RFS) over latest JVB. The device is now rooted.
Using adb tool I was able to push fb2 file to device - specifically to dev folder. (adb push file.fb2 /dev). Using Moon Reader I can open and read it! That's terrific after long time of finding a way of doing this.
Unfortunately, Moon reader is the only app that works. FBReader tries to open the book but fails with writing cache to sd card (which is broken).
This is a most useful post, thank you. I get the phone working on 2.2 which is great but I am unable to find the JL8 stock ROM, I locked for it everywhere but could not find it, would someone please indicate where to find it...
raullugo said:
This is a most useful post, thank you. I get the phone working on 2.2 which is great but I am unable to find the JL8 stock ROM, I locked for it everywhere but could not find it, would someone please indicate where to find it...
Click to expand...
Click to collapse
Why would you need old stock ROM?
Just flashed XXJVP stock ROM to my I9000M. This is Android 2.3.4. Taken from http://forum.xda-developers.com/showthread.php?t=1011901
Flashed CF-Root-XX_OXA_JVP-v3.7-CWM3RFS on top of it for rooting
Phone works
It needed some tricks this time to upload a file to deivce. For some reason all folders appear to be read only, including dev. So I used abd shell command to change folder permissons
adb shell
$ su
# chmod 777 /data
then exit and
adb push file.fb2 /data
File is stored and is not lost on reboot, like it was for dev folder
stuck on step 6..
first of all, this is a great post for those who still stuck with a dead i9000m and no help from Sammy!
Steps (this is how i followed)
1. fine
2. fine
3. fine (i inserted a 16gb Sandisk class 2 in FAT32 format)
3a. i couldn't 'boot to froyo' i'm not sure if you mean fully boot into the OS or not, but it was in a bootloop
4. i was able to get to step 4 somehow to the recovery (3e) and wipe data (there was still the cant mount error when wiping data but no error when wiping cache partition - is that normal?)
5. i cant find JL8 but others here suggested any other 2.1 ROM works so i tried JM8 (no repart/no update bootloader)
6. the phone did do something other than boot loop! (first time wow!) it was trying to copy something but it didn't go all the way through.. there was an error saying 'efs format failed /dev/block/mmcblk0p2' after/during 'coping media files'.
- could it be the wrong format going in (should it be something other than FAT32?)
- could it be that class 2 was not the right class (no fast enough??)
- the copying process stopped after it finished copying media files.. (the micro sd card did have some media files
- there was 2 folders Samsung folder (with media files) and svox (i think that was the name of the folder)
can anyone shed some light on where i did wrong, thanks everyone, love this forum btw.
pavbul said:
Why would you need old stock ROM?
Just flashed XXJVP stock ROM to my I9000M. This is Android 2.3.4. Taken from http://forum.xda-developers.com/showthread.php?t=1011901
Flashed CF-Root-XX_OXA_JVP-v3.7-CWM3RFS on top of it for rooting
Phone works
It needed some tricks this time to upload a file to deivce. For some reason all folders appear to be read only, including dev. So I used abd shell command to change folder permissons
adb shell
$ su
# chmod 777 /data
then exit and
adb push file.fb2 /data
File is stored and is not lost on reboot, like it was for dev folder
Click to expand...
Click to collapse
Thank you for the instructions, tha only reason to look for the jl8 rom is to follow the instructions to the letter. I trying your method right now, thank you for taking the time to give me another shot at my SGS, I will let you know how it goes