Develop Bugs

Verizon stock ROTO files minus the Data partition

*** EDIT *** Sorry these files are no good so I'm removing the links. There are a few other threads that will provide the help and files needed
I have used this thread to restore my Tab and it worded perfectly
http://gizmoninja.com/2011/04/21/how-to-root-latest-samsung-galaxytab-verizon-update-ec02/
I've had a few problems up to this point but now having these files has helped me feel more secure about recovering back to a completely fresh Verizon stock image including reverting to rfs from ext4.
Ok, here are the files create from a ROTO back-up minus the data. This was completed on a brand new Verizon G-Tab with only temp root. I know quite a few people may need this so share as needed.
Includes the following files:
boot.bin
cache.rfs
dbdata.rfs
efs.rfs
factoryfs.rfs
ldb.db
modem.bin
param.lfs
param.rfs
pit.pit
bls.bin
zImage
Hope these help

rjansen110 said:
I've had a few problems up to this point but now having these files has helped me feel more secure about recovering back to a completely fresh Verizon stock image including reverting to rfs from ext4.
Ok, here are the files create from a ROTO back-up minus the data. This was completed on a brand new Verizon G-Tab with only temp root. I know quite a few people may need this so share as needed.
Includes the following files:
boot.bin
cache.rfs
dbdata.rfs
efs.rfs
factoryfs.rfs
ldb.db
modem.bin
param.lfs
param.rfs
pit.pit
bls.bin
zImage
http://rapidshare.com/files/44808085...GTab-Stock.zip
or
http://dl.dropbox.com/u/21215221/Verizon-GTab-Stock.zip
Hope these help
Click to expand...
Click to collapse
Just curious, did you happen to repartition using the PIT file?

Nope. But from what I have read, it should work. We were just missing the actual file to do it...
Let me know how it works if you do it

rjansen110 said:
Nope. But from what I have read, it should work. We were just missing the actual file to do it...
Let me know how it works if you do it
Click to expand...
Click to collapse
Hmm, ok. I had read that once you converted to EXT4 that you needed to repartition to get back to RFS. I'm not saying that's true, just that I saw it somewhere.
I'll try to flash first without repartitioning, then repartition if that doesn't work.

The reason I said no, is because I have not used these to recover yet.
I did have the issue where I needed to repartition and couldn't find the file anywhere. So I ended up returning my device for a new one. Then did this pull so I could recover if I got back to that situation again.
By all means , use the pit file. that's what it's there for

rjansen110 said:
The reason I said no, is because I have not used these to recover yet.
I did have the issue where I needed to repartition and couldn't find the file anywhere. So I ended up returning my device for a new one. Then did this pull so I could recover if I got back to that situation again.
By all means , use the pit file. that's what it's there for
Click to expand...
Click to collapse
Gotcha. Well, I'm charging my tab now, so we'll see what hapens.

Ok, i'm having issues with the repartitioning.
I have all the files in the right spot, but when I hit start, I get "failed to retrieve config descriptor"
Anyone get this before? Any fixes?

I haven't seen or heard of that error. Might want to PM Roto to see if he has any ideas

rjansen110 said:
I haven't seen or heard of that error. Might want to PM Roto to see if he has any ideas
Click to expand...
Click to collapse
I can't, he's set to not receive PMs
Someone mentioned that there's a way to boot into a secondary bootloader and try flashing in the download mode that way, but I don't exactly know how to do that.
I'm THIS close to sending this thing into samsung for a warranty repair.

Well you got further along then I did when I was in your shoes. I sent mine back and got a new one. That's why I created the Roto backup...
I saw what the other guy said and was confused also. Never to that before so I wouldn't know how to start...

rjansen110 said:
Well you got further along then I did when I was in your shoes. I sent mine back and got a new one. That's why I created the Roto backup...
I saw what the other guy said and was confused also. Never to that before so I wouldn't know how to start...
Click to expand...
Click to collapse
I just created a repair ticket with Samsung, I'm tired of dealing with this.
I'm seriously considering selling the Vzw tab and getting a GSM tab. It seems so much easier to fix if it breaks.

It does seem there is a lot more support for GSM.
BTW, I haven't had any issues with my new device and I'm rooted, running CWM recovery and Klean ROM.

rjansen110 said:
It does seem there is a lot more support for GSM.
BTW, I haven't had any issues with my new device and I'm rooted, running CWM recovery and Klean ROM.
Click to expand...
Click to collapse
That's what I thought too
It may turn out that my device had a hardware problem, but who knows. I'll be sending it out tomorrow and report back when I get my new one.
One thing that I did find weird though. I was letting the Samsung screen stay on for a while when it first was "bricked" and eventually there was an audible voice telling me something about being "unable to mount data" or something close to that. Anyone else ever hear that?

