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!
Related
Hey everyone, so I tried rooting the device with 4zroot and SuperOneClick both methods don't work. With 4zroot, when push root, the program backs out and force closes. With SuperOneClick, the program got stuck at "Waiting for device..." for over 15 minutes. I also gone and double-check every setting is in the correct order. I tried several times with both methods and failed. So do you have any ideas on getting root access on this device. Thank you.
Firmware version: 2.2.2
Kernel version: 2.6.32.9 [email protected]#1
Build number: FROYO.DXKF3
Edit1: Rooted successfully!! After trying about every suggestions i could find, i couldn't connect to kies, it said pc suite mode need to be activated, but there's no option for that in the 5.0 wifi, but after internal memory format and factory setting reset, i connect to pc (pc recognize, but kies didn't) i use the SuperOneClick and BAM! it is rooted!!
You use the program that I want to try some of the root. Now I have a problem with kies it invisible to me to me.
Another rooted Galaxy YP-G70
Device Info:
Model number: YP-G70CW (on the back of the device)
Firmware ver: 2.2.2
Kernel ver: 2.6.32.9 [email protected] #12
Build number: FROYO.ZSKE2
Tools:
1. Install SAMSUNG USB Driver for Mobile Phones
2. SuperOneClick version 2.1.1
i confirm, today i've rooted my galaxy s wifi 5 with super one click in a minute!
i just got this device it's great the screen is huge, so i'm glad it can be rooted. the question is can i restore it to factory state? how do i backup the ROM?
ronnieg said:
i just got this device it's great the screen is huge, so i'm glad it can be rooted. the question is can i restore it to factory state? how do i backup the ROM?
Click to expand...
Click to collapse
in the superoneclick menu there is the voice "unroot", so it's very simple!
root yp-g70
sorry i have this phone i want to rooted but i don´t know ho to do it anyone can help me
josetup123 said:
sorry i have this phone i want to rooted but i don´t know ho to do it anyone can help me
Click to expand...
Click to collapse
You have to use superoneclick. It's so userfriendly, perfect for a newbye.
Don't worry, let's try !
Inviato dal mio YP-G70 usando Tapatalk
WT Ho said:
Device Info:
Model number: YP-G70CW (on the back of the device)
Firmware ver: 2.2.2
Kernel ver: 2.6.32.9 [email protected] #12
Build number: FROYO.ZSKE2
Tools:
1. Install SAMSUNG USB Driver for Mobile Phones
2. SuperOneClick version 2.1.1
Click to expand...
Click to collapse
get give download link for the SAMSUNG USB Driver for Mobile Phones installer? thanks
mustikasakti said:
get give download link for the SAMSUNG USB Driver for Mobile Phones installer? thanks
Click to expand...
Click to collapse
here it is your drivers! http://forum.xda-developers.com/showthread.php?t=961956
Hello everyone I can not rooter my samsung galaxy s wifi YP-5.0 g70 g70
someone can help me thank you
manu17300 said:
Hello everyone I can not rooter my samsung galaxy s wifi YP-5.0 g70 g70
someone can help me thank you
Click to expand...
Click to collapse
what's the problem?
Stuck at Step#1
I can't get my Samsung galaxy S 5 wifi rooted either. First I was getting stuck on detecting the device like the OP. Then I installed the latest drivers from the link tapioco2000 provided (Thanks tapioco2000!). Now I can see the device when I type "adb devices". And Super One Click now progresses to Step #1. But now it's stuck there trying to temporary install busybox. I tried the Shell Root method as well. But there I get stuck at step #1 as well.
Any help would be appreciated. Thanks.
got mine rooted! Now what's the best rom to install?!
Need to be careful about the ROMS, you can download the stock ROM currently and it is easy to root. Don't forget to enable USB debugging.
I bricked mine after some root tweaking, and was able to restore using ODIN and the original firmware.
os2baba said:
I can't get my Samsung galaxy S 5 wifi rooted either. First I was getting stuck on detecting the device like the OP. Then I installed the latest drivers from the link tapioco2000 provided (Thanks tapioco2000!). Now I can see the device when I type "adb devices". And Super One Click now progresses to Step #1. But now it's stuck there trying to temporary install busybox. I tried the Shell Root method as well. But there I get stuck at step #1 as well.
Any help would be appreciated. Thanks.
Click to expand...
Click to collapse
So no one else is stuck with rooting the device? Especially at Step #1 where it can't seem to install busybox?
Make sure you are in USB debug mode and have allow non-market installations checked. See if that helps any.
Ishman said:
Make sure you are in USB debug mode and have allow non-market installations checked. See if that helps any.
Click to expand...
Click to collapse
Yes both are set.
problem root my device - superuser will not install to device?
After rooting i can not find superuser from programs list?
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 1,59s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4,06s
Waiting for device...
OK 0,03s
2.2.2
Getting manufacturer...
samsung
OK 0,04s
Getting model...
YP-G70
OK 0,04s
Getting version...
XXKG1
OK 0,04s
Checking if rooted...
True
OK 0,06s
Installing BusyBox (temporary)... - Step #1
708 KB/s (1062992 bytes in 1.465s)
OK 1,51s
Installing BusyBox (temporary)... - Step #2
OK 0,05s
Rooting device... - Step #1
295 KB/s (585731 bytes in 1.937s)
OK 1,97s
Rooting device... - Step #2
OK 0,04s
Rooting device... - Step #3
OK 0,01s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 0,06s
Rooting device... - Step #5
OK 8,08s
Remounting /system with read-write access...
OK
OK 0,10s
Creating /system/xbin...
mkdir failed for /system/xbin, File exists
OK 0,05s
Installing su (/system/xbin)... - Step #1
328 KB/s (26264 bytes in 0.078s)
OK 0,54s
Installing su (/system/xbin)... - Step #2
OK 0,05s
Installing su (/system/xbin)... - Step #3
OK 0,04s
Installing SuperUser... - Step #1
176 KB/s (196521 bytes in 1.089s)
OK 1,32s
Checking for busybox
OK 0,04s
Remounting /system with read-only access...
OK
OK 0,34s
Running a SU test...
Test failed!
FAILED
Did anyone try installing a standard Galaxy S ROM on it? I mean, it seems to be the same hardware sans the phone/3G transmitter, no?
The rooting may or may not be working. Trying to use casual to update my phone but I get he "Noob" error, when I try to update to their bootloader I get the sboot.bin fail. Not sure where to go with this, downloading the huge 1605VRLJB file but that shoudl not be the issue. Any ideas?
For use with Verizon Galaxy Note 2 ONLY! This CASUAL is designed to assist with unlock and provide other services to Verizon Galaxy Note 2 owners.
--Suck It Verizon--
This exploit was designed by Ralekdev, AdamOutler and Rebellos, it will work with I605VRALJB. For best results you should flash Revision by AdamOutler as a baseline before attempting this exploit. See XDA-Developers.com for more. Link: http://goo.gl/a1HMS
mkdir failed for /data/local/tmp, File exists
Pushing dependencies
Pushing su binary...
4727 KB/s (91980 bytes in 0.019s)Pushing SuperSU app...
5042 KB/s (996704 bytes in 0.193s)Pushing Exynos-Abuse exploit
4835 KB/s (64373 bytes in 0.013s)Pushing root script
176 KB/s (361 bytes in 0.002s)Pushing Busybox
4774 KB/s (1867568 bytes in 0.382s)Pushing viewmem
1763 KB/s (5417 bytes in 0.003s)Pushing raw exploit code
54 KB/s (56 bytes in 0.001s)Setting Permissions....
Executing Root Exploit.
[*] s_show->seq_printf format string found at: 0xC086C348
[*] sys_setresuid found at 0xC00967C4
[*] patching sys_setresuid at 0xC0096808
[!] set user root failed: Operation not permitted
Your device should be rooted. If you have upgraded past VRALJB firmware the exploit may not function properly.
CASUAL requires a reboot because we look at the memory logs after the device boots to verify proper bootloader version.
rebooting...
[x]Ready for exploit
[x]Found rooted device
[INFO] Reading 512 bytes at 0x40000200...
HellNo
IMPROPER BOOTLOADER VERSION DETECTED. FOLLOW DIRECTIONS NOOB! GUYS LIKE YOU ARE THE REASON DEVELOPERS HAVE SO MUCH PROBLEMS!!!!!! DO YOU REALIZE WHAT IT TAKES TO MAKE SOMETHING LIKE THIS COME TOGETHER?? AND HERE YOU ARE JUST TRYING TO SCREW THINGS UP.... DAMNIT! GET OFF THE INTERNET!
So uhhh....
Is there a question somewhere in there?
God bless the American people.
That looks like the old unlock process are you using the jail break method
Sent from my SGH-T889 using Tapatalk 2
kintwofan said:
That looks like the old unlock process are you using the jail break method
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Right now I have rooted based on the [GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II then tried to apply casual, which fails due to the incorrect bootloader. I am unable to restore a stock rom, and I can not change that ****ing bootloader. So right now I can not unlock with the casual method. I get that noob error. Anyway to fix this?
I'm trying the new method, assuming that is the post jan 26th post. One person recommended finding the alternative recovery with out sboot.bin. I have not found that yet, root66 seems to be the only one that is working.
Yeah I got crazy frustrated with this one. Here goes. So I booted into odin, which needed the kies driver is memory serves. Ran the Root66 in PDA. Then I rebooted my phone, went into the usb debugging and MTP for usb. Updated my phone, to VRALL4 like the normal OTA updates from VW. ran CASUAL-BackAtchaVerizon-Revision311b with java (build 1.7.0_17-b02). The damn thing went through. Not trying to run sboot.bin through odin. As far as the guides go, you need to click the generic serial to be replaced in casual. Also some guides didnt show what state the phone was in for casual. Just boot up the phone like normal. I'm trying to figure out what other snags i ran into...
Sigh.. I've had a roller coaster ride with these ROMs and trying them out and making mistakes over and over again and I'm tired of fixing them till 5 am... So at the moment my phone is on VRALL4 not rooted... Only because Casual wont let me root which is one of the reasons why I'm taking a serious break from all of this nonsense... I want to go completely Stock with VRAMC3... I read this on droidstyles post:
"2) If you flashed custom software on your device without unlocking, please refer to Section 1B of my GUIDE in development section(*Take note to only use the ALTERNATE RESTORE FILE if your device has or previously had the VRALL4 or VRAMC3 update applied)!! Reason being the latest update black listed the first VRALJB bootloader, so you can not ever go back to this bootloader version. However you can still use the VRALJB factory image that does not have the bootloader( ALTERNATE RESTORE FILE) that is linked in my guide. This will bring your device back up and running in stock condition!! "
Now.. I've done this and it won't let me update to VRAMC3.. If I try it just says "Update Failed" so I'm not quite sure how but is there any way I can just get my phone perfectly 150% Stock ?
I initially tried the latest Casual by the way... Got this message probably because this is version is meant for VRAMC3?
Pushing Exynos-Abuse exploit
[CRITICAL]1
1
java.lang.ArrayIndexOutOfBoundsException: 1
java.lang.ArrayIndexOutOfBoundsException: 1
at CASUAL.CASUALInteraction.showUserCancelOption(CASUALInteraction.java:144)
at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:305)
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:66)
at CASUAL.CASUALScriptParser$1.run(CASUALScriptParser.java:122)
at java.lang.Thread.run(Unknown Source)
A critical error was encoutered. Please copy the log from About>Show Log and report this issue
[CRITICAL]CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
java.lang.RuntimeException: CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
java.lang.RuntimeException: CASUAL scripting error
push "$ZIPFILEexynos-abuse" /data/local/tmp/
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:73)
at CASUAL.CASUALScriptParser$1.run(CASUALScriptParser.java:122)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
at CASUAL.CASUALInteraction.showUserCancelOption(CASUALInteraction.java:144)
at CASUAL.CASUALLanguage.commandHandler(CASUALLanguage.java:305)
at CASUAL.CASUALLanguage.beginScriptingHandler(CASUALLanguage.java:66)
... 2 more
A critical error was encoutered. Please copy the log from About>Show Log and report this issue
CASUAL experienced an error while parsing command:
push "$ZIPFILEexynos-abuse" /data/local/tmp/
please report the above exception.
Script Complete
And so.. I tried an older version.. "Back Atcha Verizon Revision 465b" and got this message
ERROR: No partition with identifier "60" exists in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
[Heimdall Error Report] Detected:
Heimdall uncontinuable error; Script halted
[/Heimdall Error Report]
done
Comfy95 said:
ERROR: No partition with identifier "60" exists in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
[Heimdall Error Report] Detected:
Heimdall uncontinuable error; Script halted
[/Heimdall Error Report]
done
Click to expand...
Click to collapse
It seems to me that if I want to go completely stock I'll need to address this issue... So maybe start there? I don't know.. You guys certainly know more than I do so if you can help that'd be great..
If I'm reading your first post correctly, you WERE "150%" stock. Going to an older android version does not make you more "stock" - in fact going back to an older system version would be "less stock" using your terms.
I think more reading and less tinkering would do you best. Or reference one of the other 1, 283, 312 other "going back to stock" threads in every category of this forum.
Sorry to come across as a jerk, but when you see the same damn question asked in a million different threads (including STICKIES) you start to get annoyed.
SEARCH. READ. STUDY. LEARN.
Sent from my SCH-I605 using Tapatalk 4 Beta
1ManWolfePack said:
SEARCH. READ. STUDY. LEARN.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Can you do it for me?
I would say you should coin SRSL, but then I realized you would be getting hundreds of replies asking what it means
1ManWolfePack said:
If I'm reading your first post correctly, you WERE "150%" stock. Going to an older android version does not make you more "stock" - in fact going back to an older system version would be "less stock" using your terms.
I think more reading and less tinkering would do you best. Or reference one of the other 1, 283, 312 other "going back to stock" threads in every category of this forum.
Sorry to come across as a jerk, but when you see the same damn question asked in a million different threads (including STICKIES) you start to get annoyed.
SEARCH. READ. STUDY. LEARN.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well my problem is that I want to be on VRAMC3 without anything modded whatsoever.. Like they blacklisted the bootloader I think it was and I imagine thats whats keeping me from OTA updating from VRALL4 to VRAMC3 thats why I made this post.. I can go back to stock VRALL4 all day long with this assumed bootloader problem but thats just the thing... I don't want to have anything anywhere be even somewhat modded... and when I said 150% stock I was referring to when I had first bought my phone and all the files were legit and untouched and I was on the up-to-date VRALL4...
go back to stock vrall4, root and unlock, then flash beans stock rooted vramc3 in recovery...its no different than the OTA other than root.
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.
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.