Database Info

HELP! Brick Bug!

So long story short, my tab was running stock ICS (rooted, with temp CWM/cwm.zip). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Do I have the Brick Bug?

rumpypumpy said:
So long story short, my tab was running stock ICS (rooted, with temp CWM). I decided to try a new rom (paranoid android) so I backed up everything via CWM and I flashed the new rom. But I forgot to do a factory reset before doing so which resulted in a bootloop. I returned to CWM to try to restore the previous ROM, all seemed to be fine and the tab restarted but was also bootlooped. Now I can't even access the stock recovery to acess CWM, I get an error message:
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC code : THL
Successfully applied multi-CSC
E :failed to mount / system (invalid argument) <in red.
Is there anything I can do to return to my stock ROM?!
Click to expand...
Click to collapse
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers

gmaster1 said:
Can it get into download mode? If so try flash a stock rom with odin. Im not a sgt user but i am a samsung phone user and usualy when i forget to wipe all i have to do is go back into recovery. Then wipe everything and flash the same rom. NEVER go straight to a backup unless you pass setup. Then it can create a link almost so it supports going back. Or so thats what ive been told by devs on other forums...sounds kinda wierd tho but anyway if you forget to do something while flashing roms then go back indo recovery and do it again
Sent from the phone of Gamers
Click to expand...
Click to collapse
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...

rumpypumpy said:
It loads the amination for the stock recovery, then I get the error message I posted above. I need to get onto the stock recovery to get into CWM. Im not too sure what to do at the moment...
Click to expand...
Click to collapse
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers

gmaster1 said:
Thats a messege saying the system has broke basicly because you went straight to a backup. Download mode and odin are your only hope
Sent from the phone of Gamers
Click to expand...
Click to collapse
I forgot about download mode. I'll have a go then I'll report back.
Thanks

Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction

rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866

rumpypumpy said:
Now I'm stuck at the "<ID:0/005> factoryfs.img" stage!
I'm a bit scared of unplugging the tab, what would be the best thing to do now?
EDIT: If I flash a kernel or CWM, would this solve my problem?
Thanks in advance
EDIT:I managed to get CWM working, a step in the right direction
Click to expand...
Click to collapse
If cwm works then we both know theres hope
Sent from the phone of Gamers

lsherif said:
From CWM wipe data, cache & dalvik & reboot.
And flash this ICS zip file from CWM. if yours is 6800.
http://forum.xda-developers.com/showthread.php?t=1796866
Click to expand...
Click to collapse
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually

rumpypumpy said:
I did everything you said, but the progress bar has been stuck at 75% for over an hour, this has happened with all the ROMs I've tried to install. Is there anything else I could do? I red somewhere that a low battery doesn't allow ROMs to be installed properly.
Although I have no idea of my battery life, I'm just gonna leave it to charge for a bit. I hope everything turns out fine eventually
Click to expand...
Click to collapse
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers

gmaster1 said:
Battery life has nothing to do with it. People just say make sure you have high battery incase something happens. I think that it might be a very expensive brick now. Unless anyone else knows then i habe no idea
Sent from the phone of Gamers
Click to expand...
Click to collapse
:crying:
I was reading the following articles:
http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
http://forum.xda-developers.com/showthread.php?t=1810954
Could this Brick Bug be the source of my problems?
I was running a leaked version of ICS AND I have been using the cwm.zip so there is the possibility

Being unable to flash through either Odin or CWM surely sounds a lot like the brickbug.
If I were you, I'd reboot to download mode, and install a full ROM with repartition + PIT file. If it works, install locerra's CWM (it's one of the few recoveries for our tablet that's confirmed to be brickbug-free), and work as usual. But remember to wipe everything before installing anything through CWM...
If Odin doesn't work, you probably have been hit by the brickbug. However, all is not lost: this guy seems to have found a "fix" for many devices. It involves giving up on all your data and making your onboard storage a couple of GB smaller than it used to be, but it can make your device work again. Read the thread, try to understand it, and (if you can't find another way out) use the PIT file for the GT-6800 provided. If your tab isn't the international WiFi+3G GT-P6800, you may have to ask the guy (hg42) for a PIT tailored to your device.
The other option, in the case of a eMMC-related brick, is to remove all traces of CWM, go to a Samsung store and repair it under warranty, saying "its broke down when I were running that backie upppe thing in kies".

The other option is the better one, as i bricked my note. When i am able to revive it, i am left with 8GB space and it seems real laggy. Change a new motherboard would be better if still cover undr warrantly.
Sent from my GT-P6800 using xda premium

Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks

