ok so i definitely f-ed up my phone, i flashed the "fascinate" fw that samsungfirmwares.com had. little did i know that it was the us cellular fascinate not the verizon fascinate fw! i didnt even know us cellular was getting the fascinate! so is there no pda file for the verizon fw cuz the us cellular fw boots but just goes into a fc loops
blazewit said:
ok so i definitely f-ed up my phone, i flashed the "fascinate" fw that samsungfirmwares.com had. little did i know that it was the us cellular fascinate not the verizon fascinate fw! i didnt even know us cellular was getting the fascinate! so is there no pda file for the verizon fw cuz the us cellular fw boots but just goes into a fc loops
Click to expand...
Click to collapse
can you get into adb?
how can u fix by adb??? i did the samething with a vibrant file and all i get is airplane mode...any help will be grately appreciated...i have a samsung fascinate..
trapstarr56 said:
how can u fix by adb??? i did the samething with a vibrant file and all i get is airplane mode...any help will be grately appreciated...i have a samsung fascinate..
Click to expand...
Click to collapse
You get to return it to Verizon. There's no way to fix this, you overwrote modem.bin. Sorry buddy.
trapstarr56 said:
how can u fix by adb??? i did the samething with a vibrant file and all i get is airplane mode...any help will be grately appreciated...i have a samsung fascinate..
Click to expand...
Click to collapse
well, you are toast. STOP FLASHING OTHER ODIN FILES THAT I DID NOT POST!
only my odin files are safe at the moment, there are no ways to fix if you flash another device's odin files.
trapstarr56 said:
how can u fix by adb??? i did the samething with a vibrant file and all i get is airplane mode...any help will be grately appreciated...i have a samsung fascinate..
Click to expand...
Click to collapse
I hate to tell you this, but you're bricked and there is presently no known pda file released that will be able to recover your phone. Hopefully someone will leak the Verizon Facinate pda file but until that time your phone is done.
When I was on my vibrant I made a modem.bin from one of the bml partitions I believe. Not sure how different it is on the fascinate. Anyone tried yet?
Sent from my SCH-I500 using XDA App
It was bml12 on the vibrant I think. You could dd it and then it was flashable through odin. I will try and help but don't want to waste time on something if the devs here already know it won't work...
Sent from my SCH-I500 using XDA App
I downloaded the firmware from samfirmware.com and it does contain a modem.bin file. I wouldn't recommend anyone that is not a developer (with a bricked phone) test it... You can download it here: http://www.megaupload.com/?d=5IUC7UA7 you will need to unzip the file and use the rar file inside in odin. The password to unzip the file is "samfirmware.com" without the quotes.
I didn't test the modem.bin on my phone but looked through it with a hex editor and can verify it is a modem.bin for a cdma phone.... Looks like it's the right file to me... Maybe flash that and then flash the updated one after and see if it fixes your problem.
Does sprint have a fascinate? Here is another line I found in the modem.bin "Current Data Working Mode is SPRINT TEST Bed mode"
P.S. DO NOT FLASH THIS
Sent from my SCH-I500 using XDA App
Dude don't be telling people or giving them ideas to flash modem.bin.
Folks, that file will brick your phone. No data, no phone, do not pass go, do not collect 200 dollhairs.
Sent from my SCH-I500 using XDA App
Did you read my post?
Only flash if your phone is already broken.
We can't possibly make progress without people testing fixes on their already broken devices...
Sent from my SCH-I500 using XDA App
youneek said:
Did you read my post?
Only flash if your phone is already broken.
We can't possibly make progress without people testing fixes on their already broken devices...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Did you read mine? First of all, most people on these boards do not truly know what is broken and what is not, what is bricked and not.
So you telling them only to try if your phone its broken...think about it!
Secondly, I know for a fact it will brick you. We keep abreast of these things in irc.
Sent from my SCH-I500 using XDA App
This is xda... This is where developers come to share their ideas. Its also the development section.
If your phone is bricked and you are willing to help progress development for the fascinate, pm me.
Sent from my SCH-I500 using XDA App
youneek said:
This is xda... This is where developers come to share their ideas. Its also the development section.
If your phone is bricked and you are willing to help progress development for the fascinate, pm me.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Wow....classy.
Have any "DEVELOPERS" with a truly bricked device tried flashing partitions using bml unlock yet or redbend? bml12 is only 512 in size where its 12800 on galaxy s so modem.bin is not there. I know if you flashed over bml3 on galaxy s you lose your radio because you overwrite your imei (nv_data) and /efs. I don't see anything in /efs on the fascinate...
Can anyone not on the latest update do "cat /proc/partitions" and we can compare sizes to help narrow it down.
It may also help if someone who has broken their radio could also post so we have all 3 results somewhere...
Sent from my SCH-I500 using XDA App
This is the result from a working fascinate on the DI01
139 0 513024 tfsr0/c
139 1 256 tfsr1
139 2 256 tfsr2
139 3 10240 tfsr3
139 4 1280 tfsr4
139 5 1280 tfsr5
139 6 5120 tfsr6
139 7 7680 tfsr7
139 8 7680 tfsr8
139 9 329216 tfsr9
139 10 113664 tfsr10
139 11 35840 tfsr11
139 12 512 tfsr12
179 0 1953792 mmcblk0
179 1 225280 mmcblk0p1
179 2 196608 mmcblk0p2
179 3 131072 mmcblk0p3
179 4 1400824 mmcblk0p4
179 8 15693824 mmcblk1
179 9 15693823 mmcblk1p1
137 0 513024 bml0/c
137 1 256 bml1
137 2 256 bml2
137 3 10240 bml3
137 4 1280 bml4
137 5 1280 bml5
137 6 5120 bml6
137 7 7680 bml7
137 8 7680 bml8
137 9 329216 bml9
137 10 113664 bml10
137 11 35840 bml11
137 12 512 bml12
138 3 6400 stl3
138 6 1280 stl6
138 9 319488 stl9
138 10 108544 stl10
138 11 32000 stl11
Sent from my SCH-I500 using XDA App
I Really don't know much about android dev but maybe this will help
http://forum.xda-developers.com/showthread.php?t=785033
put someone in the right direction
As i was the first to truly brick my fascintate (on day one) i did all i could to make sure that it wont happen again to other peoples fascinates. I made odin restore files for the partitions that were correct, but was never able to get the modem.bin dd'd from the phone, at least not the correct one.
The link that was posted earlier in this thread for people to try to flash is a USCC alpha leak, and will brick your phone partition, with no way of recovery at the moment. So do not flash, it wont fix anything and will just break stuff.
As for this being XDA and the dev section of the forums, well, XDA is overrun by noobs now, and we do not have a very good mod here in the fascinate forum, so try to keep information that you *think* might fix something down to a minimum. If you have an idea and would like to run it by some other devs please come by #samsung-fascinate on freenode, we would love to hear more from other devs, but most of the ideas that people post on here were tried within the first week.
Almost had the same problem. Flashed something to the pda section and broke the modem. So I removed all signs of rooting and sent it to samsung. Works now. Either take it to verizon or send it to samsung.
Sent from my SCH-I500 using XDA App
i dowloaded a rom that i thaght was stock in now i see a vibrant splash screen...how do i get it off so i can send back to samsung??
Related
http://www.addictivetips.com/mobile...axy-s-gt-i9000-to-android-2-2-froyo-download/
Ok first off this is what I used to create the problem I have right now.
I was able to get it to "install" and start up but it just keeps boot cycling on the boot screen.
So, I was going to go back to stock and then go back up to 2.2 leak for US.
Well... That didn't happen. Instead whenever I use Odin, it gets to boot.bin then crashes, except when I try to re-flash from the said above link ROM. Then it just does what it did before, boot screen cycle.
So, question is, is my phone bricked or is there a way for me to fix it.
YES I HAVE READ THIS: http://forum.xda-developers.com/showthread.php?t=773032
I've done everything exactly and like I said, Odin crashes on the boot.bin install every time.
Did adding the modem screen up the process?
Also, I know that my .tar files work because I used them prior to this problem without any problems at all.
Thank you
EDIT:http://www.talkandroid.com/23911-android-2-2-1-xxjpu-rom-from-kalpik-gives-galaxy-s-some-pep/
actually I lied, I got my rom from the link here and followed the instructions on the other site. ... I think, ugh I've been working on it for too long now.
Try putting the file in Phone instead of PDA
Follow this thread exactly, battery out and sd card out, PIT file and repartition:
http://forum.xda-developers.com/showthread.php?t=1052813
What?? Why is this thread up here?
Leaked 2.2 for the i9000?
Sent from my SPH-D710 using xda premium
squshy 7 said:
What?? Why is this thread up here?
Leaked 2.2 for the i9000?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Im pretty sure hes using the wrong tar if he has an epic and not a i9000..
Sent from my SPH-D700 using XDA App
Verizon has tried to ota me 3 times today, each failed with an error about fail to install....DI01 to EA 28. I assume this fail is because of not having 05 or 09 and that Im rooted.
I have Odin, the 05, 09 files, CWM green and am running titanium bu Pro. Anything else I need I can search the forum and download.
Any advice on the quickest,hassle free update or some new approach to try ? I kept it debloated but stock since the performance was fine and battery life was amazing at 21 hours. I skipped the dl30 on some advice because of enterprise email use.
Thx in advance
Sent from my SCH-I500 using XDA App
If you don't mind being rooted, and you don't want bloat, then you should definitely check out the EB01 and SuperClean setups.
They're already at 2.2 (EB01 modem required), even before Samsung has figured out how to do some proper coding.
Just saw that ea28 is an emergency call fix. Eeh...... I assume that I can go 01 to 09 then to the froyo eb01, but not skip 09 ? I can do cwm green to red at the same time
Sent from my SCH-I500 using XDA App
You don't have to upgrade through the different revisions. If you can use Odin the easy way is to Odin eb01 with root and CWM in the developer forum.
archalon said:
Just saw that ea28 is an emergency call fix. Eeh...... I assume that I can go 01 to 09 then to the froyo eb01, but not skip 09 ? I can do cwm green to red at the same time
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Sent from my Super Clean 2.4 Froyo - Voodoo - Fascinate!
Thanks for the clarification, will give it a shot tomorrow
Sent from my SCH-I500 using XDA App
Howdy!
(sorry... guess Stampede is getting to me...)
I am looking for a Bell Vibrant (Samsung Galaxy S i9000M) expert in the Calgary AB area.
I have successfully rooted, installed custom ROMs and then "bricked" two (yes, 2) i9000M phones. Both times, I "bricked" when using ODIN.
Yes, I had researched how to use ODIN before using it... trading weeks of my "life" for the said pearls of ODIN wisodm . I've obviously missed something important, have very bad karma, or I am just an idiot...
After "ODINing", both phones ended-up looping at the SGS Logo. I have tried re-flashing via ODIN many times, always with the same result. I can get both phones into "download" mode (i.e. the yellow triangle screen).
Anyways, I am hoping to find a local expert who is willing to meet me somewhere (library???), look at my phones and confirm:
1. My SD cards have crashed; OR
2. I am a uber noob idiot;
I am also hoping that if #2 is proven the case whether the charitable expert individual might suggest a way and/or help me to fix these expensive plastic paper weights.
So, any charitable local experts willing to help-out an unlucky moron?
t.
What version are you flashing via odin?
you'll most likely have to take them in for warranty repair
@ BottleB:
I tried flashing JH2 (Stock Bell Vibrant ROM???) and 512.pit.
I had original installed CM 7.1 RC1 (via CM wiki method). Everything work awesome.
I decided to try some OC'ing, and flashed the Glitch v10 kernel... with spectacular speed results! Unfortunately, post Glitch flashing, SMS would receive but not send. Researched possible causes and cures for this, could not find any, and decided to revert to stock and try again...
... and here I am.
@graison:
I bought these i9000M's "used" off Kijiji (HATE contracts!). Both worked fine until ODINing.
As such, Bell won't "warranty" these devices (tried with the first one).
I have no problems paying for repairs... if the cost is reasonable. Any ideas/suggestions on the "how's and where's" I can go about trying this?
They most probably had lagfix installed which was not disabled when reflashed to stock. You need to flash the rfs...bin file (i'll upload it later tonight for faster accessing). I found the fix here on xda under a thread on bricked phone.
The lagfix change the filesystem used by the phone. Stock firmware is only compatible with the RFS filesystem. Also, i recommend that you flash KC1 instead oh JH2. Froyo is way better than eclair.
Sent from my GT-I9000M using Tapatalk
Found the fix
Here is the link http://forum.xda-developers.com/showthread.php?t=984140
Sent from my GT-I9000M using Tapatalk
urself25 said:
Found the fix
Here is the link http://forum.xda-developers.com/showthread.php?t=984140
Sent from my GT-I9000M using Tapatalk
Click to expand...
Click to collapse
+1
Pretty sure thats the problem. You flashed stock kernel on a EXT4'ed filesystem.
@urself25,
Ah-ha... I have a feeling that you are right, and that I did miss something CRAP!
I await your upload on bated breath... in the mean time, I will search the million posts for the fix you mentioned.
ooops... you beat me to my response.
Tell us how it went when you'll try the RFS fix.
Tried the RFS fix as per the instructions in the link.
After rebooting, both phones go into a SGS start-up screen loop.
Downloading ODIN files right now (JVE - Gingerbread???). I will try and reflash and let you know how it goes.
I'm in Airdrie, don't flash gingerbread! Sell me both phones for $100. Or search for the "trick to unbricking my sgs" thread. It worked for me. Though I am worried that because they were on Eclair firmware, they may be dead if they never got the bootloader update. I repeat, DO NOT FLASH GINGERBREAD!
Sent from my GT-I9000 using XDA Premium App
try a deodexed KC1 (current firmware for Bell Canada) firmware from [Ramad]
Using ODIN -- use a 512.pit file, re-partition ticked, Bootloader Update (just in case), and put PDA -> PDA, PHONE -> PHONE, etc.
http://forum.xda-developers.com/showthread.php?t=948790
IF it takes you to android recovery 2e or 3e (i cant remember), do a factory reset/cache wipe, and even format sd if you want. it SHOULD work (i just did this too and it worked mint.
Holy crap! It's near 4:30 a.m., and I FINALLY restored/recovered my two phones! Truth be told, I spent half the night screwing up my phones WAY worse than they were ... and the second half of the night cleaning up my mess
@urself25 & @BottleB - I can't say definitively whether or not your link really helped me any... but it definitely put me on the right path. Thanks a lot boys!
@xWarMachine04 - Thanks for the directions and link! I *kinda* went that route in a round-about-way... I just wished I would have check my post and found your reply 4 hours ago! Regardless, my gratitude.
@hansonator - Thanks but no thanks; for $100, I'd use my bricked phones as door stops. REGARDLESS, I do thank you for your gingerbread warning. I did have problems with gingerbread, and (successfully) shifted to froyo on your recommendation. Thanks dude!
All's well that ends well...
- t.
Most probably the firmware didn't install properly because fo the problem RFS problem. A fresh reinstall of the firmware with bootlader finally fix the problem. Glad everything worked out for you.
I'm in Calgary. But I'm hardly an expert. I think you've gotten further than I have.
So I have nothing to contribute to this thread. I'll see my way out.
Glad u got your phones up and running! Good thing is you probably learned a lot during that night!
Sent from my GT-I9000 using XDA Premium App
BottleB said:
Glad u got your phones up and running! Good thing is you probably learned a lot during that night!
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
~~~~~~
Learned a lot? No kidding...
Why is it that the biggest/best lessons always have to be soooo painful???
I must admit that my opinion of ODIN has sure changed; it's a pretty slick piece of software when it works right (i.e. when you have half a clue about what you are doing)!
@urself25 - It wasn't so much a firmware installation problem, as much as the SD card file format (like you suggested in the first place). I kept getting a message along the lines of "can't mount sd; storage not ready... blah blah blah... file format blah blah blah...". I did have to do a complete reinstall (PDA, Phone/Modem, CSC) WITH repartition... and on the second phone, a Bootloader update. Didn't do the repartition in the first place because 95% of the threads out there advise against it. Anyways, my solution was pretty much @xWarMachine04's approach/solution.
Unfortunately, I have developed the "randomly self-invoking" back button problem on the second phone. Fortunately, there seems to be an easy fix for that... but that's what I thought at the beginning of this journey!
Again, thanks everyone!
- t.
Now if you want to flash gingerbread it should be OK. I only advised against it because the phones were bricked. Good to hear you got it sorted out.
Sent from my GT-I9000 using XDA Premium App
davanw said:
I'm in Calgary. But I'm hardly an expert. I think you've gotten further than I have.
So I have nothing to contribute to this thread. I'll see my way out.
Click to expand...
Click to collapse
i'm in Calgary too, but i am no expert either... however i have been able to upgrade my phone from froyo (after taking my i9000m to market mall due to the internal card dying back in December), to gingerbread.
First went with Darky's 9.5... then upgraded to 10 and had NO issues with GB. I'm on GB still using the F1 Rom V9 now and love this.
For the OP: Glad to see you were able to fix both of your phones! Congrats... definitely no easy feat!
I'm posting this for anyone who wants to root their device personally.
I apologize to anyone who feels like it shouldn't be posted.
All credit goes to qbking77, chris41g, mkasick, drockstar and all those who were involved.
Step 1...........How to Root and Clockworkmod the Samsung Epic 4G on EI22 EL30 Gingerbread
Step 2...........How to root the Samsung Epic 4G on Froyo and Gingerbread
You can use this recovery in place of the acs recovery if you prefer...........cwm-5.0.2.7-epic4g.tar.md5 tar flash for odin
Can the Sprint Samsung Epic 4g on gingerbread 2.3.6 be rooted?
Hello to anyone who knows about rooting. I work in medicne so I can figure out anything with the human body but not with rooting my Samsung epic on gingerbread 2.3.6. I have tried different developers, different sites, and read till I went crazy. The lingo gets old. It would be like me talking to the common public about the interpetation of hemodynamic readings and congestive heart failure. Anyhow, I rooted my epic 4g before it automatically upgraded to gingerbread...then it froze...I researched and unbricked it with a program everyone said did not work...but it worked to unbrick my phone even though it was supposed to root my phone...it just reset it to where it was usable again. When I try to go to certain websites for rooting files to download...they seem to be missing...hmmmm. So again, can the samsung epic 4g on gingerbread 2.3.6 be rooted? If it can, please direct me to some site...so far...I have tried about 5 different sites...no luck. It is also very hard to find anything specific on gingerbread 2.3.6 on rooting...alot of info. on the other versions.
imuscle said:
Hello to anyone who knows about rooting. I work in medicne so I can figure out anything with the human body but not with rooting my Samsung epic on gingerbread 2.3.6. I have tried different developers, different sites, and read till I went crazy. The lingo gets old. It would be like me talking to the common public about the interpetation of hemodynamic readings and congestive heart failure. Anyhow, I rooted my epic 4g before it automatically upgraded to gingerbread...then it froze...I researched and unbricked it with a program everyone said did not work...but it worked to unbrick my phone even though it was supposed to root my phone...it just reset it to where it was usable again. When I try to go to certain websites for rooting files to download...they seem to be missing...hmmmm. So again, can the samsung epic 4g on gingerbread 2.3.6 be rooted? If it can, please direct me to some site...so far...I have tried about 5 different sites...no luck. It is also very hard to find anything specific on gingerbread 2.3.6 on rooting...alot of info. on the other versions.
Click to expand...
Click to collapse
Yes it can...that's why this how too is right above you if you would like me to do it for you remotely through team viewer I would gladly
Sent From My SPH-D700 Running Android 4.0 :sly:
imuscle said:
Hello to anyone who knows about rooting. I work in medicne so I can figure out anything with the human body but not with rooting my Samsung epic on gingerbread 2.3.6. I have tried different developers, different sites, and read till I went crazy. The lingo gets old. It would be like me talking to the common public about the interpetation of hemodynamic readings and congestive heart failure. Anyhow, I rooted my epic 4g before it automatically upgraded to gingerbread...then it froze...I researched and unbricked it with a program everyone said did not work...but it worked to unbrick my phone even though it was supposed to root my phone...it just reset it to where it was usable again. When I try to go to certain websites for rooting files to download...they seem to be missing...hmmmm. So again, can the samsung epic 4g on gingerbread 2.3.6 be rooted? If it can, please direct me to some site...so far...I have tried about 5 different sites...no luck. It is also very hard to find anything specific on gingerbread 2.3.6 on rooting...alot of info. on the other versions.
Click to expand...
Click to collapse
there is a thread that tells you a 3 step method. if you wanna flash another rom then here is what I did. Download the rom you want and put on the sd card. download odin if you do not already have it. download cwm-5.0.2.7-epic4g.tar.md5. open odin uncheck every thing even reboot. then click pda put the cwm.tar into the pda. make sure your phone is in download mode. by holding the #1 button on the keyboard and the power button. plug the phone in to the usb. a yellow com box should pop up. hit start it shouldn't take long but it will complete and the phone will still be on. unplug your phone and take the battery out. put the battery back and turn on using the 3 finger method. ( vol. down, camera and power button) then wipe data, wipe cache, go into advance and wipe dalvik. press the back button click then click install zip from sdcard. click choose zip from sd card and then choose your rom and install that should be all. if you want to stay stock and just be rooted you need to download superuser.zip the link is found in the first video. you do the first part the same but instead of wiping every thing you go start into install zip and then choose the super user zip. reboot your system. then you have to go into the root explorer and delete a file but I cant remember the file name. but then you turn your phone off and then you have to odin cwm again. then you will be rooted. i will edit this when i can remember the file name unless some one beats me to the punch. i hope this helps if not pm me and i will try to help i am going to be flashing back to stock and re rooting to day so..
Thanks...I will try it again.
imuscle said:
Thanks...I will try it again.
Click to expand...
Click to collapse
I could not find that file that you are suppose to delete but if you odin cwm. Then flash super user in cwm. Boot up. Go into your root explorer go ino system/etc/ it should say install.recovery.sh. I believe
Sent from my SPH-D700 using xda premium
Links to all files needed are in the descriptions under the videos.....and the videos show which ones you need.
Sent from my SPH-D700 using xda premium
Root epic 4g
to big goron, would u b willing to do the same for me? I have teamviewer.
debage39 said:
to big goron, would u b willing to do the same for me? I have teamviewer.
Click to expand...
Click to collapse
You should pm him
Sent from my SPH-D700 using XDA Premium App
debage39 said:
to big goron, would u b willing to do the same for me? I have teamviewer.
Click to expand...
Click to collapse
No problem pm me the id and password and ill root ya in no time
Sent From My SPH-D700 Running Android 4.0
I wanted to give thanx to big Goron aka uber for all his time and effort helping me with my epic. Problems and upgrades. Thanx for all ur help.
Sent from my HERO200 using XDA
Yes! A big thanks to Uber (Big Goron) for helping out everywhere!
Sent from my PantechP4100 using xda premium
Sent from my SPH-D700 using xda premium
notsosmrtgeek said:
I could not find that file that you are suppose to delete but if you odin cwm. Then flash super user in cwm. Boot up. Go into your root explorer go ino system/etc/ it should say install.recovery.sh. I believe
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
i havent rooted stock gb. so forgive me. but is system/etc the correct path for the file that needs to be deleted? also better to necro rather than make a new thread for this.
I never deleted that file. I just odin'd cwm5 with reboot unchecked, then unplugged cable, poppef battery out and in and flashed a ROM. That file install-recovery.sh is still on my phone and in the directory you specified.
Sent from my PantechP4100 using xda premium
jbadboy2007 said:
i havent rooted stock gb. so forgive me. but is system/etc the correct path for the file that needs to be deleted? also better to necro rather than make a new thread for this.
Click to expand...
Click to collapse
You don't need to unless you plan on staying stock. Otherwise just flash clockwork mod boot into it and flash a custom rom.
Sent From My Sprint Galaxy Nexus via XDA Premium
ÜBER™ said:
You don't need to unless you plan on staying stock. Otherwise just flash clockwork mod boot into it and flash a custom rom.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
The phone will remain stock or I would just flash fc09 deoxed. It's for my wife I might in the future upgrade her but this is her first android so I'm trying to go slow with it and not barrage her with too many changes.
jbadboy2007 said:
The phone will remain stock or I would just flash fc09 deoxed. It's for my wife I might in the future upgrade her but this is her first android so I'm trying to go slow with it and not barrage her with too many changes.
Click to expand...
Click to collapse
Qbking77 video on youtube I believe hasa link to a kernel (mostly stock, only the key skip fix added i believe) that you can odin to make recovery stick on stock...
flastnoles11 said:
Qbking77 video on youtube I believe hasa link to a kernel (mostly stock, only the key skip fix added i believe) that you can odin to make recovery stick on stock...
Click to expand...
Click to collapse
Isnt that a ei22 kernel though from my memory there is not a fc09 kernel of that sort.
i used this kernel on my friends epic, who wanted to stay stock fc09
ShadowKernel-FC09-v1.0.1
Hi all..
I've searched everywhere and haven't found any info on anyone developing on this tab yet. I know that not alot of people probably own one or plan on owning one, but for the people that do have this tab it would be great to see a proper root and maybe a port of CM10.
Has anyone heard of anything about this tab getting some love?
Also thanks to all the devs and everything they do for the community!
Nexttonomy
nexttonomy said:
Hi all..
I've searched everywhere and haven't found any info on anyone developing on this tab yet. I know that not alot of people probably own one or plan on owning one, but for the people that do have this tab it would be great to see a proper root and maybe a port of CM10.
Has anyone heard of anything about this tab getting some love?
Also thanks to all the devs and everything they do for the community!
Nexttonomy
Click to expand...
Click to collapse
SuperOneClick can usually root just about anything.
lucidlust said:
SuperOneClick can usually root just about anything.
Click to expand...
Click to collapse
Thanks for the reply, but I have tried this already and it just doesn't seem to work. I've tried it multiple times and I think its just an outdated root method. I wish it did work though!
Thanks again for the suggestion though
Nexttonomy
D'Anklaud said:
http://forum.xda-developers.com/showthread.php?t=1788625 , This is the rooting method all use for the Gallaxy Tab 2 7 (including me,obviously), next - http://forum.xda-developers.com/showthread.php?t=1791975 is Cyanogenmod 10 , Enjoy
Click to expand...
Click to collapse
Did you test this on the verizon model sch-i705? or do you have one of the wifi only models?
That new tab needs a dev forum
God I hope someone figures it out.
Love the device, but without the rooting ability we get no sms via google voice. :crying:
Snipecat said:
Love the device, but without the rooting ability we get no sms via google voice. :crying:
Click to expand...
Click to collapse
SMS via google voice works great on mine (stock Verizon SCH-i705).
I'd love if there was a root available too. Almost tempted to try the GS3 debugfs root but i'll probably brick it.. lol Are any devs interested in rooting? Or at least pointing some of us in the right direction to get started finding a root exploit? I don't mind tinkering when I have free time. I'm no developer (php only) but i know the basics of OO programming, scripting, and linux and would be willing to supply some time. i just need to know where to start
I'm glad to see there are a few ppl out there that have this tablet!
Hopefully someone can help out MrHyde03 with a starting point on how to come up with a possible root method..
Nexttonomy
I'm trying to find anything I can on how to go about finding exploits but without much luck..
You're right mighty, got it today.
*may* be on to something using the debugfs method used for the gs3 and several other devices. I just need to grow the cajones to try it lol. I'll post more later
MrHyde03 said:
*may* be on to something using the debugfs method used for the gs3 and several other devices. I just need to grow the cajones to try it lol. I'll post more later
Click to expand...
Click to collapse
That is great news MrHyde! keep us updated on what you figure out!
Nexttonomy
GREAT NEWS!
Found a root method that works! Posted it over in the Dev forums!
DO IT!
http://forum.xda-developers.com/showthread.php?t=1885558
MrHyde03 said:
GREAT NEWS!
Found a root method that works! Posted it over in the Dev forums!
DO IT!
http://forum.xda-developers.com/showthread.php?t=1885558
Click to expand...
Click to collapse
THIS WORKED!
Thanks a lot for finding this and testing this method out for us MrHyde.. I appreciate it
Now that we have root maybe someone who develops roms might be willing to get us a working custom recovery and perhaps some CM10!
Nexttonomy
nexttonomy said:
THIS WORKED!
Thanks a lot for finding this and testing this method out for us MrHyde.. I appreciate it
Now that we have root maybe someone who develops roms might be willing to get us a working custom recovery and perhaps some CM10!
Nexttonomy
Click to expand...
Click to collapse
No problem! Glad I could finally contribute to XDA even if its just a little.
I've been looking into that as well. However, I don't think the stock firmware has been released yet and I can't figure out how to dump the ROM on these Samsung devices. Even then.. I fear the bootloader may be locked as it was on the sgs3 until someone found a way to unlock it. If I could find a way now to dump the tablets firmware I could take a peek lol. They say you need knowledge of c/c++ and java to build ROMs n such. I have SOME experience with all three.. I'm fairly proficient in php and that's based on C so who knows.
I found all the necessary partitions. I'm extracting them using dd right now.
If I understand this correctly, without an official release from vzw or samsung, these will be required for any modifications.
If anyone is curious..
Code:
mmcblk0p1 /modem
mmcblk0p5 /aboot
mmcblk0p7 /boot
mmcblk0p12 /modemst1
mmcblk0p13 /modemst2
mmcblk0p14 /system
mmcblk0p15 /data
mmcblk0p17 /cache
mmcblk0p18 /recovery
The partitions on this device are conveniently the same as the GS3. I'm not sure about the wifi tab 2, though.
Using builder.clockworkmod.com, i uploaded my stock recovery and got a cwm back... I haven't tested it yet, kinda unsure if I want to or not. Either way, here's the link to it if any of you want to try. If ya'll are even still reading this thread.
CWM Recovery IMG
*RECOMMENDED*
Backup your own recovery!
Code:
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery.img
Move it to SD Card and use the following commands:
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
reboot recovery
If it doesn't work, you **should** be able to use ODIN to flash the original.
STOCK recovery
If this works, i'll start a new thread.
** USE AT OWN RISK! **
EDIT: Flashed the recovery.. id didn't work. Before it would even load cwm it rebooted the device. Good news is it rebooted fine and I was able to use adb to reload the stock firmware and all is good. I guess the hunt is continuing.
Hey MrHyde..
I'm still following... I appreciate all the hard work your putting into this tab.. I only wish I could help out more than just giving you words of encouragement lol
Nexttonomy
@MrHyde03
I will try to modify the stock recovery to add CWM recovery key to /res/keys, so the stock recovery will accept an update.zip signed by Google's testkey. I also need cache.img from stock firmware to extract the update-binary and learn the updater-script, how it mount /system partition.
EDIT:
Attached a modified version of SCH-i705 recovery and an update.zip (SCH-i705_root-signed.zip) for rooting. Please remember, I do not have and do not have an access to SCH-i705, try this at your own risk!
The recovery is a modified of STOCK_recovery.tar.md5 uploaded by MrHyde03. SCH-i705_root-signed.zip use update-binary extracted from Galaxy Tab 2 7.0 4.0.4 XXBLE3 cache.img. The partition mapping base on /etc/recovery.fstab information.