Develop Bugs

[GUIDE][ROOT][19/Nov] r14: VISIONary + one click root

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: This application is no longer being updated and is only recommended for use on Froyo builds.
What is VISIONary?
VISIONary (so named because it was originally an application designed for the T-Mobile G2 / HTC Vision) is an application you install on your device that allows you to Temproot or optionally Permroot your device, using the 'rageagainstthecage' exploit.
How do I use it?
It's pretty simple really. The options appear as follows:
Temproot on boot - use this to automatically Temproot on each boot (I suggest Temprooting manually first to confirm all is well before enabling this)
Run visionary.sh after root - this allows you to run a script (as root) after rooting. The script file is /data/local/visionary.sh
Set system r/w after root - this allows you to leave the /system partition read/write after root
Temproot now - root temporarily (the root wil be lost after reboot)
Attempt permroot now - attempt to apply a permanent root (please read the safety information below before doing this!)
Unroot now - this will unroot your device
Safety information!
You use VISIONary at your own risk! Although we test it as much as possible, we are unable to guarantee that weird things won't happen.
As a rule, the 'Temproot' option of VISIONary should be completely safe. It installs an application (Superuser) in the conventional way and then sets up a 'ramdisk' for the other parts, which is wiped on boot. As such, no changes are made to the system partition of your device, hence it is considered a 'safe options'.
Permroot on the other hand is inherently more risky. Permroot does make changes to the /system partition of your device. Technically speaking the only change that is made is the installation of a small file to /system/xbin, but any system partition change comes with risks. If you try to permroot, be aware that you might get into a situation where your device will not boot. For this reason, we recommend you have a 'safety net'.
In general, the best 'safety net' for going ahead and doing a Permroot is ensuring that you have a copy of the stock ROM to reinstall should things go wrong. This should be an original update EXE or zip from your device manufacturer / provider which matches the software version currently installed on your device. Bear in mind that flashing older versions is often not possible, so if your device has been updated over-the-air, an update may not yet be available in this form. Hence, you may not be able to find a 'safety net' and attempting to Permroot would be inherently risky. For HTC devices at least, one option would be to Temproot, edit the MISC partition to revert the 'mainver' to an older version, thereby allowing you to flash an update older than the currently installed version should things go wrong. That option is currently outside the scope of this post, although I will provide details on how to accomplish this in another post.
Got your safety net? Aware of the risks? The download is below.
Download
r14 - (see changelog below for details) - [url="http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/]DOWNLOAD[/url]
The download is in APK format (if it is downloaded with a 'zip' extension simply rename). Copy to your device and click to install (or run 'adb install -r com.modaco.visionaryplus.r14.apk' if you have the SDK installed).
NOTE: USB DEBUGGING MUST BE ENABLED FOR VISIONARY TO WORK!
And finally
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P

thanks for you guys work

works perfectly! thanks

Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App

Question Answered..
Thank you P, my reboot question has been answered... just click and proceed. (To Be Tested)
It feels so good to see you on the scene.. It's been a while.. Since the N1

v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Same here

v8pwrdz28 said:
Does nothing for me, just sits there saying rooting device, flashes every few seconds
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Reboot and try again...
P

paulobrien said:
Reboot and try again...
P
Click to expand...
Click to collapse
How long should the program run?

I have no experience whatsoever in developing or rooting on Android, so excuse me if this is a stupid question. When you say that if we want something to happen every time we finish rooting at bootup, to put it in /data/local/visionary.sh, what exactly does that mean? How does one go about doing this?

when i run this it just keeps saying rooting device with spinning wheel at top then it reboots

Not Working
Just getting the spinning wheel and flashing with no progress. Even tried to reboot and start over with no results

Thank you for making my life easier.

Does this app require you to do the "one-time" first step of the temp root process before you can use it?

Like others have said, this doesnt work for me. Just flashes rooting please wait and nothing happens.

Hey thanks it worked .. At first it kept running and nothing happened, so i rebooted the phone and it worked in the first try.

LogicHell said:
Does this app require you to do the "one-time" first step of the temp root process before you can use it?
Click to expand...
Click to collapse
No...
P

What should happen...
Boot device
Click VISIONary icon
Phase 1 runs
Logo disappears briefly as app reloads
Phase 2 runs
App disappears and root is complete
If this doesn't happen, I suggest rebooting and trying again.
P

Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Disconn3ct said:
FYI I altered the script to survive cache flushes and such. If you use this instead of the old 'root' script (and put everything in /data/local/bin instead of tmp) it will make the bare mininum number of changes to /system and those changes will last until you reboot (instead of flushing out over time).
Click to expand...
Click to collapse

Auto Root
I downloaded Startup Manager from the Market and set VISIONary to auto load on each bootup and so as of right now it auto loads with each restart. Very handy until it auto loads on itself. Just a thought.

Disconn3ct said:
Does it use the old 'root' script (copy everything to /system/bin and /system/app) or the new method? The old one expires eventually when linux drops the cache, the new one stays forever (until reboot). (Also, putting superuser on /data/app means it remembers it's permissions and grants across reboot, instead of losing it every time.)
The updated script is here:
Click to expand...
Click to collapse
Good call on putting the Superuser APK on /system/app! re: the 'old' or 'new' way, i'm doing it the old fashioned way (didn't know there was another way, heh)!
If you can point me to it, i'll change it for r2.
P

[Q] mmcblk0 error, please help

Hi, I need some help, i was changing the partition sizes of my SD card with "mini tool partition wizard" and now my phone doesn't recognize my sd card, i can access it from recovery (clockwork 2.5.0.7) to transfer files but that is it, Apps on my phone dont see an sd card, Astro and other file managers say 'please insert sd card', same for HTC music and gallery apps. Nandroid restore gives me 'md5 sum's don't match' when i get into recovery i get these 2 error messages:
choose zip from sd card
E: cant mount /dev/block/mmcblk0 (or /dev/block/mmcblk0p1)
(invalid argument)
Wipe data/factory reset
E: cant mount /sdcard
E: cant mount /dev/block/mmcblk0p2
(file exists)
I have formatted the whole SD card using windows disk management and still getting the same error. Different SD cards are also having the same affect
Ive used the search function and cant find the same error to mine
Any help please?
Thank you, Jack
*edit* im also finding it hard to use the sdk to push files because i'm constantly getting the message "failed to copy (file) to (file):Read only File System

hi,
did you used ext partition ??
if so should fat32 first and then extx
but if other sdcard didn't fixe it and you can acces fasboot commnad
did you already try ?
Code:
fastboot oem enableqxdm 0
hope this help

The same error? There must be loads of topics or posts that have the same issue as you. Look harder.
It use to do it to me but I ignored it since I don't use a2sd. No idea how I fixed it. There are solutions. Use Google if you have to.
Sent from CM7

fragargon said:
hi,
did you used ext partition ??
if so should fat32 first and then extx
but if other sdcard didn't fixe it and you can acces fasboot commnad
did you already try ?
Code:
fastboot oem enableqxdm 0
hope this help
Click to expand...
Click to collapse
Thanks for the reply
I was using EXT3 but formatted the whole card to fat32. Tried the fastboot command and nothing changed. thanks for the help anyway

did you formated with primary partition fat32 such error gives a bad partition tables... good fat32 primary part label lba
look harder there is plenty such messages... felt that when partionning with win you lose the mont point... use gparted instead
there is llive cd gparted on the net... googlise

Check as well with minitool partition wizard that your sd card is NOT partitioned as FAT32 "Logical", the SD must be labeled as "primary" to work.

Just checked and it is Primary fat32, il be reformatting again with gParted in a few weeks, i left my SD adapter at university and gParted doesn't detect the phone in recovery, somehow i have made some progress and can now flash a new ROM and restore via nandroid. so i went back to an old restore but i am still getting an error. I still cannot wipe data/factory reset because i get the same error. Thanks for the help so far

It could be that the SD card is damage..
What I did in the past when I had an error with it, is to connect the SD card trough a card reader on a win 7OS, and with the partition manager built in it done a full format.
It's always worked for me, but since you have done it already...
Good luck anyway!

The Professor said:
Kubino was spot on - the misc overwrite was what caused the issue. If you modify a misc.img to include your CID and flash it back to mtd0, you will restore functionality. I can confirm that USB, BT, FM, recovery all work again on my Desire. The only thing we're not certain about is whether the ROM value in misc.img matters at all, but it doesn't appear to.
Stupid amounts of props go to IEF and adam235 at MoDaCo and kubino here. Thanks to all of you, so much.
MOD EDIT:
below is the post, as this was a combined effort, we don't need to link to modaco.....
As most of you know, people have been hard at work to fix the USB issues we've been seeing due to recovery setting us into USB debugmode.
After unsuccessful attempts to change the kernel commandline , eg. to:
board_bravo.disable_uart3=0
board_bravo.usb_h2w_sw=0
we've been successful in discovering (with the help of XDA-developers) that these switches are stored in the first NAND partition, mtd0, or 'misc'.
You must be rooted to try the following, it seems you can't write to mtd0 without root.
Do step 1 again if you have to.
Also, SD card functionality has to work. For this, do 'fastboot oem enableqxdm 0' in fastboot mode.
Steps involved:
1. Find out your CID. Go into fastboot mode, and do 'fastboot oem boot'.
The log will say something like the following:
CODE
#INFOTAG:Ramdisk OK
#INFOTAG:smi ok, size = 0
#INFOTAG:hwid 0x0
#INFOTAG:skuid 0x21F04
#INFOTAG:hero panel = 0x0
#INFOTAG:engineerid = 0x0
#INFOMCP dual-die
#INFOMCP dual-die
#INFOTAG:mono-die = 0x0
#INFODevice CID is not super CID
#INFOCID is HTC__E11
In this specific case, the CID is HTC__E11.
2. Get the following mtd0.img from the attached files below
Edit this image to the CID you found above with a hex editor.
Optionally, you can use this CID generator by stevebrush instead. Untested by me, but it should work properly.
//Edit: Updated link location for stevebrush. Thanks a ton for the generator!
3. Get flash_image from the attached files below
Move this to /data/ , and flash the modified image using:
"/data/flash_image misc /data/mtd0.img"
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator:
'cat /sdcard/flash_image > /data/flash_image'
'cat /sdcard/mtd0.img > /data/mtd0.img'
You might have to do 'chmod u+x /data/flash_image' before you run the commands (or chmod 755 /data/flash_image)
4. Repeat step 3 a couple of times if it doesn't seem to work well.
5. All done! Reboot, you should have normal usb connectivity. Post your 'fastboot oem boot' log and intermediate steps if it fails.
Credits:
-kubino @ XDA for providing us with the 'misc' information
-TheProfessor @ irc.freenode.net #modaco for being the first test subject + debugging
-adam235 @ irc.freenode.net #modaco for being a test subject as well + debugging
-SgtDavePwnage @ irc.freenode.net #modaco -> moral support + debugging
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-DrMon @ irc.freenode.net #modaco -> being brave enough to test on his non-bricked device!
Click to expand...
Click to collapse
Sent from my HTC Desire using XDA Premium App
Brrp all problems will be fixed
Sent from my HTC Desire using XDA Premium App

Hi; it 's kind of you reaper but the fix mentionned in the kubino s thread is about misc error partition...
This is not mccblok0 error and would not advice to follow the tips for misc issues... ( misc issued is like USB brick)
Sent from my HTC Desire using XDA App

This thing happened to me and it took me a week to figure out the solution....
Here's what you need to do;
Boot from Linux...
Use Gparted...
make sure it is formatted as FAT32..
create ext1 & ext2.
keep the ext1 & 2 unallocated
Format the SD card to your phone using the recovery
Reboot and test to see if the issue is resolved
(*note: sometimes you can format the SD without booting into recovery, just do it inside the running Android OS....Settings/Storage**you know where to playaround for sure)
If anyone has a better solution,,,I am open for correction.
Just my few cents.

the stuff i posted fixes the misc error bcuz u flash a new one over the corrupted one Mtd0.img

[Q] Dinc corrupt primary file system *serious software help needed*

to start off with here is the problem list:
1) any rom, ruu, etc loaded will not boot past htc screen and if they do it boot loops 5 seconds into the animation.
2) clockwork reads error, E: /dev/block/xxxxxxxxxxx and cant mount data or cache partitions.
3) when doing a cat of mounts there are only five items instead of the 20 an unrooted stock phone possesses.
so in short i am asking for ideas maybe i have not tried "be creative here" to recover or reinstall "in my opinion the best fix" the whole main file system. just as if it was merely hardware blank from the factory. maybe push over new /dev, /system, /data, /cache etc etc as i believe the file system is corrupted and missing directories.
thanks for your time and thoughts...
*edit* i have been trouble shooting with the brilliant guys over at incredibleforum as well and thus whats lead me to my question here. so the back story, everything i've tried already, findings, and pictures are already posted here (not to violate TOS just for reference):
incredibleforum . com/forum/htc-incredible-rescue-squad/10812-boot-loop-after-exhausting-ever-possible-fix-my-head-experiance-help.html

