Related
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..
Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
lethcore said:
Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
Click to expand...
Click to collapse
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
donalgodon said:
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
Click to expand...
Click to collapse
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
The good news is that Download mode is still working. AS long as that's the case, you can get it back. Just keep trying. Switch PCs, switch cables, switch ports, re download a different stock ROM, etc. do whatever it takes to try every variable you can think of.
Eventually, you'll find what's causing it and the ROM will flash successfully. When that happens, get immediately into recovery and wipe data.
(Remove the battery after it flashes, but it back in and hold vol-up+home+power.)
After the data wipe....
Reboot.
Like I said, Download mode means you can find a way to flash, but working with Odin to resolve these issues can sometimes be a PITA. I've had the same thing myself before. Just don't give up. Try to stay calm, and work your way through it. You'll get it eventually.
Edit: Just noticed that you flashed a CHINA firmware. (Why? ) You may be facing this issue because (I think) they use a different pit. There's a thread devoted to resurrecting the device with pit. Maybe check it out.
lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
dont flash China or Hong kong firmwares.
please post odin progression
samersh72 said:
dont flash China or Hong kong firmwares.
please post odin progression
Click to expand...
Click to collapse
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
lethcore said:
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
Click to expand...
Click to collapse
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
lethcore said:
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
recovery is flashed, try to boot into it and make the wipe then re-flash stock, re-wipe.
if not, flash a custom recovery, format system, cache, re-flash stock, re-wipe
@donalgodon
Why ? well i got the I9500 in hong kong (im actually based in china now) (not Chinese though) thought i'll see some nice changes? but seems i fK'ed the phone.... pit? i haven't a clue man pit number? think i've KILLED HER... lol (i never knew the dangers of Chinese firmware) - wont be going down that route again.
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
lethcore said:
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
Click to expand...
Click to collapse
flash custom recovery,
if not see my signature for flashing right pit with the firmware
samersh72 said:
flash custom recovery,
if not see my signature for flashing right pit with the firmware
Click to expand...
Click to collapse
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
lethcore said:
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
Click to expand...
Click to collapse
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
samersh72 said:
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
Click to expand...
Click to collapse
Well you be happy to know
installed the previous firmware and that pit file for I9500 from your sig and everything seems well... booted correctly nothing lost all seems good to early to tell but will keep you informed !
THANK YOU!!!
I tried to install the 4.4.2 N9005XXUENA6_N9005OXXENA5_N9005XXUENA2 update on my Note 3 via odin 3.09.
Got an ext4 update failed error.
After this, the phone's bricked and is stuck on the Kies Recovery Screen. I tried to go into recovery mode in Kies, but it says this model does not have initialization.
I tried installing a 4.3 N9005XXUDMK3_N9005TNLDMK1_N9005XXUDMK2, but again failed. Download mode shows SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
Can someone please guide me to unbrick my phone?
I don't know what ROM I was on initially. It was the stock ROM that came with the phone.
I dont have CWM and TWRM installed.
This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine.
MrAndroid12 said:
This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine.
Click to expand...
Click to collapse
Thank you for that advice. How do I add a .pit file, and would you happen to have a link where I can download it from?
rinuvimal said:
Thank you for that advice. How do I add a .pit file, and would you happen to have a link where I can download it from?
Click to expand...
Click to collapse
search better mate http://forum.xda-developers.com/showthread.php?t=2550823
tasked28m said:
search better mate http://forum.xda-developers.com/showthread.php?t=2550823
Click to expand...
Click to collapse
I've tried all the .pit files in that thread, bro. None work. Cannot generate own pit as in phone is in recovery mode.
rinuvimal said:
I've tried all the .pit files in that thread, bro. None work. Cannot generate own pit as in phone is in recovery mode.
Click to expand...
Click to collapse
i know cfautoroot has the correct pit file in , try rooting your phone with cfautoroot.
MrAndroid12 said:
This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine.
Click to expand...
Click to collapse
I tried a variety of N9005 .pits and each time, it shows PIT FAIL: TOTAL SECTORS (30777344) :crying:
(Read OP) . Try flashing the polish firmware again with odin v1.85 and try using different usb ports. Close most of your running applications such as firefox skype etc that can interrupt the process and flash official firmware.
tasked28m said:
(Read OP) . Try flashing the polish firmware again with odin v1.85 and try using different usb ports. Close most of your running applications such as firefox skype etc that can interrupt the process and flash official firmware.
Click to expand...
Click to collapse
Whenever I try the 4.4.2 polish, it fails at system.img.ext4. When I try 4.3, it fails at aboot.
Here's the Odin log for 4.4.2 polish:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
bootloop note 3
After installig android 4.4.2, i tried to root with cf-root, now it is in a loop.
I cannot come into in recovery mode.
The phone starts with: -recovery booting,-recovery is not seandroid enforcing,- set warrant bit recovery
when i keep the battery out and then put it in, it says again -recovery booting,-recovery is not seandroid etc.
Who can help me????
rinuvimal said:
Whenever I try the 4.4.2 polish, it fails at system.img.ext4. When I try 4.3, it fails at aboot.
Here's the Odin log for 4.4.2 polish:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You won't be able to downgrade back to 4.3 - Use the PDA slot on ODIN and try flashing again.
poedy said:
After installig android 4.4.2, i tried to root with cf-root, now it is in a loop.
I cannot come into in recovery mode.
The phone starts with: -recovery booting,-recovery is not seandroid enforcing,- set warrant bit recovery
when i keep the battery out and then put it in, it says again -recovery booting,-recovery is not seandroid etc.
Who can help me????
Click to expand...
Click to collapse
I answered in your other thread about this...
rinuvimal said:
I tried to install the 4.4.2 N9005XXUENA6_N9005OXXENA5_N9005XXUENA2 update on my Note 3 via odin 3.09.
Got an ext4 update failed error.
After this, the phone's bricked and is stuck on the Kies Recovery Screen. I tried to go into recovery mode in Kies, but it says this model does not have initialization.
I tried installing a 4.3 N9005XXUDMK3_N9005TNLDMK1_N9005XXUDMK2, but again failed. Download mode shows SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
Can someone please guide me to unbrick my phone?
I don't know what ROM I was on initially. It was the stock ROM that came with the phone.
I dont have CWM and TWRM installed.
Click to expand...
Click to collapse
try to downlaod and flash the 4.4.2 tar again, you cant downgrade to 4.3 as your bootlaoder got upgraded
Edit- darn am i too slow or are you too fast today @radicalisto? second time...LOL :good:
Khizar said:
try to downlaod and flash the 4.4.2 tar again, you cant downgrade to 4.3 as your bootlaoder got upgraded
Edit- darn am i too slow or are you too fast today @radicalisto? second time...LOL :good:
Click to expand...
Click to collapse
15 hour sleep man, seems to have me buzzing around lol :highfive:
Solution
I also have Hong Kong N9005 32GB with N9005XXUBMI5 PDA, tried to flash 4.4.2 with Odin and stuck at "invalid ext4 image", was't able to flash anything after it.
But after 16 hours I finally found a solution:
1. Get leaked Polish ROM (that one with 4 files, do not use the official - it has one file rom)
2. Extract archive
3. Extract "CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar" and get your pitfile - HLTE_EUR_OPEN.pit
4. Flash your phone with this pitfile and other 4 files from archive (I used Odin 3.09) with repartitioning enabled.
After this procedure I have fully working android 4.4 :victory:
m1ndst0rm said:
I also have Hong Kong N9005 32GB with N9005XXUBMI5 PDA, tried to flash 4.4.2 with Odin and stuck at "invalid ext4 image", was't able to flash anything after it.
But after 16 hours I finally found a solution:
1. Get leaked Polish ROM (that one with 4 files, do not use the official - it has one file rom)
2. Extract archive
3. Extract "CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar" and get your pitfile - HLTE_EUR_OPEN.pit
4. Flash your phone with this pitfile and other 4 files from archive (I used Odin 3.09) with repartitioning enabled.
After this procedure I have fully working android 4.4 :victory:
Click to expand...
Click to collapse
Have you tried rooting it with Chainfire's CF-Auto Root yet?
m1ndst0rm said:
I also have Hong Kong N9005 32GB with N9005XXUBMI5 PDA, tried to flash 4.4.2 with Odin and stuck at "invalid ext4 image", was't able to flash anything after it.
But after 16 hours I finally found a solution:
1. Get leaked Polish ROM (that one with 4 files, do not use the official - it has one file rom)
2. Extract archive
3. Extract "CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar" and get your pitfile - HLTE_EUR_OPEN.pit
4. Flash your phone with this pitfile and other 4 files from archive (I used Odin 3.09) with repartitioning enabled.
After this procedure I have fully working android 4.4 :victory:
Click to expand...
Click to collapse
can you show the download link for the leaked rom with 4 files?
vndnguyen said:
can you show the download link for the leaked rom with 4 files?
Click to expand...
Click to collapse
I have no permission to post links yet, but try googling for N3KitKat.rar.torrent
Leaked download link is in my sig (not this cause I am on xda app l check my other posts)
Sent from my SM-N9005 using XDA Premium 4 mobile app
ManUtdRul3 said:
Have you tried rooting it with Chainfire's CF-Auto Root yet?
Click to expand...
Click to collapse
Just tried latest one, ended up in bootloop with "KERNEL IS NOT SEANDROID ENFORCING"...
Now flashing original ROM again.
m1ndst0rm said:
Just tried latest one, ended up in bootloop with "KERNEL IS NOT SEANDROID ENFORCING"...
Now flashing original ROM again.
Click to expand...
Click to collapse
Seems to be a common problem. Hopefully an update to it will fix it.
Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?
gokhan04uk said:
Hi All
I have the Hong Kong Note 4 N910U
PDA N910UXXU1AOC3
CSC N910UZZH1AOC3
As you may know, lollipop 5 is not out yet for this particular version. As I am experiencing some issues with the phone, I thought I'll just do a factory reset. However I've read somewhere here that I can use the other stock roms of the N910U eg; Taiwan 5.01 or New Zealand 5.0.1. So I thought I might aswell update to lollipop and then do a fresh factory reset.
So I downloaded this Taiwan one
PDA N910UXXU1BOD4
CSC N910UZZT1BOD4
However it keeps failing in ODIN.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910UXXU1BOD4_N910UZZT1BOD4_N910UXXU1BOD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img
<ID:0/006> cache.img
<ID:0/006> hidden.img
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I did use all different versions of ODIN, tried on different usb ports, re-installed installed new drivers, used a different computer etc.. Still same outcome. I am using the original usb cable that came with the phone. What am I missing, any help will be much appreciated ?
Click to expand...
Click to collapse
I have identical problem. Same device, same stock firmware. Trying to update to BOD4
Dancing around:
I've installed last TWRP (https://twrp.me/devices/samsunggalaxynote4exynos.html) from Odin after multiple failed attempts with N910UXXU1BOD4
Device booted normally (long boot with "updating applications")
TA-DA!
it booted to 5.0.1
It's creepy magic, but it works.
BTW, sammobile has newer version (N910UXXU1BOE3_N910UZZT1BOE3_BRI.zip)
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"
gokhan04uk said:
Thanks for that mate. Will try it when i get home. Im not familiar with using odin or this TWRP thing. So do i download the TWRP tar file and load it to odin, then what? Can you give me the full nstructions please. Im quite confused especially the last bit under odin install method ,
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery"
Click to expand...
Click to collapse
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox
I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
stari4ek said:
I've repeated same procedure with newer rom: N910UXXU1BOE3/N910UZZT1BOE3:
Attempt to flash via Odin new firmware
Get error
Unplug device. Remove battery. Insert battery back. Boot to download mode again
Flash TWRP via odin
Successfully reboot to new system
Click to expand...
Click to collapse
stari4ek said:
My device booted to TWRP by itself without any problem, so no need to force it with keys or fastboot.
I forgot to mention, since TWRP is custom recovery You will trigger "knox void warranty 0x1", so if it's important to you - you need another way.
Does Your device boot to system after error with N910UXXU1BOD4? Cause my didn't.
Probably flashing original recovery will fix it also and will not trigger knox
Click to expand...
Click to collapse
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.
a_ballads said:
I just want to clarify this just to be clear.
So after it fails you turn off, pull battery, turn on to download mode and install TWRP and then it will boot into TWRP and you just reboot and the BOE3 Taiwan firmware will just boot up? Sounds like magic, like you mentioned before.
Click to expand...
Click to collapse
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
gokhan04uk said:
Well after the error that odin gave me, i managed to recover my device using kies so my phones back on its original firmware all working. So, what is the method you used to install the latest taiwan update? Did you just go through the normal odin method or ? I dont really want to root the device, i just want to install the original stock 5.1 firmware.
Click to expand...
Click to collapse
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk
stari4ek said:
yes. after error.
i "reboot" device to download mode (disconnect from usb, take out battery, put it back. volume-down+home+power).
in download mode I install TWRP.
if "auto reboot" is ticked in odin - it will reboot to new recovery (twrp) automatically. it (twrp) will perform some patching and will reboot device automatically. device will boot to system.
first boot can take a while.
---------- Post added at 10:12 AM ---------- Previous post was at 10:05 AM ----------
it.s 5.0.1 btw. There is no 5.1 yet
Yes I went through normal odin with last taiwan firmware.
it did fail with error above.
reboot to download mode.
I flashed TWRP on top of it.
when twrp is installed - system boots to new 5.0.1
KNOX is triggered!
some hours device is alive and fully working. no issues... yet =)
As usual. No responsibility here, Do it on Your own risk
Click to expand...
Click to collapse
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..
gokhan04uk said:
I see. Well there should be a way of getting this installed without having to root/trigger the knox. I dont see how others are doing it through odin and our ones are failing. There should be a reason. Or it might be that this specific taiwan one fails for everyone? I did see some who flashed the new zealand one without issues..
Click to expand...
Click to collapse
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)
stari4ek said:
probably it doesn't like that we're flashing different CSC.
the last image flashed is hidden.img, which if I'm not mistaken has CSC stuff
I'd expect that flashing this TAR without hidden.img or flashing original recovery instead of TWRP - will keep KNOX 0. But this homework is for someone else =)
Click to expand...
Click to collapse
Ok, Well if i do it the way you done it, will i get future ota updates or not ? i dont mind voiding warranty because the device is from hong kong, even if something goes wrong it will be a headache to send it back there and wait for it to come back. If I can get future updates wirelessly then i dont mind rooting it.
Nope. It rejects to check OTA. Manual update via Odin is still an option.
Probably, if flash original recovery and reset device, so it switches to new CSC - OTA will work. Probably.
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
This sounds interesting, can you please expand on the inductions as I am I little confused about when to flash hidden.img.
Thanks[emoji1]
Salim.Keady said:
@gokhan04uk
Flashing a custom recovery does solve the problem... but when i tried the method below i noticied changes
BUT DO IT AT YOUR OWN RISK
it worked for me
Rename tar.md5 to tar
Extract tar using 7zip
Extarct hidden.img
Flash it via Odin as PDA/AP
It was succesfull for me
P.S: Knox is not triggered
Click to expand...
Click to collapse
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else
gokhan04uk said:
Can you give us full instructions please. I downloaded N910UXXU1BOE3_N910UZZT1BOE3_N910UXXU1BOE3_HOME
After I rename the md5 file to tar and extract. What do I do with the hidden.img file ?
Do I need to use only odin? or anything else
Click to expand...
Click to collapse
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user
Salim.Keady said:
Flash firmware
Hidden fails
Extract hidden.img and flash it as pda
Simple as that
And remeber am not responsible even if it worked for me and another user
Click to expand...
Click to collapse
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?
gokhan04uk said:
So I have to go through the normal odin process. Once it fails. I have to flash hidden.img through odin?
Click to expand...
Click to collapse
Yes
How do you even flash the hidden.img,ext4 files through odin?
Hey I am trying to uninstall cyanogen mod on my galaxy s4 so that I can return it to stock to sell it. I was following this guide techbeasts.com/how-to-unroot-samsung-galaxy-s4-all-versions/
I downloaded my firmware off of samsungs site the newest firmware available for my phone. I tried to restore it and it gave me an error about xmitdata fail so I had to unplug the phone and try again. Now if I try and boot up the phone it says firmware upgrade encountered an issue. Please select recovery mode in kies and try again. If I try and reflash it in odin I get this far now and it freezes...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOH1_I337MOYAGOH1_I337MVLUGOH1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Firmware update start..
<ID:0/004> aboot.mbn
any ideas please? and thankyou!
Your phone is the i337 or i337m?
The firmware you are flashing looks like it is for the i337m.
audit13 said:
Your phone is the i337 or i337m?
The firmware you are flashing looks like it is for the i337m.
Click to expand...
Click to collapse
Sorry should have put that behind my battery it says sgh-i337m
Are you using the original Samsung USB cable?
Odin errors when trying to flash aboot.mbn file? If it does, the firmware may not be for the phone.
Boot into download to confirm model number.
audit13 said:
Are you using the original Samsung USB cable?
Odin errors when trying to flash aboot.mbn file? If it does, the firmware may not be for the phone.
Boot into download to confirm model number.
Click to expand...
Click to collapse
yes original cable, it doesn't error it just freezes there. in Download mode it says this:
Odin Mode
Product Name: SGH-I337M
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-Config-Lsb: 0x30
Secure Download: Enable
Write Protection: Enable
eMMC Burst Mode enabled
I downloaded my firmware from sammobile.com and looked up the SGH-I337M and chose the one for Fido Canada as that is what I have
Maybe try different USB ports or USB cables?
Bell, Telus, and Rogers use the same forwards with slightly different customized applications.
audit13 said:
Maybe try different USB ports or USB cables?
Bell, Telus, and Rogers use the same forwards with slightly different customized applications.
Click to expand...
Click to collapse
I have tried different port and I don't have another cable, and does that mean I could download like a bell firmware and try that instead?
or is there a way that reinstalling cyanogenmod would fix it and somehow wipe my personal info? that's all I really need to do
Yes, you can try bell or Telus firmware but that should not make a difference.
Odin is freezing when trying to flash aboot.mbn?
audit13 said:
Yes, you can try bell or Telus firmware but that should not make a difference.
Odin is freezing when trying to flash aboot.mbn?
Click to expand...
Click to collapse
Ok downloading now to try, but ya its freezes the progress bar on phone doesn't move and the Odin app just sits there at aboot.mbn
I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.
audit13 said:
I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.
Click to expand...
Click to collapse
ya I downloaded latest firmware.... and phone encrypted I don't no....
Well, if Odin fails again, I suggest flashing twrp via Odin, boot into twrp, factory wipe, and flash a custom ROM to ensure the phone still functions.
audit13 said:
I assume you are trying to flash the latest firmware and the phone is not encrypted.
The aboot.mbn file is the bootloader.
Click to expand...
Click to collapse
audit13 said:
Well, if Odin fails again, I suggest flashing twrp via Odin, boot into twrp, factory wipe, and flash a custom ROM to ensure the phone still functions.
Click to expand...
Click to collapse
I will try this now and post back...
I don't think this is good stuck with this....
<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> SingleDownload.
<ID:0/005> recovery.img
Weird, before it got stuck at aboot.mbn or is the latest error when trying to flash twrp?
You're only unzipping the file once from sammobile.com and flashing the tar.md5 file in the pda box?
audit13 said:
Weird, before it got stuck at aboot.mbn or is the latest error when trying to flash twrp?
You're only unzipping the file once from sammobile.com and flashing the tar.md5 file in the pda box?
Click to expand...
Click to collapse
yes, that was while trying twrp, I managed to borrow another cable and got the firmware installed it said passed but phone gets stuck during boot up, I installed twrp now what shall I do install cyanogen again?
If you successfully flashed stock rom, boot into recovery and perform a factory wipe and reboot. The first boot make take a while but the led should pulse blue as it is booting the rom.
audit13 said:
If you successfully flashed stock rom, boot into recovery and perform a factory wipe and reboot. The first boot make take a while but the led should pulse blue as it is booting the rom.
Click to expand...
Click to collapse
I did a factory wipe and rebooted and it froze ive tried 3 or 4 times now it is upgrading 29/89 will post back if it works..
got it booted up and now its asking for set up, I appreciate your patience and help very much
Flash stock again but do not check anything except f.reset time, flash stock rom, when you see the word pass in the status window, remove USB cable, remove battery and wait 5 seconds, replace battery, boot into recovery, factory wipe, reboot.
thanks ill do that if I have a problem, for now phone is up and running and ready for use
That's great news. I guess all you needed was a different USB cable. I find the s4 to be very picky about USB cables when using Odin.