[Q] Soft brick - Fail flashing Stock ROM at hidden.img Odin - Galaxy Note 3 Q&A, Help & Troubleshooting

Guys good morning.
I have rooted and successfully flashed custom recovery and custom firmwares on my Note 3 (9005 Qualcomm LTE), however the last flash (stock ROM 4.4.2 N9005XXUENB4) attempt with Odin (v 3) failed at the end of the flash process ( hidden.img.ext4 -> FAIL! (Size)):
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now the phone won't boot anymore, it is stuck at the following screen (click to enlarge):
I cannot boot in recovery mode. What can I try?

RixNox said:
Guys good morning.
I have rooted and successfully flashed custom recovery and custom firmwares on my Note 3 (9005 Qualcomm LTE), however the last flash (stock ROM 4.4.2 N9005XXUENB4) attempt with Odin (v 3) failed at the end of the flash process ( hidden.img.ext4 -> FAIL! (Size)):
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now the phone won't boot anymore, it is stuck at the following screen (click to enlarge):
I cannot boot in recovery mode. What can I try?
Click to expand...
Click to collapse
You need to flash with this PIT file:
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click PIT, select that file and tick Re-Partition in addition to the other stuff.

Wrathlon said:
You need to flash with this PIT file:
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click PIT, select that file and tick Re-Partition in addition to the other stuff.
Click to expand...
Click to collapse
You mean I need to flash again the whole stock ROM + PIT & repartition using the suggested file?

RixNox said:
You mean I need to flash again the whole stock ROM + PIT & repartition using the suggested file?
Click to expand...
Click to collapse
Correct

Flashed successfully, however the Samsung logo kept glowing endlessly at startup, so I have removed the battery, booted in recovery mode and wiped cache and factory reset and YESSSSSSSSSSSS!!!!!!!!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You rule mate!!! Thanks a lot!!!!!!!!!!!

Thankfully Samsung have a secondary bootloader. The picture you displayed is secondary bootloader, if the flash fails there then you are looking at a brick, not a soft brick but a true paperweight...
You can also forget Kies, since the MJ3 bootloader Kies doesn't recognise the Note 3....

ultramag69 said:
Thankfully Samsung havce 2 bootloader modes, the picture you displayed is secondary bootloader, if the flash fails there then you are looking at a brick, not a soft brick but a true paperweight...
Click to expand...
Click to collapse
I recall once upon a time it was very easy to brick Samsung phones over Odin. Did things change lately? Are later firmwares/phones more foolproof than before as much as HTC are?

RixNox said:
I recall once upon a time it was very easy to brick Samsung phones over Odin. Did things change lately? Are later firmwares/phones more foolproof than before as much as HTC are?
Click to expand...
Click to collapse
Since the Samsung Galaxy S I can safely say it has a secondary bootloader, maybe before but I started on the Samsung galaxy tab7(1st edition) which was an enlarged Galaxy S. If you used Heimdall you'd see it has a file called SBL - secondary bootloader.
It gives you 2 chances to stuff up completely though if you do flash the wrong firmware - for different device - then you overwrite the secondary bootloader and essentially brick your device...

ultramag69 said:
Since the Samsung Galaxy S I can safely say it has a secondary bootloader, maybe before but I started on the Samsung galaxy tab7(1st edition) which was an enlarged Galaxy S. If you used Heimdall you'd see it has a file called SBL - secondary bootloader.
It gives you 2 chances to stuff up completely though if you do flash the wrong firmware - for different device - then you overwrite the secondary bootloader and essentially brick your device...
Click to expand...
Click to collapse
So what conditions can occur to brick the phone?
- damaged/wrong firmware?
- power failure while flashing?
- Or?

RixNox said:
So what conditions can occur to brick the phone?
- damaged/wrong firmware?
- power failure while flashing?
- Or?
Click to expand...
Click to collapse
All the above but if you have the pictured screen on the device you have a final chance to flash correctly... This really is the FINAL chance though, Screw up that flash and you've got a brick that won't turn on or charge...
I have a friends Gtab 7" to prove it. Short of replacing the MB there is no way to get it up and running....

ultramag69 said:
All the above but if you have the pictured screen on the device you have a final chance to flash correctly... This really is the FINAL chance though, Screw up that flash and you've got a brick that won't turn on or charge...
I have a friends Gtab 7" to prove it. Short of replacing the MB there is no way to get it up and running....
Click to expand...
Click to collapse
Very risky.... I wonder how they manage at Samsung OTA/Kies updates... are they any safer? Maybe it's a bad habit to download firmwares from other sites?

It's a standard risk when you flash a rom... This is why the MD5 checks are there, even from the best source you can get a corrupted file...
Also why the devs put the disclaimer that you are flashing your rom and they take no responsibility if it fails...