Have you tried to ruu to stock froyo, and then do a factory reset thru hboot? Also when you say you ruu'd before did you do the PB31IMG.zip ruu or the ruu exe, or did you try both? Also have you at some point gotten the 5 vibes of death while booting?

i have done the ruu's both in hboot pb31img and via the exe while i booted into hboot. and i've never gotten nor heard of the five vibes. but exploring the file system there are directories missing for some reason. so i'm figuring the ruu's and roms aren't installing certain files due to not having a place to put them.

Sounds bad to me. I know they say if it turns on its not bricked, but if an ruu cant write to the partitions you will probably never be able to find a way to either. Hey im not an expert though by any means. Hope some one can help you figure it out.

the ruu cant write to the partitions because they don't seem to exist or the mounts for those directories. thats why i'm interested in finding a way to rewrite the partitions back to factory. there is a way because the phone wasn't built with this file system on it so there is a way to write /dev /system /cache /data etc.. maybe even a way to pull it off a stock phone and write to this one?? i can adb shell and view all of the files so i know its accessible. and hboot and recovery both work and can flash successfully. come on xda don't let me down i know there are some really brilliant and creative minds out there who think this is an easy fix to them.

tophkr said:
the ruu cant write to the partitions because they don't seem to exist or the mounts for those directories. thats why i'm interested in finding a way to rewrite the partitions back to factory. there is a way because the phone wasn't built with this file system on it so there is a way to write /dev /system /cache /data etc.. maybe even a way to pull it off a stock phone and write to this one?? i can adb shell and view all of the files so i know its accessible. and hboot and recovery both work and can flash successfully. come on xda don't let me down i know there are some really brilliant and creative minds out there who think this is an easy fix to them.
Click to expand...
Click to collapse
which hBOOT do you have? have you tried to reinstall the hBOOT?
http://pvillecomp.com/?page_id=4
after you reinstall hBOOT then try to ruu with the .exe

