Database Info

[Q] Firmware upgrade encountered... zImage -> FAIL

Hey There.
I am trying to root + cmw my infuse 4G (ATT)
I was in download mode and tried to flash any of these: http://forum.xda-developers.com/showthread.php?t=1698367
But get the following error log and the phone is stuck "Firmware upgrade encountered..."
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> 2012.05.20-ODIN-Infusion-GB-Zen-CoreA-16.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> zImage
<ID:0/015> Complete(Write) operation failed.
<ID:0/015> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Odin is still recognizing it. Am i flashing the wrong tars???

ami2510 said:
Hey There.
I am trying to root + cmw my infuse 4G (ATT)
I was in download mode and tried to flash any of these: http://forum.xda-developers.com/showthread.php?t=1698367
But get the following error log and the phone is stuck "Firmware upgrade encountered..."
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> 2012.05.20-ODIN-Infusion-GB-Zen-CoreA-16.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> zImage
<ID:0/015> Complete(Write) operation failed.
<ID:0/015> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Odin is still recognizing it. Am i flashing the wrong tars???
Click to expand...
Click to collapse
Ok so i had to go back to the first kernel. how do I upgrade the kernel or can i new just install JB roms?
Now the infuse just sits at the samsung sign, i can get into download and CWM tho.
Can anyone help me please!
Now I got 2.3.6 on there, it says baseband I997UCLB, kernel 2.6.35-i997UCLB-CL977492, it boots, but CWM is distorted with green blue red lines, unreadable. I am outta luck...

You need to update the bootloader to gb Google it. You use Odin.
Sent from my dr0id running Liquid Smooth r0m

That messed up recovery means you need the GB bootloaders. Do some search and be careful!
Sent from my SGH-I997 using xda app-developers app

Hey thanks for replying. I've googled all night and there are so many different ones. I thought I had the right. Do I need to go back to froyo and the original boot loader? How do I know which one the right one is?

You need a stock uclb3 pack, either heimdall or odin.
The one-click heimdall includes bootloaders.. you would only have to run it once, then a second time but with "flash bootloaders" checked.
You can find everything on the iset thread stickied on thw development section.
Sent from my SGH-I997 using xda app-developers app