Man you're full of firsts... I haven't heard that one and I let mine sit for an hour one time out of frustration
But now that I think about it, it was the /Data partition that couldn't be mounted in any of the recoveries once I got to that point so I can kind of understand, just not hearing the voice. Could it be that was in your head, LOL

Coolsaber57 said:
That's what I thought too
It may turn out that my device had a hardware problem, but who knows. I'll be sending it out tomorrow and report back when I get my new one.
One thing that I did find weird though. I was letting the Samsung screen stay on for a while when it first was "bricked" and eventually there was an audible voice telling me something about being "unable to mount data" or something close to that. Anyone else ever hear that?
Click to expand...
Click to collapse
Yup I had that when I was trying to restore my tab. This means your partition table is messed up and you have to repartition with pit file.
Sent from my PC36100 using Tapatalk

I used the files in this post to return to stock and I now have a brick. Has anyone succeeded in flashing these.

Nobody knows for sure, but bootloaders, modem and pit file in this post seem to be corrupted. There's no existing stock firmware for VZW tab like for Sprint one. No leaks from Verizon

roadhero said:
Nobody knows for sure, but bootloaders, modem and pit file in this post seem to be corrupted. There's no existing stock firmware for VZW tab like for Sprint one. No leaks from Verizon
Click to expand...
Click to collapse
Here is how to restore Verizon TAB http://www.droidforums.net/forum/sa...84-how-restore-vzw-galaxy-tab-stock-dj11.html
This thread must be closed. I flashed files from first post and bricked my unit.

The thread on droid forums lacks modem, bl and sbl files though, a lot of guys in this forum need them. But agree, these files in this topic are corrupted.

Updated OP to remove the link to the files and added a link to a thread that helped me restore recently.

[HELP] Bricked my S3 i747M.

Hey guys, im new to the scene, and while fiddling around with my Galaxy S3, i have managed to brick it! Here is what happened.
I rooted the phone using a tutorial from here:
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Everything worked fine and the phone successfully rooted. But than i came across roms ... and i found a tutorial that told me how to install CyanogenMod 9:
http://forum.xda-developers.com/showthread.php?t=1778165
I tried to follow the instructions, but i would get (Error 7), and i realized that this tutorial instructed me to install the ClockworkMod Recovery version 5.8.4.7. So i downloaded the file from ClockworkMod's website, and it was in a .img format. When i had rooted my phone and installed ClockworkMod i used a .tar version via Odin, and this time i had a .img. After going through many tutorials, i found someone that showed how to install the .img varient via Android Terminal Emulator. So i followed the instructions:
http://forum.xda-developers.com/showthread.php?t=1363132
After i was finished following the instructions i rebooted the phone. And boom, it would not turn on. I tried all variants of holding the external buttons etc. Than i plugged the phone into a Windows PC. and the phone shows up in device manager as "QHSUSB DLOAD". So after tirelessly researching, i finally found the drivers for this and installed them. And know the phone shows up in Odin as COM10 in yellow. So i tried to flash the stock Image. I fire up Odin, select PDA, than the stock image, and click start. This is all that happens in the "Message Log":
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
(I have attached a screenshot of the above)
Please guys, i just got the phone and now it is bricked, any help would be greatly appreciated. Thanks!!

First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!

Hi, Thanks for your reply. I tried using a "Jig" and it did not put the S3 into download mode. LIke i said previously. When the S3 is connected to my PC it shows up as "QHSUSB DLOAD". And no Samsung drivers would work with it. I had to research and find the drivers that finally worked and allowed Odin v1.85 to see the phone as "COM10", and i select the ROM under the PDA and click the "Start" button. But than it does not go past SetupConnection. I thought maybe the "Jig" was faulty and didnt work, but i tested it with another working Samsung Galaxy S2, and it worked exactly as it was supposed to. Should i still try your suggestion or is it pointless?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse

Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
I would get ahold of Josh at www.mobiletechvideos.com as it sounds like jtag might be required.

Hey, Thanks for the info. But the image i flashed via the Android mobile terminal app on the phone, i was flashing a ClockworkMod v5.4.8.1, that was made for the AT&T i747 (I have the Bell i747M, which i am told is the same thing?) , is that the bootloader? I know someone here that is local that does the jTag repair. But im not sure if the problem i have is in relation to the bootloader. Please let me know. As the phone still does show up when connected to the PC.
neubauej said:
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
Get ahold of Josh at as it sounds like jtag might be required.
Click to expand...
Click to collapse

