S4 mini i9195 US with no recovery, cant flash it via odin! - Galaxy S 4 Mini Q&A, Help & Troubleshooting

hello guys, im having a problem with a s4 mini, i dont have a recovery, a friend gave it to me with this problem.
I can get download mode but when i try to flash TWRP or CWM i get the OK signs in odin but it doesnt get into recovery, well it gets to recovery but it says "no command" (sin comando, in spanish).
It used to have jellybean and updated itself to kitkat, it never had a custom rom.
This is what the screen in download mode shows:
ODIN MODE
PRODUCT NAME : GT-I9195
CURRENT BINARY: samsung official
SYSTEM STATUS: Official
KNOX KERNEL LOCK : 0x0
KNOX WARRANTY VOID : 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION ENABLE
I tried lot of things, but my last resort is to ask, if you have anything to help i appreciate!

maybe should try stock rom next with odin.

S3miniFin said:
maybe should try stock rom next with odin.
Click to expand...
Click to collapse
Already tried many stock firmwares for i9195 , when odins flashes it, it reboots to recovery and it says "NO COMMAND" ( Sin comandos ) then reboots and starts again with that.

Did you get this fixed mate. I'm pulling my hair out with the same problem. My son messed up a perfectly good phone that I had used for 3 years, and the toerag won't tell me what he did. (apparently he was texting when it when down) Tried various version of stock ROM and I get get diddly squat. ODIN fails to write the firmware and I get aboot on the phone screen. Current problem is stuck on Bootloop. Might just throw the thing away and buy a new one. Would like to fix it though....I'd be eternally grateful for any advice....Thnx

Capokhatpin,
Your son didn't do anything to your phone ! It's just faulty hardware and common problem to Samsung S4 Mini ...
And until now there are dozens of phones that are broken and there is still no solution for that problem.
So, leave the kid alone ...
Cheers !

I have the similar problem at my i9195 - at booting directly to recovery after "successful" flash of cwm over odin or heimdall, the stock recovery appears again without any change...
So did I understand it correctly that there is no chance to fix it?

lupus92 said:
I have the similar problem at my i9195 - at booting directly to recovery after "successful" flash of cwm over odin or heimdall, the stock recovery appears again without any change...
So did I understand it correctly that there is no chance to fix it?
Click to expand...
Click to collapse
No I think you have different problem, are you flashing cwm recovery 2x? You need to flash it once then boot immediately back into download & flash it a 2nd time. If you only do it once or you do a normal boot between flashes it will not work, start again.

2x? Hmh, i tried it (both odin and heimdall), but it doesn't work either (also 3x or 4x)... again just stock recovery.
The story behind it: An update from stock rom failed, and after it it stuck at boot logo. When starting recovery, error messages that mounting /system failed appear. So I decided to try to flash CM on it -> first custom recovery. I tried the CM recovery, CWM recovery, Twrp.... No success. In Odin mode it says "Current Binary: Samsung Official" and "System Status: Official".
Any ideas how to fix it?

lupus92 said:
2x? Hmh, i tried it (both odin and heimdall), but it doesn't work either (also 3x or 4x)... again just stock recovery.
The story behind it: An update from stock rom failed, and after it it stuck at boot logo. When starting recovery, error messages that mounting /system failed appear. So I decided to try to flash CM on it -> first custom recovery. I tried the CM recovery, CWM recovery, Twrp.... No success. In Odin mode it says "Current Binary: Samsung Official" and "System Status: Official".
Any ideas how to fix it?
Click to expand...
Click to collapse
I couldn't do it, i threw it away, just give the kid a slap, don't keep trying, you deserve better.
God**** phone.

IronRoo said:
No I think you have different problem, are you flashing cwm recovery 2x? You need to flash it once then boot immediately back into download & flash it a 2nd time. If you only do it once or you do a normal boot between flashes it will not work, start again.
Click to expand...
Click to collapse
So, I tried also to flash the stock ROM by booting it with „debrick“ image from SD card and flashing from „download mode“ went good, but after reboot it was same and I couldn't boot into „recovery“ with message „No command....“ or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Sent from my GT-N7000 using XDA-Developers mobile app

Boombastical said:
So, I tried also to flash the stock ROM by booting it with â??debrickâ?? image from SD card and flashing from â??download modeâ?? went good, but after reboot it was same and I couldn't boot into â??recoveryâ?? with message â??No command....â?? or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Click to expand...
Click to collapse
No, sorry I misunderstood @lupus92 original situation.

Boombastical said:
So, I tried also to flash the stock ROM by booting it with �¢??debrick�¢?? image from SD card and flashing from �¢??download mode�¢?? went good, but after reboot it was same and I couldn't boot into �¢??recovery�¢?? with message �¢??No command....�¢?? or something like that. And You write that I have to flash only CWM or other TWRP recovery and then twice in the row. Is that correct ?
Click to expand...
Click to collapse
jobs done so back to xda.
I have wondered if in situations like the above where nothing seems to work if a nand erase in Odin would help, but I've never seen it mentioned here on the S4 Mini forum. Is there a reason?
I've not researched it or tried it, but have seen it done on other forums (maybe the S4????). You have to use the full original stock firmware that originally came with your phone at the SAME TIME (else it will brick) I think and have a back up of your imei (though it should rebuild?). I'm not even sure if it deletes ALL partitions or leaves some ..... might be worth looking into it. @lupus92

