Post Reply

Question [Q] Soft brick - Fail flashing Stock ROM at hidden.img Odin

OP ReeX

26th February 2014, 10:09 AM   |  #1  
OP Senior Member
Thanks Meter: 10
 
175 posts
Join Date:Joined: Jul 2011
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?
The Following 2 Users Say Thank You to ReeX For This Useful Post: [ View ]
26th February 2014, 10:36 AM   |  #2  
Member
Thanks Meter: 20
 
97 posts
Join Date:Joined: May 2009
Quote:
Originally Posted by RixNox

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?

You need to flash with this PIT file:
http://forum.xda-developers.com/show...9&postcount=77

Click PIT, select that file and tick Re-Partition in addition to the other stuff.
The Following 9 Users Say Thank You to Wrathlon For This Useful Post: [ View ]
26th February 2014, 10:47 AM   |  #3  
OP Senior Member
Thanks Meter: 10
 
175 posts
Join Date:Joined: Jul 2011
Quote:
Originally Posted by Wrathlon

You need to flash with this PIT file:
http://forum.xda-developers.com/show...9&postcount=77

Click PIT, select that file and tick Re-Partition in addition to the other stuff.

You mean I need to flash again the whole stock ROM + PIT & repartition using the suggested file?
The Following User Says Thank You to ReeX For This Useful Post: [ View ]
26th February 2014, 11:46 AM   |  #4  
Member
Thanks Meter: 20
 
97 posts
Join Date:Joined: May 2009
Quote:
Originally Posted by RixNox

You mean I need to flash again the whole stock ROM + PIT & repartition using the suggested file?

Correct
The Following 4 Users Say Thank You to Wrathlon For This Useful Post: [ View ]
26th February 2014, 03:08 PM   |  #5  
OP Senior Member
Thanks Meter: 10
 
175 posts
Join Date:Joined: Jul 2011
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!!!!!!!!!!!
Last edited by ReeX; 26th February 2014 at 03:18 PM.
The Following 2 Users Say Thank You to ReeX For This Useful Post: [ View ]
26th February 2014, 04:16 PM   |  #6  
ultramag69's Avatar
Senior Member
Flag Waratah
Thanks Meter: 604
 
4,545 posts
Join Date:Joined: Nov 2007
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....
Last edited by ultramag69; 26th February 2014 at 04:46 PM.
26th February 2014, 04:32 PM   |  #7  
OP Senior Member
Thanks Meter: 10
 
175 posts
Join Date:Joined: Jul 2011
Quote:
Originally Posted by ultramag69

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...

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?
26th February 2014, 04:51 PM   |  #8  
ultramag69's Avatar
Senior Member
Flag Waratah
Thanks Meter: 604
 
4,545 posts
Join Date:Joined: Nov 2007
Quote:
Originally Posted by RixNox

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?

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...
26th February 2014, 04:58 PM   |  #9  
OP Senior Member
Thanks Meter: 10
 
175 posts
Join Date:Joined: Jul 2011
Quote:
Originally Posted by ultramag69

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...

So what conditions can occur to brick the phone?
- damaged/wrong firmware?
- power failure while flashing?
- Or?
27th February 2014, 02:03 AM   |  #10  
ultramag69's Avatar
Senior Member
Flag Waratah
Thanks Meter: 604
 
4,545 posts
Join Date:Joined: Nov 2007
Quote:
Originally Posted by RixNox

So what conditions can occur to brick the phone?
- damaged/wrong firmware?
- power failure while flashing?
- Or?

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....

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes