Related
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
you custom flashed??
what do u mean u custom flashed??
Get a rom with bootloader in it. Don t use repartition. Make sure you flash the bootloader.
Sounds like you wiped from a stock Samsung kernel, which is a big no no. The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage. If you search hard enough, you'll find a thread about it. I successfully recovered a phone I bricked way back with the first LP1 ICS kernel. It does work! You'll lose some space though.
http://forum.xda-developers.com/showthread.php?t=1667886
And there's the thread I was talking about.
tibosee said:
Get a rom with bootloader in it. Don t use repartition. Make sure you flash the bootloader.
Click to expand...
Click to collapse
Can you send me a link with a rom which has this please?
Here i had the same problem when I tried to flash my first rom. Just tried to flash on another computer and guess what... Successfully done!
Sent from my GT-I9100 using Tapatalk 2
smalmagal said:
Sounds like you wiped from a stock Samsung kernel, which is a big no no. The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage. If you search hard enough, you'll find a thread about it. I successfully recovered a phone I bricked way back with the first LP1 ICS kernel. It does work! You'll lose some space though.
http://forum.xda-developers.com/showthread.php?t=1667886
And there's the thread I was talking about.
Click to expand...
Click to collapse
Yes I factory reset a STOCK ICS ROM .. please can you assist in what I need to do.. Which PIT file and which ROM Shall I try to flash with.. please assist.. Many thanks..
Thanks for your help guys .. followed the german dudes tutorial and downloaded the .PIT file and managed to re flash stock ICS .. Now the only issue is my internal memory is showing 8.24 GB.. what happened to the other approx 8GB? I thought the Note was 16GB? Before windows used to show it as 11GB but now showing 8.24 GB is there a fix for this or is the bad or do I have to live with it.. ?
read the whole tut again it tells you why since you have to move partition tables.
Yes...it's a rather small deal anyway...there are 64gb SD card after all.
mkohman said:
Thanks for your help guys .. followed the german dudes tutorial and downloaded the .PIT file and managed to re flash stock ICS .. Now the only issue is my internal memory is showing 8.24 GB.. what happened to the other approx 8GB? I thought the Note was 16GB? Before windows used to show it as 11GB but now showing 8.24 GB is there a fix for this or is the bad or do I have to live with it.. ?
Click to expand...
Click to collapse
My advice is "live with it". Coz what the "German dudes" pit files do is avoid the "locked" sectors in your internal card. While you can try different pit files or try create new partitions via adb -- you probably wont gain much.
Or you could send it to Sammy for a warranty claim, after resetting the flash counter and then bricking it again via odin using the original pit file. Basically what you need to do is erase all evidence that u tampered with it. This is a risky option... (You can tell them phone got messed up in kies upgrade). This happened to me (on an almost new note, so i kinda did the same, except that i went a step further and deleted the boot-loader as well = hard brick. However i dont recommend it). And they replaced the phone.
I emphasize again this is risky -- and do more research before if you do this.
Problem as of now is since you've modified the pit -- and also the phone is working, you cant claim now.
nipuna said:
My advice is "live with it". Coz what the "German dudes" pit files do is avoid the "locked" sectors in your internal card. While you can try different pit files or try create new partitions via adb -- you probably wont gain much.
Or you could send it to Sammy for a warranty claim, after resetting the flash counter and then bricking it again via odin using the original pit file. Basically what you need to do is erase all evidence that u tampered with it. This is a risky option... (You can tell them phone got messed up in kies upgrade). This happened to me (on an almost new note, so i kinda did the same, except that i went a step further and deleted the boot-loader as well = hard brick. However i dont recommend it). And they replaced the phone.
I emphasize again this is risky -- and do more research before if you do this.
Problem as of now is since you've modified the pit -- and also the phone is working, you cant claim now.
Click to expand...
Click to collapse
Thanks for your assitance bro.. I will live with it. .I don't mind loosing 3 gb .. Already got 32GB SD card so no issue. Just happy its all back up and running really.. Big thanks to the German brother you the man
Its Forest1971 who first wrote this workaround and it was hg42 who rewrote the pit file and it was Dr null who proposed this way, Its all XDA members who helped you out of this brick. Not some German sites. Google throws up German results first
I am not harsh by anyway saying this. Just want to write it as it happened.
Was witnessing all the issues.
I am writing a guide for Noobies for bricks. Guess I get some help ....
prabhu1980 said:
Its Forest1971 who first wrote this workaround and it was hg42 who rewrote the pit file and it was Dr null who proposed this way, Its all XDA members who helped you out of this brick. Not some German sites. Google throws up German results first
I am not harsh by anyway saying this. Just want to write it as it happened.
Was witnessing all the issues.
I am writing a guide for Noobies for bricks. Guess I get some help ....
Click to expand...
Click to collapse
I actually followed his guide and repartioned manually and only lost about one Gbyte vs using the pit file and losing over 3 G bytes. Took a lot of trial and error though
Sent from my GT-N7000 using Tapatalk 2
RE:
mkohman said:
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
Click to expand...
Click to collapse
hi! i was in the same state as you! now, listen very carefully. Now, all you have to do is to use another PC and run ordin. Everything should work fine! My note was soft-bricked yesterday night and i had tried endless counts of tries just to get it up and running. Just earlier today,I saw someone who posted a comment in a similar forum and suggested that you should try a different PC it worked. AND IT worked for me now, just use this pit file that i had upload and download any (G-N7000)stock firmware that has (code.md5, modem.md5 and csc.md5). just place the pit file in ordin. ( do note you will lose 3gb of your internal memory) and click start hopefully it worked for you
-yours truly-
zairui from Singapore
can you contact entropy before sending your unit to samsung??
entropy is looking, if im not mistaken, for a purely stock bricked note... kindly pm him
zairui said:
hi! i was in the same state as you! now, listen very carefully. Now, all you have to do is to use another PC and run ordin. Everything should work fine! My note was soft-bricked yesterday night and i had tried endless counts of tries just to get it up and running. Just earlier today,I saw someone who posted a comment in a similar forum and suggested that you should try a different PC it worked. AND IT worked for me now, just use this pit file that i had upload and download any (G-N7000)stock firmware that has (code.md5, modem.md5 and csc.md5). just place the pit file in ordin. ( do note you will lose 3gb of your internal memory) and click start hopefully it worked for you
-yours truly-
zairui from Singapore
Click to expand...
Click to collapse
Not necessary to use the 3gb regain patch.
There's a 1gb or 2gb regain patch also. And it's enough.
WJ
Sent from xda-developers Galaxy N7000 ICS 4.0.4 LRK / CriskeloROM v.11.1 / Speedmod K3-12
---------- Post added at 11:34 PM ---------- Previous post was at 11:26 PM ----------
mkohman said:
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
Click to expand...
Click to collapse
Though so many ppl told u alrd, i just want to say, in any case, when u r in ICS alrd, it is totally prohibited to do factory reset through CWM with samsung ICS original kernel.
When u need to wipe or factory reset, make sure u r on a safe kernel like speedmod or notecore.
If u want to recover ur note, just use the pit file method. It works.
Make sure u use the correct patch of 16gb or 32gb, depends on ur note.
Always try from the smallest patch, so u won't loose so many storage.
Anyway, latest CriskeloROm with speedmod is the best for battery life nd performance.
WJ
Sent from xda-developers Galaxy N7000 ICS 4.0.4 LRK / CriskeloROM v.11.1 / Speedmod K3-12
I'm having the same issue now.
I did wipe data / factory reset with stock ICS kernel and I think, I bricked the Note.
I didn't know there were such issue.
I couldn't find a ROM with 3 files (code.md5, modem.md5 and csc.md5).
Please kindly guide me where to find such ROM.
i bricked mine last week and used the patched pit files to restore i went through a few pit files b4 i found one that worked i now have about 9 gb nand left but my phone works and has jb on it now
anubis1126 said:
i bricked mine last week and used the patched pit files to restore i went through a few pit files b4 i found one that worked i now have about 9 gb nand left but my phone works and has jb on it now
Click to expand...
Click to collapse
So we dont need 3 files ROM?
Kind of a niche guide, but at least non-Japanese people owning an SC-01C have some sort of guidelines.
Before we begin
The SC-01C is the rebranded Japanese version of the P1000, locked exclusively to NTT DoCoMo. If you have this model and want to upgrade and/or flash custom ROMs with it, this guide may be able to help you.
Before beginning, you have to check your firmware version. What you'll have to download will depend on it. If you have Android 2.2 Froyo, read on, otherwise, if you're already running Android 2.3 Gingerbread skip to the Gingerbread Users section.
Also, based on experience, if you want to upgrade to other ROMs in the future you will have to keep your stock GB ROM file, your gt-p1000_mr.pit, the dbdata.tar and the entire Overcome kit (kernel and ROM). You will need all of them in the future because I've found that to install a new ROM you have to repeat the entire process of restocking to GB, then installing Overcome Kernel and ROM, then installing whatever ROM you want. It sucks, but it's the only way I've seen so far.
Froyo Users
If you're planning to install a custom ROM, you can't do it on Froyo straight away, at least not on a stock ROM with a protected bootloader. If you don't know if your bootloader is protected or not, the safest thing to do is to first upgrade your firmware to the stock Japanese Android 2.3 Gingerbread. Then you can follow the Gingerbread guide afterwards.
Froyo Users Will Need
Stock Japanese GB ROM (you can get it from here or from SamFirmware.com). The ROM is a .tar archive file, so you will also need 7-Zip or another file extracting utility to extract files from the tar file.
Odin 1.7 (higher versions will likely not hurt either)
Heimdall (in case Odin doesn't work or you aren't running Windows)
Upgrading to Gingerbread
Make sure your PC has the drivers for your Tab. If you've already connected your PC to the Tab before, you already have them. Otherwise, plug your Tab into your PC and let the drivers install automatically. This works even if you're in Download Mode. If they don't install automatically, you might need to download Samsung Kies or just the Samsung USB Driver for Mobile Phones to get the driver to install.
[FOR HEIMDALL USERS]
You will need to plug in your Tab and run zadig.exe for your drivers, which is found either in the same folder as your Heimdall.exe or in the Drivers folder in that same folder, depending on which version you have. From there, select Options -> List All Devices, then select Gadget Serial or Android USB Composite Interface, then click Install Driver.
After getting the drivers, unplug your Tab (you can keep the PC end plugged in). Turn off your Tab and plug your USB Interface cord into your PC (not the Tab just yet), then put your Tab into Download Mode. You can do this by either holding down the Power and Volume Down keys while the Tab is off, or simply holding down the Volume Down key while plugging in the cord to your Tab. If done correctly, you should see a screen with a yellow Android with a shovel, together with the words "DOWNLOAD MODE, DO NOT TURN OFF TARGET!"
If you're running Windows and using Odin, extract the gt-p1000_mr.pit from the .tar archive into the same folder as the archive. Otherwise, if you're running Heimdall, extract the entire archive into the same folder as your Heimdall.exe.
Plug your Tab back in if you haven't already. The next step will vary for Odin and Heimdall users.
[FOR ODIN USERS]
Open Odin and check if there is a yellow box amongst all the white ones which says [COM4] or something like that, it doesn't matter as long as the box is yellow.
Click PIT and select the gt-p1000_mr.pit you extracted from the stock Japanese GB .tar file, then click Start. This will re-partition the device, and it is absolutely critical that this is done first, as missing this step can cause a brick.
After the PIT flashing is successful, click Reset, then click PDA and select the stock Japanese GB .tar file, and click Start. You will have to wait for a few minutes while the ROM flashes. Progress bars will appear both on the Tab screen and Odin.
NOTE: If after flashing you boot into Recovery Mode and you get the following error:
Code:
E: part(1) DATA Checksum Error
E: part(1) Checksum Error
Internal MMC checksum verify failed.
Then you will have to download and flash dbdata.tar as PDA (Google "P1000 dbdata.tar"; it's about 1.25MB or so). That should solve it.
[FOR HEIMDALL USERS]
Since you already extracted the contents of the stock Japanese GB .tar file into the same folder as your Heimdall.exe, all you have to do is run the following command from a Terminal window (or Command Prompt if you're running Windows):
Code:
heimdall flash --repartition --primary-boot boot.bin --cache cache.rfs --dbdata dbdata.rfs --factoryfs factoryfs.rfs --pit gt-p1000_mr.pit --modem modem.bin --param param.lfs --secondary-boot Sbl.bin --kernel zImage --verbose
Wait a few minutes while Heimdall flashes the ROM. It should inform you when the flashing is successful.
After the flashing is successful, you should now be running stock Android 2.3 Gingerbread. You can stop here or continue on to the Gingerbread Users section for flashing a custom ROM.
Gingerbread Users
Since you're already on Gingerbread, which is the latest stock Android version you have, you're probably reading this guide to find out how to install custom ROMs. Personally I've found, after bricking my Tab a couple of times, that trying to flash custom ROMs from the stock Japanese GB ROM doesn't work unless you flash the Overcome kernel and ROM first.
Hence, the first step to getting a custom ROM running on an SC-01C is to flash the Overcome kernel. For instructions on how to do this, go to the guide thread at the end of the paragraph. You can skip the restocking part, as you're already running stock GB. Instead, follow the instructions from Step 7 of the guide, found on Page 10. After following the instructions there and flashing the Overcome kernel and ROM, you should now be able to flash any other custom ROM you want, following the instructions for the regular P1000.
Getting the Overcome kernel and ROM: http://forum.xda-developers.com/showthread.php?t=1881981
Questions, Answers and Possible Issues
My SC-01C is stuck at boot logo after trying (and failing) to flash custom ROM.
Solving this issue depends on your firmware version and whether or not you can still get into Download Mode. If you can, just follow the instructions in this guide exactly and the problem should be solved.
My SC-01C is stuck at phone-exclamation mark!-computer screen.
This is also likely because of a failed ROM flashing or firmware upgrade. In that case, you can use Heimdall OneClickUnbrick to fix it. A guide to do so can be found here.
My SC-01C isn't detected by Odin, and/or Heimdall produces a "Claiming interface failed" error.
Your drivers aren't being detected and either need to be installed or reinstalled. To force a driver reinstall on Windows, plug in your Tab, go to the System Tray, right-click Safely Remove Hardware and Eject Media, then select Open Devices and Printers. Find your Tab's device name from there, then right-click it and select Remove Device, then unplug your Tab and plug it in again. The drivers should reinstall automatically. If they still don't reinstall, download Samsung Kies or the Samsung USB Driver for Mobile Phones and try again.
For other possible questions or concerns, please reply to this thread.
After successful repair, No Network/ No service
I followed the first method and recovered a bricked P1000 docomo
But No network/service
Any ideas ?
dannyogolo said:
I followed the first method and recovered a bricked P1000 docomo
But No network/service
Any ideas ?
Click to expand...
Click to collapse
You'll need to modify it further to get it to work with other providers. I'm personally not sure if it's a hardware or a software hack, because I paid someone to unlock my Tab back when I didn't know jack **** about modding. If it was already unlocked prior to being bricked, try to flash a new ROM over it. Either way, please hit back if you find the answer so I can add it to the FAQ section.
Hi! I just got the SC-01C & it was already loaded with a custom ICS firmware. Would it be ok to flash another custom firmware DIRECTLY? or Do I still need to flash the GB first?
only root
how to root without change stock rom?
It is possible ?
Thank you
zmeus said:
how to root without change stock rom?
It is possible ?
Thank you
Click to expand...
Click to collapse
Yes it's possible, just Google "how to root galaxy tab". There's a few methods, so just pick one.
Sent from my GT-P1000 using xda app-developers app
Thank you
This it will help me for sure.
Sent from my GT-I9100 using Tapatalk 4
"Hi im a noob and i hate myself"
finally found a thread that that covers japanese p1000.
I have a one it was given to me and still on android froyo 2.2 it is been unlocked by software and i don't know if its been rooted or not.
for the past days i've been looking over the net for this particular device to be upgrade to the latest jellybean rom.this will be very helpful for me since i dont know anything about flashing. been reading threads over and over bec i dont want to brick this device for i use it as a secondary phone
Will flashing to the original docomo GB 2.3... stock firmware make the tab in an locked state again? and is the new rom like the cyanogenmod 10.1 or 10.2 have a built in unlock?
joevinz said:
"Hi im a noob and i hate myself"
finally found a thread that that covers japanese p1000.
I have a one it was given to me and still on android froyo 2.2 it is been unlocked by software and i don't know if its been rooted or not.
for the past days i've been looking over the net for this particular device to be upgrade to the latest jellybean rom.this will be very helpful for me since i dont know anything about flashing. been reading threads over and over bec i dont want to brick this device for i use it as a secondary phone
Will flashing to the original docomo GB 2.3... stock firmware make the tab in an locked state again? and is the new rom like the cyanogenmod 10.1 or 10.2 have a built in unlock?
Click to expand...
Click to collapse
No, 2,3 has an unlocked bootloader. Just follow the guide carefully step by step and you should be fine.
geno93n0 said:
No, 2,3 has an unlocked bootloader. Just follow the guide carefully step by step and you should be fine.
Click to expand...
Click to collapse
ok that's good to know, i'll prep up first before having a go. just be patient with me pls. bec from time to time i'll be asking you alot if i mess up. . thank in advance. thank button has been used.:good:
joevinz said:
ok that's good to know, i'll prep up first before having a go. just be patient with me pls. bec from time to time i'll be asking you alot if i mess up. . thank in advance. thank button has been used.:good:
Click to expand...
Click to collapse
No problem, ask away. I made a lot of mistakes by experimenting on my own, so I made this guide to make the process easier for people with our model.
Hi i have a problem with SC-01C Gingerbread OMKE2, ive been stuck in boot.bin and it fails to flash the overcome using ODIN, what should i do? pls help
Help I think I am bricked
I have a sc-01c bought in japan...I tried flashing and now all i get is the docomo screen...I think i may have deleted everything on the tab...I can get into dl mode but whether flashing with odin or heimdall i get errors...Is there a way to wipe totally and reinstall from scratch....
WILLIEFRANCE said:
I have a sc-01c bought in japan...I tried flashing and now all i get is the docomo screen...I think i may have deleted everything on the tab...I can get into dl mode but whether flashing with odin or heimdall i get errors...Is there a way to wipe totally and reinstall from scratch....
Click to expand...
Click to collapse
What are you Trying to do? and what errors?
SC-01C
rence.slvdr said:
What are you Trying to do? and what errors?
Click to expand...
Click to collapse
I am trying to install the stock rom using odin. I flash the pit then reboot go back to dl mode and flash the tar(stock) i think i hosed the device...Odin says it passed and it reset...but all i get is docommo screen then after the samsung galaxy screen and it keeps blinking ever few minutes like it cant reboot...I ALSO tried flashing the newer Stock 2.3? and the same issue...
I think I may have mucked up the software but can get into DL mode...any ideas?
I followed the directions but still no joy....Perhaps I am dense...
But basically
Flash pit
reboot
Flash stock
Blinking samsung
Odin says reset and no errors...
WILLIEFRANCE said:
I am trying to install the stock rom using odin. I flash the pit then reboot go back to dl mode and flash the tar(stock) i think i hosed the device...Odin says it passed and it reset...but all i get is docommo screen then after the samsung galaxy screen and it keeps blinking ever few minutes like it cant reboot...I ALSO tried flashing the newer Stock 2.3? and the same issue...
I think I may have mucked up the software but can get into DL mode...any ideas?
I followed the directions but still no joy....Perhaps I am dense...
But basically
Flash pit
reboot
Flash stock
Blinking samsung
Odin says reset and no errors...
Click to expand...
Click to collapse
This happened to me as well, it's why I wrote this guide. Try the Overcome method that I posted in the guide, or search for it in this forum. Also, are you using the stock Japanese GB ROM or just a normal stock ROM? You need to use the stock Japanese Gingerbread ROM. I provided links in the guide.
rence.slvdr said:
Hi i have a problem with SC-01C Gingerbread OMKE2, ive been stuck in boot.bin and it fails to flash the overcome using ODIN, what should i do? pls help
Click to expand...
Click to collapse
Don't flash them all at once. Look at the Overcome guide carefully.
pls help
hi.. im new here and i have a problem with modding my sc01c tab. im already running on official gingerbread SC01COMKE2 firmware and im also rooted. i followed all the steps but always ended up with a soft brick. heres what i did.. i downloaded overcome files from http://forum.xda-developers.com/showthread.php?t=1881981 and followed step by step guide. i flashed Overcome_Kernel_v4.0.0.tar and boot into recovery mode.. then flashed Overcome_7_Series_v4.1.0_Wipe.. but it says cannot open BAD FILE. i redownload even the no wipe version but same happens. i tried to restock using GB-Stock-Safe-v5 but it failed in odin.. whats weird is that when i flashed my tab with official firmware it succeeded without a problem.. can you guys help me here? what did i miss or do wrong? pls dont hate me much im just a noob.
geno93n0 said:
No problem, ask away. I made a lot of mistakes by experimenting on my own, so I made this guide to make the process easier for people with our model.
Click to expand...
Click to collapse
ah finally had the time to modd my docomo tab, heres what happened, fashing the pit file went ok, but flashing the rom went haywire ended up brick. i did everything to the letter but to no success. i manage to unbrick the tab and redo the whole thing but i always end up bricking it. rom fails to flash. any ideas? should i be rooted in froyo before doing this?
ah finally after countless trial and error finally updated my tab to gingerbread, now next step is to root and install clockwork recovery mod. i will not rst until my tab gets the lates jellybean rom hahahah,
Hi guys,
I have big problem with my Core Plus. I'm little bit skilled with rooting, flashing custom ROMs and so on, but not for SAMSUNG devices. SO what's the problem?
One day I used ODIN for flashing latest stock ROM for my Core Plus. The problem is that I downloaded wrong STOCK file which belongs to other SAMSUNG phone. So flashing process through ODIN stopped and I had no chance. Now my phone is completely wrong, all partition system is damaged.
> When I turned it ON, I saw only big yellow triangle with info about broken update and I have to use Samsung Kies sw and go through Recovery bla bla.....of course I cannot use Kies SW, it doesn't recognize connected phone in this status
> I cannot boot to Recovery mode now (POWER + APP + VOLUP buttons). Before it goes ok so I think that Recovery partition is also broken
> I tried to use .PIT file and checked boxes Auto Reboot, Re-Partition, F.Reset Time, Nand Erase ALL, Phone Bootloader Update and Phone EFS Clear. Al process went ok, I rebooted phone but I see only Samsung initial logo and small red exclamation mark in the left upper corner. I still cannot enter Recovery mode
> ODIN mode (POWER + APP + VOLDOWN buttons) is still working
So when I try to flash official STOCK ROM through ODIN, it allways ends/stop with this message:
<ID:0/004> hidden.img
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
SO what to do now? Is there some way, how to fix whole partition system? May I use ADB commands or what to do?
Thank you very much!
Rado
I tried also use ODIN 3.07, 3.09 and 3.10, also with different .md5 roms, but allways the same result. Process allways failed on the same step (described upper)
So in my problem....phone completely hard-bricked. I couldn't get into Recovery mode, but through ODIN I flashed Recovery image. Now recovery is working, I deleted and formated all partitions and cache. After that I tried to flash stock .MD5 file through ODIN, but the same result. It allways fails during flashing Hidden.img file... I think that partition named "hidden" is not in my phone as I discovered through ADB commands. Now when I turn ON the phone, I see original SAMSUNG Galaxy Core Plus SM-G350 logo (with small red exclamation mark in left upper corner.....I don't know what it means, but it's there), but after that phone shows only black screen. But I think I'm on a good way...
Because today is no flashable Android for this model, I tried to flash from SD card .ZIP for another similar phone - Galaxy Trend Plus. Difference between Core Plus and Trend Plus is in screen size. I knew that it cannot work properly, BUT - whole flashing process of that .ZIP was OK. So that means that I can fix my phone, but only with flashable .ZIP . I'm affraid that I have to wait till someone create flashable .ZIP from stock ROM for Galaxy Core Plus
SOLVED I found that original stock for Afganistan coutry is smaller (appr. 300MB) than other origo ROMs. So I flashed it through ODIN and flash process worked ! After that I flashed original Slovakia stock file through ODIN and it's OK now :cyclops:
I have same problem. What exactly Afghanistan stock do you flash?
sm g350m unbrick , root , steps
Dr_Wolodya said:
I have same problem. What exactly Afghanistan stock do you flash?
Click to expand...
Click to collapse
Hi , I was in the same situation , I have a samsung galaxy core Plus sm G350M and was in android 4.4.2 and cannot root it with anything , so I tried 4 different roms from sammobile and after softbrick (the message that says conected to Kies to fix the software or something in that nature ), and only one worked for me the following Rom:
G350MNXUANB4_G350MMXANB4 this rom has android 4.3 , and I used Odin 1.85 to installed it. Then after the phone came to life I used Iroot to rooted and it worked in the first try.Then I installed Supersu and eventhough it asked me like 5 times to grant permission and said once that it was not granted , finally it worked and the phone. So know I have my sm G350m alive and rooted, now I want to unlocked it with one of my tools (octoplus), I will keep you posted.
If you need any help let me know, and if any of the information helped you, I will appreciate your thanks.
Hopefully I helped one friend with your issue.
riclau_75 said:
Hi , I was in the same situation , I have a samsung galaxy core Plus sm G350M and was in android 4.4.2 and cannot root it with anything , so I tried 4 different roms from sammobile and after softbrick (the message that says conected to Kies to fix the software or something in that nature ), and only one worked for me the following Rom:
G350MNXUANB4_G350MMXANB4 this rom has android 4.3 , and I used Odin 1.85 to installed it. Then after the phone came to life I used Iroot to rooted and it worked in the first try.Then I installed Supersu and eventhough it asked me like 5 times to grant permission and said once that it was not granted , finally it worked and the phone. So know I have my sm G350m alive and rooted, now I want to unlocked it with one of my tools (octoplus), I will keep you posted.
If you need any help let me know, and if any of the information helped you, I will appreciate your thanks.
Hopefully I helped one friend with your issue.
Click to expand...
Click to collapse
i have diferent problem with my SM-g350m, my touch broke so i replaced it, te problem is that the touch is not working, i tried flashing other firmware but it doesn´t work, do you know what could be de problem?
Galaxy Core PLus (SM-G350) firware upgrade encountered an issue both odin & kies
i have Galaxy Core PLus (SM-G350) with firware upgrade encountered an issue. both odin & kies give this message after flash. can any one help? is it software hardware?
Hi!
I have a galaxy sm g350 croatia t mobile..I downloaded stock FW from sam firmware.After i start flashing with odin 3.11 i recived eror message, after ciple seconds,,I tryed diferent usb ports.. I using win10....Can you help?
thocenski said:
Hi!
I have a galaxy sm g350 croatia t mobile..I downloaded stock FW from sam firmware.After i start flashing with odin 3.11 i recived eror message, after ciple seconds,,I tryed diferent usb ports.. I using win10....Can you help?
Click to expand...
Click to collapse
* Did you install the correct drivers?
* Did you turn off Antivirus, etc.?
* Did you try an older version of Odin? (3.09 should be good)
* Are you sure your cable isn't faulty?
Hi!
I have sucsses but with another carirer stock rom.. But i not resloved eror ; when i try long press home button i have recive ui system eror..How i can fix this ui sys eror ? Phone is rooted but on stock rom...
rado77 said:
SOLVED I found that original stock for Afganistan coutry is smaller (appr. 300MB) than other origo ROMs. So I flashed it through ODIN and flash process worked ! After that I flashed original Slovakia stock file through ODIN and it's OK now :cyclops:
Click to expand...
Click to collapse
Like dude , how about linking the rom because I have the same problem, like I can't find that rom can you please help me!!
I have the same problem dude for real!!
Hi. I'll try to be as detailed as possible.
I have been using the Lollipop 5.0.1 I9505XXUHOA7 German ROM that got leaked early last month, and have just had a few niggling issues, like no silent mode.
So, I looked at SamMobile yesterday and found that there are later versions of Lollipop for the S4 that fixed things like silent mode. I obtained I9505XXUHOB7.
However, when using Odin to flash it to my phone, each and every time, it has gotten to the very end of system.img.ext4 (takes about 5 minutes), and then fails at the very end. I've tried a number of things including a different cable and different USB ports, flashing a new recovery and trying to reboot through that, and even obtaining the CSB_signed_Fusion3_EUR_0325_V2.pit file to Re-partition. At this stage, I don't care if I lose files. I keep most stuff backed up. Just really want my phone to be up and running again, and not too sure what to do.
When I flashed the I9505XXUHOA7, it came with Bootloader, PDA, Phone and CSC to use within Odin, whereas any of the newer ROMs don't seem to have anything but the .tar.md5 file to use in PDA.
Any help would be greatly appreciated. Thanks very much.
Mate, when you download the file in Sammobile you only get 1 .tar file.. it comes with everything.. not like the leaked OA7
1. try using the latest odin 10.6 i think, AP to flash Firmware
2. Reinstall drivers to your PC
3. Or try to redownload a firmware again.. latest is OC6... it might be a bad download too..
4. Refrain using .pit file.... no good at all! Specially for official firmware...
I always brick my phone before and i had no issues flashing diff firmwares from diff country
Did you try flashing the OA7 again? The leaked OA7 (4 files + pit) is a service firmware and should fix issues like these (just to make it running again). After success, you should try an other firmware f.e. OB8 (maybe a bad download?)
Greetings,
Yesterday I was about to change my current rom as my phone was running on a custom rom that I found here on the forum with a CWM recovery.
So I went into recovery mode to make a nandroid backup for my device just incase of something bad happens.
When I started the backing up process it took a min or 2 to start and transferring the data and afterwards the device turned off and it went to a black screen with the android logo and it says downloading don't turn off target..
the thing is it still on that screen since yesterday and I can do anything about it because it took longer than the usual as the youtube videos showed me.
I tried turning off the device and turning it back on and still no luck.
I went to download mode to bascially flash a TWRP recovery or a root using odin to later on flash the rom that I wanted but I had no luck as every single time I try to flash something in odin it says "There is no PIT partition"
I looked up online and I found few PIT files and I tried again and its the same thing but it says re partition operation failed something like that.
after doing some research I found even If I flashed the stock firmware it won't change anything as the device won't accept it because of the PIT thing.
I really need your help guys, what can I do now ?
Try using different USB cables and USB 2.0 ports to flash a stock ROM with Odin.
audit13 said:
Try using different USB cables and USB 2.0 ports to flash a stock ROM with Odin.
Click to expand...
Click to collapse
I did and I still have the same issue..
I even tried a different computer and nothing really works, keep in mind that I have downloaded the official stock rom and tried to flash that too and I still have no luck.
I really need help guys :/
Find the correct PIT file and flash that or take for service repair .
Alright I'm writing this reply to whoever searches online for a similar problem.
I fixed my phone long time ago and the problem was ... "the phone USB port"
it turns out my port isn't really good as it had issues in the past and it was changed but I didn't know that until recently and I completely forgot about it.
I didn't fix my port though but how did I fix the phone ?
well it turns out even if your port was bad (depends on the ports condition of course) getting an original cable can help you flash something isn't big such as a root or a recovery mode.
in my case I used an original cable a normal micro USB but after using an original USB 3.0 cable I was able to flash a root and a custom recovery, yes I tried flashing a stock firmware but it I didn't work because of how my port is acting I was kinda limited to the things I can flash so I was able to flash small files but not an entire operating system.
So I flashed a root and a TWRP custom recovery in order to be able to flash an entire OS through the phone itself without the need of plugging it to my computer so I uploaded my custom ROM on an SD Card and flashed it through the recovery mode and I was back in business!
I can safely say the case is solved, I don't know if you guys close the solved topics here or something but thanks for everyone's help.
SEE YA LATER
But port is not PIT problem .