[Bricked] Chinese SGT p1000 Bricked after flashing JQ1 - Galaxy Tab Q&A, Help & Troubleshooting

I modified this post to recap the whole story. You can find the timeline development from the second post on.
My TAB is now bricked, it does not give any sign of life even after letting it charging for hours.
Not Odin or heimdall would recognize it to I cannot flash anything.
Samsung Mexico (where I am now) told me they cannot fix it because the mexican version has a different hardware configuration.
I also called Samsung US and they told me they cannot accept it, I should go back to china and repair it there (??).
I decided not to waste my time anymore on this, as it become anti economic.
(if anyone is interested in buying it as spare-parts, please let me know!)
what happened, for reference:
Chinese unicom GST p1000, previously flashed (and running) with success roto-JME.
I tried to flash JQ1 with bootloaders but ODIN failed at hidden.rfs. Since then I never manage to boot the tab anymore.
I then couldnt flash any ROM containing either hidden.rfs or movinand.mst, it would always FAIL. In order to PASS I had to remove these two from the flash, but TAB will hang at Samsung logo during boot (not sure if the reason for not booting is because of the missing files, or these 2 problems have the same cause, but are not related with eachother).
I tried a huge number of different ROMs, all give same results (even JME will fail at movinand.mst now)
in case you are wondering I already tried different computers, win and ubuntu, Odin and heimdall, changed USB cables, always the same problem.
Given the above situation (base ROM not complete and not booting + /data unmountable) I managed anyway to install Overcome and AF974, but they both hung at GALAXY TAB boot screen (the very first one) and keep rebooting every few seconds. (This is different from when it hangs at samsung logo - see above)
After this recovery started to report partition errors:
I cannot mount /DATA in either CWM or ADB , it says:
mounting /dev/block/mmcblk0p2 on /data failed: No such file or directory
indeed /dev/block/mmcblk0p2 does not exist.
I tried the flashing routine again, and new different partition errors came up
now the internal sd-card was not mountable anymore, instead it would read ext-sd as internal
I tried the flashing routine again, and it bricked completely to death
What I DIND'T do (learned about it too late!) prior to flash JQ1 was to neither ROOT or patch bootloaders before flashing, but I belive I should be ok:
I flashed JME successfully in the past and should be pre-rooted.
I also have reasons to think my bootloaders are not protected as:
I tried chainfire's SGTBootloaderCheck-1.0,it says I am clean.
I can flash CF-root, which is supposed to fail on protected bootloader.
I was brave and stupid enough to format /boot from recovery. Tab would not boot but I could flash it back from Odin with no problems (still, flashed an incomplete ROM without hidden.rfs)

i also tried other ROMS, but have the same problem with all of them
I tried chainfire's SGTBootloaderCheck-1.0 while on recovery mode, but it says I am clean
I cannot get out of this brick, can anyone point me in the right direction?

I'm not the one with the answers, but I casually saw these two posts hours ago:
How to unbrick tabs:
http://forum.xda-developers.com/show....php?t=1133590
This unlocks bootloaders so your SamFirmware.com rom won't brick you:
http://forum.xda-developers.com/showthread.php?t=888071

thanks but I have already seen and tried all of these.
The most commune solution to a soft brick in the forum is: "flash again".
but in my case it seems I just cannot flash anything.
Perhaps what I am looking for is a method/checklist to diagnostic the source of my problem?
or should I just keep trying flashing every possible rom? (i already tried at least 9)

2 cents
Hi,
First of all, get AF974's ROM and also his kernel and the modem for your region. Put these zips on your external SD.
Get into recovery : mount every single thing you can mount, then format every thing (use ext4 if possible). Without leaving recovery, flash the kernel , then the ROM and finally the modem. Reboot and wait ...

thank you but I'd need more directions..
dirlan2001 said:
First of all, get AF974's ROM and also his kernel and the modem for your region. Put these zips on your external SD.
Get into recovery : mount every single thing you can mount, then format every thing (use ext4 if possible). Without leaving recovery, flash the kernel , then the ROM and finally the modem. Reboot and wait ...
Click to expand...
Click to collapse
Thank you. this is a new approach and definitively worth trying it.
I would need more directions thou, as I only can flash roms using odin.
Are you saying I can flash this ROM from the recovery mode, I don't need Odin?
I am a bit confusing about the process: you are saying: 1) mount everything 2) format 3) flash.
1. What do you mean my 'mounting'?
when I go to my recovery mode i can see the option 'apply update from sdcard'. Is this what you mean by mounting?
2. Then format everything. what and how? you mean the SDcard? I am not aware of anything else I could be formatting. Please precise.
3. then flash everything.
how is flash different by Mounting, in this case? havent I already 'applyed' these files in step 1?
I am sorry if all these questions sounds idiot, I probably miss a lot of basic knowledge. I swear I did my homework, I spent DAYS reading all the forums. It's just hard to catch up everything from stratch without help.
thank you!!

i think i got it
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?

jacopo3001 said:
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
Click to expand...
Click to collapse
Hi,
Seems you got a old CWM (probably 3.x) that came with Roto"s ROM. Anyway, if you got the files I previously mentioned, make a copy of the kernel.zip and rename it into update.zip, put that 'new' update zip on your SD (eventually replacing the old one) and fire up CWM, running the 'update from SD'.
After reboot you should have a newer CWM that has more options to it. Note that the reboot may take some time... Then you can use the 'mount' to get all partitions mounted r/w... Then you run the kernel.zip and the ROM.zip from 'install zip from SD | go to external SD | choose the kernel.zip // redo the same for the ROM.zip without rebooting in between'