ultramag69 said:
It's a standard risk when you flash a rom... This is why the MD5 checks are there, even from the best source you can get a corrupted file...
Also why the devs put the disclaimer that you are flashing your rom and they take no responsibility if it fails...
Click to expand...
Click to collapse
The good thing is that an OTA or Kies flashing failure will be covered bi warranty, if any.
Any chance to get the bit 0x1 to 0x0 once "spoiled"? Flashing an original stock rom will not reset to 0...

Still Stuck
RixNox said:
Flashed successfully, however the Samsung logo kept glowing endlessly at startup, so I have removed the battery, booted in recovery mode and wiped cache and factory reset and YESSSSSSSSSSSS!!!!!!!!!!!
You rule mate!!! Thanks a lot!!!!!!!!!!!
Click to expand...
Click to collapse
Many thanks to Wrathlon as I was stuck in the same place! Now I'm stuck at the Samsung logo. I cannot boot into recovery mode to wipe cache and factory reset. Any suggestions?

RixNox said:
The good thing is that an OTA or Kies flashing failure will be covered bi warranty, if any.
Any chance to get the bit 0x1 to 0x0 once "spoiled"? Flashing an original stock rom will not reset to 0...
Click to expand...
Click to collapse
Nope... The bounty is over $3000 USD...

jebanec said:
Many thanks to Wrathlon as I was stuck in the same place! Now I'm stuck at the Samsung logo. I cannot boot into recovery mode to wipe cache and factory reset. Any suggestions?
Click to expand...
Click to collapse
As I wrote I got through removing the battery, booting in recovery mode, performed a wipe data (format) & wipe cache (2 steps in total)

RixNox said:
As I wrote I got through removing the battery, booting in recovery mode, performed a wipe data (format) & wipe cache (2 steps in total)
Click to expand...
Click to collapse
Please excuse my ignorance, but how are you actually booting into recovery? I'm on stock ROM and haven't rooted.

jebanec said:
Please excuse my ignorance, but how are you actually booting into recovery? I'm on stock ROM and haven't rooted.
Click to expand...
Click to collapse
Once you've turned off the phone, keep pressed at the same time (with following sequence)
1) Volume up
2) home
3) power
Keep the buttons pressed at the same time until the phone shows "booting recovery"
This should bring into recovery mode. navigate menus using volume up/down and use power button to confirm/enter. Perform both wipe data factory reset & wipe cache. Once done select reboot

RixNox said:
Once you've turned off the phone, keep pressed at the same time (with following sequence)
1) Volume up
2) home
3) power
Keep the buttons pressed at the same time until the phone shows "booting recovery"
This should bring into recovery mode. navigate menus using volume up/down and use power button to confirm/enter. Perform both wipe data factory reset & wipe cache. Once done select reboot
Click to expand...
Click to collapse
Many thanks. I tried this earlier but for some reason I couldn't get into recovery. I'll try again later to see if I can get it to work.

jebanec said:
Many thanks. I tried this earlier but for some reason I couldn't get into recovery. I'll try again later to see if I can get it to work.
Click to expand...
Click to collapse

Related

Help my gt-i9505 stocked on samsung logo..

