[Q] MY Galaxy Tab is stuck in a boot loob - Galaxy Tab Q&A, Help & Troubleshooting

Hello Guys
I Have a Galaxy tab GT-P1000 WI-FI+GSM
It's Stuck In a BOOTLOOP:crying::crying:
AND THE 4 TOUCH BUTTONS IN THE BOTTOM OF THE TABLET DOESN'T WANT TO LIGHT:crying::crying::crying:
BECAUSE WHEN THEY LIGHT THE TABLET WORKS FINE
I Have TO PUT IT IN THE CHARGER FOR ABOUT 8-9 HOURS TO WORK
AFTER I COMPLETLY FORMATED THE DEVICE AND INSTALED THE STOCK 2.3.3 ROM THE PHONE STUCK IN A BOOT LOOP
I PUT IT IN THE CHARGER FOR ABOUT 8-9 HOURS BUT THIS TIME IT DIDN'T WORK:crying::crying::crying:
PLEASE,HELP.

What did you do? What files did you flash? We need details

Here Are The Files
Jarmezrocks said:
What did you do? What files did you flash? We need details
Click to expand...
Click to collapse
P1000JPJPD_P1000OJPJPE_P1000JXJP4_HOME.tar.md5
gt-p1000_mr.pit
dbdata.tar
these files worked fine until i formated every thing on the device using overcome kernel 4.0.0 and reinstalled those files
i tried every way that made it run in the past but....nothing,the 4 touch buttons in the bottom of the device doesn't work any more
the tablet will work if they light up

Preacher_M4 said:
P1000JPJPD_P1000OJPJPE_P1000JXJP4_HOME.tar.md5
gt-p1000_mr.pit
dbdata.tar
these files worked fine until i formated every thing on the device using overcome kernel 4.0.0 and reinstalled those files
i tried every way that made it run in the past but....nothing,the 4 touch buttons in the bottom of the device doesn't work any more
the tablet will work if they light up
Click to expand...
Click to collapse
Yes your device should be recoverable. If it is working all bar the touch buttons then something just must have gone wrong in the flash?
I have had issues with similar files. I would suggest that you go to the thread where you downloaded the Overcome kernel and you will see the download for GB_Stock_Safe_v5.zip. Try >>> Here thread by @sos_sifou
Ensure that you have copied all of the data you require off your internal SDcard (Try mounting the card in recovery if you are unable to boot your device - Overcome kernel should allow this very easily)
Put the device into download mode, Use Odin 1.7 (only use this version)
select the same pit gt-p1000_mr.pit as PIT (naturally) and then choose GB_Stock_Safe_v5.tar as PDA, and then choose JP4 modem (or similar - what ever is best for your region)
Flash your device.
If you have troubles or brick your device (it happens - I must have done it at least 30 times last week ) then download Heimdall Oneclick Unbrick by Adam Outler >>> here. You will probably need this so you should download it anyway.
Any questions. Post back here.
BTW I am no expert, I have just failed lots of times fairly recently so I am in good order to pass on this valuable info.

I'm download the files now
Jarmezrocks said:
Yes your device should be recoverable. If it is working all bar the touch buttons then something just must have gone wrong in the flash?
I have had issues with similar files. I would suggest that you go to the thread where you downloaded the Overcome kernel and you will see the download for GB_Stock_Safe_v5.zip. Try >>> Here thread by @sos_sifou
Ensure that you have copied all of the data you require off your internal SDcard (Try mounting the card in recovery if you are unable to boot your device - Overcome kernel should allow this very easily)
Put the device into download mode, Use Odin 1.7 (only use this version)
select the same pit gt-p1000_mr.pit as PIT (naturally) and then choose GB_Stock_Safe_v5.tar as PDA, and then choose JP4 modem (or similar - what ever is best for your region)
Flash your device.
If you have troubles or brick your device (it happens - I must have done it at least 30 times last week ) then download Heimdall Oneclick Unbrick by Adam Outler >>> here. You will probably need this so you should download it anyway.
Any questions. Post back here.
BTW I am no expert, I have just failed lots of times fairly recently so I am in good order to pass on this valuable info.
Click to expand...
Click to collapse
i will try that,thanx:good:

