Database Develop

[Q] Help! Broken microUSB port

Hi,
I'm pretty sure the microUSB port on my AT&T Captivate is shot... It will charge using the outlet adapter, but will *not* charge or connect to any of several PCs. I've uninstalled/reinstalled drivers multi times, and another Captivate exactly like it connects just fine (with same cable, same port, etc.) Good news: it's still under warranty. Bad news: it's been rooted and updated with a "Low-designgears" util.
Do I need to revert to stock in order to return for warranty, and is it possible to do that if the phone can't connect to a PC?
Stupid questions probably. Thank you.

I would think that you need to return to stock...you can chance it. But it's up to you.
Sent from my SGH-I897 using XDA Premium App

What firmware are u on? I think there was a cwm flashable stock somewhere...don't know if that would help.
Sent from my SGH-I897 using XDA Premium App

There is a cwm flashable jh7 but I think it only works from 2.1. Might work with 2.2 but if all else fails format boot in recovery and tell at&t your phone said there was an update and it failed. I would probably format system, cache, and data too just so there isn't any evidence of your wrong doing. Unlikely it would ever find its way back to you though. Has worked for a lot of people.
It should hard brick your phone though
Sent from my I897 using xda premium

Firmware is 2.2. Thanks for the help. I'll look for that cwm flashable, and consider my options. Thanks.

xijar said:
There is a cwm flashable jh7 but I think it only works from 2.1. Might work with 2.2 but if all else fails format boot in recovery and tell at&t your phone said there was an update and it failed. I would probably format system, cache, and data too just so there isn't any evidence of your wrong doing. Unlikely it would ever find its way back to you though. Has worked for a lot of people.
It should hard brick your phone though
Sent from my I897 using xda premium
Click to expand...
Click to collapse
1. As long as it's rooted he can replace 3e recovery, install cwm, and flash that from 2.2.
2. Formatting does not hard brick. Why would there be an option that would completely **** your phone? Like a self destruct button that could accidentally be pressed if you don't know what you're doing. Makes no sense.