i will tell all the information here..i have my samsung gt-i9505 carrier locked to globe telecom here in the philippines..
i tried to factory unlock here http://forum.xda-developers.com/showthread.php?t=2282683 but i have no luck on it..i have change my baseband several time via odin but still i pin request always shows after i reboot..i have android version 4.2.2, stock firmware DXUBMF8.
so i stopped from there..i moved on to try to root my s4,before having this phone i had owned a s4 factory unlock and i have had rooted it but i already forgot how to do it again..so started anew by looking again at forum threads,i have tried omega custom rom but if i goes to recovery mode my screen only shows the following options: reboot system now, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, apply update cache..my question here was,is this the default recovery mode of s4 now?because i can still recall that my last s4's default recovery menu shows with advance option with wipe dalvik cache etc..and my recovery menu now shows no apply update from internal storage..when i tried flashing the custom rom save on my sd card: apply update>omega*something*.zip..it all well done but after rebooting my phone didn't any stuff from that custom rom nor rooted at all..can you help me solving this?
and lastly this is my main problem now,i searched again the thread and went down to this thread http://forum.xda-developers.com/showthread.php?t=2250824 i downloaded the pre-rooted rom XXUBMF8..flashed it with odin PDA..passed and from then my phone was stocked every time i reboot to samsung logo..
i have tried to flash again on a stocked rom. odin>PHONE>(the stock rom)>start>passed then reboot it still stocked to samsung logo..
sorry this was too long to read but i have to tell what all i have been done resulting to this..can someone help me..i will be very thanful for your help..
can anyone help me with this?i have been searching the forum for hours..i have done flashing through odin with stock rom and pit file but it ended up failed..done factory reset with default recovery mode but nothing happens still stucked on boot logo..
still no luck.. it was almost 24 hours since my phone bricked..can someone kindly help me.
voidjov said:
still no luck.. it was almost 24 hours since my phone bricked..can someone kindly help me.
Click to expand...
Click to collapse
The recovery your talking about is cwm not default s4 recovery you'll find that recovery here
http://forum.xda-developers.com/showthread.php?t=2281367
After its installed try wiping data then cache then going into advanced and wiping dalvik cache
S4 Info
did you try from the stock rom to go to recovery many and wipe to factory default again...
Have you tried to install a recovery like Philz and see if you can access the file system of your GS4.
You'll also find more wiping option
Edit: oh great some1 posted before me.
also try to do it from your official rom
TingTingin said:
The recovery your talking about is cwm not default s4 recovery you'll find that recovery here
http://forum.xda-developers.com/showthread.php?t=2281367
After its installed try wiping data then cache then going into advanced and wiping dalvik cache
S4 Info
Click to expand...
Click to collapse
no it was stock recovery what i have used not cwm i think..thats the problem because i am used to using cwm that's where all my problem started because i used stock recovery instead which i am not so familiar.
daibaron said:
did you try from the stock rom to go to recovery many and wipe to factory default again...
Have you tried to install a recovery like Philz and see if you can access the file system of your GS4.
You'll also find more wiping option
Edit: oh great some1 posted before me.
also try to do it from your official rom
Click to expand...
Click to collapse
i have read philz thread and tried flash the .tar file with PDA odin but an error shows:
odin failed once again after flashing a stock rom, the error was:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
no im on a screen shows firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.,
now i cant go even on a stock recovery but i can do download/odin mode..i will not do any further steps from now on,i will wait for your help guys,i don;t want to pay to unbricked my s4,i have to fix it all by myself and your kind help guys..
voidjov said:
no it was stock recovery what i have used not cwm i think..thats the problem because i am used to using cwm that's where all my problem started because i used stock recovery instead which i am not so familiar.
i have read philz thread and tried flash the .tar file with PDA odin but an error shows:
odin failed once again after flashing a stock rom, the error was:
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
no im on a screen shows firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.,
now i cant go even on a stock recovery but i can do download/odin mode..i will not do any further steps from now on,i will wait for your help guys,i don;t want to pay to unbricked my s4,i have to fix it all by myself and your kind help guys..
Click to expand...
Click to collapse
In the Thread you point out... read AGAIN about PIT
http://forum.xda-developers.com/showthread.php?t=2265477
Download the PIT and follow the exact procedure... it's not like flashing a new firmware so read which boxes you check
Try the PIT file with / without the firmware
check also this thread... in case you have a pit related error.
http://forum.xda-developers.com/showthread.php?t=2283919
I'm sure you have all you need to recover your phone.
When you will have recovered your phone, update this thread saying you solved your problem.
check also this thread... in case you have a pit related error.
OH, don't forget to update my thanks counter
Hello,
I saw an answer to this problem in another thread. You have to swipe the phone by starting it with VOLUME UP + HOME + POWER, and then whatever options you have to swipe everything.
Problem SOLVED!!!
hey guys i have solved my greatest problem since i started rooting back on my N7100,my 1st s4 and now my new s4..
thank you for all who helped me,after more than 24hours of reading and waiting for you replies and doing some intervention on my s4,i have recover it..i will post here how i did it for reference for others who might encounter this problem same as mine:
first of all i have noticed this just after successfully revived my phone, you have to WIPE THE DATA/FACTORY REFORMAT via recovery mode before and after doing any firmware update,then i just removed my battery may be a minute and put it back again every time i do flashing..
i used odin version 1.85 not version 3.04..i first chose the pit file and flash it.(when i tried flashing the pit and stock rom together it always ended up to fail)..so i decided to chose to flash the pit file only using odin v1.85(it automatically ticked the "repartition option on this odin version" then it passed..after that as i have said remove battery,wipe data,then i removed again the battery,then put it back and do download/odin mode on my phone,then i flashed stock rom from www.sammoble.com, i searched for globe carrier since my phone was locked on that carrier, then after 2-3minutes(be patient and don't do anything while waiting) my phone backed to life!!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMF8_I9505OLBBMF8_I9505DXUBMF8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> NON-HLOS.bin
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
for those guys who helped me, i have pressed the thanks button for you guys 100x(i hope i can do that)..but truly i am very much thankful for you guys..i do not have to go to service provider technician or any cellphone repair stall just to repair my phone and pay,i have revived it with your help..THANK YOU!!!
i must add i would like to ask what is the best way to root my phone, i have read chainfire autoroot, is the best way to root my phone?as i can remember it is the same way i have rooted my first s4 two months ago because i saw my old folder here on my pc with that application..and best custom rom?
and the best way to factory unlock my phone, the working firmware..
you can post the link so i can read and do it myself..

[HELP]After EFS Bootloop->All attemps verified failed

Good Morning @ll.
I hope one of you can help me. I´m here for years with my HTC. Than i change to iPhone and now I´m back with my Samsung Galaxy Note 3.
What I do:
- became "root", no problem.
- searching for one ROM, no problem.
- Install from the Play Store the "GooManager"
- Now I start in Recovery Mod
- Then I see i must be make an Backup. I Download the "EFS BACKUP" from the AppStore.
Now the problem starts.
After rebooting I have messages from Android with "problems by starting the system" Wait or OK" I can´t Reset in the Settings the Note 3. I do in the Recovery Mode first the Install from the new Rom.
Now I have the problem with the Bootloop. When Android starts, after a few try, I can´t go to Settings->Infos for the system or do a complete Restore. I can´t connect to the Internet because Wifi doesn´t connect and the sim card the have in the right corner an "ban" logo.
Ok, i search here for somethink. I use this:
http://forum.xda-developers.com/showthread.php?t=2507403
I use the Java JDK and the Android SDK for ADB. Install it and use it under System->Path! ADB is working in CMD.
When I go to the CustomRecoveryMod, the PC doesn´t Notifite it. Only when I say "apply update from ADB" I can send with "adb sideload c:\update.zip" a file.
I want to connect it and want to try the "adb shell", but I can´t
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok. Then I see an Zip file for it. Download it, put it on the MicroSD and go to the CustomerRevocerymenu and want to update it.
I use the Odin Updater with a German Rom and a PIT File to debrand the Note 3: http://www.android-hilfe.de/anleitungen-fuer-samsung-galaxy-note-3/509516-anleitung-note-3-debranding-alle-eu-modelle-zu-dbt.html
But everythink I do, I have the error "E: verified failed.
Now, I hope anyone can help me
Thanks.
How can I install TWRP with Terminal? - I have download it. Save it on C:\ Now I go to the Revocer Mode und Press "apply update from ADB" After I say in the cmd Box "adb sideload C:\update.zip" I have the E:signature verification failed"....i hate this!
No one can help me ?
Deathack said:
No one can help me ?
Click to expand...
Click to collapse
You didn't have any custom recovery installed?
Try to boot into download mode and flash TWRP by using Odin.
Make sure the driver has been installed.
vndnguyen said:
You didn't have any custom recovery installed?
Try to boot into download mode and flash TWRP by using Odin.
Make sure the driver has been installed.
Click to expand...
Click to collapse
Thanks for your Answer.
Has you one Download Link for me for the TWRP? Odin I have it.
Thanks.
Deathack said:
Thanks for your Answer.
Has you one Download Link for me for the TWRP? Odin I have it.
Thanks.
Click to expand...
Click to collapse
How can u go without any custom recovery!
U can find the correct TWRP for your device here: http://teamw.in/twrp_view_all_devices
I personally use CWM recovery, but they are both quite good.
Make sure the correct version of TWRP for your device and the correct driver installed.
Thanks for the Link.
For Germany I Download: openrecovery-twrp-2.6.3.8-hltetmo.img.tar
TWRP for Samsung Galaxy Note 3 (T-Mobile) [hltetmo]
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
Whats wrong? Pit File?
Thanks.
EDIT
OK now I have it.
Thanks first....Now I want to use the Terminal and answer.
So now i have CWM based Recovery v6.0.4.4 on the device and install the zip from here:
http://forum.xda-developers.com/showthread.php?t=2507403
Wipe data and reboot! But the same error such before.
Than I use this:
http://forum.xda-developers.com/showthread.php?t=2471421
But here also the same mistake.
What can I do
Thanks for your Help.
Deathack said:
So now i have CWM based Recovery v6.0.4.4 on the device and install the zip from here:
http://forum.xda-developers.com/showthread.php?t=2507403
Wipe data and reboot! But the same error such before.
Than I use this:
http://forum.xda-developers.com/showthread.php?t=2471421
But here also the same mistake.
What can I do
Thanks for your Help.
Click to expand...
Click to collapse
May be there is a problem with the modem?
What region is your Note 3 from? What firmware version are u using?
Go to http://www.sammobile.com/firmwares/?page=1 and search for your stock rom, then flash it via Odin.
Hope that helps.
vndnguyen said:
May be there is a problem with the modem?
What region is your Note 3 from? What firmware version are u using?
Go to http://www.sammobile.com/firmwares/?page=1 and search for your stock rom, then flash it via Odin.
Hope that helps.
Click to expand...
Click to collapse
How can i look witch I have?
I´m from Germany with Vodafone or T-Mobile. I mean its DBT. This is the Last Firmware I Flash:
Now I check from Vodafone...I buy it with a Vodafone payment, but the Note 3 came first, without Branding.
Update with Odin was ok:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005DBTDMJ4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But the Mistake is the same....and now
http://forum.xda-developers.com/showthread.php?t=2567133
It worked for me
Deathack said:
...
But the Mistake is the same....and now
Click to expand...
Click to collapse
follow this instruction step-by-step exactly: http://forum.xda-developers.com/showthread.php?t=2567133
Deathack said:
Good Morning @ll.
I hope one of you can help me. I´m here for years with my HTC. Than i change to iPhone and now I´m back with my Samsung Galaxy Note 3.
What I do:
- became "root", no problem.
- searching for one ROM, no problem.
- Install from the Play Store the "GooManager"
- Now I start in Recovery Mod
- Then I see i must be make an Backup. I Download the "EFS BACKUP" from the AppStore.
Now the problem starts.
After rebooting I have messages from Android with "problems by starting the system" Wait or OK" I can´t Reset in the Settings the Note 3. I do in the Recovery Mode first the Install from the new Rom.
Now I have the problem with the Bootloop. When Android starts, after a few try, I can´t go to Settings->Infos for the system or do a complete Restore. I can´t connect to the Internet because Wifi doesn´t connect and the sim card the have in the right corner an "ban" logo.
Ok, i search here for somethink. I use this:
http://forum.xda-developers.com/showthread.php?t=2507403
I use the Java JDK and the Android SDK for ADB. Install it and use it under System->Path! ADB is working in CMD.
When I go to the CustomRecoveryMod, the PC doesn´t Notifite it. Only when I say "apply update from ADB" I can send with "adb sideload c:\update.zip" a file.
I want to connect it and want to try the "adb shell", but I can´t
Ok. Then I see an Zip file for it. Download it, put it on the MicroSD and go to the CustomerRevocerymenu and want to update it.
I use the Odin Updater with a German Rom and a PIT File to debrand the Note 3: http://www.android-hilfe.de/anleitungen-fuer-samsung-galaxy-note-3/509516-anleitung-note-3-debranding-alle-eu-modelle-zu-dbt.html
But everythink I do, I have the error "E: verified failed.
Now, I hope anyone can help me
Thanks.
How can I install TWRP with Terminal? - I have download it. Save it on C:\ Now I go to the Revocer Mode und Press "apply update from ADB" After I say in the cmd Box "adb sideload C:\update.zip" I have the E:signature verification failed"....i hate this!
Click to expand...
Click to collapse
I had similar issue "System not responding" and boot loop,and I managed to fix it check my thread and follow the steps in post #1
http://forum.xda-developers.com/showthread.php?t=2540822
Hope it helps
Raphy511 said:
http://forum.xda-developers.com/showthread.php?t=2567133
It worked for me
Click to expand...
Click to collapse
By me, no. But thanks for you Help.
Dahdoul said:
I had similar issue "System not responding" and boot loop,and I managed to fix it check my thread and follow the steps in post #1
http://forum.xda-developers.com/showthread.php?t=2540822
Hope it helps
Click to expand...
Click to collapse
I Love you This is the right answer. I complete make all you write and it works. Many Thanks.

S5 Active (G870A) stuck at AT&T logo

I was having issues with the WiFi on my phone so I made backups to the SD card, removed it and did a factory reset on the phone. I'm not sure what it was running at the time, but not lolipop. It now boots to AT&T logo and heats up until I pull the battery out (I've waited upwards of 30 mins). I tried flashing stock and 0F3 roms with odin and I get the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone it says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
I've tried flashing with PIT, tried flashing the boot loader, G870AUCU1ANE4_Full_Odin, and G870A_OC5_Bootloader, to no avail. I also downloaded Samsung Kies 3 and tried to do Firmware upgrade and initialization, which also didn't work. It comes up to Firmeware emergency recovery and asks for a recovery code (which I don't have). I've also tried from recovery mode to factory data reset and also tried to flash the roms from external SD. Is there anything else I can try or something I am missing that can get this working? Any help would be greatly appreciated.
Guess no one can help me. Lame. :[
I'm just trying to find root package so I can downgrade my active and root it. But I'm having trouble finding it. Can you give me any help please?
S5 Active
My little cousin soft bricked (same issue).
My little cousin said he went into SU and did "full unroot" and after the reboot got stuck on the AT&T logo, the kid brought the phone to me in search of help.
I've tried every which way I could think of using odin to try and reflash everything under the sun and cannot find a solution. I can get into download and recovery fine but I cannot flash anything: odin flashes fail except when I when I use odin to flash boot.tar (AP), modem.bin (CP), recovery.tar (BL), it's one of the few times the flash is a pass instead of a fail; recovery won't authenticate any roms.
stumbled on this thread and downloaded an official rom but flashing fails after authentication:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
He said he was on 5.0, stock rooted stock rom - he told me he was sick and tired of the 5.1 update notification and tried to unroot to update and now it's soft-bricked.
here's a screen of all the firmwares and softwares and roms I've tried flashing every which way possible
Smart Switch and Kies3 asks for a recovery code (no idea where to get that); Sammobile only has FW for 4.3, this phone was at 5.0 - my understanding is that it's very difficult to go back from 5.0. I was thinking I could root again and then install custom recovery but can I even do that with no rom installed? any help would be much appreciated!
one more pic for good measure:
Fancy resizing your image?!
*Detection* said:
Fancy resizing your image?!
Click to expand...
Click to collapse
image 1 - error after authentication: http://imgur.com/1mPpRls
image 2 - list of what i've been using http://i.imgur.com/NqZeQlL
image 3 - booting: http://i.imgur.com/ygHqDWn
extra images:
trying to update via kies screen shots: http://imgur.com/GZV20R8
failes kies on the phone: http://imgur.com/07dilCW
I mean your already posted 16k screenshot above
*Detection* said:
I mean your already posted 16k screenshot above
Click to expand...
Click to collapse
sorry, i don't follow
phi303 said:
sorry, i don't follow
Click to expand...
Click to collapse
This post you made with your photos of your phone, the photo is huge
http://forum.xda-developers.com/showpost.php?p=65637433&postcount=4
You need to remove it, resize it, and upload it again
Maybe you can't see if you are browsing from a phone, from a PC, the image is ridiculously big
This is what we see from a PC (EDIT - Seems to be the XDA Classic forum theme that doesn't resize automatically)
*Detection* said:
This post you made with your photos of your phone, the photo is huge
http://forum.xda-developers.com/showpost.php?p=65637433&postcount=4
You need to remove it, resize it, and upload it again
Maybe you can't see if you are browsing from a phone, from a PC, the image is ridiculously big
This is what we see from a PC (EDIT - Seems to be the XDA Classic forum theme that doesn't resize automatically)
Click to expand...
Click to collapse
I haven't changed any themes on xda and the images are automatically resized to width on the desktop:
SS: https://imgur.com/NvCyid7
I know, I mean I am using the classic theme, and it doesn't resize it
Don't worry
If you want to check, switch the theme down at the bottom left of the forum to XDA Classic
Then go look at your screenshot
Muunia said:
I was having issues with the WiFi on my phone so I made backups to the SD card, removed it and did a factory reset on the phone. I'm not sure what it was running at the time, but not lolipop. It now boots to AT&T logo and heats up until I pull the battery out (I've waited upwards of 30 mins). I tried flashing stock and 0F3 roms with odin and I get the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone it says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
I've tried flashing with PIT, tried flashing the boot loader, G870AUCU1ANE4_Full_Odin, and G870A_OC5_Bootloader, to no avail. I also downloaded Samsung Kies 3 and tried to do Firmware upgrade and initialization, which also didn't work. It comes up to Firmeware emergency recovery and asks for a recovery code (which I don't have). I've also tried from recovery mode to factory data reset and also tried to flash the roms from external SD. Is there anything else I can try or something I am missing that can get this working? Any help would be greatly appreciated.
Click to expand...
Click to collapse
I have the same problem, I want to flash stock firmware but it was always failed like what poested. I dont know how to fix it until now. What i did was flash TWRP then flash custom ROM but i want to flash stock firm. Did you manage to fix this problem?
The assasin said:
I have the same problem, I want to flash stock firmware but it was always failed like what poested. I dont know how to fix it until now. What i did was flash TWRP then flash custom ROM but i want to flash stock firm. Did you manage to fix this problem?
Click to expand...
Click to collapse
Nope, never could find any more information on it. AT&T just told me to file an insurance claim that it was lost, and I got an s6 active for 99$ instead of a new s6 active.

I9505 Softbricked, Cannot be flashed with odin :(

Hello,
I have problems with my s4 I9505 while I try to unbrick it
After a ota update from android 4.4.2 to 5.X (Orginal Firmware from Samsung) it cannot boot and enter Recovery and now I try to flash Firmware with odin but my phone turning screen off during odin says System.img.ext4 but the phone seens still working because it is showing in odin as connected but it doesn't continue flashing
I also see a new stuff in Download Mode Like Write Protection Enabled and eMMC Burst Mode Enabled
MichalPlays said:
Hello,
I have problems with my s4 I9505 while I try to unbrick it
After a ota update from android 4.4.2 to 5.X (Orginal Firmware from Samsung) it cannot boot and enter Recovery and now I try to flash Firmware with odin but my phone turning screen off during odin says System.img.ext4 but the phone seens still working because it is showing in odin as connected but it doesn't continue flashing
I also see a new stuff in Download Mode Like Write Protection Enabled and eMMC Burst Mode Enabled
Click to expand...
Click to collapse
Which firmware were you trying to flash through Odin? Is it KK or Lollipop?
Post the Odin log here.
Mandark52 said:
Which firmware were you trying to flash through Odin? Is it KK or Lollipop?
Click to expand...
Click to collapse
I tryed to flash Lollipop 5.0.1 (Orginal Firmware) and before brick I had Cyanogenmod Lollipop with Old Samsung Lollipop Modem and all worked fine until this **** ota update :/
Lennyz1988 said:
Post the Odin log here.
Click to expand...
Click to collapse
Ok, I will post it at 4:30p.m. (German Time Zone)
Lennyz1988 said:
Post the Odin log here.
Click to expand...
Click to collapse
ODIN LOG:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUHOJ2_I9505OXAHOJ2_I9505XXUHOJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
(Device Freeze,after 2h battery empty)
<ID:0/007> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
MichalPlays said:
ODIN LOG:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUHOJ2_I9505OXAHOJ2_I9505XXUHOJ2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
(Device Freeze,after 2h battery empty)
<ID:0/007> Removed!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Use a different usb port/different usb cable. That will solve it.
Lennyz1988 said:
Use a different usb port/different usb cable. That will solve it.
Click to expand...
Click to collapse
Nope I tryed now this already :/
I tested also the battery with my other s4 and it worked fine.
There is a pict. that showing where I put the firmware file and what option I select
hmm, what is this CSC and Phone slots at odin?
sry 4 my bad english
Maybe try a newer version of Odin?
MichalPlays said:
Nope I tryed now this already :/
I tested also the battery with my other s4 and it worked fine.
There is a pict. that showing where I put the firmware file and what option I select
hmm, what is this CSC and Phone slots at odin?
sry 4 my bad english
Click to expand...
Click to collapse
Then try a different pc. the log doesn't show anything strange that would let me doubt my suggestion.
Lennyz1988 said:
Then try a different pc. the log doesn't show anything strange that would let me doubt my suggestion.
Click to expand...
Click to collapse
At all my pc's one with win7 and another with windows xp - sp3 it are the same, maybe I need to flash something other and them the firmware :/
@MichalPlays Try using Odin 307.
downgrade Samsung s4 [GT-I9505] from Lolipop 5.0.1 to kitkat 4.4.2
Please read the entire post and don’t skip any steps, note that we cannot be blamed in case something goes wrong and you brick the phone.
1)-Make sure that your phone version is GT-I9505 (if you don't know how to check ; remove your battery then you will find)
2)-Download[/B] " SAMSUNG USB Driver for Mobile Phones" and setup, if you dont have it already
-Download Odin3-v3.09
-Download "PDA" ; "[email protected]" [1.52 GB]
-Download "BL" ; "Bootloader_GNK2.tar" [2.12 MB]
-Download "CP"; "Modem_GNK2_FULL.tar" [61.46 MB]
3)- your phone must be Charged 70% or more, and Rooted, if you have Samsung Kies; reboot your pc then end Kies from CPU (Ctrl + Alt + Supp).
4)-extract Odin and Start a program as an administrator then put only the PDA file which you've already downloaded and extracted before "([email protected])"
-Disable « Auto Reboot » and « Re-Partition »
-Enable « F. Reset Time » only
-Reboot your phone on Download Mode ( Power off the Phone completely, Press and hold Volume Down, Home and Power buttons, all at the same time.
Release the buttons only when the ‘Warning!!’ message appears.
Next, press Volume Up button to confirm that you wish to enter Download Mode.
Your device will now show a green Android with the ‘Downloading… Do not turn off target’ text listed under it.).
-Connect your device with your PC and check "Added Message" and « ID:COM » in Odin
-Start
5)-Once you have "PASS" Plug out your Phone, and Reboot again in "Download Mode",
-Reset Odin
-Enable « Auto Reboot »and « F. Reset Time » only
-Put « Bootloader_GNK2.tar » on "BL"
-Put « Modem_GNK2_FULL.tar » on "CP
-Plug in your Phone and check "Added Message" and « ID:COM » if it doesn't work; restart Odin.
-Start to Downgrade
6)-Once the Downgrade done, plug out your phone and Hard Reset ;
(Power off your phone completely. Boot it in Recovery Mode. Select the ‘wipe data/ factory reset’ option. Confirm process by selecting the ‘Yes — delete all user data’ option. Press Power to confirm process. Reboot the phone when the Hard Reset/ Factory Reset is completed).
7)-Enjoy...
MichalPlays said:
At all my pc's one with win7 and another with windows xp - sp3 it are the same, maybe I need to flash something other and them the firmware :/
Click to expand...
Click to collapse
Ok then we can probably rule that out.
Are you using the original cable? Did you try different cables?
Lennyz1988 said:
Ok then we can probably rule that out.
Are you using the original cable? Did you try different cables?
Click to expand...
Click to collapse
I use always Original Cable and tested with cable from s4, s3, s3neo and htc one x plus and all doesn't work I tryed now the tutorial from this one guy this all was the same :/
btw. can I flash and enter a costum recovery without android on it ??
MichalPlays said:
I use always Original Cable and tested with cable from s4, s3, s3neo and htc one x plus and all doesn't work I tryed now the tutorial from this one guy this all was the same :/
btw. can I flash and enter a costum recovery without android on it ??
Click to expand...
Click to collapse
Yeah you can do that. Flash the latest TWRP. Uncheck auto-reboot before flashing with Odin.
Lennyz1988 said:
Yeah you can do that. Flash the latest TWRP. Uncheck auto-reboot before flashing with Odin.
Click to expand...
Click to collapse
oh, ok I will try this becasue I have this cyanogenmod .rar file on sd card and have also there an nandroid backup

