sgh I337 trouble flashing ROM - Android Q&A, Help & Troubleshooting

hey everyone! this was my 1st time playing with modding my android device,I must say it's so fun and I'm hooked! so i have :
ATT sgh I337 with android 4.4.4 Nj4
rooted with kingroot
i have tried to load cm11 from the ext sd card, i did tons of research and read all the guides. I think my problem lies with the bootloader. I still have a secure bootloader status. I looked into safestrap, and even though i installed it, and it said it was complete, upon recover boot, it did not load. I have had crazy problems trying to get ADB working because i am running windows 8.1 on my laptop After all this, my google play services / framework is jacked up, because google play cannot connect to their server. but my main goal was to load a good ROM like CM 11 and be able to have more control over my device's operations. any advice or comments for me are appreciated, I'm fairly sure my problem is the bootloader, from what i read about this phone and att

bo0ts said:
hey everyone! this was my 1st time playing with modding my android device,I must say it's so fun and I'm hooked! so i have :
ATT sgh I337 with android 4.4.4 Nj4
rooted with kingroot
i have tried to load cm11 from the ext sd card, i did tons of research and read all the guides. I think my problem lies with the bootloader. I still have a secure bootloader status. I looked into safestrap, and even though i installed it, and it said it was complete, upon recover boot, it did not load. I have had crazy problems trying to get ADB working because i am running windows 8.1 on my laptop After all this, my google play services / framework is jacked up, because google play cannot connect to their server. but my main goal was to load a good ROM like CM 11 and be able to have more control over my device's operations. any advice or comments for me are appreciated, I'm fairly sure my problem is the bootloader, from what i read about this phone and att
Click to expand...
Click to collapse
Edit solved with flahfire

Related

[Q] Virgin (ZTE) Awe ROM?

Hi there,
I just obtained a new Moto G which I am planning to use from now on, and I decided it would be beneficial to root my old phone -- Virgin (ZTE) Awe (N800) -- and try to gain some experience in the field of development. Mainly, however, I just wanted to upgrade the OS. I successfully rooted the phone using Kingo Android root; then I went on to try to install Cyanogenmod 11. However, it said my phone was unsupported.
Next step -- do it manually. So I downloaded the Android SDK and tried to get ABD running -- with no luck -- as I was trying to use abd sideload to load the OS file for Android 4.2 (but for Nexus 7). However, with failure after failure of trying to load abd, I has to ask myself: Will I brick my phone?
So, any thoughts? Are ROMs phone-specific? Can I get a better ROM for this phone? Would I brick it if I tried to load another phone's rom?
Any help/advice greatly appreciated!
Jhdoubleoseven said:
Hi there,
I just obtained a new Moto G which I am planning to use from now on, and I decided it would be beneficial to root my old phone -- Virgin (ZTE) Awe (N800) -- and try to gain some experience in the field of development. Mainly, however, I just wanted to upgrade the OS. I successfully rooted the phone using Kingo Android root; then I went on to try to install Cyanogenmod 11. However, it said my phone was unsupported.
Next step -- do it manually. So I downloaded the Android SDK and tried to get ABD running -- with no luck -- as I was trying to use abd sideload to load the OS file for Android 4.2 (but for Nexus 7). However, with failure after failure of trying to load abd, I has to ask myself: Will I brick my phone?
So, any thoughts? Are ROMs phone-specific? Can I get a better ROM for this phone? Would I brick it if I tried to load another phone's rom?
Any help/advice greatly appreciated!
Click to expand...
Click to collapse
ROMS are phone specific do your research google your phone virgin mobile awe n800 and after you type that just type xda there are roms for uour phone but after you root you need a recovery make sure your sd card will be sufficient to hold all of your backups and data

[Q] I think I've got it? (from root to rom)