I tried your solution. The phone when connected to the PC with does not show up in Odin 3.07 (Correct version for my phone, from your link), But if i turn on Odin 1.85, the phone shows up fine in that as COM10 in yellow. So does my phone need a jTag? Samsung Canada told me to send the phone in for service and they will reset it and send it back. At the moment the phone does not turn on or go into download mode, and when connected to the computer it shows up as HS-USB QDLoader. So my question is: If i send it to Samsung, will they discover that i have Rooted it and void my warranty and not fix the phone?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse

If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
As for your bootloaders, you pushed a custom recovery that failed, corrupted, or was an incorrect application. The recovery lies in the bootloader..
If it doesn't power up, won't go into download mode, and Odin won't flash it I'd say its jtag or send it to sammy time.

I see, well i do not care if they charge me anything. Money is not an issue, Ok well i just got the email from Samsung with the shipping label. Thanks for your information.
neubauej said:
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
Click to expand...
Click to collapse

Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.

After doing some more research, i found that another person with a different Samsung phone. Followed the same instructions to flash ClockworkMod via Android Mobile Terminal using the same instructions i did and got the same problem. On his post somebody told him that the flash was made to the wrong partition or something like that. So ... Lesson for next time. READ EVERYTHING BEFORE TRYING IT!
neubauej said:
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
Click to expand...
Click to collapse

Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium

pchemerys said:
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app

Frowben said:
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ah yes..that makes sense. That would pooch the phone. As for cwm it appears I was mislead as I read on few posts that newest versions don't work or not recommended for Canadian variant but it appears u might be right and I'm now seeing more and more report that it is installable. I'll have to check it out. Thanks

You flashed a recovery for the LG Thrill 4G. At what point in time did you assume it was the same phone as the I747M? You have bricked your phone. It needs JTAG service. Samsung will probably cover it under warranty, or you can pay someone that has the equipment to do it. You have no other options at this point. When you get it back from repairs, make sure you only flash AT&T/Bell/Telus/Rogers I747(M) software to the phone....

Ya i got the phone back from Samsung after waiting 3 weeks. They had to change the motherboard on the phone. Yes, it was the wrong instructions i followed which screwed me over! Since than i re-rooted how i did the first time i got the phone. Just a few days ago i saw the new CyanogenMod 10 M1 Rom, which i wanted to install. And again like last time in order to install it i had to upgrade my CWM to the newest version. This time i did not rush into it like last time and consulted with my buddy who is an expert in Android. The problem i had last time was i downloaded the new CWM in an .img file, and this time i ended up finding the newest CWM in a .tar and used Odin to flash it successfully. Than i just installed the rom and was good to go. My main reason for wanting to install a custom rom was i was getting absolutely HORRIBLE battery life from my S3. I ended up buying a juice pack which greatly helped me out. But now that i have CM10 my battery life is phenomenal, + the juice pack i now go maybe 2 days without having to charge. Now my sister who has the Wind Mobile S3 T999V wants me to upgrade her rom to the same as mine. I have found the T-Mobile CWM for her phone, and all the relevant software, but i am still hesitant to install the CWM on her phone. The T-Mobile CWM 6.0.1.2 is compatible with the Wind Mobile S3 T999V right? Or do i have to use a different version?

just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices

jefferson9 said:
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
Click to expand...
Click to collapse
Yes, i know that. I realized after i had done everything that the instructions where for another phone. Now im trying to find the CWM 6.0.1.2 for my sister phone T-Mobile S3 T999V that is in a .tar file already. Any suggestions on where i can get it?

I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium

JB calhoun said:
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Ya for my sisters phone i have that version as a flashable tar, however to install CM 10 M1 i need to install CWM 6.0.1.2.

Did u try rom manager
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] JB back to GB problems

Hey and hello here!
I'm rather new to flashing, etc. and have tried the JB leak. Great job on you guys there!!
Now I want to return to GB, also found a quite easy work thru by michal_ag, and flashing back to his Russian stock worked like a charm. Unfortunately I cannot install any GB version after that. Odin tells me, that I'm trying to flash a modded modem version and aborts (tried various stock roms from sammobile).
Soooo I'm back to JB, but I miss using bluetooth in a convenient way, not having to restart my phone each time to enable it for deep sleep, and the lack of NFC is a bit of a bugger, too.
Any suggestions for getting back to I8160PXX/DBT/LK2? Sorry I'm new and not yet allowed to post in the dev section cos of that.
Best regards,
primewell