Soft Bricked S4

*****************Thread can be closed as issue has been resolved*****************
I think I have soft bricked my phone.
I tried this tutorial and everything went according to the instructions except that the wifi couldn't be turned on.
So I opened a thread asking for help regarding my wifi, I was advised to flash a custom ROM (Android 5.0.1 Lollipop SDK 21) thru TWRP but I must have done something wrong because the phone was stuck in Android System Recovery.
Then I was advised to flash the original firmware thru Odin (Android 4.2.2) and that's where I think the brick happened.
The phone can go into download mode but there is a gray line that says "Write protection: Enable" and everything I try to flash thru Odin gives the same fail error:
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Urgent help is much appreciated as I have no other phone and I have been incommunicated for a week+ now
UPDATE:
I just tried to go into Android System Recovery just now it worked! I swear I wasn't able to. It says on top:
LRX22C.I337UCSGOK3 (I was on NB1, where could have this come from?)
And has a couple extra options I had never seen before (last 3 or 4 from the list:
reboot system now (tried it and gets stuck on Samsung logo)
apply update from ADB
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
Enable cp logging
Disable cp logging
At the end of the recovery screen there are 2 lines in red:
failed to mount "/system" (Invalid Argument)
E: failed to mount /system (Invalid Argument)
What is the model # in download mode?
audit13 said:
What is the model # in download mode?
Click to expand...
Click to collapse
It says:
Product Name: SGH-I337
PS: Sorry I didn't specify because I thought this forum section was only that model.
The bootloader on the sgh-i337 is locked while the bootloader on the sgh-i337m is unlocked. which means you cannot flash TWRP or CWM to the sgh-i337.
Look here: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814 and note the following comments from that thread.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+).​
audit13 said:
The bootloader on the sgh-i337 is locked while the bootloader on the sgh-i337m is unlocked. which means you cannot flash TWRP or CWM to the sgh-i337.
Look here: https://forum.xda-developers.com/ga...-to-update-to-i337oc3-5-0-1-keeproot-t3075814 and note the following comments from that thread.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. If you are not already rooted (or to unbrick) you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+).​
Click to expand...
Click to collapse
Mine is not the "M" version.
What am I supposed to get from those notes? Are you suggesting I follow the steps in that thread?
I'm not too technical, but I can follow steps.
If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)
What bootloader are you on? Only the MDL bootloader can use the 4.2.2 Odin firmware.
audit13 said:
If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)
Click to expand...
Click to collapse
I am on NB1, will try this tru Odin and will report back.
StoneyJSG said:
What bootloader are you on? Only the MDL bootloader can use the 4.2.2 Odin firmware.
Click to expand...
Click to collapse
Is the bootloader that one at the top of the Android System Recovery? If so, mine says:
LRX22C.I337UCSGOK3
audit13 said:
If you are to unbrick you must first flash the I337UCUFNB1_Rootable_Full_Odin.tar (use Odin's PDA slot (AP in Odin v3.09+)
Click to expand...
Click to collapse
It seems that I already had tried this because when I extracted the file it had to be replaced on my Desktop. Anyways I tried it again and it said the same thing:
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE:
Somehow I can go into recovery now and it says LRX22C.I337UCSGOK3 and unable to mount /system. Please refer to first post for complete info about this.
Publish the Odin log of possible.
You tried using different usb cables and usb ports?
audit13 said:
Publish the Odin log of possible.
You tried using different usb cables and usb ports?
Click to expand...
Click to collapse
I have successfully flashed stuff using this cable. I do swicth usb ports every time I get a fail just to make sure.
I really think the fail is due to the "Write Protection: Enabled" legend that appears on my screen as it wasn't there before and I was able to flash without mayor issues.
I'll try using a new cable now but I don't think I'll get a different result.
Will post the entire logs when I do.
Holy_Purple said:
I have successfully flashed stuff using this cable. I do swicth usb ports every time I get a fail just to make sure.
I really think the fail is due to the "Write Protection: Enabled" legend that appears on my screen as it wasn't there before and I was able to flash without mayor issues.
I'll try using a new cable now but I don't think I'll get a different result.
Will post the entire logs when I do.
Click to expand...
Click to collapse
OMG! I tried a new cable and it went thru!!! I cannot believe my eyes! and the wifi is working!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUFNB1_TWRootable_Full_Odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> non-hlos.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
You were on the OK3 bootloader. Now you're on the NB1 bootloader. You're stuck with using safe strap recovery and can only boot custom ROMs based on touchwiz as your bootloader is locked and can no longer be exploited with loki doki.
StoneyJSG said:
You were on the OK3 bootloader. Now you're on the NB1 bootloader. You're stuck with using safe strap recovery and can only boot custom ROMs based on touchwiz as your bootloader is locked and can no longer be exploited with loki doki.
Click to expand...
Click to collapse
Thanks for the info! I won't be messing with my phone any more, haha :victory:
Glad you got it fixed
I always have a few Samsung cables on hand for flashing.

Categories

Resources