i flashed the files
Jarmezrocks said:
Yes your device should be recoverable. If it is working all bar the touch buttons then something just must have gone wrong in the flash?
I have had issues with similar files. I would suggest that you go to the thread where you downloaded the Overcome kernel and you will see the download for GB_Stock_Safe_v5.zip. Try >>> Here thread by @sos_sifou
Ensure that you have copied all of the data you require off your internal SDcard (Try mounting the card in recovery if you are unable to boot your device - Overcome kernel should allow this very easily)
Put the device into download mode, Use Odin 1.7 (only use this version)
select the same pit gt-p1000_mr.pit as PIT (naturally) and then choose GB_Stock_Safe_v5.tar as PDA, and then choose JP4 modem (or similar - what ever is best for your region)
Flash your device.
If you have troubles or brick your device (it happens - I must have done it at least 30 times last week ) then download Heimdall Oneclick Unbrick by Adam Outler >>> here. You will probably need this so you should download it anyway.
Any questions. Post back here.
BTW I am no expert, I have just failed lots of times fairly recently so I am in good order to pass on this valuable info.
Click to expand...
Click to collapse
i flashed all the files,they worked fine but i am stuck in the boot loop
i opend the recovery and these words were written by yellow color
-- verfing internal mmc block...
checksum confirmation -> check(0)
not need checksum confirmation
already executed!!...
#MANUAL MODE#
-- Updating application...
successfully updated application.
--Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/EGY/system/'.
successfully applied multi-CSC
I Think that's the problem
i need help,thanx:laugh:

Related

[Q] Samsung Galaxy S: Black Screen after Flash