From many many different threads and frankly confusing instructions I think I have puzzled together the following solid guideline for my kindle fire hdx from basic root to custom rom. Currently my firmware is 13.3.1.0.
Could someone take a look at this and tell me if I got this right or if I need to do stuff differently (or could do them better)? Don't assume that something is obvious, if it isn't written down, don't be shy to mention it. I would be ever so grateful .
Edit: I'm updating my experience as I move along the list and get more info just in case this might be useful to someone who is just as lost as I was in the beginning
Obligatory disclaimer: this is just a step-by-step guideline that worked for me. I'm not responsible if you chose to follow any of these steps and damage or brick your device.
Guideline:
-Download firmware version 3.2.3.2 and upgrade directly from any of the previous version by putting the file into the internal storage of the kindle, going to settings>device>system update on the kindle and installing the update from there.
-Root with Towelroot in the HDX toolkit downloaded from here (Edit: I got various error messages at this step but got it to work in the end. The 3rd post here shows what I did to get it working after getting error message 2 and 3 at various times)
-block OTA also with the tool in the HDX toolkit (is there a way to safely check that this worked? Edit: It worked )
-connect to wifi and install Flashify from the playstore (Edit: I ended up installing File Expert and flashify on another android device, backing up the flashify apk and sideloading it with ES File Explorer from the amazon app store to the kindle, I guess I could have also download the apk somewhere but I have trust issues.)
-download the img of TWRP 2.8.5.0. and put it in internal storage of kindle (had no problems)
-use flashify to save original stock recovery (had no problems)
-Use flashify to flash TWRP (had no problems)
- Boot into recovery mode via flashify to see if it worked (had no problems)
Now either A)
-download CM11 image and gapps and put the zip files on internal storage
-Edit: disconnect Kindle from USB afterwards
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- flash cm11 image and gapps (under install and then find them in the files)
- reboot
-Edit: I had the wifi not connecting problem that some people have with CM11 but a reboot took care of it.
-Edit 2: I couldn't get the kindle app to work on CM11 (it wouldn't synch my books, the device wasn't recognized by amazon and it would crash every time I logged in.) so I ended up replacing it with the Nexus rom. If the chance of this happening doesn't bother you then CM11 seems to still be a good choice.
or B)
- download HDX thor nexus rom and gapps and put the zip files on internal storage
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- Edit: disconnect Kindle from USB afterwards
- flash nexus rom and gapps (under install and then find them in the files)
- reboot
- Edit: I'm very happy with it, it works flawlessly. Since it's based on Jelly Bean I may try replacing it with another rom sometime in the future, but I'm in no hurry
Mostly correct, you can update directly to 3.2.3.2 no need for incremental steps. The only way to know if ota blocker worked is to check for update but there's really no need, as soon as you've run towel root just disable WiFi as it won't be needed anymore.
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
uhraman said:
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
Click to expand...
Click to collapse
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
derpadoodle said:
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
Click to expand...
Click to collapse
Thanks for your replies! Is the method uhraman hinted at the better one?
snorklm said:
Thanks for your replies! Is the method uhraman hinted at the better one?
Click to expand...
Click to collapse
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
derpadoodle said:
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
Click to expand...
Click to collapse
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
snorklm said:
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
Click to expand...
Click to collapse
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Davey126 said:
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Click to expand...
Click to collapse
Thanks for the sound advice, I will probably never feel comfortable enough for that , especially because I haven't achieved much at all yet. I haven't even flashed TWPR yet.
Yay, I did it. CM11 seems to be working as intended! Thanks again for everyone who replied and also to everyone who put so much work into making and improving all the tools and software necessary to make this kind of thing even possible, I appreciate it!
What firmware were you on to begin your process mate... ?
B3NJY said:
What firmware were you on to begin your process mate... ?
Click to expand...
Click to collapse
I was on 3.0.5 when I got the device. Amazon didn't upgrade the firmware at all before sending it out, then I upgraded to 13.3.2.3. Why do you ask?
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
snorklm said:
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
Click to expand...
Click to collapse
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Davey126 said:
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Click to expand...
Click to collapse
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
snorklm said:
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
Click to expand...
Click to collapse
Glad to hear everything is working well! My daily driver is on Nexus and I could not be happier. Everything works as it should. No need to unlock the bootloader unless you plan to do more modding. Enjoy your device!
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
johnwaters said:
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
Click to expand...
Click to collapse
Agreed, I was overwhelmed by all the different threads and possibilities at first. I ended up approaching it like any other research project for a paper or presentation and dumped every solid (and recent) piece of good advice into Evernote and sorting it out there. But writing and updating guides (especially with the fast development I have observed) would be a lot of work, I understand completely why no one would volunteer to do it and everybody would rather answer questions on a case by case basis.
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
dynein said:
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
Click to expand...
Click to collapse
First thing you want to do is block OTA (over the air updates) or your device may be upgraded by Amazon to a level that gives you less options. Suggest using HDX Toolkit (here) to both root and block OTA. Then install twrp (here). From there you can opt to replace Fire OS will several different roms including Nexus, CM11 or CM12.
Flashify is an app that allows flashing recovery and roms from from within Android vs adb or a recovery environment. You can grab it from the Play store or another market. It's a dangerous tool; use with extreme caution.
Be aware that any of the above actions, if executed incorrectly, can permanently brick your device with little/no hope of recovery (guess that's the definition of permanent). Read, read and read some more before taking any action. Be sure to keep WiFi off on your device until OTA is blocked to prevent auto-updates.

Kfhdx 7" 13.3.0.5

tldr;
So Optimal solution would be to get Gapps working on Stock 13.3.0.5, and from there I'll install and android launcher. But to do this, the Xposed problem will need to be fixed.
Has anyone else had a problem with Xposed where every menu leads to just a blank white screen?
Not-so-optimal would be to do all the upgrading, OTA blocking, flashing, and backing up to get it on like CM11 or something.
Hey all,
I just made my XDA account, I've been kinda lurking on the forums for a little while though.
I won a Kindle Fire HDX 7" (idk What gen or how to determine what gen it is. Its got 2gb RAM and 32gb Internal) that says its running 13.3.0.5 and so I decided to do a little research about custom roms and rooting and found this wonderful forum. I've had a bit of experience with custom roms, I loaded CM9 onto an LG Thrive (look that one up, its a bit of a pain to flash as well) And I'd love to see about flashing this brand new FHDX.
Now, I didn't purchase this tablet, so it is of no expense to me, however, I would rather not be reckless in my attempts to mess with it.
What I want:
Google Apps -- Play/Music/Gmail/Calendar/etc
Root
Android JB or KK OS or Android-like Launcher or Ubuntu Touch (idk about this one, it seems really cool, I've heard about it for a long time and never got the chance to play with it)
I'd love to stay away from bricks, but I'm not afraid of them enough to not flash it. I'm a computer engineer and kinda have some experience with android and flashing.
Now, as to my progress so far:
I've rooted it with towelroot and installed ES FileManager, SuperSU, and I've tried to install Xposed/HDXposed multiple times but it simply will not work correctly. Xposed gives me a white screen when I go into any of the menus and doesn't allow me to install after clicking "Framework". I've tried many different renditions of Gapps packages, but almost all of them result in a process failing or stopping.
Thanks and if you need more information or I've left something out, feel free to ask away!
b1nary
UPDATE:
I turned wifi on for a little bit and my Kindle decided it wanted to update, so now its running 13.3.2.5 :/
I've put it in airplane mode, and I'm thinking about doing this to downgrade it.
b1nary.v01d said:
UPDATE:
I turned wifi on for a little bit and my Kindle decided it wanted to update, so now its running 13.3.2.5 :/
I've put it in airplane mode, and I'm thinking about doing this to downgrade it.
Click to expand...
Click to collapse
I'm not sure what you're up to, but I'd suggest to downgrade to 3.1.0 using the procedure in the thread you linked to (be sure to scroll down for the procedure for 3.2.5/3.2.6 because you can NOT use the edited build number anymore!), then install TWRP, unlock the bootloader and flash a ROM of your choice.
You're up to that? Or what's on your mind?
Yea, sounds great! I'll post my progress as I get things going.
btw I love your name if its a play on Tom Clancy. Love those books and the games inspired by them!
b1nary.v01d said:
Yea, sounds great! I'll post my progress as I get things going.
btw I love your name if its a play on Tom Clancy. Love those books and the games inspired by them!
Click to expand...
Click to collapse
Alright, basic approach is here. Lots of info to read, so any questions just ask, before you brick your HDX.
I'm now Rooted running on 13.3.1.0
I've disabled OTA updates as well. From here I'll pick the rom I want to d/l, get TWRP installed, unlock bootloader with python/.unlock file, and flash the rom.
(I'll edit this post as I finish things)
Thanks!
b1nary.v01d said:
I'm now Rooted running on 13.3.1.0
I've disabled OTA updates as well. From here I'll pick the rom I want to d/l, get TWRP installed, unlock bootloader with python/.unlock file, and flash the rom.
(I'll edit this post as I finish things)
Thanks!
Click to expand...
Click to collapse
OK, don't forget to make a backup of Fire OS in TWRP (and move it to your PC) before you flash any custom ROM. Might be useful one day.
Alright!!
I'm backed up, unlocked, custom recovery'd, and flashed to the new Nexus KitKat 4.4.4!
Thanks so much for the help Cl4ncy both in this thread and all the others.
And thanks to the XDA community for hosting all these awesome tools!
Now to have some fun with my new psuedo-nexus 7" tablet >
b1nary

Nabi Big Tab 20 Stock Rom Request.

Long story short I modded my stock rom and only made a backup after I removed a bunch of system apps I knew were safe. Well youtube stopped working and my children like to watch you tube and Nabi release an update to patch their system to fix the youtube issue but I can not flash due to missing system files. Looking for stock unupdated or even updated rom for the nabi big tab 20 and help would be great. TWRP is the only recovery that I am aware of for this tablet.
Thanks in Advanced!
bump
Still Needing That Stock Rom?
I kinda did the same thing. So I just bought another Big Tab 20 to flash TWRP and backup the stock rom. I must mention at some point the Twrp Backups did not restore properly on the previous device. Dont know what happened. Im scared as hell to do this because it seems like theres no turning back to stock and this one cost me a cool $100.
Where I may find the stock rom or TWRP backup for this tablet?
I bricked this, just doing root and rename launcher and chrome apk in system folder, after this I get a bootloop.
And I need pinout a nabi connector, don`t have a usb cable..
Bringing this back from the DEAD
Hello,
I just got this Nabi BIG TAB HD - Model on device is bgtab-nv20a.
I am able to access recovery and select to wipe it, however when booting into Android it will ask for you to connect to the internet, regardless if you do it or not, a message will appear not allowing me to proceed, the error will be that it cannot connect to the FUHU server or that it cannot perform update and therefore cannot continue.
I am looking for either a way of rooting and flashing a custom ROM or simply get it to boot with the already installed Android system.
basementx said:
Bringing this back from the DEAD
Hello,
I just got this Nabi BIG TAB HD - Model on device is bgtab-nv20a.
I am able to access recovery and select to wipe it, however when booting into Android it will ask for you to connect to the internet, regardless if you do it or not, a message will appear not allowing me to proceed, the error will be that it cannot connect to the FUHU server or that it cannot perform update and therefore cannot continue.
I am looking for either a way of rooting and flashing a custom ROM or simply get it to boot with the already installed Android system.
Click to expand...
Click to collapse
If you can find a custom mom for this device please let me know lmfao. There's some extreme hardware packed under this really old device.

Trying to root Verizon Note 2 on 4.4.2 ND7... no dice | Update: Rooted successfully!

Massive update: I was able to root my phone successfully! Read my post below for detailed steps and why I think it worked!
Hi. New guy around. Disclaimer: I live in the Dominican Republic, using the Orange carrier, despite having a Verizon device.
I currently own a Verizon Galaxy Note 2 SCH-I605 which, until yesterday, was rooted and running a 4.3 stock ROM. Because of the Pokémon Go craze, I did my research and figured I could update the phone to 4.4, the minimum version required for Go. So I downloaded the Samsung software (running Win10 here), connected the phone, and upgraded the OS. After the upgrade, I obviously lost root, but also got a bunch of bloatware I had originally deleted when I first rooted it (NFL, IMDB and a bunch of other crap), and now, no matter what the hell I do, none of the multiple methods I've tried will work for rooting the phone. Off the top of my head, Odin fails with a NAND write error, CASUAL loops trying to install the same thing continuously, and the Android Toolkit clearly states that it can't root (I thought it could).
Currently these are the phone/OS specs:
Android version: 4.4.2
Baseband: I605VRUFND7
Kernel version: 3.0.31
Build number: KOT49H.I605VRUFND7
SE for Android status: Enforcing
Hardware version: I605.06
While doing my research, I've read that if the bootloader is locked, there's no luck for me in trying to root this thing, but I have no way of telling whether it is indeed locked or not. Furthermore, this update applies an unreasonable amount of annoyance to my phone, including not being able to write to the external SD card.
Is there anything I can do to get my phone rooted safely? If not, is there any reasonably foolproof way for me to return to the previous version (4.3) so that I can keep the device rooted?
I will appreciate any input on this. Thanks in advance and apologies if I'm breaking any rules with this thread; I went over the rules and didn't see anything I could be breaking with this.
MrSh1k1 said:
Hi. New guy around. Disclaimer: I live in the Dominican Republic, using the Orange carrier, despite having a Verizon device.
I currently own a Verizon Galaxy Note 2 SCH-I605 which, until yesterday, was rooted and running a 4.3 stock ROM. Because of the Pokémon Go craze, I did my research and figured I could update the phone to 4.4, the minimum version required for Go. So I downloaded the Samsung software (running Win10 here), connected the phone, and upgraded the OS. After the upgrade, I obviously lost root, but also got a bunch of bloatware I had originally deleted when I first rooted it (NFL, IMDB and a bunch of other crap), and now, no matter what the hell I do, none of the multiple methods I've tried will work for rooting the phone. Off the top of my head, Odin fails with a NAND write error, CASUAL loops trying to install the same thing continuously, and the Android Toolkit clearly states that it can't root (I thought it could).
Currently these are the phone/OS specs:
Android version: 4.4.2
Baseband: I605VRUFND7
Kernel version: 3.0.31
Build number: KOT49H.I605VRUFND7
SE for Android status: Enforcing
Hardware version: I605.06
While doing my research, I've read that if the bootloader is locked, there's no luck for me in trying to root this thing, but I have no way of telling whether it is indeed locked or not. Furthermore, this update applies an unreasonable amount of annoyance to my phone, including not being able to write to the external SD card.
Is there anything I can do to get my phone rooted safely? If not, is there any reasonably foolproof way for me to return to the previous version (4.3) so that I can keep the device rooted?
I will appreciate any input on this. Thanks in advance and apologies if I'm breaking any rules with this thread; I went over the rules and didn't see anything I could be breaking with this.
Click to expand...
Click to collapse
Nope you are stuck on 4.4.2 since you upgraded and locked the bootloader. Only way back is to send it to a company but thats located in the states and im sure its not worth it. I believe you can still root though using towel root. Thats why you never accept updates. There are some stock roms you can flash now with that option, using R3Ds rom may be your best option.
Update: I was able to root the phone!
Essentially, this reddit post had what I needed: reddit.com/r/AndroidQuestions/comments/2oekwf/can_i_root_my_verizon_note_2_schi605_442/cmn5y51
What I think saved me was the fact that the phone had been rooted before the upgrade, so Root Browser, SuperSU and Busy Box were still there, even if they weren't running anymore.
I repeated the steps on it up until the second time I had to run adb devices to ensure the device was still connected — at this point I had to kill the adb server and start it again. After that, I finished the process with ghettoroot 0.2.2, but didn't see anything new or different on my phone. Then an idea occurred to me — what if SuperSU was failing to install because it was already there? So I fired up Root Browser (which wasn't deleted with the upgrade) and found the location of the SuperSU apk, reinstalled it, and voilá: root access again!
With full credits to the reddit user who posted that message, I'm going to repost and reorganize the entire process here for future reference:
Ensure you have the device drivers for the Note 2, you can get them from the Samsung site
Download Ghettoroot 0.2.2 and 0.3.2 from here: forum.xda-developers.com/showpost.php?p=55170966&postcount=1
Unzip both in an easily accessible location, make sure each has their own folder
Open a CMD window with "Run as Admin"
In the CMD window, navigate to the folder containing Ghettoroot 0.3.2
Inside this folder, type cd tools\win\adb and run the command adb devices (this should show you if your phone is recognized and connected)
Type cd ..\..\.. to return to the Ghettoroot 0.3.2 folder
Type install.cmd and let it run (remember, we're running 0.3.2)
Let the phone reboot and leave Installer mode
Run the cleanup; chances are it will fail, so try again until it works (it should, eventually — it took me a bunch of tries until it finally worked)
Type cd tools\win\adb to enter the adb folder
Type adb kill-server to kill adb, then type adb start-server to restart it (I needed this step because after running Ghettoroot adb wouldn't see my device anymore)
Type adb devices to ensure your device is still visible to adb
Now navigate to the Ghettoroot 0.2.2 folder
Type Type install.cmd and let it run (remember, this time we're running 0.2.2)
Let the phone reboot and leave Installer mode
Run cleanup again until it works
This SHOULD be enough to root your phone, especially if it was rooted before. If it was indeed rooted before, you should already have Root Browser and SuperSU in your /system/app folder, so navigate there and run/install Superuser.apk and execute it to be granted root access. I can't say if this would work if the phone wasn't rooted on 4.3, and I'm really iffy about mucking around with my device now that I safely got it rooted — apologies for not being able to offer more in-depth testing. But for what it's worth, I was finally able to root my Verizon Note 2 running ND7 with the above steps.
Hope this helps someone else out there.
Thanks so much! Somehow I lost root after a SuperSU update (?) from the Play Store. I'd forgotten how much trouble rooting this was.

Categories

Resources