I am using Galaxy Y S5360 and also my phone is rooted. After some fooling around in the new rooted device i guess i bricked it.
I had installed supersu and also different kernel version and also the creed custom rom. After some unknown things i landed up booting my phone where the screen just shows the Samsung galaxy y young written and nothing. I tried getting into recovery mode but with no success. I tried flashing a stock rom via odin but its also says failed.
Here is the code
Code:
<ID:0/019> Added!!
<ID:0/019> Odin v.3 engine (ID:19)..
<ID:0/019> File analysis..
<ID:0/019> SetupConnection..
<ID:0/019> Initialzation..
<ID:0/019> Get PIT for mapping..
<ID:0/019> Firmware update start..
<ID:0/019> boot.img
<ID:0/019> NAND Write Start!!
<ID:0/019>
<ID:0/019> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am using firmware provided here. S5360_DDLA3_ODDLA2_DDLA2 (revision 1)
I am unable to get into the recovery mode. Holding the power up key and the home button key with power key just brings the galaxy y written in black screen and nothing else. In download mode previously it was Current Bin: Custom rom but now its Samsung official. And the custom bin down : yes(1 counts) is showing.
Please help me. How to get my phone back?
or which pit or csc or other files to be used with the pda?
or what shall i do to make my phone work again.
please help me.
After using Odin to perform a Nand Erase All on my n8000, the boot screen(which should be Samsung Galaxy Note 10.1 GT-N8000) turns into the Download mode screen. All features are working. How to recover. Thanks.
Add: and is still booting. Only UI change
Boot Logo Modder
Kavin Zhao said:
After using Odin to perform a Nand Erase All on my n8000, the boot screen(which should be Samsung Galaxy Note 10.1 GT-N8000) turns into the Download mode screen. All features are working. How to recover. Thanks.
Add: and is still booting. Only UI change
Click to expand...
Click to collapse
See here: BOOT LOGO MODDER :good:
And you can use your own BOOT LOGO ofcourse:laugh:
tanker32 said:
See here: BOOT LOGO MODDER :good:
And you can use your own BOOT LOGO ofcourse:laugh:
Click to expand...
Click to collapse
Exactly the same problem.
Thanks a lot for that, going to try it. :good:
Well, that worked. But after flashing another picture provided by the second post(on another thread), a even more serious problem came: Device Bricked Anything helps?
Doesn't even power on(turn on the screen) was it bricked or something else?
Help!!!! What shall I do?
Describe your problem in detail, please!
Kavin Zhao said:
Well, that worked. But after flashing another picture provided by the second post(on another thread), a even more serious problem came: Device Bricked Anything helps?
Click to expand...
Click to collapse
You must describe what exactly you did before brick the device.
1. Type of your device
2. Are you used my MOD with new picture before brick your device?
3. Did you exactly proceed step by step like I describe in my thread?
4. Was your picture in good size (1280x800 landscape mode and portrait mode 800x1280 according to type of device) ?
5. Picture must have same name, same type (logo.jpg) as is in my MOD!
6. Check your ZIP, if you have good path and structure as in my MOD exactly!
7. If you don't made a mistake and you've kept my proceed, problem is somewhere else.
Try to go to recovery, download my first type MOD and wipe cache, dalvik cache and install ZIP and don't forget reboot back to RECOVERY
and after then use system reboot !!!!! I'm waiting for your answer. Then we will try something else (according to your problem) :good:
---------- Post added at 11:18 AM ---------- Previous post was at 11:09 AM ----------
Kavin Zhao said:
Doesn't even power on(turn on the screen) was it bricked or something else?
Help!!!! What shall I do?
Click to expand...
Click to collapse
You have my answer above, but I see that even POWER ON doesn't work!
Hold POWER more than 30 sec! Then you try go to recovery... If didn't work, hold POWER+VOLUME DOWN and when you see boot logo release
POWER and then VOLUME DOWN. You should be in DOWNLOAD MODE. And then proceed with ODIN software and stock firmware. But I think
that you made mistake when you try put you picture in my MOD in ZIP file.
User jordimra in BOOT LOGO MODDER THREAD has the same problem see:
The picture attached is made by me, but I think it looks like the original Samsung Galaxy Note 10.1 logo.
Edit 1: Installed "boot-logo-GT-N8000.zip" and went OK. But if I modify the "logo.jpg" inside with my own one, the device gets stuck on black (logo?) screen, and can't get into recovery.
Edit 2: Reason: bad zip structure
Thankyou for your care.
Answers:
1.N8000
2.Yes
3.Yes--perhaps
4.Didn't check that, my picture was exactly the same as The picture attached is made by me, but I think it looks like the original Samsung Galaxy Note 10.1 logo.
Edit 1: Installed "boot-logo-GT-N8000.zip" and went OK. But if I modify the "logo.jpg" inside with my own one, the device gets stuck on black (logo?) screen, and can't get into recovery.
Edit 2: Reason: bad zip structure(attachment)
5.Yes
6.Yes
...and huh? how did I enter download mode just now:laugh:?
Is flashing stockrom the only way?
tick nand erase all?
tested, can only enter download mode
My advice
Kavin Zhao said:
Thankyou for your care.
Answers:
1.N8000
2.Yes
3.Yes--perhaps
4.Didn't check that, my picture was exactly the same as The picture attached is made by me, but I think it looks like the original Samsung Galaxy Note 10.1 logo.
Edit 1: Installed "boot-logo-GT-N8000.zip" and went OK. But if I modify the "logo.jpg" inside with my own one, the device gets stuck on black (logo?) screen, and can't get into recovery.
Edit 2: Reason: bad zip structure(attachment)
5.Yes
6.Yes
...and huh? how did I enter download mode just now:laugh:?
Is flashing stockrom the only way?
tick nand erase all?
tested, can only enter download mode
Click to expand...
Click to collapse
If you can go to download mode only, you don't need flash entire ROM. Forget tick Nand erase all and in Odin just flash boot.img or sboot.img, you can find here a lot of this file. But img must be Android same version as you have! Then flash sboot.img through PDA in Odin, and everything should be back in normal.:good: Just try it and then send me, how successful you've been :highfive: Regards, Peter
I have to reboot in to Ubuntu to get the tar files ready for flashing. Sadly, I found Odin cannot flash in anything(sboot.bin and boot.img) except the stock bundle and as you can see, i flashed the stock bundle. And your advice made me found another perfect thing on Google that I have always been searching for-- Dual boot
But it still cannot boot. I think I have to tick Nand Erase All to erase the trouble-causing boot picture.
Wish you good luck, Peter. Cheers:highfive:
P.S While flashing the bootloder(from the tar I made myself), it shows this:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
and stuck here
Keep going...
Kavin Zhao said:
I have to reboot in to Ubuntu to get the tar files ready for flashing. Sadly, I found Odin cannot flash in anything(sboot.bin and boot.img) except the stock bundle and as you can see, i flashed the stock bundle. And your advice made me found another perfect thing on Google that I have always been searching for-- Dual boot
But it still cannot boot. I think I have to tick Nand Erase All to erase the trouble-causing boot picture.
Wish you good luck, Peter. Cheers:highfive:
P.S While flashing the bootloder(from the tar I made myself), it shows this:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sboot.bin
and stuck here
Click to expand...
Click to collapse
Well, I'm so sorry about to hearing that. But as the poet says: "By seeking and blundering we learn." So O.K. try NAND ERASE ALL and then Flash your device by STOCK firmware with ODIN or KIES. Then let me know, how did you get... Regards :fingers-crossed: and for sure :highfive:
Operation Successful
Device successfully unbricked after Nand Erase All
Thank you Peter. It was not your responsibility to help me, but you did... and thank you again for that.
And after this post's been published, I think I'm not a new member anymore.
P.S
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8000ZSCMD2_N8000OZSCMD2_1149484_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Erase...
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> sboot.bin
<ID:0/006> tz.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
It's my pleasure to help!
Kavin Zhao said:
Device successfully unbricked after Nand Erase All
Thank you Peter. It was not your responsibility to help me, but you did... and thank you again for that.
And after this post's been published, I think I'm not a new member anymore.
P.S
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8000ZSCMD2_N8000OZSCMD2_1149484_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Erase...
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> modem.bin
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> sboot.bin
<ID:0/006> tz.img
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
YES! You welcome! :highfive:
It was the picture's problem. I optimized the picture to 1200x800 and it’s OK.
The zip with the optimized picture is below. Should look like the original.
hi
i have the same problem,after flashed this tablet,stuck on bootloop
no access to recovery,i tried many method but no success
i tried:
pit - 4 file - 1 file - all recovery - clear efs & repair again with odin & z3x - nand erase all & ...
but no success
tablet always in bootloop & just can put into download mode
when i turn on tablet,it's take 1 second and reboot and reboot and reboot & ... on Samsung Galaxy Note 10.1
Whenever I am trying to flash my note pro every time odin faild to flash and on my device showing "Invalid ext4 Image" even whenever I want to emergency firmware recovery or update, also failed and stuck on download mode and my device says "invalid ext4 img"
Firmware installation stuck on "invalid ext4 img" for odin or kies both.
My device is SM-P905
Already I have downloaded 3 rom from sammobile, but all file failed to install!
the file are:
P905XXUANAE_P905DBTANA6_DBT.zip
P905XXUANAE_P905OXXANA7_BTU.zip
P905XXUANC3_P905BTUAND2_BTU.zip
when I am trying to flash, odin says:
"<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!"
** I have tried using different usb cable to flash
** I have tried both 3.9 or 3.7 odin
** I have tried different pc to flash
** I have used 2.0 or 3.0 both usb cable
** I have tried both kies3 or previous kies
** I am thinking may be the problem is about pit. and I don't know where I will find a .pit file for SM-P905. some how may be the pit of my note pro is corrupted. i don't know actually I am not a developer!
It would probably be helpful to others if you indicate firmware versions both existing and the one you are attempting to flash in addition to the source of the image you're trying to flash.
Sent from my SM-P900 using Tapatalk
Sounds like your file is bad or the download is corrupted... Try another firmware from sammobile.
Already I have downloaded 3 rom from sammobile, but all file failed to install!
the file are:
P905XXUANAE_P905DBTANA6_DBT.zip
P905XXUANAE_P905OXXANA7_BTU.zip
P905XXUANC3_P905BTUAND2_BTU.zip
Already I have downloaded 3 rom from sammobile, but all file failed to install!
the file are:
P905XXUANAE_P905DBTANA6_DBT.zip
P905XXUANAE_P905OXXANA7_BTU.zip
P905XXUANC3_P905BTUAND2_BTU.zip
and my existing firware is:
Baseband version: P905XXUANA7
Build number: KOT49H.P905XXUANAE
I am also giving the screen shot bellow!
screen shot
muzzy996 said:
It would probably be helpful to others if you indicate firmware versions both existing and the one you are attempting to flash in addition to the source of the image you're trying to flash.
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Already I have downloaded 3 rom from sammobile, but all file failed to install!
the file are:
P905XXUANAE_P905DBTANA6_DBT.zip
P905XXUANAE_P905OXXANA7_BTU.zip
P905XXUANC3_P905BTUAND2_BTU.zip
and my existing firware is:
Baseband version: P905XXUANA7
Build number: KOT49H.P905XXUANAE
I am also giving the screen shot bellow!
YES
cavkic said:
Sounds like your file is bad or the download is corrupted... Try another firmware from sammobile.
Click to expand...
Click to collapse
Already I have downloaded 3 rom from sammobile, but all file failed to install!
the file are:
P905XXUANAE_P905DBTANA6_DBT.zip
P905XXUANAE_P905OXXANA7_BTU.zip
P905XXUANC3_P905BTUAND2_BTU.zip
ok i have a problem with Odin and my S3 since a year
i tell you my story. i have an S3 and its bricked since a year. some times i tried to flash with Odin v3.04 and other version but nothing works. today is it again i want to try to flash it. but i tried EVERY tutorial, every method. but it shows evertime IN EVERY FLASH THIS
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
ok and i readed anything about i should try another cable or anything, but does it really help ?
at the moment i try it with this ROM: I9300XXUGNG3_I9300DBTGNG2_I9300XXUGNA8_HOME.tar.md5 but it wont work :/
so pls help me <3
DursyArts said:
ok i have a problem with Odin and my S3 since a year
i tell you my story. i have an S3 and its bricked since a year. some times i tried to flash with Odin v3.04 and other version but nothing works. today is it again i want to try to flash it. but i tried EVERY tutorial, every method. but it shows evertime IN EVERY FLASH THIS
ok and i readed anything about i should try another cable or anything, but does it really help ?
at the moment i try it with this ROM: I9300XXUGNG3_I9300DBTGNG2_I9300XXUGNA8_HOME.tar.md5 but it wont work :/
so pls help me <3
Click to expand...
Click to collapse
i see a communication fail in between flashing tool /computer and device ...this may be due to damage in your usb cable or may be damage in your port of device. You can try flashing again with a new usb cable .
in case you need pit file visit here
http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
Adi Shakthi said:
i see a communication fail in between flashing tool /computer and device ...this may be due to damage in your usb cable or may be damage in your port of device. You can try flashing again with a new usb cable .
in case you need pit file visit here
http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
Click to expand...
Click to collapse
ok i have 3 USB cables and 3 PC's but i wont work, i tried all combinations and it shows the same error :/ and when i boot in recovery mode it shows many error like "Cant Mount E:/" bla bla when i want to wipe it shows the errors too :/
Hey guys!
I'm from Brazil and I have seen some information in various forums about the desperate attempt to revive the G3502T ...
I am also in this fight ...
Already downloaded all the ROM 's officers ( 03 in total) , several pit files, which are listed below , but none of the attempts resulted in success .
The errors are:
1 ERROR
Phone connected properly ;
no pit file;
rom placed in the " AP " option
ODIN:
Added!!
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
There is no PIT partition.
All threads completed. (succeed 0 / failed 1)
PHONE:
WRITE PROTECTION: Enable
ODIN: flash read failure
2 ERROR
Phone connected properly ;
with pit file;
rom placed in the " AP " option
ODIN:
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
FAIL!
Re-Partition operation failed.
All threads completed. (succeed 0 / failed 1)
PHONE:
WRITE PROTECTION: Enable
SECURE CHECK FAIL: PIT
The tested PIT files are:
CS023g.pit
SM-G3502_9-10-2014_15-13-16.pit
SM-G3502T_7-1-2016_10-43-21.pit
SM-G3502T_7-1-2016_10-45-1.pit
SM-G3502T_25-7-2015_12-27-14.pit
CS02VE3G_ZC.pit
CS02VE3G_ZN.pit
I believe that the error may be in the pit file that has not yet found the correct , or compatibility with ODIN , but tested versions : V3.10.17 / 1.85 / 03.07 ...
As you can see , even some that are tested other versions ...
Well guys this is it!
Sorry for the horrible English .
francis1505 said:
Hey guys!
I'm from Brazil and I have seen some information in various forums about the desperate attempt to revive the G3502T ...
I am also in this fight ...
Already downloaded all the ROM 's officers ( 03 in total) , several pit files, which are listed below , but none of the attempts resulted in success .
The errors are:
1 ERROR
Phone connected properly ;
no pit file;
rom placed in the " AP " option
ODIN:
Added!!
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
There is no PIT partition.
All threads completed. (succeed 0 / failed 1)
PHONE:
WRITE PROTECTION: Enable
ODIN: flash read failure
2 ERROR
Phone connected properly ;
with pit file;
rom placed in the " AP " option
ODIN:
Added!!
Enter CS for MD5..
Binary Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1100)..
File analysis..
SetupConnection..
Initialzation..
Set PIT file..
DO NOT TURN OFF TARGET!!
FAIL!
Re-Partition operation failed.
All threads completed. (succeed 0 / failed 1)
PHONE:
WRITE PROTECTION: Enable
SECURE CHECK FAIL: PIT
The tested PIT files are:
CS023g.pit
SM-G3502_9-10-2014_15-13-16.pit
SM-G3502T_7-1-2016_10-43-21.pit
SM-G3502T_7-1-2016_10-45-1.pit
SM-G3502T_25-7-2015_12-27-14.pit
CS02VE3G_ZC.pit
CS02VE3G_ZN.pit
I believe that the error may be in the pit file that has not yet found the correct , or compatibility with ODIN , but tested versions : V3.10.17 / 1.85 / 03.07 ...
As you can see , even some that are tested other versions ...
Well guys this is it!
Sorry for the horrible English .
Click to expand...
Click to collapse
Hello,
Please post your query here Ask any Query Newbie Friendly with all relevant details, thee experts there maybe able to assist you.
-Vatsal