rumpypumpy said:
Thanks for the replies guy.
I have decided I will return it as faulty, in the hope it is repaired. I haven't been able to boot into CWM anymore, only the download mode, so I am guessing it is fine to return it as it is?
Thanks
Click to expand...
Click to collapse
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.

Steve_max said:
If I were you, I'd return it to something as close to stock as possible.
One suggestion: grab the latest Odin-flashable ROM for your country. You'll get a .tar.md5 file, such as P6800UBLA2_P6800ZTOLA2_ZTO.tar.md5. Try to flash it through Odin, just to see if it works; if it doesn't, write down the name of the .img file that gave you problems. If it works, congratulations, you have your tablet back, and you can stop reading.
Now, Rename that file to .tar (or, remove the .md5 extension), and open it in WinRAR/7zip/whatever. You'll see a lot of .img files inside, including the one that gave you problems. Remove it, and try to flash this new .tar file. If the flash works, proceed to the next paragraph. If it doesn't, write down the name of the .img file that gave you problems, and repeat this paragraph using your new .tar file.
After a flash that works, your device should be as close to stock as possible. Maybe it will even boot, but I wouldn't count on it (try anyway). I'd send it to the repair centre only when it is at this stage.
Click to expand...
Click to collapse
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:

rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Thats...a...problem...if it takes longer then 15 mins its bricked...i have been a gt user and devs on other sites told me it was bricked. Maybe there is a solution but...i havnt found one. It should never take too long on one thing in odin.
Sent from the phone of Gamers

rumpypumpy said:
The tab gets stuck at 'factoryfs.img'. I'm a bit cautious since it is the biggest file in the .tar. Isn't the tab 'stock' stock enough as it is?:silly:
Click to expand...
Click to collapse
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.

Steve_max said:
Even so, flash the other .imgs. You want to be closest to stock, including the recovery (imagine the guys at the Samsung centre manage to enter recovery, just to see CWM: your warranty is now gone). Having all partitions on stock, or at least most of them, can only help your case.
Click to expand...
Click to collapse
The warrenty is not void unless they find proof of tampering with system files. So basicly yeah...everything that guy said. Get it as close to stock as possible and send.
Sent from the phone of Gamers

Right OK, I definately don't want my warrenty void!
So would it be ok if I flashed 'P6800OXALQ1_P6800XXLQ1_HOME.tar.md5' (minus the factoryfs.img) to my tab?
Thanks

[Q] Help in returning to stock rom

So i'm looking for a little help.
A little while back I used this thread : [GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
To help me install this custom rom : [ROM][TF300]|Mar 28| Energy™ -.¸¸.·´¯ Official JB 4.2.1 Stock or Themed ¯´·.¸¸. -
onto my girlfriends TF300T tablet
and I have this : [RECOVERY][TF300T/TG] TWRP 2.5.0.0 Touch Recovery! [2013-4-9] on there as well
but I can't remember if this was part of the unlock/root/flash process or not, so i'm not sure if it used it during the process or if I added it shortly afterword
now its been while since I have done it but then the tablet started to restart randomly while she was using it.
so I figured no biggie maybe an app got messed up or something, and so I told her to back up her pics, exc she wanted off the unit
and I could look at reinstalling the apps or just taking the unit back to factory rom
about a week later it started to reboot more often randomly
and now it is to the point where it will not make it into the rom
now I can make it into the boot selection where I can choose RCK (for the TWRP), USB, or the other 2 options
and I know I can make it into the TWRP tool as well and it does not repeatedly boot from there, so i'm sure its a rom issue and not a hardware issue, but I could still be wrong
the unit is currently charging so I have not had a chance to try for the usb connection option or anything else yet
hopefully the usb option will work so I can try to recover the pics, exc before taking the unit back to factory
now in the process I know I have unlocked the unit, I believe I have done the min root but have not fully rooted the unit if that makes sense
so i'm just wondering if I will half to fully root (and how do I do that if I do since I can't make it into a rom)
how do I clear the rom that has gone bad
how do I install a factory rom (how do I tell which is the lastest rom, and which one is needed for my unit)
and then I should be good from there
if you need any more info please let me know and maybe some instructions on how to get to that info
in the process of putting the energy rom onto it, I spent a week of reading, researching, and figuring out which way would probably be the safest for me to do, plus the easiest for me to understand
now that it has been so long I have been reading and researching again, I just need that nudge that gets me in the right direction
i'm sure i'm not the only one that has had this issue with a rom, and i'm also sure there is a guide out there already that goes over how to put it back to a factory rom
just for some reason i'm either over looking it or not finding it

