I have a Sprint Note 3 which had previously been flashed with CWM Recovery and had ClockworkMod 11 for hlte installed. This was prior to the hlte split of CM. In attempting to install the newest hltespr nightly of CM through CWM, I received an error that the CM build I'm trying to install doesn't match the architecture of the phone, which is hlte. So, I tried to flash the hltespr variant of CWM Recovery. After flashing the new recovery and attempting to enter it, I encounter the following:
Recovery Booting
KERNEL IS NOT SEANDROID ENFORCING
Warranty bit: recovery
--(phone reboots without reaching recovery screen)--
KERNEL IS NOT SEANDROID ENFORCING
Warranty bit: kernel
--(phone boots into CM normally)--
I've attempted this installing CWM through the ROM Manager app and installing both CWM and TWRP through Heimdall. All of these encounter the same issue on attempting to boot into Recovery. Any help would be greatly appreciated.
Soichiro11 said:
I have a Sprint Note 3 which had previously been flashed with CWM Recovery and had ClockworkMod 11 for hlte installed. This was prior to the hlte split of CM. In attempting to install the newest hltespr nightly of CM through CWM, I received an error that the CM build I'm trying to install doesn't match the architecture of the phone, which is hlte. So, I tried to flash the hltespr variant of CWM Recovery. After flashing the new recovery and attempting to enter it, I encounter the following:
Recovery Booting
KERNEL IS NOT SEANDROID ENFORCING
Warranty bit: recovery
--(phone reboots without reaching recovery screen)--
KERNEL IS NOT SEANDROID ENFORCING
Warranty bit: kernel
--(phone boots into CM normally)--
I've attempted this installing CWM through the ROM Manager app and installing both CWM and TWRP through Heimdall. All of these encounter the same issue on attempting to boot into Recovery. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I run Philz custom CWM hltespr v6.12.9 what message you are getting is normal. Usually in three different colors of text, right ? As for it not booting into CWM recovery I would redownload the .tar file make sure it is the right version for your device and flash it again through ODIN . Here is my thread should answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
jimzweb1 said:
I run Philz custom CWM hltespr v6.12.9 what message you are getting is normal. Usually in three different colors of text, right ? As for it not booting into CWM recovery I would redownload the .tar file make sure it is the right version for your device and flash it again through ODIN . Here is my thread should answer all your questions http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 Enjoy !!!
Click to expand...
Click to collapse
After trying it a couple more times (running Heimdall in verbose mode) I think it is actually not transferring the new image and this is why I can't access recovery. I'm getting the infamous "libusb error -7 whilst receiving bulk transfer." error. Which after looking at all the Google results and trying different sets of patches to Heimdall, I have yet to get the error to go away. I'm on a Mac so I wonder if this could be causing the libusb issue? I can try with Windows in a few hours if there are no solutions for the Mac version of Heimdall.
The full Heimdall log looks like this, also the blue bar does go across the screen of the Note 3:
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.
Downloading device's PIT file...
PIT file data received, read 'empty' packet...
PIT file data receive completed, send kRequestEndTransfer...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer.
ERROR: Failed to receive end PIT file transfer verification!
ERROR: Failed to download PIT file!
Ending session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Releasing device interface...
Soichiro11 said:
After trying it a couple more times (running Heimdall in verbose mode) I think it is actually not transferring the new image and this is why I can't access recovery. I'm getting the infamous "libusb error -7 whilst receiving bulk transfer." error. Which after looking at all the Google results and trying different sets of patches to Heimdall, I have yet to get the error to go away. I'm on a Mac so I wonder if this could be causing the libusb issue? I can try with Windows in a few hours if there are no solutions for the Mac version of Heimdall.
The full Heimdall log looks like this, also the blue bar does go across the screen of the Note 3:
Code:
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Some devices may take up to 2 minutes to respond.
Please be patient!
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Session begun.
Downloading device's PIT file...
PIT file data received, read 'empty' packet...
PIT file data receive completed, send kRequestEndTransfer...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer. Retrying...
ERROR: libusb error -7 whilst receiving bulk transfer.
ERROR: Failed to receive end PIT file transfer verification!
ERROR: Failed to download PIT file!
Ending session...
WARNING: Empty bulk transfer after sending packet failed. Continuing anyway...
Releasing device interface...
Click to expand...
Click to collapse
Sorry I can't be of more help, I'm not that familiar with Heimdall and Mac, I run windows 7 on PC.
I did get it to flash PhilZ recovery on Windows using Odin. It seems like Heimdall and the Note 3 just don't cooperate well (I wasn't able to get Heimdall to work on Windows either). However, I am running into another issue now.
I installed the latest CM Nightly (cm-12-20150114-NIGHTLY-hltespr), and the install succeeded, but I have no phone signal at all in the new build. If I restore back to the old build (cm-11-20140916-SNAPSHOT-M10-hlte) I have my phone signal back. I know this can be caused by installing the wrong build, but hltespr should be the correct build, right? I know that I have a N900P from Sprint.
Soichiro11 said:
I have a Sprint Note 3 which had previously been flashed with CWM Recovery and had ClockworkMod 11 for hlte installed. This was prior to the hlte split of CM. In attempting to install the newest hltespr nightly of CM through CWM, I received an error that the CM build I'm trying to install doesn't match the architecture of the phone, which is hlte. So, I tried to flash the hltespr variant of CWM Recovery. After flashing the new recovery and attempting to enter it, I encounter the following:
Recovery Booting
KERNEL IS NOT SEANDROID ENFORCING
Warranty bit: recovery
--(phone reboots without reaching recovery screen)--
KERNEL IS NOT SEANDROID ENFORCING
Warranty bit: kernel
--(phone boots into CM normally)--
I've attempted this installing CWM through the ROM Manager app and installing both CWM and TWRP through Heimdall. All of these encounter the same issue on attempting to boot into Recovery. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Off question sorry but what mac OSX are you using? And have you checked around on the CM thread to see if others are having the same problem?
Goat1378 said:
Off question sorry but what mac OSX are you using?
Click to expand...
Click to collapse
10.9.5 Maverick
Soichiro11 said:
10.9.5 Maverick
Click to expand...
Click to collapse
But you are using a windows with odin now yes? If this is happening to you it may be happening to someone else at the CM thread. Id check around there if you haven't already. If its a nightly then the build just might have issues. But I dnt know much about CM myself.
Goat1378 said:
But you are using a windows with odin now yes? If this is happening to you it may be happening to someone else at the CM thread. Id check around there if you haven't already. If its a nightly then the build just might have issues. But I dnt know much about CM myself.
Click to expand...
Click to collapse
I use a Mac at work and Windows at home. I found a blog entry which says that the issue may be caused by an outdated modem on the phone. I am downloading the latest stock firmware right now and will flash the modem when I get home.
Soichiro11 said:
I use a Mac at work and Windows at home. I found a blog entry which says that the issue may be caused by an outdated modem on the phone. I am downloading the latest stock firmware right now and will flash the modem when I get home.
Click to expand...
Click to collapse
If you could and if time allows... Could you update your outcome so that others may see incase they are having the same issue? And maybe a useful thread link to where you found your info so others may read up. So many times I've been chasing down answers and the trail runs cold.
Goat1378 said:
If you could and if time allows... Could you update your outcome so that others may see incase they are having the same issue? And maybe a useful thread link to where you found your info so others may read up. So many times I've been chasing down answers and the trail runs cold.
Click to expand...
Click to collapse
I went through the process of flashing the latest stock ROM (including modem), then reflashing a custom recovery and reinstalling the latest CM. Unfortunately, still no mobile signal. I'm back to the working M10 snapshot for now, but hoping someone can come up with an answer.
Soichiro11 said:
I went through the process of flashing the latest stock ROM (including modem), then reflashing a custom recovery and reinstalling the latest CM. Unfortunately, still no mobile signal. I'm back to the working M10 snapshot for now, but hoping someone can come up with an answer.
Click to expand...
Click to collapse
Have you tried to update your prl and profile in settings/general/update? If not try that and reboot your phone.
Goat1378 said:
Have you tried to update your prl and profile in settings/general/update? If not try that and reboot your phone.
Click to expand...
Click to collapse
Yes, I attempted all of these. No dice.
Soichiro11 said:
Yes, I attempted all of these. No dice.
Click to expand...
Click to collapse
Are you on the new NK4 baseband? If not maybe that needs to be updated.
Goat1378 said:
Are you on the new NK4 baseband? If not maybe that needs to be updated.
Click to expand...
Click to collapse
Yes, NK4 is the one that I flashed yesterday. I even checked in the stock updates screen to make sure it was the latest OTA update.
Soichiro11 said:
Yes, NK4 is the one that I flashed yesterday. I even checked in the stock updates screen to make sure it was the latest OTA update.
Click to expand...
Click to collapse
And did all the proper wipes and such? Did you just update baseband or full NK4? And when you updated did you do the update process as instructed from a completely powered down state?
Goat1378 said:
And did all the proper wipes and such? Did you just update baseband or full NK4? And when you updated did you do the update process as instructed from a completely powered down state?
Click to expand...
Click to collapse
I flashed the full NK4 stock rom through Odin.
Soichiro11 said:
I flashed the full NK4 stock rom through Odin.
Click to expand...
Click to collapse
Did the Nk4 have signal? Or whatever it is thats not working?
Does CM suggest to format data?
Did you wiped and factory reset before flashing?
Maybe the CM rom was a bad download?
If not and sorry if its been said I did read the posts but it was yesterday.
Try booting into whatever recovery you have (stock or custom) and doing a full wipe then battery pull. Wait 10 sec. Put the battery back in and 3 button combo to download mode.
Uncheck reboot opinion.
Flash your full NK4 and just for kicks pull the battery again wait 10 sec .
3 button combo into download mode.
Now when your in odin check the reboot and flash.
If it boots and all is well go rite in and update your prl/profile and reboot.
Then do your root/recovery. I know its alot but sometimes it just works that way.
Then try you CM rom make sure you read all of the suggestions and follow to the T. You probably have I just wanna cover all grounds is all. Good luck.
I'm not able to test with your reflash instructions until later, but I did find out that apparently I'm not alone: http://www.reddit.com/r/cyanogenmod/comments/2sjqzb/hltespr_no_service/
I wonder if there's any place I could get a newer version of CM11 for hltespr and test with that? I tried to download a CM11 build from the official site but all the links prior to CM12 give 404s.
Soichiro11 said:
I'm not able to test with your reflash instructions until later, but I did find out that apparently I'm not alone: http://www.reddit.com/r/cyanogenmod/comments/2sjqzb/hltespr_no_service/
I wonder if there's any place I could get a newer version of CM11 for hltespr and test with that? I tried to download a CM11 build from the official site but all the links prior to CM12 give 404s.
Click to expand...
Click to collapse
If thats the case it might be as simple as if could have been a bad upload and they pulled it.
Related
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.
About 2 weeks ago, I unlocked the bootloader to my Nexus 9. I installed TWRP and a CyanogenMod nightly. After deciding the only availible Cyanogen builds for the Nexus 9 (the nightlies) are far too unstable for general use, I tried today to flash the recovery ROM. I flashed the rom with an error:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(893,0xa04ae1d4) malloc: *** mach_vm_map(size=1816023040) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1814205204 bytes
error: update package missing system.img
I then made the ridiculous mistake of locking my bootloader again (fastboot oem lock) which ran successfully, but then got me stuck in a recovery boot loop (teamwin splash screen). After about a minute of this, the screen went black and the device is now a $399 paperweight. I cannot use any key combinations to get the screen on. It won't show up in fastboot either. I have no hopes of getting a repair from HTC for three main reasons:
1. I got the device from somebody who attended a conference at Google and received the device for free. Does it affect my warranty?
2. If there is a custom recovery, I have surely voided what warranty I would've had.
3. I live in a Central American country, where it is extremely difficult to ship items to the United States, especially items of high value.
Is my wonderful device that was so kindly given to my now an HTC branded brick?
[UPDATE] I have been able to get into fastboot, but I still get the error? I got the firmware from the official Google page, and I am 100% sure I downloaded the correct rom :/
You're most likely sol. Read this thread, http://forum.xda-developers.com/showthread.php?p=59677447
Sent from my Nexus 9 using XDA Free mobile app
With the error you get when trying to flash factory image through adb . Have you tried first to unzip the images from inside the file downloaded from google and flash individually? You've already flashed the bootloader/radio when you started installing the factory image, I wonder if you flash the image files inside the zip inside the factory tgz if you might escape? look here, http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668 if you can still fastboot this might help?
nrsmac said:
About 2 weeks ago, I unlocked the bootloader to my Nexus 9. I installed TWRP and a CyanogenMod nightly. After deciding the only availible Cyanogen builds for the Nexus 9 (the nightlies) are far too unstable for general use, I tried today to flash the recovery ROM. I flashed the rom with an error:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(893,0xa04ae1d4) malloc: *** mach_vm_map(size=1816023040) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1814205204 bytes
error: update package missing system.img
I then made the ridiculous mistake of locking my bootloader again (fastboot oem lock) which ran successfully, but then got me stuck in a recovery boot loop (teamwin splash screen). After about a minute of this, the screen went black and the device is now a $399 paperweight. I cannot use any key combinations to get the screen on. It won't show up in fastboot either. I have no hopes of getting a repair from HTC for three main reasons:
1. I got the device from somebody who attended a conference at Google and received the device for free. Does it affect my warranty?
2. If there is a custom recovery, I have surely voided what warranty I would've had.
3. I live in a Central American country, where it is extremely difficult to ship items to the United States, especially items of high value.
Is my wonderful device that was so kindly given to my now an HTC branded brick?
[UPDATE] I have been able to get into fastboot, but I still get the error? I got the firmware from the official Google page, and I am 100% sure I downloaded the correct rom :/
Click to expand...
Click to collapse
First of all why the HELL did you lock your bootloader?? Secondly, every single person who has tried to flash these factory images from google using the built in script got this same exact error, including me. All you had to do was manually "fastboot flash system system.img" and thats it. Problem solved. Unless you can manage to get the bootloader unlocked again, its bricked. Good luck
bynarie said:
First of all why the HELL did you lock your bootloader?? Secondly, every single person who has tried to flash these factory images from google using the built in script got this same exact error, including me. All you had to do was manually "fastboot flash system system.img" and thats it. Problem solved. Unless you can manage to get the bootloader unlocked again, its bricked. Good luck
Click to expand...
Click to collapse
I made the mistake of blindly following the advice on the Google page (which did tell me to lock the device). Google needs to fix that script, and get us 5.1 on our nexus devices!!!
casual gives error on stock rooted 4.1.1 android version
hi guys.
so i had android 4.3 and downgraded to stock rooted 4.1.1 with odin.
Root66 stock VRALJB 4.1.1 12/2/12 from this thread http://forum.xda-developers.com/showthread.php?t=2024207&nocache=1
the problem is that casual it gets stuck with this:
Uploading BOOTLOADER 100% ERROR: Failed to confirm end of file transfer sequence! ERROR: BOOTLOADER upload failed!
version used: NoYouVerizon-GalaxyNote2-CASUAL R515
tried to flash to this non rooted version with odin CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar, but fails after the start.
tried with 2 different usb cables and different usb ports but not working.
any idea guys.i need to unlock that bootloader to install a rom that has italian language for use in italy.i want to give this phone to my mom, but is from US locked.
any ideas guys?
update:
so with BackAtchaVerizon-CASUAL-Revision465b it works well till at almost at the end, says failed recovery and something and gets stuck.
-----NoYouVerizon-GalaxyNote2-CASUAL R515
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Uploading PIT
PIT upload successful
Uploading BOOTLOADER
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOTLOADER upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
[Heimdall Error Report] Detected:
Heimdall uncontinuable error; Script halted
[/Heimdall Error Report]
done
Script Complete
-----BackAtchaVerizon-CASUAL-Revision465b
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
BOOT upload successful
Ending session...
Rebooting device...
Releasing device interface...
[Heimdall Success]
Your device should be rebooting into Android now.
waiting for ADB device connection...
mkdir failed for /data/local/tmp, File exists
Pushing dependencies
Pushing su binary...
5757 KB/s (91980 bytes in 0.015s)
Pushing SuperSU app...
4799 KB/s (996704 bytes in 0.202s)
Pushing Exynos-Abuse exploit
4029 KB/s (64373 bytes in 0.015s)
Pushing root script
0 KB/s (361 bytes in 1.000s)
Pushing Busybox
5083 KB/s (1867568 bytes in 0.358s)
Pushing viewmem
5 KB/s (5417 bytes in 1.000s)
Pushing pit
8 KB/s (8192 bytes in 1.000s)
Setting Permissions....
Executing Root Exploit.
[*] s_show->seq_printf format string found at: 0xC086C348
[*] sys_setresuid found at 0xC00967C4
[*] patching sys_setresuid at 0xC0096808
remounting system rw....
moving su into position
moving Superuser.apk into position
[x]Ready for exploit
Linux version 3.0.31-414933 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Sun Oct 28 13:34:23 KST 2012
[x]Found rooted device
[x]Device Verification Checks Complete
[x]Ready for exploit
Injecting Code
16+0 records in
16+0 records out
8192 bytes transferred in 0.002 secs (4096000 bytes/sec)
[x]Exploit Injection Done.
your device is now rebooting into a totally insecure download mode. Press the Volume Up buton when requested by Download Mode. You will then flash the Suck It Verizon bootloader located here: [url]http://d-h.st/DQG[/url]. Upon completion of this step, you will be rebooted into TWRP Recovery. CASUAL will wait for you to complete the insecure flash of the Suck It Verizon Bootloader. Press the Up Key before you flash the bootloader in Odin Mode.
Waiting for Downoad Mode device.......Executing Heimdall command.
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
[url]http://www.glassechidna.com.au/[/url]
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
[url]http://www.glassechidna.com.au/donate/[/url]
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading recovery
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: recovery upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
[Heimdall Error Report] Detected:
Heimdall uncontinuable error; Script halted
[/Heimdall Error Report]
done
also i flashed to root66 using a pit file otherwise odin3 will fail
any help guys?
imnopro said:
any help guys?
Click to expand...
Click to collapse
Casual only works on 4.1.2, which was the last Android version on the i605 that has a bootloader that you could unlock yourself.
4.3 has a locked bootloader that will prevent you from being able to successfully downgrade the phone to any Android version before 4.3. The best you'll be able to do is use Odin to restore the phone back to stock 4.3. You can root 4.3 with SafeRoot, and then use Safestrap Recovery to run 4.3 based Roms that use the stock 4.3 kernel. You should be able to find details on how to do this by searching the threads.
Hope this helps.
mattnmag said:
Casual only works on 4.1.2, which was the last Android version on the i605 that has a bootloader that you could unlock yourself.
4.3 has a locked bootloader that will prevent you from being able to successfully downgrade the phone to any Android version before 4.3. The best you'll be able to do is use Odin to restore the phone back to stock 4.3. You can root 4.3 with SafeRoot, and then use Safestrap Recovery to run 4.3 based Roms that use the stock 4.3 kernel. You should be able to find details on how to do this by searching the threads.
Hope this helps.
Click to expand...
Click to collapse
why should i go to 4.3 if i'm on rooted root66 4.1.1 ?
check last post:
http://forum.xda-developers.com/showthread.php?p=62930543#post62930543
imnopro said:
why should i go to 4.3 if i'm on rooted root66 4.1.1 ?
check last post:
http://forum.xda-developers.com/showthread.php?p=62930543#post62930543
Click to expand...
Click to collapse
imnopro said:
hi guys.
so i had android 4.3 and downgraded to stock rooted 4.1.1 with odin.
Click to expand...
Click to collapse
I did read all of your posts. You said that your phone was on 4.3...so I'm taking that to mean that the phone was on Stock Verizon 4.3. You used root 66 to downgrade the system, but Verizon/Samsung security will not allow you to downgrade the bootloader to anything previous to 4.3. This is well documented throughout the Note 2 threads. So... Casual will not work for you because your bootloader is still on 4.3.
And just to provide more proof to what I'm telling you, go to Droidstyle's Restore guide here:
( http://forum.xda-developers.com/showthread.php?p=34891181)
and read where he says--
As most know by now, Devices that took the MJ9 4.3 OTA update permanently locked the bootloader. The previous Root and Unlock methods no longer work for this latest update. However our kind Devs developed SafeStrap for a workaround, which allows root and flashing Touch Wiz roms. Please head over to this thread for installing SafeStrap on 4.3 VRUEMJ9- http://forum.xda-developers.com/showthread.php?t=2693131
mattnmag said:
I did read all of your posts. You said that your phone was on 4.3...so I'm taking that to mean that the phone was on Stock Verizon 4.3. You used root 66 to downgrade the system, but Verizon/Samsung security will not allow you to downgrade the bootloader to anything previous to 4.3. This is well documented throughput the Note 2 threads. So... Casual will not work for you because your bootloader is still on 4.3.
Click to expand...
Click to collapse
so,android is 4.1.1 and the bootloader is 4.3...this means no custom rom on 4.3.great
at least a different sim will work on this root66 or i need to take the imei and go on some websites and pay and get the code to unlock it?
imnopro said:
so,android is 4.1.1 and the bootloader is 4.3...this means no custom rom on 4.3.great
at least a different sim will work on this root66 or i need to take the imei and go on some websites and pay and get the code to unlock it?
Click to expand...
Click to collapse
If I were you, I would probably just restore the phone to 4.3 and root it with Saferoot if you want a rooted stock ROM, but that's just me. With 4.3, you can also install Safestrap and then have some options with Custom ROM'S.... but they must be based on stock 4.3 TouchWiz and use the stock 4.3 kernel (so this means no AOSP, MIUI, etc).
Other XDA members said their Note 2 worked well in Italy (see here: http://forum.xda-developers.com/showpost.php?p=50982212&postcount=57 ).
The Verizon Note 2 is Sim/Carrier unlocked, so you should at least get voice service when you insert the Sim card. You may have to manually add APN's to get data working. Here's a good post from Max Lee that may help with changing APN settings if needed: http://highonandroid.com/android-howtos/how-to-fix-3g4g-lte-data-by-manually-setting-apn/
mattnmag said:
If I were you, I would probably just restore the phone to 4.3 and root it with Saferoot if you want a rooted stock ROM, but that's just me. With 4.3, you can also install Safestrap and then have some options with Custom ROM'S.... but they must be based on stock 4.3 TouchWiz and use the stock 4.3 kernel (so this means no AOSP, MIUI, etc).
Other XDA members said their Note 2 worked well in Italy (see here: http://forum.xda-developers.com/showpost.php?p=50982212&postcount=57 ).
The Verizon Note 2 is Sim/Carrier unlocked, so you should at least get voice service when you insert the Sim card. You may have to manually add APN's to get data working. Here's a good post from Max Lee that may help with changing APN settings if needed: http://highonandroid.com/android-howtos/how-to-fix-3g4g-lte-data-by-manually-setting-apn/
Click to expand...
Click to collapse
so i tried with one sim and works,but data doesn't,and can't configure apn because there is empty and can't do nothing.
i think i'm done with this stuff.
thanks for reply.
@mattnmag even though I didn't need your help. You definitely went above and beyond. Since he couldn't say thank you. I will, Nice explanations and good links to previous threads!
Had issues rooting but I think I did it. Now trying to install TWRP.
With phone in Download mode the tiny writing tells me the version is N910v as in, Verison developers
In About Device it says, SM-N910F
Baseband version - N910FXXU1BOC4
Build number - N910FXXU1BOC5
I've been trying to do and understand all the stuff required to install the latest Cyangenmod, but Odin keeps failing and maybe it is because I thought I was using the packages for SM-N910f.
Sorry if this doesn't make total sense, or I've missed things out - have been trying to do this for about 6hrs and got not very far.
Any advice as to which version my phone is, or other ideas why Odin might keep failing. Because phone isn't actually rooted?
Thank you for your trouble.
Hi install
Phoninfos from playstor
Cyanogen does not install with odin.
What verse of odin?
Open the odin init file then
The Deviceinfos line = 0
For deviceinfos = 1 save the changes.
Reopen odin, option, then check device info, put your mobile in donload mode, connect to odin then click start, you just have to read the log on screen.
Hit the button thank you if it helped you.
Hi.
I got a pretty good deal on a S9+ (Korean version) and when I got it I saw it has TWRP as recovery and perhaps some custom rom installed in it (I don't really know).
I would like to leave it stock, as it comes from fabric, to get OTA updates and passing safetynet (very important to me).
What things do I need to do?
Thank you :good:
SkyLey said:
Hi.
I got a pretty good deal on a S9+ (Korean version) and when I got it I saw it has TWRP as recovery and perhaps some custom rom installed in it (I don't really know).
I would like to leave it stock, as it comes from fabric, to get OTA updates and passing safetynet (very important to me).
What things do I need to do?
Thank you :good:
Click to expand...
Click to collapse
if it has TWRP on it, 99% sure its rooted and therefore wont pass safety net. You can get it up and running and get magisk installed to hide root from the vast majority of apks that would be affected by root.
youdoofus said:
if it has TWRP on it, 99% sure its rooted and therefore wont pass safety net. You can get it up and running and get magisk installed to hide root from the vast majority of apks that would be affected by root.
Click to expand...
Click to collapse
Just ran RootChecker and it said it is not rooted.
Actually I'm not even interested in rooting. Just want it clean as from fabric.
I guess I have to flash its stock rom and recovery and closing the bootloader, but I have no idea how to. Any help?
Reboot to download mode and check the warranty state
i know you dont want to root due to the secure folder comment(errrr, safety net rahter)
im just saying that i bet it already has been rooted if it has TWRP on it, and youre likely out of luck
youdoofus said:
Reboot to download mode and check the warranty state
i know you dont want to root due to the secure folder comment(errrr, safety net rahter)
im just saying that i bet it already has been rooted if it has TWRP on it, and youre likely out of luck
Click to expand...
Click to collapse
Ok, this is its download mode:
https://i.imgur.com/YkzfQlv.jpg
I have no idea what all that means, lol
What things do I need to flash?
SkyLey said:
Ok, this is its download mode:
https://i.imgur.com/YkzfQlv.jpg
I have no idea what all that means, lol
What things do I need to flash?
Click to expand...
Click to collapse
flash this
https://www.sammobile.com/samsung/g...e/SM-G965N/KOO/download/G965NKSU1CSG2/282440/
bot download it with one of these
Samfirm
or this (newer prettier GUI, but its the exact same result with either tool)
Frija
youdoofus said:
flash this
https://www.sammobile.com/samsung/g...e/SM-G965N/KOO/download/G965NKSU1CSG2/282440/
bot download it with one of these
Samfirm
or this (newer prettier GUI, but its the exact same result with either tool)
Frija
Click to expand...
Click to collapse
it won't work
https://imgur.com/LZdLH9m
I also tried Samfrim but it displays an error too-
Error loading library: 14001
Please make sure "Microsoft Visual C++ 2008 Redistributable Package (x86)" and "Microsoft Visual C++ 2010 Redistributable Package (x86)" are installed
Error: Could not send BinaryInform. Status code 200/401
Authorization failed
Could not fetch info for SM-G965N/SKC. Please verify the input or use manual info
SkyLey said:
it won't work
https://imgur.com/LZdLH9m
I also tried Samfrim but it displays an error too-
Error loading library: 14001
Please make sure "Microsoft Visual C++ 2008 Redistributable Package (x86)" and "Microsoft Visual C++ 2010 Redistributable Package (x86)" are installed
Error: Could not send BinaryInform. Status code 200/401
Authorization failed
Could not fetch info for SM-G965N/SKC. Please verify the input or use manual info
Click to expand...
Click to collapse
install ADB drivers and reboot
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
View attachment 4846361
SkyLey said:
it won't work
https://imgur.com/LZdLH9m
I also tried Samfrim but it displays an error too-
Error loading library: 14001
Please make sure "Microsoft Visual C++ 2008 Redistributable Package (x86)" and "Microsoft Visual C++ 2010 Redistributable Package (x86)" are installed
Error: Could not send BinaryInform. Status code 200/401
Authorization failed
Could not fetch info for SM-G965N/SKC. Please verify the input or use manual info
Click to expand...
Click to collapse
please use the image upload on the forum itself vs imgur. I cant access imgur at work (where i currently am) and the forum now allows for pics to be attached almost regardless of size
youdoofus said:
install ADB drivers and reboot
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
OK, at the end I downloaded the ROM from the sammobile link you provided me (https://www.sammobile.com/samsung/g...e/SM-G965N/KOO/download/G965NKSU1CSG2/282440/)
I know you told me to not download from it but anyways... I flashed that ROM using Odin and well everything seems normal and working, but Safetynet still won't pass.
I checked on developer settings and the bootloader was still unlocked so I relocked it but... still nothing. Safetynet just won't pass.
What could be happening?