I have searched everywhere - Google, XDA, AndroidCentral, everything.
I am very savvy with computers and phones - I'm a programmer myself.
I had CM11 nightly installed for weeks. All of a sudden, my phone restarts itself into an infinite boot loop (doesn't go past the SAMSUNG Galaxy S 4 screen).
I have tried EVERYTHING. Restoring an old nandroid backup, reflashing CM11 and Gapps - nothing.
Every time I try to install the stock firmware - both L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 (acquired directly from Samsung) and L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 (again, direct download) it always fails at the same spot:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_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> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I flashed the MK2 modem when flashing the MK2 stock ROM... no dice. Same thing for the NAE modem + ROM.
Please, help me. I have no clue what to do at this point. The only backup I have, which is of Android 4.2.2, also doesn't work. Same bootloop.
I have tried all of the above things with three different version of Odin: 1.805, 3.04 and 3.07.
I re-installed the Samsung USB drivers, in case that was the issue.
I am completely clueless.
The main problem (I believe) is this:
aboot.mbn
Please and thank you.
rpnunez said:
I have searched everywhere - Google, XDA, AndroidCentral, everything.
I am very savvy with computers and phones - I'm a programmer myself.
I had CM11 nightly installed for weeks. All of a sudden, my phone restarts itself into an infinite boot loop (doesn't go past the SAMSUNG Galaxy S 4 screen).
I have tried EVERYTHING. Restoring an old nandroid backup, reflashing CM11 and Gapps - nothing.
Every time I try to install the stock firmware - both L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5 (acquired directly from Samsung) and L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5 (again, direct download) it always fails at the same spot:
I flashed the MK2 modem when flashing the MK2 stock ROM... no dice. Same thing for the NAE modem + ROM.
Please, help me. I have no clue what to do at this point. The only backup I have, which is of Android 4.2.2, also doesn't work. Same bootloop.
I have tried all of the above things with three different version of Odin: 1.805, 3.04 and 3.07.
I re-installed the Samsung USB drivers, in case that was the issue.
I am completely clueless.
The main problem (I believe) is this:
aboot.mbn
Please and thank you.
Click to expand...
Click to collapse
I know this sounds redundant or maybe you've done this too.
Charge the phone fully - while powered off. Take the battery out for 15 earth minutes. Then run Odin as administrator on your PC 1st (use the full NAE tar put in the PDA slot (in the dev section read the thread for some other tips too)) Then put phone into download mode and then plug into computer
ALSO I know this too sounds silly, but try a brand new USB cable. Can't tell you how many times that has caused problems for me.
Good luck
leaderbuilder said:
I know this sounds redundant or maybe you've done this too.
Charge the phone fully - while powered off. Take the battery out for 15 earth minutes. Then run Odin as administrator on your PC 1st (use the full NAE tar put in the PDA slot (in the dev section read the thread for some other tips too)) Then put phone into download mode and then plug into computer
ALSO I know this too sounds silly, but try a brand new USB cable. Can't tell you how many times that has caused problems for me.
Good luck
Click to expand...
Click to collapse
Thank you for such a quick response!
The phone won't go into the "charging mode" which I know is what you're talking about
The USB cable is fine, every time I flash one of the stock ROMs on the phone I have to re-flash the recovery, so we can cross that one off the list.
Am I not using the correct tar file? The file was zipped in a file entitled "Samsung-Updates.com-SPH-L720-SPR-L720VPUAMDC-1365579188.zip" which I downloaded yesterday.
It's charging now in Philz Recovery. Once it's at 100%, I will take out the battery for 15 minutes (hell, probably even 30! lol) and see what happens.
Any other suggestions my friend? Once again, thank you!
rpnunez said:
Thank you for such a quick response!
The phone won't go into the "charging mode" which I know is what you're talking about
The USB cable is fine, every time I flash one of the stock ROMs on the phone I have to re-flash the recovery, so we can cross that one off the list.
Am I not using the correct tar file? The file was zipped in a file entitled "Samsung-Updates.com-SPH-L720-SPR-L720VPUAMDC-1365579188.zip" which I downloaded yesterday.
It's charging now in Philz Recovery. Once it's at 100%, I will take out the battery for 15 minutes (hell, probably even 30! lol) and see what happens.
Any other suggestions my friend? Once again, thank you!
Click to expand...
Click to collapse
If your phone had an MJA or later - MK2 or NAE bootloader you CANNOT flash any Odin ROM previous because of the Knox bootloader.
You're trying the MDC - that won't work.
Keep the phone charging and try the NAE
Here is a similar post and similar problem with my response (includes the link to the NAE .tar)
leaderbuilder said:
If your phone had an MJA or later - MK2 or NAE bootloader you CANNOT flash any Odin ROM previous because of the Knox bootloader.
You're trying the MDC - that won't work.
Keep the phone charging and try the NAE
Here is a similar post and similar problem with my response (includes the link to the NAE .tar)
Click to expand...
Click to collapse
Ahhh... that makes sense.
I just tried flashing the MDC modem, because I believe my 4.2.2 backup is on MDC...but now I have the weirdest message saying "System software not authorized by Samsung has been found on your phone".
Now I think I messed things up...
I'm downloading the NAE file. Hopefully flashing that will fix everything.
Why can't I just delete *everything*? Like a reformat on a Windows PC? Literally, destroy everything - and just flash the stock NAE firmware?
I appreciate your help now so much my friend. Thank you.
rpnunez said:
Ahhh... that makes sense.
I just tried flashing the MDC modem, because I believe my 4.2.2 backup is on MDC...but now I have the weirdest message saying "System software not authorized by Samsung has been found on your phone".
Now I think I messed things up...
I'm downloading the NAE file. Hopefully flashing that will fix everything.
Why can't I just delete *everything*? Like a reformat on a Windows PC? Literally, destroy everything - and just flash the stock NAE firmware?
I appreciate your help now so much my friend. Thank you.
Click to expand...
Click to collapse
Because of the Knox bootloader you can't wipe everything. Read my other thread as to why. Knox bootloader is in the chips security container and once tripped is not, as of now removable.
Flashing the tar should get you all good to go.
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
Because of the Knox bootloader you can't wipe everything. Read my other thread as to why. Knox bootloader is in the chips security container and once tripped is not, as of now removable.
Flashing the tar should get you all good to go.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was able to successfully flash to the TAR you linked me to!
However, I am still stuck in a bootloop...
It won't even let me boot into recovery.
You've been such a help buddy. Any other ideas?
If the tar flashed successfully try power off completely.
Then boot to stock recovery - Power on + Volume up (kind of tricky on the S4, I often miss the right length of time to hold both kind of freaks me out/pissed me off, but eventually after many battery pulls I'll get it on boot. )
Then try a factory reset.
Edit if that fails then try this also:
You can also try to Odin a custom recovery - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltespr/philz_touch_6.08.9-jfltespr.tar.md5 [download mode, odin in PDA slot - do NO check f-reset or autoreboot - once odin is finished do a battery pull]
Then try to get to custom recovery and flash the stock NAE kernel if it doesn't boot
Here's Philz http://forum.xda-developers.com/showpost.php?p=51411121&postcount=1955
leaderbuilder said:
If the tar flashed successfully try power off completely.
Then boot to stock recovery - Power on + Volume up (kind of tricky on the S4, I often miss the right length of time to hold both kind of freaks me out/pissed me off, but eventually after many battery pulls I'll get it on boot. )
Then try a factory reset.
Edit if that fails then try this also:
You can also try to Odin a custom recovery - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltespr/philz_touch_6.08.9-jfltespr.tar.md5 [download mode, odin in PDA slot - do NO check f-reset or autoreboot - once odin is finished do a battery pull]
Then try to get to custom recovery and flash the stock NAE kernel if it doesn't boot
Here's Philz http://forum.xda-developers.com/showpost.php?p=51411121&postcount=1955
Click to expand...
Click to collapse
Can't get to stock recovery - it just says "RECOVERY BOOTING..." then reboots.
Installed Philz Recovery, installed CF-Auto-Root since Philz complained that I wasn't rooted, when I tried to flash the NAE kernel, it says:
Using legacy property environment for update-binary...
Please upgrade to latest binary...
Currently installing kernel
format() expects 4args, got 5
E:Error in /storage/sdcard1/Negalite_NAE_Stock_Kernel.zip (Status 7)
Installation aborted.
Click to expand...
Click to collapse
Why me
That's okay. Status 7 is an updater script error. There are a few things.
Let's try another kernel.
OR another recovery (I keep multiple recoveries on my externaSD for this reason.
Here is Reverepats TWRP You can flash the recovery from recovery and reboot recovery. Say that five times..
Since you did get to custom recovery you're heading the right way.
Try flashing the stock kernel from the TWRP recovery and
You can try another kernel too.
Ktoonsez' latest kernel is here You can grab the 4.4 TW one (take note of the build prop edit you may have to do to get wifi working - that'll require rooting (cf-autoroo) and a root explorer to get to it)
All seems kernel related to me.
Here is a vid on disabling script checking tha may work too. I relize that it's for full ROMs but it may help.
leaderbuilder said:
That's okay. Status 7 is an updater script error. There are a few things.
Let's try another kernel.
OR another recovery (I keep multiple recoveries on my externaSD for this reason.
Here is Reverepats TWRP You can flash the recovery from recovery and reboot recovery. Say that five times..
Since you did get to custom recovery you're heading the right way.
Try flashing the stock kernel from the TWRP recovery and
You can try another kernel too.
Ktoonsez' latest kernel is here You can grab the 4.4 TW one (take note of the build prop edit you may have to do to get wifi working - that'll require rooting (cf-autoroo) and a root explorer to get to it)
All seems kernel related to me.
Here is a vid on disabling script checking tha may work too. I relize that it's for full ROMs but it may help.
Click to expand...
Click to collapse
I tried flashing Recerepats TWRP via Philz... no dice. I guess it's just not my day lol. I tried Odin'ing openrecovery (2 versions) and noooo dice.
So I went back to the Philz 6 (I tried flashing Philz 5 and.. no luck), flashed the kernel you linked to, it flashed fine.
....still in a boot loop. I'm so sorry for taking up your time buddy, you've been such a great help.
I'm guessing I should re-odin the NAE tar now, since the kernel has been modified?
I feel like a mechanic who can't change his own car oil lol. I'm a programmer and write PHP/JavaScript daily, none of these things scare me - but nothing is working!
Ya,
I'd try re-odining the tar again.
Just put in the pda slot as usual, but this time try unchecking the Auto Reboot and F. reset time. and when done just battery pull and restart.
Edit/Add:
Oh and you might still have to 'factory reset' from stock recovery' if it gets stuck on bootloop.
BUT remember the first boot takes a freaking long time - 5-10 earth minutes for first boot! wait and then try the reset if it doesn't get past it
leaderbuilder said:
Ya,
I'd try re-odining the tar again.
Just put in the pda slot as usual, but this time try unchecking the Auto Reboot and F. reset time. and when done just battery pull and restart.
Edit/Add:
Oh and you might still have to 'factory reset' from stock recovery' if it gets stuck on bootloop.
BUT remember the first boot takes a freaking long time - 5-10 earth minutes for first boot! wait and then try the reset if it doesn't get past it
Click to expand...
Click to collapse
Just finished re-odinining the tar file. Nothing. Still in a bootloop.
How can my device be so ruined? All I would do is install new CM nightlies - the right way, too. I remember I was in a shopping market yesterday, everything was nice and dandy, and when I get in my car, this bootloop thing started happening,
I'm baffled by this... I really, really am. With your help, along with other things I've tried, I've tried everything under the sun.
The only thing I haven't thought of is using ADB/working on the phone via command line.
What do you think?
Worth a shot.
One thing though.
Before you give up pull the battery again for about 15+ minutes. then put it back in and then try to Odin. I had to do that on my old Epic a few times.
Couldn't hurt to try adb.
One last thing - in custom recovery (philz say) wipe the cache and then wipe the Dalvik cache (in advanced I think) then try booting again. Sometimes that helps bootloops.
But for sh*ts and giggles how about trying to install a custom ROM? Maybe Negalites's Here's his release version
To install boot to Philz recovery; wipe cache, wipe dalvik and the wipe to install new ROM/Factory reset then select the negalite.zip and run throught the install.
@rpnunez haven't seen a post back. Hope you got it going.
leaderbuilder said:
@rpnunez haven't seen a post back. Hope you got it going.
Click to expand...
Click to collapse
Leaderbuilder, thank you so much for following up like that - it really means alot!
Unfortunately, I tried your latest suggestions, and still nothing - both unchecking Auto Reboot and F. Reset Time + battery pull for 15 mins, and the wiping of the cache and dalvik cache.
I should try flashing a custom ROM, but may I ask why flashing CM + Gapps would be different? I've tried flashing CM countless times :/
Also, could any of this be happening because of Knox? I've read about Knox, but I don't really know much about it. Before I posted this thread, I downloaded a multi-tool kit (Dr. Ketan's Multitool v6 - I followed this guide: http://techbeasts.com/2014/01/17/how-to-deknox-samsung-galaxy-s3-s4-note-2-note-3/) and it was to "reset" the Knox counter, but it didn't get me out of the boot loop.
I just wish there was a "Format" function for my phone lol. Is there anything else you can think of? I really don't understand how a phone can get so... destroyed. No water damage, no fall, nothing - from one moment to the next, boot loop.
Would the stock recovery help? When I flash the NAE tar, I hold Volume Up + Power, I see "RECOVERY BOOTING..." and then... boot loop! Can that give any clues?
What's odd is that it won't go past the Samsung Galaxy S4 screen - it's like a computer not being able to go past the BIOS screen.
Once again, I greatly appreciate your time and effort.
Well you can Odin a custom recovery again. And wipe the crap out of everything - caches, system, DATA for sure do that, wipe to install new ROM. (if you use TWRP - there is an option to use rm vs format which may help in advanced I think.)
Then flash Philz maybe and again try another ROM like Negalite
I'm pretty stumped but that's what I'd do - wipe the sh*t out of it, reboot recovery wipe again then try installing ROM.
leaderbuilder said:
Well you can Odin a custom recovery again. And wipe the crap out of everything - caches, system, DATA for sure do that, wipe to install new ROM. (if you use TWRP - there is an option to use rm vs format which may help in advanced I think.)
Then flash Philz maybe and again try another ROM like Negalite
I'm pretty stumped but that's what I'd do - wipe the sh*t out of it, reboot recovery wipe again then try installing ROM.
Click to expand...
Click to collapse
It's really odd that I can't flash any recovery other than PhilZ "philz_touch_6.25.0-jflte.tar.md5". I can't even flash a slightly older version, "philz_touch_5.18.2-jfltespr.tar.md5". Hell, I've tried all of these:
OUDHS-Recovery-jfltespr-1.0.3.3.tar
openrecovery-twrp-2.7.0.1-jfltespr.tar
openrecovery-twrp-2.6.3.0-jfltespr.tar
clockworkmod_6.0.3.2_jfltespr.img
GalaxyS4-CWM-6.0.4.4-Sprint.tar
openrecovery-twrp-2.6.0.0-jfltespr.tar
And NONE of them work.
In PhilZ, I formatted everything (wipedata, wipe to install new rom, formatted /boot, /preload/ cache, /system, everything that can be formatted - flashed NAE tar again and nothing.
I'm going to go ahead and try to flash Negalite's ROM. I'm about to just take the damn phone to Best Buy because luckily have I have insurance on it... but geez, I really cannot fathom what is going on with this device. But I still want to try a few more things.
Do you know of any ADB commands/guides or something that can perhaps generate a "log file" as to what's going on during the boot process? Or something to that effect?
Thank you for your time my friend. :angel:
Edit/Update:
Flashed Negalite's ROM... nothing. I'm getting tired of looking at the Samsung Galaxy S4 boot screen lol.
Would using "Re-partition" help? Maybe something got partitioned? I'm really running out of ideas..
rpnunez said:
It's really odd that I can't flash any recovery other than PhilZ "philz_touch_6.25.0-jflte.tar.md5". I can't even flash a slightly older version, "philz_touch_5.18.2-jfltespr.tar.md5". Hell, I've tried all of these:
OUDHS-Recovery-jfltespr-1.0.3.3.tar
openrecovery-twrp-2.7.0.1-jfltespr.tar
openrecovery-twrp-2.6.3.0-jfltespr.tar
clockworkmod_6.0.3.2_jfltespr.img
GalaxyS4-CWM-6.0.4.4-Sprint.tar
openrecovery-twrp-2.6.0.0-jfltespr.tar
And NONE of them work.
In PhilZ, I formatted everything (wipedata, wipe to install new rom, formatted /boot, /preload/ cache, /system, everything that can be formatted - flashed NAE tar again and nothing.
I'm going to go ahead and try to flash Negalite's ROM. I'm about to just take the damn phone to Best Buy because luckily have I have insurance on it... but geez, I really cannot fathom what is going on with this device. But I still want to try a few more things.
Do you know of any ADB commands/guides or something that can perhaps generate a "log file" as to what's going on during the boot process? Or something to that effect?
Thank you for your time my friend. :angel:
Edit/Update:
Flashed Negalite's ROM... nothing. I'm getting tired of looking at the Samsung Galaxy S4 boot screen lol.
Would using "Re-partition" help? Maybe something got partitioned? I'm really running out of ideas..
Click to expand...
Click to collapse
Okay, by chance is your device the T model? - the Triband one?
Because I can see and think of no reason why all this wouldn't work unless it was not the Sprint SPH-L720.
leaderbuilder said:
Okay, by chance is your device the T model? - the Triband one?
Because I can see and think of no reason why all this wouldn't work unless it was not the Sprint SPH-L720.
Click to expand...
Click to collapse
I do believe it is the Triband one... it has a SIM card, and I remember seeing options like "GSM, GSM/CDMA, GSM/CDMA/LTE" when selecting network mode or w/e it's called. Is there a way to determine if it is Triband?
Related
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
The_SilverOne said:
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
Click to expand...
Click to collapse
The kernel message was no problem for me.using safe strap?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
the kernel error is common just proceed as you did
did you wipe all including system before flashing? i don't usually wipe in aroma unless no choice given
did you choose your correct carrier--who is your carrier--that info helps us tp help you--
i don't have i337m so can't be specific on things relating to that phone. you say i337m and i337 is in your sig
if you have i337 you need to flash loki-doki after rom
maybe try twrp--i use 2.5.0.2--i have, and there is a flashable zip for it (i337)
got to go for now--
rugmankc said:
the kernel error is common just proceed as you did
did you wipe all including system before flashing? i don't usually wipe in aroma unless no choice given
did you choose your correct carrier--who is your carrier--that info helps us tp help you--
i don't have i337m so can't be specific on things relating to that phone. you say i337m and i337 is in your sig
if you have i337 you need to flash loki-doki after rom
maybe try twrp--i use 2.5.0.2--i have, and there is a flashable zip for it (i337)
got to go for now--
Click to expand...
Click to collapse
Thank you both for your replys, your help is very much appreciated.
So I wiped it with recovery not aroma.
Carrier is Fido (Rogers subsidiary)
Phone is Canadian S4 variant (SGH-I337m) I believe it is the same as i337 (The m being a canadian designation) but don't quote me on that.
I was under the assumption that Canadian s4 Didn't need lokidoki.
Can you elaborate on safestrap?
No matter what I try it goes boots to download mode. Even if I plug it in to charge not pressing any power button.
Canadian s4 doesnt need loki doki. And your not on safestrap if you have twrp.
As far as your problem. Did it complete the install of the rom even after it said it failed the kernel?
I suggest installing then flashing a 4.3 tw kernel for your device before rebooting system. You shouldn't need a compatibility pack as your not att. Plus im pretty sure the compat pack has loki in it which may cause problems. I also remember philz recovery as having auto loki. So I dont know if you've used philz recovery b4 successfully. If you haven't then id suggest trying twrp. Definitely just try a kernel for your device though. Ktoons worked for me. Other kernels left me stuck at spash screen
SelfElevated2 said:
Canadian s4 doesnt need loki doki. And your not on safestrap if you have twrp.
Click to expand...
Click to collapse
I believe that my phone's bootloader is unlocked (as with most other jtflecan models), but again don't quote me. As a result I have never used safestrap. Should/could I still use it if my bootloader is unlocked?
SelfElevated2 said:
As far as your problem. Did it complete the install of the rom even after it said it failed the kernel?
Click to expand...
Click to collapse
It seemed that way as that was the only error, and aroma proceeded through. First time I tried without the ATT compatibility pack, no go, then with and still no go. Then i tried with a few kernels and same thing.
SelfElevated2 said:
I suggest installing then flashing a 4.3 tw kernel for your device before rebooting system. You shouldn't need a compatibility pack as your not att. Plus im pretty sure the compat pack has loki in it which may cause problems. I also remember philz recovery as having auto loki. So I dont know if you've used philz recovery b4 successfully. If you haven't then id suggest trying twrp. Definitely just try a kernel for your device though. Ktoons worked for me. Other kernels left me stuck at spash screen
Click to expand...
Click to collapse
I transitioned from cwm to philz for ntfs capability as my external sdcard is ntfs. I remember reading somewhere that autoloki was not included and some have complained about it so im not sure if it was added in a later build. In any case I just tried flashing twrp and got a mushy brick.
Now Im curious if I should restore to original and use safestrap or what as my phone does nothing but odin mode.
As always thanks for your valued input.
Your boot loader is definitely not locked. If it was you wouldnt have a custom recovery. So you don't need safestrap. Just restore and reroot and get a recovery. What you put on your phone after that is up to you. I know hyperdrive wouldn't boot for me with most kernels it was just stuck on the splash screen. But it booted for kt kernel. I would honestly find another Rom if I was in the same position
MINI UPDATE:
Phone was bootlooping so I tried to restore to stock 4.2.2 but ODIN failed continuously. Tried 4.3 stock (mk6) and odin failed, tried older odin and succeeded but it bootlooped and went to the kies upgrade error. Tried multiple Computers (2PC 1OSX) multiple ports and cables and all failed.
Trying to figure this out but not much help out there with regards to canadian s4, att guides ok? any suggestions? trying kies restore now but kies hangs after it downloads firmware. urgh
ODIN Outuput:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
ODIN seems to fail at different points, sometimes in recovery, or modem or etc.
do i need to repartition?if so where do i find the pit file for my device?
im reading that im screwed and praying its not true.
Thanks for any help
You cant get into recovery? Only odin? Just keep looking around. I bet its because the aroma flashed a incomplete flash. But I dont know the difference between i337 and i337m so I dont know what to tell you. I suggest keep trying to Odin. If it doesn't work I believe theres a tool to force a stock image onto the phone but I cant remember what its called
SelfElevated2 said:
You cant get into recovery? Only odin? Just keep looking around. I bet its because the aroma flashed a incomplete flash. But I dont know the difference between i337 and i337m so I dont know what to tell you. I suggest keep trying to Odin. If it doesn't work I believe theres a tool to force a stock image onto the phone but I cant remember what its called
Click to expand...
Click to collapse
no i only get odin.
phone only turns on when plugged in to usb on pc, otherwise unresponsive to hardkeys.
Every instance of ODIN flashing fails. No matter which firmware or computer i used, either write failure or PIT failure. both of which im attributing to an incomplete flash, and its making me think that the partition tables are chewed.
im stumped and phonless
any idea what that app was called? google yields no results
thanks for your help
Heres something to read. I dont know if you need the.Canadian pit or reg att pit. Dont just flash one. Get informed first
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
SelfElevated2 said:
Heres something to read. I dont know if you need the.Canadian pit or reg att pit. Dont just flash one. Get informed first
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Click to expand...
Click to collapse
Thank you very much for that link. It summed up everything i have been reading for the past 24 hours, but alas i have yet to figure out which pit to use, whether I can use the att pit, wind (different provider, uses aws (2 different frequencies from gsm standard) as opposed to gsm although they may have changed that recently),find a rogers pit, since they and fido are essentially the same network or continue searching for a fido pit.
Knowing what the pit does, would it really be carrier specific (asides from the difference in radios between fido/rogers and wind)? Is it ROM version and android version specific?
Update:
-Have Tried all options for recovery in KIES on multiple Pcs and Multiple Macs
-Download/Odin Mode Reads:
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
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224,1440]
BAR [240,1440
Questions:
Before this whole fiasco ODIN didnt show KNOX. I assume thats from the 4.3 revert i tried?
Does Write Protection have anything to do with it? I do recall being able to odin flash with this before.
eMMC Burst is new to me, havent seen this before
BAR pops up before failing but not seconds before, maybe a minute before.
Still Stumped
Edit: Even if i were to find the pit file, i cant seem to find modem, csc, and bootloader to add to odin. (unless they are all combined in that md5 file) so i wouldnt be able to flash until having all the necessary items as pit rewrites the partitions and all data is lost.
i also remembered one odd thing, may or may not apply here, but just before flashing to hyperdrive, i was not able to properly format. it would take a few tries to format data or whichever for example, before files were actually gone.
tried reverting to MDJ got vibrate loop
trying again to MK6
The_SilverOne said:
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
Click to expand...
Click to collapse
Hi, I am currently having this problem after trying to install RLS15.
After trying to flash the new ROM, phone would not boot, and I was no longer able to install ROMS or Restore backups.
When I would try to restore a backup, it would get to Restoring Data, and immediately fail.
When installing the ROM and its kernel, I got the same message as you:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
I've tried:
flashing kernels before flashing the ROM
re-install of Loki + TWRP + Motochopper Casual (Did not revert back to stock before doing this)
flashing the AT&T Compatibility pack.zip for RLS15 Before and After flashing the ROM
Fixing permission
I've noticed once or twice, when trying to restore a backup, a message in TWRP saying that SuperUser was not installed, and it asked if I wanted to install it. So I did the "Swipe to install" in TWRP, but the phone quickly reboots and again doesn't get passed the boot logo.
Sooo, I'm not too sure where to start on this one
d9vabder said:
Hi, I am currently having this problem after trying to install RLS15.
After trying to flash the new ROM, phone would not boot, and I was no longer able to install ROMS or Restore backups.
When I would try to restore a backup, it would get to Restoring Data, and immediately fail.
When installing the ROM and its kernel, I got the same message as you:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
I've tried:
flashing kernels before flashing the ROM
re-install of Loki + TWRP + Motochopper Casual (Did not revert back to stock before doing this)
flashing the AT&T Compatibility pack.zip for RLS15 Before and After flashing the ROM
Fixing permission
I've noticed once or twice, when trying to restore a backup, a message in TWRP saying that SuperUser was not installed, and it asked if I wanted to install it. So I did the "Swipe to install" in TWRP, but the phone quickly reboots and again doesn't get passed the boot logo.
Sooo, I'm not too sure where to start on this one
Click to expand...
Click to collapse
What variant do you have?
So I figured out my problem. In TWRP recovery, I went to mounts, and mounted my micro SD card. It was mounted to internal memory and I guess that was screwing up flashes. Hope this works for you too!
Sent from my SAMSUNG-SGH-I337 using xda premium
good evening
I am in a bit of tight spot
and before a srew it up (more) I wonder if you could help
I have a SM-G900V which is rooted and I had TWRP working just fine
I tried to flash a rom (project infinity) with aroma which freezed on installing aroma
the developer replied to me that the problem was from TWRP which had a bus and that I should instal CWP
I tried to install CWP on top of TWRP through ODIN and got a failure message
as of now I have neither TWRP or CWP or any rom flashed in mydevice
once I go into recovery mode and try to flash the previous rom that I had through the sdcard it says "footer is wrong signature fail" an reboots and gets stuck with no rom
just tried to reinstall TWRP through ODIN and got the failure message again
with the folowing message:
<ID:0/003> Added!!
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)
please help
Hey man,
Sounds like you're in a bit of a pickle. Not sure if this would be a bit extreme, but I'd download the stock firmware and flash it through Odin. After that, reflash recovery and retry your rom.
I kind of see flashing back to stock a 'fail safe' in most cases, so it's always handy to have the stock firmware stored somewhere anyway. ?
Sent from my SM-G900I
..
fffft said:
Don't flash anything until someone discerns what went wrong..
being impatient at this point will put you at high risk of bricking or worse.
The phone boots normally up until the footer error?
What is the exact error message that you see?
What version of TWRP did you have?
Any backups? If so, do they include your baseband, EFS & PIT?
16 GB ROM?
Did you have a Verizon ROM when this happened?
Rooted?
.
Click to expand...
Click to collapse
let me start by thank you for your time!
I am a bit new to all this, I have flashed some roms in the past so I am also familiar with some stuff...
The phone doesn't boot it gets stuck like the attached picture, the OS doesn't start.
I don't see any message as it is stuck like I mentioned before, I just saw a message of "FAIL!" in Odin when I tried to install CWM on top of TWRP
my version of TWRP was 2.7.1.0
I had a backup on TWRP but as I dont see TWRP working anymore I dont know if its still available
my phone is 16GB
my SM-G900V is rooted and at the moment I had working perfectly SpeedROM v1 Rev2
if you would like to contact me through chat let me know, and again thank you very much!!
Try this
..
fffft said:
Okay, on the positive side there isn't anything to suggest that your bootloader is corrupt which would make this a lot harder. Probably the failed aroma install just messed your kernel up. But I don't want to recommend messing around with shortcut solutions e.g. just flashing the kernel that may or may not work, but would put you at unnecessary further risk.
The earlier suggestion to flash a full stock image is generally sound advice, but it does not apply to all situations. My questions were basically aimed at getting a sense of whether you have corrupted the bootloader or partitioning which has a bearing on how to best recover your phone.
First, I am assuming that you do not have the Dev (unlocked bootloader) version S5. If you have the Dev edition with the unlocked bootloader, do not proceed with the rest of this post until we discuss that.
On the assumption that you have a regular 16 GB Verizon SM-G900V S5, then I would like to see you Odin flash a full stock S5 Verizon image that has been rooted. Unfortunately I couldn't find anyone who has made and posted a stock rooted Verizon S5 image like that. I don't mean a stock rooted (custom) ROM.. I mean the full stock firmware image, including the bootloader, but rooted.
That's fine. The rooted part would just be a little extra insurance put against theoretical possible snags i.e. Knox issues. So I will suggest that you use Odin to flash a full stock Verizon S5 image, with an explicit partition table. Normally we don't touch the partition information (PIT) in Odin, but in your case we need to.
Download the files below from this thread
Unless you already have the file on your PC
Verizon S5 Retail Tar 4.4.2 NCG baseband and Mar 31 kernel
MD5: 699a949b57c771b00db9f3ed675c7a5e
NCG Pit
MD5: 3dd82f91a02c82e60e0a1f9964fdb5c0
Odin 3.09
MD5: 810ad286967d0a33881fd8181d35959f
You should thank the OP in that thread for collating the files that you need in one place.
Particularly that all important PIT file.
Start Odin and check these three boxes only: Auto reboot, Re-Partition, F. Reset Time
Choose the PIT file in the PIT window. Note that the PIT file needs to be extracted. Do not leave it zipped.
Choose the stock firmware tar.md5 file in the PDA window. The tar.md5 file needs to remain tarred i.e. tar.md5 or .tar
Put your phone into download mode. Ensure that your phone is off, remove the battery for a few seconds if necessary, then press volume down + home + power until you see the android robot screen come up. If it doesn't go into download mode, repeat these steps. And in the very unlikely event that you can't get into the download mode at all, stop and post that information
Connect your phone to your PC, Odin should say that it has detected your phone
Press start and let Odin flash your phone
Basically we are replacing all of the system files and assuring that your partitioning has not been corrupted
When Odin finishes with a success message your phone should be back to normal. Do a normal reboot to confirm
If you did not backup your phone, your user files in the /data partition might still be accessible
Decide if you wish to back them up or not. Do so if you need them. Then do a factory reset from the Settings menu
You will need to re-root and reinstall your apps, etc
If you run into any difficulties:
If the Odin write fails, note the error message and double check that your Odin settings were correct
Do not close Odin. Pull the battery from your phone for ten seconds.
Then replace the battery and go into download mode again (vol down + home + power)
Note whether Odin detects the phone
Then try flashing with Odin again. Note that you are not closing the Odin program if the first flash attempt fails
Odin can be a bit picky and it is not unheard of to have to reset the phone like this and run the session a second time
Odin is also picky about USB cables. If you still continued trouble, try a different USB cable and USB port
Don't despair if anything goes astray. There is almost always an alternate way to go about something.
Let us know your results so that we can (hopefully) celebrate. Or at least regroup.
.
Click to expand...
Click to collapse
you senior member??? pppffffffff
you should OWN this forum!!! thanx a lot for your extended time in this explanation mate, I will proceed and let you know
Agreed. I use a Dell and sometimes I have problems with odin using the front usb. I have to use the read usb and then no problems.
Hi Guys!!
I am back, back with my phone completely restored
A special THANX to fffff for your help!!
..
I need help. lol. my Samsung note 3 is stuck in bootloop. I posted this in the thread for the hyperdrive rom because its what I was trying to flash.
i wiped and flashed in the stock slot. and now im stuck in the bootloop problem. it says recovery booting in the upper left of the screen and just keeps rebooting. I tried going in to odin and reloading the "n900v kk firmware" and nothing. anyone know a fix for this. is there something I can download to flash to fix this. I know I will have to use odin, just not sure what.
donelam304 said:
I need help. lol. my Samsung note 3 is stuck in bootloop. I posted this in the thread for the hyperdrive rom because its what I was trying to flash.
i wiped and flashed in the stock slot. and now im stuck in the bootloop problem. it says recovery booting in the upper left of the screen and just keeps rebooting. I tried going in to odin and reloading the "n900v kk firmware" and nothing. anyone know a fix for this. is there something I can download to flash to fix this. I know I will have to use odin, just not sure what.
Click to expand...
Click to collapse
Hi I'm kinda new to the community and Android, but I'll try to help. I've been having issues trying to use safestrap to install my custom roms. I know that 3.72 had issues with the extra slots. That was supposed to be fixed in 3.75. In short I haven't reached a loop but have had to flash to stock several times with Odin. I had to remove my battery to get the phone in "power off" mode. From there, I booted to download for odin (assuming you can get it to boot to download-volume down/home/power buttons to get there).
Once I got there, I just made sure I had the firmware version I wanted to go back to, plugged it into odin and bam! Back to stock to start over.
Bryotch said:
Hi I'm kinda new to the community and Android, but I'll try to help. I've been having issues trying to use safestrap to install my custom roms. I know that 3.72 had issues with the extra slots. That was supposed to be fixed in 3.75. In short I haven't reached a loop but have had to flash to stock several times with Odin. I had to remove my battery to get the phone in "power off" mode. From there, I booted to download for odin (assuming you can get it to boot to download-volume down/home/power buttons to get there).
Once I got there, I just made sure I had the firmware version I wanted to go back to, plugged it into odin and bam! Back to stock to start over.
Click to expand...
Click to collapse
I can boot in to the download mode. has no problem. even tried flashing the n900v_kk_firmware.tar.md5 tar,
ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
and even tried the N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5
and when I do the MJE one it says invalid. am I flashing the wrong file is there something else I should be using. when I get in to manual mode after it boots in to manual recovery mode it says im on NC4. it says in the upper left corner the following:
Android stem recovery <3e>
KOT49H.N900VVRUCNC
volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
is there a way to flash safestrap or CWM in odin.
donelam304 said:
I can boot in to the download mode. has no problem. even tried flashing the n900v_kk_firmware.tar.md5 tar,
ALL_N900VVRUBMJE_N900VVZWMJE_2106277_REV03_user_low_ship_MULTI_CERT.tar.md5
and even tried the N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5
and when I do the MJE one it says invalid. am I flashing the wrong file is there something else I should be using. when I get in to manual mode after it boots in to manual recovery mode it says im on NC4. it says in the upper left corner the following:
Android stem recovery <3e>
KOT49H.N900VVRUCNC
volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
is there a way to flash safestrap or CWM in odin.
Click to expand...
Click to collapse
You're running the same build I have, been having similar issues. I used Odin no completely repartition and wipe the phone. I used N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5 and the HLTE.pit file (for this build). In Odin You put the pit and md5 files in (.pit file in the PIT slot and md5 in the AP slot on Odin 3.09) This took me back to the KK NC4 build, granted, I lost alot of data but I didn't use a Nandroid backup either. This got me back to a functional device but i'm still having issues getting ANY custom roms to work. I did flash to NC2 kernel since then and still no luck. Let me know if that helps. I can get the files I used if you can't find them, but most everything came from xda.
PS. you can find some firmwares with recovery and other things added. I avoided these just to make sure I could get back to stock. I use Towelroot, BusyBox, SuperSU, and Safestrap 3.75 b04
Bryotch said:
You're running the same build I have, been having similar issues. I used Odin no completely repartition and wipe the phone. I used N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5 and the HLTE.pit file (for this build). In Odin You put the pit and md5 files in (.pit file in the PIT slot and md5 in the AP slot on Odin 3.09) This took me back to the KK NC4 build, granted, I lost alot of data but I didn't use a Nandroid backup either. This got me back to a functional device but i'm still having issues getting ANY custom roms to work. I did flash to NC2 kernel since then and still no luck. Let me know if that helps. I can get the files I used if you can't find them, but most everything came from xda.
PS. you can find some firmwares with recovery and other things added. I avoided these just to make sure I could get back to stock. I use Towelroot, BusyBox, SuperSU, and Safestrap 3.75 b04
Click to expand...
Click to collapse
i done a search on the stock firmware you mentioned and after about 2 dozen websites and and trying about 15 flashes I finally got it to work. this has been one heck of a day. I finally got it to work. I am in the process of trying to get safestrap and stuff on it now. I already used towelroot to rot it. what version of safestrap do you recommend. I was told 3.72 was for KK. and 3.75 was for the Samsung galaxy S5.
donelam304 said:
i done a search on the stock firmware you mentioned and after about 2 dozen websites and and trying about 15 flashes I finally got it to work. this has been one heck of a day. I finally got it to work. I am in the process of trying to get safestrap and stuff on it now. I already used towelroot to rot it. what version of safestrap do you recommend. I was told 3.72 was for KK. and 3.75 was for the Samsung galaxy S5.
Click to expand...
Click to collapse
here is the link I found with all the carriers for the note 3
http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/
donelam304 said:
here is the link I found with all the carriers for the note 3
http://galaxynote3root.com/galaxy-note-3-repair/how-to-unroot-galaxy-note-3/
Click to expand...
Click to collapse
thanks so much by the way. I greatly appreciate the assistance.
Alas, let me tell you my tale of woe. And just so you know, I have pretty much called myself every name in the book.
My wife and I both had S4's (I337). We have since moved on to other phones but both of us have kept our S4's. We have decided to give my daughter my wife's old S4 phone. Let me set the stage for you: the phone is (was) already rooted and I had CWM recovery on it. I was also using @iB4STiD 's GoldFinger ROM on both phones. They had the look of the S5. I decideded to go ahead and update the phone before we gave it to her. I went into the ROM and wiped the cache and did the "Install new ROM" box. Everything went smoothly. Well, to my horror, I had forgot the most crucial part -- putting the GoldenEye ROM onto the phone!! I tried to mount the SD card via USB and it would not mount. I then hit the back button and went too far back and the phone rebooted. To add insult to injury, several months ago, my wife's phone went thru a horrible boot loop. Come to find out, the power button was messed up. I had to open the phone up and completely remove the power button! So I cannot boot into recovery since I have no power button to hold.
So I thought I would try ODIN. If I pop the battery and put it back in, hold the volume down button and plug the USB cable in, I can get the phone to boot up and go into ODIN. But now, the ODIN files keep failing saying:
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I know, XDA. I should feel ashamed. But as a father I beseech you on behalf of my daughter to help me get out of this jam.
PS: If you need any information, my other S4 was flashed with the same ROM and is nearly identical to my wife's S4.
Any idea which bootloader version is on the phone?
audit13 said:
Any idea which bootloader version is on the phone?
Click to expand...
Click to collapse
Thankfully still MDL. I never updated the bootloader nor had to worry about safestrap.
I DID IT! I went to SamMobile, made an account, and downloaded the firmware for the phone. Flashed it with Odin and now I'm back in business.
Glad you got it working. I was going to suggest flashing a stock rom via Odin since your bootloader is unlocked.
audit13 said:
Glad you got it working. I was going to suggest flashing a stock rom via Odin since your bootloader is unlocked.
Click to expand...
Click to collapse
Well, now I have another problem. It loaded the original recovery. The recovery I had was CWM with touch since the phone does not have a working power button. I used ADB to log into recovery but I get hung up there without my power button to select the options. I then tried flashing a recovery with ODIN but again I fall into the Auth Fail. I had to go to work but I was reading about putting the recovery.img file in the root of the /sdcard and using Terminal Emulator to flash it in. Any thoughts on that? I also had tried fastboot but it said it was waiting for device and nothing happened.
Try flashing TWRP or CWM using Odin by doing this:
Open Odin, uncheck everything except f.reset time, flash recovery, when you see the word "reset" in the status window, remove USB cable, remove battery, replace battery, boot into recovery using button combination.
audit13 said:
Try flashing TWRP or CWM using Odin by doing this:
Open Odin, uncheck everything except f.reset time, flash recovery, when you see the word "reset" in the status window, remove USB cable, remove battery, replace battery, boot into recovery using button combination.
Click to expand...
Click to collapse
That's the part I'm having problems with. It fails during flashing the recovery. It will say FAIL (Auth). I will probably go ahead and try TWRP if I can find a .tar.md5 file of it. That's the other issue: the CWM file I downloaded was an .img file. I used a tool I found here on XDA to convert it to a .tar.md5 file but it still failed. If I can get a recovery that works via the touchscreen I'll be golden.
Use them latest twrp tar file. Then use twrp to flash the latest img file.
audit13 said:
Use them latest twrp tar file. Then use twrp to flash the latest img file.
Click to expand...
Click to collapse
Do you think this one will work even though it's originally for I9500 series? http://forum.xda-developers.com/showthread.php?t=2375908
Isn't this for the att: https://dl.twrp.me/jflteatt/
Cygwin can convert img to tar.
First of all let me say that I appreciate any help you guys can give me.
So I was trying to unlock to bootloader on my phone from KitKat 4.4.2 (NCG)
I was impatient and did something stupid.
I flashed the G900V_Firmware_PB1.tar.md5 file with Odin and repartitioned with the PIT file.
Of course it didn't work... Annnnnd I bricked... (Softbrick).
So after trying a few other things to no avail I panicked and booted into Stock Recovery Mode and did a full wipe/factory reset, wiped cache, then booted back into DL Mode and TRIED to flash the stock firmware to start over. The problem is the ODIN flash keeps failing and I don't know what to do.
I tried downloading the Stock Firmware from multiple sources and it keeps failing.
So I'm starting to freak out a little.
I can still successfully flash the G900V_Firmware_PB1.tar.md5 but that doesn't help me.
Any Help?
Enviola said:
First of all let me say that I appreciate any help you guys can give me.
So I was trying to unlock to bootloader on my phone from KitKat 4.4.2 (NCG)
I was impatient and did something stupid.
I flashed the G900V_Firmware_PB1.tar.md5 file with Odin and repartitioned with the PIT file.
Of course it didn't work... Annnnnd I bricked... (Softbrick).
So after trying a few other things to no avail I panicked and booted into Stock Recovery Mode and did a full wipe/factory reset, wiped cache, then booted back into DL Mode and TRIED to flash the stock firmware to start over. The problem is the ODIN flash keeps failing and I don't know what to do.
I tried downloading the Stock Firmware from multiple sources and it keeps failing.
So I'm starting to freak out a little.
I can still successfully flash the G900V_Firmware_PB1.tar.md5 but that doesn't help me.
Any Help?
Click to expand...
Click to collapse
@Bren123, I've passed this to @stang5litre earlier today and not sure if hes gotten with the user yet. What do you think he needs to do? I mentioned to the user via PM that he needs to do a backup of everything, which is including a Nandroid but didn't mention if did or didn't. If so, should try that first? Should've just unlocked the bootloader first with what ROM it's currently using and then go from there to update.....hadn't had time to get back to them....not home yet. Appreciate it guys!!
Enviola said:
First of all let me say that I appreciate any help you guys can give me.
So I was trying to unlock to bootloader on my phone from KitKat 4.4.2 (NCG)
I was impatient and did something stupid.
I flashed the G900V_Firmware_PB1.tar.md5 file with Odin and repartitioned with the PIT file.
Of course it didn't work... Annnnnd I bricked... (Softbrick).
So after trying a few other things to no avail I panicked and booted into Stock Recovery Mode and did a full wipe/factory reset, wiped cache, then booted back into DL Mode and TRIED to flash the stock firmware to start over. The problem is the ODIN flash keeps failing and I don't know what to do.
I tried downloading the Stock Firmware from multiple sources and it keeps failing.
So I'm starting to freak out a little.
I can still successfully flash the G900V_Firmware_PB1.tar.md5 but that doesn't help me.
Any Help?
Click to expand...
Click to collapse
Well to be honest I would just go to BPB1 here is the BPB1 Stock tar for odin (different than the one your using) https://www.androidfilehost.com/?fid=24438995911970571
And use this pit https://www.androidfilehost.com/?fid=24052804347765167 in the pit slot in odin could be in the options on the left
And flash then report back any errors if odin gives one
Bren123 said:
Well to be honest I would just go to BPB1 here is the BPB1 Stock tar for odin (different than the one your using)
And use this pit in the pit slot in odin could be in the options on the left
And flash then report back any errors if odin gives one
Click to expand...
Click to collapse
HORY SHET!!! :laugh:
That actually worked!
something so simple I didnt even think of it....
You gentlemen are life savers!
Now what? what are my next steps? I assume I have to root all over again?
@Bren123, thanks bud!!!! I figured you'd know of hand, as my notes amd crap are at home....which of course I'm not there yet....lol
Enviola said:
HORY SHET!!! :laugh:
That actually worked!
something so simple I didnt even think of it....
You gentlemen are life savers!
Now what? what are my next steps? I assume I have to root all over again?
Click to expand...
Click to collapse
Yeah re root and follow the bootloader unlock guide and you should be good to go