andros11 said:
You need a stock uclb3 pack, either heimdall or odin.
The one-click heimdall includes bootloaders.. you would only have to run it once, then a second time but with "flash bootloaders" checked.
You can find everything on the iset thread stickied on thw development section.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Yeah I looked through that thread, literally looked at the tons of links on there, information overload :silly:.
So do I have to return to froyo stock, now that I can't access CWM (distorted display) or can I just flash the the Heimdall UCLB3 GB (http://forum.xda-developers.com/showthread.php?t=152408) twice (2nd time with bootloaders) to get to GB from where I am right now? (system info says 2.3.6 UCLB3, but CWM is distorted)
Assuming that it works, can I dl a JB rom and flash it through CWM or do I have to put JB bootloaders on the phone, and then only flash JB?
Can I just follow GB to JB (http://forum.xda-developers.com/showthread.php?t=1878458)
I have flashed dozens of ROMs my mytouch, g note and gs3 and never had to deal with bootloaders. So, I apologize for all the noob questions...

Yup flash twice, 2nd time bootloader checked. Then follow jb flash instructions
Sent from my dr0id running Liquid Smooth r0m

eZdubzitmk4 said:
Yup flash twice, 2nd time bootloader checked. Then follow jb flash instructions
Sent from my dr0id running Liquid Smooth r0m
Click to expand...
Click to collapse
so not reverting back to froyo and froyo bootloaders but straight heimdall that shizzel to GB, and again GB bootloader?
I don't wanna hardbrick the device messing with the wrong bootloader.

I used Odin and flashed uclb or whatever, then I have a file that is bootloader only and flashed that
Sent from my dr0id running Liquid Smooth r0m

I finally got it on JB.
So for whoever is having the same issues, not being able to flash to GB, then to ICS:
What I did, and fixed it:
(just fyi, i was on froyo, and flashed UCLB3 once and couldn't get into recovery, giving me distortions, and a hear attack - my gf phone ! )
0) back up your EFS! I didn't have to restore it, but might as well do it (takes like 5 seconds), if you like me where recovery was messed up then you can't do a nandroid back up through recovery (SOL at that time)
1) Put the phone in Download Mode, use Heimdall UCLB3 (http://forum.xda-developers.com/showthread.php?t=152408)
First flash without bootloaders, flash until it goes through (it stopped a couple times on me, i had to put my phone into download mode again a couple of times. so dont give up. once it goes through flash again, but with bootloaders (which also stopped at uploading kernel, freaking out again) - so that I had to do multiple times as well, then I finally had GB on it with GB boot loaders (with red CWM).
Once you can boot GB nicely, download a JB ROM and put it on the sdcard, also add the gapps (only the ones in the thread worked, for some reason I couldn't flash the newest one...)
2) Then I used the following instructions from GB to JB (http://forum.xda-developers.com/show....php?t=1878458) to get the ICS boot loaders which got me CWM 5.x (blue CWM) (if you get "bad, and aborted" just re-download it and try it again)
3) Now that i got CWM 5.x to work I didn't even care to boot ICS, I could wipe the cache, davlik, data/factory and flashed (choose form sd card) my JB ROM, and flash gapps right away (not letting JB boot) once that was done. I wiped cache, davlik, and clicke don fix permissions and took out the SD card and then booted the phone. it rebooted twice, giving me another heart attack. but then it booted fine. (the first real boot of the JB rom takes forever, so chill.
Thats it! Now its shiney and new.
Update: I put my regular apps on this baby, for now just two: beautiful widgets and pandora. Now I have a weird problem of random reboots where my battery drops by 3 or 4%. Any ideas anyone?
For now I uninstalled those two apps, wait and see if the random reboots occur. any ideas?

Just to follow up on this the phone started rebooting more and more. So I sent it in for power button repair and now it's perfect! After 15 months of using it, the power button got stuck at times which forced reboots/boot loops
I hope this helps.
Sent from my SGH-T999 using xda premium

[Q] Soft Brick Can't Flash VRALEC bootchain

I rooted my phone the other day using this thread: http://forum.xda-developers.com/showthread.php?t=2046439. Then I tried to install MOAR rom and it didn't work, weird I thought. So I flashed my phone back to the recovery image I made before installing MOAR. However, my phone would start to randomly turn off. Well the screen would turn off and nothing would help to turn the phone back on unless I remove the battery and reboot. One of those time, it got stuck on the galaxy s3 screen and wouldn't go anywhere.
I tried reflashing a rom and it said that it couldn't mount my /system. So then I looked into this guide: http://www.androidauthority.com/galaxy-s3-i535-unbrick-soft-brick-125413/. Right now I'm trying to install the VRALEC bootloader and it gets stuck on the sbl2.mbn file. It's probably been like that for half an hour now. I've tried turning off odin and rebooting into download mode and trying different cables, but to no avail. Is there anything else that anyone can suggest me doing?
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRALEC.bootchain.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> sbl2.mbn
This is the Odin log. I'm using Odin 3.07

My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. Then use Ez-Unlock 1.2 to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk

Sandman-007 said:
My suggestion is to flash one of the rooted stock ROMs through Odin. There's a thread in android development that has rooted stock. Then when that's done boot up your phone. Then use Ez-Unlock 1.2 to unlock your bootloader. Make sure it's 1.2. Now use GooManager to flash TWRP. You are done! This is probably the easiest way to do this.
Thread: http://forum.xda-developers.com/showthread.php?p=33948598
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice. I tried it and for whatever reason it gets to NAND WRITE START after sbl2.mbn and then doesn't do anything else. Any chance I've actually hard bricked my device? Or is that term only used for phones that cannot boot into download mode? And what is sbl2.mbn?

Check md5 it may be a bad download.
Sent from my SCH-I535 using Tapatalk

Okay I checked the md5, it checked out. I tried a different file from that thread and it still halts when it gets to sbl2.mbn. This is really frustrating..

Another question. If I installed the Sprint MOAR rom instead of the Verizon MOAR rom, is there any chance I would still be able to boot into download mode? Because I might have done that. I think I googled galaxy s3 moar rom and got to the sprint page, but I'm not completely sure. I deleted the files I used because I was running out of space on my hard drive so I can't check them.

nike t said:
Another question. If I installed the Sprint MOAR rom instead of the Verizon MOAR rom, is there any chance I would still be able to boot into download mode? Because I might have done that. I think I googled galaxy s3 moar rom and got to the sprint page, but I'm not completely sure. I deleted the files I used because I was running out of space on my hard drive so I can't check them.
Click to expand...
Click to collapse
You could check your browser history. Btw, it sounds like you may need to reflash a pit file to get around all your issues. Idk if that will definitively resolve your issues though.
Sent from my SCH-I535 using Tapatalk 4

Awesome, I think that would be good to try. Is this the pit file I need? http://forum.xda-developers.com/showthread.php?p=30547929 and then would I just use one of the ROM's from the thread that Sandman posted? Or would I be using the stock ROM from samsung-updates?

nike t said:
Awesome, I think that would be good to try. Is this the pit file I need? http://forum.xda-developers.com/showthread.php?p=30547929 and then would I just use one of the ROM's from the thread that Sandman posted? Or would I be using the stock ROM from samsung-updates?
Click to expand...
Click to collapse
Try using one from samsung-updates, it will wipe /sdcard though which is the internal storage. To clarify, our phone is SCH-i535 (or d2vzw) so do not flash anything in Odin unless it's meant for our device.

Okay so I got the vzw-i535vbrmf1-20130627174111.zip file and the sch-i535-16gb.pit file. I just put the zip file in the pda spot and then the pit file in the pit section and then check repartition and hit start right? I'm just trying not to screw this part up because I know I'll hard brick it if I do.
edit: I'm guessing I need to unzip it to get the tar out first
Update: I tried the pit and vbrmf file and it wouldn't go past nand write!!!!... Could this be a motherboard issue?

nike t said:
Okay so I got the vzw-i535vbrmf1-20130627174111.zip file and the sch-i535-16gb.pit file. I just put the zip file in the pda spot and then the pit file in the pit section and then check repartition and hit start right? I'm just trying not to screw this part up because I know I'll hard brick it if I do.
edit: I'm guessing I need to unzip it to get the tar out first
Update: I tried the pit and vbrmf file and it wouldn't go past nand write!!!!... Could this be a motherboard issue?
Click to expand...
Click to collapse
Hmm, why is it getting stuck at that same point? Are you using the Samsung OEM cable? Able to try a different port or try this on another computer? And to clarify, you are pressing "Start" correct?

I wish I could tell you why it always stops at the same spot :/.I am using the OEM cable and tried different ports on the ccomputer and multiple versions of Odin. I haven't tried another computer though. I'll try that soon. And yes I am pressing start. I don't know what's happening

nike t said:
I wish I could tell you why it always stops at the same spot :/.I am using the OEM cable and tried different ports on the ccomputer and multiple versions of Odin. I haven't tried another computer though. I'll try that soon. And yes I am pressing start. I don't know what's happening
Click to expand...
Click to collapse
Maybe uninstall the Samsung drivers, reboot the computer, then put your S3 into download mode and plug it into your computer to force install new drivers. Once it installs new drivers, boot the phone back into download mode and try again with Odin. If its a laptop, keep it plugged into the wall outlet.

So I tried what you just suggested (uninstalling the samsung drivers and then rebooting the computer) and then also tried writing the stock image from a different computer. I'm getting the same problem. It will not get past the "NAND Write Start!!" part..
Would trying the debrick image on an SD card work for me? Or is that mostly just to be able to get the phone into boot mode and then from there flash the regular image? I'm so extremely confused why this is happening to my phone
EDIT: http://forum.xda-developers.com/showthread.php?t=2345831. I'm now reading this thread. It says that if flashing a pit file fails my phone is dead, and the motherboard is screwed. True story? I also know this is for Samsung Galaxy S2, but I thought that the same would apply to the S3
EDIT2: http://forum.xda-developers.com/showthread.php?t=1457458. Now I'm reading this thread. Could I have a NAND corruption? Again I know this says Galaxy S2, I'm just trying to get as much information as I can

Sorry for the double post, but I found this thread and I'm beginning to think that "nand erase all" might help. I have the official rom from samsung-updates for the vbrmf1 firmware. If I flash that while having the nand erase all checkbox checked does anything think that this would help me solve my problem? I read this thread: http://forum.xda-developers.com/showthread.php?t=1976695. There's also this thread that suggest the nand erase all: http://forums.androidcentral.com/sa...ot-flash-really-really-stuck-please-help.html.
If I do use nand erase, it'll be like the guide for soft bricking, but without flashing the bootchains. How necessary is it to flash those boot chains? Would I be able to try flashing them after I try flashing the stock rom? Or must the order of the soft brick thread by Hero an absolute?
Another question. What happens if I flash just a pit file without anything in the PDA section?

Okay, well I was able to get my recovery back after trying to flash my pit with the stock firmware checking nand erase all and repartition. In the end it failed because it said there was no pit partition.
However, now I'm unable to do a factory reset because it cannot mount system or cache. It also asks for a password when I first boot up the recovery. Anyone know what's going on?

nike t said:
Okay, well I was able to get my recovery back after trying to flash my pit with the stock firmware checking nand erase all and repartition. In the end it failed because it said there was no pit partition.
However, now I'm unable to do a factory reset because it cannot mount system or cache. It also asks for a password when I first boot up the recovery. Anyone know what's going on?
Click to expand...
Click to collapse
I just had all the issues you described on the latest TWRP when flashing a 4.4 ROM. Try the latest CWR. Format system and data using CWR 6.0.3.1
Sent from my SCH-I535 using Tapatalk

I tried CWR 6.0.1.2 and I was able to flash it, but I wasn't able to do a factory reset. It said that there was an error mounting /sdcard/.android_secure and it also says E format_volume: make_extf4fs failed on /dev/block/mmcblk0p17.

nike t said:
I tried CWR 6.0.1.2 and I was able to flash it, but I wasn't able to do a factory reset. It said that there was an error mounting /sdcard/.android_secure and it also says E format_volume: make_extf4fs failed on /dev/block/mmcblk0p17.
Click to expand...
Click to collapse
Use the latest version!
Sent from my SCH-I535 using Tapatalk

Alrighty, tried 6.0.4.3, no go. Thanks for all the help. I think the phone's done. It's gotta be some kind of nand problem. I'll probably send it in for JTAG or maybe try to transplant a motherboard from a different phone..

[Q] Unable to mount internal storage

Hello,
yesterday my Galaxy Note (n8010) suddenly rebooted (without me pushing any button) and since then, I could not boot into OMNIROM anymore.
Recovery is there (TWRP) but each time I try to do anything from flashing over whiping I get the same error.
"unable to mount internal storage"
Since this storage is basically needed for anything I am lost.
I cannot see this storage on my computer so I am not able to format it (since I believe, it could be corrupted).
I cannot use adb sideload because it does not start.
I cannot use the USB OTG because I cannot tick the box (just like the data box in TWRP).
I cannot flash a new ROM vio ODIN => error.
Nothing works. What can I do to get access to the internal storage?
Please help me. I spend the whole day with that and could not solve this problem.
PLEASE!!!

Did you had a 4.4.2 rom ? You got stuck with n8000 bootloader like me.
If you did, use odin to flash a stock 4.04, then you will get ota to jb, but only until xxucma5.
Sent from my GT-N8010 using Tapatalk

I'm afraid that you get the worst case scenario in flash memory storage....limited life time (extremely rare) & I hope I'm wrong.
Have you did way too many flashing/writing data to your internal memory?
Flash memory have a limited write cycle & if you did a huge number of write/delete/copy into you internal memory each day it can reduce your internal memory life time significantly.
If you want to try, use your microsd & place the AromaFM.zip (Aroma File Manager, just search here in XDA).
Open AromaFM by installing it like flashing your ROM (in this case nothing is installed, just running AromaFM).
Try to check if your internal memory is broken/corrupted & if it is still recoverable.

KoRoZIV said:
Did you had a 4.4.2 rom ? You got stuck with n8000 bootloader like me.
If you did, use odin to flash a stock 4.04, then you will get ota to jb, but only until xxucma5.
Sent from my GT-N8010 using Tapatalk
Click to expand...
Click to collapse
Unfortunately I cannot flash ANY Rom at all. Neither with ODIN nor with TWRP. Each time I try this I get an error.
Odin => Just did not do it and sais it failed.
TWRP => unable to mount data + internal storage (since data is on the internal storage it is logical that I am unable to mount data)
I tried to flash the original ROM (coming from Sammobile) but even that failed.
d4rkkn16ht said:
I'm afraid that you get the worst case scenario in flash memory storage....limited life time (extremely rare) & I hope I'm wrong.
Have you did way too many flashing/writing data to your internal memory?
Flash memory have a limited write cycle & if you did a huge number of write/delete/copy into you internal memory each day it can reduce your internal memory life time significantly.
If you want to try, use your microsd & place the AromaFM.zip (Aroma File Manager, just search here in XDA).
Open AromaFM by installing it like flashing your ROM (in this case nothing is installed, just running AromaFM).
Try to check if your internal memory is broken/corrupted & if it is still recoverable.
Click to expand...
Click to collapse
I just rooted my tablet 2 weeks ago. Hence, I did not flash/whipe that often. I only had ONE custom Rom until now (which was OMNIROM) and this Rom was updated 2-3 times since then.
I just tried to install / run AROMA via TWRP => Did not get it to run => unable to mount internal storage.
Is there any way that I can access this memory via my PC so that it tells me that the system is broken bla bla please format it bla bla and that I AM ABLE TO FORMAT IT? I cannot even see those 16Gigs anymore.
Thank you both for your help so far!!!!!!!!!!

Please try to give more information. Like what ROM did you had when the problem ocured. You said omnirom but was it 4.4.2, 4.1 or whatever android version was based on.
What stock firmware did you tried with Odin and post a screenshot with the error.
The more complete the information you give, the better, maybe someone will be able to help.
Sent from my Nexus 5 using Tapatalk

KoRoZIV said:
Please try to give more information. Like what ROM did you had when the problem ocured. You said omnirom but was it 4.4.2, 4.1 or whatever android version was based on.
What stock firmware did you tried with Odin and post a screenshot with the error.
The more complete the information you give, the better, maybe someone will be able to help.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I was on the highest OMNIROM (so 4.4.2).
The used the stock rom that was available via Sammobile "N8010XXUCMH2_N8010OXACMH2_DBT" => it was the only one available there.
I tried to copy a screenshot from TWRP onto the SD Card, but it was tried to be saved in "data" which is => unable to be mounted.
Nothing works

Like I said try a 4.0.4 stock with Odin. I'll get home in about 1 hour and tell you exactly what firmware if needed.
Sent from my Nexus 5 using Tapatalk

Please tell me also, where I get this ROM from, since I could not find any earlier version on Sammobile and I do not know other sources of Samsung Stock Roms.
Thank you! I give it a try.

Unfortunately I didn't find a n8020 4.0.4 stock firmware either
This is a screenshot of my odin error when trying to flash a jb stock firmware.

I just found one but the Download will take 2 more hours to complete...
But since you got an error, I think this will be the same with me.
What really makes me wonder is that ODIN via USB connection works find, but when I tick the USB box in the recovery it does not work. As if there was no USB connection, but THERE IS!
If the USB connection worked outside of odin there would be no problem to just format the internal storage. I think it could be repaired if I format it. It is very unlikely that the internal storage has a broken hardware, I think.
Any suggestions?

I get errors in odin only with 4.1.2, 4.0.4 works just fine. Do not atempt to format before you try a 4.0.4 stock in odin.
where did you found a stock 4.0.4 for n8020 ? give me the link, maybe i can provide a mirror for it

KoRoZIV said:
I get errors in odin only with 4.1.2, 4.0.4 works just fine. Do not atempt to format before you try a 4.0.4 stock in odin.
where did you found a stock 4.0.4 for n8020 ? give me the link, maybe i can provide a mirror for it
Click to expand...
Click to collapse
http://www.handy-faq.de/forum/samsu...ung_galaxy_note_10_1_offizielle_firmware.html
I really hope it works. I keep you updated later...hopefully with good news. Thanks for your time!

In the link you gave me there is no 4.0.4 for n8020, only 4.1.1 and 4.1.2. You can try a 4.1.1 if you didn't until now, but i don't know if it will work.
Be careful, you can try an n8000 4.0.4 but you will not have lte, and is a hell of a mix :
you will end up with a kitkat n8000 bootloader and a n8000 ics fimware on your n8020, so i don't recommend it.

KoRoZIV said:
In the link you gave me there is no 4.0.4 for n8020, only 4.1.1 and 4.1.2. You can try a 4.1.1 if you didn't until now, but i don't know if it will work.
Be careful, you can try an n8000 4.0.4 but you will not have lte, and is a hell of a mix :
you will end up with a kitkat n8000 bootloader and a n8000 ics fimware on your n8020, so i don't recommend it.
Click to expand...
Click to collapse
I have an n8010 and there is a 4.0.4. for it

Lol I was confusing threads i think. I'll come back to you with a private message for another link.
Edit:
You have a private message with an alternate link.

Download completed, and ODIN was able to flash it...
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N8010XXALH2_N8010OXAALH2_1015435_REV00_user_low_ship.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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
BUT! The tablet still has TWRP (although it has to be the Stock recovery according to Odin, it still not boots => stuck with "Galaxy Note"
TWRP still cannot mount Data
TWRP cannot be changed (I just tried to Install TWRP 2.4 and CWM afterwards) it still is TWRP 2.7.
I have no more ideas...I tried everything and was so happy, that there was a progress bar with the Stock Rom now, but although falshing it seemed to be a success according to odin, it was not.

Sorry to hear that. Strange that you still have twrp. I remember that mine didn't want to start at first after flashing 4.0.4 and I entered in recovery (the stock one) and did a factory reset, wipe data and dalvik cache. After that, the tablet booted normally. Get the firmware that I sent you in pm and try again, remember to wipe everything in recovery when finished flashing. I mean don't check auto reboot in odin and when you finished flashing disconnect the cable and boot in recovery.
Don't worry about csc, you will change that with csc changer from playstore before setting up everything (it does a factory reset)
I forgot to ask, when in download mode my tablet appears N8000 instead of N8010, how is yours ?
Sent from my GT-N8010 using Tapatalk

In Download Mode => n8010
Tried it again without autoreboot, instead I waited until odin was finished, unpluged USB, pressed power & vol+ but the same happened.
Odin showed "success" but still TWRP, still unable to mount data etc...
Well, when I leave TWRP it says SU is not installed (although I installed it via TWRP and ODIN multiple times...) could that be the reason?
If so, could you please tell me, what I should do in which order:
My suggestion is:
Download Mode
Connect to ODIN
Install SU via Odin => Autoreboot?
Install Stock Rom via Odin => no Autoreboot according to you
Go to recovery (which should be stock recovery now)
Whipe everything...

You do not have the same issue that I have, mine shows n8000 now and I have no idea how to get it back to n8010.
If you try to get stock I don't see the poit in using SU. You can try but use another version of SU, for me the .99 version didn't work, I had to use .96 to be able to use triangle away.
Try your way first, its less time consuming.
As for my way, it's worth a try, just use the file from my pm, that one gave me stock recovery at least.
Sent from my GT-N8010 using Tapatalk

Just tried your file. No success either.
Odin once again said it was a success but still TWRP bla bla bla
I believe I need to format the internal storage first and after that all my problems can be solved. But as I said, I cannot format it via TWRP => unable to mount internal storage and I cannot format it via my PC because I cannot find it there.
Can anyone help?

[Q] System software not authorized by Verizon error after attempting CM install

I've searched and searched for hours on this topic and still haven't had any luck, so maybe someone can tell me if my phone is recoverable. Here are the specifics.
At some point in the past (maybe ICS timeframe), I rooted my phone. I suspect that also unlocked my bootloader way back when because every time the phone booted, I'd see the unlock symbol and the word "custom".
Verizon just pushed out to me an OTA for 4.4.2. My phone was slow enough before, this didn't seem to improve it.
An acquaintance told me he had good luck with his Android phone performance by installing Cyanogenmod, so I figured I'd give that a try.
I started following the directions at the Cyanogenmod site (Install_CM_for_d2vzw).
After completing Step 5, the phone threw the "System software not authorized by Verizon" error.
I've tried all kinds of things, using Odin and trying to get back to something that will allow my phone to work.
Nothing has worked so far.
Running Windows 8.1 on my laptop. Drivers to talk to the phone seem good (must have worked enough to get me here).
Can anyone help at all? I'd be most grateful to get the phone to anything that will actually work.

mdesq said:
I've searched and searched for hours on this topic and still haven't had any luck, so maybe someone can tell me if my phone is recoverable. Here are the specifics.
At some point in the past (maybe ICS timeframe), I rooted my phone. I suspect that also unlocked my bootloader way back when because every time the phone booted, I'd see the unlock symbol and the word "custom".
Verizon just pushed out to me an OTA for 4.4.2. My phone was slow enough before, this didn't seem to improve it.
An acquaintance told me he had good luck with his Android phone performance by installing Cyanogenmod, so I figured I'd give that a try.
I started following the directions at the Cyanogenmod site (Install_CM_for_d2vzw).
After completing Step 5, the phone threw the "System software not authorized by Verizon" error.
I've tried all kinds of things, using Odin and trying to get back to something that will allow my phone to work.
Nothing has worked so far.
Running Windows 8.1 on my laptop. Drivers to talk to the phone seem good (must have worked enough to get me here).
Can anyone help at all? I'd be most grateful to get the phone to anything that will actually work.
Click to expand...
Click to collapse
Long story short, 4.3+ have permanently locked the bootloader beyond any current known XDA exploit. No AOSP once you have taken VRUCML1 4.3, VRUCNC1 4.3, and VRUDNE1 4.4.2 OTAs. Additionally, once officially on 4.4.2, you can not downgrade via Odin to 4.3. Being that this 4.4.2 OTA is new, there is not much in the way of resolving hard bricks for the 4.4.2. OTA.
My primary suggestion is to Odin flash this VRUDNE1 4.4.2 tar if you can boot into Download mode.

SlimSnoopOS said:
My primary suggestion is to Odin flash this VRUDNE1 4.4.2 tar if you can boot into Download mode.
Click to expand...
Click to collapse
Many, many, MANY thanks! That worked and I'm back in with a running phone.

mdesq said:
Many, many, MANY thanks! That worked and I'm back in with a running phone.
Click to expand...
Click to collapse
Glad that worked out for you!
Sent from my SCH-I535 using Tapatalk 4

I'm currently on the 4.4.2 ne1, but buggy and laggy. I tried factory reset. But still iffy, can I Odin the ne1 tar and it wipe the phone and start fresh?

theviper90210 said:
I'm currently on the 4.4.2 ne1, but buggy and laggy. I tried factory reset. But still iffy, can I Odin the ne1 tar and it wipe the phone and start fresh?
Click to expand...
Click to collapse
Yes, download VRUDNE1 tar from Sammobile.com or Samsung-updates.com and search for "sch-i535" and flash with Odin. The VRUDNE1 tar from these websites will wipe the phone clean.

(Edited wrong post)..Slimsnoopsos, thanks I'll do that!!!

SlimSnoopOS said:
Yes, download VRUDNE1 tar from Sammobile.com or Samsung-updates.com and search for "sch-i535" and flash with Odin. The VRUDNE1 tar from these websites will wipe the phone clean.
Click to expand...
Click to collapse
Slim, I downloaded the one from Sammobile.com and odin it and it completed sucessfull, phone booted back up not wiped!! it just re flashed 4.4.2 over my current 4.4.2, what did I do wrong to make it not wipe then flash? I want Wipe then reflash 4.4.2

SlimSnoopOS said:
Yes, download VRUDNE1 tar from Sammobile.com or Samsung-updates.com and search for "sch-i535" and flash with Odin. The VRUDNE1 tar from these websites will wipe the phone clean.
Click to expand...
Click to collapse
theviper90210 said:
Slim, I downloaded the one from Sammobile.com and odin it and it completed sucessfull, phone booted back up not wiped!! it just re flashed 4.4.2 over my current 4.4.2, what did I do wrong to make it not wipe then flash? I want Wipe then reflash 4.4.2
Click to expand...
Click to collapse
Ok also downloaded the one from samsung-updates.com and it also is a no wipe. So is there a ne1 tar, that will wipe before flashing?

theviper90210 said:
Ok also downloaded the one from samsung-updates.com and it also is a no wipe. So is there a ne1 tar, that will wipe before flashing?
Click to expand...
Click to collapse
Are you positive neither wiped your phone? How do you know they did not wipe your phone?
To answer your question, those websites are the two primary sources that supply stock tar files and their tar files have always wiped the phone on prior OTAs. No, I do not know of anywhere else to download them from. I guess you'll have to boot into recovery and do a factory reset from there. From a powered off state, hold: volume up, power, and home until it boots into recovery.

Positive, after both flashes phone booted right back into android with all my data still installed. No "setup wizard" just back to where I left off. And both times the flashes were successful. So weird

theviper90210 said:
Positive, after both flashes phone booted right back into android with all my data still installed. No "setup wizard" just back to where I left off. And both times the flashes were successful. So weird
Click to expand...
Click to collapse
And that's with:
-Odin 3.07
-auto reboot and f. reset are selected
-install the tar via the tab labeled "PDA"
-your S3 is fully booted into download mode (volume down, home, and power)
Correct?

It was Odin 3.09!?!
Tar via the ap tab (no PDA tab in 3.09)
These were the directions from the sites were the tar was. Could that really make a difference.
And yes in download mode. Odin will flash, reboot to the android with spinning stomach for a minute run a progress bar. Reboot into android and success. But no wipe?
---------- Post added at 08:53 AM ---------- Previous post was at 08:51 AM ----------
Kinda like a dirty flash

theviper90210 said:
It was Odin 3.09!?!
Tar via the ap tab (no PDA tab in 3.09)
These were the directions from the sites were the tar was. Could that really make a difference.
And yes in download mode. Odin will flash, reboot to the android with spinning stomach for a minute run a progress bar. Reboot into android and success. But no wipe?
---------- Post added at 08:53 AM ---------- Previous post was at 08:51 AM ----------
Kinda like a dirty flash
Click to expand...
Click to collapse
Download Odin 3.07 from here then let me know if this works. ONLY FLASH IN PDA. Do not flash in any other tab.

I'll have to try it when I get home from work. But I'll let u know thanks!!

theviper90210 said:
I'll have to try it when I get home from work. But I'll let u know thanks!!
Click to expand...
Click to collapse
That's cool, hope it helps out!

SlimSnoopOS said:
That's cool, hope it helps out!
Click to expand...
Click to collapse
Flash was success using 3.07 and PDA option, but still NO WIPE, phone booted normally with all data.
Here is the message data from odin. I dont notice any wipe command?
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I535VRUDNE1_I535VZWDNE1_I535VRUDNE1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> aboot.mbn
<ID:0/010> NAND Write Start!!
<ID:0/010> sbl2.mbn
<ID:0/010> sbl3.mbn
<ID:0/010> rpm.mbn
<ID:0/010> tz.mbn
<ID:0/010> boot.img
<ID:0/010> recovery.img
<ID:0/010> system.img.ext4
<ID:0/010> cache.img.ext4
<ID:0/010> NON-HLOS.bin
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Removed!!
<ID:0/010> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

The .tar files from Samsung are no wipe. They are exact copies of OTA including lock down.

prdog1 said:
The .tar files from Samsung are no wipe. They are exact copies of OTA including lock down.
Click to expand...
Click to collapse
That's a very surprising change from before

That's what I thought, so I just used kies and it will wipe and fresh install

Can't install anything on device

Hey guys,
I've been trying to figure this out for about the last 8 hours and have been hitting brick wall after brick wall.
I accidentally deleted all my system files on my phone when trying to install a new rom. I can no longer access TRWP recovery. Whenever I do I get the firmware upgrade encountered an issue error. I have plugged the phone into my computer but Kies can't connect to it. I have tried to reinstall 5.0 and I get sw rev check fail aboot fused 2 binary 1 error. I am currently downloading 4.4.2 to hope that this will work but I'm not sure on what to do now. Any help would be greatly appreciated.

Forget about Kies, you need to Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel). This will get you back on stock Lollipop. Once you get that done, post back and I can give you instructions on Odin'ing TWRP and installing a custom rom if you want to.

Ramer said:
Forget about Kies, you need to Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel). This will get you back on stock Lollipop. Once you get that done, post back and I can give you instructions on Odin'ing TWRP and installing a custom rom if you want to.
Click to expand...
Click to collapse
Downloading it right now. Will let you know what happens when I try to install it

kevorski said:
Downloading it right now. Will let you know what happens when I try to install it
Click to expand...
Click to collapse
I know I shouldn't have to ask this, but being as it's happened once before, I'm making an assumption that since you posted on a Sprint forum, you are on the Sprint network?

Ramer said:
I know I shouldn't have to ask this, but being as it's happened once before, I'm making an assumption that since you posted on a Sprint forum, you are on the Sprint network?
Click to expand...
Click to collapse
Yeah I'm on Sprint. Funny that you would have to ask that question

Ramer said:
Forget about Kies, you need to Odin'd the [ODIN][TAR][5.0] SM-G900P OA6 (Official!) - Full Restore (ROM, Modem, Kernel). This will get you back on stock Lollipop. Once you get that done, post back and I can give you instructions on Odin'ing TWRP and installing a custom rom if you want to.
Click to expand...
Click to collapse
So I downloaded the image and tried to flash it.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_G900PVPU1BOA6_G900PSPT1BOA6_CL3859396_QB3804569_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
This is the error I get when trying to flash it. Any ideas?

kevorski said:
So I downloaded the image and tried to flash it.
This is the error I get when trying to flash it. Any ideas?
Click to expand...
Click to collapse
Which OS are you running on PC? Also, use an MD5 checker to confirm good download.

Ramer said:
Which OS are you running on PC? Also, use an MD5 checker to confirm good download.
Click to expand...
Click to collapse
Windows 7 64bit I ran a checksum and they match

kevorski said:
Windows 7 64bit I ran a checksum and they match
Click to expand...
Click to collapse
I suspect I left out an important step, you need to be on the OA6 firmware to to install a lollipop rom and you may have wiped yours out. Odin this file, it's the OA6 firmware and KT TWRP.
Before you do this, if you have an extSD, this is the link for MOAR, you can try any rom you want, but let's attempt to get you going on a rom I'm familiar with. You need to copy the rom to your extSD beforehand. Download link is about half way down to OP.
So, to recap:
1. Download and copy MOAR to extSD and put back in your phone.
2. Odin OA6 firmware with TWRP. (Turn off auto-reboot, as you don't have a system to boot into)
3. After it PASSES, unplug from PC and pull the battery. Wait a few seconds and put battery back in and go into recovery mode (Volume UP, Home and Power).
4. If all goes well, TWRP is loaded and you can now navigate to you extSD and flash MOAR. (Clean install etc and remember, first boot can take about 20 minutes.

Ramer said:
I suspect I left out an important step, you need to be on the OA6 firmware to to install a lollipop rom and you may have wiped yours out. Odin this file, it's the OA6 firmware and KT TWRP.
Before you do this, if you have an extSD, this is the link for MOAR, you can try any rom you want, but let's attempt to get you going on a rom I'm familiar with. You need to copy the rom to your extSD beforehand. Download link is about half way down to OP.
So, to recap:
1. Download and copy MOAR to extSD and put back in your phone.
2. Odin OA6 firmware with TWRP. (Turn off auto-reboot, as you don't have a system to boot into)
3. After it PASSES, unplug from PC and pull the battery. Wait a few seconds and put battery back in and go into recovery mode (Volume UP, Home and Power).
4. If all goes well, TWRP is loaded and you can now navigate to you extSD and flash MOAR. (Clean install etc and remember, first boot can take about 20 minutes.
Click to expand...
Click to collapse
I still get the same error as above.

kevorski said:
I still get the same error as above.
Click to expand...
Click to collapse
Shoot. Sorry I'm out of ideas Maybe someone else can help?
Some other thoughts, Try updating your Samsung drivers. Reboot your PC. (Actually, try that first) Try a different USB port and a different cable. Make sure you see the blue COM:ID button in Odin.

Ramer said:
Shoot. Sorry I'm out of ideas Maybe someone else can help?
Some other thoughts, Try updating your Samsung drivers. Reboot your PC. (Actually, try that first) Try a different USB port and a different cable. Make sure you see the blue COM:ID button in Odin.
Click to expand...
Click to collapse
Hey Ramer,
Just wanted to let you know that I took the device to someone that does this for a living and found out that I had fried my bootloader. Didn't know if you wanted to know about the status. I have it up and running now with it rooted and running lollipop. Thanks for all the help that you provided.

kevorski said:
Hey Ramer,
Just wanted to let you know that I took the device to someone that does this for a living and found out that I had fried my bootloader. Didn't know if you wanted to know about the status. I have it up and running now with it rooted and running lollipop. Thanks for all the help that you provided.
Click to expand...
Click to collapse
Good to hear, but slightly confused. The bootloader (firmware) can be odin'd and if you installed the full OD3 stock tar it would have been included. Regardless, glad you're up and running.

Well now after I did a backup of the stock rom the guy put on it is locked up...again.