[Q] Restoring unrooted Galaxy Tab to stock - Galaxy Tab Q&A, Help & Troubleshooting

I think I have done something quite stupid. I have a T Mobile Galaxy Tab (SGH-T849) running Froyo. It was completely stock and I had not rooted it.
I was curious to try Cyanogenmod, so I followed the instructions under "Installing the ClockworkMod Recovery" here:
wiki.cyanogenmod.com/wiki/Samsung_Galaxy_Tab_(GSM):_Full_Update_Guide
Even though the directions said it was for a Galaxy Tab on the stock 2.3 release, I forged ahead installed the ClockworkMod recovery image using Heimdall.
The tablet now does not get past the T-Mobile boot screen. I did not backup the original kernel.
I am not normally this stupid! I don't know if I can go to stock Gingerbread using the overcome.net guide as my tablet was not rooted.
Is there any way to restore my original kernel and start again?

I don't think you need to root.
You can use overcome method.
I believe Overcome only ask you to root first to make sure you don't have protected bootloader and to backup using Titanium Backup.
You don't need all that now.
Just go ahead and flash GB Stock Safe
using heimdall will be:
1) naturally unpack the GB_Stock_Safe_v5.tar
2) go to download mode
3) heimdall flash --repartition --pit ./gt-p1000_mr.pit --factoryfs ./factoryfs.rfs --cache ./cache.rfs --dbdata ./hidden.rfs --primary-boot ./boot.bin --secondary-boot ./Sbl.bin --param ./param.lfs --kernel ./zImage
4) at this point you can reboot to the stock rom.
I like heimdall a lot compared to Odin.

Unfortunately, that did not work. I get this error:
Uploading PIT
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...
And then the tablet just displays the T-Mobile screen. Is there something else I can try?

what if you do it without pit ?

Doing this with the --verbose flag gives this:
Uploading PIT
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.
ERROR: Failed to confirm end of PIT file transfer!
PIT upload failed!
Ending session...
Rebooting device...
I am doing this on a Mac and I see that this is a problem with the OS X version of Heimdall. I have an old Windows XP machine I can try to use.
Let me try that before omitting the PIT file.
Thanks!

The PIT file loads on Linux, but the kernel doesn't:
98%
File Part #59... Response: 0 0 0 0 3B 0 0 0
100%
ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
Rebooting device...
Re-attaching kernel driver...
I'll boot up the old windows box and try that next.

BTW, don't use latest heimdall (1.3.2?)
use 1.3.1 I think
Edit: sorry, at in Mac use 1.3.0
http://forum.xda-developers.com/showthread.php?t=1655689&page=6
my ubuntu I have 1.3.1

This looks promising! I installed heimdall 1.3.0 on my Mac and was able to install everything successfully, then the tablet rebooted. It went to the recovery screen and I selected the reboot option.
It's been on the Samsung logo for about 20 minutes now. I don't know how long it will take but I'll let it sit overnight.
Thanks so much for your advice!

Not quite right.
Mine reboot to setup wizard upon flashing.
You did the complete parameters like I put there?
Do wipe all cache and data.
If still no go, reflash.
Sent from my GT-P1000 using xda app-developers app

Okay, I think that did the trick! I wiped the data and cache, and now it looks like everything is working! I will have to flash the T-Mobile modem file as well.

priyana said:
Not quite right.
Mine reboot to setup wizard upon flashing.
You did the complete parameters like I put there?
Do wipe all cache and data.
If still no go, reflash.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Seriously, I think you should be paid by Samsung Customer Service (Or Technical Support). You beat most of us on attending these problems! we P1000 users can't thank you enough!

just helping others
imagine if we don't help them out. The SGT7 will be collecting dust.

Priyana, if it hadn't been for you, my next step would have been shipping my Tab off to Samsung to be reset! As yappoe said, I can't thank you enough!
Something odd - even though I wiped the caches, and did a data/factory reset, much of my user data was on the tablet, such as pictures and some books I had downloaded. This was fortunate as I hadn't backed anything up, but it was curious.
I will make a backup before I work up the courage to flash ICS! Thanks again!

Hmm, I have never seen data survived a format.
However, having said that, I have proven to myself that when I did restock from AOKP mtd from, back to gb-stock safe using heimdall with pit file, and my internal SD intact.
People told me flashing with pit file ensure everything on internal SD is wiped out because it was repartitioned, but definitely not mine.
But, I heimdall flash and immediately flash overcome kernel without booting into the gb rom.
Sent from my GT-P1000 using xda app-developers app

Related

[Q] Please Help CM7 error