synisterwolf said:
which hBOOT do you have? have you tried to reinstall the hBOOT?
http://pvillecomp.com/?page_id=4
after you reinstall hBOOT then try to ruu with the .exe
Click to expand...
Click to collapse
+1 for reflashing hboot.
An ruu is ment to program the phone as if it were strait off the line never touched. It should create the file structure and partitions if they dont exist. What bothers me about your problem is that flashing roms or dooing ruu's compleet sucessfully without error. If the ruu cant write to these partitions it should stop and give an error, not just continue as if everything is ok. So to me it seems its writing to them fine but then for some reason cant read from them. Same for flashing a rom if it cant mount the partitions it should halt and give an error.

cmlusco said:
+1 for reflashing hboot.
An ruu is ment to program the phone as if it were strait off the line never touched. It should create the file structure and partitions if they dont exist. What bothers me about your problem is that flashing roms or dooing ruu's compleet sucessfully without error. If the ruu cant write to these partitions it should stop and give an error, not just continue as if everything is ok. So to me it seems its writing to them fine but then for some reason cant read from them. Same for flashing a rom if it cant mount the partitions it should halt and give an error.
Click to expand...
Click to collapse
well you have have a partition that has blocked write access so when RUU reads it, it works but when it try's to write it skips it.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i currently have .92 installed but i've gone back as far as .77 due to it being the development copy with full fastboot and adb capabilities. but i will try to reflash hboot .92 and then run ruu from computer while still in hboot.. worth a shot