studacris said:
1. As long as it's rooted he can replace 3e recovery, install cwm, and flash that from 2.2.
2. Formatting does not hard brick. Why would there be an option that would completely **** your phone? Like a self destruct button that could accidentally be pressed if you don't know what you're doing. Makes no sense.
Click to expand...
Click to collapse
Sorry, back again guys...
I've got cwm installed but I can't find a way to get past 3e recovery. I tried to flash cwm recovery from rom mgr - and it says current recover is cwm 2.5.1.2 - but going into recovery mode still shows 3e (don't know what cwm recovery should look like). Flashing any rom (tried a couple customs too) dies with sig verification error.
been searching for a few hours on replacing 3e, but everything i run across requires ability to connect with the pc.
any idea how i can replace 3e recovery without ability to connect via usb?

http://forum.xda-developers.com/showthread.php?t=1052991
The second method does not require a pc. Download the fix files with your phone, then download a file explorer from the market that has root access, root explorer, file expert, astro file manager to name a couple. Paste in the file reboot into recovery, reinstall packages twice and that will boot you into cwm, which its green with more options...

brick the phone n say kies ****ed it up. that worked for me.
Samsung captivate
glitch kernel
cyanogenmod 7 #89
OC and UV

[Q] Failed downgrading from ICS leak, no charging, bootloop after flashing GB PC Odin

Hi!
So i figured i wanted to get of the faulty ics leak in order to keep my phone safe, but it seems I was able to do the exact oppsite...
I will try to make a detailed overview of what I did, here we go.
I was using Stunner on CLP5. Followed this guide to do the downgrade:
http://www.youtube.com/watch?v=jr3DDEh8vyc&list=UUlVIlK8QHZ2PFkXF97bA0lg&index=5&feature=plcp
What i did:
Flashed the Abyss kernel - rebooted
Wiped with the new recovery
Flashed rocketrom
Got stuck on bootloop. (I should've probably done another wipe here, am i right? )
After flashing Rocketrom, I once again got a new recovery, I figured I was on a safe kernel and recovery now so instead of trying wiping or a different rom, I was stupid enough to do a restore of a backup of a stock rom with root I had from December when i bought the phone.
This made everything even worse, my battery drained and I was unable to charge my phone through USB or 220v. Luckily I got my friend to charge my battery (same phone)
Booting up my phone agian, I was no longer able to acess recovery, but I still had acess to Download mode.
I flashed a stock GB rom successfully through PC Odin, and yet AGIAN I was stuck at bootloop. The file I flashed was a single .tar file. I didn't select update bootloader, should i try this? maybe re-ptartitioning?
I still have acess to download mode.
Has anyone got a clue how to fix this mess?
Thanks for all replies!

Tried different stock ROM and PIT partitioning, no luck so far

lameplx said:
Tried different stock ROM and PIT partitioning, no luck so far
Click to expand...
Click to collapse
Please, pit partitioning seems to get thrown out there like smarties but imo should only ever be used as a very last resort as a lot can go wrong.
Have you tried wiping cache and dalvik? Sorts out reboots 99 percent of the time.
Sent from my GT-N7000 using xda premium

SpyderTracks said:
Please, pit partitioning seems to get thrown out there like smarties but imo should only ever be used as a very last resort as a lot can go wrong.
Have you tried wiping cache and dalvik? Sorts out reboots 99 percent of the time.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I,m not able to enter recovery. UP+POWER+ MENU, right?
Stuck on bootloop on stock GB.

lameplx said:
I,m not able to enter recovery. UP+POWER+ MENU, right?
Stuck on bootloop on stock GB.
Click to expand...
Click to collapse
volume up+power+home
Wait until it reboots
Sent from my GT-N7000 using xda premium

Hg42's pit files and a stock gb rom unbricked my phone, have you read forest 1971s guide i think it is?
Sent from my GT-N7000 using XDA Premium HD app

Mc_CuLLa said:
Hg42's pit files and a stock gb rom unbricked my phone, have you read forest 1971s guide i think it is?
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Solved the problem by downloading yet a another stock GB rom, this time with three files, instead of the one .tar file.

lameplx said:
Solved the problem by downloading yet a another stock GB rom, this time with three files, instead of the one .tar file.
Click to expand...
Click to collapse
Thats good to know...

lameplx said:
Solved the problem by downloading yet a another stock GB rom, this time with three files, instead of the one .tar file.
Click to expand...
Click to collapse
Well done
Sent from my GT-N7000 using xda premium

Samsung T849 Stock Rom Need

If anyone know where I can get the stock firmware for this devices please let me know. I search the forum and all the links are deads, Sammobile doesn't have firmware for this model.
Thank you

may I know why you want to return to stock T849?
It was a Froyo rom. Any special need to get it back to stock stock?

priyana said:
may I know why you want to return to stock T849?
It was a Froyo rom. Any special need to get it back to stock stock?
Click to expand...
Click to collapse
it was hard bricked, got jtag, now i need to reload it.
I found threads on here but link with multiupload are dead

then no need to
Just use Overcome guide to load Gingerbread ROM
Go to overcome site
Http://www.teamovercome.net
Read the guide,
Missing pictures can be seen here.
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
Basically to restock:
Download GB-stock-safe-v5.zip, unzip it and and flash with ODIN according to the guide.
Stop there and you will have Gingerbread JQ1
You can continue with the rest, and you will get Overcome 4.1 and you won't regret.
From there you can then try AOKP or CM9, all requires you to have Overcome Kernel with its CWM recovery to flash.
the package include a T-mobile modem to choose
it will let you have 3G in T-mobile network but no voice call.
If you use the JPZ modem that is also included, you can get voice call but EDGE speed for internet.

thank you will do that and report back

i tried to reload per the instruction, it ran for about 3 minutes near the end it "FAILED"

Hmm no idea.
Hope it is not a locked bootloader.
Can you try it again?
You are using Odin 1.7 that is included in the gb stock safe, right?
Sent from my GT-I9300 using xda app-developers app

priyana said:
Hmm no idea.
Hope it is not a locked bootloader.
Can you try it again?
You are using Odin 1.7 that is included in the gb stock safe, right?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Im using 1.7 that came with the package, tried 5 times already
Yes, may be i should let you know how the device bricked
I accepted the OTA update after reboot the phone never turn back on .
Could it be that the fw im trying to update is older then the OTA caused it to fail ?

I doubt the version matters, I am wondering if it is caused by broken NAND chip.
I have never encountered this before.
Let's have some crazy idea.
I am thinking of flashing cm9 or aokp mtd rom on it.
I myself am using Stimpz0r AOKP build 40.
Can you download it and put in external SD card,
And also the gapps-ics.
Just get it ready.
While for the tab, flash overcome kernel 4.0 tar as per the guide, as if it was a successful restock.
Once the kernel is flashed, force it power off.
Then try to boot to recovery.
If that works, try flash the ICS rom and see if it works.
You need to flash it twice, as first one converts to mtd.
Second flash will install.
Hopefully it boots.
Sent from my GT-P1000 using xda app-developers app

I flashed the kernel now it able to boot to the galaxy tab then the android animate but it in a boot loop at the android. I can't go to recovery, that's Vol Up + Power correct ?

i was able to install CM9 but getting "Encryption Unsuccessful" error after boot
I tried to wipe data/factory reset and got the following error:
format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
probably bad block where this partion is located that why it failed when tried to flash Overcome rom.
there is a tool to relocate this partion to a different block and hopefully it work? do you know such tool ?

I have never come across such tool.
There is a thread that discuss about bad internal sdcard, and using external SD instead.
By you have to open up the tab and desolder the NAND chip.
Sent from my GT-P1000 using xda app-developers app

this tool
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12

Oh repartition.
Should be easier since we are in mtd now.
I am not one, but the devs are good at mtd partition.
Maybe they can help you rearrange the partition do that you get smaller but usable /data
Sent from my GT-P1000 using xda app-developers app

am sorry but how can i get the dev to help?
if you could, please print the partition table of your device ? Ill try to re-create while waiting for the dev to help
Thanks

I dont know if we have recovery with parted.
but this is my fdisk
Sent from my GT-P1000 using xda app-developers app

Is my Galaxy Tab bricked?

Hey there guys I'm hoping someone can help me! I have a 16gb P1000T (Australian Telstra version)
I was going through the motions of upgrading my tab from an ICS build to a JB build, which failed, I then tried to flash back the previous build with the same error. I tried numerous ROM's and versions with nothing working (I would always get a boot loop) Eventually it stopped booting into even the CWM recovery mode. I then optioned to restock, I now cannot access the recovery mode no matter what kernel or recovery I flash or how. I can only get the stock ROM to boot and even then the ROM will automatically shutdown if the display is allowed to flick off...
So basically I'm at the current point;
- I can get a 'downloading' screen and 'successfully' flash almost anything using Heimdall or ODIN
- I cannot access any type of recovery mode... at all using power+vol down
- The only ROM that will boot is the stock one
- The stock ROM turns the tab off if the display is allowed to go to sleep
Any help would be greatly appreciated!
Cheers,
Hamish

Try overcome method
http://www.teamovercome.net
Read the guide,
https://docs.google.com/file/d/0B7k...EyNS00Yzg5LWE0MTktYmYyMjA1MThmYzQz/edit?pli=1
Missing pictures can be seen there.
Follow the picture step by step.
missing files at
http://tabfirmware.com/2012/01/romk...e-7-series-v4-1-0-♫-overcome-kernel-v4-0-0-♫/
Jump here for the kernel
Here is the kernel (tar format for Odin, zip isn't the one you want I guess)
http://forum.xda-developers.com/showpost.php?p=27801159&postcount=8
Sent from my GT-P1000 using xda app-developers app

Since you can go to download mode, i can assure you that you have not bricked your tab, unless you have messed with the partitions. i do not know much about cdma tabs, but you have not bricked your tab

I think I may have inadvertently messed with the permissions - The overcome method doesn't work - same issue over and over. Something about MTD ROMs vs non-MTD? I'm not sure what they mean, but I think I may have gone from one to the other without restocking?
Also the tab runs on GSM 850/2100, not CDMA.

Can you elaborate which part of overcome method fails?
The first part is flashing gb stock safe.
You need to tick repartition.
Did you get that done successfully and tab boot to stock gb nicely? Or still the screen off and it is powered off again.
Sent from my GT-I9300 using xda app-developers app

Hi Priyana, I get a nice stock GB, but as soon as I try and root, I can't boot or enter recovery - I'm trying again now.

From fresh stock.
Just boot to download mode, and flash overcome kernel using Odin.
Once done, the tab reboot, ignore it, just force it off.
Then boot to the new recovery.
And immediate flash ics rom. You need to do this twice.
Then flash gapps.
Then reboot to ics.
I have done this so many times, using Odin or heimdall. And guides so many people doing it. Works all the time.
Sent from my GT-P1000 using xda app-developers app

I eventually got it to work - **** knows what I did though lol cheers!

Try overcome method
Sent from my GT-P1000 using xda app-developers app

[Q] Bootloaders

I feel like an idiot after reading this forum for the last couple of weeks. My problem started when I really wanted Jelly Bean on my i897 instead of the stock Gingerbread. I found out I failed to install Cyanogenmod and ended up with a phone that could no longer go into download mode, couldn't get into recovery, my laptop no longer recognized the phone and when I powered up the phone it was bootlooping on the AT&T screen.
I ended up buying a jig. It came in the mail today and I got into download mode and using Heimdall flashed I897UCKK4 Stock, NO Bootloaders, Wipe-One-Click.
I wanted to root my phone so I flashed Corn Kernel. My phone didn't go into download mode (it showed the battery charging when I tried) so I had to use the jig to get into into download mode. When I tried to get into recovery, it bootlooped on the AT&T screen. And I noticed during a normal power up of my phone, right after the AT&T screen, I see rainbow colored lines.
I asked someone who has been nice to enough to help me these last couple weeks and he said that the garbled lines mean I'm trying to use a gingerbread kernel and I don't have gingerbread bootloaders. Would the easy way to fix this is to use the same Heimdall One Click I used flashing the same stock and CHECK flash bootloaders this time?
Thanks for your help in advance!

No...u need the one with bootloaders option included...because if the one u have is the one i packaged then the bootloaders are not even included in that package, so even if u chose the bootloader option it would not work.
And if i remember correctly, even with the Heimdall One Click that has the option to install bootloaders etc., it will require two flashes to get the bootloaders. The first flash installs the firmware and then the second installs firmware with the bootloaders. That is just the way it is with heimdall. Just follow the promps and u should be good.
There r other ways of gettin the i897 gb bootloaders of course. The Odin kk4 one click that contains them that i put together in that same one click stickied thread in the dev forum. Also TRusselo has a download of them alone in his Guide that is a stickied thread in the q & a forum. See his op for them.
And etc. etc. :thumbup:
Sent from my SAMSUNG-SGH-I777 using xda premium

4-2ndtwin said:
No...u need the one with bootloaders option included...because if the one u have is the one i packaged then the bootloaders are not even included in that package, so even if u chose the bootloader option it would not work.
And if i remember correctly, even with the Heimdall One Click that has the option to install bootloaders etc., it will require two flashes to get the bootloaders. The first flash installs the firmware and then the second installs firmware with the bootloaders. That is just the way it is with heimdall. Just follow the promps and u should be good.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Will that solve my problem of not being able to get into download mode or recovery, by adding the bootloaders this time? I don't want to brick my phone, although I've been reading that its nearly impossible to brick. ha
Thank you.

Yes the i897 gb bootloaders have solved users problems with button combos to get in download and recovery mode.
But always be careful flashin bls. Mixed matched bls or bad flash of them...loosin power to ur pc during the flash of them or loosin connection of ur usb/micro usb cord during the flash will possibly hard brick ur phone.
So just be sure to have a constant power source, reliable usb/micro usb cable, and don't interupt the flash during the few seconds it takes to install the boot.bin and sbl.bin files. And once u have installed the gb bootloaders there is absolutely no need to flash bls again. If u ever need to flash back to stock just use kk4 with No bls.
Keep us posted on how it goes...
Sent from my SAMSUNG-SGH-I777 using xda premium

4-2ndtwin said:
Yes the i897 gb bootloaders have solved users problems with button combos to get in download and recovery mode.
But always be careful flashin bls. Mixed matched bls or bad flash of them...loosin power to ur pc during the flash of them or loosin connection of ur usb/micro usb cord during the flash will possibly hard brick ur phone.
So just be sure to have a constant power source, reliable usb/micro usb cable, and don't interupt the flash during the few seconds it takes to install the boot.bin and sbl.bin files. And once u have installed the gb bootloaders there is absolutely no need to flash bls again. If u ever need to flash back to stock just use kk4 with No bls.
Keep us posted on how it goes...
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I downloaded the Heimdall package WITH the bootloaders this time and my phone is having the same problems. I watched it flash twice but I didn't notice Heimdall installing anything different the second time. Was I supposed to check "flash bootloaders" at any time?

Yep. That gives permission for the install of the bootloaders. Check it before u begin the flash.
Sent from my SAMSUNG-SGH-I777 using xda premium

My personal preference is to do an odin flash of just the bootloader package from here http://forum.xda-developers.com/showthread.php?t=1350266 ... I bought my wife a cappy about a month ago and was trying to do a one-click to kk4 w/bl and it kept hanging. After a lot of fighting with it I ended up just flashing to bootloader package and then a custom kernel and all was good.

Yep. Some of the Captivates do not like one click packages. Mine is a 1009 build and thankfully has not had a problem with 'em.
Sent from my SAMSUNG-SGH-I777 using xda premium

4-2ndtwin said:
Yep. That gives permission for the install of the bootloaders. Check it before u begin the flash.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
FIXED! Thank you so much. No more rainbow pixels, I can get into download mode and recovery now.
I was following the instructions word by word cuz I didn't want to screw anything up and it didn't say to check the box. I'm ignorant.
Thanks again!

^ :thumbup:
Glad u got it. Now off u go to get ya some jellybeans.
Sent from my SAMSUNG-SGH-I777 using xda premium

4-2ndtwin said:
^ :thumbup:
Glad u got it. Now off u go to get ya some jellybeans.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
WOOOO JellyBeans!!!

4-2ndtwin said:
^ :thumbup:
Glad u got it. Now off u go to get ya some jellybeans.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Ha! Watch me screw it all up again. But its all good cuz I've got a jig now, I feel a lot safer.
I think my lack of knowledge regarding Odin and Heimdall on the same computer probably had something to do with my loss of the laptop being able to recognize my phone. I learned that I need to stay away from Odin, it never worked right for me.

Haha...u ought to be fine. Just remember, no need to flash bootloaders again. And the only other possible thing to be concerned about is the "Encryption Unsuccessful" error that has happened with users of this phone and several other phone models. There are two threads in the development forum if u wanna know more about that subject. Other than that the Captivate is a really tough phone. I have enjoyed mine for over 2 yrs now.
Sent from my SAMSUNG-SGH-I777 using xda premium

southernblonde said:
Ha! Watch me screw it all up again. But its all good cuz I've got a jig now, I feel a lot safer.
I think my lack of knowledge regarding Odin and Heimdall on the same computer probably had something to do with my loss of the laptop being able to recognize my phone. I learned that I need to stay away from Odin, it never worked right for me.
Click to expand...
Click to collapse
One thing I will mention is this... Coming from any other version to Jellybean, when you do the initial flash of the ROM it will either reboot automatically or show that the flash completed really quickly and then you'll reboot thinking you're installed. Either scenario will likely land you in a boot loop. Don't freak out because this is normal when you are first flashing to Jellybean. Its because of the partition layout differences and it just requires a reboot. Just get yourself back into recovery and flash everything again and all should be good.

m1batt1 said:
One thing I will mention is this... Coming from any other version to Jellybean, when you do the initial flash of the ROM it will either reboot automatically or show that the flash completed really quickly and then you'll reboot thinking you're installed. Either scenario will likely land you in a boot loop. Don't freak out because this is normal when you are first flashing to Jellybean. Its because of the partition layout differences and it just requires a reboot. Just get yourself back into recovery and flash everything again and all should be good.
Click to expand...
Click to collapse
Is Cyanogenmod supposed to be installed before I flash Jelly Bean? I'm going to be using Slim Bean. Thank you!

southernblonde said:
Is Cyanogenmod supposed to be installed before I flash Jelly Bean? I'm going to be using Slim Bean. Thank you!
Click to expand...
Click to collapse
No, just flash Slim Bean twice. Flash the first time, get back in recovery and reflash Slim Bean right over it.

BWolf56 said:
No, just flash Slim Bean twice. Flash the first time, get back in recovery and reflash Slim Bean right over it.
Click to expand...
Click to collapse
The first time I attempted to flash it, when it rebooted, it was stuck on the AT&T screen forever. I didn't know whether or not it had froze or not so I took the battery out, powered it up, and then it started bootlooping between the AT&T and Semaphore screens.
I should have put it back into download mode again and reflashed it?

southernblonde said:
The first time I attempted to flash it, when it rebooted, it was stuck on the AT&T screen forever. I didn't know whether or not it had froze or not so I took the battery out, powered it up, and then it started bootlooping between the AT&T and Semaphore screens.
I should have put it back into download mode again and reflashed it?
Click to expand...
Click to collapse
No, you go back in recovery and reflash it. The first time, it needs to rewrite the partition so it won't fully flash. After the first flash is over, you get back in recovery and flash right over it (what we call a dirty flash). Then it should boot up just fine!

BWolf56 said:
No, you go back in recovery and reflash it. The first time, it needs to rewrite the partition so it won't fully flash. After the first flash is over, you get back in recovery and flash right over it (what we call a dirty flash). Then it should boot up just fine!
Click to expand...
Click to collapse
You guys are so smart, its sick :laugh:
I was just reading over Slim Bean installation and it says I need to boot up with CM9 or CM10. Is it still necessary to install it? Since I'm coming from Gingerbread. Here's where I read it at: http://www.slimroms.net/index.php/installation

southernblonde said:
You guys are so smart, its sick :laugh:
I was just reading over Slim Bean installation and it says I need to boot up with CM9 or CM10. Is it still necessary to install it? Since I'm coming from Gingerbread. Here's where I read it at: http://www.slimroms.net/index.php/installation
Click to expand...
Click to collapse
Can't see that page as I'm at work (yay for Gov's internet..)
As long as you have the GB bootloaders, you don't have to worry about much. Just make sure you have a cwm recovery (often gotten from flashing Corn kernel with Odin 1.85). But if you are already on a custom GB ROM, you don't have to worry about that.
Next is to factory reset, clear cache and dalvik in recovery and flash Slim Bean (Twice*) and finally the Gapps.
The process is the same for pretty much any JB ROM.
I'm a bit confused though, did you already flash it or not?