Database Info

[Stock Flash][CWM]ReRFS.Format.ROM.DK28 to revert back to RFS from ext4

The whole purpose of this ROM flash is to easily revert back to RFS from the ext4 file system without having to resort to odin. The Froyo DK28 Modem is a prerequisite. Please use a 3 finger salute to enter clockworkmod rather than quickboot recovery before flashing this.
***NOTICE*** THIS TOPIC IS NO LONGER SUPPORTED.
A new, more reliable ReRFS Format Stock ROM EC05 is available here:
http://forum.xda-developers.com/showthread.php?t=1027904
This is a stock Froyo DK28 odexed ROM, prerooted with some mods. Nothing fancy, but will get you to a trusted Froyo environment without any hassles. This can be flashed from either ClockworkMod versions 2 or 3, and will replace cwm3 with cwm2. It also flashes the stock DK28 kernel. This flash can prove incredibly useful for those experiencing problems during the ext4 conversion process, and those with Macs who don't have access to odin.
Warning: For some people, this hs failed. Symptoms included not being about to mount, umount, or format the stl blocks. The phone wouldn't boot past the samsungmobile.com logo. If this happens, an odin flash will fix it.
Edit: I did perform at least a dozen tests with both Quantom Rom 2.7 and Bonzai4All 1.1.4, using all clockworks. Also coming from both ext4 journaled and nojournaled. I couldn't get it to fail. So if this fails for you, please tell me as much as possible about the situation: was it nonbootable previously? What ROM were you coming from? What file system? Can you adb while the phone is in clockwork and type "mount | grep stl" (without quotes)? What is the output?
Note: This will erase all data, so perform a backup first before flashing. I intend to make another release as soon as I can find a way to reliably secure both a nandroid backup and restore from the script.
Hopefully this will soon be deprecated by a version of ClockworkMod 3 that can format and handle both the ext4 and RFS file systems.
Credits go to:
Noobnl for the original modded stock rom, supercurio for his voodoo lagfix sources that clarified the use of fat.format, and Dameon87 for parts of the Edify script. Noobnl once again for guidance and patience.

Great!
Would've helped me the first time I tried to flash (ViperRom..) and booted straight to CWM every time.
Sh0t from my Bonsai'd SPH-D700 using the XDA Android app.

No more windows, your a life saver. Thanks for this!
Sent from my SPH-D700 using XDA App

I used this and my screen would not get past the samsung screen on boot up.

redram38 said:
I used this and my screen would not get past the samsung screen on boot up.
Click to expand...
Click to collapse
what rom were you using before the flash? and what filesystem?

thanks needed this!

DRockstar said:
what rom were you using before the flash? and what filesystem?
Click to expand...
Click to collapse
Bonsai4All EXT4 1.14 was on RFS used CWM3 to convert. I probl messed up something somewhere. Ended up bricking the phone trying to get back to stock.

Updated original post with my latest test results... I couldn't get the flash to fail. Please continue to post your results here.
One interesting thing: I was able to use the ReRFS.Format.ROM to get back from a failed bonsai4all 1.1.4 install from cwm2.
Sent from my SPH-D700 using Tapatalk

I was running DK28 and CWM 2.5.1.0, I updated to CWM 3.0.0.5, and after the 3-finger salute, and the back-up creation, the phone began freezing at the Samsung screen. In my naivety, I removed my SD card from the back of my phone and proceeded to replace all the files on the SD card with the ones I had backed-up (since the install caused an SD card format)
And from there, my phone wouldn't do ANYTHING outside of the CWM 3 menu. I can't update, format, mount/unmount, backup, or restore. I have an original DK28 update.zip that I tried to use, it wouldn't work. I tried installing the Quantum Rom, since it's supposed to be compatible with the CWM3 file-type, no avail. Also tried to use the ROM you provided, everything runs, and it claims it's successful, but it won't boot past the CWM3 menu. And since the phone won't load past the menu, I can't get it into download-mode for an Odin flash. Odin recognizes the phone, but this is what I get:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection.
and it just sits, nothing happens. So, I'm out of options. I've really no clue what I'm doing with this whole Android development thing and I was taking a gamble by even attempting to update it, so I guess it's what I get for meddling where I shouldn't be meddling.

Okay, was able to finally get the phone into download mode, but only for a slit second. And, this was my Odin experience:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> param.lfs
<ID:0/005> Complete(Write) operation failed.
now, the phone won't turn on at all.

zdavidi said:
Okay, was able to finally get the phone into download mode, but only for a slit second. And, this was my Odin experience:
Added!!
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
param.lfs
Complete(Write) operation failed.
now, the phone won't turn on at all.
Click to expand...
Click to collapse
Take out your battery, and while holding down both the 1 key and the power buttons with one hand, replace the battery with the other hand. This should get you back into download mode.
Sent from my SPH-D700 using Tapatalk