You could try this. Sounds like your issue. Post 3.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/page__st__20

tried that and i'm guessing the correct partitions are no longer there because i recieve this:
Error: /dev/block/mmcblk0: unrecognised disk label
and get that with every partition in the mmcblk catagory

ok so i have a question based on a possible cause to this problem.. if the prebious owner had flashed a droid incredible 2 rom insted of a DINC rom.. i know that can cause issues flashing the wrong roms.. how would you go about fixing that?

tophkr said:
ok so i have a question based on a possible cause to this problem.. if the prebious owner had flashed a droid incredible 2 rom insted of a DINC rom.. i know that can cause issues flashing the wrong roms.. how would you go about fixing that?
Click to expand...
Click to collapse
Did you try the link on the last page?
Sent from my sexy assistant. (AMOLED HTC Incredible)

synisterwolf said:
Did you try the link on the last page?
Sent from my sexy assistant. (AMOLED HTC Incredible)
Click to expand...
Click to collapse
the link to using parted to fix the partition format.. yes but those folders do not exist. when i show a list of my mounted partitions cache, data, system and a few others don't show up in the list at all. so because they don't exist anymore i don't know what partitions to remake or what folders need to go in them, which to mount etc.

So when you run the RUU's and PBIMG's they complete successfully without error?
also on a kind of related note, have you looked into booting a rom from your SD card or internal storage? Its not a fix or anything just merely might give you the satisfaction that your phone can boot a rom lol though it might not be by the traditional or standard means