primewell said:
Hey and hello here!
I'm rather new to flashing, etc. and have tried the JB leak. Great job on you guys there!!
Now I want to return to GB, also found a quite easy work thru by michal_ag, and flashing back to his Russian stock worked like a charm. Unfortunately I cannot install any GB version after that. Odin tells me, that I'm trying to flash a modded modem version and aborts (tried various stock roms from sammobile).
Soooo I'm back to JB, but I miss using bluetooth in a convenient way, not having to restart my phone each time to enable it for deep sleep, and the lack of NFC is a bit of a bugger, too.
Any suggestions for getting back to I8160PXX/DBT/LK2? Sorry I'm new and not yet allowed to post in the dev section cos of that.
Best regards,
primewell
Click to expand...
Click to collapse
Yeah, well maybe its because you have I8160P and good thing you're not allowed to post on dev... because this does not belong there.

Dr01nE said:
good thing you're not allowed to post on dev... because this does not belong there.
Click to expand...
Click to collapse
I actually wanted to reply on michal's thread.
Dr01nE said:
maybe its because you have I8160P
Click to expand...
Click to collapse
I'll take it as a "bummed cos you've got the nfc version, told you so newb, hahaha, etc" situation?
I took the chance, since I know some ppl flashing a 8160P to JB, and it worked fine. So I figured I might try the same non-P way to revert, since there is IMHO nothing at all to be found specificly for the 8160P.

primewell said:
I'll take it as a "bummed cos you've got the nfc version, told you so newb, hahaha, etc" situation?
I took the chance, since I know some ppl flashing a 8160P to JB, and it worked fine. So I figured I might try the same non-P way to revert, since there is IMHO nothing at all to be found specificly for the 8160P.
Click to expand...
Click to collapse
Nope. I didn't mean it that way.
As for the revert, you can try to find a full firmware for I8160P. the one that has CODE_REV...blahblahblah & CSC_REV...blahblablah. That's the only thing I can think of.
Oh wait, can you post what Odin shows?

