yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] julian.kueh:
Tried loading Boca's new Tom which went smoothly but ran into a few problems such as running low on memory so couldn't install apps and internal SD card unable to be mounted. So restocked to Icarus and teamed that with 3.3 kernel and now Icarus is smooth and fast. Thanks again, OC team.
[Galaxy Tab  Android Development] dannyvanderzande:
@rangercaptain

No I havent but Ill try after dinner!

So.. I should unrar the tar file and flash dbdata.rfs? In which Odin field do I have to put this? No need to repartition or use a pit-file I guess?
[Galaxy Tab  Android Development] Pharaohnough:
Unfortunately so.

I too was quite pleased with how focused this thread was thus far

Every village has its idiot I suppose

You're right it should not take that long

Is it still there? Did you or the Tab do anything?

It looks like you are using Stock-Safe-v4.

I know it's been said and you've already confirmed using v5 but could you please triple check? The errors in your image happen with v4 but were resolved in v5

"stock market" - ha ha :D
[Galaxy Tab  Android Development] alphard_alshua:
I just bought samurai. 2 : vengeance, but i can't install it, it says "Error, there is insufficient space on this device", how do i fix this? I check on settings, and there is still 12gb free on the internal sdcard and 8 on the external.
[Galaxy Tab  Android Development] dannyvanderzande:
@Pharaohnough

I just redownloaded the files from the overcome website after I deleted the old ones. So if the files on the overcome website are right ones I am a 100% sure Im using v5... I will download the V5 one more time... just to make sure sure sure sure sure!
[Galaxy Tab  Android Development] charon72:
Still there .

havent touched anything. havent fiddled around with cable or buttons. and restocking is at 1 hour plus now.

can i power off and enter download mode again or will that cause a brick ?

attached a screenshot of odin. but everything is looking fine.
[Galaxy Tab  Android Development] Pharaohnough:
It sounds like your partitioning/conversion did not take place correctly

Be sure to check all three checkboxes in Odin when you re-stock- this is crucial

Are you facing any other issues with space, like the Market issues other people were facing?

The only reason I can think of for not having enough space after a re-stock is if you restocked with v4
[Galaxy Tab  Android Development] marjibis:
Damaged Internal SD Card ...

.. is the message I'm getting after going the whole procedure of installation. I have followed the procedure exactly but I'm getting the message after booting up and before installing the actual Jupiter Rom.

I have done:

*the signed boot patch - succesful

*used latest Odin to install the pit,stock and modem - succesful (damaged SD card message started after booting from this stage)

* used Odin and installed the Kernel - succesful

after which I am getting the said message again and cannot access both SD cards

What should I do?

Thanks
[Galaxy Tab  Android Development] dannyvanderzande:
@Pharaohnough In the picture I posted you can see I did that, the screenshot was taken seconds before I hit the start button...

edit: this picture
[Galaxy Tab  Android Development] Pharaohnough:
What OS are you running on your PC?

Have you successfully re-stocked with Odin before?
[Galaxy Tab  Android Development] charon72:
Running win7 x64 ult.

and yes i have restocked before on this system with no problems.

i am quite puzzled what went wrong here.

followed guide to the letter like the other times i restocked.

sigh.
[Galaxy Tab  Android Development] charon72:
Fubar...

now i got a FAIL.

and usb device not recognized.

tab still on download screen.

do i try again ?
[Galaxy Tab  Android Development] dannyvanderzande:
@Pharaohnough/tpb

Downloaded the stock v5 again from the download section of the website and tried again...

Still the same :( .. what now?
[Galaxy Tab  Android Development] Pharaohnough:
Did you do anything or did it go fubar on its own?

Try the following:

- Close Odin

- Power off your Tab completely and start it in Download mode again

- Right-click Odin and go into its properties- run it in Compatibility Mode (Windows XP) and also as Administrator (even if you are an Admin on your machine)

These steps may help

Please report
[Galaxy Tab  Android Development] Alcibiade:
I don't mind giving my UV settings (-50mV all accross the board) but if you ahvea bit of experience in overclocking and undervolting (I do, I have been overclocking since I built my very first PC ehehe) you will understand that not all chips are born equal and some will tolerate higher levels of overcloking or undervolting than others

That saids your epxrience is interetsing, I will try to undervol more all across the board except at 600Mhz
[Galaxy Tab  Android Development] Alcibiade:
Yep i remmber having to do that initially with my tab after I bought it... I was soooo happy when IJMF came out and I found out i didn't need to do that anymore
[Galaxy Tab  Android Development] charon72:
Well, did not do anything at all. it managed to fail by itself.

was not able to get the download image back on tab, got some ugly pic of

phone>!>pc

but i was able to get odin to recognize device and did restock again, and it has just finished.

now it has booted up and problem seems to be solved, let me fiddle a bit more and see if all is well.
[Galaxy Tab  Android Development] alphard_alshua:
No other issue with the space just the market. I checked the storage space and the cache, but there are still a lot of space. Will patch the market solve this problem?
[Galaxy Tab  Android Development] charon72:
Att Pharaohnough

Thank you for the assistance.

i am now in CVW and flashing the jupiter.

i did do one thing different when i tried the restocking the second time.

i removed the microsd card...

can this be the explanation ?

and if so, please add this to the guide :)