nope i've never looked into how to boot a rom from internal storage. could you supply a link to instructions as this might be a temp fix while i continue to try and fix this.
and yes when i run them they compleate with no errors. only errors appear when looking in recovery.

tophkr said:
nope i've never looked into how to boot a rom from internal storage. could you supply a link to instructions as this might be a temp fix while i continue to try and fix this.
and yes when i run them they compleate with no errors. only errors appear when looking in recovery.
Click to expand...
Click to collapse
I would try a Google or XDA search because I've never tried it myself. Last I remember punk.kaos did it back when I had an Eris and I think more recently conap did it with the Incredible. Sorry I couldn't be of more help :/

i'm going to look into it but i've never heard of it being done except on the hd2 and hd7 using ram loading. but thanks for the ideas

Please Help! - Never doing this again! {SOLVED}

Ok so long story short I tried to upgrade to Android 6.0 and in the process completely messed up the Screen Calibration on my Verizon Note 4 (SM-N910V) phone (wherever I press it is an 1 inch off)
On Verizon devices you cannot use the *#2663# trick to bring up the calibration menu without having a rooted device.
So after extensive reading it seems that I have to access the HIDDEN_MENU file and edit it which will require the phone being permanent rooted.
So in order to perma-root the device I guess I have to downgrade to KitKat 4.4
Whenever I go to use Odin 3.12.7 to load the stock firmware (N910VVRU1ANJ5 it FAILS! and the phone says
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOT: ENABLE (CSC)
AP SWREV: S1, T2, A1, A2, P1
SECURE DOWNLOAD: ENABLE
UDC START
SW REV CHECK FAIL: [aboot] Fused 2 > Binary 1
[1] eMMC write fail: ABOOT
It was a Developer Edition... probably not anymore... i probably screwed that up. but whatever...
I dont even care about rooting or upgrading anymore.... I just want my phone Calibration back right!!! Can anybody help!?!?! :crying:
CURRENT PHONE STATUS
Android 6.0 (N910VVRU2CQF2) installed

Just tried to flash to N910VVRU1ANI1_N910VVZW1ANI1_VZW also and it still fails...
phone says
SW REV CHECK FAIL: [aboot] Fused 2 > Binary 1
[1] eMMC write fail: ABOOT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Get Root in Odin: https://download.chainfire.eu/590/CF-Root/CF-Auto-Root/CF-Auto-Root-trltevzw-trltevzw-smn910v.zip
For MMB29M.N910VVRU2CQF2 Developer.
And Take TWRP/SU.

maxnuk said:
Get Root in Odin: https://download.chainfire.eu/590/CF-Root/CF-Auto-Root/CF-Auto-Root-trltevzw-trltevzw-smn910v.zip
For MMB29M.N910VVRU2CQF2 Developer.
And Take TWRP/SU.
Click to expand...
Click to collapse
Ok THANK YOU but let me ask some details so I understand your last post...
Get Root in Odin... ok I will try but under what firmware do you want me to be.... N910VVRU2CQF2 ??
What is the difference between MMB29M.N910VVRU2CQF2 Developer and https://www.sammobile.com/firmwares/galaxy-note4/SM-N910V/VZW/download/N910VVRU2CQF2/183597/
are they the same...? If not then where do I get MMB29M.N910VVRU2CQF2 Developer ????
And what do you mean "Take TWRP/SU" ? Do you mean try and install TWRP with Odin and then TWRP install SU afterwards??
Thanks for any help.

Ok while I was waiting for maxnuk and others replies I was able to temp-root with KingRoot and change /efs/carrier/HiddenMenu contents via ADB
Code:
F:\android\sdk\platform-tools>adb shell
[email protected]:/ $ su
[email protected]:/ # rm /efs/carrier/HiddenMenu
[email protected]:/ # cp /sdcard/HiddenMenuOn /efs/carrier/HiddenMenu
[email protected]:/ # cd /efs/carrier
[email protected]:/efs/carrier # ls
HiddenMenu
[email protected]:/efs/carrier #
But *#2663# still DOESNT WORK!! and the calibration is still way off!

zdanman said:
Ok THANK YOU but let me ask some details so I understand your last post...
Click to expand...
Click to collapse
You have "CURRENT PHONE STATUS - Android 6.0 (N910VVRU2CQF2) installed", that right ??
But this is ROM for Retail... (You lost Developer, becouse you not have Backup your ABOOT??)
Do you have twrp ?
"Get Root in Odin... ok I will try but under what firmware do you want me to be.... N910VVRU2CQF2 ??"
Yes, this CF-autoroot for this CQF2. Root Perm, not Temp.

please see next post

PS I figured I'd mention this here aswell
I have the following TWRP backups:
And the contents of each:

maxnuk said:
You have "CURRENT PHONE STATUS - Android 6.0 (N910VVRU2CQF2) installed", that right ??
But this is ROM for Retail... (You lost Developer, becouse you not have Backup your ABOOT??)
Do you have twrp ?
"Get Root in Odin... ok I will try but under what firmware do you want me to be.... N910VVRU2CQF2 ??"
Yes, this CF-autoroot for this CQF2. Root Perm, not Temp.
Click to expand...
Click to collapse
Yes I have N910VVRU2CQF2 installed and can install N910VVRU2BPA1 easily as well however KitKat N910VVRU1ANJ5 fails everytime I try to install with Odin
As far as a Backup, I don't know really...
I created a TWRP backup (when my phone was KitKat 4.4) and checked all the boxes and it contains the following files....
I see there is a boot file in there so idk... I'm too noob to understand what they are.
I can possibly get TWRP back on here again (by downgrading to 5.1.1 and kingrooting and then run samsung_unlock_n4-fix and then use odin to install/flash the TWRP recovery img etc....)
I also, this morning, tried using TWRP to restore the backup mentioned before but then I get a startup loop (Samsung Galaxy Note 4 custom screen loop) even after doing a factory reset.
Somewhere during my whole upgrade rooting process my device id changed from a448c46d to 657e54fc btw so maybe this is the problem idk

What's your problem now? (you don't need kingroot if you already have twrp ... Only put SupeRoot.zip in Twrp)