DRockstar said:
...
Warning: For some people, this hs failed. Symptoms included not being about to mount, umount, or format the stl blocks. The phone wouldn't boot past the samsungmobile.com logo. If this happens, an odin flash will fix it.
...
Click to expand...
Click to collapse
Can you elaborate on the part where said "an odin flash will fix it"?
The only thing I knew how to do with Odin was flash the DK28 modem, which I did, but it did not change my situation - still stuck at the SAMSUNG splash...

I found SPH-D700-DK28-8G-REL.tar.md5 and flashed that and now I'm back in business - **phew**

I tried to flash it through clockwork but got the frozen samsung screen after.
I tried odin but odin needs to have a tar file i believe and this is zip.

I had that exact same problem when I did that..i was going around asking for help all I was getting im doing something wrong...just don't trust ext4 and cwm3 never did ... I ended up replacing my phone....
Sent from my SPH-D700 using XDA App

As wonderful as this sounds on paper and concept...its not working, will keep a eye out for any updates.
Sent from my SPH-D700 using XDA App

Cobaltikus said:
Can you elaborate on the part where said "an odin flash will fix it"?
The only thing I knew how to do with Odin was flash the DK28 modem, which I did, but it did not change my situation - still stuck at the SAMSUNG splash...
Click to expand...
Click to collapse
You gotta download the DK28 Md5 .tar file, then use that in Odin. Put it in the PDA section of Odin. You don't need the modem and pit file when your using the Md5.tar file, as it already has those 2 in it...
Sent from my SPH-D700 using XDA App

same happened to me, just sitting on boot screen.

I am having a very strange problem with OTA [NOT A NOOB][READY TO DONATE]

I tried pretty much everything on the internet before posting here.
My stock/no root phone started bootlooping. So I used Odin and root66.tar to get it back. Everything seemed to be good. After I got 3 updates:1) 30mb, 2) 60mb and 3) JB updated OTA. After 60Mb update my phone said Samsung and shows unlocked lock. After JB update my phone bootloops again.
I though it it was a bad update and reflashed stock no root 4.0.4 and OTA did the same thing.
I tried the gs3 tool to flash the recovery and it always fails.
I would appreciate any help.... I have been dealing with this non sense for the past 24h.

droidxrooting said:
I tried pretty much everything on the internet before posting here.
My stock/no root phone started bootlooping. So I used Odin and root66.tar to get it back. Everything seemed to be good. After I got 3 updates:1) 30mb, 2) 60mb and 3) JB updated OTA. After 60Mb update my phone said Samsung and shows unlocked lock. After JB update my phone bootloops again.
I though it it was a bad update and reflashed stock no root 4.0.4 and OTA did the same thing.
I tried the gs3 tool to flash the recovery and it always fails.
I would appreciate any help.... I have been dealing with this non sense for the past 24h.
Click to expand...
Click to collapse
Try to use Odin to flash back into stock not the root66 one as that is the rooted stock ROM.

jmxc23 said:
Try to use Odin to flash back into stock not the root66 one as that is the rooted stock ROM.
Click to expand...
Click to collapse
I did flash back to stock 4.0.4 and still get the same results. I was thinking If someone could provide the stock 4.1.1 update in a zip format. I wanted to flash it trough stock recovery to see the result.

I downloaded the JB 400mb update and installed it via recovery. Before I turned the phone on did factory reset and wiped the cache. I turned the phone on it boot loops. Does not make any sense at all. ICS works absolutely fine but JB fails to install properly.
This is a puzzle for me why it would do that.
Update: I was able to flash teamwin recovery though Ez-app from the play store. I still dont have luck with JB update. Update softbricked my phone 4 times now.

droidxrooting said:
I downloaded the JB 400mb update and installed it via recovery. Before I turned the phone on did factory reset and wiped the cache. I turned the phone on it boot loops. Does not make any sense at all. ICS works absolutely fine but JB fails to install properly.
This is a puzzle for me why it would do that.
Update: I was able to flash teamwin recovery though Ez-app from the play store. I still dont have luck with JB update. Update softbricked my phone 4 times now.
Click to expand...
Click to collapse
Are you flashing a custom recovery before the ota? If you run a custom recovery the ota wont take.

x714x said:
Are you flashing a custom recovery before the ota? If you run a custom recovery the ota wont take.
Click to expand...
Click to collapse
Everything was stock when I ran the OTA 2 times. The other 2 times I was rooted and still stock. Nothing I do works. I am not a noob. I have done some flashing in my life but this does not make sense at all.

droidxrooting said:
Everything was stock when I ran the OTA 2 times. The other 2 times I was rooted and still stock. Nothing I do works. I am not a noob. I have done some flashing in my life but this does not make sense at all.
Click to expand...
Click to collapse
What happens when you Odin flash the stock VRBLK3 tar?

