Hello, I have a 10.1 that runs on Verizon 4G here in the states. I'm familiar with rooting, as I have done it on other devices, but this was different. I had a update.zip that I used to get back to working condition until I can find the fix.
My model number is SCH-I905
I was in the process of odining the "[stock rom][3.0.1] P7100BUKDF + bootloader unlock" by chainfire. For some odd reason, I keep getting this error.
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
Click to expand...
Click to collapse
I either need to figure why this is not working, and finsh the bootunlock, and proceed to root from there.
If anyone can please help me fix this problem I'd be greatly appreciated. I fly out in a matter of hours and would like to have this fixed by then.
Why are you flashing that version? It's supposed to be for the Galaxy Tab 10.1v (7100, not SCH-I905)
What you want to do is root your device and change your recovery for CWM (stock ROM), just that, right?
If that's what you want, check this thread: http://rootzwiki.com/topic/2242-root-recovery-galaxy-tab-101-lte/
That thread is a little old, but it looks like still works for HC 3.2. If you want a newer version of CWM, don't flash the recovery from the previous link, instead download it from here: http://droidbasement.com/db-blog/ and flash it via Odin.
And have this threads at hand in case something goes wrong
http://forum.xda-developers.com/showthread.php?p=16812034
http://forum.xda-developers.com/showthread.php?t=1205639
Curses all these different verisons. I already flashed SU and flashed CWM via rom managee. Is that the equivilent to what you posted?
Sent from my GT10.1
How did you flashed SU?
I don't have the verizon tablet, but I think that the CWM provided by ROMManager is only for p4wifi, maybe they change it. Anyway, if everything is working fine, then leave it like that. But I prefer flashing cwm with Odin or a flashable (via recovery) zip.
I used this method:
http://forum.xda-developers.com/showthread.php?t=1657758
Root appears to be working, I know I installed root uninstaller and it did grant it access upon opening.
Related
Below is the situation i'm in. Please dont reply with a generic "flash xyz in Odin" post as ive tried if you read.
I got a used Note 2. It has a clean ESN. Works fine. I wanted too root/unlock it to load a custom recovery and then a custom ROM.
It has VRALI3 as both baseband and Build.
I tried to use multiple version of Casual with no luck. I then tried to use different odin files with no luck..i keep getting an error and fails during the nand flash portion. At one point I soft bricked it (only boot logo..no recovery...no boot).
Only way i restored it was via sch-i605-16gb.pit in the pit area, I605VRLI3- verizon.tar for PDA and uncheck re-partition.
So back to where I was.
I tried to then use the pit file with CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar
No luck..fails with nand flash write error.
Tried instructions at http://forum.xda-developers.com/showthread.php?p=34891181
No luck.
Then I tried to load root66_VZW_stock_system.tar and it worked. It only has a system.img file in it.
With this..I have a baseband of VRALI3 but with a build of VRALJB with ROOT.
So I was supper happy and then tried to repeat everything above with no luck still..nand flash error.
I tried goo manager since i had root and loaded custom recovery..got the yellow triangle.
Back to pit + vrali3..then pit + root66 back to root.
And thats where i sit.
I think VRALI3 was a prelease build???? But i dont know what i need to do to get out of it and unlock the bootloader. I have no idea what version bootloader was/is loaded already....
What can I do??
Thank you for reading...and any help would be appretiated.
guardianali said:
Below is the situation i'm in. Please dont reply with a generic "flash xyz in Odin" post as ive tried if you read.
I got a used Note 2. It has a clean ESN. Works fine. I wanted too root/unlock it to load a custom recovery and then a custom ROM.
It has VRALI3 as both baseband and Build.
Click to expand...
Click to collapse
Vrali3 is the pre release which has a different bootloader than the other 3 versions. As far as I know, you are up a creak without a paddle. There is no way to unlock bootloader and root, or change to a different version when you are on that. Probably why the person was selling it. I'm guessing the person was selling it for cheaper than other ones and that's why you bought it. That pre release is known to be attached to that damn toolkit that people think is awesome. Sell it and buy a different one.
Sent From My Sticky Note, Too?
EDIT: Solution for anyone having the same issues I saw below: Step 3, here:
http://forum.xda-developers.com/showthread.php?t=2281949
I'm not deleting the post since someone else may find this useful unless the mods think this post is noise. I do have one questions for the community: I would like to get to 4.4 and ideally, rooted. Does anyone with one of the first Verizon Note 2's have an experience similar to mine or advice on which route to take? Or should I just stick with OTA and forget root?
I need help getting my phone working. My original goal was to get a modified stock 4.4 ROM + root on my phone. My phone was 4.1.1 until I began this process. I tried to root via exynox, that failed, but using CF-Auto-Root (CF-Auto-Root-t0ltevzw-t0ltevzw-schi605.tar) worked. I added CWM, wiped data/cache, and tried to install this kernel: http://forum.xda-developers.com/showthread.php?t=2607652 and this ROM: http://forum.xda-developers.com/showthread.php?t=2765021. Similar to some of the messages in the ROM thread, I was stuck at the red screen. I followed krowley3's strategy here: http://forum.xda-developers.com/showpost.php?p=52982544&postcount=41, I Odin'd back to 4.1, unlocked the phone again, got to 4.3, ran saferoot, tried to flash to 4.4, that failed updating the firmware - failed to write sboot.bin.
I tried the suggestion in this thread: http://forum.xda-developers.com/showthread.php?p=39299305 using the VRALJB update to Odin a new PDA. I did get this within the first month of release and didn't take any OTA, so per the warning, I used that version. No luck. Per advice in a thread I'm trying to find again, I Odin'd this PIT: http://www.mediafire.com/download.php?05cj895zu3tls7z, which worked, tried to Odin the bootloader, but that fails at sboot.bin and says: Complete(Write) operation failed.
The status of my phone: it boots into recovery and I can install 4.1.1 stock. It still fails at the sboot when I try a bootloader. When I try to load the firmware, its stuck at the black screen that says "samsung galaxy note 2" and doesn't continue.
In trying to debug, I opened CASUAL-SuckItVerizon-Injection9 while it was loading (to see if it would spit out any logs) and it did something odd: it when I'm on the black screen, it keeps saying 'connected' and 'disconnected' and the adb server connects and disconnects. I'm not familiar enough with debugging these things to dig further. I can't abb to the phone via command line on Windows 7. When I go to Odin mode on the phone, it says:
Product Name: SCH-I605
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
KNOX WARRANY VOID: 0
AP SWREV: A2
Click to expand...
Click to collapse
I'm reading up on this one: http://forum.xda-developers.com/showthread.php?t=2690033, but I'd REALLY appreciate any advice you can give me. At this point, I want a working phone, rooted and at 4.4 (or 4.3) are nice-to-haves.
Sorry if I'm missing something obvious in the stickies - I'm getting stressed right now.
Hey all. I had Hypderdrive installed. I updated it to 21 but had a force close issue. I wiped to reinstall in safestrap and realized that I didn't have the ROM on the device anymore. Whoops. All of a sudden I had no OS and couldn't connect to the phone via USB to put the ROM onto it.
After trying some stuff I got a bit more stuck. I can only reboot into 3 places: 1) Download mode (with volume down) 2) stuck at samsung unlocked icon (no buttons pressed) and 3) default recovery mode (with volume up). I tried with Kies to just install the latest firmware, figuring I'd be happy with lollipop and just go ahead and get a new phone in the near future. That firmware upgrade process fails right when the status bar shows up on the screen. Now rebooting the phone says Software Update Failed.
What are my options via Kies, Odin, or something else to either get back to rooted Hyperdrive or just get the latest firmware up and running? Thanks!
ODIN v3.10
https://docs.google.com/file/d/0B4RU_ZH5QUASNmxLX3JpejBXREE/edit?usp=docslist_api
This is the SCH-I545 lollipop image:
https://docs.google.com/file/d/0B4RU_ZH5QUASaU9LcDJ3WWZfdXM/edit?usp=docslist_api
And once you go forward..There is NO ROOT or ROMMING!!!
If you want to stay NK1 and ROOT:
https://docs.google.com/file/d/0B4RU_ZH5QUASdHE1b2Q2NXpVX0U/edit?usp=docslist_api
In ODIN, WITH EITHER file select these checkboxes:
Auto-Reboot
Re-Partition
F. Reset Time
NAND Erase All
Phone Bootloader Update
Phone EFS CLEAR
Thanks a ton. Haven't gotten it to work yet. I followed your directions and Odin fails with "SW REV. CHECK FAIL : fused : 7, Binary : 6". My guess is that is a mismatch of the bootloader versions? I believe I was on NC5 before, so I tried flashing the No Wipe file from here: http://forum.xda-developers.com/showthread.php?t=2735172 and had no luck.
Any idea what version I should be trying to get it to work? Thanks for the help so far!
No. That means you are on lollipop Bootloader already! You have to flash lollipop
KaosMaster said:
No. That means you are on lollipop Bootloader already! You have to flash lollipop
Click to expand...
Click to collapse
Yup. Learned that while I was thinking about it. Such is life, right? Currently trying to just get OC1 installed via Odin but it keeps failing late in the process with XmitData_Write. If anyone has an idea beyond changing cables and ports (which I'm doing now) then I'm all ears.
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
volantis said:
Quick update. I've been following the instructions and advice from this thread: http://forum.xda-developers.com/galaxy-s4-verizon/help/unbrick-taking-oc1-t3122230
I have not yet gotten my phone working, but have made slight progress. I'm currently flashing from the Software Update Failed screen and not the Odin Download Mode screen. I've been checking all the listed boxes. I've tried flashing as CSC and as AP and it is now failing on the NON-HLOS.bin file. It's failed there 4 or 5 times now.
Any advice on what changes to try next?
Click to expand...
Click to collapse
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
KaosMaster said:
the Single Service File goes in the CSC box. Not sure why it keeps failing, but my OPinion is that you should Try to Load into Recovery, Perform A Factory Data Reset then Try again!
Flash with the Check-Boxes befoire without the "Phone EFS Clear" option...When THe phone turns on....if it is The firmware Recovery screen...Flash there, if it is the Samsung LOGO, Pull the Battery, and LOAD into "Odin Mode" and Flash AGAIN There!
Click to expand...
Click to collapse
Thanks. I finally got it working. I'm not sure exactly what did it. I kept trying various combinations of flashing at CSC or AP and in Download mode and Software Upgrade Failed. I believe the one that actually took was the Sammobile stock OC1 file flashed as AP, but I'm not 100% and not sure that really is what made the difference. I did have all the options checked when it finally took.
After the Odin flash passed it did just boot to a black screen with the LED on solid blue. I went to recovery and did a factory reset and the phone booted up. Maybe that'll help someone else.
Don't have root anymore, but Lollipop seems like a very nice update coming from KK.
Thanks! - but still in trouble.
Spoke too soon!! Yours was the only one that actually loaded with Odin. After that phone will not reboot, just comes on for 2 seconds and then turns off. Any ideas would be greatly appreciated.
I have tried the following firmware versions, except for yours, they all get fused: 7 , binary : 6:
I545_VZW_I545VRUDMI1_I545VZWDMI1_Original
I545_VZW_I545VRUEMJ7_I545VZWEMJ7_Original
VZW-I545VRUFNC5-20140429111807
VZW-I545VRUFNG6-20141021092718
plus several others
--------------
Thanks, bricked my Verizon S4 and tried 5 different firmware files, including the ones from the Samsung site. Yours is the only one that worked.
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
volantis said:
Looks like you need to flash a more recent file. You'll probably have to go with the latest stock version without root.
Click to expand...
Click to collapse
Sorry, thought I updated the post. I tried again and the second time around it worked all the way through with the file on this thread.
PROBLEM SOLVED: Downloaded newer version of Firmware and that worked. I feel super super dumb for not thinking of that sooner. I was following an older guide to unroot/restore to stock and the newest available link was VREUMJ9 and apparently that was too old.
I'm trying to send my Galaxy Note 2 in for warranty. It had accepted 4.3 OTA but I had rooted it afterward. So I went to restore to stock and unroot so I could send it in. I had just recently done another Note 2 (My dads) back to stock without a hitch so I figured it would be no big deal. Except I forgot one minor detail that his phone didn't take 4.3 OTA and still had unlocked bootloader. So I opened up Odin 3.07 and put PIT file in PIT and VRAMC3 firmware in PDA and hit start and the flash failed. Took me a few seconds to realize that I flashed the wrong firmware and should've been VRUEMJ9. I was panicing and downloaded VRUEMJ9 and attempted to flash that and it wouldn't even start the flash just failed right away. Now ODIN isn't even recognizing the phone anymore. Am I totally screwed here? I've been googling furiously and it sounds like maybe cause I selected a .PIT file it may have hard bricked my device? I just instinctively did that because it was required to make it work correctly on the last phone I did just a few weeks ago.
I can still access download mode but ODIN doesn't show anything in COM window. Trying to boot phone normally shows "Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again" I've tried repeatedly restarting phone and rebooting PC and reinstalling USB drivers. Is "Software Repair Assistant" something I should try? It sounds like Verizon's version of ODIN? http://www.verizonwireless.com/support/knowledge-base-80201/
Any help GREATLY appreciated. I really really really don't have the money to pay full price for this bricked phone Assuming I can't get this fixed and I just send them the phone as-is what are the chances they even notice? Do they test them?
I managed to get ODIN to recognize the phone using a different computer. Upon attempting to flash VRUEMJ9 in PDA of ODIN this happens: http://imgur.com/2msfTEQ
Firmware update start..
sboot.bin
NAND write start!!
FAIL!
All threads completed. (Succeed 0 / Failed 1)
This happens whether I do just the firmware or firmware + PIT. Flashing PIT by itself will succeed and the phone changes to a message saying something about unsupported software and to turn my phone off and take it to Verizon. But it doesn't seem to change anything cause flashing FW still doesn't work. Almost identical error message using ODIN 3.09 figured I would try a newer version of ODIN.
Edit: After reading some more. It sounds like I might have a corrupted NAND which from what I read is only fixable by replacing MB. Is this true? If so how much would it cost to get repaired if I went to a samsung service center?
Extremely sorry to post this thread again - actually I referred all the threads in XDA Developers Forums but though a few of them matched my requirement but it was closed since 2013 - hence reopening again...
I have a Samsung GT-P1000 - Made in Korea (I don't live there - live in India though) - FCC ID: A3LGTP1000 - S/N: R2DB129469E
I will provide complete details to make it coherent to you...
CURRENT STATUS -- Soft Bricked (Symbol: A mobile - A yellow triangle with exclamation - A desktop) - (The only thing I see in the tab now!!!)
BEFORE -- Android 2.3.3 Gingerbread, no mods (no root, no custom boot-loader, etc...) -- Complete Original Tablet
What I tried to do --
Install Android 6.0.1 Marshmallow (Following this guide: https://www.droidthunder.com/galaxy-tab-gt-p1000-android-marshmallow-rom/) but soon failed in the rooting step itself, precisely, while installing cwm13...
Now, what I want to do --
After some research, which I must have done earlier, not sure, but maybe people are trying to say that installing Android 6.0.1 Marshmallow is not possible... I did not go deeper...
Anyway, I thought we will revert back to what it was... to Android 2.3.3 Gingerbread...
The problem I face doing this --
To install Android 2.3.3 Gingerbread back I used,
-- Odin3_v1.83
-- And the PIT, PDA, and Phone files are here (https://drive.google.com/drive/folders/1CLrfcUdk-oZ1N6ZZ90LbDCdMW5KYkHnV?usp=sharing) - (I got these while referring to a YouTube video:
)
-- And also installed the USB drivers (updated)
And then, following the above YouTube video, I came up with this, (After connecting the device with the PC - after around 15 mins the brick screen appears - It shows a yellow color port in odin - and I start), And stops after this log,
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Then I switched the ports aswell, and the only difference from the above error is the id changes from 7 to 6...
Also, tried with Odin_v3.07, Odin_v3.13.1, Odin_v3.09, Odin_v3.12.3, but the same logs...
And then, started researching this error but no answer was up to my requirement (there are same threads in this forum but the answers for them did not work for me)
Any help would be highly appreciated,
Thank You
My father once had this tablet. But he never flashed a custom rom to it.
Maybe the partitions were changed for flashing the custom rom. To install a stock rom again, you have to flash the original pit file in order to get partitions into the state for fitting the stock firmware. In Odin, there are separate partition options that you have to set.
Have a look here about repartition using Odin:
Thread 'Re-Partition in Odin, what is it for?' https://forum.xda-developers.com/t/re-partition-in-odin-what-is-it-for.860432/
It_ler said:
My father once had this tablet. But he never flashed a custom rom to it.
Maybe the partitions were changed for flashing the custom rom. To install a stock rom again, you have to flash the original pit file in order to get partitions into the state for fitting the stock firmware. In Odin, there are separate partition options that you have to set.
Have a look here about repartition using Odin:
Thread 'Re-Partition in Odin, what is it for?' https://forum.xda-developers.com/t/re-partition-in-odin-what-is-it-for.860432/
Click to expand...
Click to collapse
Thank You for replying @It_ler , this was my 1st question in this forum and waiting since a month or more, I am glad you put your precious time in this thread.
I am new to this forum, and I see you are pretty experienced in here, I would really really appreciate if you can help me gather more minds into this. I have memories linked with this tab, and all these days I have been eagerly waiting for a reply.
As you said, to check the re-partition in Odin, I see that it automatically gets checked once I start flashing, but the logs remain the same...