IronRoo said:
jobs done so back to xda.
I have wondered if in situations like the above where nothing seems to work if a nand erase in Odin would help, but I've never seen it mentioned here on the S4 Mini forum. Is there a reason?
I've not researched it or tried it, but have seen it done on other forums (maybe the S4????). You have to use the full original stock firmware that originally came with your phone at the SAME TIME (else it will brick) I think and have a back up of your imei (though it should rebuild?). I'm not even sure if it deletes ALL partitions or leaves some ..... might be worth looking into it. @lupus92
Click to expand...
Click to collapse
I have here an S4 Mini and when I boot it with SD Card and 'debrick' image on it, it always fail to write to nand but it allow me to go to 'download mode' and to flash original stock ROM but after succesful flashing and reboot it still have no acces to recovery...
Does flashing only any custom recovery would help ?
Any idea ?
Sent from my GT-N7000 using XDA-Developers mobile app

Boombastical said:
I have here an S4 Mini and when I boot it with SD Card and 'debrick' image on it, it always fail to write to nand but it allow me to go to 'download mode' and to flash original stock ROM but after succesful flashing and reboot it still have no acces to recovery...
Does flashing only any custom recovery would help ?
Any idea ?
Click to expand...
Click to collapse
I don't think another recovery will help, but I'm no expert about this sort of thing. I would say it's worth a try through.
If that doesn't work and you are at the point of throwing your phone away, I wonder if it's worth giving the "nand erase all" command a try as it has been shown to fix write permissions (though I'm not sure if this is your problem) and other major issues software issues. But as it deletes the entire nand memory so you need to be very careful & know exactly what will hapen. You need a backup of your efs/imei (I'd use 2 methods just to be sure as have just read someone couldn't restore it from some app),( can you boot into system?) Also you must use a FULL stock ROM with pit file etc to rebuild partitions.
For example the guy below with a regular S4 seems to be in similar situation, though for different reason, he was able to recover using nand erase all. But our phone is different of course!
Also have read one case where guy had to flash stock with nand erase all ticked then had to immediately reflash stock again without erase ticked.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
--–-------------------------------------
edit; Also another S4 thread they have flashed bootloaders to fix write access to partitions,
http://forum.xda-developers.com/showthread.php?t=1840030
&
http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/

IronRoo said:
I don't think another recovery will help, but I'm no expert about this sort of thing. I would say it's worth a try through.
If that doesn't work and you are at the point of throwing your phone away, I wonder if it's worth giving the "nand erase all" command a try as it has been shown to fix write permissions (though I'm not sure if this is your problem) and other major issues software issues. But as it deletes the entire nand memory so you need to be very careful & know exactly what will hapen. You need a backup of your efs/imei (I'd use 2 methods just to be sure as have just read someone couldn't restore it from some app),( can you boot into system?) Also you must use a FULL stock ROM with pit file etc to rebuild partitions.
For example the guy below with a regular S4 seems to be in similar situation, though for different reason, he was able to recover using nand erase all. But our phone is different of course!
Also have read one case where guy had to flash stock with nand erase all ticked then had to immediately reflash stock again without erase ticked.
http://forum.xda-developers.com/galaxy-s4/help/help-nand-erase-t2863345
--–-------------------------------------
edit; Also another S4 thread they have flashed bootloaders to fix write access to partitions,
http://forum.xda-developers.com/showthread.php?t=1840030
&
http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/
Click to expand...
Click to collapse
Thanks for sharing your thoutghs, but unfortunately I can't boot anymore to 'Download mode'. [emoji45] It can be still booted by 'Debrick' image from SD card but nothing more then that. From there I can't go anywhere further. Without SD Card it doesn't give signs of life except if it is attached via USB it shows as QHSUSB_DLOAD...
I have no time now to play with the phone, but I will try in the weekend again to come to 'Download mode' and to flash again recovery or to erase flash nand cause I have already EFS back up somewhere on my external HD and then we will see what will happened. Thanks again and cheers !
Edit: I can't flash anything thru 'Debrick image' via Odin 3.09. It always give error: Faild to write mmc nand... It can't erase nand nor boot to 'Download mode' ... So I'm clueless at the moment... It looks as the nand is damaged and it can't be accessed anymore... Sadly, I think this S4 Mini will be ended as spare phone for parts only for my girlfriend phone... That's it... If someone have more ideas about it I can still try it... Cheers !
Sent from my GT-N7000 using XDA-Developers mobile app

Related

Has my phone bitten the dust?

Really hope somebody can help.
I have had a galaxy note 2 for about 6 months on Vodafone UK N7100.
Today while i was at work i felt something hot in my pocket, my phone was very hot (i was not doing anything with it) The phone was stuck on the Samsung boot screen.
After a few minutes of looking at this i realised it was stuck and removed the battery. SInce then i have been unable to get past the boot screen, i can't get into download mode or reboot mode. The only things to note. When i turn my phone on a red light flashes. When i plug my charger in the charge icon appears on screen but it does not charge.
Really hoping somebody can help.
I had rooted my phone if that helps (it did not cause this problem and has been functioning rooted for months)
Update
Just managed to get to a screen which warned me about installing custom software and did i want to continue. I said yes and it is now downloading something
How did you get to that screen?
Sent from my Desire S using xda app-developers app
The Mole said:
Really hope somebody can help.
I have had a galaxy note 2 for about 6 months on Vodafone UK N7100.
Today while i was at work i felt something hot in my pocket, my phone was very hot (i was not doing anything with it) The phone was stuck on the Samsung boot screen.
After a few minutes of looking at this i realised it was stuck and removed the battery. SInce then i have been unable to get past the boot screen, i can't get into download mode or reboot mode. The only things to note. When i turn my phone on a red light flashes. When i plug my charger in the charge icon appears on screen but it does not charge.
Really hoping somebody can help.
I had rooted my phone if that helps (it did not cause this problem and has been functioning rooted for months)
Update
Just managed to get to a screen which warned me about installing custom software and did i want to continue. I said yes and it is now downloading something
Click to expand...
Click to collapse
does it get recognize in odin if yes try to flash stock rom and revive your phone hopefully u are not using the 4.1.1 rom better get a 4.1.2 and bring it to life :good:
if u can get to download mode now then flashed philz recovery first. After flashing recovery wipe dalvik, cache partition & then data reset.then u can flash stock using odin. try this if the first one doesnt work
shhbz said:
does it get recognize in odin if yes try to flash stock rom and revive your phone hopefully u are not using the 4.1.1 rom better get a 4.1.2 and bring it to life :good:
if u can get to download mode now then flashed philz recovery first. After flashing recovery wipe dalvik, cache partition & then data reset.then u can flash stock using odin. try this if the first one doesnt work
Click to expand...
Click to collapse
I got there through home volume down and power during boot up.
I can't get into recovery though (using volume up)
Which version of odin should i be using? I am using 3.07
I am using the rom suggested in this guide http://reviews.cnet.co.uk/mobile-ph...e-2-from-rooted-to-factory-settings-50010623/
If i should not be using that where can i get the one i should be using.
When i try to install the stock rom linked above i get the message failed no PIT partition
Thanks for all the help so far
The Mole said:
I got there through home volume down and power during boot up.
I can't get into recovery though (using volume up)
Which version of odin should i be using? I am using 3.07
I am using the rom suggested in this guide http://reviews.cnet.co.uk/mobile-ph...e-2-from-rooted-to-factory-settings-50010623/
If i should not be using that where can i get the one i should be using.
When i try to install the stock rom linked above i get the message failed no PIT partition
Thanks for all the help so far
Click to expand...
Click to collapse
this would be your last hope http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5 follow the guide properly marked in red and remember to tick re partition in odin, if this doesnt work then your phone has been affected by sds due to 4.1.1 rom so u need to take it to service for motherboard replacement which is borne by samsung so no worries, and remember never to use a 4.1.1 rom in note 2 get the 4.1.2 rom or rather they will install that only this time and in future just go through dr.ketan thread http://forum.xda-developers.com/showthread.php?t=1896696 here it will guide you perfect instead following some untidy guides
for odin use 3.04 it works great though i havent tried new version as 3.04 works great you will get it in ketan thread
shhbz said:
this would be your last hope http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5 follow the guide properly marked in red and remember to tick re partition in odin, if this doesnt work then your phone has been affected by sds due to 4.1.1 rom so u need to take it to service for motherboard replacement which is borne by samsung so no worries, and remember never to use a 4.1.1 rom in note 2 get the 4.1.2 rom or rather they will install that only this time and in future just go through dr.ketan thread http://forum.xda-developers.com/showthread.php?t=1896696 here it will guide you perfect instead following some untidy guides
for odin use 3.04 it works great though i havent tried new version as 3.04 works great you will get it in ketan thread
Click to expand...
Click to collapse
Thanks for the advice i am downloading the file now.
I did not manage to install the rom i suggested i was using so i don't think that could have been the issue. My phone just seemed to get hot then stop working, i hope as you suggested it is not my motherboard. Did you say that i should still be covered by the warrenty even though i had rooted my device?
The Mole said:
Thanks for the advice i am downloading the file now.
I did not manage to install the rom i suggested i was using so i don't think that could have been the issue. My phone just seemed to get hot then stop working, i hope as you suggested it is not my motherboard. Did you say that i should still be covered by the warrenty even though i had rooted my device?
Click to expand...
Click to collapse
well your reply is quite confusing
1.did you manage to flash the rom with pit in odin. was it successful or you get any errors
2.does your phone start now
3.if not then your phone has died and it needs to be taken to service guys ,but just check what the status of your phone in download mode is it official or custom . if its official then no worries just go ahead and take it to service guys and tell them abt your issue that the phone stopped working while in pocket dont info them that you rooted it ever just make them blv that it was a sds caused by 4.1.1 rom so they replace it free.
i mean your motherboard
Sorry if i am confusing matters.
I did not manage to flash anything it was just coming up with failed no PIT partition.
Current binary samsung official
My system status is custom
Are these ok to return my phone with?
I decided to take the advice offered and download the recovery but got confused.
Do i need all of the files from that link or just 1?
I downloaded the first one N7100XXDMB2_Factory
It contained
boot
cache
hidden
modem.bin
recovery
sboot.bin
system
tz
None of these are the md5 format
i am now thinking i should have downloaded XXDLJ2_OXA_Factory
Is that correct or was i right with the first file. If i was right downloading the first file then where do i get the md5 files required for odin to do my factory restore.
Know these are very noobish questions just doint want to do anything wrong
In answers to your questions....
1) Did i manage to flash the rom with it in odin
No
I got confused which files i should be using and did not want to do anything without being sure
2) My phone does not start
3) When i am in download mode my phone shows
Current binary Samsung official
My system status is custom
Are these ok to return my phone with?
The Mole said:
Sorry if i am confusing matters.
I did not manage to flash anything it was just coming up with failed no PIT partition.
Current binary samsung official
My system status is custom
Are these ok to return my phone with?
I decided to take the advice offered and download the recovery but got confused.
Do i need all of the files from that link or just 1?
I downloaded the first one N7100XXDMB2_Factory
It contained
boot
cache
hidden
modem.bin
recovery
sboot.bin
system
tz
None of these are the md5 format
i am now thinking i should have downloaded XXDLJ2_OXA_Factory
Is that correct or was i right with the first file. If i was right downloading the first file then where do i get the md5 files required for odin to do my factory restore.
Know these are very noobish questions just doint want to do anything wrong
Click to expand...
Click to collapse
well follow this video but just select all file required and then flash instead flashing twice hope this video helps as u need to select individual file
https://www.youtube.com/watch?v=CMSsoCqZr1w if you still face prob ask the uploader in that thread maybe he can help you and as far as system status is concerned u need to either flash a stock rom or get into recovery to wipe data and factory reset or ven this https://www.youtube.com/watch?v=PpWcM44On88 for your proper understanding. dont you get .tar file and pit file in that download
are u able to enter into recovery mode as first post u mentioned download mode not working now u say its working
shhbz said:
well follow this video but just select all file required and then flash instead flashing twice hope this video helps as u need to select individual file
https://www.youtube.com/watch?v=CMSsoCqZr1w if you still face prob ask the uploader in that thread maybe he can help you and as far as system status is concerned u need to either flash a stock rom or get into recovery to wipe data and factory reset or ven this https://www.youtube.com/watch?v=PpWcM44On88 for your proper understanding
are u able to enter into recovery mode as first post u mentioned download mode not working now u say its working
Click to expand...
Click to collapse
Sorry recovery mode is not working, only download mode, i will have a look at the suggested video.
Thanks again for your continued help
The Mole said:
Sorry recovery mode is not working, only download mode, i will have a look at the suggested video.
Thanks again for your continued help
Click to expand...
Click to collapse
well initially it was a bootloader issue but destroying the pit became an issues hopefully u get it back to life this time
shhbz said:
well initially it was a bootloader issue but destroying the pit became an issues hopefully u get it back to life this time
Click to expand...
Click to collapse
I have managed to get hold of the correct files, however when i try to run them in ODIN ODIN does not get past the stage get PIT for mapping.
Can i try anything without the PIT stage?
The Mole said:
I have managed to get hold of the correct files, however when i try to run them in ODIN ODIN does not get past the stage get PIT for mapping.
Can i try anything without the PIT stage?
Click to expand...
Click to collapse
If your phone doesn't have a partition map, then no, you can't.
You can try, as a last resort, using this guide: http://forum.xda-developers.com/showpost.php?p=43760271&postcount=22
I had a similar problem not too long ago (although it started with all apps crashing and then stuck at bootscreen) and managed to fix my phone.
Sent from my GT-N7100
vladeco said:
If your phone doesn't have a partition map, then no, you can't.
You can try, as a last resort, using this guide: http://forum.xda-developers.com/showpost.php?p=43760271&postcount=22
I had a similar problem not too long ago (although it started with all apps crashing and then stuck at bootscreen) and managed to fix my phone.
Sent from my GT-N7100
Click to expand...
Click to collapse
Sounds like the same issue i have had. Apps kept crashing, i never thought it was the phone just the apps. I will look into the link thanks very much
CAn i just ask what is an EFS and how do i get a backup of it
If you need any help I'm here. Cheers!
Sent from my GT-N7100
vladeco said:
If you need any help I'm here. Cheers!
Sent from my GT-N7100
Click to expand...
Click to collapse
Thanks can i just ask what EFS is and how i get a backup of mine before i carry out your guide.
The Mole said:
Thanks can i just ask what ENS is and how i get a backup of mine before i carry out your guide.
Click to expand...
Click to collapse
EFS is a part of the system that stores your serial number, IMEI and everything related to your phone specifically. You are generally able to back it up using a custom recovery or using software on your PC while the phone is rooted and booted on the android OS. Since you cannot boot into recovery and also can't boot into android itself, I don't think you would be able to back it up.
If you ever installed a custom rom with AROMA, there is a chance you have it backed up already. But if you don't explicitly remember...
vladeco said:
EFS is a part of the system that stores your serial number, IMEI and everything related to your phone specifically. You are generally able to back it up using a custom recovery or using software on your PC while the phone is rooted and booted on the android OS. Since you cannot boot into recovery and also can't boot into android itself, I don't think you would be able to back it up.
If you ever installed a custom rom with AROMA, there is a chance you have it backed up already. But if you don't explicitly remember...
Click to expand...
Click to collapse
Ah ok,
I will give the guide a go and let you know how i go.
Thanks again
I get the error message write operation failed in ODIN, i am guessing that means its dead.
Do you happen to know if i take it back to my phone company to fix if they will be able to tell i had rooted it
on the download screen i have
Current binary samsung official
My system status is custom
could they tell anything from that?