SlimSnoopOS said:
What happens when you Odin flash the stock VRBLK3 tar?
Click to expand...
Click to collapse
Downloading COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship_NOWIPE_fixed.tar.md5 right now. I will flash it report it back.
Is there any reason that this file is 1.2GB?

droidxrooting said:
Downloading COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship_NOWIPE_fixed.tar.md5 right now. I will flash it report it back.
Is there any reason that this file is 1.2GB?
Click to expand...
Click to collapse
They're all large files due to TW. VRALG1 tar measures in at about 800 mb. The update from VRALHE to VRBLK3 was 400 mb so that's not unusual.

SlimSnoopOS said:
They're all large files due to TW. VRALG1 tar measures in at about 800 mb. The update from VRALHE to VRBLK3 was 400 mb so that's not unusual.
Click to expand...
Click to collapse
I tried the flash the VRBLK3 but it always fails not matter what I do. Any other suggestions?

Re: I am having a very strange problem with OTA [NOT A NOOB]
droidxrooting said:
I tried the flash the VRBLK3 but it always fails not matter what I do. Any other suggestions?
Click to expand...
Click to collapse
What error code do you get in Odin? What is the exact file name you're attempting to flash? Where are you downloading it from?
Sent from my SCH-I535 using xda app-developers app

SlimSnoopOS said:
What error code do you get in Odin? What is the exact file name you're attempting to flash? Where are you downloading it from?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
name: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship_NOWIPE_FIXED.tar.md5
downloaded from here : http://www.androidfilehost.com/?fid=9390214368362234406
code says failed and : <ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

droidxrooting said:
name: COMBINATION_I535VRBLK3_I535VZWBLK3_381038_REV09_user_low_ship_NOWIPE_FIXED.tar.md5
downloaded from here : http://www.androidfilehost.com/?fid=9390214368362234406
code says failed and : <ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Erase...
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you tried a different port? Also, is this with the OEM usb cable?

SlimSnoopOS said:
Have you tried a different port? Also, is this with the OEM usb cable?
Click to expand...
Click to collapse
Trying different port now. Yes the cable is OEM.
I was able to flash root66.tar with non oem cable just fine. Everything works but the phone does not like jelly bean update.
After I flashed CM10.1 the phone bootlooped again. I am restoring back to stock right now.

droidxrooting said:
Trying different port now. Yes the cable is OEM.
I was able to flash root66.tar with non oem cable just fine. Everything works but the phone does not like jelly bean update.
After I flashed CM10.1 the phone bootlooped again. I am restoring back to stock right now.
Click to expand...
Click to collapse
You unlocked the bootloader, flashed C10.1, and it bootlooped again? If you're back on rooted ics, you could try the VRBLK3 rooted rom by Beans. I'm having difficulty accepting the notion your phone will not run VRBLK3 but then again there was that thread where a few people were having issues with VRBLK3 bootlooping regardless of what they tried.

SlimSnoopOS said:
You unlocked the bootloader, flashed C10.1, and it bootlooped again? If you're back on rooted ics, you could try the VRBLK3 rooted rom by Beans. I'm having difficulty accepting the notion your phone will not run VRBLK3 but then again there was that thread where a few people were having issues with VRBLK3 bootlooping regardless of what they tried.
Click to expand...
Click to collapse
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas why it is failing? Do you think I can flash it trough cwm?

droidxrooting said:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas why it is failing? Do you think I can flash it trough cwm?
Click to expand...
Click to collapse
Well this one failed because its a rom that you flash in CWM or TWRP. Make sure you've unlocked the bootloader already.
Edit: You flash ".tar" or ".tar.md5" via Odin, .zip goes in recovery.

SlimSnoopOS said:
Well this one failed because its a rom that you flash in CWM or TWRP. Make sure you've unlocked the bootloader already.
Edit: You flash ".tar" or ".tar.md5" via Odin, .zip goes in recovery.
Click to expand...
Click to collapse
I think my phone is one of those which do not take jelly beam update. Now I have to send it to samsung to get it fixed. I did not buy it from verizon so I can not get it replaced.
I have tried pretty much everything that is on the internet. Nothing helps .... freaking ICS work just fine and every feature works on ICS.....
This does not make sense at all.

droidxrooting said:
I think my phone is one of those which do not take jelly beam update. Now I have to send it to samsung to get it fixed. I did not buy it from verizon so I can not get it replaced.
I have tried pretty much everything that is on the internet. Nothing helps .... freaking ICS work just fine and every feature works on ICS.....
This does not make sense at all.
Click to expand...
Click to collapse
It bootlooped again when flashing Beans custom rom via recovery?

SlimSnoopOS said:
It bootlooped again when flashing Beans custom rom via recovery?
Click to expand...
Click to collapse
Yes, nothing works but the stock ics. the root66.tar works and stock no root works. Other than that everything make the phone to boot loop. I have the other GS3 and that works absolutely fine. I can not under stand why in the hell this would not accept JB update.

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