jacopo3001 said:
I think I got why I dindt understand your previous post:
I dont have thoese options in Recovery.
The only things I see are:
Reboot, apply update from sdcard, wipe data, wipe cache.
This phone was originally working with Roto-JME and then bricked while flashing JQ1. I am not sure which version does this recovery belongs to.
Can I still do anything with this version of recovery?
Click to expand...
Click to collapse
This sounds like you are in stock recovery and need cwm installed again.
________________________
Sent from my DROIDX X

dirlan2001 said:
Seems you got a old CWM (probably 3.x) that came with Roto"s ROM. Anyway, if you got the files I previously mentioned, make a copy of the kernel.zip and rename it into update.zip, put that 'new' update zip on your SD (eventually replacing the old one) and fire up CWM, running the 'update from SD'.
Click to expand...
Click to collapse
thank you I will try later tonight.
yesterday I was quite desperate and sent the tab in to the local samsung assistance center, and they just called me they couldnt fix it!
Tonight as I get it back I will try this approach and will let you know.
thanks

jacopo3001 said:
thank you I will try later tonight.
yesterday I was quite desperate and sent the tab in to the local samsung assistance center, and they just called me they couldnt fix it!
Tonight as I get it back I will try this approach and will let you know.
thanks
Click to expand...
Click to collapse
On second thought, it may even be better to install the Overcome kernel first. That has the most recent version of CWM build in, and it makes your device ext4 instead of the old RFS. After that you easily can flash AF974's combo via CWM, whitout need to rename/copy anything. The link provides the guide to the mirror of OC, as their website isn't working anymore...