see next post

maxnuk said:
What's your problem now? (you don't need kingroot if you already have twrp ... Only put SupeRoot.zip in Twrp)
Click to expand...
Click to collapse
Ok.... well if you use TWRP's superuser rooting interface (the option given when you are exiting TWRP when it says "it doesnt look like your phone is rooted try now?") if you do that then you get the infinite boot loop glitch I don't know what you mean by that.
Any way heres the UPDATE so far....
[UPDATE]
It looks like I've successfully installed ModestRom.v9 although I didn't do a full Android 6.0 installed before hand.... only a Android 5.1.1 but it still runs so I'm assuming its fine.
Its also ROOTED with Magisk!
However I'm still having major Calibration problems... I really cant even use the touch screen with my hands... pretty much have to do everything with the pen.... :/
So right now I'm trying to figure out how to do the TSP FW update which I guess can only be done via the *#2663# keycode and since this phone is Verizon... you can't use the secret keycodes!!!!
I tried this app which supposedly forces this but it doesnt work.... https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en
You think it should be no problem because this is TouchWiz ROM that is rooted but apparently Verizon has blocked the TSP interface it some other way....
Please help maxnuk... thanks in advance
I hate you Verizon.... so much....
Heres the screens...

Again.... I have ROOT now... please help me fix my calibration!

