[tool] [app] diag mode switch by solcam - Thunderbolt Android Development

This is a tool I made (with the help of this thread >> http://forum.xda-developers.com/showthread.php?t=1060184 << thanks hydrosity) that will install GScript and scripts to your HTC THUNDERBOLT and allow you to use QPST, QXDM, DFS cdma tool, and cdma workshop on your phone. It is meant to put the device into DIAG mode after you have flashed to a custom rom that doesn't have ##3424# capabilities built in. It is flashable thru recovery mode. It is very useful if you have flashed your TB to another carrier (i.e. Cricket, Metro, etc.) and need to re-write nv and/or nam settings. This took me 3 and a half days to create because of the tedious work of creating an updater-script with notepad++. This is my first flashable package i have ever created and it works nicely. Instructions are as follows...
1. Reboot to Recovery mode that uses edify.
2. Enable signature checking.
3. Choose flash rom from sdcard.
4. After rebooting, run GScript app.
5. Touch menu button.
6. Choose load.
7. Touch diag_on.sh and save.
8. Touch diag_off.sh and save.
9. Run GScript again.
10. The 2 scripts are there so, its a no brainer from then on.
11. Enjoy.
If you have any problems with anything not working properly, reboot to recovery again and choose fix permissions. That should help with FCs. I hope I have helped someone the way XDA has helped me numerous times. My way of giving back to the community. BTW, making flashable packages WAS very very hard for me to do. Now it's only kind of hard. LOL. I wonder if i could kang a SG3 JB rom and compile it to run on our aging Thunderbolt? Hmmm....To DEVS, if this is not in the correct place please move it. Thanks. Peace out.

Thanks for the tool man.
I REALLY wish I could flash my old Thunderbolt to Page Plus but I need some good step by step instructions. I found a decent video but only half of the process and I can't afford CDMA workshop.
But this tool will definitely be useful for those who can do it. Thank you for that.
Sent from my XT912 using xda app-developers app

Thanks for downloading my tool. And you need to follow this guide for your task. http://forum.xda-developers.com/showthread.php?t=1473141 I hope this helps. If so hit thanks. Then hit thanks on that thread also. That tool will definitely help you as you don't have to flash back to stock nor reboot your phone to get into diagnostic mode. :good:

Page plus from what I have researched, is like an mvno (virtual network operator) if my memory serves me right. And they are under verizon kinda like boost mobile under sprints network. And u can use DFS CDMA Tool and/or QPST. Both are free. I recommend DFS though. It's what I use for most of my phone programming driver.

You could also use a text file in the init.d with the contents:
Code:
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
echo 1 > /sys/class/android_usb/android0/enable
echo 1 > /sys/class/android_usb/f_diag/on

Thanks for replying. I didn't know that. I'm in the process of compiling a custom rom for the thunderbolt based on the new VZW ICS update, but with parts from jellybean. Would love to get a total dump of the new HTC One, as it would probably be easier to build.

tb script
Solcam
thank you so much - I have been searching how to get into Diag mode. I thought going thru bootloader and getting to USB would do it - it gave me a com port, but the computer could not talk to the phone. I am trying to put pageplus on a thunderbolt, problem is I rooted it first and it is a little bit of a hassle to get it back to stock
I ran the script but I get this on the bottom of the screen after running it stderr: sh: <stdin>[1]: cannot create /sys/devices/virtual/android_usb/android0/f_diag/on: no such file or directory, what is supposed to happen? It is supposed to reboot into diag mode?
thanks again.
BoilermanAres
solcam said:
This is a tool I made (with the help of this thread >> http://forum.xda-developers.com/showthread.php?t=1060184 << thanks hydrosity) that will install GScript and scripts to your HTC THUNDERBOLT and allow you to use QPST, QXDM, DFS cdma tool, and cdma workshop on your phone. It is meant to put the device into DIAG mode after you have flashed to a custom rom that doesn't have ##3424# capabilities built in. It is flashable thru recovery mode. It is very useful if you have flashed your TB to another carrier (i.e. Cricket, Metro, etc.) and need to re-write nv and/or nam settings. This took me 3 and a half days to create because of the tedious work of creating an updater-script with notepad++. This is my first flashable package i have ever created and it works nicely. Instructions are as follows...
1. Reboot to Recovery mode that uses edify.
2. Enable signature checking.
3. Choose flash rom from sdcard.
4. After rebooting, run GScript app.
5. Touch menu button.
6. Choose load.
7. Touch diag_on.sh and save.
8. Touch diag_off.sh and save.
9. Run GScript again.
10. The 2 scripts are there so, its a no brainer from then on.
11. Enjoy.
If you have any problems with anything not working properly, reboot to recovery again and choose fix permissions. That should help with FCs. I hope I have helped someone the way XDA has helped me numerous times. My way of giving back to the community. BTW, making flashable packages WAS very very hard for me to do. Now it's only kind of hard. LOL. I wonder if i could kang a SG3 JB rom and compile it to run on our aging Thunderbolt? Hmmm....To DEVS, if this is not in the correct place please move it. Thanks. Peace out.
Click to expand...
Click to collapse

boilermanAres said:
Solcam
thank you so much - I have been searching how to get into Diag mode. I thought going thru bootloader and getting to USB would do it - it gave me a com port, but the computer could not talk to the phone. I am trying to put pageplus on a thunderbolt, problem is I rooted it first and it is a little bit of a hassle to get it back to stock
I ran the script but I get this on the bottom of the screen after running it stderr: sh: <stdin>[1]: cannot create /sys/devices/virtual/android_usb/android0/f_diag/on: no such file or directory, what is supposed to happen? It is supposed to reboot into diag mode?
thanks again.
BoilermanAres
Click to expand...
Click to collapse
Your phone won't reboot at all. Thats the other reason I made this, because it is faster than ##DIAG#>auto reboot phone>program phone>##DIAG#>auto reboot phone. GOD forbid you didn't program it right the first time. You are supposed to open your app drawer, (the button that shows all apps) touch gscript app to run it, (its blue) hit menu, load and save both scripts. The 2 scripts are on your sdcard inside a folder called 'gscript' without the '' of course. So you could probably use srcipt runner app from playstore to execute the scripts. I just tried with root explorer app and it force closed, so thats not an option. So look here -->http://forum.xda-developers.com/attachment.php?attachmentid=1923849&stc=1&d=1367296728 then you should see this after you hit the menu button-->http://forum.xda-developers.com/attachment.php?attachmentid=1923850&stc=1&d=1367296728 and this after you've added both scripts-->http://forum.xda-developers.com/attachment.php?attachmentid=1923851&stc=1&d=1367296728 If your phone still complains that the files are not found, download and extract this http://forum.xda-developers.com/attachment.php?attachmentid=1923852&stc=1&d=1367296728 folder to the root of your sdcard and try to add the scripts again. So it will look like this /sdcard/gscript/diag_on-diag_off (there is no -, I'm just saying both scripts will be in the gcript folder). After you add the scripts, go back to gcript app, open it and touch 'diag_on' to activate diag mode. I dont know why it did not flash correctly for you in this first place. It should have placed all files in the correct places. By the way, which rom are you running? And did you flash that file from the OP from recovery? I kept compiling and flashing it over and over again until I got it to put all files in the right places. Which recovery are you using? I hope this helps you get your phone flashed over to PP. Good luck. :good:

Thank you! I have 3 Bolts on page plus and have always had to nandroid back to GB to connect to my radios. I'll be giving this a shot soon, the old way of using g_script stopped working after some updates but it seems your tool has brought it back to life....

You are welcome gimmeitorilltell. GScript IS a great app. When used with scripts like this, it streamlines the tedious process of nam/nv programming. I'm just happy that I have helped out some people on XDA, because it's is my number 1 source of alot of stuff for all the phones that I have to program or hack. Just glad to be giving something back to the community. (offtopic)- Why do some of the smartest people on here not know how to speak 2nd grade English? Seems like no one uses the conjunction 'you're' anymore...they say your, which is possessive. Or 'than' instead of 'then'. EX- Your not going anywhere fast than= You're not going anywhere fast then. I don't get it. SMH. Sorry for the rant...it just burns me up. LOL. Hit the thanks button if I've help you...even if it is just taking them back to grade school. LOL.

You are very welcome gimmeitorilltell. I'm happy to help out fellow members. Just glad to give back to the community finally. XDA is my number 1 source of information on how to program or hack devices that I need to program. Hey twistedumbrella, when are you gonna drop your next AOSP rom update? Are you waiting for HTC to release their source code? I'm downloading your ROM (Multisource) right now to check it out. I love AOSP roms because i can play games on my phone with Wii or PS3 gamepads. Plus it sticks it to the MAN (HTC). LOL. MODS please delete this post. I can't seem to be able to.

I used the other script and it went in. I think because there were already some directories made up in the root. So I got into diag mode, I then tried flashing with the site "cyberflashing". It seems like everything gets blocked from writing to the phone.
I rooted it with Revolutionary, Running Liquid ICS android 4.0.4. Nice setup, I should have waited to root and flashed it with the stock rom then rooted it later. I have QPST and DSF plus the free ones from CDMA for ulocking the sps.
After flashing with cyberflash (which did not seem to do anything -$10 gone like that!) they want you do the following (which I did not know if there is a script for this??) info below.
I imagine i could do everything with the right software, just have not found all the videos and tutorials to get it done. It almost makes you want to give it to a guy that does it all the time and pay him for his services, but I am stubborn too, and it has been a learning experience.
What is interesting is that the only number that dialing from the phone that works is the one below
Dial *#*#4636#*#*
Phone information
Scroll down to the CDMA LTE/EVDO box
Change it to CDMA LTE/EVDO
Press back button until back at home screen.
Upon completion of flash restart the phone again by removing the battery.
Then dial ##3424 then press Send
Press Menu
Select Re-boot to enable embedded mode
After the phone reboots dial ##778 then press SEND
Go to edit mode, password 000000
Then go to Modem Settings and match what is below...
-Slot Cycle Index = 2
-Preferred Serving System = Automatic
-Preferred Mode = CDMA Only
-Preferred Mode(9k) = HDR LTE only
-HDR Hybrid Preferred = Enable
-HDR Hybrid Preferred(9k) = Enable
-Clear All MRU Entry = No
-Rev. A = Disable
-1X Diversity = Disable
After this is complete press menu, commit modifications and phone will reboot
Replace LTE Sim card in phone to restore call ability.
Menu, Settings, Wireless and Networks, Mobile Networks, Network Type, CDMA Only

used to work
I don't know why it won't create the directory on the phone, It used to work. I have tried it on two rooted phones and I get the errors. I have found the directories on the phone, but not same structure. Tried to change it - but phone won't let me create new directories on it.
solcam said:
Your phone won't reboot at all. Thats the other reason I made this, because it is faster than ##DIAG#>auto reboot phone>program phone>##DIAG#>auto reboot phone. GOD forbid you didn't program it right the first time. You are supposed to open your app drawer, (the button that shows all apps) touch gscript app to run it, (its blue) hit menu, load and save both scripts. The 2 scripts are on your sdcard inside a folder called 'gscript' without the '' of course. So you could probably use srcipt runner app from playstore to execute the scripts. I just tried with root explorer app and it force closed, so thats not an option. So look here -->http://forum.xda-developers.com/attachment.php?attachmentid=1923849&stc=1&d=1367296728 then you should see this after you hit the menu button-->http://forum.xda-developers.com/attachment.php?attachmentid=1923850&stc=1&d=1367296728 and this after you've added both scripts-->http://forum.xda-developers.com/attachment.php?attachmentid=1923851&stc=1&d=1367296728 If your phone still complains that the files are not found, download and extract this http://forum.xda-developers.com/attachment.php?attachmentid=1923852&stc=1&d=1367296728 folder to the root of your sdcard and try to add the scripts again. So it will look like this /sdcard/gscript/diag_on-diag_off (there is no -, I'm just saying both scripts will be in the gcript folder). After you add the scripts, go back to gcript app, open it and touch 'diag_on' to activate diag mode. I dont know why it did not flash correctly for you in this first place. It should have placed all files in the correct places. By the way, which rom are you running? And did you flash that file from the OP from recovery? I kept compiling and flashing it over and over again until I got it to put all files in the right places. Which recovery are you using? I hope this helps you get your phone flashed over to PP. Good luck. :good:
Click to expand...
Click to collapse

Solcam I have not had much luck with this script running 4EXT recovery. Are you using CWM or something different? I would love to be able to do my programming without restoring the ole GingerBread nandroid. Lol

HTC One
Anyone know if this will work with an HTC One

freduser said:
Anyone know if this will work with an HTC One
Click to expand...
Click to collapse
Highly unlikely
Sent from my HTC6500LVW using Tapatalk

Sorry I haven't replied to this thread in a long time. I'm not sure which phones and/or roms this will work on! I just remembered I had posted this and am currently trying to get this working on cm10.x for the Eco 4g LTE. BTW I built this with titanium backup but have forgotten exactly how I did it as I hate Linux scripts. I'm gonna download this and compare the Evo's file system to the Thunderbolt's. Probably will report back but idk...

twistedumbrella said:
You could also use a text file in the init.d with the contents:
Code:
echo 1 > /sys/devices/virtual/usb_composite/diag/enable
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
echo 1 > /sys/class/android_usb/android0/enable
echo 1 > /sys/class/android_usb/f_diag/on
Click to expand...
Click to collapse
last one works for HTC desire 510 -> echo 1 > /sys/class/android_usb/f_diag/on

solcam said:
This is a tool I made (with the help of this thread >> http://forum.xda-developers.com/showthread.php?t=1060184 << thanks hydrosity) that will install GScript and scripts to your HTC THUNDERBOLT and allow you to use QPST, QXDM, DFS cdma tool, and cdma workshop on your phone. It is meant to put the device into DIAG mode after you have flashed to a custom rom that doesn't have ##3424# capabilities built in. It is flashable thru recovery mode. It is very useful if you have flashed your TB to another carrier (i.e. Cricket, Metro, etc.) and need to re-write nv and/or nam settings. This took me 3 and a half days to create because of the tedious work of creating an updater-script with notepad++. This is my first flashable package i have ever created and it works nicely. Instructions are as follows...
1. Reboot to Recovery mode that uses edify.
2. Enable signature checking.
3. Choose flash rom from sdcard.
4. After rebooting, run GScript app.
5. Touch menu button.
6. Choose load.
7. Touch diag_on.sh and save.
8. Touch diag_off.sh and save.
9. Run GScript again.
10. The 2 scripts are there so, its a no brainer from then on.
11. Enjoy.
If you have any problems with anything not working properly, reboot to recovery again and choose fix permissions. That should help with FCs. I hope I have helped someone the way XDA has helped me numerous times. My way of giving back to the community. BTW, making flashable packages WAS very very hard for me to do. Now it's only kind of hard. LOL. I wonder if i could kang a SG3 JB rom and compile it to run on our aging Thunderbolt? Hmmm....To DEVS, if this is not in the correct place please move it. Thanks. Peace out.
Click to expand...
Click to collapse
Any Simular tool with latest Android Support?
My XIAOMI 6 is root, not enable Diag yet.

Related

EPST code "##778 call" Stopped working

I am on Stock 2.1, Rooted
For some unknown reason I have lost ability to go into EPST from phone by ##778 code.
QPST is working in diagnostic mode.
Does anyone know what could have caused this and more importantly how to get it back.
Any suggestions would help.
I have searched many places but did not find answers.
seconded...
EPST works fine on my rooted/2.1 stock phone... not on my wife's. None of the ##xxx codes works.
Weeks after rooting my DInc w/ unrevoked 3.0, I decided it was safe to go ahead and do the same on my wife's phone. It's 2.1 stock, rooted with unrevoked 3.1/CM 2.5.0.x...plus the wifi tether kernel for AP mode wifi. Deleted CityID and installed root apps Ti Backup (full version), IncrediLite, and AdFree (which required manual symlinking /system/etc/hosts --> /data/data/hosts).
That's IT. Her phone is simpler in terms of apps installed. There's very little there that I haven't also done to my own phone... she has HandCent SMS where I don't; rooting method plus clockwork recovery were/are newer, and I never quite got AdFree working on one of the handsets.
I've no idea why this happened to one phone and not the other...I don't understand the where the config files are stored, or how the dialer accesses the 'hidden' menu. Unless I find an informative answer, I'm just going to try unrooting hers & reverting to stock...
figured out a few things
running ASTRO's process manager on my W's rooted phone, I see that dialing ##778 does invoke an instance of EPST... but you don't get the view/edit mode dialogue.
Trying to launch EPST from the ASTRO process mgr ("go to application") gives the view/edit choice, and if you hit edit you are prompted for the password... but after typing in 000000 it just hangs on 'wait while verifying password'
logcat has lots of entries containing 'epst' but I don't know how to interpret them.
I notice that the com.google.android.epst file lives in /data/data, where one has to muck around when getting a hosts file symlinked for AdFree...but I didn't do anything clumsy, and the permissions are rwxr-xr-x which looks right.
That's about as far as I can go. Anyone know what breaks EPST?
QPST workaround...
I guess this problem must be pretty isolated since no one has responded... but fwiw, as OP alluded, Qualcomm's QPST utility offers a workaround if you can't launch EPST from your phone/dialer:
1. Find a copy of QPST 2.7 build 323 (don't ask me where). Install to PC.
2. Install HTC Sync (for drivers), then Connect phone as 'charge only' via USB with debugging enabled.
3. Open Device Manager and look under Ports to find which COM# is the HTC Diagnostic Interface.
4. Launch QPST Configuration applet. Click the Ports tab, then Add New Port. Select the COM port you found in Step 3 from the list at left, then hit OK. Your phone should now show up under the Active Phones tab as FFA/Surf QSD8650 Rev. 2.0. If not, unplug phone, dial ##DIAG#, wait 10s and plug back in as in Step 2.
5. Open the QPST Start Clients menu & choose Service Programming. Select your phone, hit OK, then click 'Read from Phone' button in the resulting window.
6. You now have access to the same configuration items you normally reach via ##778 on your phone. 'Write to Phone' will commit any changes you make, without further warning.
Obviously it is possible to seriously BORK your phone from here, requiring a restore from backup (which you should have before trying this). I take no responsibility for what you do with QPST. I used it only to change the tethering NAI from <number>@dun.vzw3g.com --> <number>@vzw3g.com so I could tether my wife's DINc. via Windows DUN. That worked, but I can't guarantee the results of other edits.
Same issue
Sorry to resurrect an old thread, but I am having nearly the same issue.
When I try to access epst from dialing ##778# on my girlfriends hero nothing happens at all. I ended up adding a shortcut with anycut and now the view or edit menu comes up. When I hit view it just hangs when I hit edit and enter the password it stays on "please wait verifying password". I can get ##data# to work and a few other ##xx# codes to work but I need access to the epst advanced settings.
Any help would be greatly appreciated, I have tried 1.5 stock 2.1 stock Fresh versions 2.1.3 (i think that's right) Fresh 2.3.3 and Damage control 2.09.....
I have qpst and CDMA workshop 2.7 but I know there are more options I need to change to get data on cricket. I don't have the $100 to spend on the new version on CDMA workshop.
Thanks in advance.

[Mod] Native WiFi Tethering MobileAP port from Galaxy S i9000 - Infrastructure AP!

According to the Vibrant forums, Jr33 has fixed and ported the MobileAP (native Infrastructure Wifi Tethering AP) from the Galaxy S i9000 to the Vibrant:
http://forum.xda-developers.com/showthread.php?t=756804
Why this is important and better than the Wifi tethering apps (Barnacle and android-wifi-tether):
This is REAL infrastructure mode. Not the hacked up ad-hoc mode (which android-wifi-tether and barnacle uses) which A LOT of devices (other android phones, ps3, wii, corporate laptops included) cannot connect to.
Because it being infrastructure mode, it supports WPA, a much more secure protection than WEP.
This is natively built into the Galaxy S i9000 phones. But taken out by AT&T and T-mobile. It just works, and works well - because it was MADE for our phones!
android-wifi-tethering hard crashes a lot on start, forcing you to do a battery pull, and may lose connectivity every so often.
Barnacle requires you to change the MTU of your client device, not possible in a lot of cases (consoles, phones, etc), and may cause conflicts when moving to a different wifi AP.
-------------------------------------------------------------------------------------------------------------------------------
Update 8/22:
Designgears has figured out a way to automatically launch the wlp2pservice on boot, therefore, no more manual entry is needed (but requires kernel flashing). Please see:
http://forum.xda-developers.com/showthread.php?p=7785171
The reason why it requires flashing the kernel (while Vibrant did not) can be explained by Jr33:
i know the stock kernel for the vibrant had the iptables included as well as wlp2pservice. what i have been finding is all these different features have just been commented out in different places. the same source was used for all three phones. you can see this when you start decompiling the odex files and comparing files, it is all the same. just needs a little tweaking here and there to activate certain features
Click to expand...
Click to collapse
-------------------------------------------------------------------------------------------------------------------------------
Update 8/20:
With the help of Jr33 (person that did the port to Vibrant), we *kind* of got it working with a few hoops. Jr33 should be given credit as he created and repackaged the captivate MobileAP update.zip; I was merely a test dummy. This thread will be locked when a solution is made and Jr33 will create a new thread with the final version. Go buy him a red bull!
REQUIREMENTS
Update.zip downloaded below
Rom Manager
ClockworkMod Recovery flashed on your phone (using Rom Manager)
Busybox
An Android Terminal App (ex: http://www.appbrain.com/app/jackpal.androidterm)
DOWNLOAD The Captivate mobileAP update.zip:
http://www.mediafire.com/?ownoqzgo6cbtmoj
File is also attached at the end of this post.
INSTRUCTIONS
Rename to update.zip, put it on your INTERNAL SD card root
Boot into ClockworkMod Recovery (using Rom Manager) and reinstall/update packages.
Reboot - note: first time boot after updating this will take a little while.
Now go into an Android terminal app and type the following:
Code:
su
busybox nohup /system/bin/wlp2pservice &
This starts the wlp2pservice. (Props to designgears for finding out this new command)
Old command (just typing in /system/bin/wlp2pservice in terminal (does not require busybox)) works BUT you will need to keep Terminal open during the duration, if force closed, you will have to retype that command in again.
5. Now you can go into Settings -> Wireless and Networks -> Mobile AP Settings to start your Access point.
Note: if you change any of the settings (AP name or WPA password) it may crash wlp2pservice. Use a task manager to force close "MobileAP Settings." Do step 4 again and your settings should be there.
This works until you reboot your phone. If you reboot, you need to go back into terminal and manually start wlp2pservice again (do step 4 again).
If you do not manually launch wlp2pservice, when you open up MobileAP settings, it just sits there on a black screen and if you check logcat, you see the looping message pasted below. We are currently trying to fix the necessity of manually launching wlp2pservice. This is not how it was intended to be.
-----------------
Developers with a Captivate, we need your help:
Upon opening MobileAP settings WITHOUT manually launching wlp2pservice in terminal, yields the following (from logcat):
Code:
I/ServiceManager( 3459): Waiting for service WLP2PService....
It loops until you force close "MobileAP Settings" in your task manager. Something is not calling wlp2pservice to execute.
Also, rebooting the phone or closing/ending terminal (on the pc or phone) requires you to go back into terminal and execute wlp2pservice manually, otherwise opening MobileAP settings yields the same loop above.
I am guessing that wlp2pservice is not launching on boot, or not executing at all when you open up MobileAP settings. I'm not sure which is supposed to happen.
This *seems* like an easy fix, and because Jr33 does not have a Captivate it is hard for him to help troubleshoot this. This is why we need other people to help figure out a way.
According to the front page: Update: This is a mod to add in the Samsung version of Mobile AP intended for the Galaxy S, but was removed by T-Mobile.
It was also removed by ATT, so wonder if it is possible :/
andy2na said:
According to the front page: Update: This is a mod to add in the Samsung version of Mobile AP intended for the Galaxy S, but was removed by T-Mobile.
It was also removed by ATT, so wonder if it is possible :/
Click to expand...
Click to collapse
This would be excellent to be ported over. While the current wireless tether (found in the associated thread) works... it does it in ad-hoc mode. This apparently supports infrastructure mode which would make it even more useful.
Go mods go!
rickgrob said:
This would be excellent to be ported over. While the current wireless tether (found in the associated thread) works... it does it in ad-hoc mode. This apparently supports infrastructure mode which would make it even more useful.
Go mods go!
Click to expand...
Click to collapse
wireless tether and barnacle "work" but still require you to go through hoops.
Wireless tether hard crashes A LOT.
Barnacle requires you to change MTU in your OS.
Please see OP for Update.
andy2na said:
wireless tether and barnacle "work" but still require you to go through hoops.
Wireless tether hard crashes A LOT.
Barnacle requires you to change MTU in your OS.
Click to expand...
Click to collapse
Yeah i changed my mtu (took like 30 seconds) and barnacle works great now. I was able to register for my fall semester from disneyland last weekend
I hope this isn't too far off topic, but would it then be possible to use a similiar techique to restore usb tethering to captivate ROMS in which AT&T has it removed/disabled?
jsmith8858 said:
I hope this isn't too far off topic, but would it then be possible to use a similiar techique to restore usb tethering to captivate ROMS in which AT&T has it removed/disabled?
Click to expand...
Click to collapse
When did it get removed? And i doubt the mobileAP is anywhere near related to the USB tethering samsung includes.
I currently have the stock rom, it has usb tethering. Mobile ap is related since they're both tethering.
Perhaps I can extract the file out of my phone where I to be instructed how.
Sent from my SAMSUNG-SGH-I897 using XDA App
Bowsa2511 said:
I currently have the stock rom, it has usb tethering. Mobile ap is related since they're both tethering.
Perhaps I can extract the file out of my phone where I to be instructed how.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I guess if you want to be completely broad they are both tethering solutions....
But their implementation i would assume is different and dont affect each other.
thanks Andy for bring this to Jr33's notice to get this implemented for Captivate.
was wondering if there is any app which wld start this service on boot or something like Tasker if it can start a system service.
Thnx
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Edit: removed
pewpewbangbang said:
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Click to expand...
Click to collapse
It's not a signed .zip bro. You need to download rom manager off the market if you don't have it, then reboot recovery from it and it will put you into clockwork recovery mode and then run the update.zip from that. It also lets you run other .zips even if they aren't named update.zip.
Hope that helps ya!
Sent from my GT-I9000 using Tapatalk
anilkuj said:
thanks Andy for bring this to Jr33's notice to get this implemented for Captivate.
was wondering if there is any app which wld start this service on boot or something like Tasker if it can start a system service.
Thnx
Click to expand...
Click to collapse
I thought about that, but because it has to start your terminal program and execute the wlp2pservice (and leave it running), I'm not sure if it had a large impact on battery life.
I setup Better Terminal Emulator to have a shortcut key to type out "/system/bin/wlp2pservice" for me, so its a few taps and Its ready. The amount of tethering I do right now is not that often that this is a big deal, but would be nice..
pewpewbangbang said:
when i boot into recovery......theres no update option. I have the reinstall packages but it just says installation aborted.
Does the update.zip need to have lowercase "u"?? i did upercase, maybe ill try lowercase
Nope.......i ran into a problem i guess. I named the file to update and i boot into recovery with rom manager but when i get to recovery, there is no updates buttom (im guessing there never was?) I click reinstall packages and it seems to start installing the update.zip but then it says "Installation aborted"
help??
Click to expand...
Click to collapse
My bad, it should be "Reinstall Packages" then after selecting it, it makes you scroll down past all the No's to Yes, install package.
Make sure when you open up when you open up Rom Manager you see:
Current Recovery: ClockworkMod 2.5.0.4, if not tap Flash ClockworkMod Recovery. (maybe reinstall it just incase) Then tap reboot into recovery.
Ahhh yes got it. Thank you, I didn't flash my rom before. Got it to work now. Thanks =)
As a quick note:
Please mod alert the Original Post to get this moved back to the Captivate development forum, so more developers that know what they are doing can see this thread and hopefully chime in.
This *seems* like it would be an easy fix. wlp2pservice just needs to launch at boot.
New problem. When I try to run the command in android terminal is says
/system/bin/wlp2pservice
not found
Ok I ran into the same problem because my clockworkmod was borked, so I had to reflash Clockwormod Recovery. When you tap Flash Clockworkmod recovery, it replaces update.zip in your root of the SDCard, so when you hit reinstall/update packages, it just reinstalled clockworkmod recovery again, no harm done.
So what you need to do is redownload the mobileAP zip and replace the current update.zip with the one found in this thread.
Go back into Rom Manager and reboot into recovery (dont hit flash clockworkmod), then update/reinstall packages, it should work then.

QPST DIAG Mode CM7 (Aka ##3424)

(UPDATE: 8/24/11 New flashable update.zip for install via recovery, includes Gscript (credit goes to PinkVenture for developing the app!) and my simple on/off scripts already installed. You can link shortcuts directly to the desktop for each ON or OFF through add shortcut on homescreen, see attachments at the end of this post)
I'll start this off by mentioning that all the threads you may find saying "CM7 DIAG Enabled!" such as this one here Etc, are not valid solutions for OUR device. That may/may not work with the eris/hero(haven't tried) etc as those topics discuss. They merely SPECULATE it will for any CM7 based rom - it doesn't for ours.
echo 1 > /dev/qct_diag_enable (to enable diag mode)
..and your phone should go into USB diag mode. when you are done just:
echo 0 > /dev/qct_diag_enable (to disable diag mode)
Click to expand...
Click to collapse
WONT DO ANYTHING for you. In fact, it made my "qct_diag_enable" file disappear. Scroll to the bottom to skip my bantering and explaining of the reason this is a useful feature for people like myself, and to just show the actual findings of this thread.
So you have CM7 and (of course) are lovin' it. The only thing is you have an alternate carrier (cricket personally) and hate the fact that manually switching prl's or needing to change your EPST settings can be a pain (since CM7 has no EPST built-in!). Especially when its [*feature name here] that you would LIKE to have the ability to use, but can live without if it means having to restore (or flash one if you have no backups) a sense rom just to change any of your EPST (##778, etc) settings.
Well, if you know anything about QPST for windows (google), then you know that you need to have your phone in DIAG mode to use it (##3424) and have the hero diagnostic drivers installed on your windows machine. (For the record, I'm an Ubuntu man and my main machine is NOT dual boot, meaning I still have to switch to my windows laptop to use QPST >< but we'll just pretend you have windows and this is more convenient for *you*).
Back to the point, once you've realized all the hassle, yada yada, you just say, "Ill just fix it later, I can live without it for now." AND how sick you are of saying that, here is the solution to no longer switching ROM's for EPST, as there IS a way without the ability to ##3242 in CM7 to enable DIAG mode.
(NOTE: This is also useful for those of you already on CM7 WITH Verizon/Alltell who would like to follow the guide in the Development section Droid Incredible Wiki regarding switching to the whole Verizon PRL/Alltell Hybrid PRL, along with other guides involving EPST or ## codes found there)
Simply go to (via adb shell/terminal emulator) /sys/devices/virtual/usb_composite/diag and run (1 for on and 0 for off, respectively)
Code:
echo 1 > enable
echo 0 > enable
To simplify all this I've included a zip file which includes Gscript.apk for you to install, and two scripts in the Gscript directory (place entire Gscript directory on root of sdcard). Open Gscript application, then once open - menu button>add script>load file>diag on/off.sh>save for each script respectively. Then you can simply toggle on/off DIAG mode from the Gscript application (or even add shortcut>gscript>diag on/off from CM7 home screen, for each script respectively). And without further excess explanation, here's the .zip signed-diagscripts.zip flashable update.zip file for recovery
By the way, if a mod reads this, could you please move to the Development section and remove my restriction? I know I don't have my whole 10 posts etc, etc, but I don't really have enough to say or the patience to say it most of the time to post 10 posts. However, I've lurked these boards and been rooting phones and flashing phones via this forum since my first android phone back from what feels like ages ago. (going on 4 rooted and flashed to cricket android phones now, all sold except my current, Dinc)
cool, thanks, man!!!
Sure thing, let me know if anyone experiences issues by pm or reply. I was thinking about compiling an installable zip so this can be installed after rom in recovery too.
Sent from my ADR6300
Just wondering... Any idea if this will work on Evo as well?
Work on the EVO too?
Yeah, I would really like to know if this would work on the evo!!
hydrosity said:
I'll start this off by mentioning that all the threads you may find saying "CM7 DIAG Enabled!" such as this one here Etc, are not valid solutions for OUR device. That may/may not work with the eris/hero(haven't tried) etc as those topics discuss. They merely SPECULATE it will for any CM7 based rom - it doesn't for ours.
WONT DO ANYTHING for you. In fact, it made my "qct_diag_enable" file disappear. Scroll to the bottom to skip my bantering and explaining of the reason this is a useful feature for people like myself, and to just show the actual findings of this thread.
So you have CM7 and (of course) are lovin' it. The only thing is you have an alternate carrier (cricket personally) and hate the fact that manually switching prl's or needing to change your EPST settings can be a pain (since CM7 has no EPST built-in!). Especially when its [*feature name here] that you would LIKE to have the ability to use, but can live without if it means having to restore (or flash one if you have no backups) a sense rom just to change any of your EPST (##778, etc) settings.
Well, if you know anything about QPST for windows (google), then you know that you need to have your phone in DIAG mode to use it (##3424) and have the hero diagnostic drivers installed on your windows machine. (For the record, I'm an Ubuntu man and my main machine is NOT dual boot, meaning I still have to switch to my windows laptop to use QPST >< but we'll just pretend you have windows and this is more convenient for *you*).
Back to the point, once you've realized all the hassle, yada yada, you just say, "Ill just fix it later, I can live without it for now." AND how sick you are of saying that, here is the solution to no longer switching ROM's for EPST, as there IS a way without the ability to ##3242 in CM7 to enable DIAG mode.
(NOTE: This is also useful for those of you already on CM7 WITH Verizon/Alltell who would like to follow the guide in the Development section Droid Incredible Wiki regarding switching to the whole Verizon PRL/Alltell Hybrid PRL, along with other guides involving EPST or ## codes found there)
Simply go to (via adb shell/terminal emulator) /sys/devices/virtual/usb_composite/diag and run (1 for on and 0 for off, respectively)
Code:
echo 1 > enable
echo 0 > enable
To simplify all this I've included a zip file which includes Gscript.apk for you to install, and two scripts in the Gscript directory (place entire Gscript directory on root of sdcard). Open Gscript application, then once open - menu button>add script>load file>diag on/off.sh>save for each script respectively. Then you can simply toggle on/off DIAG mode from the Gscript application (or even add shortcut>gscript>diag on/off from CM7 home screen, for each script respectively). And without further excess explanation, here's the .zip gscript_diagscripts.zip
By the way, if a mod reads this, could you please move to the Development section and remove my restriction? I know I don't have my whole 10 posts etc, etc, but I don't really have enough to say or the patience to say it most of the time to post 10 posts. However, I've lurked these boards and been rooting phones and flashing phones via this forum since my first android phone back from what feels like ages ago. (going on 4 rooted and flashed to cricket android phones now, all sold except my current, Dinc)
Click to expand...
Click to collapse
so wait let me get this straight. this mod is so we can update our prl??? or is this for people that would like to still run the altel hybrid prl?
because a simple *22899 will let you update it. i know this because i have been on cm7 nightly from day one and there was 1 update of the prl and it worked.
EVO + CM 7 + this solution = GO (GREEN LIGHT) WORKS.
Is there any way of running the ##3282# (if it's a file you run or an APK you install?)
Hows about this
i got one better for ya.
Code:
am start -a com.android.dmcommandservice.START -n com.android.dmportread/.DMPortActivity
what is so great about getting to Diag mode this way you say?
1. well it doesn't require root access.
2. its cross model supported. (well any model with the DMPortRead.apk installed which i have yet to see one without).
btw you can do the ##3282# in the same way... the apk is call EPST.apk. just look in the Android-Manifest.xml for the info.
tronoftroy said:
i got one better for ya.
Code:
am start -a com.android.dmcommandservice.START -n com.android.dmportread/.DMPortActivity
what is so great about getting to Diag mode this way you say?
1. well it doesn't require root access.
2. its cross model supported. (well any model with the DMPortRead.apk installed which i have yet to see one without).
btw you can do the ##3282# in the same way... the apk is call EPST.apk. just look in the Android-Manifest.xml for the info.
Click to expand...
Click to collapse
Remember, Im on CM7 GingerBread, not SENSE....
Ok so it should work on the EVO since the architecture is pretty much the same as the DINC. Now as far as it being for updating the PRL, yes it can be for that. But it is for people who need to use a program such as QPST or CDMA Workshop to change carrier based settings on their phones(IE the "flashing" [no not as in rom flashing, but carrier]). Where *228 and such is not a feasible replacement for doing so and would prevent their phone from functioning correctly, such as with mine which is flashed to cricket.
Any sort of *228 business breaks my cricket flash, and I used to have to make a backup and go back to restore a sense rom to go into the EPST app with ##778 or to be able to dial ##3424 to put the phone into DIAG mode where I could revise the settings again to make it function properly, THEN flash back since CM7 does not have the EPST.apk which supports both of these features.
With this you can avoid the whole hassle of all this if you have the QPST application for your PC by simply putting your phones DIAG mode ON or OFF. Where you can manually put in what ever PRL you want and manually set any carrier-specific settings. Not as convenient as EPST and its ##778 feature, but much more so than the previously described process.
ALSO I've now included all of this in a simple .zip file flashable from recovery to streamline this crude process a little more. Get it HERE. The file in the original post has been updated too.
m4f1050 said:
Remember, Im on CM7 GingerBread, not SENSE....
Click to expand...
Click to collapse
if CM7 doesn't have DMPortRead.apk couldn't you just push it to you framework/app folder? or even install the apk and just run that when ever you need to connect to the Diag port? (for Qpst, or what ever you need it for) i'm not very familiar with CM7 so i could be wrong.
i use it to send my own serial commands. i find qpst to be more of a hassle then helpful. manuf. have been making there own NV items that are not listed in Qpst models for a while now. ie. the ERI banner for some hero's is not pulled from the usual eri.xml but instead read from the NV items. i think NV item 8042.
now, i while i was snooping around with the flash command. i notice that you can use "-s" (i think, i could be thinking of fastboot.) to specify your own memory location to flash an img file to.
now if we can find the mem location of the NV items you can simply read your entire NV items as an .img then use flash cmd to write all your NV items at once, and maybe even with the Recovery update.zip. im looking into the recovery source atm. if anyone knows where the NV items are stored plz let me know. is it mtd or mem location?
Can you check if you have the file /sys/devices/virtual/usb_composite/diag/enable? If you do.. Create a GScript that echoes 0 or 1 (0 for disable and 1 for enable) to the file /sys/devices/virtual/usb_composite/diag/enable it works like a charm!
tronoftroy said:
if CM7 doesn't have DMPortRead.apk couldn't you just push it to you framework/app folder? or even install the apk and just run that when ever you need to connect to the Diag port? (for Qpst, or what ever you need it for) i'm not very familiar with CM7 so i could be wrong.
i use it to send my own serial commands. i find qpst to be more of a hassle then helpful. manuf. have been making there own NV items that are not listed in Qpst models for a while now. ie. the ERI banner for some hero's is not pulled from the usual eri.xml but instead read from the NV items. i think NV item 8042.
now, i while i was snooping around with the flash command. i notice that you can use "-s" (i think, i could be thinking of fastboot.) to specify your own memory location to flash an img file to.
now if we can find the mem location of the NV items you can simply read your entire NV items as an .img then use flash cmd to write all your NV items at once, and maybe even with the Recovery update.zip. im looking into the recovery source atm. if anyone knows where the NV items are stored plz let me know. is it mtd or mem location?
Click to expand...
Click to collapse
Hmmm... Can you write to NVItem 0,1 or 2 this way?
m4f1050 said:
Hmmm... Can you write to NVItem 0,1 or 2 this way?
Click to expand...
Click to collapse
yes. you can write any nv item through DM Mode. well almost any.
i guess some call the NV item image file SPL???... poking about on the forums seems like you are unable to backup the radio and the nvitems maybe stored within. just a guess though.
tronoftroy said:
yes. you can write any nv item through DM Mode. well almost any.
i guess some call the NV item image file SPL???... poking about on the forums seems like you are unable to backup the radio and the nvitems maybe stored within. just a guess though.
Click to expand...
Click to collapse
in EFS you can access NV items locked (on some HTC devices, tested with EVO 3D and EVO 4G) by creating folder "open sesame door" rebooting phone then going back to EFS the folder NVM should not have the lock, allowing you to see / write these NV items. So if you lack an easy to use NV Item browser you can use this approach.
Can you please update the link for the update.zip file to flash in recovery? Or if someone has it can you point me in the right direction?
I am trying to get QPST working with Sensation.
After echo'ing 1 to enable, the USB modem driver shows up. I dunno which driver u have used but I am using this one: http://forum.xda-developers.com/showthread.php?t=801570
and in QPST it doesn't recognize phone model so I can'T pull NV data from it.
any suggestions?
BTW I have QPST 2.7 Build 366
Curious! said:
I am trying to get QPST working with Sensation.
After echo'ing 1 to enable, the USB modem driver shows up. I dunno which driver u have used but I am using this one: http://forum.xda-developers.com/showthread.php?t=801570
and in QPST it doesn't recognize phone model so I can'T pull NV data from it.
any suggestions?
BTW I have QPST 2.7 Build 366
Click to expand...
Click to collapse
yeah, just open up your QPST Configuration. and set the Comport then your phone will show in QPST.
Hmmmm, modem? You're on 64 bit Windows 7? I recommend 32 bit..
Does this work on the evo??

Rooting the SCH i400 - Step by Step Instructions for Newbies

I just managed to root my SCH i400 (first ever rooting of any Android device for me).
I am very surprised by how smoothly it went, despite reports & warnings everywhere about complications (like this one - which should be totally ignored if you're using SuperOneClick v2.1.1 or higher).
For the benefit of n00bs like me who may be confused by multiple sources, resources, versions and problem reports, I am posting a step by step procedure that is confirmed (by me, on Windows XP SP3) to be working smoothly, without a single hitch of complications:
Phone: Make sure setting > applications > unknown sources is checked.
Phone: Make sure phone is in debugging mode.
Phone: Make sure SD card is unmounted!
PC: Make sure Windows USB driver for this phone installed and works
PC: Make sure .NET 3.51 SP1 is installed.
PC: Unzip SuperOneClickv2.1.1-ShortFuse.zip ==> C:\Program Files\SuperOneClickv2.1.1-ShortFuse
PC: Double-click SuperOneClick.exe
PC (in SuperOneClick): Make sure you're on the Universal tab (the only other tab is Samsung Captivate, which isn't the i400).
PC (in SuperOneClick): Now click the root button and wait for the process to complete.
PC (in SuperOneClick): "BusyBox not found. Would you like to install it?" Yes!
PC (in SuperOneClick): "Root install has completed! Would you like to run a test?" Yes!
PC (in SuperOneClick): "Your device has been rooted! Would you like to donate now?"
Exit SuperOneClick, unplug phone from USB, power down phone, power on phone. -- this step might not be mandatory, I just did it to be on the safe side.
Enjoy!
Great job on this tut.
Sent from my SCH-I400 using xda premium
Nice...
I may have to sneak my wife away from her for a bit....
Sent from my DROID using XDA App
Froyo is so nice... Here's how...
Hey guys... new poster here.
Just got a (Gently used) Samsung Continuum for free from Verizon after the power button on my G Droid 1 broke.
Anyways, after rcving it and realizing that it would only support Android 2.1 - I was slightly upset.
My D1 was rooted and modded to the max many times over with just about every ROM you can get.
So after reading up about IMNUTS leaking the Froyo download for the Continuum, my hopes were raised.
It is now debinged, debloated, lightening quick and amazing!
There may not be ROMS out there yet - but I truly hope some of you geniuses decide to make a few.
Just wanted to say thanks and encourage you to do some research before rooting it.
Here's what worked for me.
Odin 1.3
Continuum PIT.pit file
froyo_modem.tar.md5
cwm_recovery_test4_adryn.tar
cyan Clockwork Mod Recovery (BLUE, not yellow) (update.zip file, which is placed on the root of your SD card - renamed to update.zip)
stock_deodexed_ec03.zip (ROM)
(Place all of these files on your Desktop for easy access)
How to do it...
1. Connect your phone to your computer and Mount it.
2. Place the cyan CWM Recovery zip file to your SD card. (rename it to update.zip & do not put it in any folders. Just drag the file to your SD card - whatever drive it is listed as. Mine is my Removeable F
3. Make a new folder on your SD card. Name it whatever you want. (Mine is named "Froyo") Place the stock_deodexed_ec03.zip file in the folder on your SD card.
4. Open Odin 1.3 on your PC.
5. While your phone is off... hold the down volume button and connect it to your computer via USB. The yellow triangle will appear and it will say "Downloading". (Some people say to take the battery out, but my Odin program would not recognize my phone without the battery. Whichever works for you is fine.)
6. In Odin - Click the PIT file button. Load the Continuum.Pit.pit file into the file field. (Just double click it once you find the file from your Desktop.)
7. In Odin - Click the PDA button. Load the froyo_modem.tar.md5 file into the file field. (same as #6. Just double click it once you find the file from your Desktop.)
8. Click Start in Odin.
It should think for a minute, then say resetting, then say PASS
Then your phone will probably turn back on - turn it off again and reconnect it to your PC in download mode as stated in #5 above.
9. In Odin - Click the PDA button again. Load the cwm_recovery_test4_adryn.tar file as you did in #'s 6 and 7 above.
10. Click Start again in Odin... same as before. (thinking, resetting and PASS)
Your phone will turn on again.
11. Disconnect your phone from the computer & turn it off.
12. Hold both Volume buttons and turn it on. It will boot into the Samsung Recovery mode.
13. Use your Volume buttons to go down to highlight "apply update.zip" Then find the place where your normal Menu softkey would be and push it. The phone should then reboot into Clockwork Mod Recovery. It will be orangish.
14. In CWM, use the Volume buttons to highlight Backup/ Restore. Use the Power Button to choose it. Then at the next field, highlight Backup and make a backup.
15. After is makes the backup, press where the softkey Back button should be to go back to the original screen. From there, do a Wipe Data/ Factory reset. Do not forget to do this part.
16. Once it does the Data Wipe - go back to the main menu and and highlight & select the "zip from SD card" choice. Find your "Froyo" folder (of whatever you named it) and apply the stock_deodexed_ec03.zip file.
17. After that, go back to the main menu again and reboot your phone.
It may take a while, but your phone should restart in Froyo.
Of course, you have to re-sign in to your Google network...
Thanks so much guys for all the posts. Without them, is nowhere near as cool.
Hanging at Step #5, Now what?
Thank you for sharing. Wish I could say it went as smoothly for me with my SCH-I400 Continuum... I'm still working on it! I followed recommendations of several different developers/rooters. I've installed .Net Framework 4.0 and the SDK developers kit (who knows, maybe I'll start a new hobby...), and now when I run Superoneclick it hangs at step #5 with this message:
link_image[1728]: 3252 could not load needed library 'libdiskconfig.so' for './zergRush' (load_library[1058]: Library 'libdiskconfig.so' not found)CANNOT LINK EXECUTABLE
I have rebooted the computer and the phone, unmounted the SD card, settings to allow unknown sources, and turned on USB debugging. I'm not sure why the config file can't be found, and I don't know where to get it...
Do I need to reinstall the SDK? Or install the additional Java developers software? Or am I over-complicating this whole thing?
Any ideas will be greatly appreciated...
-James
Perhaps the easiest way is to flash a rooted ROM through Odin (or Heimdall)... Especially if you don't use Windows. This is how I did it:
http://forum.xda-developers.com/showthread.php?t=1203597
Two topics in one thread?
Hmmm... seems we have 2 things happening hear. 1: Rooting a Samsung Continuum, and 2: Flashing a ROM...
My concern is the "hang" at step five for Rooting my Continuum SCH-I400... Cant use a ROM until the dang thing is rooted, and can't seem to figure out the hang.
Tried Z4 root from the phone rather than through the PC and it hung indefinitely... Maybe there's a related issue, and I don't care if it's Superoneclick or Z4 that gets the job done.
Has anyone gotten past the same issue?
-James
bighigmt said:
Hmmm... seems we have 2 things happening hear. 1: Rooting a Samsung Continuum, and 2: Flashing a ROM...
My concern is the "hang" at step five for Rooting my Continuum SCH-I400... Cant use a ROM until the dang thing is rooted, and can't seem to figure out the hang.
Tried Z4 root from the phone rather than through the PC and it hung indefinitely... Maybe there's a related issue, and I don't care if it's Superoneclick or Z4 that gets the job done.
Has anyone gotten past the same issue?
-James
Click to expand...
Click to collapse
That's where you are over complicating. You don't actually have to root BEFORE you flash a new rom, if the rom is 'prerooted'. I've never rooted this thing via s1c or z4. I simply flashed the kernels via odin and flashed the rom in cwm.
Either let me fly or give me death. Let my soul rest, or take my breath. - DMX
Txwolf1980 said:
That's where you are over complicating. You don't actually have to root BEFORE you flash a new rom, if the rom is 'prerooted'. I've never rooted this thing via s1c or z4. I simply flashed the kernels via odin and flashed the rom in cwm.
Either let me fly or give me death. Let my soul rest, or take my breath. - DMX
Click to expand...
Click to collapse
That's fine Txwolf, but still doesn't address the issue... Or the original reason for this thread - Rooting - which is is essential for the programs I am going to run, and that is what I have been asking about...
bighigmt said:
That's fine Txwolf, but still doesn't address the issue... Or the original reason for this thread - Rooting - which is is essential for the programs I am going to run, and that is what I have been asking about...
Click to expand...
Click to collapse
The issue seems to be that you just have to use that little search box a little better via xda or your web browser and find more information the root program your trying to use.
When you give up on that you can take txwolf1980 's advice
PS hang on step 5 in OP? Or in 3rd post? That would be getting into dl mode lol
Sent from my SCH-I400 using xda premium
Come on now...
ciscogee said:
The issue seems to be that you just have to use that little search box a little better via xda or your web browser and find more information the root program your trying to use.
When you give up on that you can take txwolf1980 's advice
PS hang on step 5 in OP? Or in 3rd post? That would be getting into dl mode lol
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
I spent 6 hours last night troubleshooting, researching, digging deep, and "using that little search box." Seems to me You guys need to "just read the thread." It's about rooting your phone, period. If a forum is out there, I've probably read it. I'm using superoneclick to do it. SDK is installed. Net framework is installed. My error message frome SOC is above. When I am finally rooted, THEN I will install several programs - starting with a wifi tether.
I see you have the same phone as I do. Is it rooted with a one-click method? I also tried Z4root and didn't like it.
bighigmt said:
...Seems to me You guys need to "just read the thread."...
I see you have the same phone as I do. Is it rooted with a one-click method? I also tried Z4root and didn't like it.
Click to expand...
Click to collapse
well i did read the thread...
ive been out of town for a week and finally back on my pc... i would love to help you yet more info is needed.
you are running dl17 stock 2.1 correct?
what OS is your pc running?
and yes i have same phone as you. i have used superone click on ec03 build once.
just for root. but then flashed a deodexed rom to use custom mods and apps.
and since have been flashing rooted kernels, imnuts and adrynalynne have released most all of them.
there are a few ways to root the device, best bet is, as always is go to IRC.
clarity and patience are key, we all got to practice both
I rooted EC09 with soc no problem. If I send someone the EC09 could they extract the apks and send them to me? I deleted some sys apps for the ticker and rss feeds and need them back now to use it.
Sent from my SCH-I400 using xda premium
Unzip factory.rfs of ec09 to grab missing apks and put them on sdcard and install from there.
Sent from my SPH-M580BST using Tapatalk 2
verizonless said:
[*]PC (in SuperOneClick): Make sure you're on the Universal tab (the only other tab is Samsung Captivate, which isn't the i400).
Click to expand...
Click to collapse
FYI, my Windows Defender threat scanner just reported this SuperOneClickv2.1.1-ShortFuse.zip file as Exploit:AndroidOS/CVE-2011-1823, more specifically pointing at a file named Exploits/GingerBreak in that ZIP file.
I am going to delete this ZIP file as I no longer need it, but I got curious: Any idea what this means?
verizonless said:
FYI, my Windows Defender threat scanner just reported this SuperOneClickv2.1.1-ShortFuse.zip file as Exploit:AndroidOS/CVE-2011-1823, more specifically pointing at a file named Exploits/GingerBreak in that ZIP file.
I am going to delete this ZIP file as I no longer need it, but I got curious: Any idea what this means?
Click to expand...
Click to collapse
It means it'll root your phone. Some applications could try to do this without permission and do shady things with your phone. Nothing to worry about if your doing it on purpose.
trailblazer101 said:
It means it'll root your phone. Some applications could try to do this without permission and do shady things with your phone. Nothing to worry about if your doing it on purpose.
Click to expand...
Click to collapse
Im assuming by now everyone is on EG04 Gingerbread?

[Guide] Step by Step from Stock N910V 6.0.1 to hsbadr's CyanogenMod 13.0

Code:
/*
*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
IMPORTANT: Read the ENTIRE instructions set before starting, make sure you know what you are getting into. I have been as straight forward as possible with my instructions to assist noobs with the procedure.
Mission Statement
The purpose of this post is to combine the following 4 guides, in an easy to read manner to help people get from a stock Note 4 Version running 6.0.1 to a fully rooted Note 4 running CM13.0
Guides Referenced and Summarized:
[Guide] A noob's guide to Perm Root & TWRP on Verizon Note 4 Retail 5.1.1 (BPA1) http://forum.xda-developers.com/note-4-verizon/general/guide-noobs-guide-to-perm-root-twrp-t3360883
[HOWTO] Bootloader Unlock and Upgrade to Marshmallow [N910V] http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144
(no title, sub post #1403, describes going from CPD1 to Jasmine with CPF3 and Firmware/Kernel Patch) http://forum.xda-developers.com/showpost.php?p=67481370&postcount=1403
[ROM] [6.0.1] [UNOFFICIAL] CyanogenMod 13.0 [Jul 24, 2016] http://forum.xda-developers.com/note-4-verizon/development/cyanogenmod-t3253973
I will use large chunks from some of these guides, skip some parts not necessary and/or extrapolate/modify on the instructions given within.
Thankx & Achnologments
Main Contributors (I plagiarized, quoted, or sourced)
Robots_Never_Die
hsbadr
Tech Support
BickNasty
Feel like I missed you, it wasn't intentional....PM me and I'll consider adding you, if I feel you actually contributed in some way or I copied your work.
Satisfied Customers (Did my method work for you? Post a reply and let us know, I'll add you to the list)
jwp1299 - 1 hour
Viper-Link
keviinese - 1.5 hours
pfcland - 1.5 hours
Required Apps (Google Play) All Free
Search for and install these apps
eMMC Brickbug Check (free)
Required Downloads (note on version numbers: version numbers I specify are ones available at the time I wrote this guide. For most tool grab the newest version, such as Odin/ADB)
NOTICE Total size of Downloads is approximately 7 GB, some of the links may be slow! Time required may vary due to your network speeds, and luck with speeds from file hosts. (expect several hours)
ADB – minimal_adb_fastboot_v1.4.0_setup.exe
Odin - newest version (3.12.3 at time of writing)
Kingroot - Grab latest stable version, only grab NewKingroot(XXXXX).apk
Samsung USB drivers (windows) - newest version
Bootloader Unlock - samsung_unlock_n4-fix
TWRP - twrp-3.0.2-0-trltevzw.tar.md5
N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5
N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 (Alternate Torrent if slow: Torrent started by pfcland)
JasmineROM_v7.0_N910VVRU2CPF3.7z
N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z
Gapps For ARM SDK23 (Android 6.0) (mini version is recommended)
UNOFFICIAL CyanogenMod 13.0 Builds for Verizon Samsung Galaxy Note 4 (SM-N910V) (grab newest from top)
Xposed framework for ARM SDK 23 (NOTE: Grab both the xposed23.zip and XposedInstaller****.apk)
XPosed is OPTIONAL, but there are a lot of rooted apps that use the XPosed framework to get more control over your phone. Such as hiding mock locations for example.
NOTE: Internet is REQUIRED for KingRoot to function (grants temporary root, so ADP commands can be executed to unlock bootloader), at one point WiFi will NOT function but internet is still required. So a valid SIM with internet is required (Verizon will definitely work, others might[/] work)
NOTE: The entire installation will take an estimated 1-2 hours. (Not including time spent downloading) All steps are MANDATORY, do not SKIP anything....You've been warned
Install eMMC Brickbug Check (free) on your phone, and RUN IT. Your CID MUST start with 15. If it doesn't I can't help you, and this guide is not for you.
Install the Samsung USB drivers on your windows PC
Backup your phone, if you don't know how.....google it...And learn how, you will want to backup frequently. Every time you get to a point you can boot up into Android, backup...it's safer for you...I will not remind you again, this is on your head.
Disable Encryption on your phone, both the SD card and Device
Disable Samsung Phone Lockout. YOU MUST DO THIS OR ELSE!!!! (Settings > Security > Reactivation Lock)
Do 2 factory resets on your phone, one after another (hold volume up, home button, power when starting to enter recovery mode where you can reset phone). Not required but if you don't, you'll spend an extra hour or two doing this because Kingroot will crash/fail more often.
Boot up your phone in Download Mode (hold volume down, home button, power)
Open Odin3, Click the AP button and select the file N910VVRU2BPA1_N910VVZW2BPA1_VZW.tar.md5, once it checks it, goto options and make sure the Re-Partition is NOT selected. Now click start to flash and downgrade to Android 5.1.1.
Turn on your phone, and let it boot up.
Skip everything possible when setting up your phone. Don't even put in a google account, not necessary
Goto Setings and set the following
Settings > Security > Reactivation Lock = Disabled (EXTREMELY IMPORTANT, VERIFY)
Settings > Security > Unkown Sources = Enabled
Settings > Developer Options > USB debugging = Enabled
Developer options are unlocked by going to Settings > About Phone. Find "Build Number", and start clicking it till you get a message that Developer Options have been unlocked (about 10 clicks I believe, never counted).
Settings > Developer Options > Verify App via USB = Enabled (should be by default, CHECK)
Settings > Lock Screen = None
Settings > Display > Turn off Display = 10 Minutes
Plug your phone into your computer via USB, copy the NewKingroot****.apk to your download directory (samsung-sm-N910V\Phone\Download)
Install ADB onto your Windows PC. Select an easy directory such as c:\ADB
Copy the following file directly into the ADB directory
samsung_unlock_n4-fix
Open up command line interface. Hold windows key & press R key for run, type in "cmd" press enter. Will open a terminal window for you. Type the following commands:
cd\
cd adb (or whatever you named your directory where you installed ADB)
adb devices
This should return a list of devices you have connected, something like:
Code:
List of devices attached
SerialNum device
If no devices are displayed, check you have the Samsung USB drivers installed properly.
Type the following command
adb push samsung_unlock_n4-fix /data/local/tmp/
Got an error? check your spelling (or copy/paste from me), check you put the file into the ADB directory (not just a link), your phone must be on and screen not locked and check you have usb debugging enabled.
BTW: Do NOT CLOSE the window unless I instruct you to!
Install Kingroot on your phone, which you previously moved into your downloads folder, you can find it via My Files app that comes with phone.
Now run KingRoot. Flip down to the bottom and click "Try It", it will run some quick test then give you a button to try to root your phone.
Wait...Wait...Do not worry if your phone restarts, it will go back into KingRoot automatically on reboot. Just sit back and wait, it may fail multiple times and you may have to re-run Kingroot. Just keep trying . Once it succeeds you must do the following IMMEDIATELY AND AS FAST AS POSSIBLE. Kingroot is HIGHLY UNSTABLE.
On the windows PC, back in the command window you left open. Start Typing.
adb shell
su
cd /data/local/tmp/
chmod 777 samsung_unlock_n4-fix
chown root.root samsung_unlock_n4-fix
./samsung_unlock_n4-fix
After the last command it may prompt you to type yes, do so immediately. it won't write on the screen but type yes anyway for it to continue. Once it's done it should automatically start to reboot your phone. Unplug it and pull the battery, wait 5 seconds, put battery back in and plug the phone back in.
This was the initial setup for unlocking your bootloader, you now have to run it AGAIN so turn your phone back on. Repeat steps 22-24, after the 2nd time PULL OUT YOUR SD CARD BEFORE TURNING ON YOUR PHONE
Congratulations you now have an unlocked bootloader, you can close the command window on your PC.
The SD card has a restore point for your phone prior to removing your bootlock. Save it if you want, or plug into your phone and format the 18mb partition you are able to. You must format it on a PC before you can use it again in a phone!!!! Will shut your phone off immediately if you put the SD in without formatting that 18mb partition.
Now reboot your phone into download mode (hold volume down, home and power buttons when turning on)
Open Odin App on your PC, Click the "AP" button and select the file twrp-3.0.2-0-trltevzw.tar.md5 (which you downloaded earlier). Once it does it's check, verify that re-partition is NOT selected in options. Now click start to flash twrp bootloader.
Your phone will restart, re-enter download mode. If you missed it pull cable/battery and try again.
Now extract and flash N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5 via Odin, same as you did with twrp. VERIFY THAT RE-PARTITION IS NOT SELECTED IN OPTIONS.
Boot up in recovery mode (hold volume up, home and power when turning on) (note: no longer TWRP since you flashed firmware, will look different again)
"Wipe data/factory reset ", then reboot your phone.
Now repeat steps 9-12 (NewKingRoot should still be in your downloads, but verify anyway) (NOTICE: wifi will NOT work with the CPD1 firmware, but Verizon internet should in case you need internet for some reason, wifi will restore later in guide - Other internet from other providers MIGHT work with proper APN settings)
Install a clean SD card into the phone.
Now repeat steps 15-25. This time you should only need to run the samsung_unlock_n4-fix file once to break your boot. This is what it typically says on successful bootloader unlock: (if you got this message, pull the battery, cable and SD card.)
Code:
[email protected]:/ # cd /data/local/tmp/
[email protected]:/ # chmod 777 samsung_unlock_n4-fix <
[email protected]:/ # ./samsung_unlock_n4-fix
============================== samdunk unlock 0.0.1 ==============================
NOTE 3 BETA UNLOCK!!!!!!!!!!!!!
this application comes with NO WARRANTY (express or implied)
this binary may not be rehosted, repackaged, one-clicked, etc.
there is no support provided for this application
this application has been tested on the Verizon Galaxy S5 only
it may work on the AT&T Galaxy S5, and possibly other similar Galaxy devices
there are no compatibility checks, do your research first
if run on an incompatible phone, it will likely permanently ruin the device
we STRONGLY advise against running any binary not obtained from the official source
official source is available at http://github.com/beaups/SamsungCID
SD card is required, all data on the SD card will be destroyed
changing to this developer CID may have other implications
the psn derived from the CID may be used for critical services
changing this psn may cause unexpected behavior or loss of services
continue at your own risk, you've been warned
aboot dev signature research credit to ryanbg
http://forum.xda-developers.com/member.php?u=766721
eMMC vulnerability, exploit, and the code you are running by beaups (sean beaupre)
http://forum.xda-developers.com/member.php?u=711482
Do you understand the implications of these warnings?
(Yes/No)
[+] CID at boot time is/was: 150100523231384d4100657e54fc1200
[+] dev CID matching, proceeding to unlock
[+] backing up loaders, this will take a few minutes
[+] loaders successfully backed up
[+] success! powering off device, hopefully its not bricked!
Now boot back into download mode
Flash TWRP via Odin again (I'm summarizing greatly now, as you should by now understand this kind of shorthand)
Ok, now boot up into TWRP recovery mode (vol up, home, power)
Navigate through TWRP menus to create a Backup. Click Backup Button, and swipe to create backup. (this is just so that it creates the directory structure on your phone)
Click the Reboot System button, skip all the setup you can again. (DO NOT INSTALL SUPERSU!!! will cause bootloop)
Extract the "JasmineROM_v7.0_N910VVRU2CPF3.7z" file it will create a directory called "JasmineROM_v7.0_N910VVRU2CPF3".
Plug USB into phone and to computer. Copy the JasmineROM_v7.0_N910VVRU2CPF3 folder into \Internal storage\TWRP\BACKUPS\Phone SN\
Reboot into TWRP recovery
Click the Restore button (DONT start the restore yet!!!), and check that your JasmineROM is listed as a recovery option. (don't recover YET) If it's not there you copied it into the wrong directy, try again before proceeding.
Go back to the main menu, Click the Wipe button. Click the 'Advanced Wipe' button, and wipe the following cache/dalvik/system/data
Go back to Restore (from 2 steps ago) and run the JasmineROM_v7.0_N910VVRU2CPF3 recovery, return to main menu afterwards
Go to wipe, and wipe the cache/dalvik only this time.
Reboot into download mode
Flash the N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.m d5.7z file via Odin
Reboot the system, this will take a LONG TIME. WAIT for it. (if reboot takes >10 min, pull battery and restart)
Once it boots up, skip all the setup again. Copy the CM13, Gapps and XPosed (both zip and apk) to your downloads. Don't unzip anything, not necessary.
Now reboot into recovery go to WIPE and do a factory reset by swiping.
Then goto Install (still in recovery) and install CM13, then Install Gapps.
Reboot your phone, this time you are setting up properly reboot will take a while to optimize your apps depending on Gapps version used. So do all your setup as you want your phone setup. Once that's done, restart the phone in recovery. (if reboot takes > 5 min, pull battery and restart)
Install via TWRP the XPossed.zip file.
Reboot your phone, once on. Navigate via My Files, to downloads and install XPosed.apk
CONGRATULATIONS. You now have a fully Unlocked, Rooted Note 4 Verizon with CryanogenMod 13.0 installed and XPosed Installed.
Suggested Apps
Kernel Auditor [ROOT], will allow you to adjust kernel settings. Such as CPU clock speeds and thermal throttling, if your phone is too hot.
Note: About ROOT[/], you will have root once you finish this guide. But it is disabled by default, you can enable root in developer options (no reboot required when changing). Unlock your developer options again, and scroll down you will see an option to enable/disable root. This allows you to keep turn off during normal use, and only enable it when you need to install an app that requires root. You can always just leave it on all the time, that is your choice.
Note: Some apps on Google PlayStore will become unavailable due to incompatibility (according to google, HA). Such as YouTube Music, you will no longer be able to install it through the store. But you can install it by using an APK site, such as APK Downloader. On this site you find the app you want on play.google.com, copy the HTTP link and put it into the APK Downloader and it will generate a direct download link to the APK file. Copy onto your phone and sideload (ie. install) through file explorer. I don't endorse them, they are just one of many places you can get APK files.
Change Log
7/28/2016
Another success story :good:
Added note about how root works in CM 13.0
Corrected Step 34
Minor text adjustments, for clarification
Made note that wifi doesn't work with CDP1 flash
Added note that you MUST HAVE a valid sim card with internet access for step 35! KingRoot requires internet to function, and Wifi will NOT WORK after flashing CPD1 firmware (incomparable drivers).
Added another note about internet at the top of the instructions, to make sure people are aware.
7/27/2016
Added Bicknasty to the Contributors list - helped resolve issues I had with CM 13.0 kernel & modem.
Added a note to downloads section regarding total size of files downloaded and expected time.
Re-wrote steps 40-48 to make it easier to understand. Adding some steps and explaining in more detail.
Added note at the top to read ALL the instructions once before starting
Added note with the estimated time to perform all the steps
Added note suggesting Kernel Auditor app, and made reference to the fact that some apps on playstore will NOT install from playstore. Suggested APK Downloader for apps not available from store
Added a Success Story Section
Added note on how to enable developer options
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
jwp1299 said:
Any faster source for N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar.md5
Click to expand...
Click to collapse
Probably, but that's the only one I know which is a free download that I'd trust.
JacekRing said:
Probably, but that's the only one I know which is a free download that I'd trust.
Click to expand...
Click to collapse
Alright, still works just a little long. Thanks so much for the guide, working great so far!
jwp1299 said:
Alright, still works just a little long. Thanks so much for the guide, working great so far!
Click to expand...
Click to collapse
How far are you now?
And let me know when you finish, critique my guide. If parts weren't clear enough let me know.
And finally if you run into any issues let me know.
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
Yea I do appreciate the help Bicknasty. I'll add you to contributors list later as helping with cyanogen issues I was having.
Bicknasty said:
Great guide (I honestly haven't read it, it's too long but it looks thorough, and I know you were annoyed with the tedious process), glad I was able to help you figure things out!
Click to expand...
Click to collapse
You know it wasn't so much that it annoyed me it's that there was no concrete guide telling me what to do. It's a thread here, a post there to do a specific thing but they aren't coordinated in a logical way for users to easily find.
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
jwp1299 said:
Alright ignore what I said before this edit, I just skipped a step.
I must say though, steps 41-43 are very confusing. What is the ROM folder?
Click to expand...
Click to collapse
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
JacekRing said:
The ROM folder I'm referring too is the folder inside the Jasmine zip file. I only reference it so people wouldn't try to take just the files inside the folder which is inside the zip file. Lol yea that's confusing....I'll think about how to rewrite those and make adjustments in a couple hours to make it clearer.
But basically when you extract the Jasmine zip file it creates a folder with files in it. Copy the whole folder not just the files to where it makes your recovery folders.
Click to expand...
Click to collapse
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
Lol yea, didn't think to mention reading the whole thing first. To me that's a given I always read everything before starting. I'll add a note to read everything.
As to download time, well it is like what 12 gigs in total? Basically 4 full versions of the Android OS at 2 gigs reach plus all the extras.
I'll try to see if I can't explain the twrp recovery of Jasmine better. Only reason you need to do Jasmine is for the 6.0.1 device drivers (such as modem).
jwp1299 said:
Okay, awesome. Also I think the TWRP part could be explained a little clearer.
Other than that, 100%
oh also, at the start I would say to read the entire thing before starting, and give a warning that downloads will take like 4 hrs
Click to expand...
Click to collapse
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
JacekRing said:
I've modified the guide appropriately, to resolve all of the issues (I think) you mentioned. And to make some steps easier to understand and follow.
I also added a recommended app on the bottom, and mentioned a site you can use to get PlayStore apps which will now list as incompatible with our phones.
Finally, question: Did you succeed using this Guide? Just curious if everything is working as expected after following my guide. I wrote the thing from memory, after spending 3 days rooting my phone and figuring everything out from various sources. Hopefully this saves people some time where they don't have to piece a dozen sources together to figure out how to do it. I only mentioned the main 4 I referenced, but there were other lessons learned from various places that aren't covered in those posts.
Click to expand...
Click to collapse
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
jwp1299 said:
I was quite successful with the root. Even though I messed up a few times (skipping steps), it all works out and now it's working lovely. It only took an hour of actual work, plus a lot of download time because of slow hosts.
Thanks so much for the guide, the only issue was with the slow hosts, and that's hardly your fault. I do wonder if maybe setting up a torrent of the heavier files might help though.
Edit: I will say, this is a wonderfully tedious root effort.
Click to expand...
Click to collapse
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
JacekRing said:
An hour..........I spent 2 hours watching kingroot try and root my damb phone, LOL because I didn't wipe before trying to get temporary root the first time you use it (before I read in a post that wiping twice will make it MUCH more successful). Took me 10+ hours of actual work to get my phone rooted and CM 13.0 setup, because I didn't have steps to follow, LMAO. Made it up as I went.
As to the Torrent, I'd be the only one sharing and my upload speeds are not that great. maybe 500 kbps, I live in a rural area. At least my download speed is 40 mbps.
And it is hellofa tedious root for the Note 4, I haven't seen any other phone as crazy tedious to root.
Edit: Mind if I add a 'success story' section and add you to it?
Click to expand...
Click to collapse
Oh of course, go ahead and add me.
Also, if you do end up making a torrent, i'd be happy to help seed at least for a while. I have pretty good upload and no data caps or anything so it would probably help a bit (anything is faster than that 100 kbps that xda was giving)
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Viper-Link said:
You called N910VVRU2BPA1_N910VVZW2BPA1_VZW.zip, "N910VVRU2BPA1 Full Firmware". Which kinda got me confused, (maybe its just me trying to do this at 1 am >_>) but might want to edit that. Other then that Iv'e had a pretty easy time following this guide. Thanks! (still doing it fyi, I got an infinite bootloop, so figured I messed up somewhere after reflashing TWRP, now im starting from scratch.)
Click to expand...
Click to collapse
Not sure what to tell you viper as not enough info. Hope you figured it out...
pfcland said:
I have a Very weird problem , I followed your instructions correctly i was on step 25 did exactly what you said pulled the unpluged the USB and pulled the battery and and waited 5 seconds and put the battery back in and rebooted the phone only problem is now it is stuck in a boot loop of the image Samsung galaxy note 4 and just keeps rebooting . I haved tryed doing a factory reset and wiping cache and reinstalling 5.1..1 via odin and it is still doing the boot loop i am not sure what i did wrong or what to do . I know its not hard brick because i can get into recovery and download but just wont boot the past the Samsung not 4 logo
---------- Post added at 05:05 AM ---------- Previous post was at 04:57 AM ----------
Ok so i went and wiped and factory rest like 10 times and now it got past the screen So that is a relief lol
Click to expand...
Click to collapse
Was this after the first time you inputted the adb commands our second? Make sure you pull the SD card after the second time, as it will cause reboots after the second time until you reformat the SD card on your PC. Size will be wrong on PC but size will fix when you reformat the SD card a second time on your phone.
Edit it creates like 20 partitions on the ad card when you do adb, it creates a backup of your phone os.

Categories

Resources