I have a SGS with firmware I9000XWJG5 and Root. I tried to do a Speed fix, but afterwards it was slower so i tried to flash the phone with the I9000XWJG5 firmware again.
After the flash, the phone rebooted and i came to the recovery menu. There the phone wrote:
update media, please wait
and in the next lines:
E: Can't mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Now when i try do start the phone, i get a black screen after the bright S
What i have tried: Flash agein with and without re-partition and Factory Reset
Has anybody an idea what i can do?
and sorry for my bad english
bump. can anyone help with this topic..
i am having some problem..
help us guys
thanks
Fixed... use odin 512
Thread moved in Galaxy S I9000 General.
I can definately help with this one, as I worked through it last night...
I found that if you're trying to flash the JG5 rom (as mentioned in Modaco's thread) with the 513 Pit file, then you'll get the black screen of despair!! For some reason the two combination of the two don't work.
However, if you do a google search for Odin PIT 512, then download this file
You will be able to download the 512 PIT file instead. Now use this in Odin3 to flash the JG5 rom and you should have no further issues....it worked for me.
I also discovered that Samsung have just released a later firmware, so I just flashed this one on top of the JG5 one...I have a nicely running phone now.
Hope this helps...it did me!
Mike
Mine was completely knackered. Couldn't get to recovery either. Flashed Modaco's MCR R3, after the JG5 flash, using all the files in the JG5 download. Working a treat...
Cheers,
BS...
blacksoul93 said:
I have a SGS with firmware I9000XWJG5 and Root. I tried to do a Speed fix, but afterwards it was slower so i tried to flash the phone with the I9000XWJG5 firmware again.
After the flash, the phone rebooted and i came to the recovery menu. There the phone wrote:
update media, please wait
and in the next lines:
E: Can't mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Now when i try do start the phone, i get a black screen after the bright S
What i have tried: Flash agein with and without re-partition and Factory Reset
Has anybody an idea what i can do?
and sorry for my bad english
Click to expand...
Click to collapse
hello, i got the same problem. trying to reflash with I9000XXJPY 2.2.1 and the 512 pit, but still the same problem.
ash969 said:
hello, i got the same problem. trying to reflash with I9000XXJPY 2.2.1 and the 512 pit, but still the same problem.
Click to expand...
Click to collapse
Same here.
I tried JS3 and going back to JP6....and always the same result.
I'm obviously missing something. Maybe my 512.PIT is corrupted. I get the black screen and the same /dev/block.st110 errors in recovery.
i beleive you need to have a CSC file also for the odin flash.
i sorted mine like this:
Downloaded some JP2 odin files [used this as this was the only one on Samsung-firmwares that had all 3 PDA, Modem and CSC Files. flashed this using a .512 pit in odin. - this allowed the phone to boot normally.
connected to Kies and using reg hack [set to XEU] managed to update to JPY.
the following the Darky guide, flashed the CF Root kernel, installed the ROM Manager from the market, using the recovery mode installed the update.zip file for clockworkMod.
Formatted everything in ClockworkMod
Factory Reset in ClockworkMod
Installed Darky ROM V8.0 Wipe
thanks for your find !
Rumble6059 said:
i beleive you need to have a CSC file also for the odin flash.
i sorted mine like this:
Downloaded some JP2 odin files [used this as this was the only one on Samsung-firmwares that had all 3 PDA, Modem and CSC Files. flashed this using a .512 pit in odin. - this allowed the phone to boot normally.
connected to Kies and using reg hack [set to XEU] managed to update to JPY.
the following the Darky guide, flashed the CF Root kernel, installed the ROM Manager from the market, using the recovery mode installed the update.zip file for clockworkMod.
Formatted everything in ClockworkMod
Factory Reset in ClockworkMod
Installed Darky ROM V8.0 Wipe
Click to expand...
Click to collapse
thanks mate ! after a huge scare sorted mine with this firmware as well, this after I tried several other newer firmware packages from samfirmware and was ,slowly but surely ,starting to lose hope ...
for some reason this particular firmware JP2 seems to fix this problem
cheers and thanks again for your find !
fix for black screen after flash with no recover or download mode working.
Hey All.
So like the subject says, you flash and then your phone restarts or whatever, and then you get the normal galaxy s startup, with the sound and the visuals, but then that's it. Henceforth you are greeted with the two lights (if its a Bell Vibrant) from your options and back keys.
To fix it use the attached file. Its called ADB or something - I just know it works. It was a fix for the galaxy s phones that didnt have the recovery/download mode stock.
so here is how it goes:
1. download adb to your desktop and unpack it (if its in winrar or zip or whatever) to a file folder named adb.
2. open a command prompt.
3. type "cd" and then the address of the "adb" folder. so for example it should be in C:\Users\your user name\Desktop\adb. where "your user name" is your user name a duh.
4. plug in your galaxy s via usb.
5. type "adb reboot download" in the command prompt. copy it using your mouse as well.
6. turn on your phone.
7. press enter in the command prompt, then keep copying and pasting and pressing enter until you see the download screen on your phone. each time you press enter it says device not connected or something but just keep trying.
the article i read:
can't post it but the thread is called "How to get the 3 button recovery mode working"
Credit to Goots from samsung galaxy s forums. Go Goots!

Solution JPM Not Prepared your storage yet, please use UI menu for format and reboot

On first boot I get
Can not mount / dev/block/stl10 (Invalid argument)
copy_dbdata_media: Can not mount DBDATE
Not Prepared your storage yet, please use UI menu for format and reboot actions
default copy content failed half
wiping / data cache and Does not Seem To fix anything.
Format sdcar unresponsive
HELP any occurrence and brick my phone
criskelo said:
On first boot I get
Can not mount / dev/block/stl10 (Invalid argument)
copy_dbdata_media: Can not mount DBDATE
Not Prepared your storage yet, please use UI menu for format and reboot actions
default copy content failed half
wiping / data cache and Does not Seem To fix anything.
Format sdcar unresponsive
HELP any occurrence and brick my phone
Click to expand...
Click to collapse
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
Fixed in a while I explain
My solution
With Odim 1.3, pit 512,
in my case JH2 I9000T GT
But for Europe JM8
Mark Re-partition, phone EFS clear and Phone bootloader Update
Then start
This process started well
JPM Process
Then uncheck re-partition, phone EFSclear and Phone Bootloader Update
JPM Pit 803 and firm JPM
Start
To enjoy
Thanks
criskelo said:
Then uncheck re-partition, phone EFSclear and Phone Bootloader Update
Click to expand...
Click to collapse
Is it normal for T model, or you just use weird and dangerous settings for fun?
Wiping EFS can lead to test-imei number and broken product code. Be sure you haver a backup of that folder before wiping that.
criskelo... I tried this and I didn't get anywhere :/
I had the same issue and it took me 2 hours to resolve (with a lot of pain, lol).
I've simply flashed the XWJM8 version using odin 1.3, no pit file and HENCE no repartition ticked.
It then booted to recovery console, because there was another error (can't remember which one cause I was too excited).
Anyway I did a wipe, cash clear and reformat SD card at the menu and let it boot.
After that I have flashed the latest version XXJPY also without PartitionInformation Table. (PIT). Then all the wipe and format stuff again.
I have now to go from scratch to setup anything again, but hey, at least my phone is alive again.
Some additional info. I also had that connection symbol on the screen with exclamation mark and triangle....so I thought I was done (due to trials with pit 512 which hung), but after removing battery and some trials I was able to enter download mode again....
Why happened that? I DON'T KNOW! I simply wanted to reflash the XXJPY stock rom, this time with pit512 and it lead to the topic of this thread!!!
This su**ed a lot, I didn't even modify something before!!!!
So: Less is even more! Don't fiddle with EFS and bootloader options it worked for me even without a pit!
Thanks to sardor for the initial idea, the XWJM8 seems to be a fixing rom for that when used properly, anyway to load a pit without to tick repartition is not a useful setting!
Well I was a long time reader at this great forum, IMHO the best regarding phone stuff, because there is the most useful knowledge shared.
I hope my first post will save other phones as well from sending it to repair.
Thanks I'm happy again..(let's see how long it'll last..lol...)
bricked my samsung galaxys and recoverd it
Hi I had exact same problem I totally bricked my i9000 Australian Optus version
I used
I9000DTJG4 firmware Australian Optus
With pit 512
And odin3 v1.3
Got all the files from
samfirmware . com / WEBPROTECT - i9000 . htm
Had to sign up but it’s free
However following criskelo's advice I unchecked the re partion box in odin
Even though the site above tells u to check it
And it worked
Thanks for everyone’s help on this thread.
Without you I would have had an expensive paper waited
Also the reason I got here in the first place as because I messed around with lag fix in clockwork recovery when I don’t know anything about it.
I was lucky this time but it’s really not worth playing around with things you doing understand.
sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook
Awesome, thanks buddy! I have spent too much time trying to fix this phone and it all totally pays off now!
Here is the fix for the Bell firmware:
Background info: I orginally tried the Lagfix and bricked my phone, this is how I finally fixed it...
1. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJH2
Use Phone: Modem.bin
(both files came from samfirmware, I9000UGJH2 download)
Use: 512.pit(also from samfirmware at the bottom of the i9000 page)
Check Re-Partition, Auto-reboot, F. reset time, phone EFS clear and Phone bootloader update. I know everyone above says don't but I tried their way first and it didn't work, I would recommend you do try their way first and if no results try mine.
2. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJL2
Use 803.pit
Check only Auto-reboot, F. reset time
Good luck! I hope you do your happy dance like I did!!
crazycanuckeh said:
Awesome, thanks buddy! I have spent too much time trying to fix this phone and it all totally pays off now!
Here is the fix for the Bell firmware:
Background info: I orginally tried the Lagfix and bricked my phone, this is how I finally fixed it...
1. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJH2
Use Phone: Modem.bin
(both files came from samfirmware, I9000UGJH2 download)
Use: 512.pit(also from samfirmware at the bottom of the i9000 page)
Check Re-Partition, Auto-reboot, F. reset time, phone EFS clear and Phone bootloader update. I know everyone above says don't but I tried their way first and it didn't work, I would recommend you do try their way first and if no results try mine.
2. Using Odin v1.82
Put Phone in download mode
Use PDA: I9000UGJL2
Use 803.pit
Check only Auto-reboot, F. reset time
Good luck! I hope you do your happy dance like I did!!
Click to expand...
Click to collapse
hey how did it worked for you. Not working for me.
did you extracted the tar file? which file did you loaded into the pda tab then ?
Didnt worked for me at all
sardor said:
Go to Download Mode and flash ROM XWJM8 with pit512 and Re-Partition,after flash XXJPM with pit803 and without Re-Partition-this help
Click to expand...
Click to collapse
you saved my phone after me corrupting internal SD! just did my victory dance though hands still shaking a bit
Just thought I would add to what got my phone back running again after having the Can't mount DBDATA error. It's a bell I9000M.
Used Odin 1.3 , Flashed Darky's resurection per his instructions pulled battery once complete, went back into download mode and flashed stock JL2 with Odin , re-partition un-checked and no Pit file and after that my phone was running again.
You can find Darky's Resurection Here!
Can not find the link for the JL2 stock rom but it's in the general section somewhere.
the xxjpu version worked for me
tlick repartition
add 512 pit
tick and add pda
tick and add modem
tick and add csc
go to download mode
connect usb
press start
Need help with Fascinate
Hey guys, I've read the above posts but frankly it's above my skill.
Some how I ended up with the same message that the OP got.
Can someone walk me through the steps to completely fix my phone and get it back to bone stock?
I'm not familiar with PIT and other files. I need someone to hold me hand on this one...
cddt said:
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook
Click to expand...
Click to collapse
Was also messing around with darky. decided to go back to 9.5 for now. also got the error, then did what cddt said (thanks!!).
first flash - different error (something about CSC)
for second flash i used JS7 + 803pit + no repartitioning
worked flawlessly Thanks!
Stuck in boot loop
Samdroid_G_S said:
Just thought I would add to what got my phone back running again after having the Can't mount DBDATA error. It's a bell I9000M.
Used Odin 1.3 , Flashed Darky's resurection per his instructions pulled battery once complete, went back into download mode and flashed stock JL2 with Odin , re-partition un-checked and no Pit file and after that my phone was running again.
You can find Darky's Resurection Here!
Can not find the link for the JL2 stock rom but it's in the general section somewhere.
Click to expand...
Click to collapse
Hi,
I have bell sgs and I tried this and since then my phone is on boot loop. I can only go in download but not recovery. IT all started when I installed the boot loader for gingerbread...
Flashing Error - resolved
cddt said:
I was messing with Darky's Rom which alway cause problems for me and found myself in the same situation as the first post.
What worked for me.
JM8 (2 files = code to PDA - Modem to PHONE) + Repartition + 512pit
after reset different error so goto download mode again then:
JPM + 803pit
Default OS reconfigures, Thank Fook
Click to expand...
Click to collapse
Just followed this and it worked a treat thank you
Hi there,
I am having issues the same way. I am unable to do something. Can some explain me the procedure how to do it.
From where can i get the files.
Please help me out

[Q] Indian Tab Flashing Information ?

Could some one for benefit of Indian Tab Owners, write a step-by-step instructions or guide. Lot of information to digest for a new user including details of 1) rooting 2) installing recovery 3) flashing ... this information would be great useful for everyone.
My Tab details :
(Model: GT-P1000 | Code: INU | Version: P1000DDJK3/P1000ODDJJ1/P1000DDJJ1)
hey..even i have a galaxy tab indian version...just follow the guides that are avaliable here for rooting flashing etc...etc...and i had the same modem when i bought it but its since been upgraded to a newer version of the modem so i just updated the modem to the ...DXJM2 version..thought the asian modem would be better for me..if u want i'll post the modem.bin
Dare{D}evil said:
hey..even i have a galaxy tab indian version...just follow the guides that are avaliable here for rooting flashing etc...etc...and i had the same modem when i bought it but its since been upgraded to a newer version of the modem so i just updated the modem to the ...DXJM2 version..thought the asian modem would be better for me..if u want i'll post the modem.bin
Click to expand...
Click to collapse
Thank you for quick reply. I started compiling the files need to flashing. So far, I could do following. Please advice me whether I am on the right path or not.
1. Rooted my tab with Z4root. Now I got root permission.
2. Downloaded Odin3 v1.7.exe and s1_odin_20100803.pit for flashing
3. Downloaded Roto-JMI-Full-v2.zip and Roto-JMI-Upgrade-v2.zip
Now, using Odin PDA button, I want to flash Roto-JMI-Full-v2.zip ?
Few questions:
a) Is this correct way of flashing or I am missing something?
b) Does above flash install Recovery also ?
c) which files need for PHONE and CSC files ?
d) Which firmware best suitable for Indian Tab ?
Thank you in advance for clarifying above.
I really appreciated reply for my questions as it would allow me to move forward. I will ensure a good documentation at the end of the process for benefit of other users.
nchary05 said:
Thank you for quick reply. I started compiling the files need to flashing. So far, I could do following. Please advice me whether I am on the right path or not.
1. Rooted my tab with Z4root. Now I got root permission.
2. Downloaded Odin3 v1.7.exe and s1_odin_20100803.pit for flashing
3. Downloaded Roto-JMI-Full-v2.zip and Roto-JMI-Upgrade-v2.zip
Now, using Odin PDA button, I want to flash Roto-JMI-Full-v2.zip ?
Few questions:
a) Is this correct way of flashing or I am missing something?
b) Does above flash install Recovery also ?
c) which files need for PHONE and CSC files ?
MId) Which firmware best suitable for Indian Tab ?
Thank you in advance for clarifying above.
Click to expand...
Click to collapse
Install Adfree or something which requires root acess for installation. Once rooted download something like root explorer from market which allows you to backup the modem.bin file. Or me or somebody else can just upload the file here.
Read the post/link in the thread where you downloaded Roto's JMI rom.
Use the .pit file from Roto's link not the thing which you posted...same place where you got the same ROM file. If you are flashing first time/from another rom then use the Full v2 zip file. Else use Update v2 when flashing from one of Roto's rom.
Connect the tab to your pc, reboot and go into download mode...press power+vol down button while rebooting...a yellow triangle icon with an android digging will come up...to get out of download mode,just keep the power button pressed till it rebooted normally.
Once in download mode, open up Odin and check that the yellow com box option is on. Check repartition option to ensure everything is wiped and you have a fresh install from scratch.
For PIT select the pit file downloaded from roto's link
For PDA select the Full.tar file
For PHONE select the modem.bin file
For CSC leave it blank...
Once done, recheck and hit start.
PLEASE CHECK ROTO'S JMI V2 THREAD IN THE DEVELOPEMENT SECTION...it has a link to howto which is old but gives some idea of how to proceed...for pit, pda, phone follow as I suggested and things will go fine...
Sent from my GT-P1000 using XDA App
Thank you.. I will do the same let you know the status....
blackheart2925 said:
Install Adfree or something which requires root acess for installation. Once rooted download something like root explorer from market which allows you to backup the modem.bin file. Or me or somebody else can just upload the file here.
Read the post/link in the thread where you downloaded Roto's JMI rom.
Use the .pit file from Roto's link not the thing which you posted...same place where you got the same ROM file. If you are flashing first time/from another rom then use the Full v2 zip file. Else use Update v2 when flashing from one of Roto's rom.
Connect the tab to your pc, reboot and go into download mode...press power+vol down button while rebooting...a yellow triangle icon with an android digging will come up...to get out of download mode,just keep the power button pressed till it rebooted normally.
Once in download mode, open up Odin and check that the yellow com box option is on. Check repartition option to ensure everything is wiped and you have a fresh install from scratch.
For PIT select the pit file downloaded from roto's link
For PDA select the Full.tar file
For PHONE select the modem.bin file
For CSC leave it blank...
Once done, recheck and hit start.
PLEASE CHECK ROTO'S JMI V2 THREAD IN THE DEVELOPEMENT SECTION...it has a link to howto which is old but gives some idea of how to proceed...for pit, pda, phone follow as I suggested and things will go fine...
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
I followed the steps after flashing 'full' tar, it rebooted tab, started the normally. After that, I verified that, all applications , phone (GSM) and wifi working fine.
Now my question is do I really need to flash *second* tar file ? what is it for ?
^^No. It is only for people upgrading from previous versions! You are good to go!
Now, I want to install CWM recovery. Please some one can confirm below steps:
1. Make sure to have Samsung Kies installed, and your tab at least connected once, to be sure the drivers are correct.
2. Your Tab must be Rooted.
3. If you wish to do a backup, now is the time.
4. You will need an SD Card with enough free space for the filesystem conversion, and to put the Overcome ROM on before we start. (An empty 4gb should be plenty, as long as it is empty, or close too)
5. Download and Extract the following file to your computer: http://www.apksmash.com/corodius/galaxytab.zip (Contains "Odin3 v.1.7.exe" "Overcome_Kernel_v1.0")
Now, we will Install the Kernel and perform the EXT4 filesystem conversion.
1. Turn off your Galaxy Tab.
2. Turn your Galaxy Tab on into DOWNLOAD mode (Press Volume DOWN and Power On at the same time).
3. Open Odin3 v1.7.exe on your PC.
4. Connect your Galaxy Tab to your PC via the USB cable.
5. Make Sure the ID:COM box is highlighted yellow (meaning it sees your tab).
6. Click on the PDA button and select the Overcome_Kernel_v1.0.tar file you downloaded earlier (make sure PDA is ticked after selecting the file).
7. The only boxes ticked should be:
A. Auto Reboot
B. F. Reset Time
C. The PDA tickbox
8. Click start and wait for PASS! to show highlighted green on Odin.
9. Your Galaxy Tab will Reboot, and get stuck on the Samsung Boot Screen. This is fine.
10. Turn your Galaxy Tab off by holding the power button for about 5 seconds.
11. Turn your Galaxy Tab on into RECOVERY mode (Press Volume UP and Power On at the same time).
12. The Galaxy Tab will now perform the EXT4 conversion.
13. Sit tight, depending on how much data you have, this can take quite a long time.
14. Once finished, click reboot system now (by pressing the power button).
At this point, You have installed the Overcome Kernel with CWM included and converted the Filesystem to EXT4. It has been reported that many stock ROMs will boot and run fine now, however some may not, but it just depends on your ROM etc.
http://forum.xda-developers.com/showthread.php?p=11713685.
Would be there any problem ? or is there any easy way to install CWM Recovery.
I had bricked my tab while modding battery icon and it was not booting now. Now i want to flash with the custom rom available here. I am noob to flashing so just want to confirm the steps mentioned above applicable to the bricked tab. Can somebody guide me for bircked tab.
Please mentioned the good custom rom with Ext4 conversion at the time of install. I am using indian tab.
@OP:- Sorry for hijacking this thread but find some info here for my queries
Can you get into download mode? If yes then you should be able to flash...but I would suggest checking"I bricked my tab" threads in general or developement section...
Sent from my GT-P1000 using XDA App
nchary05 said:
Now, I want to install CWM recovery. Please some one can confirm below steps:
1. Make sure to have Samsung Kies installed, and your tab at least connected once, to be sure the drivers are correct.
2. Your Tab must be Rooted.
3. If you wish to do a backup, now is the time.
4. You will need an SD Card with enough free space for the filesystem conversion, and to put the Overcome ROM on before we start. (An empty 4gb should be plenty, as long as it is empty, or close too)
5. Download and Extract the following file to your computer: http://www.apksmash.com/corodius/galaxytab.zip (Contains "Odin3 v.1.7.exe" "Overcome_Kernel_v1.0")
Now, we will Install the Kernel and perform the EXT4 filesystem conversion.
1. Turn off your Galaxy Tab.
2. Turn your Galaxy Tab on into DOWNLOAD mode (Press Volume DOWN and Power On at the same time).
3. Open Odin3 v1.7.exe on your PC.
4. Connect your Galaxy Tab to your PC via the USB cable.
5. Make Sure the ID:COM box is highlighted yellow (meaning it sees your tab).
6. Click on the PDA button and select the Overcome_Kernel_v1.0.tar file you downloaded earlier (make sure PDA is ticked after selecting the file).
7. The only boxes ticked should be:
A. Auto Reboot
B. F. Reset Time
C. The PDA tickbox
8. Click start and wait for PASS! to show highlighted green on Odin.
9. Your Galaxy Tab will Reboot, and get stuck on the Samsung Boot Screen. This is fine.
10. Turn your Galaxy Tab off by holding the power button for about 5 seconds.
11. Turn your Galaxy Tab on into RECOVERY mode (Press Volume UP and Power On at the same time).
12. The Galaxy Tab will now perform the EXT4 conversion.
13. Sit tight, depending on how much data you have, this can take quite a long time.
14. Once finished, click reboot system now (by pressing the power button).
At this point, You have installed the Overcome Kernel with CWM included and converted the Filesystem to EXT4. It has been reported that many stock ROMs will boot and run fine now, however some may not, but it just depends on your ROM etc.
http://forum.xda-developers.com/showthread.php?p=11713685.
Would be there any problem ? or is there any easy way to install CWM Recovery.
Click to expand...
Click to collapse
I followed above steps and could able to install CWM RECOVER.
congrats dude
maddy_in65 said:
I had bricked my tab while modding battery icon and it was not booting now. Now i want to flash with the custom rom available here. I am noob to flashing so just want to confirm the steps mentioned above applicable to the bricked tab. Can somebody guide me for bircked tab.
Please mentioned the good custom rom with Ext4 conversion at the time of install. I am using indian tab.
@OP:- Sorry for hijacking this thread but find some info here for my queries
Click to expand...
Click to collapse
can you just tel me which modem.bin are u using coz i was planning to flash but stuck on decision bcoz of modem... is it jpz or jk3? or any other
A new GB version is available DDJPA
http://forum.xda-developers.com/showthread.php?t=1226674
need PDA PIT PHONE CSC files
Kindly send me the links for downloading the PDA PIT PHONE CSC files as I could find only broken links.
My samsung tab (Version: P1000DDJK3/P1000ODDJJ1/P1000DDJJ1)) is bricked and won't boot.
Than You
nchary05 said:
Could some one for benefit of Indian Tab Owners, write a step-by-step instructions or guide. Lot of information to digest for a new user including details of 1) rooting 2) installing recovery 3) flashing ... this information would be great useful for everyone.
My Tab details :
(Model: GT-P1000 | Code: INU | Version: P1000DDJK3/P1000ODDJJ1/P1000DDJJ1)
Click to expand...
Click to collapse