THANK GOD AND THE HEAVENS ABOVE! :highfive::highfive::victory::victory::victory:
Fixed the calibration...
So we made sure /efs/carrier/HiddenMenu contained the word "ON" instead of off
and we used the Phone INFO ★Samsung★ app to force the 2663 secret code to run.... however this stupid freaking app requires you to try to run the command like 10 times because it tries the throw adds at you every time instead of actually running it.... garbage... but AT LEAST IT WORKED...
Now I have a rooted custom ROM Android 6.0 Note 4... :fingers-crossed:
WHAT A FKN NIGHTMARE THAT WAS

Q beta 5 is GREAT,but can not mount /system for now

I've tried Magisk Canary and different TWRP versions , even wipe system (It can be mounted when it‘s empty - -)

seardna said:
I've tried Magisk Canary and different TWRP versions , even wipe system (It can be mounted when it‘s empty - -)
Click to expand...
Click to collapse
Happened to me before. I believe I cleared the system partition and it worked.

TechNash said:
Happened to me before. I believe I cleared the system partition and it worked.
Click to expand...
Click to collapse
Please tell me the version of magisk and twrp you use?
I tried to wipe the system ,data , all partitions has been wiped with TWRP 3.3.0 . Than flash-all with -w.
Maybe some steps wrong, I have no idea .

seardna said:
Please tell me the version of magisk and twrp you use?
I tried to wipe the system ,data , all partitions has been wiped with TWRP 3.3.0 . Than flash-all with -w.
Maybe some steps wrong, I have no idea .
Click to expand...
Click to collapse
Latest TWRP from website, magisk stable

TechNash said:
Latest TWRP from website, magisk stable
Click to expand...
Click to collapse
Thanks. But can you mount system in the TWRP? While install Magisk , there are some errors failed to mount /system (Invalid argument )

Would this be why titanium backup doesn't open either ??

this happened with beta 4 also. don't know if it's twrp or magisk issue

Q5,same issue here, tried everything, factory reset, format partition, no luck
apart from this, everything works
in root explorer, you can't mount R/W

A latest magisk alpha version maybe solved this problem .
Here is the custom channel :backup up FIRST!
https://raw.githubusercontent.com/yzkpqv68745/magisk/master/alpha.json

