I messed up on installing a rom and I tried restoring the backup but when I boot it up, it says Verification failed and the factory reset does not work. Please help.
Download latest firmware from Sammobile and use Odin to flash it.
kevinwu128 said:
Download latest firmware from Sammobile and use Odin to flash it.
Click to expand...
Click to collapse
I've been stuck on this for at least 10 minutes now http://i.imgur.com/aR3wSSU.png
Ok I fixed it. A video told me to use home_csc, but the non home_csc worked fine.
Related
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Robbbie said:
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2507403 flash this with cwm or twrp should work
jaythenut said:
http://forum.xda-developers.com/showthread.php?t=2507403 flash this with cwm or twrp should work
Click to expand...
Click to collapse
Hello thanks for replying.
Only problem is I cannot get into cwm or twrp. Any advice on what I can do to try to get CWM or twrp working? I can flash with ODIN. But with the CWM I tried it still just boot loops and does not allow me to get into recovery.
Thank in advanced.
Robbbie said:
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Click to expand...
Click to collapse
Same Issue here. 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.
Robbbie said:
Hey guys
I have a Hong Kong Note 3 N9005. Yesterday I flashed the 4.4.2 sammobile update to my phone using ODIN 3.09. I had auto reboot and f.reset ticked. The ROM was put in AP and I hit start. Then I received the error Invalid ext4 Image. Turns out that Hong Kong versions of the N3 cannot install European ROMs. Since then I have not been able to boot my device into android. I just loop into download mode telling me it detected a firmware update. Kies was no help.
The update DID update the bootloader, so now I cannot go back to stock ROM. I have tried a few things. I tried flashing the stock Hong Kong ROM MK1, it fails. So i found a guy that fixed a similar problem buy removing the aboot.mbn file and repacking the ROM. Tried that too and the ROM flashes but it leaves me in a bootloop. Phone turns on says booting recovery then restarts. I also tried cf-root in an effort to flash another ROM still not working. I cannot get into recovery mode no matter what I do.
It seems I have run out of ideas and am reaching out for help.
Click to expand...
Click to collapse
Got this response from MrAndroid12 in another thread I'd started:
"This is not a brick at all. Just add a .pit file and restart the upgrade via Odin again.
You should be fine."
I don't know how to add a .pit file though.
I am certain the bootloops are because it flashed the new bootloader. I think your best option is to wait for a dev like indie to release Omega V7 and try to flash that through Odin.
Or if you can extract the different partitions from the original thread you can try push them one by one with Odin.
hallydamaster said:
I am certain the bootloops are because it flashed the new bootloader. I think your best option is to wait for a dev like indie to release Omega V7 and try to flash that through Odin.
Or if you can extract the different partitions from the original thread you can try push them one by one with Odin.
Click to expand...
Click to collapse
It is the bootloader yes. But it NEEDS the bootloader to be able to boot in to KitKat. And there is no downgrading once you've installed the new BL.
Best option is to re-flash via ODIN again and not wait 2 weeks for a Dev to modify a custom ROM...
Solution
Here is the solution:
http://forum.xda-developers.com/showpost.php?p=49426283&postcount=14
m1ndst0rm said:
Here is the solution:
http://forum.xda-developers.com/showpost.php?p=49426283&postcount=14
Click to expand...
Click to collapse
Works thanks
Sent from my SM-N9005 using XDA Premium 4 mobile app
I tried to flash the Baltic ROM with odin 3.07. I didn't find a way to change CSC (so KIES can recognize it) and i tried to go back to 4.3 EUR. But:
Odin failed (Checking MD5 finished Sucessfully..... Leave CS..... FAIL!) and now when i open the phone there is the following message :Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. KIES 3 says the connected device is not supported. I tried flashing the stock rom with ODIN (even tried 3.09) again but it failed. what can i do to recover my phone?
Thanks for any answers
tetra82 said:
I tried to flash the Baltic ROM with odin 3.07. I didn't find a way to change CSC (so KIES can recognize it) and i tried to go back to 4.3 EUR. But:
Odin failed (Checking MD5 finished Sucessfully..... Leave CS..... FAIL!) and now when i open the phone there is the following message :Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. KIES 3 says the connected device is not supported. I tried flashing the stock rom with ODIN (even tried 3.09) again but it failed. what can i do to recover my phone?
Thanks for any answers
Click to expand...
Click to collapse
Force Download Mode and flash one Custom Recovery. I think the Note 3 reboot from Recovery and Rom work. Try this...
But the Baltic Rom is KitKat 4.4.2?
tetra82 said:
I tried to flash the Baltic ROM with odin 3.07. I didn't find a way to change CSC (so KIES can recognize it) and i tried to go back to 4.3 EUR. But:
Odin failed (Checking MD5 finished Sucessfully..... Leave CS..... FAIL!) and now when i open the phone there is the following message :Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. KIES 3 says the connected device is not supported. I tried flashing the stock rom with ODIN (even tried 3.09) again but it failed. what can i do to recover my phone?
Thanks for any answers
Click to expand...
Click to collapse
if you flashed kitkat you cant go back to 4.3
thx for the quick replies guys. Since there is no way to go back to 4.3 is there a way to change the CSC so KIES can recognize the device? already tried CSC Select and the dialer code but no luck
tetra82 said:
thx for the quick replies guys. Since there is no way to go back to 4.3 is there a way to change the CSC so KIES can recognize the device? already tried CSC Select and the dialer code but no luck
Click to expand...
Click to collapse
The better for me is a new CLEAN install. On Customer Recovery wipe data+cache+dalvik and format system on mount and storage.
Whit recovery on screen force Download Mode and reflash the Rom. When You enter Your language at first boot, Your CSC is installed well (if the Rom have it on multi-csc).
I flashed the Poland Rom whit XEO, after first reboot I had my TPH well, automatically. What is Your CSC?
ValenteL said:
The better for me is a new CLEAN install. On Customer Recovery wipe data+cache+dalvik and format system on mount and storage.
Whit recovery on screen force Download Mode and reflash the Rom. When You enter Your language at first boot, Your CSC is installed well (if the Rom have it on multi-csc).
I flashed the Poland Rom whit XEO, after first reboot I had my TPH well, automatically. What is Your CSC?
Click to expand...
Click to collapse
OK sorry for late reply but i had a problem with my connection. I tried a different rom this time (polish) and at the same time i did what you said (full wipe etc. Worked like a charm. Device is faster thn ever and kies recognizes it again. Thanks a lot to everyone
Hi,
I tried to downgrade my Note 3 with CSC VIA to Kitkat VIA. Downloaded and flashed firmware from Sammobile. Didn't work. failed in ODIN though it finished.
I tried it again and now i can flash Kitkat with ODIN "passed" but I'm stuck in bootloop. Full wipe and cache clean in recovery won't work. Tried it a last time with Kitkat DBT version (debranded) and added a PIT file by Darklord for 1DBT. ODIN says passed but the bootloop still is there. Download mode is still available so i see some real chance to get it done.
Is it possilbe to debrand to DBT that easily or shall I stay on VIA? I never tried the PIT file for DBT with VIA firmware. Anyone has a clue what I might try to get it working again? Ah btw. Recovery and Download seems to be perfectly fine and Knox isn't triggered.
Your input is highly appreciated, thanks in advance!
peety25 said:
Hi,
I tried to downgrade my Note 3 with CSC VIA to Kitkat VIA. Downloaded and flashed firmware from Sammobile. Didn't work. failed in ODIN though it finished.
I tried it again and now i can flash Kitkat with ODIN "passed" but I'm stuck in bootloop. Full wipe and cache clean in recovery won't work. Tried it a last time with Kitkat DBT version (debranded) and added a PIT file by Darklord for 1DBT. ODIN says passed but the bootloop still is there. Download mode is still available so i see some real chance to get it done.
Is it possilbe to debrand to DBT that easily or shall I stay on VIA? I never tried the PIT file for DBT with VIA firmware. Anyone has a clue what I might try to get it working again? Ah btw. Recovery and Download seems to be perfectly fine and Knox isn't triggered.
Your input is highly appreciated, thanks in advance!
Click to expand...
Click to collapse
Try this:
1. Full wipe first (system, data, cache and dalvik)
2. Flash the VIA Kit Kat firmware via ODIN unticking "Autoreboot".
3. Take out the battery and pull in it again when the flashing process finish.
4. Boot in Recovery and make full wipe again.
5. Reboot your device and it should boot normally.
6. Tell me if it worked for ya
Hi,
thanks for you input. I tried it - still the bootloop. So I made a try with the current version (installed before). This works - most likely because I'm unable to clean Dalvik with the standard recovery.
Anyhow in the end I'm not happy with the outcome because of the bluetooth issues of the new version. Anybody has a suggestion how to downgrade sucessfully - I'd happily install a CM12.1 as well but a nightly without installation advice seems to be a bit too much for me.
try flashing MODEM with NON-HLOS, I think you have corrupted the EFS.
peety25 said:
Hi,
thanks for you input. I tried it - still the bootloop. So I made a try with the current version (installed before). This works - most likely because I'm unable to clean Dalvik with the standard recovery.
Anyhow in the end I'm not happy with the outcome because of the bluetooth issues of the new version. Anybody has a suggestion how to downgrade sucessfully - I'd happily install a CM12.1 as well but a nightly without installation advice seems to be a bit too much for me.
Click to expand...
Click to collapse
You can flash TWRP recovery if you don't care about KNOX and follow my steps above :highfive:
I tried installing almost all recoveries under T330 and T330NU but Odin keeps reporting as fail. I have tried Odin 3.09 and further without any hope. I even tried using another PC, installing drivers, and ,any versions of Odin but report fail. When I try to boot up the device it says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Kies and Kies 3 don't recognize my device. Oh and Stock ROM from sammobile and the one provided here in the general forum also report FAIL right after aboot. Am I hard bricked?
Rusell said:
I tried installing almost all recoveries under T330 and T330NU but Odin keeps reporting as fail. I have tried Odin 3.09 and further without any hope. I even tried using another PC, installing drivers, and ,any versions of Odin but report fail. When I try to boot up the device it says Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Kies and Kies 3 don't recognize my device. Oh and Stock ROM from sammobile and the one provided here in the general forum also report FAIL right after aboot. Am I hard bricked?
Click to expand...
Click to collapse
Russ, no you're not bricked, you have a flash that failed in odin, and if i understand it correctly you now have an instruction alive in your cache that executes at reboot resulting in kicking you back to that particular message/state in odin. Succeeding in a recovery or boot.img flash should break it out of that "loop". what changes have you made to your device that odin flashes are now failing? Also , are you using the factory provided cable?
m
moonbutt74 said:
Russ, no you're not bricked, you have a flash that failed in odin, and if i understand it correctly you now have an instruction alive in your cache that executes at reboot resulting in kicking you back to that particular message/state in odin. Succeeding in a recovery or boot.img flash should break it out of that "loop". what changes have you made to your device that odin flashes are now failing? Also , are you using the factory provided cable?
m
Click to expand...
Click to collapse
I am using factory cable and have use other USB cables that are verified working. What I did was flash TWRP from sub77 and then tried to flash stock rom because it was being buggy. That is when the problem started and I cant go past the message. Although I can now access Download mode but when I try to boot up normally or to recovery I receive that message.
Rusell said:
I am using factory cable and have use other USB cables that are verified working. What I did was flash TWRP from sub77 and then tried to flash stock rom because it was being buggy. That is when the problem started and I cant go past the message. Although I can now access Download mode but when I try to boot up normally or to recovery I receive that message.
Click to expand...
Click to collapse
Okay download mode is good, flash the last known working recovery that you were using. Remember to DESELECT the auto restart option in odin.
when the flash is done [res-ok] etc. , force reboot to recovery and attempt a restore of your associated backup. Meaning if your existing backup was made with an older known working version of TWRP you must use that version. If Philz, then Philz.
Odin's later newer version is required to flash the LP 5.1.1 update for the sm-t330nu. see @thisisapoorusernamechoice 's thread for instruction.
When i try to flash latest firmware from sammobile using odin 3v3.13 it wont go past boot img????
Im losing my mind trying can someone please help me
adzo73 said:
When i try to flash latest firmware from sammobile using odin 3v3.13 it wont go past boot img????
Im losing my mind trying can someone please help me
Click to expand...
Click to collapse
Hello, I had the same problem.
Before you flash restore your phone to factory default ....settings.....general ......
or by stock recovery mode ...... https://android.gadgethacks.com/how...s10-into-recovery-mode-download-mode-0194521/
and perform a factory data reset .
Then I flashed with Odin 3.13. only the AP_File. (AP_G975FXXS3ASH1_CL16487975_QB25171324_REV01_user_low_ship_meta_OS9.tar)
This is the latest official Firmware for Samsung 10+ (Exynos).... SM-G975F_1_20190805141127_n52ujmrqr9_fac
Best regards
Antonio
granada_es said:
Hello, I had the same problem.
Before you flash restore your phone to factory default ....settings.....general ......
or by stock recovery mode ...... https://android.gadgethacks.com/how...s10-into-recovery-mode-download-mode-0194521/
and perform a factory data reset .
Then I flashed with Odin 3.13. only the AP_File. (AP_G975FXXS3ASH1_CL16487975_QB25171324_REV01_user_low_ship_meta_OS9.tar)
This is the latest official Firmware for Samsung 10+ (Exynos).... SM-G975F_1_20190805141127_n52ujmrqr9_fac
Best regards
Antonio
Click to expand...
Click to collapse
I'm just doing this with this advice here, and only running the AP_File as advised. Hope the S10 doesn't get bricked because I have not loaded other files.
Also seems Odin is in state, SYSTEM, which is now so far 20mins and don't seem to see more progress
for those who updated the german beta (android 12), remember to unlock your bootloader in settings, because the knox get triggered after detecting different system files and the original bootloader, if u unlock the bootloader, it lets odin rewrite it and get the PASS