Re rooting OTA 4.3 using mskip's Nexus7 Tool Kit - Nexus 7 Q&A, Help & Troubleshooting

IT WORKED FOR ME, BUT IT MIGHT NOT FOR YOU. TRY AT YOUR OWN RISK.
I unlocked and rooted my N7 4.2.2 wifi using this tool kit http://forum.xda-developers.com/showthread.php?t=1809195 .
I then updated to 4.3 OTA and lost root but the bootloader was still unlocked. If yours hasn't been unlocked then this isn't for you.
Download CWM 6.0.3.5 from their website and superSU v 1.51 from the superSU site.
Down load and install the Nexus7 tool kit. (Link above)
Put the CWM .img in a folder which is inside the Nexus7 tool kits main folder in C: , the folder is easy to find as there are a few together which are used to add you own files to the phone and not the kit's built in ones, so look for the add an .img file (or something similar) and there is only one folder for adding .img files.
Put the superSU zip on your phone(if you don't know how to do this, then do not go any further and wait for a one click tool kit solution.)
I donated so I have the newest V5.0.0 but I don't think it needs to be this version as an older one should do it, because you are adding the newest files yourself.
Start the tool kit and go to main option, you need to type in 99 when you get the pick a build version screen. You will then get a big list of options.
Select 1 to add the drivers!
Then after the drivers have been installed, select option 11 and then you should have two options 1 for a non permanent flash and 2 for a permanent flash: select 1, then type the name of the file(the CWM .img which if you put it in the right folder will be shown above where you have to type the name) in and follow the instructions.
Your phone will boot into fast boot, if it wasn't already, after you followed the instructions then navigate to the zip on your phone (install from sd card?) then /0 scroll down and install the superSU zip. Then ''go back' untill it gives you the option to select no or yes connected with recovery mode, I selected yes, because most tool kit instructions seem to recommend it. Go to the superSU program and see if it opens OK and if it does, like mine did, then that's it! Rooted with no problems.
If you have used CWM before then this will be very easy for you(I've used it before). I found how to do this just by reading the instructions in the tool kit and trying it, with my fingers crossed, so READ THE INSTRUCTION IN THAT PART OF THE TOOL KIT (option 11).
This was very easy and very fast (I had been trying lots of other 4.3 toolkits but couldn't get CWM to install 'no erro'?)
I did this this morning and have since uninstalled the tool kit, because I won't use it again for a while, so this is why some of the folder names aren't exact, but you will know which ones I am talking about when you look.
If someone, who is experienced at this, wants to clarify some parts in a comment, then feel free.

Thanks!
I just did this, and wanted to revise the instructions slightly based on my experience.
Download CWM 6.0.3.5 from their website and superSU v 1.51 from the superSU site.
Download and install the Nexus7 tool kit. (Link above)
Put the CWM .img in a folder which is inside the Nexus7 tool kits main folder in C: , the folder is easy to find as there are a few together which are used to add you own files to the phone and not the kit's built in ones, so look for the add an .img file (or something similar) and there is only one folder for adding .img files.
Put the superSU zip on your phone(if you don't know how to do this, then do not go any further and wait for a one click tool kit solution.)
I donated so I have the newest V5.0.0 but I don't think it needs to be this version as an older one should do it, because you are adding the newest files yourself.
Start the tool kit and go to main option, you need to type in 99 when you get the pick a build version screen. You will then get a big list of options.
Select 1 to add the drivers!
Then after the drivers have been installed, select option 11 and enter the file name. If there's only one file listed (the CWM .img which if you put it in the right folder will be shown above where you have to type the name), you can enter *
You should have two options 1 for Boot (non permanent flash) and 2 for a permanent flash: select 1
If your tablet is booted, enter 'no' to reboot to fastboot mode.
Your phone will boot into fast boot, if it wasn't already, after you followed the instructions then navigate to the zip on your phone (install from sd card?) then /0 scroll down and install the superSU zip.
Select ''go back' thren boot into recovery mode. Select yes.
Boot and run the superSU program and see if it opens OK and if it does, like mine did, then that's it! Rooted with no problems.
Reboot recovery then choose yes.
I could no longer boot to recovery, so I re-flashed recovery and was fine.

"...put the superSU zip on your phone (if you don't know how to do this, then do not go any further and wait for a one click tool kit solution.)..."
Hi, nevereven...
You don't need to wait for a one click tool kit solution.
Easiest way to "put the superSU zip on your phone" is to download it directly to the Nexus 7 first, using Chrome (or whatever browser you're using) - from the link below. (Chrome will download it to the /download folder, as will most other browsers).
http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Once CWM is flashed, navigate to the /download folder and install the SuperSU .zip.
Anyway... it's the way I'd do it (if I was a using a toolkit)
Rgrds,
Ged.

Related

[Q] How to install a rom via clockwork recovery?

As I've said before,I'm working on a custom rom.But since the system.img is extracted in a folder called system,I want to install it via clockwork.But everytime I try to install zip from sd card I get an error.Am I doing something wrong?
edit post:
Wrong section, sorry~!
fdespotovski said:
As I've said before,I'm working on a custom rom.But since the system.img is extracted in a folder called system,I want to install it via clockwork.But everytime I try to install zip from sd card I get an error.Am I doing something wrong?
Click to expand...
Click to collapse
What kind of error do you have ??? Can you write it. ;-)
fdespotovski said:
As I've said before,I'm working on a custom rom.But since the system.img is extracted in a folder called system,I want to install it via clockwork.But everytime I try to install zip from sd card I get an error.Am I doing something wrong?
Click to expand...
Click to collapse
Do you have the updater-script (or update-script) in the META-INF>com>google>android folder? Also check it for errors (make sure that all of the commands are written correctly)
Hope it helps,
Jack
JackG256 said:
Do you have the updater-script (or update-script) in the META-INF>com>google>android folder? Also check it for errors (make sure that all of the commands are written correctly)
Hope it helps,
Jack
Click to expand...
Click to collapse
Jack, is there a tutorial anywhere that shows us how to install a rom via CW recovery?
It seems I too have the same issue as fdespotovski being: How to install a rom via clockwork recovery?
GreenDroid and SYNERGY both dont use sytem.img but rather a system folder.
Can install other roms like Joe Stones or CM7 fine or by command line with .img files or others with KDZ updater, yet these ones with CW Recovery seem to be lacking tutorials on where and how to do this installation in simple language.
Any assistance would be appreciated.
zzsomebody said:
Jack, is there a tutorial anywhere that shows us how to install a rom via CW recovery?
It seems I too have the same issue as fdespotovski being: How to install a rom via clockwork recovery?
GreenDroid and SYNERGY both dont use sytem.img but rather a system folder.
Can install other roms like Joe Stones or CM7 fine or by command line with .img files or others with KDZ updater, yet these ones with CW Recovery seem to be lacking tutorials on where and how to do this installation in simple language.
Any assistance would be appreciated.
Click to expand...
Click to collapse
How to you mean, you want to install the .zip ROM. You will need to copy the update .zip file to your SDCard. Then, in Clockwork, select "Install .zip from sdcard" and choose "choose zip from sdcard" and then select the .zip you copied to your sdcard. It should begin installing the ROM. Then 'wipe data/factory reset' Reboot the phone. There, ROM is installed.
Jack
Thanks Jack,
I think the problem is, I dont have clockworkmod installed on my phone as when I use an app called Rom Manager it gives an option called Flash CWM Recovery yet nothing happens when I select that so obviously I need to install that.
Any good tut's on now to install that, whilst using Joe Stones version 2.3.2?
Will search around, so thanks again.
zzsomebody said:
Thanks Jack,
I think the problem is, I dont have clockworkmod installed on my phone as when I use an app called Rom Manager it gives an option called Flash CWM Recovery yet nothing happens when I select that so obviously I need to install that.
Any good tut's on now to install that, whilst using Joe Stones version 2.3.2?
Will search around, so thanks again.
Click to expand...
Click to collapse
Yeah, ROM Manager doesn't work with our phone, yet. But here is how to flash it on your device (without fastboot)
Download Clockwork Mod 2.5.1.8 from here.
Next, install YaffsExpert from the Market. (It's free ) Open it and in the first dropdown box, choose "Restore" and in the next, select "Recovery" press "Browser" next to the Operation File field. Select the recovery.img file. Make sure the "Target Device Model" is set to "All other" then press "Operation" wait for it to finish.Next, install YaffsExpert from the Market. (It's free ) Open it and in the first dropdown box, choose "Restore" and in the next, select "Recovery" press "Browser" next to the Operation File field. Select the recovery.img file. Make sure the "Target Device Model" is set to "All other" then press "Operation" wait for it to finish.
There, Recovery is installed
Hope it helps,
Jack
Thanks yet again there Jack, very kind of you to continually reply.
I have that version of clock work, as I have many of the the 3.x.x series as well so dont need to download that, but does it matter which one we install? I see there is now a clockwork v4 and one with an auto installer as shown by Dudeman at a Swifdroid blog he has posted.
So will it matter which CWR I use? or is it very specific?
I have also just updated to Cyanogen RC0 which is I seem to be able to do fine as well as installing Joe Stones rom too. But not the ones that need to install from zip.
Speaking of downloads, well guess what, this brings me to another problem I have
(and one I have always had) which is for the life of me, I cannot understand why I cannot download from Market.
Meaning, I also have some webspace of my own I can down and install apps or .apk files just fine, yet although when I go to market, and click on install, agree and install, the app then says downloading and takes me to the page prior to the app page.
I then go back to the app page to see whats happening and it continually says "Starting download" but will stay like this forever never changing as it will not ever download. Nor will it for any file on or from Market.
Why the heck is this? Tell ya, this has me cursed it has, and has limited me from doing many things that others are doing on their GT540.
Any more info regarding this would be most appreciated.
JackG256 said:
Yeah, ROM Manager doesn't work with our phone, yet. But here is how to flash it on your device (without fastboot)
Download Clockwork Mod 2.5.1.8 from here.
Next, install YaffsExpert from the Market. (It's free ) Open it and in the first dropdown box, choose "Restore" and in the next, select "Recovery" press "Browser" next to the Operation File field. Select the recovery.img file. Make sure the "Target Device Model" is set to "All other" then press "Operation" wait for it to finish.Next, install YaffsExpert from the Market. (It's free ) Open it and in the first dropdown box, choose "Restore" and in the next, select "Recovery" press "Browser" next to the Operation File field. Select the recovery.img file. Make sure the "Target Device Model" is set to "All other" then press "Operation" wait for it to finish.
There, Recovery is installed
Hope it helps,
Jack
Click to expand...
Click to collapse
I have done this and I cannot boot into recovery mode my phone just starts up in safe mode ?
I also have tried to flash using terminal.
su
flash_image recovery /sdcard/recovery.img
but i just get a message saying no permitions
Ive copied the Flash_image file into system/bin
any ideas im trying to flash a recovery so i can flash 2.3.3 without fast boot or a pc
Im using the Baltic 2.1 rom
Sent from my GT540 using Tapatalk

[ANDROID] ClockworkMod Permanent Installation Fix! - Step by Step Instructions

I have figured out a way to permanently install ClockworkMod Recovey on your hybrid WebOS/CyanogenMod Touchpad. Like many of you, my ClockworkMod installation failed when I tried to install using ACMEInstaller while I also installed CyanogenMod.
I realize there is now a workaround to "inject" ClockworkMod into your TP using novacom however this requires you to utilize a computer everytime you want to boot ClockworkMod. Follow the instructions below to install ClockworkMod onto your TP permanently and free yourself from your PC!
1. Boot into WebOS
2. Mount TP to your computer and create a "cminstall" folder if it no longer exists after your CyanogenMod installation
3. Copy the "update-cwm_tenderloin-1012.zip" file into the "cminstall" directory, then unmount TP from computer
4. Download the "Internalz Pro" program using the "Preware" application in WebOS if you haven't already (Google is your friend if you get stuck here)
5. Open "Internalz Pro" and navigate to the "boot" menu (will most likely require you to tap the top-most icon of a folder with two dots next to it to get to the root of the TP - should be second folder down)
6. Tap on the file "uImage.ClockworkMod" and select "move"
7. Navigate to the "media/internal/" directory and click "select" to move file
8. Now tap on the file "update-uimage" and move the file to the same "internal" directory you did in step #7
9. Exit from "Internalz Pro" and reboot device while holding down the up volume key, which will take you in to WebOS Recovery (or select WebOS Recovery when you get to the moboot screen you may have previously installed) - you should now see a large USB icon and should be connected to your computer using a usb cable
10. Go to your command prompt in Windows and navigate to the menu where you have novacom installed - you should also have the ACMEInstaller binary file copied into this directory by now (If you don't know what I'm talking about, remember Google is your friend)
11. Type in "novacom boot mem:// < ACMEInstaller" in the command line and press enter
12. You should now see ClockworkMod recovery installing on your TP - Once it reboots into moboot select "boot ClockworkMod" and watch it boot into ClockworkMod!
13. After celebrating, boot back into WebOS, go into "Internalz Pro" and move the file "update-uimage" back into the "boot" directory - the "uImage.ClockworkMod" file that you put in the "Internal" directory is no longer needed since you reinstalled ClockworkMod properly
Essentially the boot directory was overloaded which caused for insufficient space when installing ClockworkMod. Now you should be able to boot into WebOS, CyanogenMod, WebOS, AND ClockworkMod Recovery without a computer. As always, I do not take responsibility for you bricking your TP or variability you may have... use this information if it is helpful but don't blame me if something goes wrong. I'm just trying to help out the community that has helped me for so long.
Let me know if this is helpful to you. Thanks!
dseelye
What!?
Hi!
firstly, thank you for making this guide, i know that alot of people like myself will appreciate it.
but i've run into a problem, see, now i don't have the option to boot into cyanogenmod anymore !
can i flash it in clockworkmod, or do i have to do it all over again?
a reply would be appreciated
you most likely copied the wrong file from the boot folder, as there was one for clockworkmod and one for cyanogen mod... look and see if you incorrectly copied the cyanogenmod "uImage.CyanogenMod" to your internal sd card to free up space. You will have to move this back to the boot folder and grab the other one.
Thank you VERY much!
and thanks for the INCREDIBLY quick reply!
EDIT: IT WORKED!!! YOU'RE THE MAN!!!!!
No problem... let me know if that solved your concern...thx
EDIT: Oh, just saw the edit of your post...great, glad that was it!
Just wondering... how permanent is permanent?
For instance, if I use "web doctor" to restore my touchpad, will the recovery be overwritten?
Yes, I just mean that you don't have to "inject" clockworkmod into your TP using your computer which was the workaround for the people who couldn't get it installed originally during the CyanogenMod installation. This just installs it properly but can be wiped with WebOS Doctor like anything else...
bigblueshock said:
Just wondering... how permanent is permanent?
For instance, if I use "web doctor" to restore my touchpad, will the recovery be overwritten?
Click to expand...
Click to collapse
Yeap... it will not delete a single bit of CM7, just gonna restore the original bootloaders, delete moboot and skip CWM /Android on boot...
Running again ACME with only moboot and CWM in the cminstall folder will restore them.
....After WebOS doctor... it will show CM7 as the last time you shut it down.
Sent from my GT-I9000 using XDA App
I followed directions exactly but I am not seeing the uImage.clockwork in the boot folder. Any suggestions? I see that file in the cminstall folder, do I just leave in there or should I copy directly to media\internal?
Sent from my SPH-D710 using xda premium
The "uImage.ClockworkMod" may not be in the boot directory I suppose if the previous install attempts didn't put it there so not sure why it isn't in yours. Essentially you are just trying to move some of the larger files out of that directory so you can install ClockworkMod properly as the space constraint of the partition size seems to be the issue. The other file I mentioned, "update-uimage", is actually the largest one I found and you may be able to do the ClockworkMod install properly by only removing that one temporarily. Let us know if you are able to resolve.
I've installed clockworkmod recovery with no errors on the first try, is it advisable that I need to use this method?
I was installing cwm for the first time. I didn't include it originally with the install of cyanogen mod, I guess that's why it wasn't in the boot folder. I placed both files in the media\internal directory and also inside the cminstall folder and ran the command and it worked fine. When I checked internalz pro to remove the files, the cminstall folder and uimage files were gone already. So it looks like I am good to go. cwm is working, I flashed gapps from it. Thanks for reply.
Now I just need to figure out how to make phone calls.
Sent from my SPH-D710 using xda premium
If you installed ClockworkMod completely the first time and it works, then you definitely don't need to do this as this thread was intended for those that tried to install it at the same time as when they installed CyanogenMod and ClockworkMod Recovery didn't install properly. These instructions are to outline how to get it installed correctly as just trying again using ACMEInstaller wasn't working for anyone due to the small size left in the boot directory.
hey thanks for the fix but after the fix i cant get into the market
Not sure why you can't access the market...no issues here. I would suggest reinstalling the gapps zip file and possible the market fix file that are out there now that you have clockworkmod working properly.
thanks for the help thats what i had to do
Hi, the "move" option isn't available, only "copy" "info" and "open"
The entire directory is "view-only"
Not sure why "move" isn't available for you... its been a while since I installed Preware and Internalz Pro so I must have gotten root access somehow and that's why it shows up for me and others. I'd suggest searching for how to obtain root access to WebOS to find your answer... possibly development mode if you haven't already done that but I thought that was required to get Preware installed in the first place.
Move command
dseelye said:
Not sure why "move" isn't available for you... its been a while since I installed Preware and Internalz Pro so I must have gotten root access somehow and that's why it shows up for me and others. I'd suggest searching for how to obtain root access to WebOS to find your answer... possibly development mode if you haven't already done that but I thought that was required to get Preware installed in the first place.
Click to expand...
Click to collapse
I have the same problem. Move/delete commands are available on the media/internals but on boot folder move is not available.
Thanks
Awesome man! Been struggling with this since two days. Thanks a lot for the fix and step by step instructions
---------- Post added at 09:07 AM ---------- Previous post was at 09:00 AM ----------
tmkhan said:
I have the same problem. Move/delete commands are available on the media/internals but on boot folder move is not available.
Click to expand...
Click to collapse
After Opening "Internalz Pro", Open "Preferences", scroll down to the bottom. You will see an option called "Master mode". Turn it on. You will get read/write access to the boot folder.

[GUIDE] How to root SmartQ ZWatch

You can easily root the SmartQ Z1 (W1) ZWatch by modifying the firmware and updating it to the watch. I don't know of any rooting tool (like framaroot) that does the job on the watch without flashing the firmware.
[CREDIT TO GEEK78]
(1) READ the [HOW TO] in this thread by geek78 who first made a root firmware.
Download his rooted firmware HERE
Extract it with WinZip or similar zip utility - you should see files and folders which include "system"
Go to "system" -> "app". Copy "superuser.apk" to somewhere else in your computer (and remember where it is)
Go to "system" -> "xbin". Copy "su" to somewhere else in your computer (and remember where it is)
==========================================
(2) Go to Smartdevice website and download the latest firmware - HERE
Extract it with WinZip or similar zip utility - you should see the same files and folders of (1)
Copy "superuser.apk" and paste it into the "system/app" folder of this unzipped new firmware
Copy "su" and paste it into the "system/xbin" folder of this unzipped new firmware, replacing the original "su" file
[OPTIONAL]
(a) If you want to remove any apps in the original firmware, you can rename them from "xxx.apk" to "xxx.apk.bak" (eg. I don't use Weather sync app (IndroidWeather.apk), Sleep app (SleepAnalysis.apk) and Health app (SmartQWatchHeath.apk)), before the following step
(b) You can also add your own apps into the system/app folder, so that you don't need to install them after updating to the new firmware
==========================================
(3) Open WinZip or similar zip utility and navigate to the folder that contains the unzipped firmware files and folders. Highlight all the files and folders ("META-INF", "system", "boot.img", "mbr-xboot.bin", "recovery.img"), and use your zip utility to compress them back into a ZIP file called "update.zip"
==========================================
(4) BEFORE FLASHING THIS MODIFIED FIRMWARE, you must follow geek78's steps:
[HOW-TO]
1-Flash the watch with the restore tool from https://hotfile.com/dl/255788947/abfedd9/z1_restore_tool.zip.html (yes, i know, it will format the watch and you will loose everything... but it is needed)
2-Copy the rooted firmware called "update.zip" to the root of the /Sdcard of your watch
3-Start the flash from the watch
4-After the boot you can delete the 2 chinese apps with App Uninstaller
Click to expand...
Click to collapse
*** YOUR MUST USE THE RESTORE TOOL TO CLEAN THE WATCH BEFORE FLASHING THE ROOTED VERSION OF A NEW FIRMWARE ***
Thanks bro I already knew this but just wanted to thank you for your time and effort writing these instructions for everyone
Sent from my SPH-L900 using xda app-developers app
help with restore tool
Hello I have been searching through the forums and got a little help but need more. I am having problems rooting my watch. I dl'd the restore tool, problem is one of the restore tools instructions was to install the driver in a custom path but my comp keeps auto dling the driver and I cant choose the path to install. I run the restore tool and try to boot into restore mode so the tool will recognize it but it wont do anything. What am I doing wrong and do you guys have any solutions for the install path and getting into restore so I can use the tool? Thanks in advance for your time.
techgeek191 said:
Hello I have been searching through the forums and got a little help but need more. I am having problems rooting my watch. I dl'd the restore tool, problem is one of the restore tools instructions was to install the driver in a custom path but my comp keeps auto dling the driver and I cant choose the path to install. I run the restore tool and try to boot into restore mode so the tool will recognize it but it wont do anything. What am I doing wrong and do you guys have any solutions for the install path and getting into restore so I can use the tool? Thanks in advance for your time.
Click to expand...
Click to collapse
Try finding the watch in Device Manager and updating the driver manually. The driver is in this folder on Win7 x64: C:\Program Files (x86)\Smartdevices\Z1 Burn Tool\driver\x64
jatkins09 said:
Try finding the watch in Device Manager and updating the driver manually. The driver is in this folder on Win7 x64: C:\Program Files (x86)\Smartdevices\Z1 Burn Tool\driver\x64
Click to expand...
Click to collapse
Thanks for your help I tried that and it didn't work sadly. I will just have to try another comp. I have tried going to restore mode with the watch off and with it on .Do you happen to know if i did a factory restore from the watch and then used the rooted 2.2 rom from geek78 if that would work or do i absolutely have to use the restore tool to wipe first?
techgeek191 said:
Thanks for your help I tried that and it didn't work sadly. I will just have to try another comp. I have tried going to restore mode with the watch off and with it on .Do you happen to know if i did a factory restore from the watch and then used the rooted 2.2 rom from geek78 if that would work or do i absolutely have to use the restore tool to wipe first?
Click to expand...
Click to collapse
Yes according to geek78, you must use the restore tool everytime you are installing a customized firmware. I guess the reason is that the restore tool wipes everything on the watch, allowing a clean new install.
I had no problem with installing the restore tool. When I uninstall and reinstall the tool, it remembers where the driver was, therefore I could not reproduce your problem. The best way is to try to install it on another computer eg. XP or Win7 32 bit (I heard that the 64 bit gives most problem with drivers).
If this fails, you can try (I have not tested and won't test because it is a hassle to reinstall all the apps!) to wipe the watch in recovery mode (which is really a modified CWM):
(1) You have to trick the watch to reboot into recovery first -
Find ANY file and make a zip from it called "update.zip"
You should test and see if this method works first, therefore download an official firmware from HERE - rename this file "update1.zip" (or anything other that "update.zip").
Connect your watch to your PC and transfer both files to the root of the watch.
On your watch: "About" -> "Firmware upgrade". Upgrade will fail and the watch will reboot in recovery mode.
(2) If you are familiar with CWM, you should know how to wipe user data, cache, dalvik and system. If not:
Use lower button to navigate (you can only go down, but it will circle back to the top) and upper button to execute.
Go to each of these and follow instruction to execute (choose "++++++++++ Go Back ++++++++++" to previous menu for the next item)
"Wipe data/factory reset"
"Wipe cache partition"
"Advanced" -> "Wipe dalvik cache"
"Mounts and storage" -> "format /system"
Then go back to main menu and choose "Apply update from nand" -> "choose zip from nand" -> choose "update1.zip" (or whatever name you gave to the firmware)
OPTION: you can wipe cache and dalvik again after installation (recommended by many modders)
"Reboot system now"
If update of the original firmware is successful, this means you passed the test. Now you can repeat the process using the rooted and modified firmware as "update1.zip".
THERE IS NO GUARANTEE THIS METHOD WILL WORK, but I think it should.
Got it
Ok i finally got it. The 32 bit was the key. Thanks so much for the help. Loving it, gonna root 2.3 and install.
Recovery mode tested and working :good:
Did follow your instructons could not go back after mounts and storage step. With re-boot watch seems to brick. HELP!
Ton.dewaal said:
Did follow your instructons could not go back after mounts and storage step. With re-boot watch seems to brick. HELP!
Click to expand...
Click to collapse
What is happening after you format? Is the "go back" option not available? Or is it there, but the buttons no longer navigate?
Sent from my HTC One using Tapatalk
"go back" option was available brougth me back to Mount & Strorage. Have ttried restore tool on two window machines (7 & 8) tool won't find watch. I'm bricked!
Ton.dewaal said:
"go back" option was available brougth me back to Mount & Strorage. Have ttried restore tool on two window machines (7 & 8) tool won't find watch. I'm bricked!
Click to expand...
Click to collapse
The restore tool has issues with most 64bit machines. If you don't have one, you're best bet is to find a friend or family member that has a running XP system. OR, do you know how to create a dual boot on a pc?
Sent from my HTC One using Tapatalk
Thanks for advise, have now 32 bit XP avaialble. Will test this evening Central Europe Time. Fingers Crossed
Installed on 32 bit XP machine restore tool 1.0.0 windows restart: no luck. Tried to install Usb_Boot_Driver.sys but get Installed failed (unsigned) message. Any advise?
Ton.dewaal said:
Installed on 32 bit XP machine restore tool 1.0.0 windows restart: no luck. Tried to install Usb_Boot_Driver.sys but get Installed failed (unsigned) message. Any advise?
Click to expand...
Click to collapse
That doesn't sound correct...send me a PM...I will give you the login info to my FTP. I have the latest release of the burn tool in exe format on there...you need to download that.
Sent from my HTC One using Tapatalk
I can't root the watch
I tried this method several times but didn't work. after I flashed modified room the watch start OK and I can see superUser icon although the watch still not rooted, because I can't connect using: adb shell su or adb shell root.
I used a v3.5 firmware, please help me someone knows other method to root the z1 watch?
thanks in advance
morbid01 said:
I tried this method several times but didn't work. after I flashed modified room the watch start OK and I can see superUser icon although the watch still not rooted, because I can't connect using: adb shell su or adb shell root.
I used a v3.5 firmware, please help me someone knows other method to root the z1 watch?
thanks in advance
Click to expand...
Click to collapse
Download Maja's DJDroid 6.0 rom (v3.5) , its rooted already
Bad links
Can somebody post those Superuser.apk and su binaries? The download link to geek's rom is bogus and is forcing me to download a bunch of junk.
I have the latest Kitkat firmware (3.7) and stock ROM already has su binary thru adb. My question is can I replace those files thru adb without packaging a zip?
Thanks,
Hi!
Does anyone know how to add the remote camera function in 3.7 ROM? The latest ROM that had it appears to be 3.1. I could not find it as an APK, so I think it is somehow else embedded in the ROM.

trying to bring my brothers A500 to life in 2019

Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Matra-PB said:
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Click to expand...
Click to collapse
That may not be the problem I've hear a lot of people are having this problem. But it's a good place to start if he hasn't tried it yet.
Success story upgrading A500 in 2019 July
finneus_ said:
Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Click to expand...
Click to collapse
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
Step1a: Install a File Manager app from the Google playstore. This will help you extract the CPU ID and convert it with the SBK tool to get the SBK number/string. important steps SBK tool was available in file - SBCalc_v1.1.ZIP available in this forum.
STEP 2b: SUPERUSER and SUPERSU installation
1. Install SuperUser.apk first.. (IMP - Its available in this forum. Its like a base version for superSU to install over. If you do not install SuperUser.apk, then each time you try installing SuperSU, you would get an error message about a SU file being incompatible.)
2. Then install an older version of SuperSU downloaded from the website - filename -> eu.chainfire.supersu_v2.65-265.ZIP . Newer versions will not work. U got to install an older version as new version seems to be a paid SW.
3. Next Open SuperSU app on your tablet and let it update itself a couple of times each time opening and closing the app after the upgrade.
4. Remove SuperUser.apk file as now its no longer needed.
5. Now that you have ROOT access and SuperUSer access
6. Install Titanium Backup. File name in this forum- update-recovery-TWRP-rev2.0-beta4.ZIP . This will help you to flash/upgrade ROM software on your tablet.
Twrp 2.8:
http://www.mediafire.com/file/e7wpny5f39vw3pc/update-recovery-TWRP-rev2.0-beta4.zip/file
Compressed Archive (.ZIP)
File size: 4.91MB
Uploaded: 2018-08-14 21:40:26
https://www.mediafire.com/download/e7wpny5f39vw3pc
STEP 3: Install an Unlocked Bootloader i.e. unlocked bootloader Skrillax v9 - file name in this forum BabSector.rar or A500-Bootloader-Nvflash.ZIP
Once you have reached this step, you now have the basic tools needed for the final ROM upgrade of the tablet.
I did get error message after the reboots that happened after Unlocking the Bootloader. Someting about a LNX partition not being okay or some such msg. Each time I just WIPED the Cache and selected similar options to wipe System, Data, User, Dhelvic cache (spelling incorrect) etc. Since you have not installed the final OS or ROM for your tablet yet, no harm in deleting these partition data. Actually its recommended to wipe, format in f2f formats etc. all of which is possible using the TWRP Recovery software you installed in step 2. Choose Recovery menu option each time the tablet boots or gives errors.... using the volume rocket and power buttons. More info -> Go through this thread and install unlocked bootloader.
https://forum.xda-developers.com/showthread.php?t=1622425
Flashing Bootloader Steps
-------------------------
1. generate your SBK from cpuid
2. put tab in APX by holding reset (small pinhole bottom right side)
and pushing power for 3-4 sec. - then release reset approx 1 sec. later
the screen should be blank and power button should be lit - plug in USB to PC.
2. Run A501 A.bat - when finished reboot tab to recovery (win 7 and under
right click on A501 A.bat and select Run as Administrator)
3. run Recovery(power and volume-) ->WIPE -> "Advanced wipe ->System (only)and swipe to wipe.
4. unplug USB and reboot tab to APX
5. plug in USB afer it is in APX mode -> Run A501 B.bat (win 7 and under
right click on A501 B.bat and select Run as Administrator)
Bootloader unlock tutorial
--------------------------
Step 1: Get your cpuid - https://forum.xda-developers.com/showthread.php?t=1624645
Step 2: Convert it into an SBK - https://forum.xda-developers.com/showthread.php?t=1810618
Step 3: Download the A500 drivers
- http://www.mediafire.com/file/pde8rojv1t8gnif/USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501.zip/file
Step 4: Download the files to install the bootloader
- http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
Step 5: Follow the instructions in "how to.txt"
Step 6: Download a rom and flash in twrp
This tutorial is based of
https://forum.xda-developers.com/showthread.php?t=2450119 thread so big thanks to KaijiKun .
Bootloader unlock files:
http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
STEP 4. Downloaded file omni-4.4.4-20150210-a500-IconiaHD.ZIP as I was not sure version omni 5.1.1 was as stable as Omni4.4.4 reading all the threads in this forum.
First rename the downloaded OMNIROM file as update.zip .
OmniRom 4.4.4
http://www.mediafire.com/file/ghd72j3g618kk9g/OMNIROM-5.1.1-Tegraowners_ROM_v13t2.zip/file
File size: 244.66MB
Uploaded: 2015-04-05 17:40:14
STEP 5: Install another tool adb_fast.ZIP. This tool is also available in this forum.
Note:You need to copy the update.zip file to your computers folder where this tool adb_fast is installed. In mine it was C:\Program files (x86)\Minimal ADB and Fastboot folder. This adb_fast file creates an application shortcut on your computer desktop. Clicking on the short cut launches adb and fast boot programs I mentioned at the beginning.
STEP 6: Copy the file to the SD card (16GB) of your tablet.
Run the adb_fast tool from your desktop shortcut. This will open a Command Prompt type black screen window where you can enter the code as given below. Note you may need to see how your SD card is listed in a file manager in your computer
Code:
adb push update.zip /mnt/sdcard/update.zip --- NOTE: this creates mnt folder on internal storage and I had to then move the file using TWRP recovery tool installed in step 2, to the SD card.
adb push < ------- is the push command.
rom.zip < ------- is the name of the Rom zip file.
/sdcard < ------- is the location your pushing the Rom to.
E.) Reboot tablet with Power+Down Arrow i.e. This will start the Upgrade process for the tablet to OMNIROM 4.4.4
-- Power Button + UP VOLUME pressed... then release Power button after LED lights.
-- System will boot to commmand prompt
STEP 7: Install GAPPS using pico gapps short version and Wipe Data/Factory reset ----------------?>and wipe cache partition?
Reboot after 1st reboot
G.) https://opengapps.org/ to install a minimal version of Google Apps on the tablet.
File name -> pa_gapps-modular-mini-4.4.4-20150410-signed.ZIP
Root tablet again and install SuperSU if you need it
other info.
You can use TWRP to flash the OmniROM on the tablet or you can use the following in worst case senario to do the same.
Code:
fastboot devices
fastboot flash update.zip -- check if syntax is ok from threads in this forum
fastboot reboot-bootloader
copied below from other threads ---->
I find that a large amount of complaints in developer threads are due to people not properly wiping before a flash.
Of course there is times when a 'dirty' flash is fine, but if you're ever not sure, wipe as cleanly as possible.
fastboot allows for about the cleanest of wipes by the way. And each partition can be done separately too.
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
can all be done individually, but to do these all in one command
Code:
fastboot erase system -w
If possible I recommend to do these steps before flashing a ROM, and now that you know you can do this all within fastboot mode i suggest to try it out, its quick and painless!
Don't forget to wipe your kernel too! (fastboot erase boot)
~Important~ If your device uses an emulated SD card (as in no removable micro SD but an SD partition on phone)
Then be careful wiping data/userdata as this will erase all contents of internal SD - you are forewarned!
ADB= Android Debugging Bridge (ADB)
[TOOL]Minimal ADB and Fastboot [2-9-18]
https://forum.xda-developers.com/showthread.php?t=2317790&page=12
First a short explanation:
Fastboot, like ADB, is a tool to communicate from PC to Android phone. There are times when it is a must to use, and times when it is just helpful.
ADB is used within your recovery or within your OS, but when you are in bootloader mode and need to communicate with your phone then you need fastboot.
And you may ask why would i ever need this?
Well many reasons. Main one is knowledge, learning the ins and outs of fastboot, like learning ADB, can get you out of many jams.
And if you want to unlock your bootloader this is done through fastboot. Granted HTC's unlock is... well crap, but for a Nexus this is how its done.
One other reason I have to stress is learning for safety reasons, This is about the safest way possible to flash firmware to your phone (ie Radio, Hboot, Recovery)
Lastly you may want to know the limitations,
There are many of course, this isnt JTAG, it will not resurrect a hard brick, but it often save peoples phones from 'soft bricks' and lots of time when know how and when to use it.
Think of fastboot as the program that takes over when ADB cant be used, it works with firmware more than software.
https://forum.xda-developers.com/showthread.php?t=1624645&page=3
GUIDES
---------------
Civs Guide to flashing the bootloader http://forum.xda-developers.com/showthread.php?t=1622425
Walkthrough using APXFLASH tool at Step 6 http://forum.xda-developers.com/showthread.php?t=1624645&page=2
From Civato's OP of The Guide: nvFlashToolPackages
Skrilax_CZ bootloader thread http://forum.xda-developers.com/showthread.php?t=1619913 and should be "required reading" for anyone mucking about in their tabs internals!!!!
Rollback to HC
jazzyjames guide http://forum.xda-developers.com/showthread.php?t=1516012
Iconia Root http://forum.xda-developers.com/showthread.php?t=1138228 /gingerbreak: For returning to Honeycomb
----------------
To get my CPUID, I have followed the steps below:
Open yr file explorer, esfile explorer is a great one....navigate to:
/sys/firmware/fuse/acer_cpuid - add a zero to the front!
To get CPUID get a Root browser of some sort and go to sys/firmware/fuse/acer_cpu_id
convert my CPUID into SBK?
--------------------------
https://forum.xda-developers.com/showthread.php?t=1055354&page=6
What Does Root Give Me?
1. Full control over your system
2. Ability to alter system files. You can replace many parts of the "Android Core" with this including:
o Themes
o Core apps (maps, calendar, clock etc)
o Recovery image
o Bootloader
o Toolbox (linux binary that lets you execute simple linux commands like "ls") can be replaced with Busybox (slightly better option)
o Boot images
o Add linux binaries
3. Run special apps that need more control over the system
o SuperUser (lets you approve or deny the use of root access to any program)
o Task Manager For Root (Lets you kill apps that you otherwise could not kill)
Tether apps (like the one found at [android-wifi-tether.googlecode.com])
4. Backup your system
o You can make a folder on your SDCARD and backup all of your .APK files to your SDCARD (helps if an author decides to "upgrade" you to a version that requires you to pay to use the version you just had)
5. Relocate your (browser/maps/market) cache to your /sdcard
6. Relocate your installed applications to your /sdcard
7. Reboot your phone from the terminal app easily (su <enter> reboot <enter>)
Turn the rotation lock off.
-------------------------------------------------------
SUMMARY - Regardless of version, rooting is the same... next
** Unlock the bootloader.
** Fastboot flash a Custom Recovery (TWRP).
** Download to the Tablet, Chainfire's SuperSU root updater .zip
** Boot into the previously fastboot flashed Custom Recovery, and flash the SuperSU updater .zip.
** Reboot - you're rooted.
-------------------------------------------------------
PS. I tried to maintain a log in Notepad during my upgrade. Unfortunately did not write detailed instructions and link to required files. Above is a summary of what worked for me.
Can not root
sukasis said:
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
......
Click to expand...
Click to collapse
Hi sukasis, i was unable to root the tablet. I download all and run the runit.win.bat (trying normal, as admin, and open a cmd as admin and then navigate to the bat to execute).
- It say device connected
- Then push 7 files correctly
- Executing of the main script. (it freeze here a lot of time)
Then error: protocol fault (no status)
The file "su" isn't created
Not getting root!
I try in USB 3.0 and 2.0 same error.
I have windows 10.
I uncheck the Debugging mode and it's bring another error, so i believe the connection is good because in debug mode can push files.
I don't know whate else i can do.

[GUIDE] Root and/or install a GSI on razer phone 2 and pass safety net (For Windows)

YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
ISSUE: FASTBOOT Might not work on windows 10 version 2004, a solution is to use a Linux virtual machine to use fastboot commands. Test it out first as you might be lucky and it could work for you.
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port, as USB 3.0 might give you issues with the fastboot commands)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day
Usyless said:
YOUR WARRANTY IS NOW VOID! I am not responsible for anything that could happen, dead sd card, bricked phones, you name it. You chose to install this software and you face the risk of any bugs that may affect you. This is just a warning incase anything goes wrong
A complete guide on how to either just root the razer phone 2 and/or install a gsi with everything working.
The sections are: Basics - Installing TWRP - Rooting - Installing a GSI + Root - Passing safety net to use baking apps, certain games etc.
Basics: (You will have to factory reset if you have not unlocked your bootloader before)
Download this and this file, un zip them both and move them to a known directory such as C:\ADB
Then on your phone, go into developer options and enable OEM/Bootloader unlocking, and after that reboot into the bootloader by holding POWER + VOL DOWN and plug the phone into your pc (I recommend you connect it to a USB 2.0 port)
Then we need to install bootloader drivers onto our phone, so open device manager, click the drop down menu next to Android Device, right click on Android and select Update Driver, then select Browse my computer for driver software, Let me pick from a list of available drivers on my computer, Show all devices, Have disk and navigate to your folder where you extracted the .zips (in my case C:\ADB) and open the usb_driver folder and select android_winusb.inf. In the next menu select Android Bootloader Interface, proceed through the warning and install it.
To unlock the bootloader open a cmd window in the directory of your platform-tools folder, which in my case would be C:\ADB\platform-tools (type cd C:\ADB\platform-tools in cmd) and run two commands: fastboot flashing unlock (after each one select yes on your phone and let it reboot - it might take a while) and fastboot flashing unlock_critical
To install the arter97 kernel/TWRP: (keep your phone in the Bootloader and plugged into the pc)
Download both the .zip and .img file from this link (i am using r12 intentionally as it causes less issues) and download this zip file as well
Move both .zip files onto your phones SD CARD (important) and rename the .img file on your PC to Boot.img and place it into your platform-tools folder (C:\ADB\platform-tools in my case)
Open a command prompt window and like before change the directory to the platform-tools folder, then run two commands: fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Now using the volume keys select the Recovery Mode option in the bootloader and press the power key to select it, if it asks for a decryption password cancel it, and if it asks to allow system modifications swipe to allow it
Go to the Install section and navigate to external_sd and navigate to the arter-r12.zip you installed, then click it and swipe to flash, after that flash the f2fs zip and after it's complete back out to the main menu, click reboot and select recovery
Once you are back in recovery, go to Wipe and select Format Data (this will not erase your sd card if it is set as external storage) and type yes
If you don't want to root then to reboot to system go into Reboot and select System, TWRP will ask you if you want to install their special app, DO NOT INSTALL IT, CLICK ON DO NOT INSTALL.
Now you are ready to proceed to the next step(s) (these are short now don't worry)
To just root and stay on the stock ROM:
Download magisk 20.1 (works better) from here and move it onto your phone sd card by going to the main TWRP menu, selecting Mount then SD card and you should be able to transfer the file onto the sd card directly from your PC
Then simply flash the magisk 20.1 zip in TWRP as we did before and you can now reboot system (make sure to not install the TWRP app)
Magisk Manager will prompt you to update magisk, DONT do it. You can however install the latest magisk manager update
To install a GSI and Root: (lineageOS is what i have linked here, however this is not the only one you can use, make sure you NEED gapps before flashing it incase they are included anywhere)
Firstly, to have bluetooth working go to Mount and select Vendor, go back, select Advanced then File Manager then navigate to /vendor/overlay/ and delete both BluetoothResCommon.apk and RazerAuraBluetoothRes.apk
Then download the latest arm-64-bvN .img file from here, unzip it on your computer and move the .img file to your phone. If you also want gapps (google apps) download this file and move it onto your SD card as well
Now, head to the TWRP Install section, at the bottom select Install Image, select the downloaded lineageOS (or your own gsi) .img file, in the next screen select System Image and swipe to flash it.
Once it has flashed back out to the main screen and click on Wipe, then select Advanced Wipe, then select System, Repair or change file system, and finally press Resize and swipe to do it, if it fails then re do this step
Then go back into the Install section and flash the opengapps zip file and after that the magisk zip file
Now you can reboot to system (might take a couple minutes) and set up the phone.
If you notice it is running slowly go into settings > Phh treble settings (might have to force close app once for it to appear) > Misc Settings > Force FPS > and select the 120.00001 at the bottom (top numbers are 1080p and bottom numbers are 1440p)
Finally, to pass safetynet:
Head into magisk manager, go to its settings and enable Hide Magisk, then call it Manager and allow it to reinstall itself, after that enable Magisk Hide in the settings aswell (hide your banking apps with this or any game that wont boot due to ROOT)
Then go into the magisk downloads section and search for the ArCore module, install this, reboot and your safetynet will pass on a gsi
This is my first xda post so my formatting may be bad but i hope it can help some people if you have any questions drop a comment and please like the post if it helped you for more people to see it.
Have a good day
Click to expand...
Click to collapse
Thank you excellent post just what I needed.
eedwin101 said:
Thank you excellent post just what I needed.
Click to expand...
Click to collapse
I'm glad it helped you
Usyless said:
I'm glad it helped you
Click to expand...
Click to collapse
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.
eedwin101 said:
If you don't mind what other GSI ROMs have you tried that worked well with this phone I am particularly interested in the Google pixel Android 11. Thanks again you have extended the life of this phone for me.
Click to expand...
Click to collapse
I know that phhussons AOSP works on this phone with no issues aswell, you might have to use securize to get safety net to pass tho.
android 11 will boot on this phone however iirc you won't be able to hear and other people won't hear you in phone calls.
havoc gsis I believe works but I haven't tested it and I have only heard of one person using it.
BLISS/LOSQ/CAOS don't work on this phone at all.
and after that I don't think there really is many more GSIs that work as they just won't boot for bizarre reasons
How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.
_Sherrif said:
How about text messaging. Currently i have not been able to get SMS to work with any GSI on Android 10. Are you able to send and receive text messages? Did you have to do anything to get it working? If so, let me know because i have been having a heck of a time with it.
Click to expand...
Click to collapse
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.
Usyless said:
oh this issue... are you on T-Mobile by any chance as if you are there is no fix yet and you will have to wait for official lineageOS.
I am on three (UK) and everything works perfectly.
Click to expand...
Click to collapse
No AT&T.
_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)
_Sherrif said:
No AT&T.
Click to expand...
Click to collapse
or you could try this: https://t.me/razer_phone/12949
install instructions shown in the message
Usyless said:
you might be able to use this fix (it's a magisk module) as it is made for AT&T https://t.me/razer_phone/14202
its called a volte fix but it should help with sms, if it doesn't work you can just remove the module, reboot then delete some qualcomm.ims app (should be shown in your app list)
Click to expand...
Click to collapse
Aight! Definitely worth a try. Tried everything else.
Thank you!
Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.
frannet said:
Thanks!! Excellente guide, very important your note : "I recommend you connect it to a USB 2.0 port", with usb 3 doesn't work bootloader commands.
Click to expand...
Click to collapse
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.
Usyless said:
Thanks
It doesn't necessarily not work with usb 3.0, for some people (and for me) it works with a usb 3.0 port however for a lot of people they have issues with it.
I will add it tho.
Click to expand...
Click to collapse
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.
frannet said:
It's strange. With my razer blade it has not worked (usb 3) but with a Dell Precision with a one port usb 2, work fine. I was going crazy.
Click to expand...
Click to collapse
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.
Usyless said:
Yeah I remember I helped somebody else root their phone and it didn't work with their razer blade either, they had to use some very old laptop.
Click to expand...
Click to collapse
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it
frannet said:
Guys, sorry for the off-topic, is available the dark mode for razer menu? i can't find it
Click to expand...
Click to collapse
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)
Usyless said:
What do you mean razer menu? if you mean settings then it's a MAYBE.
on a gsi, dark mode is available
on stock android 9 it is possible. you need to use smali patcher to enable signature spoofing and then use swift theme installer alpha (substratum themes won't theme the settings)(you need to contact the developer to get the alpha version as others wont work)
Click to expand...
Click to collapse
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ??
frannet said:
Yeah I talk about the settings menu. I thought dark mode was available for all android versions ?
Click to expand...
Click to collapse
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha
i
Usyless said:
yeah tbh idek, all the android fanboys were saying at how long it took apple to make a dark mode but it was implemented in android 10 later than ios 12 I swear ?
but as you are rooted you should be able to get a dark mode, just do as I said with smali patcher and the swift installer alpha
Click to expand...
Click to collapse
Hahaha, yeah, If I'm honest, dark mode in iOS work fine, very fine, normally I use my iPhone 11 and I play with android devices for.. for play with the OS and develoment OS, and as second andriods phone for maybe.... I go to check the gsi mode, thanks guy!!

Categories

Resources