[Q] Soft Bricked....can't unbrick or revert to stock rom...any thoughts?

I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
kinjo1023 said:
I got a replacement GS3 through insurance and rooted it yesterday. Instead of flashing CWM I tried going with TWRP this time but didn't realize that TWRP doesn't read external SD cards and my roms were all saved on the external SD. And of course, this was after I wiped everything. So I tried unrooting and flashing back the stock firmware but it keeps failing in ODIN. So I tried re-rooting and flashing CWM which works but none of the roms will flash. I keep getting a system 7 error or something to that effect when I try flashing any rom. So now I can either get to recovery mode, or download mode. If I power the phone on it gets stuck on the Galaxy S3 screen. Any thoughts as to processes to try? Links? Threads? I've tried just about everything I could find.
Click to expand...
Click to collapse
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. Where is your nandroid backup, you know the one you made before you did anything just incase it didn't go as planned? In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did it fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to the device you are going to want to start from stock. The second sticky thread in this sub-forum is where you should start reading, because based on your post you either need a refresher or never have read it to begin with.
dntesinfrno said:
Since when does TWRP not read external SD cards? It see's mine just fine, for well over a year. In any case you didn't give much information to help troubleshoot. 'I tried unrooting' - if you were going to flash a stock ROM there is no need to unroot anything as the stock firmware is just that, stock. How did if fail in ODIN? Did it say why it failed, what file were you trying to flash? More often than not the system 7 error is caused from an out of date recovery, normally i would tell you to start there but given the fact you admitted to just randomly attempting to flash things to device you are going to want to start from stock. http://forum.xda-developers.com/showthread.php?t=1725839
Click to expand...
Click to collapse
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
kinjo1023 said:
For whatever reason, TWRP wouldn't read my sd card. And when I said I tried unrooting - I just meant flashing back to the stock ROM. Odin fails when it gets to system write. It goes down a bunch of lines of code successfully but when it gets to system write, it fails every time. I've downloaded a few different stock ROM versions for AT&T and tried switching USB ports around my laptop. I've also tried a few different versions of ODIN but I'm not coming up with anything but a soft bricked phone still.
Click to expand...
Click to collapse
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
I could have swore I made sure to check before I started the process but I cant' check now because the phone won't boot. Can't flash back to stock. Can't flash any roms. I can get into download mode and recovery though. It's weird. I've reverted other phones back to stock plenty of times. It just keeps failing no matter what I do with this.
dntesinfrno said:
Did you have usb debugging enabled before you attempted to flash via ODIN? It sounds like it doesn't have permission to write to the /system partition. You can try doing a factory reset from recovery to get past the bootloader and make sure, or use Kies to flash to stock via this thread.
Click to expand...
Click to collapse
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
kinjo1023 said:
Here's another question for you, I've looked all over for the newest CWM in .tar format but everything comes in .img format. I can't use the .img in ODIN to flash to the phone and can't boot my phone to use the CWM app to flash. I suppose I could try TWRP again but when I flashed the first time - TWRP wouldn't read my EXT SD card.....
Click to expand...
Click to collapse
if you could wipe everything get on odin with 4.1.2 update reboot use cf root to root it (if you dont have root) after reboot download ROM Manager from Play Store install CWM recovery (easiest way to root) hope this works