Charon.
[Galaxy Tab  Android Development] dannyvanderzande:
Decided to try again once more, still the error from the pic I posted earlier.

I am sure I have the right files.. (unless the overcome website hosts the wrong files ;))

There's no micro SD in my Gtab!

I even flashed under win xp compatibility mode as administrator (worth a try...)

:(

I did however notice yesterday that I lost my root somehow at this point but I managed to flash it back with a new version of CWM recov from which I installed Jupiter WIPE
[Galaxy Tab  Android Development] tovarish:
Thanks for the info. I know not all chips are the same but atleast my tab should behave the same wrt uv between two kernels (3.1.0 and 3.3.0) if the starting voltages are the same. I was just curious why this difference occurred.

Now am trying more extreme settings of

100 = -175

200 = -150

400 = -125

600 = -75

800 = -100

1000 = -100

I'll let you guys know if this is also stable. To test it I will just be running my tab from 100-400hz. Its quite slow at that speed but i guess necessary.
[Galaxy Tab  Android Development] heymerv:
Just flashed my tab to Overcome ROM for the first time.

Have been using it for the past 2 days... so far I didn't encounter major issues with it. Everything loads extremely fast and snappy. Now I can add more widgets to my home screen without much worry about performance bottleneck.

However, there are so far 3 issues identified

- New Android market lags when its trying to load up the thumbnails of the apps (Guess not fully optimized yet)

- Android market description appears in random languages (Eng, Chinese, Jap) (Problem was mentioned by someone else too)

- 3D Gallery (Stock) is extremely slow. It seems that it always have to rebuild its image cache when launched. I started switching to Gallery+ and find it loads many times smoother. Only problem with Gallery+ is scrolling too fast may cause it to force close (crash)

I am currently running on screen dpi of 202... I don't think thats the cause of the problem as all my other apps works. Btw, dpi of 182 will not work well with the dark theme as some dialog background images did not fill correctly. (No big deal anyway)

Great job to the Overcome Team.

Also hope to see more updates at your "Bugs Tracker" website page for our reference on the various releases.
[Galaxy Tab  Android Development] Pharaohnough:
The Market patch will not solve the problem but a restock certainly will.

Can you tell me the path you took to Jupiter? (which ROM did you come from, did you re-stock along the way or not, if you did re-stock what version did you use?)

I have heard some people having luck with that before :confused:

Glad you got it working in the end anyway
[Galaxy Tab  Android Development] alphard_alshua:
I patched the market, and it works now 100%. The new market is the culprit, too bad since i like the new interface design. Oh well, i hope you guys can fix it.

Other than that, it's running well.
[Galaxy Tab  Android Development] enyeng:
Market Insufficient Space

Any definitive way to check that the restocking is from v5 instead of v4? Some scripts or directory structures which exist / do not exist in one or the other?

I did a restock method with v5 (coming from CM7) -> Kernel with Odin -> Jupiter Wipe. I am quite sure that what I used is v5 because prior to coming to Jupiter, I have never restocked and never download the restock ROM. After installation, I then restore more than 200 apps using Titanium.

Tried to download "Cordy" app because this is in the Editor's Choice page of the new market and I got the "Insufficient space problem" in the market. The market page of this application says that its size is 27.96 MB. Downloading "small" apps work fine, though.

In Titanium Backup the memory information shows:

System ROM: 40.2 MB free

Internal: 837 MB free

DB data: 59.3 MB free

SD Card: 11.4 GB free

Ext. SD Card: 2.52 GB free

Will this related logcat entries provide more clue of what's happening here?

D/Finsky (11020): [1] Installer.downloadAndInstallAsset: Downloading and instal
ling Cordy.
D/Finsky (11020): [1] DownloadImpl.setState: Download 'Cordy' transitioned from
(null) to (UNQUEUED).
D/Finsky (11020): [1] DownloadImpl.createObbDownload: Skipping obb download wit
h state NOT_APPLICABLE
D/Finsky (11020): [1] DownloadImpl.createObbDownload: Skipping obb download wit
h state NOT_APPLICABLE
D/Finsky (11020): [1] DownloadQueueImpl.add: Download Download : Cordy added to
DownloadQueue
D/Finsky (11020): [1] DownloadImpl.setState: Download 'Cordy' transitioned from
(UNQUEUED) to (QUEUED).
I/installd( 237): free_cache(29323332) avail 837890048
I/installd( 237): free_db_cache(29323332) avail 59322368
D/Finsky (11020): [1] DownloadImpl.setState: Download 'Cordy' transitioned from
(QUEUED) to (CANCELLED).
D/Finsky (11020): [1] DownloadCompleteListener.onCancel: Download Download : Co
rdy: onCancel called.
D/Finsky (11020): [1] DownloadQueueImpl.remove: Download Download : Cordy remov
ed from DownloadQueue
[Galaxy Tab  Android Development] rangercaptain:
I think you need to start fresh. Turn everything off (tab, pc, mind) and go take a coffee.

After your break, print out the guide, and start at the beginning. I'm sure you will get it this time.

When you say you lost root, I think your stock flash was missing the dbdata step, so I recommend the fresh beginning.
[Galaxy Tab  Android Development] dannyvanderzande:
Problem is, I started yesterday, same result after 3,5 hours and a lot of times flashing.. Than I had a good night sleep, went to work, and decided to give it another try.. and it still doesnt work.

I am willing to video every step I take and send it to you but I am a 100% sure I'm doing the exact same thing as the guide tells me to do, it just doesnt reboot into the stock Image, It boots into android recovery.

If I reboot from that I do however boot into the stock rom, but I can not enter the CWM recovery when i reboot again.. I just keep getting stuck in the android recovery so therefore something must have gone wrong during the first step of flashing.

Another thing, I downloaded the files on 2 different locations, on different computers and even tried Heimdall (but got stuck on how to flash using Heimdall) so either I'm plain stupid... or something must be wrong with my tab...

If anyone knows how to flash this using Heimdall please tell me, I am willing to give it a try and see if it makes any difference! :)
[Galaxy Tab  Android Development] alphard_alshua:
Patch the market, it solved the insufficient space problem for me.