Soft bricked N7000. How to?

Tried everything I could with Odin and phone still stuck in a start loop.
I was downgrading from checkROM to official firmware ZSLA2 with CWM (I wanted to keep ROOT, so I selected "Keep CF-Root kernel") due to stability issues, after restarting the phone got into the start loop.
I flashed with Odin official ZSLA2 with the same result (looped start). I flashed XXKKA (again looped start). During the flashing process, Odin says the flashing was successful. By the way, both ROMS are tar.md5 files.
I tried to remove the battery for over 30 minutes and charge it for 2 hours, tried re-partition in Odin (it's my understanding that with a stock rom, it creates a clean installation), but Odin fails to start the process.
What else can I do?
I am sorry if this has previously asked, but I've been searching for over 2 hours and nothing similar came. Somebody mentioned to use a PIT file in addition, but the other person who got his phone soft bricked didn't solve the problem either. As downloading a ROM is time consuming and I've got many problems with upload sites in china (cannot access to most of them), I would thank any help in regards this issue.
Sounds like your kernel isn't talking properly to your ROM.
A fresh start is your best bet. Flash a stock rom and kernel from Odin and reroot it with CF-Root.
What files are you putting into Odin? There should be a total of 4.
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
I am using official ROM N7000ZSLA2_N7000ZSLA2_N7000XLA4_HOME.tar.md5 into PDA and also tried ROM N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5, which I used successfully in the past to make root into my phone.
Does it really make a difference to flash 4 separate files instead of a full pack? Where can I find an official ROM with pda radio and kernel separated? Just untar the ROM?
btyork said:
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
Click to expand...
Click to collapse
Oh, they do come into the Note; I flashed the Beta ICS, and one of the things they mention is to use the PIT file for the 16GB version, instead of the 32GB that comes with the leaked ROM. Unfortunately I deleted that ROM, and donwloading it is painfully slow and also wouldn't necessarily solve my problem as I couldn't even make a phone call.
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
btyork said:
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Click to expand...
Click to collapse
This are the files I am flashing:
Sorry, I am new user and still cannot post screen captures. I do have more than the 5 files.
In XXKKA I have:
Boot
Cache
Factoryfs
Hidden
Modem
param.lfs
Sbl
zImage
In ZSLA2:
Cache
Factoryfs
Hidden
Modem
zImage
btyork said:
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
Click to expand...
Click to collapse
I can only enter into Download mode, not recovery mode.
Odin is full wipe, right? What the hell am I doing wrong?
N7000xxla1_n7000oxala1_oxa
http://hotfile.com/dl/141060546/b0c7420/N7000XXLA1_N7000OXALA1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
choihan06 said:
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
mrfan said:
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
Click to expand...
Click to collapse
I have just recently dowloaded and installed the rom without problem. What do you mean by corrupted rom?
Sent from my GT-N7000 using xda premium
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.
Fix The problem
I had the same problem, the device got into start loop. JUST DO A FULL WIPE..! and the device should start normally. I worked for me.... :good:
Sent from my GT-N7000 using xda premium[/QUOTE]

[Q] Galaxy Note bricked when used "u1_02_20110310_emmc_EXT4.pit" in Odin

Okay. Some history to start with...
I got Chinese version of Galaxy Note which runs i9220 ROM and been trying to flash with HK/EU ROM last several days but out of luck so far. (And whenever failed, I re-loaded stock ROM found from Samsung-updates.com site for i9220. It then worked fine but still with original problem unsolved.
I then tried one last method that I saw someone succeed flashing Chinese ROM via use of PIT file came from one of the other downloads.. yeah, I didn't check the source PIT came from before try... which is my bad.
Without confirming it, I instantly located "u1_02_20110310_emmc_EXT4.pit" that's packaged with odin 1.85 and carelessly gave a try.
And now... my precious GalaxyNote became the most expense brick in my house and am looking for professional help from you guys.
Steps I did before bricking and tried:
1. Load GalaxyNote in Download mode (volume down + home + power)
2. Launch Odin 1.85 and no change to default setting. (Check mark on #Auto Reboot & #F.Reset Time, uncheck on #Re-Partition & #Flash Lock)
3. Set PIT to "u1_02_20110310_emmc_EXT4.pit"
4. Set PDA to "N7000XXKL7_N7000OXAKL7_N7000XXKL7_HOME"
5. Click #Start
Soon after around 5%, it failed.
I then attempted to restore factory ROM via usual way - doing same as above except no PIT this time and choosing original stock ROM for i9220.
It failed! OMG...
I then tried again (#1 ~ 5 above) but this time, check on #Re-partition for luck. Still no luck!
I then downloaded Heimdall1.3.1 and tried to extract PIT file but the tool fails as well and gives "ERROR: Failed to access device. libusb error: -12".
At all times, GalaxyNote screen shows android icon with 'Downloading... Do not turn off target!!'. And the device can also be seen from odin.
Soon as turn off galaxynote and disconnect from computer, it shows 'Software Update Fail' message.
How I can restore to original factory setting? And if possible, how I can restore to EU or Hong Kong ROM?
My Chinese friend has the same device as mine. In this case, will Heimdall tool help extracting PLT from it and help restoring my device via odin?
Your professional help is sincerely appreciated!!!!
Resolved
Using "Q1_20110914_16GB.pit" and re-partition check from odin while flashing to original stock rom has resolved an issue.
Referred from following thread.
http://forum.xda-developers.com/showthread.php?t=1533214
Never use pit and do not tick repartion when flashing.
bootloader?
U are fine. It is a recovery issue and not a bootloader. Install custom recovery and flash stock firmware w odin. Oh yea, and profit.
Toolmighty said:
U are fine. It is a recovery issue and not a bootloader. Install custom recovery and flash stock firmware w odin. Oh yea, and profit.
Click to expand...
Click to collapse
Why do you revive an old thread? The user has resolved it the day after his problem.

Categories

Resources