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...
Related
ok i am on EA28 looking to root tried some many methods and lost i rooted phone jail broke them unlocked them never had this much issues.
i tried z4root, this way..... i see no where it talks about sdk or anything help me please
Dirt_Mcgirt said:
ok i am on EA28 looking to root tried some many methods and lost i rooted phone jail broke them unlocked them never had this much issues.
i tried z4root, this way..... i see no where it talks about sdk or anything help me please
Click to expand...
Click to collapse
Forget about all of it.
Download Shortfuse.
http://forum.xda-developers.com/showthread.php?t=803682
Then open it.
Plug your phone to Computer (Make sure the USB debugging is on)
Then press Root.
When you are done, there should be pop-up saying would you like to test if the root was successful? Click yes, read the msgs if you are rooted.
It's simple as that.
If I helped you, press Thanks button at bottom right.
no go keeps hanging up.....
Getting mount path...
rootfs / rootfs rw 0 0
FAILED
SuperOneClick v1.8.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting OS Version...
OK
Pushing psneuter...
558 KB/s (585731 bytes in 1.025s)
OK
chmod psneuter...
OK
Running psneuter...
ROOTED
Pushing busybox...
394 KB/s (1062992 bytes in 2.631s)
OK
chmod busybox...
OK
Getting mount path...
rootfs / rootfs rw 0 0
FAILED
Is your phone sleeping during the process? I had issues if my screen went off.
If you still can't root you could always just Odin an already rooted image or the CWR....Though if you can't get root to work it might not be the best thing to suggest to you to flash stuff........
eah i rather not flash till i am rooted if i can avoid it lol n my phone isnt sleeping either
why dont you just get an already rooted rom? look for them in the development section, dont worry about rooting it yourself.
jorge3687 said:
why dont you just get an already rooted rom? look for them in the development section, dont worry about rooting it yourself.
Click to expand...
Click to collapse
i can do that but i like to root it myself just for the know how yeah i can use odin right?
i unlocked bootloader with teh asus unlock tool. I then rooted using the debugfsroot method found in the stickies. everything went well Or so i thought. After all rebooting was done i went into app folder and the superuser app was in there so i thought that i was rooted. Went to install twrp through goo manager and it said it couldn't get root permissions adn that i wasn't rooted. So i downloaded titanium backup to backup my apps and when i opened it it too said i wasn't rooted or that busybox wasn't downloaded. I downloaded busy box from the market and tried to install it and same thing....any one know what's up?
try rooting again with the same method and post what the cmd says after you are done with it~
lil-devil said:
try rooting again with the same method and post what the cmd says after you are done with it~
Click to expand...
Click to collapse
ok doing that now
here's what is says...
Installing Superuser.apk...
891 KB/s <843503 bytes in 0.924s>
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Rebooting...
Once your Prime reboots, it will be rooted!
Press any key to continue...
vballrkc said:
here's what is says...
Installing Superuser.apk...
891 KB/s <843503 bytes in 0.924s>
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
Rebooting...
Once your Prime reboots, it will be rooted!
Press any key to continue...
Click to expand...
Click to collapse
UPDATE: After the second root now everything i described above is requesting superuser permissions so it appears all is well. If i have problems i will repost. Thank you for your response though i guess it just didn't stick the first time.
i'm glad that it works now
Hello,
i have a litle problem with the method above everything went ok .. i have root acces i think :'(
but the problem is that almost all applications started to crash, force close ro stoped running at all.
everything that was working before the root is broken somehow
any way to fix this ,???
i would suggest you to try unrooting with the root keeper app
if that doesn't work try reseting your tab via the pin hole under the SD card
if that still doesn't solve the problem default the tf201~
Ahem, OP, you do realize your bootloader is unlocked? That your warranty is void? That you no longer can receive otas? It's failing to push superuser.apk because it's already there. seems to me that you may need just to update su binary in superuser app. To start over, you need to uninstall Superuser app (if you can). If chainsdd su binary has been installed correctly with the right permissions, then you should be able to get root through adb, and then remount /system as rw, and remove Superuser.apk from /system/app.
Whats done its done. Stop wasting time. Check out the sticky for nvflash in the dev thread (read the whole thread, seriously) and get some nvflash goodness, better safe than sorry.
After that, continue to learn the ways of fastboot (if you use a toolkit, it's considerably harder to troubleshoot when things go wrong, to see where it failed, that's why you opened this thread, you don't know what went wrong), flash latest cwm or twrp through fastboot, flash a custom rom (after factory reset in cwm/twrp, naturally) with cwm/twrp, which will have root. and a whole lot more good things. if you don't want to go custom rom just yet and stick with modified (pre-rooted!) stock roms (made for unlocked bootloaders). all of this can be found in the dev thread, as you probably know.
If you're unlocked, the whole thing gets easier.
If you really want to stick with an (tweaked) asus stock rom, even unlocked, for some unknown-to-human-race reason, you may just download a superuser/supersu cwm/twrp (flashable) zip, copy it to the internal sdcard, boot a custom recovery (which also has root) through fastboot, flash that zip you copied before, and reboot system. you'll be rooted. an exploit is only needed when device is not unlocked.
# rant
# Damn, being unlocked/with a real safety net software wise feels GOOD!
sent from my tf201
bk201doesntexist said:
Ahem, OP, you do realize your bootloader is unlocked? That your warranty is void? That you no longer can receive otas? It's failing to push superuser.apk because it's already there. seems to me that you may need just to update su binary in superuser app. To start over, you need to uninstall Superuser app (if you can). If chainsdd su binary has been installed correctly with the right permissions, then you should be able to get root through adb, and then remount /system as rw, and remove Superuser.apk from /system/app.
Whats done its done. Stop wasting time. Check out the sticky for nvflash in the dev thread (read the whole thread, seriously) and get some nvflash goodness, better safe than sorry.
After that, continue to learn the ways of fastboot (if you use a toolkit, it's considerably harder to troubleshoot when things go wrong, to see where it failed, that's why you opened this thread, you don't know what went wrong), flash latest cwm or twrp through fastboot, flash a custom rom (after factory reset in cwm/twrp, naturally) with cwm/twrp, which will have root. and a whole lot more good things. if you don't want to go custom rom just yet and stick with modified (pre-rooted!) stock roms (made for unlocked bootloaders). all of this can be found in the dev thread, as you probably know.
If you're unlocked, the whole thing gets easier.
If you really want to stick with an (tweaked) asus stock rom, even unlocked, for some unknown-to-human-race reason, you may just download a superuser/supersu cwm/twrp (flashable) zip, copy it to the internal sdcard, boot a custom recovery (which also has root) through fastboot, flash that zip you copied before, and reboot system. you'll be rooted. an exploit is only needed when device is not unlocked.
# rant
# Damn, being unlocked/with a real safety net software wise feels GOOD!
sent from my tf201
Click to expand...
Click to collapse
So many things to respond to here, how about i just choose that if you would actually read the progression of this thread instead of just reading the first post and then skipping the next 9 posts and proceeding to rant to make yourself feel better then others, you would realize the problem has been fixed and all is good and that really none of what you wrote was A. relevant to my problem and B. helpful at all. Thanks. have a nice day.
vballrkc said:
So many things to respond to here, how about i just choose that if you would actually read the progression of this thread instead of just reading the first post and then skipping the next 9 posts and proceeding to rant to make yourself feel better then others, you would realize the problem has been fixed and all is good and that really none of what you wrote was A. relevant to my problem and B. helpful at all. Thanks. have a nice day.
Click to expand...
Click to collapse
I actually had good intentions, but now I don't freaking care what you think: Don't use sarcasm on me boy. BTW, no sarcasm here: You'll never learn anything if you keep using toolkits.
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.
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!
Title says it all. I haven't gotten past root because every rooter I try fails. Tried rooting on 4.5.5.1 and .2, hoping .3 would solve any issues but it didn't. Really hoping to get a custom ROM on this thing, if anyone could help, much appreciated..
WSADKeysGaming said:
Title says it all. I haven't gotten past root because every rooter I try fails. Tried rooting on 4.5.5.1 and .2, hoping .3 would solve any issues but it didn't. Really hoping to get a custom ROM on this thing, if anyone could help, much appreciated..
Click to expand...
Click to collapse
No need to pre-root. Go for one of the bootloader unlock methods and profit.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Davey126 said:
No need to pre-root. Go for one of the bootloader unlock methods and profit.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Click to expand...
Click to collapse
Your first link shows root as a pre-requisite? Is it still not necessary?
WSADKeysGaming said:
Your first link shows root as a pre-requisite? Is it still not necessary?
Click to expand...
Click to collapse
It is not. This post offers nice summary of the necessary steps including required files.
Davey126 said:
It is not. This post offers nice summary of the necessary steps including required files.
Click to expand...
Click to collapse
I get this error when I run get_code.bat even though running 'adb devices' shows my hdx.
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to copy 'cuber' to '/data/local/tmp/cuber': couldn't read from device
cuber: 0 files pushed. 0.1 MB/s (506072 bytes in 5.020s)
error: no devices/emulators found
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
Press any key to continue . . .
WSADKeysGaming said:
I get this error when I run get_code.bat even though running 'adb devices' shows my hdx.
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to copy 'cuber' to '/data/local/tmp/cuber': couldn't read from device
cuber: 0 files pushed. 0.1 MB/s (506072 bytes in 5.020s)
error: no devices/emulators found
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
Press any key to continue . . .
Click to expand...
Click to collapse
Choices:
- do some basic troubleshooting to resolve the issue (first line offers a clue)
- use the 1-click method
Although preferable you do not need to execute get_code.bar prior to flashing the vulnerable bootloader (aboot) which is where the real magic lies. That said, a mistake at this stage can result in a black screen 'soft-brick' that is difficult to recover. Probably best to stick with 1-click.
Davey126 said:
Choices:
- do some basic troubleshooting to resolve the issue (first line offers a clue)
- use the 1-click method
Although preferable you do not need to execute get_code.bar prior to flashing the vulnerable bootloader (aboot) which is where the real magic lies. That said, a mistake at this stage can result in a black screen 'soft-brick' that is difficult to recover. Probably best to stick with 1-click.
Click to expand...
Click to collapse
Called in sick to work to spend the rest of the day googling my way thru this process and got it to 7.1.2
Sorry guys. I have exactly the same issue as in post #5 above. I do not want a one click type of solution. I would like to understand what the problem is and how to get the right drivers to fix the damn thing. I tried a dozen different drivers, installed correctly, with full reboots, etc, and nothing gets into that device. I use Windows 10. Thank you for any positive thought and solution.
[Thor][Apollo] Unlocking bootloader with any firmware
Hello. At first, I did not invent anything new, just checked some my guess on a other motherboard. All thanks and credits to our great developers. As always, all at your own risk. It does not work on the Fire HDX 8.9 (Saturn)! All steps in this...
forum.xda-developers.com
Reichmann aka realm mann, had the easiest guide imo.
Got a apollo unlocked and twrp'd in 30 minutes.
But take note you are expected to rename aboot file to "aboot_vuln.mbn"
And twrp to whatever the guide prints for the dd command. (I dont recall but just rename your twrp file to whatever that dd command references.)
Doesnt matter what windows. Or at least worked a treat on win7 for me. Reichmann used 10.
Make sure your key code file is generated or if you continue might be bricked judgjng from other posts.
Make sure you typed the commands exactly. Wmic commands are easy to mess up and could be confusing.
If you get an error double check every character of text.
Your disk index result number from wmic command replaces the X after Harddisk in dd command.
But if you dont get the same disk index result from all 3 wmic command or an error? Probably mistyped. Like "partiton".
Just double check and proof read.
Doesnt matter if you do mistype it as long as you retype it correctly eventually.