I'm desperate I just followed the steps given for installing CM7:
# Make sure your phone is fully charged! Update process will take some time.
# Make sure there's enough free space at your internal sdcard (200MB)
# Make sure you've not disabled HSPA by using the dialer code *#301279#
# Download following files from sourceforge: Captivate | Galaxy S | Galaxy S B | Vibrant
- DEVICE-efsbackup.zip
- cm7-DEVICE-initial-kernel.tar
- cm7-DEVICE-initial-XXXXXXXX.zip
# Copy following files to your internal sdcard
- DEVICE-efsbackup.zip
- cm7-DEVICE-initial-XXXXXXXX.zip
# Flash a kernel which comes with clockworkmod-recovery using odin: Captivate | Galaxy S | Vibrant
# Reboot into recovery using 3-button-combo and apply DEVICE-efsbackup.zip.
- Don't use "reboot recovery" command or other shiny things to do this!
# Flash cm7-DEVICE-initial-kernel.tar as pda using odin without auto-reboot and without re-partition
after this when i try to install zip from sd card i get the following error:
assert failed: getprop("ro.product.device") == "galaxys" || get prop("ro.build.product") == "galaxys" || getprop("ro.product.board") ++ "galaxys"
E:Error in /sdcard/update-cm-7-03122011-NIGHTLY-GalaxyS-signed.zip
(Status 7)
Installation aborted
I'm still sitting in CWM scared to do anything! Tried to restore backup but that failed too
What do i do??
Any help would be extremely appreciated!!
Martin
Looks like you didn't install the initial CM7 Zip, if it's not on your sd card already you should be able to push it with adb then install., after that try and install the nightly.
Which one is the initial cm7?
Should be called "cm7-galaxys-initial-20110304.zip" if you didn't download it, http://sourceforge.net/projects/teamhacksung/files/galaxys/
Also you may have to go through the whole procedure again. Give it a try though.
Mabee said:
Which one is the initial cm7?
Click to expand...
Click to collapse
http://sourceforge.net/projects/teamhacksung/files/galaxys/cm7-galaxys-initial-kernel.tar/download
Thats the initial kernel to get CWM it has to be flashed thru Odin. then when that is done you flash the rest thru CWM (recovery)
He flashed the kernel, missed out the initial cwm zip though.
so should i install nexus drivers (since my phone doesn't have drivers right now) and just start from the beginning or push the initial cm7 file to the phone ( I have never pushed a file before so unsure how it's done)
Really appreciate you guys helping me
Btw i dowloaded the initial zip just need to get it to my phone now
You'll need to get the android sdk, or just adb.
Assuming you're using windows:
Connect your phone, open a command prompt on your pc and navigate to where you saved adb. Then type "adb devices" If it finds something then you can use "adb push cm7-galaxys-initial-20110304.zip /sdcard"
cm7-galaxys-initial-20110304.zip will need to be in the same folder on your PC as adb for this to work.
what do i do with my phone to push the file i have installed sdk and adb but my phone is sitting in cwm still
Yeah, adb should work in cwm. If it doesn't then you'll have to restore to stock and begin process from beginning.
I managed to push file and installed cm7 initial zip sucessfully. did a factory reset / data wipe and rebooted
so it's been stuck on the stock galaxy s loading screen for some time now not really sure if i should do something else
Double post
The text or the animation?
Just the text
can i just start from the beginning and flash CF root?
I'd go back to stock firmware first. Use JPC with 3 files 512.pit and repartition checked.
I'm sorry for being retarded but i don't know how to do that. i am immensely thankful for all your help so far!
Ok, first you need to get XXJPC firmware here. It should extract to 3 files, pda, modem and csc. Load them into odin (one for each box on the right) and select a 512.pit file for pit (might have come with odin otherwise download it), tick repartition. Put your phone in download mode then connect it to your pc. Press start. Wait for odin to say success, then your phone should reboot (it can take a while).
I'm running a european galaxy does that matter or can you flash any stock firmware i remember i wasn't a JPC before i was stock XW somehting
Yeah, it won't matter, I just know JPC contains dbdata which is needed to make sure it restores properly.
btw as i'm waiting for the dl to finish i see it's an exe file is that right? shouldn't it be a rar file?

Device semi-bricked no way to rom zips to sdcard