I've been looking last night for a P firmware that consists out of two parts. I concluded that from michal's thread, too (that's why he took the Russian version, cos only fw that has more than one package, blablalba).
In Odin it goes through all the operations as it should (flashing cache.img, etc) but when it gets to modem.img it gives:
Code:
...
<ID:/003> modem.img
<ID:/003> Complete(Write) operation failed
<OSM> All threads completed. (succeed 0 / failed 1)
And on the hand held screen it says in red "modem custom", the mobile freezes, and revival increases the flashcounter by one. I'm back to JB for the day and am downloading various fw in hope of getting one with multiple files...

UPDATE: Have been looking around, and so far the fw for 8160P is always a single data file. Szaby59 posted a pre-rooted fw for 8160P, as far as I can tell it includes the PDA and CSC file by soraxx.
I'll try and get hold of a file package and try to flash back to GB. Maybe it'll work. Up to now my Ace 2 NFC seems pretty brick-safe. At least I wasn't able to brick it, and I've played about with it more than one should. But it's really sad, that the 8160P is a low "really low" activity device - it bears such goodness in its tech

Hey. This could be a stupid suggestion but why dont you try and take modem from 8160P gw and replace XXLK6 modem.. Just curious
Sent from my GT-I8160 using xda app-developers app

Dr01nE said:
Hey. This could be a stupid suggestion but why dont you try and take modem from 8160P gw and replace XXLK6 modem.. Just curious
Click to expand...
Click to collapse
I thought about that myself, but I'm axious that that could actually brick my phone in the sense of being basically unflashable. And I do not now how to create/compile a new md5-file. With what application should I do this? Winrar and 7zip only allow viewing and extraction.

after downgrade + flashing stock rom - no baseband
primewell said:
I thought about that myself, but I'm axious that that could actually brick my phone in the sense of being basically unflashable. And I do not now how to create/compile a new md5-file. With what application should I do this? Winrar and 7zip only allow viewing and extraction.
Click to expand...
Click to collapse
JFI, I have an i8160P like you an had flashed it to JB. Tried to downgrade with the russian firmware and the same faults. Can't flash any other firmware afterwards. With Odin 3.07 I was able to flash an i8160 Firmware but now I've no baseband (Phone: unknown) and no IMEI. Unfortunately i haven't saved the /efs.
Now I'm looking around for a way to get baseband back.
Sorry for my english. It's 30 years ago i had it at school.

Help unbrick note 3

I am not new to the rooting scene, however I have a problem that I can't seem to figure out. I've been reading now for the past 2 days, tried several things and still can't get this resolved. I've never had any issues in the past with odin and rooting samsung phones before, including ones with locked bootloaders. However, I've met my match. I tried following the tutorial listed on this site for rooting the samsung note 3 from tmobile. I watched the video and followed along with the files listed here
http://forum.xda-developers.com/note-3-tmobile/#root
My problem is as follows: I tried rooting with odin, installed kies for the usb support but halfway through the root process I get the big RED FAILED! phone's progress bar stops and it hangs. I though this was strange and never encountered this before. I then tried repeating the same process and same results, however this time around I am only able to bring the phone into "odin" mode "download" and not the original stock rom.
At first I was getting the original "the firmware encountered an upgrade issue" and couldn't bypass this unless I opted for download mode. I've tried the same steps to "unbrick" via oden with stock tmobile firmware for this phone and yet it yields the same results, big exclamation failed on odin. I then tried the process with the .pit file to partition that I found online somewhere and that fails too. My note starts up now, but stuck at the samsung galaxy note 3 screen. I've tried several versions of odin, switching usb cables, usb ports and I am unable to root this phone or even get it unbricked! i've read extensively here and can't seem to find a solution to my problem. Can someone PLEASE point me in the right directions?? BTW, I am using a mac with VMWARE, i've never encountered any issues with vmware in the past while running windows 8.
Phone says the following:
Once in download mode my phone says the following:
ODIN MODE
PRODUCT NAME: SW-N900T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
QUALCOM SECUREBOOT: ENAMBLE
RP SWREV: S2, T2, A2, A3 P2
WRITE PROTECTION: ENABLE
UOC START
and I get these results from ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Try a new computer...
Sent from my SM-N900T using Tapatalk

dobbs3x said:
Try a new computer...
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
You think a new computer might solve this?

Try using Heimdall. That should work natively on your Mac.
You can read about it and download it from here http://forum.xda-developers.com/showpost.php?p=7679702&postcount=1

xmatic said:
You think a new computer might solve this?
Click to expand...
Click to collapse
Actually, he might be right. But you may need to just try a different USB port instead of a new computer.
I had a problem with Odin failing when I tried to install a ROM. I remembered something about there being problems with certain USB ports, so I switched it to a port on the front of my PC and it worked. This was despite the fact that Odin recognized the device in the first port.
Hope that helps.
TL;DR: Just read through your post again and saw that you already tried that. Sorry.

dragonstalker said:
Try using Heimdall. That should work natively on your Mac.
You can read about it and download it from here http://forum.xda-developers.com/showpost.php?p=7679702&postcount=1
Click to expand...
Click to collapse
I use Odin all the time for rooting Samsung phones. Never used Heimdall, but love the idea of using it in my Mac.
Does this works with Note 3?

dragonstalker said:
Try using Heimdall. That should work natively on your Mac.
You can read about it and download it from here http://forum.xda-developers.com/showpost.php?p=7679702&postcount=1
Click to expand...
Click to collapse
Thanks for all the help, I was able to install the original rom back and restore the phone to it's original state through my mac side. I have downloaded Heimdall, but what are the steps necessary to root my phone? I only see an option to load package, flash or create package but it seems it's requiring a "PIT" file. Can anyone point me in the right direction of which particular file I need to root this note 3 with Heimdall? Thanks!

xmatic said:
Thanks for all the help, I was able to install the original rom back and restore the phone to it's original state through my mac side. I have downloaded Heimdall, but what are the steps necessary to root my phone? I only see an option to load package, flash or create package but it seems it's requiring a "PIT" file. Can anyone point me in the right direction of which particular file I need to root this note 3 with Heimdall? Thanks!
Click to expand...
Click to collapse
CF_Autoroot does not work with Heimdall? I have yet to use it eventhough i have a Ubuntu Box. So i'm curious to know also.

dragonstalker said:
CF_Autoroot does not work with Heimdall? I have yet to use it eventhough i have a Ubuntu Box. So i'm curious to know also.
Click to expand...
Click to collapse
The auto root is not working for me period! it bricked my phone 3 times already and I had to unbrick. It was a pain in the butt. All ulitmately due to odin failing with the flashes. I've tried different versions of Odin, different versions of windows within vmware and different usb slots/cables. All fail! Is there another way to root this phone guys! Please help? I am on a mac. Obviously Odin is now out of the question.

xmatic said:
The auto root is not working for me period! it bricked my phone 3 times already and I had to unbrick. It was a pain in the butt. All ulitmately due to odin failing with the flashes. I've tried different versions of Odin, different versions of windows within vmware and different usb slots/cables. All fail! Is there another way to root this phone guys! Please help? I am on a mac. Obviously Odin is now out of the question.
Click to expand...
Click to collapse
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip

dragonstalker said:
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip
Click to expand...
Click to collapse
That is what I used but get on a PC. Go over a friends house and borrow his.
TWEAKED N3

dragonstalker said:
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip
Click to expand...
Click to collapse
My apologies, I didn't think I was yelling, and I didn't mean to be ass. I am just a little frustrated because i've never had any issues before in the past rooting a phone, especially a samsung phone via Odin. I'll try this as I was using the n900t auto root. I'll advise how it goes.

xmatic said:
My apologies, I didn't think I was yelling, and I didn't mean to be ass. I am just a little frustrated because i've never had any issues before in the past rooting a phone, especially a samsung phone via Odin. I'll try this as I was using the n900t auto root. I'll advise how it goes.
Click to expand...
Click to collapse
OH no. i was saying don't yell at me for asking the question.
If you still have issues pm me. i'll give you my number and we'll walk thru it.

BACARDILIMON said:
That is what I used but get on a PC. Go over a friends house and borrow his.
TWEAKED N3
Click to expand...
Click to collapse
I failed again, can't get it to work. I wouldn't be surprised if it's a vmware thing. I just can't find anyone with a pc around.

xmatic said:
I failed again, can't get it to work. I wouldn't be surprised if it's a vmware thing. I just can't find anyone with a pc around.
Click to expand...
Click to collapse
Sorry bro I just don't know enuff about Mac products to point you in the right direction.
TWEAKED N3
---------- Post added at 11:05 AM ---------- Previous post was at 10:48 AM ----------
dragonstalker said:
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip
Click to expand...
Click to collapse
https://plus.google.com/app/basic/stream/z12yzpirzqf4srxw204cjl1aoor5ezninhc
He just updated the apps like 50 min ago
TWEAKED N3

xmatic said:
You think a new computer might solve this?
Click to expand...
Click to collapse
This is the same exact problem I'm having. Also not new to rooting.
Guess what. I'm also trying on a mac with VMWARE. Makes me wonder. But I've rooted so many times this way. What makes this android any different. Tomorrow I'll try making a boot able window HD.
Sent from my SM-N900T using xda app-developers app

starscrean said:
This is the same exact problem I'm having. Also not new to rooting.
Guess what. I'm also trying on a mac with VMWARE. Makes me wonder. But I've rooted so many times this way. What makes this android any different. Tomorrow I'll try making a boot able window HD.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Yeah, i've given up with rooting via VMWARE and Odin, it just doesn't work, period. I've tried to virtual machines, a win 8 and win 7 all with the same results. I have a feeling it's VMware, I am trying parallels now and I'll post updates afterwards. Thanks to everyone for contributing. BTW, does anyone know if it's even possible to root with Heimdall?

Update:
I was able to root fine without any issues, it seems the issue was ONLY because I used VMWARE! To all you mac users out there, I tried Parallels 9 and voila it worked!

xmatic said:
Update:
I was able to root fine without any issues, it seems the issue was ONLY because I used VMWARE! To all you mac users out there, I tried Parallels 9 and voila it worked!
Click to expand...
Click to collapse
This is good to hear. I'll give a try and update later. Thanks
Sent from my SM-N900T using xda app-developers app
---------- Post added at 05:21 AM ---------- Previous post was at 05:07 AM ----------
In the future another easy way to unbrick your Samsung just open Kies in tools drop down select the emergency firmware. A pop up will ask you to put in your phone model and S/N. Kies restores firmware via download mode. This is how I restored from 5 bricks.
Sent from my SM-N900T using xda app-developers app

xmatic said:
Yeah, i've given up with rooting via VMWARE and Odin, it just doesn't work, period. I've tried to virtual machines, a win 8 and win 7 all with the same results. I have a feeling it's VMware, I am trying parallels now and I'll post updates afterwards. Thanks to everyone for contributing. BTW, does anyone know if it's even possible to root with Heimdall?
Click to expand...
Click to collapse
MUCH THANKS !!! To you my friend. I must've bricked my phone 5x trying to gain root using vmware.
So I downloaded the parellel 9. And BOOMMMM. I was so glad to see a big green pass in Odin lol.
Sent from my SM-N900T using xda app-developers app

Error when trying to rollback from CM 12.1 to Stock on N910P

Hi!
First of all, thanks for reading this...
Yesterday I installed Cyanogen cm-12.1-20160208-NIGHTLY-trltespr on my SM-N910P but I noticed that I lost my 4G connectivity (I only receive H, I'm in Mexico, using Nextel network). Because of that, I'm trying to rollback to my stock firmware (5.1.1) but when trying to do it using Odin (I've tried several FW and Odin versions) every time I receive the following error log:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.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> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On my phone, I receive this error:
UDC START
SW REV CHECK FAIL: [aboot] Fused 4 > Binary 1
[1] eMMC write fail: ABOOT
Any suggestion? I'll really appreciate your help
Thanks for your time!
Regards.

The bootloader has increased security that prevents older bootloaders from being installed even if the reactivation lock is not enabled. You cannot go back that far in Odin.
You've most likely found that you can still go back to CM with a backup or flash ROM. You should backup the things you want to keep that are on internal memory because you need to wipe that to restore stock.
You'll need a newer stock tar to restore stock. Galaxy Tools by iDone or this application in Google Play will tell you what your bootloader is to restore the same stock tar or newer.https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo But you can most likely install the latest stock tar found in the general forum if you go into recovery and wipe everything but extSdCard, power down and use latest Odin with Odin defaults to install it.
You need to go into Settings/System update and update PRL and data profile once your restored to stock.
Sent from my SM-N920P using Tapatalk

samep said:
The bootloader has increased security ....
Click to expand...
Click to collapse
Bro, you're my hero!!!! :good: my n910p is now as original!!! but now, I really don't know how to update the PRL for my network in Mexico...
Searching on Google I found how to update for Sprint Phones (My phone is a sprint one, but unlocked, so I can use it here in Mexico...) but I don't know if that could do the job...
Thanks!!!

lordkorhat said:
Bro, you're my hero!!!! :good: my n910p is now as original!!! but now, I really don't know how to update the PRL for my network in Mexico...
Searching on Google I found how to update for Sprint Phones (My phone is a sprint one, but unlocked, so I can use it here in Mexico...) but I don't know if that could do the job...
Thanks!!!
Click to expand...
Click to collapse
Your carrier should be able to help with the network connection issues. Tech support maybe?
Sent from my SM-N920P using Tapatalk

samep said:
Your carrier should be able to help with the network connection issues. Tech support maybe?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thanks my friend for your follow up!
I contacted Tech support today and after "several revisions" they told me that it is maybe the telephone, because when we tried to go to Settings > Data Usage > Mobile Networks, the option "Network Operatos" is disabled....
I was thinking to do the same that I did to run away from Cyanogen... Use the Phone info app, see the bootloader version and look for a firmware of that version (actually I have the N910PVPS4COK1) and apply it again to my phone... to see if that helps... what do you think?
Thanks!!!

lordkorhat said:
Thanks my friend for your follow up!
I contacted Tech support today and after "several revisions" they told me that it is maybe the telephone, because when we tried to go to Settings > Data Usage > Mobile Networks, the option "Network Operatos" is disabled....
I was thinking to do the same that I did to run away from Cyanogen... Use the Phone info app, see the bootloader version and look for a firmware of that version (actually I have the N910PVPS4COK1) and apply it again to my phone... to see if that helps... what do you think?
Thanks!!!
Click to expand...
Click to collapse
They can't provision it? I'm not sure if you have to be rooted to access it on an unlocked phone?
If they won't provision it, root or the XAS stock tar version of OK1 may open up the settings at more networks if you don't see them there. Be aware that going backwards in Odin may be blocked and cause those problems with flash again.
But you're rooted anyway, right? Try adding these lines to bottom of build.prop, leaving one blank line with no spaces at end and reboot.
ril.sales_code=XAS
ro.csc.sales_code=XAS
Sent from my SM-N920P using Tapatalk

samep said:
They can't provision it? I'm not sure if you have to be rooted to access it on an unlocked phone?
If they won't provision it, root or the XAS stock tar version of OK1 may open up the settings at more networks if you don't see them there. Be aware that going backwards in Odin may be blocked and cause those problems with flash again.
But you're rooted anyway, right? Try adding these lines to bottom of build.prop, leaving one blank line with no spaces at end and reboot.
ril.sales_code=XAS
ro.csc.sales_code=XAS
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I've no root on in (already, LOL). Let me root it and then, apply the couple of lines that you told me...
I'll keep you posted.
Thanks buddy!

lordkorhat said:
I've no root on in (already, LOL). Let me root it and then, apply the couple of lines that you told me...
I'll keep you posted.
Thanks buddy!
Click to expand...
Click to collapse
It didn't work my friend... :crying: take a look to my captures...
Thanks!

What about the Access Point Names. Aren't there edit symbols on those?
I'm not the expert but I at least thought it possible to edit for carrier with MSL as well.
Maybe this helps?
https://www.whistleout.com/CellPhon...y-verizon-sprint-phone-on-a-different-network
Sent from my SM-N920P using Tapatalk

Yes, I can see and edit the APN options, in fact I add them manually to try to force the 4G connectivity, but I only reach 3G..
Let me resume that I did and how I mess all up ... I bought this Note 4 unlocked with Android 5.1.1 installed on it. When I received everything worked perfectly, even my 4G network. Then, I wanted to test Cyanogenmod, so I installed it into my device... (why I did that!!!???). I saw that I lost a lot of functions of my Note 4 and I wanted to rollback my device... As long as I noticed that I couldn't do that so easily, I posted in here looking for help... Then you helped me out saying me this: "You'll need a newer stock tar to restore stock. Galaxy Tools by iDone or this application in Google Play will tell you what your bootloader is to restore the same stock tar or newer.https://play.google.com/store/apps/d...uyen.phoneinfo But you can most likely install the latest stock tar found in the general forum if you go into recovery and wipe everything but extSdCard, power down and use latest Odin with Odin defaults to install it."
I did that and I found a ROM (from Sprint, ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar.md5) that helped me to have my stock Android again, but since then, I lost 4G. Everything works perfectly but that. Then, I saw that on my phone appeared a system update, I ran it and now I gave the version N910PVPS4COK1
The last thing that I applied to my device was the root option, to try the option that you told me... that's my little soap opera... hehehe...
No matter the result of this, please thanks for your support on this path of darkness, XD

First thing first. That kernel your non. Is known to cause issues.
Sent from my 0x1 Note 4...... I love tep

N910p unlocked without 4G, only 3G
samep said:
What about the Access Point Names. Aren't there edit symbols on those?
I'm not the expert but I at least thought it possible to edit for carrier with MSL as well.
Maybe this helps?
https://www.whistleout.com/CellPhon...y-verizon-sprint-phone-on-a-different-network
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Hi!
After being investigating, I have recovered a "parcial backup" that I did of the boot files of my phone after I changed the ROM using TWRP.
The name of the backup file of the ROM that my phone had was is 2016-02-08--17-06-42_LMY47X.N910PVPU4COG5-LTE1-ASFAHAN.
The only files that I have from that backup are:
-boot.emmc.win
-boot.emmc.win.md5
-recovery.log
Just to remember, I'm from Mexico and I receive my note 4 n910p without Sprint logos and working perfectly on 4G LTE on Nextel. After I installed CM 12 I lost 4G. Actually I have Botcatrom and all works perfect except for 4g LTE. (I only receive 3g).
I have read that if a sprint phone gets unlocked, I'll be able to use only 3g, but as I mentioned before, I receive the phone working on 4G! so there must be something for it!
As we can see in the name of the ROM, it says LTE, so that's the one! (I think) but looking for that ROM on google, I cannot find it
Do you know something about that ROM? or maybe I can do something with the Boot files that I found? I was thinking to upload that Boot files into my actual Bobcatrom, but I'm not sure if it will help or I'll brick my device.
Any help will be appreciated.
Thanks!!!

lordkorhat said:
Hi!
After being investigating, I have recovered a "parcial backup" that I did of the boot files of my phone after I changed the ROM using TWRP.
The name of the backup file of the ROM that my phone had was is 2016-02-08--17-06-42_LMY47X.N910PVPU4COG5-LTE1-ASFAHAN.
The only files that I have from that backup are:
-boot.emmc.win
-boot.emmc.win.md5
-recovery.log
Just to remember, I'm from Mexico and I receive my note 4 n910p without Sprint logos and working perfectly on 4G LTE on Nextel. After I installed CM 12 I lost 4G. Actually I have Botcatrom and all works perfect except for 4g LTE. (I only receive 3g).
I have read that if a sprint phone gets unlocked, I'll be able to use only 3g, but as I mentioned before, I receive the phone working on 4G! so there must be something for it!
As we can see in the name of the ROM, it says LTE, so that's the one! (I think) but looking for that ROM on google, I cannot find it
Do you know something about that ROM? or maybe I can do something with the Boot files that I found? I was thinking to upload that Boot files into my actual Bobcatrom, but I'm not sure if it will help or I'll brick my device.
Any help will be appreciated.
Thanks!!!
Click to expand...
Click to collapse
Only thing I can think of is get in touch with your cellular provider or the point of sale of your phone. It seems you cannot run custom ROMs on your device and you don't have a full backup to restore. Ask if the XAS stock tar with APN edits is all you need. They should be able to help with provisioning service.
Updates would most likely come from OTA only once you restore the ROM with 4G would be my guess.
You should still be able to root and modify but that would have you in need of an updated stock tar to flash as your provider updates the ROM. IDK if it works but you may get by the tar updates using OTA update if you don't modify system.
Or make a stock backup of system partition before modifying it. Then you would restore that backup and full un-root. You would have to use the latest the updated Chainfire Auto root for Note 4. And you may have to root again and immediately go with full un-root in order to get the stock recovery with dm-verity cleared for OTA update. IMO, you'd be better off with a download for stock tar site before rooting but have the backup next time just in case. It might work for OTA updates but no guarantees.
I don't claim to be the expert but that's the best advice I can give with what I know ATM. Check around and see if there's a support site that includes your phone and provider; but you might find some guides our tutorials for editing APN. And when you get your ROM restored, try to copy your APN data to manually re-enter if you choose to risk another custom ROM or just need to provision it for service. Again, I'd suggest having a backup stock tar to flash before pursuing any risks.
Sent from my SM-N920P using Tapatalk