allusion said:
So i'm looking for a little help.
A little while back I used this thread : [GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
To help me install this custom rom : [ROM][TF300]|Mar 28| Energy™ -.¸¸.·´¯ Official JB 4.2.1 Stock or Themed ¯´·.¸¸. -
onto my girlfriends TF300T tablet
and I have this : [RECOVERY][TF300T/TG] TWRP 2.5.0.0 Touch Recovery! [2013-4-9] on there as well
but I can't remember if this was part of the unlock/root/flash process or not, so i'm not sure if it used it during the process or if I added it shortly afterword
now its been while since I have done it but then the tablet started to restart randomly while she was using it.
so I figured no biggie maybe an app got messed up or something, and so I told her to back up her pics, exc she wanted off the unit
and I could look at reinstalling the apps or just taking the unit back to factory rom
about a week later it started to reboot more often randomly
and now it is to the point where it will not make it into the rom
now I can make it into the boot selection where I can choose RCK (for the TWRP), USB, or the other 2 options
and I know I can make it into the TWRP tool as well and it does not repeatedly boot from there, so i'm sure its a rom issue and not a hardware issue, but I could still be wrong
the unit is currently charging so I have not had a chance to try for the usb connection option or anything else yet
hopefully the usb option will work so I can try to recover the pics, exc before taking the unit back to factory
now in the process I know I have unlocked the unit, I believe I have done the min root but have not fully rooted the unit if that makes sense
so i'm just wondering if I will half to fully root (and how do I do that if I do since I can't make it into a rom)
how do I clear the rom that has gone bad
how do I install a factory rom (how do I tell which is the lastest rom, and which one is needed for my unit)
and then I should be good from there
if you need any more info please let me know and maybe some instructions on how to get to that info
in the process of putting the energy rom onto it, I spent a week of reading, researching, and figuring out which way would probably be the safest for me to do, plus the easiest for me to understand
now that it has been so long I have been reading and researching again, I just need that nudge that gets me in the right direction
i'm sure i'm not the only one that has had this issue with a rom, and i'm also sure there is a guide out there already that goes over how to put it back to a factory rom
just for some reason i'm either over looking it or not finding it
Click to expand...
Click to collapse
Its very simple to return to stock. But first, do you have the tablets drivers installed on your pc?
---------- Post added at 06:16 AM ---------- Previous post was at 06:14 AM ----------
And do you have fastboot?

if you are talking about the android sdk tools
yes that is installed on my computer from the first time I did the tablet
and I went ahead and did the updates for it as well
and tried plugging the unit in with the fastboot and confirm it shows up in device manager

bump
hope you didn't forget about me crazynitro

allusion said:
bump
hope you didn't forget about me crazynitro
Click to expand...
Click to collapse
sorry, i got caught up with some school work. i could walk you through the process, if you want.

if you could please, any links, post, exc you want me to read ahead of time please post
anything you need me to verify or check on please let me know
gf starting to be up my butt about her tablet, lol
but yes any help is more then appreciated

allusion said:
if you could please, any links, post, exc you want me to read ahead of time please post
anything you need me to verify or check on please let me know
gf starting to be up my butt about her tablet, lol
but yes any help is more then appreciated
Click to expand...
Click to collapse
Lol okay. Theres actually a more simple way.
1. Download the latest asus firmware.
2. Extract the zip file
3. Flash it like a normal rom.
If you cant use this method then you'll have to use fastboot. Here's a link but if you need any help, just ask : http://www.androidauthority.com/transformer-pad-tf300t-restore-stock-firmware-108016/

how do I check the sku according to that guide if i'm not able to load into the android os
that only shows if you can load into the os
would the box have that?

or now looking at the options that I should assume its is a US sku lol

crazynitro said:
3. Flash it like a normal rom.
Click to expand...
Click to collapse
lol, and how do I do that using the twrp?
can't find any detailed instructions on using twrp on flashing a rom, especially the stock one
i'm sure there is a set of detailed instructions cause I swore I saw one once
but i'm not able to find it again
cause I thought besides using the install part there were things I had to clear as well for it to work
oh and yeah the download link for fastboot is no long working in the one guide you gave me to follow so not sure if I already have what it is talking about