Hi,
I was attempting to update my P7310 to ICS and have flashed CWM 5.0.2.6 I then attempted to flash the alpha2 ICS release but it started flashing and then the device rebooted. I was able to boot back into recovery but it seems that the whole device fileystem is empty / screwed.
I have tried adb push of a file to /sdcard/ but it fails:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /sdcard/wifi.zip
failed to copy 'p5wifi_galaxian-soup-a2.zip' to '/sdcard/wifi.zip': Not a directory
Is there any way of getting a new rom zip onto the device so that I can then update again through CWM "apply update from sdcard". Can I apply update from any other way?
I can push the file to the device root:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /wifi.zip
1307 KB/s (96366459 bytes in 71.999s)
I can't run adb shell to do stuff either:
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Can I flash something that works through ODIN which still talks to the device..?
Im stuck and have ran out of ideas..any help appreciated
mj_blue said:
Hi,
I was attempting to update my P7310 to ICS and have flashed CWM 5.0.2.6 I then attempted to flash the alpha2 ICS release but it started flashing and then the device rebooted. I was able to boot back into recovery but it seems that the whole device fileystem is empty / screwed.
I have tried adb push of a file to /sdcard/ but it fails:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /sdcard/wifi.zip
failed to copy 'p5wifi_galaxian-soup-a2.zip' to '/sdcard/wifi.zip': Not a directory
Is there any way of getting a new rom zip onto the device so that I can then update again through CWM "apply update from sdcard". Can I apply update from any other way?
I can push the file to the device root:
$ ./adb.exe push p5wifi_galaxian-soup-a2.zip /wifi.zip
1307 KB/s (96366459 bytes in 71.999s)
I can't run adb shell to do stuff either:
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Can I flash something that works through ODIN which still talks to the device..?
Im stuck and have ran out of ideas..any help appreciated
Click to expand...
Click to collapse
You're telling adb to push the file into a zip? Anyways, ADB sadly does not work in our CWM (nor USB mounting as you might have noticed), so the only way you can restore functionality and start again (no erasure of your SDcard contents so don't worry) is to use ODIN back to stock. From there, start again. It could be your download was corrupted (download again), because I could flash it fine, but eventually went back to KJ5 for functionality.
Edit: Check my guide below for ODIN FAQ and how-to if necessary.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
The clockwork I posted in the CM9 thread supports adb.
A bit late for that now though...
kallt_kaffe said:
The clockwork I posted in the CM9 thread supports adb.
A bit late for that now though...
Click to expand...
Click to collapse
Edit: Sent you a PM.
was there a resolution to this issue? i have the same exact problem as the OP.
However, I cannot restore back to stock with ODIN. when writing my system.img.md5 my restore fails.
I know my devices can be fixed! i just have not found my answer yet.
you need to copy the CWM flashable rom into the sdcard:
1st: Install CWM using Odin
2nd: enter CWM and go to "Mount" and mount /system (this will enable the shell)
3rd: now you can use "adb shell" and "adb push" to push your rom into the sdcard.
I remember this thing happened to me once, that the /sdcard directory was not found, but I don't remember how I solved it.
How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...
ellokomen said:
you need to copy the CWM flashable rom into the sdcard:
1st: Install CWM using Odin
2nd: enter CWM and go to "Mount" and mount /system (this will enable the shell)
3rd: now you can use "adb shell" and "adb push" to push your rom into the sdcard.
I remember this thing happened to me once, that the /sdcard directory was not found, but I don't remember how I solved it.
Click to expand...
Click to collapse
suwandiapr said:
How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...
Click to expand...
Click to collapse
Ok, so i'll let you know what my whole problem is. I am not starting a thread yet, because i believe the problem is the same.
I wanted to install overcome's rom on a United States, Galaxy Tab 8.9 WiFi Only. I rooted my devices just fine. The instructions with pictures told me to use ODIN to flash the modified version of CWM. now, in the picture i saw a pit file being used. it was called "android_fastboot_emmc_full_p4_16G_32G.pit". I found the file and I left 'Re-Partition' checked per the picture.
After this, I had no CWM, only downloading mode. I used ODIN to reflash the P7310XXKJ4. I put that in PDA. unchecked re-partition. it failed at writing system.img.md5
stock normal recovery was back, but i had no access to the sdcard, data, or anything else.
I then used ODIN (no more pit files anymore and no more re-partition) to flash the overcome CWM. WORKED.
So now i have access to CWM, but it cannot mount sdcard, data, nothing.
I purchased the sdcard kit so i could see if i could load up a ROM on an external SDcard and flash from there. NO DICE.
I refuse to believe this is over! but I am begging for someone's help.
Tonight, I am going to uninstall the drivers i have on win7. reinstall a fresh copy of KJ4. and see if that works.
I am open to ANY suggestions. I see that others are experiencing this problem, but there is no readily available solution.
wyatt23 said:
Ok, so i'll let you know what my whole problem is. I am not starting a thread yet, because i believe the problem is the same.
I wanted to install overcome's rom on a United States, Galaxy Tab 8.9 WiFi Only. I rooted my devices just fine. The instructions with pictures told me to use ODIN to flash the modified version of CWM. now, in the picture i saw a pit file being used. it was called "android_fastboot_emmc_full_p4_16G_32G.pit". I found the file and I left 'Re-Partition' checked per the picture.
After this, I had no CWM, only downloading mode. I used ODIN to reflash the P7310XXKJ4. I put that in PDA. unchecked re-partition. it failed at writing system.img.md5
stock normal recovery was back, but i had no access to the sdcard, data, or anything else.
I then used ODIN (no more pit files anymore and no more re-partition) to flash the overcome CWM. WORKED.
So now i have access to CWM, but it cannot mount sdcard, data, nothing.
I purchased the sdcard kit so i could see if i could load up a ROM on an external SDcard and flash from there. NO DICE.
I refuse to believe this is over! but I am begging for someone's help.
Tonight, I am going to uninstall the drivers i have on win7. reinstall a fresh copy of KJ4. and see if that works.
I am open to ANY suggestions. I see that others are experiencing this problem, but there is no readily available solution.
Click to expand...
Click to collapse
The thing is, none of the ODIN images (at least the 7310 ones I've seen) have this .pit file since it is not needed at all. The CWM available is just for wiping and flashing. I'm afraid adb does not work. I heard of a Recovery in the CM9 kang thread over at the Development section in which adb works if that's what you want. There are some ODIN links in my guide and all you need to do with the downloaded file is putting the biggest (and only) file in PDA, make sure "F. Reset Time" is clicked and forget about Repartitioning (it is NOT needed in this tab).
nirogu325 said:
The thing is, none of the ODIN images (at least the 7310 ones I've seen) have this .pit file since it is not needed at all. The CWM available is just for wiping and flashing. I'm afraid adb does not work. I heard of a Recovery in the CM9 kang thread over at the Development section in which adb works if that's what you want. There are some ODIN links in my guide and all you need to do with the downloaded file is putting the biggest (and only) file in PDA, make sure "F. Reset Time" is clicked and forget about Repartitioning (it is NOT needed in this tab).
Click to expand...
Click to collapse
I have done this. when i re-flash the odin stock image, i get stuck at the restoration of system.img.md5.
I uninstalled and reinstalled the samsung usb drivers and installed the latest. i've tried different usb ports. i am truly at a loss.
i installed an odin flashable version of CWM 5.0.2.6 (? i think thats the version), but adb was not available on that.
Does adb work on the stock recovery? Do you know where i can find this CM9 Kang thread? do you know if their version of CWM in flashable via Odin? that's the only way i can push anything onto the tablet as of right now.
btw... if i restart the tab unconnected to any USB cables, I get a message saying to reconnect to Kies and perform a recovery. IMHO kies is useless.
I am still stuck. I am open to literally anything not physically harmful to my tab.
Is nvflash an option for fixing this? I've never used it before, but if it can help I would be down.
---------- Post added at 09:49 AM ---------- Previous post was at 09:41 AM ----------
suwandiapr said:
How about this.?
adb push files\your_files /data/media/.
Before that, please mount your /data partition..
Why? Because /data/media/... have the same content with /sdcard/...
Just check it, and tell me if it works...
Click to expand...
Click to collapse
$ ./adb.exe shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
If i push files, they look as tho they are transferring, but i think they are not really making their way their on to the device.
After doing a little prying today at work, I found a .pit file. I read that this contains the partition information for drive.
I downloaded the stock 3.1 image, extracted it, and i found a P5.pit. Perhaps, I can use that PIT file, while keeping Re-Partition checked, and reflash the overcome CWM?
I know others have run into my exact problem and fixed it. there's gottttta be a way.
i will keep posting my progress and/or reading for others' suggestions.
When trying to flash KJ4 , i get the following:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7310XEUKJ4_P7310XXKJ4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img.md5
<ID:0/006> NAND Write Start!!
<ID:0/006> bootloader.bin.md5
<ID:0/006> cache.img.md5
<ID:0/006> hidden.img.md5
<ID:0/006> recovery.img.md5
<ID:0/006> system.img.md5
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then when looking at my galaxy tab screen i see the following:
Code:
Partition size is small! [Bin:173568 > Part:147968] (4KB unit)
WriteExt4Partition: Error to OpenCompExt4![err:0xa]
DownloadPartition_odin: Error to WriteExt4Partition![err:0xa]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0xa]
I have to believe my partition table is all botched.
wyatt23 said:
I have to believe my partition table is all botched.
Click to expand...
Click to collapse
I believe the PIT file you flashed earlier did something to the partition table. I really don't know where did you find that PIT file . I think I saw a PIT file from an Asian ROM for our tabs months ago, but it's not on XDA. Gonna look for it.
EDIT: Found it here. Attached is the PIT file so you don't have to download the whole package (just unzip the file and there it is). I know it is for the 7300 but I don't think partitions are so different between the two models. Try it with your preferred ODIN image and see if it solves the issue.
nirogu325 said:
I believe the PIT file you flashed earlier did something to the partition table. I really don't know where did you find that PIT file . I think I saw a PIT file from an Asian ROM for our tabs months ago, but it's not on XDA. Gonna look for it.
EDIT: Found it here. Attached is the PIT file so you don't have to download the whole package (just unzip the file and there it is). I know it is for the 7300 but I don't think partitions are so different between the two models. Try it with your preferred ODIN image and see if it solves the issue.
Click to expand...
Click to collapse
and should i keep 'Re-Partition' Checked?
---------- Post added at 02:21 PM ---------- Previous post was at 02:12 PM ----------
wyatt23 said:
and should i keep 'Re-Partition' Checked?
Click to expand...
Click to collapse
ehh, so i tried it without re-partition. didn't work. still cannot mount /sdcard.
tried it with repartition checked with clockwork 5.0.2.6 and I'm stuck at the "choose download mode or recovery mode" screen. if i select recovery, the screen blinks.
TO FIX THIS: I can use odin 1.85 to flash KJ4. however, this will fail at system.img.md5. However, stock recovery will be bootable. stock recovery will give me errors saying most of my partitions cannot mount.
I then can use odin to flash clockwork 5.0.2.6 and enter recovery.
the partitions are still botched if i go that route.
OK. so... i don't know what fixed it, but here's how things went down.
i stumbled across this website: http://www.tsar3000.com/Joomla/inde...14:samsung-flashes&catid=55:samsung&Itemid=82
i downloaded the stock odin flashable version of 3.1. i was able to use the stock 3.1 (even tho it said 32G) to get a working copy of android back on.
3.2 just would not work. however, 3.1 seemed to fix the problem of the partitions. then i flashed 3.2 right on top of it right away.
after that, i used odin to flash overcome's recovery and NANDROID!
now, i'm about to run overcome 3.2.
nirogu325, do you develop at all? I think you're up for a donation. thank you for all your help.
Glad to hear you fixed your issue, thought I'd add a few side notes as I had the same problem as you pretty much but fixed it at 3am and went straight to bed and was gonna post this morning.
For my situation I was doing it all on a lenovo T500 so for any1 using one flash with the usb port closest to you, in win 7 there seems to be a difference in this port possibly being the only port with always on charge feature, the drivers handle this port differently.
Install or reinstall drivers with the tab unplugged and only plug it in once your already in download mode.
I used the same pit file posted on the previous page and used the stock 3.1 pda, no csc or modem or bootloader files, would still hang wen other files were included. Re-partition checked. Only use pit file once, later flashes shouldn't require it as you've just rectified you partition table.
Once you got 3.1 on there then continue the 3.2 flashes as you wish and hopefully no more problems.
All done trough odin and please people take your time with these steps, the rom should only take 2-3 mins and if it pauses for more than 1:30, its hung, just press and hold power button leaving everything plugged in and odin open and go straight back into download mode and try again.
I've done this several more times with 8 more roms and havent had an issue with any (all morning). I've broken it on purpose then gone through these steps so that the information is as functional as I can make it.
I know its querky but hopefully this saves someone the anguish we went through.
Sent from my GT-P7300 using Xparent Blue Tapatalk
wyatt23 said:
OK. so... i don't know what fixed it, but here's how things went down.
i stumbled across this website: http://www.tsar3000.com/Joomla/inde...14:samsung-flashes&catid=55:samsung&Itemid=82
i downloaded the stock odin flashable version of 3.1. i was able to use the stock 3.1 (even tho it said 32G) to get a working copy of android back on.
3.2 just would not work. however, 3.1 seemed to fix the problem of the partitions. then i flashed 3.2 right on top of it right away.
after that, i used odin to flash overcome's recovery and NANDROID!
now, i'm about to run overcome 3.2.
nirogu325, do you develop at all? I think you're up for a donation. thank you for all your help.
Click to expand...
Click to collapse
Lol no I don't develop. But I am glad you found the way! That was the objective!
Sent from my SGH-T959.
Hello my honorable SGT colleagues, I managed to roll back from Overcome P7300 v2.3.0 to the Russian v3.1 stock ROM (PDA/CSC/PHONE) flashing it by Odin 1.85 together with p5_0614 PIT mapping table file kindly provided above by Nirogy325, however in my case in attempt to fix modem firmware. All operations including ROM re-partitioning went absolutely smoothly! However to my regret, this has not fix my problem – every ROM (either stock and custom) I used to try do not flash PHONE firmware properly, with basedband version always indicated as “unknown” in the system properties and GSM/CDMA modem not operable… this malfunction happened after Google map app inadvertently hanged up and I tried to shut down the tablet.. does anybody have a clue what happened with the damned tablet and what might be possible cure? Will be extremely grateful for any advice
Thank you!
Thanks wyatt23 & nirogu325. I had this exact problem and downloaded 7-8 pit files that weren't working until I found this. I was about to get a baseball bat and go Office Space on the tablet. It's working fine now and will get a custom mod as soon as it charges.

[Q] SU660 with stock ICS (can't install CWM)

Flashed my SU660 to stock ICS and rooted, somehow CWM does not like to install here.
it always give me this....
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 14 NvError 0x120000
command failure: partition download failed
================================================== =============
================================================== =============
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
Press any key to continue . . .
Click to expand...
Click to collapse
any alternative and easier way to have it installed?
Try the following:
http://forum.xda-developers.com/showthread.php?p=33246703
Sent from my SGH-I897 using xda premium
This is one of the methods I tried over the weekend, it gives me the same error log.
Read about this in another thread, but it doesn't seem anyone has an answer for it.
asian_xl said:
This is one of the methods I tried over the weekend, it gives me the same error log.
Read about this in another thread, but it doesn't seem anyone has an answer for it.
Click to expand...
Click to collapse
Did you follow the instructions carefully?
Did you get in the APX mode successfully?
did google the error message, some say need to have battery inserted and some say require SD card inserted. Tried all methods, but still stuck at command 14.
Re-re-read the instruction and repeated every single step, same ending. Worst thing is, it reset everything to factory setting when it fails.
Perhaps you can try this first to get back to a clean slate
http://forum.xda-developers.com/showthread.php?p=33561620
Sent from my SGH-I897 using xda premium
meanwhile I try the above method, is there any aftermarket kernel for stock ICS rom?

[Q] Samsung Galaxy Pop

I have a Samsung Galaxy Pop with “com.android.phone” error each time the device restarts. The network goes down and comes back again. This happens twice.
I had upgraded my handset from 2.2.1 to 2.2.2 using Kies in Sept 2012. I somehow got a chance to copy the I559DDEH31_HOME.tar.md5 file which Kies creates for upgrade. The contents of the file are amss, boot.img, cache.rfs, recovery.img & system.rfs.
I have tried Odin to flash but have been unsuccessful.
I would like to know if I can use “dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096” command using adb shell to restore the handset to its original state?
I am not that good at Android so would like to know if somebody can help me.
deep143in said:
I have a Samsung Galaxy Pop with “com.android.phone” error each time the device restarts. The network goes down and comes back again. This happens twice.
I had upgraded my handset from 2.2.1 to 2.2.2 using Kies in Sept 2012. I somehow got a chance to copy the I559DDEH31_HOME.tar.md5 file which Kies creates for upgrade. The contents of the file are amss, boot.img, cache.rfs, recovery.img & system.rfs.
I have tried Odin to flash but have been unsuccessful.
I would like to know if I can use “dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096” command using adb shell to restore the handset to its original state?
I am not that good at Android so would like to know if somebody can help me.
Click to expand...
Click to collapse
No replies??
deep143in said:
No replies??
Click to expand...
Click to collapse
Why don't u flash a new gingerbread 2.3.6 stock rom? Froyo is kind of outdated. Make sure to backup your contacts and everything if u decide to do so.
kirakun said:
Why don't u flash a new gingerbread 2.3.6 stock rom? Froyo is kind of outdated. Make sure to backup your contacts and everything if u decide to do so.
Click to expand...
Click to collapse
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
that will ruin your phone
and for the message just need to wipe data from recovery
deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
My bad i was not aware of this different version. Yes do try what dheeraj has said.
I think that entering recovery should be same for u, just switch off phone, press home button and power button simultaneously and hopefully you will enter recovery.
Navigate using volume button and do a wipe data and cache. Doing so you will lose any app and everything from your phone, so do a backup before.
dheeraj (dhlalit11) said:
that will ruin your phone
and for the message just need to wipe data from recovery
Click to expand...
Click to collapse
I have already tried to wipe from recovery twice but still face the same error. Everything resets to factory defaults except this error which pops up at every restart..
reflash firmware through odin
and I will recommend you to take it to Samsung care
---------- Post added at 04:50 PM ---------- Previous post was at 04:50 PM ----------
reflash firmware through kies
and I will recommend you to take it to Samsung care
dheeraj (dhlalit11) said:
reflash firmware through odin
and I will recommend you to take it to Samsung care
---------- Post added at 04:50 PM ---------- Previous post was at 04:50 PM ----------
reflash firmware through kies
and I will recommend you to take it to Samsung care
Click to expand...
Click to collapse
I have done the wipe data and cache. Below is the response:
-- Wiping cache...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
-- Wiping data...
Formatting DATA:...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
But unfortunately same error.
I cannot flash firmware as I do not have one supported for this model of samsung (CDMA version). KIES says that the firmware is up to date so cannot flash from there as well.
deep143in said:
I have done the wipe data and cache. Below is the response:
-- Wiping cache...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
-- Wiping data...
Formatting DATA:...
Formatting CACHE:...
umount(/cache) attempt 1
(Unknown error: 0) rc=0
Cache wipe complete.
But unfortunately same error.
I cannot flash firmware as I do not have one supported for this model of samsung (CDMA version). KIES says that the firmware is up to date so cannot flash from there as well.
Click to expand...
Click to collapse
In case if you don't mind I would like to know how my phone will get ruined if I use the system.rfs from the original firmware file downloaded by Kies?
Secondly, is there a particular version of ODIN I need to use for this handset? I have tried 1.85, 3.07 and 4.38 versions.
Actually I do not have any other files than the I559DDEH31_HOME.tar.md5 required by ODIN.
I would prefer to go to Samsung service centre only when I am left with no option or if the handset fails to do its regular tasks.
Anyways, thanks for your suggestion.
you will do it while your phone is running and while doing it your mobile will reboot in the process due to change in some critical files
and we also don't know what is the structure of system.rfs
dheeraj (dhlalit11) said:
you will do it while your phone is running and while doing it your mobile will reboot in the process due to change in some critical files
and we also don't know what is the structure of system.rfs
Click to expand...
Click to collapse
Dheeraj, I understand what you are trying to say. I was plannning to do so in recovery mode. I have checked through ADB that I can access the device when in recovery mode. Will it still be a problem?
deep143in said:
Dheeraj, I understand what you are trying to say. I was plannning to do so in recovery mode. I have checked through ADB that I can access the device when in recovery mode. Will it still be a problem?
Click to expand...
Click to collapse
Alternatively I can also do when the phone is in download mode..
What do u think?
well you can't in download mode
but of you have cwm then it would be easy
open system.rfs with soft which can mount iso etc.
Copy the content of system to you sdcard
now flash aroma file manager and with the help of that copy all the files your your system.rfs to your system partition
and with dd it may copy files to /system/system or directly to /root
dheeraj (dhlalit11) said:
well you can't in download mode
but of you have cwm then it would be easy
open system.rfs with soft which can mount iso etc.
Copy the content of system to you sdcard
now flash aroma file manager and with the help of that copy all the files your your system.rfs to your system partition
and with dd it may copy files to /system/system or directly to /root
Click to expand...
Click to collapse
I used a linux machine to mount the system.rfs. Extracted phone.apk and installed the app using root explorer.
Finally the problem com.android.phone has been resolved..
Thanks for your help.
deep143in said:
Hi Kirakun,
I would love to do that but unfortunately I am not able to find dedicated Gingerbread 2.3.6 stock rom for Samsung Galaxy Pop CDMA (India) SCH-I559.
I have searched a lot but found only for Samsung Galaxy mini or S5570 which are the GSM versions of the same model.
I have also found that some have already bricked their phones using the other versions.
So I have decided to stick to froyo.
I just wanted to make sure that if I restore the /system partition using system.rfs command (dd if=/dev/block/stl12 of=/sdcard/system.rfs bs=4096) shouldn't create any new problems.
Click to expand...
Click to collapse
the upgrade is available in India but only at the official samsung repair center.
u will have to visit 'em get it upgraded

[Q] Boot loop on Captivate after reimaging stock

My girlfiend's Captivate had CM10 with ClockWork recovery. While traveling abroad it stopped booting (that's from her words - I am not sure what exactly happened ) so she brought it to a local "service center" where they attempted to fix it. not sure what they did but it looks like they tried to flash the stock - the phone boots a little past ATT animation into the stock animation and then reboots.
I went into recovery mode and it looks like stock recovery, not clockwork. So, the phone is in an unknown state and I don't know what to do to fix it. I assume there an image I can flash using ODIN to put it into some known state so I could take it form there and flash what I need. I am a beginner-intermediate ROM flasher so please give as many details as possible on a fix.
Thank you!
andreyl79 said:
My girlfiend's Captivate had CM10 with ClockWork recovery. While traveling abroad it stopped booting (that's from her words - I am not sure what exactly happened ) so she brought it to a local "service center" where they attempted to fix it. not sure what they did but it looks like they tried to flash the stock - the phone boots a little past ATT animation into the stock animation and then reboots.
I went into recovery mode and it looks like stock recovery, not clockwork. So, the phone is in an unknown state and I don't know what to do to fix it. I assume there an image I can flash using ODIN to put it into some known state so I could take it form there and flash what I need. I am a beginner-intermediate ROM flasher so please give as many details as possible on a fix.
Thank you!
Click to expand...
Click to collapse
The internal SD probably died, which is why it stopped booting. The service center was probably some local store that tried to fix it blindly by flashing it back to stock, which leads you to the state it is right now.
Steps:
1. Get a spare MicroSD if you don't already have one on hand. Format it blank. Copy a copy of Glitch Kernel from here (http://narod.yandex.ru/disk/5065044...1e2649/CM7Captivate-Glitch-V13_1-REL.zip.html). Sorry about the Russian site, but the original mirror died, at least for me.
2. Flash Semaphore Kernel (http://semaphore.gr/kernels/Semaphore_2.5.0c.tar)
3. Pull the battery, reboot into recovery. Flash Glitch Kernel. Reboot recovery
4. Use Glitch Kernel to partition the SD card. The EXT partition will be your replacement /data partition, so set the size accordingly.
5. Flash CM7 twice, without rebooting.
6. Make sure CM7 boots
7. Flash your ROM. Before rebooting, flash the patch from here (http://forum.xda-developers.com/showthread.php?t=2177876). Stick to 4.2.2 and below
thebulletfromhell said:
The internal SD probably died, which is why it stopped booting. The service center was probably some local store that tried to fix it blindly by flashing it back to stock, which leads you to the state it is right now.
Steps:
1. Get a spare MicroSD if you don't already have one on hand. Format it blank. Copy a copy of Glitch Kernel from here (http://narod.yandex.ru/disk/5065044...1e2649/CM7Captivate-Glitch-V13_1-REL.zip.html). Sorry about the Russian site, but the original mirror died, at least for me.
2. Flash Semaphore Kernel (http://semaphore.gr/kernels/Semaphore_2.5.0c.tar)
3. Pull the battery, reboot into recovery. Flash Glitch Kernel. Reboot recovery
4. Use Glitch Kernel to partition the SD card. The EXT partition will be your replacement /data partition, so set the size accordingly.
5. Flash CM7 twice, without rebooting.
6. Make sure CM7 boots
7. Flash your ROM. Before rebooting, flash the patch from here (http://forum.xda-developers.com/showthread.php?t=2177876). Stick to 4.2.2 and below
Click to expand...
Click to collapse
Thanks for the comprehensive answer.
I am stuck on #2. Trying to flash Semafore Kernel using Odin v1.85 and it's failing:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> zImage
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone is in Downlaod mode and USB driver is installed (ODIN sees the phone as 0:COM3)
Can you try another USB port/cable? If that doesn't work, try heimdall?
I removed and reinserted the battery, put it into download mode and now instead of Downloading it shows "Firmware update failed". ODIN can still see it but it gets stuck on SetupConnection. I've tried three different USB cables and all three USB ports my box has - same thing, stuck on SetupConnection. I am going to try Heimdall now
Ok, Heimdall failed to detect the phone. I tried to run Odin 3.09 instead of 1.89 and it seemed to work! This is the log:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> zImage
<ID:0/008> NAND Write Start!!
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
It did shut down the phone after completion. Does it look good?
Any way to test if the internal SD is indeed dead or not? I would much rather try to use it than an external SD
Ok I think I am making progress - after flashing Semaphore kernel I was able to boot into CWM recovery. I also chose to format /data pertition and it did it without error, which tells me that probably internal SD card is not dead.
The next problem - recovery doesn't see the external SD card. That I overcame by pushing C7 Glitch onto the internal SD card (it's alive!) using adb push.
Then I installed Glitch from internal SD. And then **** happened. I booted into Glitch recovery to install CM10.2 and it started err'ing that it can't find /sdcard. I could still see the sd card using adb shell. Using ODIN I reflashed Semaphore, thinking that Glitch is havign a glitch, but now Semaphore recovery can't see /sdcard either!
What do i do? teh internal SD card was accessible a few minutes ago - i copied CM7 there, i installed CM& Glitch from it. And now I can't access it any more. Any ideas?
From what I read I might need to reformat/repartition my internal SD card - how do I do that?
andreyl79 said:
From what I read I might need to reformat/repartition my internal SD card - how do I do that?
Click to expand...
Click to collapse
...You can't. It's a hardware problem, and the only permanent solution is to get a new board. There is no interface to access the raw internal SD (that we know of). Your best hope is just to follow the steps I've listed, and hope one day the card comes back to life (mine never did, although some people did on this forum).
thebulletfromhell said:
...You can't. It's a hardware problem, and the only permanent solution is to get a new board. There is no interface to access the raw internal SD (that we know of). Your best hope is just to follow the steps I've listed, and hope one day the card comes back to life (mine never did, although some people did on this forum).
Click to expand...
Click to collapse
I am not sure how to follow your steps in this situation - how do I flash CM7 Glitch if I can't copy it onto the internal SD? My external SD is not recognized by Semafore, and I think it's a known issue as I saw other people talking about it as well (Semaphore not seeing external SD).
Any ideas?
Try Corn Kernel: http://forum.xda-developers.com/showthread.php?t=1294477
thebulletfromhell said:
Try Corn Kernel: http://forum.xda-developers.com/showthread.php?t=1294477
Click to expand...
Click to collapse
Just flashed Corn, getting a boot loop (as expected I guess) but I can't get into Recovery mode. Vol UP+Dn+Power just boots it up and gets it into the loop.
http://forum.xda-developers.com/showthread.php?t=893880 Speedmod? Just partition straight from here, and flash CM7.
If that doesn't work, flash GearKernel/Semaphore for ICS/JB/KitKat, then flash Glitch from there.After that, format everything multiple times before you try and flash CM7 (or it'll perma bootloop, since the partition layout is wrong, and fixing it is a pain. I have no idea how I got mine working back then)
thebulletfromhell said:
http://forum.xda-developers.com/showthread.php?t=893880 Speedmod? Just partition straight from here, and flash CM7.
Click to expand...
Click to collapse
Maybe I'm not understanding smth... I flashed Speedmod, went into Recovery. What do you mean by "partition straight from there" - partition what? It still gives errors if I try to access /mount/sdcard or /cache or /boot or /system.
andreyl79 said:
Maybe I'm not understanding smth... I flashed Speedmod, went into Recovery. What do you mean by "partition straight from there" - partition what? It still gives errors if I try to access /mount/sdcard or /cache or /boot or /system.
Click to expand...
Click to collapse
Format everything, partition the SDcard from there (its in one of the menus, can't remember which). That'll partition your external SD, to replace the internal one.
thebulletfromhell said:
Format everything, partition the SDcard from there (its in one of the menus, can't remember which). That'll partition your external SD, to replace the internal one.
Click to expand...
Click to collapse
Ok, after a few days of the phone resting on my table it somehow decided it can see the external SD card as /mnt/sdcard and I was able to copy cm-7.2.0-captivatemtd.zip onto it and flash it.
Now, when I reboot it shows cyanogenmod logo and goes straight into recovery. Second attempt to flash the same 7.2 shows an error:
Installing update..
Checking state of BML/MTD...
assert failed: run_program("/tmp/updater.sh") == 0
E: error in /sdcard/cm-7.2.0-captivatemtd.zip (Status 7)
Installation aborted.
UPDATE: I flashed 7.2 twice in a row, second time it rebooted in recovery. Then I flashed CM10.2 twice in a row, first time it showed the error and second time it just rebooted into the recovery, but it shows the new version 6.0 of CWM recovery so something got updated. BUT - it still reboots in recovery - it feels like it doesnt want to flash the actual OS, just CWM
UPDATE 2: While in teh CWM recovery, I found "Partition sd card" option and i partitioned it. No errors. But now if I try to flash CM 10.1.3 I get this error:
E: error in /sdcard/cm-10.1.3-captivatemtd.zip (Status 0)
Installation aborted
Update 3: I tried to install SlimRom 3.1 - it rebooted to CWM, then I reflashed it twice again, each time no errors but it went really fast - prolly 15-20 sec each install. And then again it reboots into recovery. No errors anywhere. I am stuck at this point - after flashing any ROM it reboots into recovery.
Any ideas what's going on?
Ok, I decided to step back and just follow your initial advice.
1. I flashed Glitch
2. In Glitch I partitioned SD card
3. I flashed CM 7.1 twice
4. I rebooted and the phone still reboots into recovery
This is boot.txt log:
Code:
Thu Sep 4 04:32:38 GMT 2014
Bad block 19 at 0x4c0000.
Partition info: Total 11534336, Erase 262144, write 4096
Bad block 43 in reservoir area, skipping.
Found mapping block mark at 0xa00000 (block 40).
Found start of mapping table.
Found raw block mapping 91 -> 2042
Partition relative block mapping 19 -> 38
Absolute mapped start addresses 0x16c0000 -> 0x1fe80000
Partition relative mapped start addresses 0x4c0000 -> 0x980000
Found raw block mapping 766 -> 2041
Found raw block mapping 1387 -> 2040
Found raw block mapping 1647 -> 2039
Found raw block mapping 1800 -> 2038
Bad block has properly mapped reservoir block 19 -> 38
Successfully dumped partition to /stage1/boot.bin
umount: can't umount /sdcard: Invalid argument
cpio: dev not created: newer or same age file exists
cpio: proc not created: newer or same age file exists
2584+0 records in
2584+0 records out
1323008 bytes (1.3MB) copied, 0.201845 seconds, 6.3MB/s
cpio: sys not created: newer or same age file exists
cpio: system not created: newer or same age file exists
4401 blocks
Thu Sep 4 04:32:41 GMT 2014
What can I do?
Flash back to stock and try again. Make sure the flash actually takes a while (so the conversion is successful)
thebulletfromhell said:
Flash back to stock and try again. Make sure the flash actually takes a while (so the conversion is successful)
Click to expand...
Click to collapse
I can only find a stock image as Odin one click, but for some reason when I launch it, it doesn't see my phone. When I launch regular ODIN it can see the phone. Do you know of any non-one click stock image locations? All I could find was expired links
Odin one click is very hit-or-miss. It worked on my desktop, but not on my iMac or laptop.
http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3

Categories

Resources