http://www.teamovercome.net/?page_id=558
[Galaxy Tab  Android Development] oddball69:
I watched your video and i think you force reboot to quickly, you should wait

untill odin looks like this:

In your Youtube Video you didn't get the "GREEN" PASS in the Odin window

( above the green time window above the yellow com port window )

Try again and wait a little longer, you should see the following in the

message window as the second last line: ( succed 1 / failed 0 ) ;)
[Galaxy Tab  Android Development] dannyvanderzande:
Thank you for your responce. I tried unchecking the auto-reboot to make sure (however In my still open Odin it gave the succeed 1/failed 0 line) but unfortunately it does not make a difference. Once I reboot the tab it reboots into the android recovery and the same old errors pop up...

Do you know how to flash using Heimdall, mayb that will work...

Sorry for the inconvenience guys.. I've never had any big flashing-issues I couldnt work out,,,
[Galaxy Tab  Android Development] oddball69:
Two more things to test/check:

1: Is your battery charged ?

2: try to create a map Directly in c: ( like c:\Overcome ) and unpack your

overcome files to that map. seems like you have a very long path to your

files, and i dont know how long paths Odin can handle.

Edit:

And a question, do you get the "GREEN" PASS ??? ( TOP Left corner in Odin ),

becouse you didn't get it in your Youtube video.
[Galaxy Tab  Android Development] dannyvanderzande:
I tried to flash from C:/overcome/*FILES* but i end up with the same /efs errors. The battery is (as good as) full, I am sure of that. Thank you for your ideas...

Does anyone know what this /efs problem could be. I have no SIM card in my tab but this has never been neccesary as far as I know..
[Galaxy Tab  Android Development] thepittbull:
Sorry, just came back online and seeing all the messages. Haven't seen you

Ding ding ding ding. There's your issue. As I mentioned earlier. After that first Odin flash, you will indeed get those crap lines. It should also have yellow or red lines saying applying Multi-CSC or something to that effect. It's supposed to do that. It is after you flash the Overcome kernel, that you get the RFS->ext4 conversion. Then it should continue to reboot to the stock ROM running the Overcome kernel.

It is after this stage, where you can reboot into the Overcome CWM recovery.

BTW, @rangercaptain. If the users restock according to our guide, there's no need for the additional step to flash the dbdata.rfs. That was a requirement in the first time the stock JQ1 came out, but not with our stock safe package. It's included in the tar file AB created.

EDIT: After looking at the pic you sent, didn't have time to see the youtube video, yes, what I said above is correct. That "error" is part and parcel of it. That's what happens when you install the stock ROM now. We've removed the Overcome kernel from the stock safe image already, and it's now an additional step. For more information about why we did it, refer here: http://www.teamovercome.net/?p=1220

---

Guys, when I first coined the term "restock" it means restocking according to our process. Can we move forwards that when we say restock in the Overcome threads, it means with the stock safe package that the Overcome team created? Not the standard stock, not another persons version of it, but "restock according to the guide using the package we created"?

I don't care how you guys want to refer to it within other developers threads, but at least in the Overcome thread, at least it'll save us from having to type "restocking according to the guide using the stock safe package the team created"? It gets tiresome at support level... :(

Pretty please, please with sugar on top? ;-)
[Galaxy Tab  Android Development] dannyvanderzande:
I know you said about the red and yellow lines. problem is that they dont go away.

Even if I reboot into the "stock rom", next all the options, shutdown the tab, and vol-up and power up into recovery,

I just get into the same old android recovery menu with the same old /efs errors, CWM just doesnt show.

I just tried again and it has the same result as in my picture earlier :(

Thanks for helping though, im sorry for being hard on you guys! :(
[Galaxy Tab  Android Development] thepittbull:
Yes.... let it finish all it's supposed to apply, it should reboot to the ROM!

IF YOU TRY TO GET INTO THE RECOVERY AT THIS STAGE, IT WILL ALWAYS SHOW THAT!!!! DO YOU GET WHAT I MEAN. THE STEPS HAVE BEEN CHANGED NOW! FROM JUPITER ONWARDS, IT HAS BEEN CHANGED. YOU HAVE TO FLASH THE OVERCOME KERNEL SEPARATELY!

(Sorry for shouting, but I need to emphasise the point. The process has been changed, the guides have been updated. Please follow it step by step.)

NOW, shut down the Tab, put it into download mode again. AND FLASH THE OVERCOME KERNEL 3.3.0 (the tar package!)

Once it reboots, you should let it boot up completely. You should by now hear the sound of the sexy *****... let it finish, and let it finish booting up. It might take a few minutes.

THEN.... You should be able to get into the CwM recovery.

EDIT: Anyway, one good thing came out of this, that pic! ;-) I've added it to the guide already!)
[Galaxy Tab  Android Development] oddball69:
But after you do the Restock, you let it boot up properly and then

you should go to DOWNLOAD mode again

NOT CWM recovery, and the you should flash the Kernel and then finaly

the Overcome Rom itself, it's an extra step with the Jupiter Rom.

This is a copy/paste from the Installation Guide READ CAREFULLY :

6. Once you’ve seen the green “PASS!” notification like the one in the screen above, where there’s no failed notification, which means it’s successful! By now, if you look at the Tab, it would have rebooted itself. It should be rebooting into the stock Samsung JQ1 ROM. Please let it boot completely.

Once it’s done booting up, you should get your Tab in a new, factory-fresh JQ1 Gingerbread condition, together with the necessary setup screens (and PIN entry, if your SIM card is PIN protected). Skip past it, by pressing “next”, “next”, “next”, as necessary, until the setup wizard is done. Don’t worry about setting it up properly as we’ll be wiping it again! ;-)

7. Once you’re finally in the Tab’s default desktop screen. Press your menu key, and choose “Settings”. Navigate to: “Wireless and network” > “USB settings” > and select “Mass Storage”. Now, connect your Tab to your PC, set your Tab to use it as a mass storage device. Once it’s mounted, and you can open your Tab like a removable drive on your PC. You should copy the “001003-Overcome_v3.0.1_JUPITER_Wipe.zip” file into the root of that drive.

8. Now power down the Tab. Once it’s powered down, put your Tab into the DOWNLOAD mode again (refer to step 2 again if you’ve forgotten!). Now it’s time to flash the Overcome Kernel 3.3.0 that you’ve downloaded earlier. Once the Tab is in download mode, fire up the ODIN tool we’ve used earlier, and this time select 002001-Overcome_Kernel_v3.3.0.tar in the PDA field. You should get something like this:

This will be a very short flash. Once it’s done, the Tab should reboot itself.

9. As it reboots, you will start hearing what’s know to us as the “sexy voice” as the system converts the filesystem from Samsung’s proprietary RFS filesystem to the more robust ext4 filesystem. This should take a couple of minutes if you’ve restocked according to the instructions above. Once it’s done, it’ll continue booting up, you’re ready to flash the Overcome ROM!

Edit: Dam it Pitbull, you beat me with a couple of minutes :D
[Galaxy Tab  Android Development] dannyvanderzande:
This is what I do/what happens:

1: Put tab in Download mode

2: Odin

-Pit: gt-p1000_mr.pit

-PDA: GB_Stock_Safe_V5.tar

-PHONE: modem.bin (JPZ modem for me)

-Repartition: Checked.

-Auto Reboot: Checked.

-F. Reset Time: Checked

3: Odin --> Start

4: Wait for tab to flash (Odin Shows green light and text All threads completed. (succeed 1/failed 0)

5: Tab reboots automatically

6: Strange errors appear (/efs error, cant wipe cache, MULTI-CSC) and after a few seconds I get a recovery menu with the following options

Android Recovery - Reboot system now.

Android Recovery - Apply update from sd card

Android Recovery - Wipe data/factory reset

Android Recovery - Wipe cache partition

7: Wait.... nothing more happens....

8: Android recovery --> Reboot system now

9: System reboots into a normale Android Image...

10: Next through all the options

11: Make USB connection to pc and copy 001003-Overcome_v3.0.1_JUPITER_WIPE.zip to SD card.

12: Shutdown tab

13: Reboot into recovery (volume up and power)

14: Tab boots into android recovery and I end up back at step 6...

If I read what you are saying correct.. I'm not doing anything wrong.. If I am please point to the step I seem to not be doing right...

I think I must be stupid because I think I am now seeing what I might have done wrong... let me try...
[Galaxy Tab  Android Development] oddball69:
Step 13: But you should not boot to recovery, you should boot to DOWNLOAD mode again !!!!!! Power + volume down !!!!!

And use Odin to flash the Kernel........
[Galaxy Tab  Android Development] thepittbull:
geez! Listen!!!!

Between steps 12 and steps 13. Flash overcome kernel 3.3 tar with odin! THEN LET IT REBOOT COMPLETELY! IT WILL TAKE A FEW MINUTES

For the love of god, please follow the steps in the guide step by step will you?

OR AT LEAST READ THROUGH WHAT PEOPLE ARE TRYING TO TELL YOU!
[Galaxy Tab  Android Development] dannyvanderzande:
That is just what I thought I was seeing that I was doing wrong..

So it turns out I really really reallllyy need glasses because and some more english lessons..

I so didn't read and understand the part 8 good enough and wasted my own.. but worse.. your time as well!

Sorry for all the inconvenience and thanks for all your patience and help, it is now doing the "sexy voice"

Turns out im stupid after all... again, I'm really sorry guys! I hope this at leasts helps someone else with the same stupidity as mine...

These morning shifts do kill my mind after all...
[Galaxy Tab  Android Development] __coma__:
chrome to phone cannt aut :(( why ?
[Galaxy Tab  Android Development] oddball69:
Well Well, we all have our bad days, glad to help after all :D

Keeping my thumbs that all will go well now.
[Galaxy Tab  Android Development] oddball69:
Could you please explain a little bit more, what Rom, what version of chrome,

wich steps did you go thru etc.....
[Galaxy Tab  Android Development] clankman:
Woohoo, excellent advice my friends, volume is great now!!
[Galaxy Tab  Android Development] dannyvanderzande:
Hehehe, It has to go wrong now. Gonna try GPS tweak 2morrow, going 2 bed now..

So.. I might just see you guys 2morrow ;)
[Galaxy Tab  Android Development] __coma__:
rom : jupiter

app : chrome to phone

allways give me unable to conect ! somebody test ?
[Galaxy Tab  Android Development] Alcibiade:
I told you :)
[Galaxy Tab  Android Development] flamand:
Hope this might help someone preparing their GT for a new rom: some useful system data can be saved in Titanium Backup like wifi access point, gmail accounts, bluetooth pairings, browser bookmarks. Open Backup All System Data, deselect all and then choose only the items in green that you might need. Of course, do not run the batch operation with everything selected because that will cause problems.