Finally I Get Root On S6 Verizon with nougat :laugh: :laugh:
Edit For those didn't work with them use this
https://forum.xda-developers.com/ve...al/rom-offical-nougat-pre-rooted-rom-t3718155
There Is a Proof In Attachments
My Rom DQD1
*Do It AT YOUR OWN RISK!* I am not responsible for ANY damage to your device
Edit :
A Video Proof And How To Do
In Description Of Video I add link to my rom
To Root You Will Need The Following Files :
G920V_ENG_ROOT_B4_ 7.0 , Root Files and Odin In The Attachments
First Extract G920V_ENG_ROOT_B4_ 7.zip
Flash G920V_ENG_ROOT_B4_ 7.0.tar with odin in AP
After Reboot make Sure You enabled usb debugging go to Settings and tap on About Phone. Tab Software Info Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it
Plug Your Device To Pc
Now Extract S6Root_Unroot_SU_2_79.zip
Plug your phone into the computer
Enter The Folder S6Root_Unroot_SU_2_79 And Double Click On root.bat
If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant 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"
}
wait for minute your phone will reboot automatically
Your Phone Will reboot 2 time on 3 will boot
Every Time You will reboot your device it will reboot 2 time on 3 will boot because we have loocked bootloader
Dont Forget To hit Thanks Button
sorry For My Bad English
where is the proofs?
Dude.... and, where is the proofs? Wich nougat version did you use? Some screenshot? I dont know but a root for this phone sounds really amazing and surprising.
NerdTronik said:
Dude.... and, where is the proofs? Wich nougat version did you use? Some screenshot? I dont know but a root for this phone sounds really amazing and surprising.
Click to expand...
Click to collapse
You Are Right I will Post ScreenShot
NerdTronik said:
Dude.... and, where is the proofs? Wich nougat version did you use? Some screenshot? I dont know but a root for this phone sounds really amazing and surprising.
Click to expand...
Click to collapse
I Added Proof In Attachments Check them
Ok, I have a problem with the adb, I tried many times but it still freezing and my cellphone screen too, I searched in the internet many ways to mount the system partition as read and write but all failed. Im thinking that the problem is the nougat version, I have the J1 and Im downloading the D1. Pst, the drivers and the cables are ok, I used another adb codes and they worked.
Seems like it only works on Qd1, so if have updated QI1 or QJ1, got to flash back to Qd1 to get it to work
...
I flashed DQD1 via Odin and after that, I flashed the .tar, but it still freezing my screen, I tried first without flashing the .tar because after flashing the firmware, the custom logo appeared. But again, the adb process failed, itsn freezed like the other but was unable to copy the su.img
---------- Post added at 07:06 PM ---------- Previous post was at 06:13 PM ----------
I did the same process that you made, so, I don't know why this happen, can you please assist this?? The phone doesn't matter, I just want to prove if this really work. I'll be amazed if this really do.
I´m facing the same problem on my device as @NerdTronik , just frezes when try to remount system as rewritable.. No succes as yet and I'm on Qd1 with the same kernel version.. Dont know How you Got to succesfully Remounted the system..
Another one stuck scratching my head with the phone locking when the batch script gets to the first adb shell mount command. The flash to DQD1 (from here, all 4 files) went fine. Flashed the new boot image without issue, reboot reflects custom image. Enabled debugging, connected with ADB, but that mount would be the final thing that would occur. Hoping this is just something we need clarified in the instructions.
Ok for all of your problem tonight i will make a youtube video learn how to root with the proof of it ☺?
Thanks for the root! Tell me, after I get the root of what custom firmware I can put? I understand you only need the development of verizon?
I did a Google for the the boot image file name and came across this link:
http://www.techzai.com/eng-root-file-samsung-android-7-nougat/
NOTE: I accessed this via Google's cache, and with NoScript plugin in Firefox. The firewall I was accessing through blocked the site for a reason... unsure if that could be that it isn't safe, work just didn't want me going there during business, etc. Go at your own risk.
But one thing that was noted in those instructions was to not only enable USB Debugging, but to also enable OEM Unlock in the developer options.
The thread for the S7 (which I think would apply but we just need to use the later released S6 boot image) mentions disabling secure startup. https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
Might have time to play around with this more during the coming weekend, but maybe @faw_wal or another member will get additional info before then.
Don't work in my phone
So has any one else been able to confirm this as a working method?
DonaldAnderson said:
So has any one else been able to confirm this as a working method?
Click to expand...
Click to collapse
@DonaldAnderson
I was made a video about method but from begin when i flash the reactivation lock was on and now it's locked if you want a video with a proof i can post it for you and tomorrow i will post the full video do you want a proof video now ?
faw_wal said:
Finally I Get Root On S6 Verizon with nougat :laugh: :laugh:
There Is a Proof In Attachments
My Rom DQD1
*Do It AT YOUR OWN RISK!* I am not responsible for ANY damage to your device
To Root You Will Need The Following Files :
G920V_ENG_ROOT_B4_ 7.0 , Root Files and Odin In The Attachments
First Extract G920V_ENG_ROOT_B4_ 7.zip
Flash G920V_ENG_ROOT_B4_ 7.0.tar with odin in AP
After Reboot make Sure You enabled usb debugging go to Settings and tap on About Phone. Tab Software Info Find the Build Number and tap on it 7 times to enable Developer Options.
Now enter Developer Options and find USB Debugging. Enable it
Plug Your Device To Pc
Now Extract S6Root_Unroot_SU_2_79.zip
Plug your phone into the computer
Enter The Folder S6Root_Unroot_SU_2_79 And Double Click On root.bat
If this is your first time running ADB, you will see a prompt on your phone asking you to authorize a connection with the computer. Grant it.
wait for minute your phone will reboot automatically
Your Phone Will reboot 2 time on 3 will boot
Every Time You will reboot your device it will reboot 2 time on 3 will boot because we have loocked bootloader
Dont Forget To hit Thanks Button
sorry For My Bad English
Click to expand...
Click to collapse
Don't you think your omitting a step??, we all follow each step you pointed in the instructions and got the same problem, devices just freezes when execute the root.bat
faw_wal said:
@DonaldAnderson
I was made a video about method but from begin when i flash the reactivation lock was on and now it's locked if you want a video with a proof i can post it for you and tomorrow i will post the full video do you want a proof video now ?
Click to expand...
Click to collapse
I think that it will be nice, I'll be waiting for it in a few hours. We just want to solve the errors, exactly the mounting system partition process.
can you tell me how to do that? when i double click root.bat my homegreen freezy?
can you tell me how to do that? when i double click root.bat my homegreen freezy
motorec said:
Thanks for the root! Tell me, after I get the root of what custom firmware I can put? I understand you only need the development of verizon?
Click to expand...
Click to collapse
I was doing a research and found this thread with the same problem as us ,seems like its knox that blocking the system remount.https://forum.xda-developers.com/att-galaxy-s6/general/root-att-samsung-g920a-s6-g925a-s7edge-t3564637
DDwhite said:
I was doing a research and found this thread with the same problem as us ,seems like its knox that blocking the system remount.https://forum.xda-developers.com/at...ot-att-samsung-g920a-s6-g925a-s7edge-t3564637
Click to expand...
Click to collapse
Oh nice, it's just seems impossible until somebody find the method to write in the system partition, in the thread you posted here, there was a man saying that we need to flash or do something before run root.bat, he didn't checked before but, sounds like a development.
http://rootjunkysdl.com/files/?dir=Gates/DeBloater
Related
{
"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"
}
lieckedeeler & schlex2010
aka SCHLEXEDEELER
ONLY USE THIS TOOL IF YOU HAVE AN ICS VERSION (4.0.4)
WE ARE NOT RESPONSIBLE FOR BRICK OR ANY OTHER ERRORS ON YOUR TABLET
WE ARE NOT RESPONSIBLE FOR BRICK OR ANY OTHER ERRORS ON YOUR TABLET
ONLY USE THIS TOOL IF YOU HAVE AN ICS VERSION (4.0.4)
- Root incl. su & busybox binary (install Superuser from Play Store)
- permanent RW on system folder
- adb root shell
- DVB-T USB support (schlexedeeler Kernel 1.1+)
- CWM Recovery with touch
Click to expand...
Click to collapse
DOWNLOAD SCHLEXEDEELER TOOL V2
=============================================================================================================================
If you want flash back stock kernel or/and stock recovery and stock bootanimation.zip
First step: Copy stcok bootanimation.zip to /system/media
Second step: Flash stock kernel & recovery
It is stock recovery and kernel out of ICS 4.0.4
Download stock bootanimation.zip
Click to expand...
Click to collapse
Download Tool to flash stock kernel & stock recovery
Click to expand...
Click to collapse
Password for the 7zip files:
iknowtherisk!
Click to expand...
Click to collapse
Thank you! Going to try this as soon as i get to my a210.
.... Placeholder ....
And you can just press the 3 point?, Only root, the kernel does not need to unlock me ....
Probably not. It dumps a CWR image to /dev (overwriting the factory recovery?), which is boot, so you have to be unlocked.
CWR is used to mount /system (rw) so that adb can push Superuser and some other binaries.
I got stuck, after loading up CWR. My Windows 7 (x64) couldn't recognize my A210 while CWR was running. Downloaded USB drivers through the Android SDK, and the Acer USB drivers, but neither of them did any good i continued with the rooting process (so that it could clean up after itself) but nothing got pushed to /system (which is no surprise, seeing my tablet was unrecognized). So, now i have an unlocked bootloader, no root, and i'm unable to get into recovery... nothing happens, if i hold volume down, while powering on. I have to press the reset button, to restart it properly.
Could it be that there are no drivers for Windows 7 x64?
Edit: ok, i've read through the topic at android-hilfe.de, and got it working (had to manually install the driver). Now i have root! Thank you!
help for dummies
deleted
deleted
does it give a instruction for this tool, it would be great
Greets
Is anyone working on a ROM or MOD for the Iconia A210 ?
Sent from my A210 using xda app-developers app
Hey 4.1.1 To have?
Alexey71 said:
Hey 4.1.1 To have?
Click to expand...
Click to collapse
What exactly is your question?
I don't know if it will work with 4.1.1, because I do not have 4,1.1 on my tablet! You have?
I get everything back to its factory state, or even be the standard kernel?
Alexey71 said:
I get everything back to its factory state, or even be the standard kernel?
Click to expand...
Click to collapse
Sorry for OT:
Please learn english, or use a better translater tool for your questions!
You use this tool at your own risk, so please stop bugging me with private messages AND forum posts!
Hy everybody
I tried to root my A210 yesterday using your program. But I point out some difference between what happen and the "how to".
First, I didn't have 4 option when I start the tool. I just have the bootloader option and a root option.
Following the "how to", I first activated the open mode to boot.Then, I choose the second choice (root) and that's when it didn't follow the "how to" document. My A210 did restart and boot to a*SCHLEXEDEELER edition but it never ask me to restore my data. And when it get restarted, everything was as it were.I also didn't have all the part about installing the driver because my PC still detect the tab as "adb interface".
I aldo never had the section about mount and unmount system.
Then the*SCHLEXEDEELER tool ask me if I wanted to install the custom recovery. As I was pretty scared of what might happened, I answered "no". So the tool ended.
I cheched on my tab but I was still not root so I did all that stuff again but choose "yes" instead of "no" for the custom recovery.The*SCHLEXEDEELER tool printed out many lines but one caught my attention.
It was something like :"data\tmp\cwm[...].img : no such file or dir".there is a file called "cwm[...].img" (the [...] is because I don't recall the exact name) in the folder in wich there is the*SCHLEXEDEELER tool.
But I didn't suceed in making it finding this file.
And when I checked whether I'm root or not, it turns out that I wasn't.
Any ideas or suggestion?
Still, thanks a lot for your job.
Tab acer A210 user said:
Hy everybody
I tried to root my A210 yesterday using your program. But I point out some difference between what happen and the "how to".
First, I didn't have 4 option when I start the tool. I just have the bootloader option and a root option.
Following the "how to", I first activated the open mode to boot.Then, I choose the second choice (root) and that's when it didn't follow the "how to" document. My A210 did restart and boot to a*SCHLEXEDEELER edition but it never ask me to restore my data. And when it get restarted, everything was as it were.I also didn't have all the part about installing the driver because my PC still detect the tab as "adb interface".
I aldo never had the section about mount and unmount system.
Then the*SCHLEXEDEELER tool ask me if I wanted to install the custom recovery. As I was pretty scared of what might happened, I answered "no". So the tool ended.
I cheched on my tab but I was still not root so I did all that stuff again but choose "yes" instead of "no" for the custom recovery.The*SCHLEXEDEELER tool printed out many lines but one caught my attention.
It was something like :"data\tmp\cwm[...].img : no such file or dir".there is a file called "cwm[...].img" (the [...] is because I don't recall the exact name) in the folder in wich there is the*SCHLEXEDEELER tool.
But I didn't suceed in making it finding this file.
Click to expand...
Click to collapse
FIRST OF ALL you don't read the thread correctly:
The "How to" of Heroturtle is NOT for V2.0 Final Edition!! Do not use that "how to" !!
So here is what the tool do if you select root:
Start your device into bootloader (fastboot mode)
Flash boot.img to your device via fastboot
Pushing binary files like su and busybox to your tablet
READY!
It's important that you have install all drivers correctly!
The 4 points are from the Versions before and are not necessary anymore now.
If you have done the root process, you must install SuperUser from the PlayStore! After that you have root!
Use only schlexedeeler Tool V2... You are confusing something and write about things that no longer exist in the new version!!! No restore my data. etc...
Sorry for my bad English
schlexedeeler Kernel 1.1, Not mount USB - NTFS format....
ok, got it.
I will try to install super user tonight and see if it's good.
I'll write a message to keep you inform about that.
thank you for your quick and pertinent reply
Tab acer A210 user said:
ok, got it.
I will try to install super user tonight and see if it's good.
I'll write a message to keep you inform about that.
thank you for your quick and pertinent reply
Click to expand...
Click to collapse
If not, please let me know, then we will find a solution for you, but I think if you do only that, what the tool tell you, you're on the right way :good:
Alexey71 said:
Sorry for my bad English
schlexedeeler Kernel 1.1, Not mount USB - NTFS format....
Click to expand...
Click to collapse
I will talk to lieckedeeler... Maybe he have a solution for that.
Minor Update 2.01:
* correct some missspellings
* correct adb command for flashing CWM recovery
Link To Main Thread
{
"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"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.
Reserved
Reserved.
Looks really good... Thus is exactly the kind if tools which gonna make customs ROMs more popular and our life's easier!
The GUI looks awesome!
Cheers for that!
Well done, this is great work!! I cant use it myself as I use a mac for my music production but I wish this was about when I was using windows. Would have made life much easier. :laugh:
EDIT: Thread re-opened.
Great Tool, should help new users who are uncomfortable with fastboot and adb.
Any instructions for new users?
Like do you need to have your phone in bootloader mode <fastboot usb> plugged into pc?
Or when your phone is on, do these commands automatically reboot to bootloader and run?
If so, should the user have usb debugging enabled in settings menu?
tivofool said:
Great Tool, should help new users who are uncomfortable with fastboot and adb.
Any instructions for new users?
Like do you need to have your phone in bootloader mode <fastboot usb> plugged into pc?
Or when your phone is on, do these commands automatically reboot to bootloader and run?
If so, should the user have usb debugging enabled in settings menu?
Click to expand...
Click to collapse
All the buttons are pretty self-explanatory. Almost all of the buttons automatically reboot to the necessary mode, and tell the user if something is needed of them, such as enabling USB Debugging, choosing a file, etc.
WindyCityRockr said:
All the buttons are pretty self-explanatory. Almost all of the buttons automatically reboot to the necessary mode, and tell the user if something is needed of them, such as enabling USB Debugging, choosing a file, etc.
Click to expand...
Click to collapse
Looks like a great tool for noobs look forward to some feedback I'll gladly pass on to such when I know all functions work! good job man!
Just like the all-in-one tool, but just simpler and looks pretty much more user-friendly. I'll try this tool with my friend's One S. Thanks to the OP. Great job! :thumbup:
Edit: and it'll be much more awesome if it'll have options like, s-on (from s-off), unroot, and relock bootloader.
Good morning.
Here I am, a totally newbie in the world of modding.
I bought the One S last year, and is still completely stock.
I would like to install a rom, but I don't know in which order should I press those buttons in the toolkit.
Thanks in advance
Hello guys, thats pretty much the best tool around ! Big regards to the dev. But I have a problem , i have HTC one s s4 and wanted to unlock bootloader, everything is fine until i have to press the unlock bootloader button , it says that cant find the device .. hmm whats wrong , its connected , it says fastboot USB is on .. so .. any help ?
beerfly said:
Hello guys, thats pretty much the best tool around ! Big regards to the dev. But I have a problem , i have HTC one s s4 and wanted to unlock bootloader, everything is fine until i have to press the unlock bootloader button , it says that cant find the device .. hmm whats wrong , its connected , it says fastboot USB is on .. so .. any help ?
Click to expand...
Click to collapse
just a thought have you put the unlock_token into the toolkit folder where adb & fastboot are?
rustykwak said:
just a thought have you put the unlock_token into the toolkit folder where adb & fastboot are?
Click to expand...
Click to collapse
Yes i did ...i noticed that when i select and press reset to bootloader command, the cmd window appwears, do whats supposed to do, when i need to use another command, I need to close this window, so I can use the tool, if not, the tool cannot be used as it is unactive while the cmd window is open ...hmmm. it says device offline , i updated all adb stuff, everything is alright .. only when i choose to unlock bootloader option it loses connection with my phone , no matter that fastboot usb is shown on bootloader status screen..
Fixed it after managed to find the command line and did it manualy
Sent from my HTC One S using xda premium
beerfly said:
Yes i did ...i noticed that when i select and press reset to bootloader command, the cmd window appwears, do whats supposed to do, when i need to use another command, I need to close this window, so I can use the tool, if not, the tool cannot be used as it is unactive while the cmd window is open ...hmmm. it says device offline , i updated all adb stuff, everything is alright .. only when i choose to unlock bootloader option it loses connection with my phone , no matter that fastboot usb is shown on bootloader status screen..
Fixed it after managed to find the command line and did it manualy
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
ok so when you extract the files in the zip on to your desktop leave the files in place dont remove the application out of folder with the data file folder the tool uses leave the app and data folder in its folder.
---------- Post added at 08:08 PM ---------- Previous post was at 08:04 PM ----------
Dont know if it would work better to put the phone into bootloader mode then fastboot usb mode then run the tool?
I wanna use this to s-off but trying to run tool i get this error.
RichieRich84 said:
I wanna use this to s-off but trying to run tool i get this error.
Click to expand...
Click to collapse
You need to install the latest .NET framework from here.
Thats a nice tool you got there. Definitely should be put in general section once the full guide has been written.
At last, this phone is gonna be rooted... but... when i put the Device Identifier Token in the dev. page of HTC, it's doing something, followed by a blank page and nothing else. Don't even get the email with the unlock code.. what to do?
-=SOLVED=-
If you don't get a response from HTC or a blank page.
goto:
http://forum.xda-developers.com/showthread.php?p=47215003#post47215003
I keep getting "error device not found" i installed the drivers and everything.
fusk said:
I keep getting "error device not found" i installed the drivers and everything.
Click to expand...
Click to collapse
Same here, ADB can't detect the device..
Okay, I am sure a lot of you already know how to do this to your Pixel. Some of us do not, and I was one of them. I am the standard noob that just followed Youtube videos to unlock previous carrier locked phones. I am now enjoying this Google Pixel that is unlocked!
So if you are reading this thread, hopefully there isn't another one just like this (yes I looked).
To start off, if you are in here reading this, you have unlocked your bootloader and installed a custom recovery such as TWRP and rooted. Now you are seeing that you need to update your phone with the latest security patch. You try and you try and you can't do it. Even when you unroot it will still fail to update, or at least it did for me. Here I will explain what I went through and did to obtain the latest update. (Warning, you will loose root and custom recovery). THIS IS INTENDED FOR THE GOOGLE STORE PURCHASED PHONES
Lets get this started finally.....
Go into your developer options and enable usb debugging.
Download the newly released package file from google that has fastboot and ADB without needing android SDK.
DOWNLOAD or read about it HERE
Now you will need to download the Factory Image for you device
Find your correct device HERE
Make sure you choose the correct device and correct update, for me I downloaded the "7.1.1 (NMF26U, Jan 2017)" for my Pixel. Also a USA phone.
So now you have the adb fastboot binary package and your factory image. You will need to extract the platform-tools-latest-windows.zip and open the folder and you will see another folder, open it and now you will see a bunch of files. Now open another window and extract your factory image. Once it is done, open the folder until you see the files. Now copy these into the Platform tools folder in the directory with the fastboot.
Once this is done your folder should look like 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"
}
Now you will want to right click "flash-all" and click edit. It will open notepad and show the contents of the batch file. You can hit Ctrl+F and type in -w in the search and hit okay, or you can look for it without search (it is near the bottom). Once you find it, just delete the "-w" and save the file. Make sure to keep it as the batch file or this won't work.
Once this is done, in the folder that is shown above, click a blank area in the folder so no file is highlighted. Now hold shift and right click, it will come up with a dialog saying open command window here, click that.
Now we are going to reboot the phone into bootloader mode. In the command window, type everything that is underlined below
adb reboot bootloader
Now your phone should have booted into the bootloader screen or it should be asking for USB rights to use adb. If it asks for permission, hit okay and re run the code above and your phone should reboot.
Once you are in the bootloader screen you will need to do is run the flash-all.bat. It will load and go though some text on the CMD window it brings up. It will say some files are missing, which is fine. But if it fails it will tell you that it did. You can also tell by rebooting the phone or click "start" in the bootloader mode and then checking for OTA updates. It should say January 5th patch installed.
Now you can go through and install your custom recovery again and re root. Which takes no time at all and I am sure someone on here has posted before. If not, let me know and I can make a tutorial over it.
Note: I am very sorry for the bad layout and extended write up. First time ever doing this and I am hoping to help people. If there are any errors, let me know!
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
zelendel said:
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
Click to expand...
Click to collapse
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
exbtlegends said:
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
Click to expand...
Click to collapse
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
jrat69 said:
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
Click to expand...
Click to collapse
Not a problem ?
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
32BitWhore said:
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
Click to expand...
Click to collapse
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Good work. This is a very minute stuff of removing -w from the batch file. Very handy work.
Sent from my Pixel using Tapatalk
Do you need to reflash stock kernel before removing root/TWRP before flashing?
32BitWhore said:
Do you need to reflash stock kernel before removing root/TWRP before flashing?
Click to expand...
Click to collapse
Flashing the image overwrites anything you customized besides the regular user data and internal storage (with the -w removed). You don't have to remove or reflash anything else before following these instructions.
TCPDump said:
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Click to expand...
Click to collapse
I couldn't side load the update.. TWRP would not load the side load feature.
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
km8j said:
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
Click to expand...
Click to collapse
Even when I un rooted mine. I was still failing to get the update.
If you made any changes the the system partition then it will fail and simply unrooting doesn't make the all the changes needed. So if OTA mean anything to you then I would suggest not messing with your device as there is Jo promise that after an OTA you will be able to root again tonight away
jesssiii said:
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
Click to expand...
Click to collapse
I know the past 2 were the same for google pixel and Verizon pixel but I wouldn't assume they are always going to be. I'm sure some of them will be specific at times whenever Verizon decides they wanna mess with them
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
SpoiledHeeb said:
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
Click to expand...
Click to collapse
You need SuperSU 2.79 RC3
BRING BACK A DEAD RCA TAB
Time to set the scene. I had a stock rca tab laying around so I found the thread to a discontinued project on here. I flashed the files and could not get it to boot again. Stuck in an awesome two dog logo. Yay. So after searching a couple days for the stock files I ran across someone comparing this tab to the Cube u25gt-c4y. What do I have to lose. I searched and found the stock files and bam! I had a chinese tablet. Surprisingly it works with just a few flaws. After flashing you will see a nvram error in the wifi. Easy fix. Adb seemed finicky at first but straightened itself out. Screen rotation is also 180 degrees out. You have to tilt it down and lock the rotation. Lastly you have to change the language to english because the default is chinese. Will be trying to get the gps and fm radio working soon.
Step 1.
Install Sp Flash Tool if you have not already. There are many posts on this so I wont repost them.
Step 2.
I used the "Format and Download All" option. I have read dont do it on some threads but I have seen others that said to.
If you want TWRP then rename the file to recovery.img and replace the one in the roms file.
Step 3.
Use Kingroot 4.96.apk and then grab the Super sume to replace the kingroot with SuperSu.
Installing SU from twrp when it asks works fine.
That should be it and now you have a working tab again.
As always USE AT YOUR OWN RISK!!! Nothing to risk though if your tab is already a brick.
Thank you to all the posts I searched to get my tab back working.
https://mega.nz/#F!PY1ExBLB!fns00mTE-hvXsz6sdXdVaA
For the Wifi Nvram WARNING: ERR 0x10 https://forum.xda-developers.com/showthread.php?t=2730486
ADB FIX
So after installing this rom you may have a problem with the adb working. Originally I had this problem and I'm not exactly sure how I repaired it. I believe I had installed multiple "MTP Enabler" programs. After reinstalling I had the problem again and this time found the fix.
Code:
1. Open /data/property/persist.sys.usb.config and change to mtp,adb
2. Open /system/build.prop and add/edit these lines.
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
3. Reboot your phone and wait for the drivers to install. Enjoy.
Installed Wrong Preloader?
Luckily for us we can just open Sp Flash Tool with the correct files then push and hold the Power + Vol Up with the usb connected. After approximately 30seconds it should allow flashing.
jeffmoss1999 said:
So after installing this rom you may have a problem with the adb working. Originally I had this problem and I'm not exactly sure how I repaired it. I believe I had installed multiple "MTP Enabler" programs. After reinstalling I had the problem again and this time found the fix.
Code:
1. Open /data/property/persist.sys.usb.config and change to mtp,adb
2. Open /system/build.prop and add/edit these lines.
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
3. Reboot your phone and wait for the drivers to install. Enjoy.
Click to expand...
Click to collapse
Is your device still working?
leetree2001 said:
Is your device still working?
Click to expand...
Click to collapse
Yes. So far I have found it's hard to kill this unit. I don't have the original firmware but have it working with this firmware where it is usable. Like I stated the worst thing is the screen rotation but all u have to do is lock rotation and it's fine.
Thanks for your response. I have two of the rca6773w22B I will give a try later And post later
leetree2001 said:
Thanks for your response. I have two of the rca6773w22B I will give a try later And post later
Click to expand...
Click to collapse
This is not for the w22B just the w22.
Understand your warning. But had these under the coach
For about a year. And nothing else has poped up on the
Old inter web. Soooo,either this or the trash they go.
I have the 22B version also
leetree2001 said:
understand your warning. But had these under the coach
for about a year. And nothing else has poped up on the
old inter web. Soooo,either this or the trash they go.
Click to expand...
Click to collapse
did this work????
Did it work?
leetree2001 said:
Understand your warning. But had these under the coach
For about a year. And nothing else has poped up on the
Old inter web. Soooo,either this or the trash they go.
Click to expand...
Click to collapse
Im having the same issue looking for a rom for my Voyager 2
Did that sulution work for the w22b version?
Yay my tablet is bricked. Thanks SP flash. frickin crashed
My tablet no longer turns on after I tried SPFlashTools, it started DL process and then timed out. If I connect to windows computer, it makes a connect sound but does not do anything, neither responds to SPFlashTools anymore. Any Idea ?
jeffmoss1999 said:
BRING BACK A DEAD RCA TAB
Time to set the scene. I had a stock rca tab laying around so I found the thread to a discontinued project on here. I flashed the files and could not get it to boot again. Stuck in an awesome two dog logo. Yay. So after searching a couple days for the stock files I ran across someone comparing this tab to the Cube u25gt-c4y. What do I have to lose. I searched and found the stock files and bam! I had a chinese tablet. Surprisingly it works with just a few flaws. After flashing you will see a nvram error in the wifi. Easy fix. Adb seemed finicky at first but straightened itself out. Screen rotation is also 180 degrees out. You have to tilt it down and lock the rotation. Lastly you have to change the language to english because the default is chinese. Will be trying to get the gps and fm radio working soon.
Step 1.
Install Sp Flash Tool if you have not already. There are many posts on this so I wont repost them.
Step 2.
I used the "Format and Download All" option. I have read dont do it on some threads but I have seen others that said to.
If you want TWRP then rename the file to recovery.img and replace the one in the roms file.
Step 3.
Use Kingroot 4.96.apk and then grab the Super sume to replace the kingroot with SuperSu.
Installing SU from twrp when it asks works fine.
That should be it and now you have a working tab again.
As always USE AT YOUR OWN RISK!!! Nothing to risk though if your tab is already a brick.
Thank you to all the posts I searched to get my tab back working.
https://mega.nz/#F!PY1ExBLB!fns00mTE-hvXsz6sdXdVaA
For the Wifi Nvram WARNING: ERR 0x10 https://forum.xda-developers.com/showthread.php?t=2730486
Click to expand...
Click to collapse
What version is this Android OS?
Also: I can't have access to wifi.rar fix file. Where is it?
I am also looking around for stock rom RCT6773W22 (no additional letters or numbers)
I've installed all possible drivers for this tablet.
I physically inspected the USB charging port was not bent and (internally at circuit level) everything is connected, nothing is loose.
When the tablet is off, the device is not seen. But the screen of the tablet shows it is charging from the PC normally.
Windows 10, then proceeds to chime "device disconnected" sound.
If I turn on the tablet, I ask for ADB DEVICES and the tablet is not recognized at all. The tablet stays at logo boot loop.
Maybe I need to install something so the hardware of the tablet grants access to adb commands?
{
"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"
}
All i can find are tutorials for the Neo and Pro versions of this device. Can this version be rooted? How?
recovery sideload+magisk
alekksander said:
recovery sideload+magisk
Click to expand...
Click to collapse
Hey, thanks for the reply. I'm still new, can you elaborate? Maybe possibly link a tut? Appreciate it regardless.
alekksander said:
recovery sideload+magisk
Click to expand...
Click to collapse
What is recovery sideload?
useroso987 said:
What is recovery sideload?
Click to expand...
Click to collapse
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt
Kurt Krummbein said:
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt
Click to expand...
Click to collapse
Well, i've been reading past days...
I've installed Delta Magisk through adb on Lineage OS 20. It was quite a fast and interesting process!
Thank you.
Kurt Krummbein said:
Well, don't get me wrong, but if that's all unknown to you ... you'd better don't root your device ;-).
The risk to brick your device or open unforseen security wholes is quite too large, you'd better read some tutorials about flashing roms and customizations before trying to get into the world of Magisk.
Cheers
Kurt
Click to expand...
Click to collapse
Instead of being helpful you give some strange lessons it seems to me that you are useless here. If someone asks you politely for help, explain it to them. Every phone unlocks differently.
Kasjopea73 said:
Instead of being helpful you give some strange lessons it seems to me that you are useless here. If someone asks you politely for help, explain it to them.
Click to expand...
Click to collapse
Well, i tried to figure out, that not knowing the basics of running the phones recovery and using sideload is a bad starting point to open root access on the device.
Kasjopea73 said:
Every phone unlocks differently.
Click to expand...
Click to collapse
Well, that's not the core of my answer and i do not disagree ... just wanted to prevent a newbee from bricking his device and not beeing able to recover ;-) or walking around with a spy-phone recording and sharing his whole live-data with someone who should not know anything of it at all.
@Kasjopea73 : if you volonteer to answer request like "i tryied to root and bricked my device" in personal chat, then it's ok ... i've seen too many chats on other devices beeing flooded by those kind of requests, rendering these chats useless for developers who tried to exchange information on fixing problems.
Ciao
Kurt
Kurt Krummbein said:
Well, i tried to figure out, that not knowing the basics of running the phones recovery and using sideload is a bad starting point to open root access on the device.
Well, that's not the core of my answer and i do not disagree ... just wanted to prevent a newbee from bricking his device and not beeing able to recover ;-) or walking around with a spy-phone recording and sharing his whole live-data with someone who should not know anything of it at all.
@Kasjopea73 : if you volonteer to answer request like "i tryied to root and bricked my device" in personal chat, then it's ok ... i've seen too many chats on other devices beeing flooded by those kind of requests, rendering these chats useless for developers who tried to exchange information on fixing problems.
Ciao
Kurt
Click to expand...
Click to collapse
The best thing to do is not to write anything anymore, you are no help here and it is better to disappear. This is a forum for development, not for throwing obstacles under someone's feet. Rooting this phone is trivial, just extract the boot.img from the rom you are using, not from any other, and in magisk make a patch, instructions you will find below the post. If you don't know what is going on don't write nonsense to anyone.
Instructions Steps: Unlock Bootloader and RootPlatform Tools:
For Windows:
Download File: Download
For macOS
Download File: Download
For Linux
Download File: Download
At first, you need to connect your device to PC via USB cable.
Next, head over to the platform-tools folder, then you have to type in CMD in the address bar and click enter. Command Prompt window will popup.
Now type the below command to boot your device into fast boot mode:
adb reboot bootloader
Next, you will need to get your device-specific unlock token. For that, execute the below command:
fastboot oem get_unlock_data
You will now get an alphanumeric character, that you have to copy all of the codes without the bootloader prefix. To follow this step, you may copy all the commands, paste it in a Notepad, and then delete the bootloader prefix. Further, make sure that there isn’t any space between any line of codes.
Now go to Motorola Unlock page and sign-in with your account. After this, copy that code and paste that into provided space. Then tap on the “Can my device be unlocked button”
Then, you will receive a Unique Key on your email. In normal scenerio, the code usually takes a few minutes to reach your email. But if not wait for few more minutes and you will get the code.
Go back the command prompt window and execute the below command. In the following command replace the UNIQUE_KEY with the key that you have received from Motorola.
fastboot oem unlock UNIQUE_KEY
Your bootloader is unlocked, after the whole process is done which will take few minutes. Now if your device doesn’t reboot to the system then you can use the below command to do it manually.
fastboot reboot
CONGRATULATIONS! YOU HAVE UNLOCKED THE BOOTLOADER OF YOUR DEVICE. NOW LET’S PROCEED TO ROOT THE DEVICE
2. ROOT MOTOROLA EDGE 30, PLUS ecc......Thera are two ways root motorola edge plus: one is flashing SuperSu Zip with TWRP Recover and another one patching the boot.img file. Currerntly, there is no TWRP Recovery for motorola edge plus, so we will be choosing the latter (patching) option.
Instructions Steps:
First download the stock firmware and extract the firmware file. Now search the stock boot file which would be named as boot.img. Copy this file to your Motorola edge plus.
Install Magisk Manager which you have downloaded earlier.
After installation, open magisk manager and tap on Install > Install > Select and Patch file (Here you have to select the boot.img file)
{
"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"
}
Magisk will start the patching process which will take just a few seconds.
After the patching process is done, you should see the magisk_patched.img in your internal storage’s Downloads folder.
Now you have to transfer magisk_patched.img to your platform-tools folder. Open CMD in this folder by searching “CMD” in the address bar and hit Enter.
Connect Motorola edge plus with PC via USB Cable and type the following command:
adb reboot bootloader
Now you have to flash magisk_patched.img and for that type the following command:
fastboot flash boot magisk_patched.img
The process will take only a few seconds. Once its complete, you may reboot your device via the following command:
fastboot reboot
Now you can open magisk manger and very the root as well.
CONGRATULATIONS! YOU HAVE SUCCESSFULLY ROOTED YOUR MOTOROLA EDGE PLUS.
There is another solution for making Root on Telegram groups. Unlock the bootloader and install TWRP then Magisk.
I did this as described, it works fine. I tried a couple of days with root and stock ROM but revert back to the original because of google wallet that didn't work suddenly.
hans3103 said:
I did this as described, it works fine. I tried a couple of days with root and stock ROM but revert back to the original because of google wallet that didn't work suddenly.
Click to expand...
Click to collapse
SafetyNet fix install