[Q] TWRP 2.6.3.1 Asks for password

I woke up this morning to my phone perpetually rebooting.
I was running a nightly of CM 11.
Now when I try to go into Recovery I get a screen that asks for a password. I have no idea what that password is as I did not set one. I tried wiping data to no avail. I tried flashing a new recovery via Odin this did not work (Odin said successful but the screen on the phone never showed the transfer of the file). No matter what wipe method I use in recovery it just says fail, doesn't work at all and hangs or will say it can't mount. I have searched and searched and tried and tried and I'm stuck. I even tried ADB that didn't work either. Please help!
Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
audit13 said:
Try flashing Philz Touch (based on CWM) over TWRP via Odin. I have always had good luck with CWM and Philz.
Download the tar version: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2att
Click to expand...
Click to collapse
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.
therecker said:
I tried this already. I cannot flash ANYTHING via ODIN. Odin states that the process completed but the bar on the phone on the download screen never shows up to show that it has accepted a file.
Click to expand...
Click to collapse
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
theramsey3 said:
Did you unchecked F . reset and unchecked auto reboot when you flashed recovery in Odin? After you flash the file you have to pull the battery then replace it and boot to recovery do not allow the phone to boot to OS or you have to flash again as your recovery will only stick if you pull the battery and boot to recovery after flashing it. After you get into it the first time all will be well with the world again you can flash your heart out.
I had twrp ask me for a password once I hit the back arrow key and told it to mount my external SD card then flashed my rom, bootloader, kernel and modem then rebooted no problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This did not work. When I use ODIN all that is happening is that ODIN says it has succeeded but the little progress bar that usually shows up on the phone when you are in download mode never comes up. I did try this method though and it didn't work.
I restarted the phone in ODIN mode then opened ODIN then connected the USB cable then unchecked the two boxes you mentioned then flashed a new non TWRP recovery then waited for ODIN to say successful then the phone never showed the progress bar so I waited 2 mins until I pulled the battery then I restarted phone directly to recovery and still have the password prompt. Even after hitting cancel I cannot interact with recovery because every option I choose just says fail. I cannot even mount external sd card.
What phone do you have? What was the most recent stock ROM on your phone? Maybe you can flash a stock ROM.
There is a copy of the stock Samsung 3e recovery (which we can't use to flash zips with) I'm curious if maybe it can overwrite what you have going on? On the password screen I wasn't hitting cancel I was simply hitting the back arrow key. I will see if I have a copy of the stock recovery, just maybe you can flash it then flash another recovery after that so you can fix your phone.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have Samsung Galaxy S 3 At&T (d2att) SGH-I747 whichever one of those you want. The most recent stock rom on the phone was when I bought it brand new a few months after it came out. I tried installing a stock rom. I tried this using ODIN and it failed. The issue here is that TWRP somehow encrypted the entire file system so NOTHING at all in recovery works. When I use ODIN mode it never shows on my phone that it is accepting a transfer from the computer. When I tried the stock rom via ODIN method it actually failed in ODIN instead of telling me it succeeded and then just not work. It failed at the point when it says Firmware Update Start...aboot.mbn...NAND Write Start!...Complete(Write) operation failed. I am up for any suggestions but I need them to be detailed instructions because I have tried so many things I need to know what exact steps to follow.
I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.
audit13 said:
I believe the aboot file is a bootloader. Did you ever have a stock 4.3 ROM on the phone? If you did, it probably has the stock 4.3 AT&T bootloader which cannot be downgraded without bricking the phone which means you cannot flash a ROM with an older bootloader via Odin.
Click to expand...
Click to collapse
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?
therecker said:
To my knowledge I never had a stock 4.3 ROM on the phone. The only stock ROM to touch this phone was the one that came on it. So be specific what are you actually suggesting in this post that I do?
Click to expand...
Click to collapse
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?
audit13 said:
I am surprised that the aboot file was giving you a problem because the bootloader can be downgraded as long as it is not a 4.3 bootloader.
Do you recall exactly which ROM was on the phone when you got it? Where did you get the stock ROM?
Click to expand...
Click to collapse
It was a CM11 Nightly ROM from the very beginning of February. And before that it was a CM10.2 Stable ROM.
Which stock ROM was on your phone before you loaded a custom ROM?
audit13 said:
Which stock ROM was on your phone before you loaded a custom ROM?
Click to expand...
Click to collapse
I have no idea. It was when I first got the phone in November of 2012.
Sounds like your phone may be running a 4.3 bootloader which means your bootloader is locked and cannot be downgraded. This may explain why you are getting errors when trying to flash Odin. There is no stock AT&T 4.3 ROM that can be flashed via Odin.

[Q] Flashing stock firmware in Odin doesn't change anything

tl:dr I've been trying to flash the stock firmware using Odin but nothing seems to change after I reboot.
SGH-T889
TWRP v2.6.3.1
Devil Kernel
Jedi X Rom (20)
I had this setup for a few months until this morning when my phone had shut off on its own some time while I was sleeping. Turning on the phone would only load up to the Devil Kernel Splash screen. I can get into TWRP but it asks me for a password that I never set. After some searching, I'm assuming that this is because my data partition has possibly been corrupted.
I've tried doing a factory reset in TWRP, it says it's successful but practically there is no change. The console states that it is unable to mount /efs, /cache, and /system.
I tried using 'Format Data', but choosing this options only seems to reset TWRP because I see the TWRP splash screen and then am asked for a password again. From my understanding, shouldn't formatting the data should remove any encryption?
I tried to just reflash the stock firmware to reset everything but every time I finish flashing in Odin, Odin states that everything is fine but there is no change on my phone. I still only see the kernel splash screen on boot.
I've tried doing an Emergency Firmware Recovery through Kies but Kies is unable to do anything after it detects my device version.
kyang321 said:
tl:dr I've been trying to flash the stock firmware using Odin but nothing seems to change after I reboot.
SGH-T889
TWRP v2.6.3.1
Devil Kernel
Jedi X Rom (20)
I had this setup for a few months until this morning when my phone had shut off on its own some time while I was sleeping. Turning on the phone would only load up to the Devil Kernel Splash screen. I can get into TWRP but it asks me for a password that I never set. After some searching, I'm assuming that this is because my data partition has possibly been corrupted.
I've tried doing a factory reset in TWRP, it says it's successful but practically there is no change. The console states that it is unable to mount /efs, /cache, and /system.
I tried using 'Format Data', but choosing this options only seems to reset TWRP because I see the TWRP splash screen and then am asked for a password again. From my understanding, shouldn't formatting the data should remove any encryption?
I tried to just reflash the stock firmware to reset everything but every time I finish flashing in Odin, Odin states that everything is fine but there is no change on my phone. I still only see the kernel splash screen on boot.
I've tried doing an Emergency Firmware Recovery through Kies but Kies is unable to do anything after it detects my device version.
Click to expand...
Click to collapse
Odin the UVALJ1 ROM (i use the Mr. Robinson rooted version). I have been down that road before. I had to flash 2x before it fixed my devices file system.
Then install the current TWRP recovery as 2.6.3.1 is not the best option. From there you should be able to get started again.
Coug76 said:
Odin the UVALJ1 ROM (i use the Mr. Robinson rooted version). I have been down that road before. I had to flash 2x before it fixed my devices file system.
Then install the current TWRP recovery as 2.6.3.1 is not the best option. From there you should be able to get started again.
Click to expand...
Click to collapse
I tracked down the ROM that you're referring to by mrRobinson but after trying another 4 times I'm still getting the same results.
Can you clarify your second line about TWRP recovery? I tried seeing if TWRP was the problem since I could not format data but I cannot flash any new recoveries (stock, CWM, or older versions of TWRP). Does anyone know of any alternate means other than flashing through Odin?
Thanks for the reply though, hearing that other people have had similar problems gives me some hope.
kyang321 said:
I tracked down the ROM that you're referring to by mrRobinson but after trying another 4 times I'm still getting the same results.
Can you clarify your second line about TWRP recovery? I tried seeing if TWRP was the problem since I could not format data but I cannot flash any new recoveries (stock, CWM, or older versions of TWRP). Does anyone know of any alternate means other than flashing through Odin?
Thanks for the reply though, hearing that other people have had similar problems gives me some hope.
Click to expand...
Click to collapse
Try the UVUCMK7 version. That might do it.
Your version of TWRP is old. Try the current version for better results. My first issues with corruption involved 2.6.3.1 though I can't implicate it directly.
Coug76 said:
Try the UVUCMK7 version. That might do it.
Your version of TWRP is old. Try the current version for better results. My first issues with corruption involved 2.6.3.1 though I can't implicate it directly.
Click to expand...
Click to collapse
Thanks again for the response! Flashing recoveries in Odin isn't giving me any results so I'll try getting an external sd card and flashing version 2.7.2.0 from within TWRP.
kyang321 said:
Thanks again for the response! Flashing recoveries in Odin isn't giving me any results so I'll try getting an external sd card and flashing version 2.7.2.0 from within TWRP.
Click to expand...
Click to collapse
Coug76 said:
Try the UVUCMK7 version. That might do it.
Your version of TWRP is old. Try the current version for better results. My first issues with corruption involved 2.6.3.1 though I can't implicate it directly.
Click to expand...
Click to collapse
So I can't seem to change my recovery. Odin will supposedly pass but the version stays the same in my phone. Within TWRP I cannot mount my external sd card so I can't flash from there either.
I tried to see if I could do something with ADB but TWRP won't let me go into ADB side load because it cannot mount /cache.
Any ideas?
Download the ODIN flashable version of TWRP and flash from within ODIN. That will get you at least a new recovery. From there you can restore/etc. I had a similar issue a few weeks back. My partitions got corrupted and doing the standard full ODIN, regardless of which ODINversion/firmware combo I used, resulted in me having a stock recovery with literally nothing else. System, cache, data....nothing would mount. I thought I was permanently soft bricked. Each ODIN flash seemed to go well, but upon booting up, the phone would immediately go into stock recovery with those mounting errors. I used the ATT version of twrp 2.7.2.2...or whatever the latest version was because it had the partition repair option that the TMO version hasn't been updated to yet.
Install the recovery from ODIN.
Boot into recovery.
Click the wipe tab. Then do the advanced wipe...select one partition at a time then click on the 'repair partition' option. I think only cache, system and data can be repaired. The others won't let you repair. Will give an error saying failed or not repairable or something like that.
That's what helped me get out of my dilemma. Fortunately, I had a stock backup on an SD card I was able to restore at that point. If you don't, flash a new ROM, log in, then download Mobile ODIN from the market. You can then flash full firmwares from within the phone itself and get back to 100% stock, minus boot loader. But if you're already on the 4.3 bootloader then there won't be any problems.
I'll check back to see if you had any success. It worked for me, but I offer no guarantees.
Good luck.
carlz28 said:
Download the ODIN flashable version of TWRP and flash from within ODIN. That will get you at least a new recovery. From there you can restore/etc. I had a similar issue a few weeks back. My partitions got corrupted and doing the standard full ODIN, regardless of which ODINversion/firmware combo I used, resulted in me having a stock recovery with literally nothing else. System, cache, data....nothing would mount. I thought I was permanently soft bricked. Each ODIN flash seemed to go well, but upon booting up, the phone would immediately go into stock recovery with those mounting errors. I used the ATT version of twrp 2.7.2.2...or whatever the latest version was because it had the partition repair option that the TMO version hasn't been updated to yet.
Install the recovery from ODIN.
Boot into recovery.
Click the wipe tab. Then do the advanced wipe...select one partition at a time then click on the 'repair partition' option. I think only cache, system and data can be repaired. The others won't let you repair. Will give an error saying failed or not repairable or something like that.
That's what helped me get out of my dilemma. Fortunately, I had a stock backup on an SD card I was able to restore at that point. If you don't, flash a new ROM, log in, then download Mobile ODIN from the market. You can then flash full firmwares from within the phone itself and get back to 100% stock, minus boot loader. But if you're already on the 4.3 bootloader then there won't be any problems.
I'll check back to see if you had any success. It worked for me, but I offer no guarantees.
Good luck.
Click to expand...
Click to collapse
I already have TWRP 2.6.3.1. In trying to see if that version is a problem, I've tried flashing a different version through Odin but it doesn't have any effect (the version will always stay as 2.6.3.1 regardless of what I flash through Odin).
So it's been a week since my issue started and I haven't gotten any further since I started.
I've tried flashing a new pit file to no avail (stuck on get pit file mapping). I've also tried doing a nand rewrite but I get a nondescript error.
As of this point I've given up and am just going to use an old phone lying around until my contract is up. If you've found this thread because you've had similar issues I wish you better luck than I had.

S4 mini i9190 recovery errors odin make pass but no changes

Hello i'm new here , I own a Samsung S4 mini i9190, recently it starts boot-loop, i haven't installed any roms before that, and it is not rooted
Here's what i tried so far :
Enter recovery by pressing the recovery buttons: erase data / wipe cache : it gives me no commands + error
i used Odin 3 for flashing stock firmwares (i tried 4 so far), it says pass, but soon i enter the recovery for wiping cache and data it goes the same error, and the bootloop starts again without any changes
i tried to update recovery, and soon it finished i enter the recovery for wiping data/cache the error appears and the boot-loop persists
Hope you can help , please i'm running out of options
I ask moderators to remove my ex-duplicate thread, I just found this S4 Section, Sorry !
Please help !
I know that there is someone here who can help
PLZ Anyone ! HELP !!!!!!
Are you tried to install TWRP Recovery ?
Install this one and wipe / format all, included data and data media ( int. Sdcard ) than flash Stockrom.
Ah finally Thank you for reply !
bierma32 said:
Are you tried to install TWRP Recovery ?
Install this one and wipe / format all, included data and data media ( int. Sdcard ) than flash Stockrom.
Click to expand...
Click to collapse
I tried to install custom-twrp-3.0.3-0-serrano3gxx-STABLE-signed and many different twrps with different odin versions, but as soon as odin 3 finish, and I press the phone's buttons when it vibrates to enter the recovery, I find myself with the same recovery and the same errors; but still I install the stock rom after that twrp, and odin says Pass when nothing passes ! the bootloop and the recovery still in place, nothing ever change ! and I didn't done anything before all of these errors, no root no custom firmware nothing.
Please ! help !
I think I have the same problem here https://forum.xda-developers.com/galaxy-s4-mini/help/boot-loop-samsung-gt-i9195-errors-t3596676
but still no solution. No matter what recovery I flash I get the same errors (can't mount, can't format...) and the same boot loop.
I can only flash original firmware and nothing else.
I don't know what to do...
Read somewhere that maybe a problem with the memory getting corrupted (hardware fault) but I don't know.
ciozvarda said:
I think I have the same problem here https://forum.xda-developers.com/galaxy-s4-mini/help/boot-loop-samsung-gt-i9195-errors-t3596676
but still no solution. No matter what recovery I flash I get the same errors (can't mount, can't format...) and the same boot loop.
I can only flash original firmware and nothing else.
I don't know what to do...
Read somewhere that maybe a problem with the memory getting corrupted (hardware fault) but I don't know.
Click to expand...
Click to collapse
Hello Yes the recovery says : "no command" when starting it, and when doing erase data/wipe cache it says: "can't mount", "can't format" and finally it says "error" then it reboot in infinite boot-loop
I flashed 5 different firm-wares until now ! without change
Please Help ! tell us at least if it's a hardware failure or not
I don't get "no command" but I get "can't mount", "can't format"...the weird thing is that no matter what recovery i flash (cwm, stock or twrp) after restart I have the previous recovery, in my case CWM 6.05 or something....
Don't know what to do
Please Anyone Help !!
where are you all !
3 Days of waiting + 101 Views and No one Reply !
yes...nobody knows what to do...
I did this https://forum.xda-developers.com/showthread.php?t=1284196 and this https://forum.xda-developers.com/showthread.php?t=1272595 to check my if it's a hardware problem. For me it's not but you can check also.
I downloaded Odin 3.12.3 and from http://www.tsar3000.com/Joomla/ complete firmware recovery (with bootloader, firmware and all the other files).
I flashed with success but it didn't solved my problem. Still stucked in CWM and the phone still reboots.
Thanks man but still nothing..
FU*KK this Forum
i9190 said:
Thanks man but still nothing..
FU*KK this Forum
Click to expand...
Click to collapse
Any solution my friend?
I have the same problem. I think the reason is the dead emmc. I tried to make backup immediately after odin flash and got a error while reading of the system partition. Sometimes I got system mount error. It is a strange case, becouse odin does not notice about some errors while firmware writing. Maybe odin writes the system partition without errors check from emmc? And TWRP restores /system from a backup without problems, but reads the partition not always.

Categories

Resources