solución
hello good forgive my English is not very good but I will tell you the solution I had the same problem the solution is that you have to go mount and select read mode and check the boxes then install the twrp in zip and then magisk and will not give you the system saddle problem and vendor I have magisk running that way if you have any questions let me know and I help you a greeting.

ismael47 said:
hello good forgive my English is not very good but I will tell you the solution I had the same problem the solution is that you have to go mount and select read mode and check the boxes then install the twrp in zip and then magisk and will not give you the system saddle problem and vendor I have magisk running that way if you have any questions let me know and I help you a greeting.
Click to expand...
Click to collapse
this method will work, I tried this with beta 4. But even then you can`t mount system and delete system apps. You will just pass the error while flashing magisk. I hope the dev will find solution for this. Also system apps are not in system/app anyomore, maybe that have some impact with all this

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
darkoj2007 said:
this method will work, I tried this with beta 4. But even then you can`t mount system and delete system apps. You will just pass the error while flashing magisk. I hope the dev will find solution for this. Also system apps are not in system/app anyomore, maybe that have some impact with all this
Click to expand...
Click to collapse
so that the system remains installed you have to leave it in read mode and select the vendor and the system you leave it marked then without unchecking you install the twrp and the magisk and everything is correct the system will be mounted.

I'm on official release 10.0.0 (QP1A.190711.020, Sep 2019) flashed without "-w" over android 9. Pixel 2.
Flashed latest TWRP (3.3.0-0) and 19.3 Magisk, then latest canary. Nothing helps.
Did you manage to find solution? I would appreciate any help.

ismael47 said:
[/IMG]
so that the system remains installed you have to leave it in read mode and select the vendor and the system you leave it marked then without unchecking you install the twrp and the magisk and everything is correct the system will be mounted.
Click to expand...
Click to collapse
Dude that does seem to work at least for the magisk install. It doesnt help fix other issues like adaway and titanium backup from not being able to mount system though!
Appreciate your effort anyway

There's a setting in magisk that'll allow you to install adaway. Systemless hosts...tap it then reboot and adaway should install.
That worked for me.

I was able to get /system to mount by going to Advanced Wipe and selecting 'system' and choosing repair -> Change File System - EXT2 then go back and switch it back to EXT4.
I have not been able to get /vendor mounted and I believe it is because the syntax used has changed.
I read that AOS10 uses a form of EXT4 that preserves it as ready only, possibly by filling the used space of the drive preventing any writing.
This explains some of the new obstacles TWRP must compensate for in order to maintain compatibility w/ AOS10
https://source.android.com/devices/architecture/kernel/mounting-partitions-early
I have had luck installing Magisk by enabling USB Debug and typing in ADB shell:
cat /dev/block/sda19 > /sdcard/boot.img
Open Magisk and chose to install to file and select the boot.img.
Replace boot.img in the zip file that contains Android 10 factory firmware.
Current Marlin factory firmware [ https://dl.google.com/dl/android/aosp/marlin-qp1a.191005.007.a1-factory-c27241e0.zip ]
Inside marlin-qp1a.191005.007.a1-factory-c27241e0.zip is another archive: image-marlin-qp1a.191005.007.a1.zip ; inside this archive is boot.img.
Using 7zip you can open this archive and drag / drop boot.img replacing the stock image with the Magisk patched one.
Run Flash-all.bat, note it *WILL Wipe* your device but include a Magisk patched boot.img.
Once you finish initial setup of phone, download magisk manager and when you open it, it will automatically patch and reboot your phone enabling root. (make sure you have internet connection before opening magisk manager)
After you have root enabled phone you can customize /system to your liking and then cat /dev/block/sda33 > /sdcard/system.img to replace the firmware version.
(Still am not able to load /system as RW using FX, so have yet to be able to modify .props)
You can locate the various links and identify if you are using slot a/b by typing in TWRP terminal : ls -la /dev/block/by-name/
Side note:
The wizard himself has delicate and important matters of being a present father and managing the obstacles of keeping the brood happy-content and also providing nurturing support to the new addition and persistent validation for the wifey. [Congrats])
(apologies for improper formatting de-pretyfied by inotoxication)