allusion said:
lol, and how do I do that using the twrp?
can't find any detailed instructions on using twrp on flashing a rom, especially the stock one
i'm sure there is a set of detailed instructions cause I swore I saw one once
but i'm not able to find it again
cause I thought besides using the install part there were things I had to clear as well for it to work
oh and yeah the download link for fastboot is no long working in the one guide you gave me to follow so not sure if I already have what it is talking about
Click to expand...
Click to collapse
Its simple lol. When you download the firmware from asus, its usually in a .zip form. In it, there is another zip file. Copy that zip file onto your tablet and flash it with twrp.

crazynitro said:
Its simple lol. When you download the firmware from asus, its usually in a .zip form. In it, there is another zip file. Copy that zip file onto your tablet and flash it with twrp.
Click to expand...
Click to collapse
what about having to clear anything? I could of swore the instructions showed going to 2 or 3 spots for clearing data or info or something from the unit

allusion said:
what about having to clear anything? I could of swore the instructions showed going to 2 or 3 spots for clearing data or info or something from the unit
Click to expand...
Click to collapse
Yes. You have to do a factory reset first.

and how do I do that lol, and what happens when I don't do that first

is this tablet now dead since the step of doing the reset was not complete? cause now I can not access twrp and it just sits there with the asus logo and the swirling dots
when I try to access the usb option all I have is rck, android and wipe, rck just gives a failure shortly after trying

allusion said:
lol, and how do I do that using the twrp?
can't find any detailed instructions on using twrp on flashing a rom, especially the stock one
i'm sure there is a set of detailed instructions cause I swore I saw one once
but i'm not able to find it again
cause I thought besides using the install part there were things I had to clear as well for it to work
oh and yeah the download link for fastboot is no long working in the one guide you gave me to follow so not sure if I already have what it is talking about
Click to expand...
Click to collapse
If you want to use twrp, download the us stock firm ware. when you open it, you'll see a file that looks like this: "US_epad-user-10.6.1.15.3". copy that file onto your tablet and flash it like a normal rom. haha
For fastboot, if you have the android sdk, then you already have fastboot so you dont have to download fastboot again.
---------- Post added at 03:36 PM ---------- Previous post was at 03:32 PM ----------
allusion said:
is this tablet now dead since the step of doing the reset was not complete? cause now I can not access twrp and it just sits there with the asus logo and the swirling dots
when I try to access the usb option all I have is rck, android and wipe, rck just gives a failure shortly after trying
Click to expand...
Click to collapse
if you tried installing the newest firmware, you wont see the usb icon when you press power and volume+ it automatically enters fastboot. you dont have to select anything
---------- Post added at 03:39 PM ---------- Previous post was at 03:36 PM ----------
allusion said:
and how do I do that lol, and what happens when I don't do that first
Click to expand...
Click to collapse
if you cant enter twrp, then you dont have to worry about the factory reset you can flash the stock rom using fastboot.

Cant update phone/flash with odin/root