dirlan2001 said:
it may even be better to install the Overcome kernel
Click to expand...
Click to collapse
I have tried to flash GB-Stock-Safe-v5 (as for Overcome's docs) with Odin but it fails, just like all the other flashes I tried.
Btw, I just discovered that on the back of my TAB (chinese unicom) is written WCDMA. As I always used GSM cards with it I always assumed it was a GSM version, but now I am getting the doubt.
can you confirm I am on GSM version?
the full specs written on the back case are:
WCDMA无线数据终端 (wireless data terminal)
Model:GT-P1000
CMIIT 10 2010CP4950

jacopo3001 said:
I have tried to flash Overcome with Odin before but it fails, just like all the other flashes I tried in this period.
Btw, I just discovered that on the back of my TAB (chinese unicom) is written WCDMA. As I always used GSM cards with it I always assumed it was a GSM version, but now I am getting the doubt.
can you confirm I am on GSM version?
the full specs written on the back case are:
WCDMA无线数据终端 (wireless data terminal)
Model:GT-P1000
CMIIT 10 2010CP4950
Click to expand...
Click to collapse
Hi,
WCDMA is the 3.5G data-line : this means, it's NOT the WiFi alone version. If it's marked as P1000 just as is, then it's the GSM version. That means, you have EDGE/GPRS quadband @ 850/900/1800/1900 Mhz and HSDPA 7.2Mb/s=HSUPA 5.7 Mb/s triband @ 900/1900/2100 Mhz ...
Hmmm, what error did Odin give out when the flash failed ?
BTW, happy newyear etc ...

dirlan2001 said:
BTW, happy newyear etc ...
Click to expand...
Click to collapse
Happy new year to you, and that you very much for your help!
dirlan2001 said:
Hmmm, what error did Odin give out when the flash failed ?
Click to expand...
Click to collapse
Basically it's always the same error, no matter which ROM i flash.
it always fails at either Hidden.rfs or Movinand.mst, depending on the ROM.
here is how it looks like when I try GB-Stock-Safe (recommended by Overcome) for example:
Code:
<ID:0/018> Firmware update start..
<ID:0/018> boot.bin
<ID:0/018> cache.rfs
<ID:0/018> dbdata.rfs
<ID:0/018> factoryfs.rfs
<ID:0/018> movinand.mst
<ID:0/018>
<ID:0/018> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
If I remove these files (Hidden.rfs or Movinand.mst) from the TAR i can flash with no errors, but the tablet wouldn't boot.
This apply to EVERY Roms i tried so far, with no exclusion.
I am making up a new theory: the first bricking error happened after I flashed JQ1, which has bootloaders. Could it be that those bootloaders go in conflicts with the chinese version of hardware, and thefore the brick?
I am keep trying flashing different combinations of ROM's, I am just afraid to get worst... :S

jacopo3001 said:
Happy new year to you, and that you very much for your help!
Basically it's always the same error, no matter which ROM i flash.
it always fails at either Hidden.rfs or Movinand.mst, depending on the ROM.
I am keep trying flashing different combinations of ROM's, I am just afraid to get worst... :S
Click to expand...
Click to collapse
Hi,
No thanks, you're welcome LOL
The problem seems indeed the bootloaders playing up. I guess you'll need to try repair them with this thread from the same guy that made this thread
I suggest you try to repair the lot via the guides he gives to get a up and running again. After that you can retry to install AF974's latest...
Cheers, and good luck

dirlan2001 said:
The problem seems indeed the bootloaders playing up. I guess you'll need to try repair them with this thread from the same guy that made this thread.
I suggest you try to repair the lot via the guides he gives to get a up and running again. After that you can retry to install AF974's latest...
Click to expand...
Click to collapse
thanks, I know those threads already (read them all!)
the main problem I don't get about the bootloader fix is that chainfire released a APK, which assume you can boot the phone!
He starts the thread saying his phone was bricked and cannot flash anything on it, then he fixes it with a APK! that got me lost, how to get out of the brick first?
regarding AF974, that's not my priority, I am just trying to have this thing working again..

jacopo3001 said:
He starts the thread saying his phone was bricked and cannot flash anything on it, then he fixes it with a APK! that got me lost, how to get out of the brick first?
Click to expand...
Click to collapse
Hi,
He did a 200 mile trip to have the MoBo changed .. LOL That doesn't help you any further I guess...
Did you try to put the renamed kernel.zip and flash that through CWM as I previously proposed ? What is the outcome ? Or eventual errors ?
PS : as long as you can get it in download mode (odin) or CWM it's not a brick, it just not booting completely...

dirlan2001 said:
Hi,
Did you try to put the renamed kernel.zip and flash that through CWM as I previously proposed ? What is the outcome ? Or eventual errors ?
Click to expand...
Click to collapse
I chickened out last minute!
I could upgrade to a latest version of CWM by simply flashing CF-ROOT with odin.
but I was not sure about proceeding mounting Overcome's kernel:
OC's documentation raccomends to mount on a clean and functioning install of JQ1 (which i dont have) and says that its kernel will automatically convert the formatting to ext4.
I am not sure it's a good idea to convert formatting while at this situation.
Would I be able to revert in case something goes wrong?
What do you think?

jacopo3001 said:
I chickened out last minute!
I could upgrade to a latest version of CWM by simply flashing CF-ROOT with odin.
but I was not sure about proceeding mounting Overcome's kernel:
OC's documentation raccomends to mount on a clean and functioning install of JQ1 (which i dont have) and says that its kernel will automatically convert the formatting to ext4.
I am not sure it's a good idea to convert formatting while at this situation.
Would I be able to revert in case something goes wrong?
What do you think?
Click to expand...
Click to collapse
Hi,
Do I understand correctly your system is up and running again ? In that case I would certainly recommend to run the complete guide to make it first stock again. The kernel indeed does a conversion to ext4, which is a way better filesystem as the rfs from Samsung. Look in the Overcome thread for the mirrors as OC seems still to have serious problems with their serversystem.
And if you take courage (and the habit) you might start looking for a more recent kernel and ROM...

dirlan2001 said:
Do I understand correctly your system is up and running again ?
Click to expand...
Click to collapse
The system is NOT up and running.
It's hanging at the Samsung logo.
But I can at least get to both download and recovery mode.
What happens is that, regardless which ROM I try, I cannot flash neither hidden.rfs nor movinand.mst (depending on Rom's content), they always FAIL on ODIN.
If I flash a ROM removing those 2 it Odin would success, but the tab will not Boot and hang at Samsung logo.
That's why I say the system is not stable now, I am not sure whether it's a good idea to go into changing FS now or would it screw up things even worst...

Related

[Q]-Verizon-GTab-How to return to stock

First off, I have searched and performed a few different recovery processes and my Tab is partially functional (FC's on a lot of apps)
I used Z4Root.
Next I used the Verizon_zImage to install CWR (converted to Ext4)
I installed the Dodexed Verizon from this forum
Everything ran fine for about a month
I started getting FC's on a lot of apps
Decided to revert to stock via this post: http://www.droidforums.net/forum/sa...84-how-restore-vzw-galaxy-tab-stock-dj11.html
Used Heimdall to flash the Cache, Param, factory, Kernel and Recovery
Following the directions, I booked into recovery (stock)
When I tried to wipe Data and Cache, is where the problems started
I get a bunch of errors about not being able to mount /Data
I have tried to get back to where I was with flashing the Verizon_zImage and wiping data and cache that way (seemed to work but all my apps and data are still there)
If someone can tell me how to get the Data wiped, I think I can get ther rest working...
Help please as I'm going to visit my brother this month and he's an Apple guy so I was going to show off how much better Android is...
Did you repartition with a PIT file? If you've gone to EXT4, I believe you need to repartition the device before you can go back to an RFS ROM.
Regards,
Dave
Can't find anything telling me how to do this or a PIT file for Verizon, so no. Kind of was thinking the same thing.
Anyone have a PIT file for a verizon Tab?
I screwed my tab using Verizon Tab Boostrapper from the market, trying to get to EXT4, it was already rooted with SuperOneClick; it booted into recovery and did a nandroid backup but i think failed the first time then tried to do some flashing then rebooted back into a nandroid backup finally completeing after what i think was a successful backup and EXT format. It may not be successful because when i try either of the md5 in Odin they both fail and i dont think i did enough research to find out how to push these files to the device yet.
After not reading what i should have nor having found a suitable stock verizon rom i tried relfashing with a JMF rom using odin which i am not sure if i jacked it even more but got it to boot to a different samsung startup screen but just hang up there, no carrier logo. Point being i can finally get back to a verizon startup screen after reformatting with P1_add_hidden.pit, it boots to a verizon logo and does the single single vibrate followed by a double vibrate i notice this thing doing everytime it fails with an app or software in general.
After trying this method with heimdall and all files in their right places as instructed by the first post i can flash in download mode but heimdall never tells me that the flash is successful even after waiting a good 10-15 minutes after the progress bars stop. Should it take this long to complete the flash?
Also, i know you said not to use any other files in heimdall but if i try using a CWM zImage file from the forums or even one i found for verizon, i can get heimdall to flash and say successful completed flash but it still vibrates and loops on startup. Any suggestions? Or can someone point me in the direction of how to restore my backup with heimdall?
I can boot into stock recovery and download mode, ive also tried to just flash the CWM from the CWM beta post with heimdall and it says successful flash but it still has stock recovery after reboot.
SUCCESS! ok so my brother has a vzw tab also, i used roto's backup method and backed up his device thru adb, i then heimdall with my bros factory.rfs, kernel(zImage), param.lfs, boot.bin, cache.rfs, dbdata.rfs, modem.bin and recovery(zImage) but got black screen of death so reformatted with P1_add_hidden.pit to get back to looping verizon logo, then back to download mode and this time i removed the kernel and recovery files and tried again which got me back to a verizon logo loop but then i tried a wipe data and wipe cache and WALA! tab booted right up, only missing modem (i think its modem bc i cant get carrier service) and menu/home/search buttons dont respond in android. CWM 3.0 flashes on both tabs but doesnt boot up to it so i used the galaxytabandclockworkmod combo found in these forums to get CWM 2.5.1 on it and am trying to restore from my odin claimed mismatched( but md5summer tells me they are good) nandroid backup, will post findings soon
cooljo555 said:
SUCCESS! ok so my brother has a vzw tab also, i used roto's backup method and backed up his device thru adb, i then heimdall with my bros factory.rfs, kernel(zImage), param.lfs, boot.bin, cache.rfs, dbdata.rfs, modem.bin and recovery(zImage) but got black screen of death so reformatted with P1_add_hidden.pit to get back to looping verizon logo, then back to download mode and this time i removed the kernel and recovery files and tried again which got me back to a verizon logo loop but then i tried a wipe data and wipe cache and WALA! tab booted right up, only missing modem (i think its modem bc i cant get carrier service) and menu/home/search buttons dont respond in android. CWM 3.0 flashes on both tabs but doesnt boot up to it so i used the galaxytabandclockworkmod combo found in these forums to get CWM 2.5.1 on it and am trying to restore from my odin claimed mismatched( but md5summer tells me they are good) nandroid backup, will post findings soon
Click to expand...
Click to collapse
Any chance you could post the files, there are a lot of us stuck at verizon logos without other tabs to copy data from haha.
Thanks in advance!!!
After all the things I tried, I gave in and took it back to Verizon (still within the year Sansung warranty) . I'll have a new one either tomorrow or Monday. Once I get it, I'll preform Roto's backup via command line and get all the required files if they are not posted first. If I read Roto's command strings correctly, I can even get the .pit file so we should be covered.
Like I said, if cooljo555 doesn't post these I'll work on posting them when I get my new device...
MrCheetah said:
Any chance you could post the files, there are a lot of us stuck at verizon logos without other tabs to copy data from haha.
Thanks in advance!!!
Click to expand...
Click to collapse
rjansen110 said:
After all the things I tried, I gave in and took it back to Verizon (still within the year Sansung warranty) . I'll have a new one either tomorrow or Monday. Once I get it, I'll preform Roto's backup via command line and get all the required files if they are not posted first. If I read Roto's command strings correctly, I can even get the .pit file so we should be covered.
Like I said, if cooljo555 doesn't post these I'll work on posting them when I get my new device...
Click to expand...
Click to collapse
Please post these file when you get the chance! I would really appreciate it!
The stock files are posted here
Hello everyone,
All the files are here in the XDA-Developers, in advance I'll like to apologize if I am breaking any rules by adding the link:
http://forum.xda-developers.com/showthread.php?t=955342
I downloaded the files I just don't know how to flash them, including the pit.pit files, help please since my tab is severely broken and I need to flash all files to bring it back to factory.
I'll appreciate anybody helping me. I already tried with heimdall, but it will not do anything when I put the pit.pit file, I tried odin, but it does not work neither, since I don't have a tar file for this, I no matter what I do, if I created one it does not work. If the instructions to do this are included somewhere else, can you please point me in the right direction?

[Q] Stuck in Boot-Loop (Gingerbread,Juwe'sROM 4.0, CR-Root3.1, ext4)

Hi all,
I upgraded to Gingerbread and Juwe's ROM last night and all went well. That is until today when I ran the script to convert the filesystem to ext4. It rebooted into CWM and all seemed to go well except my phone is now stuck in a boot-loop. It gets as far as the initial "Galaxy S GT-I9000 Samsung" screen and then restarts to it every few seconds.
Background:
I followed the instructions as given in Juwes thread. Initially flashed XWJVB XEE firmware with bootloaders from this thread (this exact firmware I think) with re-partition,etc checked. After that I flashed CF-Root-XW_XEE_JVB-v3.1-CWM3RFS (no-repartition) and flashed ROM. ROM was working perfectly till I ran ext4.
Does anyone know of any way to fix this problem? I can boot into Download mode and CWM Recovery v3.0.0.5. I'm trying to avoid reflashing the ROM but if I can't get a solution soon I guess I'll just have to do that
Hmmm,
Are you able to get into recovery or download mode?
Edit: Just noticed you can.
Another question,
What did you use to convert to ext4?
Did you install Chainfire's ext4 addon?
electrotune1200 said:
Another question,
What did you use to convert to ext4?
Did you install Chainfire's ext4 addon?
Click to expand...
Click to collapse
Ya it's Chainfire's ext4 addon I used. Although it's just occurred to me that I think I used the one packaged with the ROM instead of the newest one from Chainfire's thread. Could it be an older version?
Yeah I really don't know about that. When we get the phone sorted, I would install his most recent addon to see if that's the issue.
As far as I know, you may only have 2 options.
First, you can try to do a factory reset in CWM.
If that fails, I'd start from the beginning, flashing with a 512 pit and re-partion.
electrotune1200 said:
Yeah I really don't know about that. When we get the phone sorted, I would install his most recent addon to see if that's the issue.
As far as I know, you may only have 2 options.
First, you can try to do a factory reset in CWM.
If that fails, I'd start from the beginning, flashing with a 512 pit and re-partion.
Click to expand...
Click to collapse
I was afraid you'd say that. Just got the phone setup as I wanted it
Just tried the factory reset in CWM and no joy. Guess I'll re-partition when I get home. Should probably be doing some work at the moment anyway
Sorry man,
Next time, set everything up after you convert it to ext4. Might save you another headache.
Also, make sure you have some free space on your internal sd card. I try to leave 1.5gb free for file system conversions.
Oh and,
get some work done already
Before you go and flash everything again.
Try flashing Chainfire's 3.1 kernal again. It might pull it out of the boot loop. Worth a shot though before starting all over.
Hopefully it works out for you without starting all over.
I tried reflashing the kernel but no joy. Just went with the complete reflash in the end. Was painless enough because I had everything set up to go from the night before
Thanks for all the help electrotune! Appreciate it

[Q] Stuck in bootloop...need help

So I updated the MIUI on my Cappy from whatever I had before to 2.3.30 that is GB 2.3.7 from this location:
http://miuiandroid.com/community/threads/archived-miui-versions-captivate-gb.16558/
I didnt care for it so I downloaded SlimICS. I downloaded the base and the cappy essentials. Put them both on my internal sd. I factory reset, wiped data, cache and system and dalvic, just as i do for every phone i work on. I ran the SlimICS base and now it keeps rebooting and going back into recovery and doing this:
Finding update package...
Opening update package...
Installing update...
Slim ICS
Once Slim ICS pops up, it reboots and does it all over. I can yank the battery and manually go into recovery, but if i try to boot it up normal, it goes back into the loop. I am on CWM 5.0.2.7 also.
So what did i miss?
GB bootloaders most likely missing - flash 'em using Heimdall. And SlimICS doesn't have modem. So. Flash my ROM for a change may be.
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
And you flashed the base and the cappy essentials right? Not just the base
Sent from my SGH-I897 using xda premium
korockinout13 said:
Sounds like you just need to flash again. You have to do that when you are going from GB to ICS, and vice versa I believe.
Click to expand...
Click to collapse
trying to flash again just put it back in the loop. And I read that that does happen alot going from GB to ICS on the Cappy. But for Slim it didnt work.
Wdustin1 said:
And you flashed the base and the cappy essentials right? Not just the base
Click to expand...
Click to collapse
I never could get that far because it was the base that I started to install and it got bootlooped on, everytime it restarted, it went back into recovery and started to run the base again, and repeated boot loop. I read somewhere that teamhacksung's rom would get me over the GB to ICS bridge. This one here:
http://forum.xda-developers.com/showthread.php?t=1363760
It did the bootloop to, but when i yanked the battery and went back in and installed it a 2nd time, it didnt restart and installed correctly. After that I installed SlimICS. But I dont like it as much as i thought i would and now when i try to reinstall teamhacksung ROM, it errors out during the beggining of the installation. The MD5 is still fine. I dont think it likes the version of CWM recovery that SlimICS installed. I know CWMR went to an older version when i went from teamhacksung to SlimICS.
Flash glitch kernel first. Also, don't use the builds from that thread, it is old. Just flash the latest CM9 nightly
Swyped from my ICS Samsung Captivate
Stuck in A boot loop after flashing paranoid rom to cappy i897
I downloaded all needed files to internal SD just as the (how to upgrade the captivate i897 to Paranoid ROM said to do )
wipe data factory reset,wipe cache,selected install zip zip>package (pa_captivatemtd-1.99-13AUGUST2012.zip, md5sum: cc03bacf0f07a94bf25b482d64b94e63) then it started boot looping / att screen twice then android guy ,, then falling over with exclamation point in the middle of him , let it go considering options of 3 button combo weren't working ,, beside guide said 5-10 min to install then it made it to devil kernel installed gapps >> (gapps-jb-20120726-signed.zip, md5sum: f62cfe4a827202899919fd932d5246d7) now back in the boot loop again>>
i did make a nandroid backup but cant seem to get into cwm recovery or download mode . I did follow that guide to a tee.
any help or suggestions on this i would greatly appreciated if this post in wrong spot sry im new.
Also stuck in bootloop reverting to Gingerbread
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Reply Back.
HG_User said:
I am also stuck in boot loop after attempting to restore back into Gingerbread.
Here's how I got in this mess: I had been running Gingerbread on my Captivate for several months (rooted). I decided it was time to try upgrading to Jelly Bean (cm9 version). I installed ClockworkMod Recovery and that appeared to be working, so I made a NANDroid and proceeded to install CyanogenMod on my phone.
It booted OK, but I didn't like it and figured I'd just revert by restoring my NANDroid. Only thing is, it didn't restore correctly and my phone was stuck at the initial AT&T "bars" screen.
So I attempted to reboot in recovery and restore my latest update.zip. This did not seem to help at all. My phone would just boot to the AT&T screen and be stuck there. I checked to see adb was reachable behind the scenes but it wasn't.
After that I loaded Odin 1.85, downloaded a copy of the stock Captivate ROM, unzipped it and loaded it to my ROM (using the method described in this link I'm not allowed to show you because I'm a new user), more or less.
Odin said it was successful, but the phone is now still stuck in a boot loop. The ClockworkMod Recovery options are gone from the recovery menu. Now it looks like my stock recovery menu. There are some diagnostics on the recovery screen:
-- Copying media files --
E: failed to mount /dbdata (Invalid argument)
E: copy_dbdata_media: Can't mont /dbdata
your storage not prepared yet. please use UI menu
for format and reboot actions.
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Installing Multi-CSC
Applied CSC-code 'ATT'
Successfully copied multi-CSC.
-----
the bold text indicating errors appears in orange.
I tried "wipe data/factory reset" and "wipe cache partition" and rebooting. This had no apparent effect. The Captivate still continues to loop on reboot.
What next? It seems like it's missing something it needs to boot that's not in the standard Gingerbread Captivate image I downloaded with Odin. What else do I need to do? Keep in mind that right now the only way I can get files onto the phone is Odin (or similar) via the USB port. The phone never gets booted enough to get to it with adb, let alone mounting as a drive on my computer.
Thanks
Click to expand...
Click to collapse
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out. ??
---------- Post added at 06:38 PM ---------- Previous post was at 06:27 PM ----------
321321wrick said:
While searching threw all this mess on this site and various other :
I did stumble on something that might help u get your cwm
mode Look up Captivate Q&A the scroll to T, Russel thread has file needed to get your cwm mode working using rageagaistcage method.
Odin has multi file upload for stock alone check to make sure you selected right one . then just reflash should be good
mine i examine really thoroughly and figure out i try to jump to high .
i had stock then firefly then darkfire which is based off i900 <> Cappy rom bad <>idea on my part i try to jump to paranoid rom from darkfire '
don't think files were save to SD internal card - download section instead so firmware lost track of it self .
reviewing errors made on my part order 2 jig for my 2 cappys
my plan use jig get into download flash back to stock using odin one click using kies flash to froyo and stick with it for another six months
while reading everything i need to know about flashing that high up , besides that rom will become more stable less bugs and it will give me
time to see what errors occurs with this phone model on that rom last time i check there was only 7 posted user using it
again i was trying to flash paranoid rom for Samsung captivate SGH_I897'' I hope you get your issue resolved.
If u try one click unbrick and on win xp uninstall kies the drivers will not work together log in to administrator account <> just Google it if not on welcome screen there a few ways to get into that account,, but that did work for me on my cappy . let me know how u make out.
There also Ginger Bread Boot loaders Needed for it to start up Correctly - i personally don't know that much bout gingerbread rom i didn't like it as much as froyo WiFi issues'' the the stock odin should erase all info on your part thou 'e use Is OCD 1 i897UCJF6>lowercase work every time for me.
cept now because my usb is not able to charge phone or enter download mode or recovery which leaves jig option .
Click to expand...
Click to collapse
HG_User,
U can't go back to GB (or froyo/eclair) from CM, MIUI, ICS, JB, AOSP etc., etc. without using Odin or Heimdall---because of the different partitions used---Stock firmware is bml/rfs and all the AOSP etc etc are mtd/yaffs(2).
And u can only restore a backup when u r back running the base rom where u made the back up.
Use this...Stock i897ucKK4 GB 2.3.5 with or without bootloaders... http://forum.xda-developers.com/showthread.php?p=18370912
This kk4 should get u going. Then u can use Odin to flash Corn Kernel to get a cwm back...:thumbup:
Sent from my SGH-I897 using xda premium
... one step on the way: Back to Eclair
thanks for the advice. Ultimately, I decided I should use Odin 3 1-click to revert back to original (2.1 Eclair) firmware that I found on the first post of thread titled
[STOCK ROM] Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY
This is a huge step forward because it makes my phone work, but it's also a step back in time to the early Eclair days.
Now my next step is to upgrade back to Gingerbread...
Edit: Thanks to all who pointed me in the right direction. I took the phone back to Eclair then used Samsung KiesMini (twice) to get it back to Gingerbread. After re-rooting and removing the AT&T Bloatware, it works fine again. I might try upgrading again to ICS or JB, but I didn't like Cyanogen 9 at all. Maybe I'm just used to the way AT&T polishes the UI, but Cyanogen didn't appeal at all. Now looking for a relatively polished but lightweight ICS or JB version... Also, it would be nice if when I upgrade it preserves the installed apps and what's on my home screens, but that seems unlikely going from AT&T-branded Gingerbread to an independent ICS or JB.

Phone won't boot

Hello, i have had my galaxy note for a couple of weeks now.
bit of this and that, you know how it is, flashing a few roms, checking things out, keeping it safe and stuff.
idiotic of me, didn't do a backup.
now
everything was working perfectly fine.
'till i decided to put some music on my sdcard
so i shut the phone down, open it up, take out the battery, take the sdcard, put it in pc, put some music (music i had on it before, so the files could've somehow magically ****ed up the device) then but it back on.
ever since, my device won't boot, it will go to CWM recovery, it will go to download mode, but not like, properly boot. all it does is show the Samsung Galaxy Note N7000 thingie, then screen goes black, and back again to Samsung Galaxy Note N7000, then black again, over and over again.
i figured, it must be something wrong with the bootanimation, had a custom one put there, so i deleted it, cuz that way it goes back to stock.
did that, didn't help, same thing.
then, decided to flash the rom again, even tho it was working perfectly for a few days now, (stock 4.0.4 deodexed zipaligned with hydracore safe kernel)
reflashed, didn't help, nothing happened.
things were weird, i thought i should go back to a GB rom, that always...fixes the problem.
tried to flash with ODIN, stuck at factoryfs, when i pulled the cable out, it would tell me the thingummyjig with firmware update has encountered an issue please bla bla kies.
then, I EVEN TRIED the kies, it won't connect, even tho my drivers are right, and i used kies with it before.
NOW, i thought to myself, ****, the phone won't go to recovery anymore, won't boot normaly, just in download, well, download a speedmod kernel which is safe and flash it, that should give you a CWM and safe kernel to flash from
did that, worked.
flashed the stock 4.0.4 rom again, then flashed philz latest kernel for the rom, and i'm back to square one.
nothing changed, i still can't use my note.
WHAT. DO?
right, well, i tried flashing alliance rom, and it gets stuck at mounting partitions....
the blue bar goes on and on till it gets out of the designated loading space
i can't wipe cache, i can't wipe dalvik, it just gets stuck.
Etnoscope said:
... tried to flash with ODIN, stuck at factoryfs ...
Click to expand...
Click to collapse
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
ThaiDai said:
I just quoted the bad line in your post. This is a strong indicator that you have a bricked device.
So you should try to install a different stock GB or ICS Rom with Odin again. If it stucks there again: bricked.
Then you can try to use the workaround described in hg42's thread with repartition. Or send your device for a motherboard replacement to Samsung.
hg42 has a partition scanner which allows to check for emmc problems. Try this.
Click to expand...
Click to collapse
Thing is, phone worked flawlessly before, safe kernel,could flash anything,then this just happened....
Phone doesnt have warranty, sending it to some service would only have me end up with extra costs for putting the motherboard there, which i can do myself
right, welll
i tried flashing speedmod kernel with odin, it worked.
then i tried installing a GB rom via CWM
works well till it gets stuck at flashing modem.
what does this mean?
Etnoscope said:
...what does this mean?
Click to expand...
Click to collapse
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
ThaiDai said:
As I wrote before: possibility that you have a bricked device.
Why don't you try the partition scanner or why don't you try to flash a stock GB and check if you get stuck again with factoryfs.img.
As long as you try different things without a "plan" what you want to test you'll get nothing in the end.
Click to expand...
Click to collapse
tried flashing a stock gb with odin (tried 1 file in pda before, now i tried with 3 files(modem, rom, csc), same thing happened.)
stuck at factoryfs again
i didn't want to get to the partition scanner yet, wanted to clear out any other possibility first, using the scanner as a last resort.
what about pit files?
***
also, i really wanna thank you for showing some interest in my issue, means a lot to me, just wanted to let you know i really appreciate it, and i acknowledge the fact that you're a good, helping member.
thanks bro, you're awesome.
If you have tried also with the correct original pit, then it's time for the scanners to do its job
nokiamodeln91 said:
If you have tried also with the correct original pit, then it's time for the scanners to do its job
Click to expand...
Click to collapse
right
so, i've checked out this thread, about the pit method, and after i opened the emmc_find_brick_start.zip, it started scanning normally, and it finished without being stuck anywhere, and then at the end it said scanned 15027 MiB = 15757 MB completed --> OK then the ---end thingie and done.
so the brick start isn't there, which i assume means my phone is NOT bricked, at least not by the emmc thingummyjig
but if so, what the hell am i to do? like really?
tried flashing gb with cwm, stuck at flashing modem
tried flashing gb with odin, stuck at factoryfs
what the ****?
Get the pit file from this thread
http://forum.xda-developers.com/showthread.php?t=1424997
Then flash the GB rom using pc odin. Make sure pit is selected and the repartition is ticked.
Also if you still have access to cwm try to install a CM10 rom first before trying out the above method.
SOOOOO
bit of an update.
right, after the whole emmc scanning brick mbs and stuff, decided to try and flash allianceROM 4.0.4 final
did it, worked, the flashing.
now i'm stuck at a non blinking, non changing non nothing, Smasung Galaxy Note GT-N7000 screen, with the yello jello triangle, same as before, but its not blinking now.
Ok. Try booting into recovery and performing a full wipe.
nokiamodeln91 said:
Ok. Try booting into recovery and performing a full wipe.
Click to expand...
Click to collapse
full wipe means:
factory reset
wipe cache
wipe dalvik
reboot.
right?
did that, as soon as i hit reboot, it got stuck again there, the frozen CWM screen.
battery in/out, back to square 1
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
nokiamodeln91 said:
Still try a cm rom as it's small in size and easier to download. CM10.1 flash from recovwey
Click to expand...
Click to collapse
official 4.2.1 will do?
Yeah
nokiamodeln91 said:
Yeah
Click to expand...
Click to collapse
any way we could talk via IM?
would be much better conversation-wise
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
nokiamodeln91 said:
We could but where I am, it's 4 am. And I will be off to sleep in a while. Hehe
Click to expand...
Click to collapse
i get status 7 error when i try to flash a CM rom btw, i know what to do, updating philz kernel as we speak
i want you to know i really appreciate this bro, couldn't have come so far without you. thanks a lot man.
right, well, i was using kangbang kernel, tried to install the cm rom, and it gets stuck at installing update...
been there for too long now,so i guess thats a safe bet.
gonna try with a different cm rom
right, well, apparently anything i try to flash gets stuck at installing update....
any solutions?

Softbrick N7000 Need Help

When my phone boots it only gets to the samsung logo
I am able to use the recoverymode and downloadmode.
Wiping data won´t work. Wiping cache works.
Can´t flash a CustomROM from my SDcard through CWM
I was able to connect my phone to the PC. ADB finds the phone but adb shell won´t work. (No such file or directory <2>)
How can I install either a regular Androidversion or a CustomROM now.
found this but only for Galaxy S3, so the files won´t help me
http://forum.xda-developers.com/showthread.php?t=1840030
Hope you can help me
Tobias
Download a Stock Rom from sammobile.com or one of the prerooted Roms (I always use a GB LC1 from bodivas for this) and install it with the PC version of Odin.
tried that, Odin stops at "NAND write start!!"
AW: Softbrick N7000 Need Help
What Rom did you have and what did you do before this happened?
Sent from my GT-N7000 using xda premium
Now I used a regular Android 4.0.4. ROM
Before that I tried with a 2.3.1 ROM. This is probably the reason for the trouble, isn´t it?
Tobias H. said:
tried that, Odin stops at "NAND write start!!"
Click to expand...
Click to collapse
I wrote to download a new rom and to try it with Odin. 15 min later you said: did this.
So I want to ask: Did you really download a new Rom or did you use one you had already?
And what Rom exactly?
And what did you do before stopping at boot logo?
ThaiDai said:
I wrote to download a new rom and to try it with Odin. 15 min later you said: did this.
So I want to ask: Did you really download a new Rom or did you use one you had already?
And what Rom exactly?
And what did you do before stopping at boot logo?
Click to expand...
Click to collapse
I was already downloading the 4.0.4. ROM. Because I read somewhere it´s not possible to go from ICS to Gingerbread.
The download just finished right after you answered and I tried. I am 100% sure i got the right ROM.
Before getting all these Problems, I wanted to get a CustomROM on my phone. Android 4.0.4 was installed at that point of time.
I rooted my phone and did a backup with CWM. Then i chose wipe data, while doing that I started to charge my phone (I don´t know if that matters). I didn´t see what happen exactly because i wasn´t looking at my phone all the time, but when i looked at it again there was only the charging sign shown. Then I tried to get into recoverymode again. This wouldn´t work. I tried to flash CWM with Odin which worked after some time. Then I tried to Wipe data and cache again. wipe data wouldn´t work. Wipe cache worked. I tried to install the backup. After waiting for more then 1 hour it looked like nothing happend and the installation was stuck. But the regular recovery of Android was installed.
Because flashing a ROM through CWM wouldn´t work, I tried to flash it through Odin. First time I tried with a Gingerbread Version. I was thinking, I don´t care which version as long as it works and try again to install a CustomROM from there on. Odin stopped at NAND Write Start!!. Tried it with the ICS Stock version. Same thing.
This is where I am at now
Did you use cwm.zip?
To use with Odin? No
When I started it from the regular Android Recoverymode? Yes
Don´t you think this might be exactly the problem I have?
http://forum.xda-developers.com/showthread.php?t=1840030
Tobias H. said:
I was already downloading the 4.0.4. ROM. Because I read somewhere it´s not possible to go from ICS to Gingerbread.
The download just finished right after you answered and I tried. I am 100% sure i got the right ROM.
Before getting all these Problems, I wanted to get a CustomROM on my phone. Android 4.0.4 was installed at that point of time.
I rooted my phone and did a backup with CWM. Then i chose wipe data, while doing that I started to charge my phone (I don´t know if that matters). I didn´t see what happen exactly because i wasn´t looking at my phone all the time, but when i looked at it again there was only the charging sign shown. Then I tried to get into recoverymode again. This wouldn´t work. I tried to flash CWM with Odin which worked after some time. Then I tried to Wipe data and cache again. wipe data wouldn´t work. Wipe cache worked. I tried to install the backup. After waiting for more then 1 hour it looked like nothing happend and the installation was stuck. But the regular recovery of Android was installed.
Because flashing a ROM through CWM wouldn´t work, I tried to flash it through Odin. First time I tried with a Gingerbread Version. I was thinking, I don´t care which version as long as it works and try again to install a CustomROM from there on. Odin stopped at NAND Write Start!!. Tried it with the ICS Stock version. Same thing.
This is where I am at now
Click to expand...
Click to collapse
Why did u buy SGN? To brick it?
Do you even read and search before doing something for the first time?
LOOK, READ AND LEARN THIS for stock ROMs and kernels, specialy for ICS:
- http://forum.xda-developers.com/showthread.php?t=1424997
-http://forum.xda-developers.com/showthread.php?t=1371007
-http://forum.xda-developers.com/showthread.php?t=1827394
To run ur device find something and READ.
Try leaked JB custom ROM and stock rooted kernel with safe emmc_cap_erase block (emmc bug fix) -Philz Kernel
READ and LEARN.
Have fun
P.S. Maybe you will need our friend hg42 and his famous .PIT files so here it is: http://forum.xda-developers.com/showthread.php?t=1667886

Categories

Resources