*Copied mostly from my topic on AndroidForums*
/*from June 27th, thread start*/
So I found out that on the 25th or 26th there was an update for the Verizon GS3. Every time I try to update, it gives me this error (see below) after it reboots. I should also probably note that when it reboots, you briefly see "Booting into recovery" in the top left corner, though it doesn't actually boot into recovery. I was rooted, but I did a full unroot with SuperSU, and it still doesn't work. I dont want to flash a stock image because of all my app data that I do not want to lose.
Here is what the update screen looks like: i . imgur. com/oC04moq.png
And after the "update": i . imgur. com/oC04moq.png
Scroll down a little bit on that same box: i . imgur. com/iSqwQl0.jpg
Please someone help me! This is driving me crazy!
/End post 1\
Click to expand...
Click to collapse
/revive post October 6th\
So its been about 3 months now. Problem still persists. Again, I can not flash anything with ODIN(307), or update the phone. I have tried with Kies and in the phone. I can boot into download mode and recovery mode fine. Any help would again be greatly appreciated. I don't have access to my pc atm but any suggestions are still appreciated.
*The phone runs flawlessly, I just want to be able to root again *
/end post
Click to expand...
Click to collapse
/suggestion from user
"I would wind this back to the start.
It may not be just a phone issue. Uninstal kies and any android drivers and reboot.
Try this first:
★[8/27] [Casual] [Root, Unlock, Recovery] Vzw S3 Toolkit or 1-Click!! [ALL OTA's]★ - xda-developers
For the Verizion only. Anyone else thinking of using this start a new thread!!"
Click to expand...
Click to collapse
and my respose after trying: gyazo . com/3827e1487bf8cb3aeb0871b946fde785.png
Been on this for about 10mins, videos I have seen have done nearly instantly. I don't want to disconnect anything...
EDIT: I tried again twice. Same issue. I'm going to uninstall all drivers etc and try again.
Nup, still not working. Any more suggestions?
So far I have tried:
Odin(for root)
Kies(for updating)
Casual
Uninstalling kies/drivers and reinstalling and retrying all
All recognize the device, but nothing happens.
Click to expand...
Click to collapse
Now I'm here. I've never seen or heard anything like this before. Please post any suggestions you might have. I am down to try almost anything.
Sorry if I'm breaking any rules or anything. I just want this resolved.
And sorry for long post.

I'm assuming you've done all this with the same USB cable? Try a different cable (preferably the included one), different usb port, and also a different computer.
Sent from my SCH-I535 using Tapatalk 4

I can't even tell what is going on, this post is very confusing. Is Odin giving a fail message?
1. Odin should work, if it doesn't in a normal circumstance, then this method will work http://forum.xda-developers.com/showthread.php?t=1840030. This is will wipe all your data, but you'll be good to go from there.
2. Why did you unroot through super su? What rom are you running right now?
3. You can try using this image:
http://forum.xda-developers.com/showthread.php?t=1974114, then after you do this method you can run casual and root from there, while preserving your data.
Sent from my SCH-I535 using Tapatalk 2

Thanks to both of you!!!!!! I used a different port on my PC, and used the nowipe image BadUsername posted, and now I'm rooted, custom recovery, unlocked bootloader, and no data loss!! Again, thank you so much.

:highfive: yea teamwork! And last thing I'll suggest is to backup your IMEI if you haven't done so before.

[Q] Galaxy Note 1 I717 Stock Flash won't fix boot loop

I received a Galaxy Note 1 I717 (AT&T) and it was in a bootloop. I have experience with flashing stock roms through Odin and fixing bootloops that way. So after going through recovery mode, wiping, flashing, I am still getting put into a bootloop after a successful flash on Odin. I've spent 2 days with this and tried all the little suggestions of wiping before flashing, using the original roms from XDA , trying some other stock roms specifically for my model and I'm still left with a bootloop. I'm capable of getting into download and recovery, and I've actually gotten different stock recovery modes! So the flashes are working, but it just won't boot up correctly. I looked around for the U.S. version of the Pit CSC Phone and PDA to try and re partition it, but they are absolutely NOWHERE! Any help would be greatly appreciated, whether it's a ROM suggestion, the re partition files, or whatever else.

Charles Sparkley said:
I received a Galaxy Note 1 I717 (AT&T) and it was in a bootloop. I have experience with flashing stock roms through Odin and fixing bootloops that way. So after going through recovery mode, wiping, flashing, I am still getting put into a bootloop after a successful flash on Odin. I've spent 2 days with this and tried all the little suggestions of wiping before flashing, using the original roms from XDA , trying some other stock roms specifically for my model and I'm still left with a bootloop. I'm capable of getting into download and recovery, and I've actually gotten different stock recovery modes! So the flashes are working, but it just won't boot up correctly. I looked around for the U.S. version of the Pit CSC Phone and PDA to try and re partition it, but they are absolutely NOWHERE! Any help would be greatly appreciated, whether it's a ROM suggestion, the re partition files, or whatever else.
Click to expand...
Click to collapse
A bad kernel can be the cause of this problem. Try and search for a custom kernel for your device and flash it.
I hope this will solve your problem.

Ibrahim9999 said:
A bad kernel can be the cause of this problem. Try and search for a custom kernel for your device and flash it.
I hope this will solve your problem.
Click to expand...
Click to collapse
I already tried flashing the stock Rom then flashed the kernel and got boot loops still from this XDA page http://forum.xda-developers.com/showthread.php?t=1506330 . Having a lot of trouble with this one.

Charles Sparkley said:
I already tried flashing the stock Rom then flashed the kernel and got boot loops still from this XDA page http://forum.xda-developers.com/showthread.php?t=1506330 . Having a lot of trouble with this one.
Click to expand...
Click to collapse
OK, download these files and put them on your device:
Rom: http://goo.gl/81TamM
Gapps (important!): http://goo.gl/ws5KZF
Then follow these steps exactly:
1. Boot to recovery (CWM or whatever you use)
2. Wipe data/factory reset
3. Wipe Cache
4. Wipe Dalvik cache (advanced-> wipe dalvik cache)
5. Flash rom
7. Flash the gapps
This must work, if it doesn't, please say it, maybe I can help you further.

Ibrahim9999 said:
OK, download these files and put them on your device:
Rom: http://goo.gl/81TamM
Gapps (important!): http://goo.gl/ws5KZF
Then follow these steps exactly:
1. Boot to recovery (CWM or whatever you use)
2. Wipe data/factory reset
3. Wipe Cache
4. Wipe Dalvik cache (advanced-> wipe dalvik cache)
5. Flash rom
7. Flash the gapps
This must work, if it doesn't, please say it, maybe I can help you further.
Click to expand...
Click to collapse
My bad for not properly explaining my situation, the note is stuck in a boot loop. So I can't upload files to it through drag and drop in USB. It's still capable of flashing through Odin and going into recovery with CWM, but there's no way I know of putting files onto a boot looping phone.

Charles Sparkley said:
My bad for not properly explaining my situation, the note is stuck in a boot loop. So I can't upload files to it through drag and drop in USB. It's still capable of flashing through Odin and going into recovery with CWM, but there's no way I know of putting files onto a boot looping phone.
Click to expand...
Click to collapse
Doesn't the Galaxy Note 1 I717 has a MicroSD-Card Slot?
I tought it had one..

Ibrahim9999 said:
Doesn't the Galaxy Note 1 I717 has a MicroSD-Card Slot?
I tought it had one..
Click to expand...
Click to collapse
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?

Charles Sparkley said:
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?
Click to expand...
Click to collapse
Yes of course, or put the files with a computer on the SDCard.
If you've put the files onto the SDCard, insert it to your Note, and follow the steps on my previous post.

Charles Sparkley said:
Oh it does, would I just put those files onto a good sd card via a working phone and THEN put it into the Note?
Click to expand...
Click to collapse
Did it work?

Ibrahim9999 said:
Did it work?
Click to expand...
Click to collapse
Just got an extra SD card my friend is letting me borrow. I'm going home tonight, putting the files on, and going to try to flash it. I'll tell you how it goes!

Charles Sparkley said:
Just got an extra SD card my friend is letting me borrow. I'm going home tonight, putting the files on, and going to try to flash it. I'll tell you how it goes!
Click to expand...
Click to collapse
OK, hope the best for you!

Ibrahim9999 said:
OK, hope the best for you!
Click to expand...
Click to collapse
Alright, so on my good phone I threw the 2 zips on my extra SD card. Then I put that SD card in the note, went into CWM, wiped the necessary areas as you said, and the dead android with a red triangle appeared. It's a long error, but the end says Error in /sdcard/cm-10.1.3-quincyatt.zip
(Status 7)
Installation aborted.
Are you sure you gave me the right ROM to install?

Charles Sparkley said:
Alright, so on my good phone I threw the 2 zips on my extra SD card. Then I put that SD card in the note, went into CWM, wiped the necessary areas as you said, and the dead android with a red triangle appeared. It's a long error, but the end says Error in /sdcard/cm-10.1.3-quincyatt.zip
(Status 7)
Installation aborted.
Are you sure you gave me the right ROM to install?
Click to expand...
Click to collapse
Status 7 means the device is incompatible, but that's impossible since we have the right ROM for your device.
OK just be sure, I'll give you another ROM and you must follow the other steps, but with the different files of course.
ROM: http://downloadandroidrom.com/file/...CARBON-JB-NIGHTLY-20131015-0513-quincyatt.zip
Google Apps: http://downloadandroidrom.com/file/gapps/gapps-jb-20130813-signed.zip
This is an Android 4.3.1 ROM so you're really up to date with this one.
Put these on a SD Card and follow the given steps in my other post.
This one has to work.

Ibrahim9999 said:
Status 7 means the device is incompatible, but that's impossible since we have the right ROM for your device.
OK just be sure, I'll give you another ROM and you must follow the other steps, but with the different files of course.
ROM: http://downloadandroidrom.com/file/...CARBON-JB-NIGHTLY-20131015-0513-quincyatt.zip
Google Apps: http://downloadandroidrom.com/file/gapps/gapps-jb-20130813-signed.zip
This is an Android 4.3.1 ROM so you're really up to date with this one.
Put these on a SD Card and follow the given steps in my other post.
This one has to work.
Click to expand...
Click to collapse
Hate to say it, but installed the new ROM file and got the same exact message. Right now I'm on CWM-based Recovery v5.5.0.4 and I flashed to stock before this, thanks for all of the help so far. Any suggestions?

Charles Sparkley said:
Hate to say it, but installed the new ROM file and got the same exact message. Right now I'm on CWM-based Recovery v5.5.0.4 and I flashed to stock before this, thanks for all of the help so far. Any suggestions?
Click to expand...
Click to collapse
Do you know for sure you're on a Galaxy Note i717 AT&T?
Because 2 roms incompatible is almost impossible.

Ibrahim9999 said:
Do you know for sure you're on a Galaxy Note i717 AT&T?
Because 2 roms incompatible is almost impossible.
Click to expand...
Click to collapse
Sorry for not getting back in a while, thanks for all the effort you've been putting into helping out.
I'm 100% positive, I'm looking at the back below where the battery goes and it says SGH-I717. I thought that model number meant for sure it was AT&T. I live in the states also if that helps.

Charles Sparkley said:
Sorry for not getting back in a while, thanks for all the effort you've been putting into helping out.
I'm 100% positive, I'm looking at the back below where the battery goes and it says SGH-I717. I thought that model number meant for sure it was AT&T. I live in the states also if that helps.
Click to expand...
Click to collapse
But don't you think it's maybe a Chinese replica with a different kernel?
If you got it cheap, that might be the case.
And can you please thank my posts?
Because the few clicks you do, help me a lot

Ibrahim9999 said:
But don't you think it's maybe a Chinese replica with a different kernel?
If you got it cheap, that might be the case.
And can you please thank my posts?
Because the few clicks you do, help me a lot
Click to expand...
Click to collapse
No it was definitely bought in the US, legit from a phone store.

Charles Sparkley said:
No it was definitely bought in the US, legit from a phone store.
Click to expand...
Click to collapse
So, for my understanding, you bought it new from the store and rooted it and then got in a bootloop?
Can you please tell me how you came in the bootloop, did you get it with flashing a ROM or a kernel etc.?

Ibrahim9999 said:
So, for my understanding, you bought it new from the store and rooted it and then got in a bootloop?
Can you please tell me how you came in the bootloop, did you get it with flashing a ROM or a kernel etc.?
Click to expand...
Click to collapse
I bought it from a friend because they had it in a boot loop. Everything on it was completely stock since they were your average user, I'm pretty sure this isn't a hardware issue either if that helps because randomly after flashing CWM one time it actually booted up and I was able to use the phone. But after rebooting, it bootlooped again :\. I haven't been able to replicate this again sadly.

Installed TWRP on StraightTalk SCH-S968C Samsung Galaxy S III - now no OS! - resolved

I have a rooted StraightTalk SCH-S968C Samsung Galaxy S III (with the stock AOSP ROM) that I just screwed up. I had used EZ-Recovery to flash TWRP 2.2.0 to the phone. Now TWRP says there is no OS! I can only boot into TWRP - nothing else. It won't even let me power-down the phone. Is there some way I can recover from this, or do I now have a very expensive electronic brick (that runs TWRP)? I have adb installed on my laptop and I know it works, so that's one possible route to recovery. Any help would be much appreciated!

ScottDB said:
I have a rooted StraightTalk SCH-S968C Samsung Galaxy S III (with the stock AOSP ROM) that I just screwed up. I had used EZ-Recovery to flash TWRP 2.2.0 to the phone. Now TWRP says there is no OS! I can only boot into TWRP - nothing else. It won't even let me power-down the phone. Is there some way I can recover from this, or do I now have a very expensive electronic brick (that runs TWRP)? I have adb installed on my laptop and I know it works, so that's one possible route to recovery. Any help would be much appreciated!
Click to expand...
Click to collapse
I'm pretty sure it's possible to return it completely to stock with the COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5 file through Odin. I just to happen to have the file right here.. small warning though, it's 1.2 gigs.
https://mega.co.nz/#!gRI3DD5L!dRW8ORzfQI5j1JyKHVBTNifomPCXoqL14B9GF4oxvQY

aekel87 said:
I'm pretty sure it's possible to return it completely to stock with the COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5 file through Odin. I just to happen to have the file right here.. small warning though, it's 1.2 gigs.
https://mega.co.nz/#!gRI3DD5L!dRW8ORzfQI5j1JyKHVBTNifomPCXoqL14B9GF4oxvQY
Click to expand...
Click to collapse
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!

Deleted.

ScottDB said:
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Click to expand...
Click to collapse
Thank you!!!! I just had the same problem. However even when using cwm i get errors in the recovery. Unable to mount anything or do anything besides reboot. Any ideas?

need stock Firmware
Have any idea where i can get this file? Ive bricked my phone too. Durnnit!

iamwaynes said:
Have any idea where i can get this file? Ive bricked my phone too. Durnnit!
Click to expand...
Click to collapse
This is the h1 stock you need. type this in google you should find the download if not I have it.
COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV0
Dont use e-z recovery. I had the same problem neither cwm or twrp from ez recovery worked and then cwm said no os on my phine so I flashed that file from download mode and was back to stock.

How did u find a recovery that worked mine is saying the same thing
Sent from my SM-N900T using Tapatalk

iamwaynes said:
How did u find a recovery that worked mine is saying the same thing
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1771398
In that thread go down to method 2 of getting a custom recovery. I downloaded cwm touch from the link there and then installed it with android terminal emulator using the codes that it says to type in. I tried to look up that stock rom but I didnt find it. Its on the forum somewhere in a thread about how to root the straight talk s3 and how first you need to download and flash the h1 baseband stock rom

Thanks I found the stock rom fixing it now.
Sent from my SM-N900T using Tapatalk

iamwaynes said:
Thanks I found the stock rom fixing it now.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Ok I've re rooted and tried to install recovery. Odin put it in wrong place. Says no operating system . What now?
Sent from my SM-N900T using Tapatalk

iamwaynes said:
Ok I've re rooted and tried to install recovery. Odin put it in wrong place. Says no operating system . What now?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Have you gotten recovery installed and straightened out yet?
Let me know if you need some help, tell me where you're at and what you've got going on with what you have.

I returned phone to stock. The recovery wasn't in the right place obviously. So that's where I am . Stuck back at stock. Thanks for any help you can give.
Sent from my SM-N900T using Tapatalk

iamwaynes said:
I returned phone to stock. The recovery wasn't in the right place obviously. So that's where I am . Stuck back at stock. Thanks for any help you can give.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Are you on stock not rooted or you are rooted?
Do you have stock recovery or custom.
I can get you to wherever you need or want. Tell me what you need or where you'd like to be.

Droidriven said:
Are you on stock not rooted or you are rooted?
Do you have stock recovery or custom.
I can get you to wherever you need or want. Tell me what you need or where you'd like to be.
Click to expand...
Click to collapse
I have combined 2 s3's to make one good one. This is the proper thread for the model of the chipset. The phone has been worked on buy someone who only thought they were a genious. I've found traces and from surfing the forums I'm pretty sure I know what they did even. I'm gonna grab these stock images and flash back to stock. I just wanted to put a word in now to see how dead this thread is. BTW just for the record easy safe root is achievable with safroot for Att g s 4. I've confirmed that. Root is no issue. Modem drivers are jacked up. I want what I have now with WiFi in tact and custom recovery. Just wanted to get the word in in case I hit a wall with recovery as I am now before the flash to stock. Thanks in advance for any help. Sorry for the ramble
---------- Post added at 07:23 AM ---------- Previous post was at 07:03 AM ----------
ScottDB said:
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Click to expand...
Click to collapse
Does anyone have a good link for h1 stock. All the links I can find including aa51 are dead. I need to go stock to fix the modem. I can handle everything from there I just need stock and I've trolled XDA , aa51, and several others. All links are dead. Probably for a long long time . any help is greatly appreciated
---------- Post added at 07:42 AM ---------- Previous post was at 07:23 AM ----------
sazendrak said:
I have combined 2 s3's to make one good one. This is the proper thread for the model of the chipset. The phone has been worked on buy someone who only thought they were a genious. I've found traces and from surfing the forums I'm pretty sure I know what they did even. I'm gonna grab these stock images and flash back to stock. I just wanted to put a word in now to see how dead this thread is. BTW just for the record easy safe root is achievable with safroot for Att g s 4. I've confirmed that. Root is no issue. Modem drivers are jacked up. I want what I have now with WiFi in tact and custom recovery. Just wanted to get the word in in case I hit a wall with recovery as I am now before the flash to stock. Thanks in advance for any help. Sorry for the ramble
---------- Post added at 07:23 AM ---------- Previous post was at 07:03 AM ----------
Does anyone have a good link for h1 stock. All the links I can find including aa51 are dead. I need to go stock to fix the modem. I can handle everything from there I just need stock and I've trolled XDA , aa51, and several others. All links are dead. Probably for a long long time . any help is greatly appreciated
Click to expand...
Click to collapse
Finally found it here
https://forum.xda-developers.com/showthread.php?t=2516498&page=28