Related
flashed CM7 RC2 I think month or so ago. Phone's been running fine slow but fine. Today Im texting the gf and look down and see blank wall paper. Reboot teh phone htc screen comes up vibrates then starts over. Cant do **** with this think besides stick down the front of my pants! Ive powered and booted to hboot, fastboot etc., cant get it to go into recovery any help would be greatly appreciated before I have a stroke!
FAIL. This should be in Q+A. Can you start ADB and access the device? Are you s-off? How did you root the phone? What have you tried? What recovery do you have? Can you read? Is the battery full? Did you search?
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an a...?
Questions don't belong in the Development section <---please click link and read....moved to general...
TMcGuire17 said:
well since I rooted the phone about 2 [email protected]##ing years ago memory does not serve. S-off dont know does it do that when you flash the rom or install clockworkmod recovery or the several other steps that you follow when you flash the new ROM? If you have to flash it with the image then no that wasn't an option when I loaded this ROM.
ADB automatically starts when the system boots so I don't have to start it, yes its running no I cannot see the device. Battery was about 75% when the screen went blank.
Im going to ignore the can you read and should be in the Q&A comment el duce as this is the place where the experts play and the other 10000 questions about boot looping reside. Does anyone wanna help or just be an ass?
Click to expand...
Click to collapse
I might be an a.., but I am helping, that's why I asked a bunch of questions. You are not s-off, you would know if you were. ADB is a program you use on your computer, not the phone. I asked because you can flash a recovery image using ADB even though the phone won't boot - so my new question here would be do you have ADB on your computer? You should have ADB if you rooted a long time ago, before there were 1-click root methods. I would recommend charging your phone, since many reboots would kill it. Wait til the charging light turns green. Once it's green boot into the bootloader, then access your phone via ADB and see if recognizes the device. If it does we can work from there. As to your BS about posting in dev because it felt better, that's lame as hell, I would have helped in q+a as well, but I would've been less of an ass because you were posting in the correct section. Anyway, charge it up, and reply if you know how to use ADB or not, then we can move on.
EDIT: I just reread your posts, did you say you can boot into your ROM, just not recovery? If so you can also flash a recovery image using terminal emulator. Let me know.
@TMcGuire17
Let’s take the aggression down about 5 notches and remember that when asking for help it is important to post in the correct section. The fact that you want your question answered quickly does not change the fact that this thread has no place in development. XDA is not tech support and while members can be very helpful you should not expect answers from anyone. When you have to search for the answer or figure out a solution…you are able to learn…understand…and then help others…and that is what XDA is about. Calling people names is never acceptable...I have edited your post. I am tempted to close this thread but I will leave it open in the hopes that you find your answer…but any more name calling or bickering and this thread is closed.
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
krook6023 said:
@il Duce
Thanks for helping...but next time leave out the "FAIL. This should be in Q+A" and just report the post...it is only going agitate the situation.
Thanks!
krook6023 (mod team)
Click to expand...
Click to collapse
LOL ok my bad. I get angry. It's the Irish in me.
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
TMcGuire17 said:
Well there you have it! Im as Irish as they come any good conversation between Irish is gonna start with either a beer or a fight. Now that intro's are over....I do have adb loaded need to update it. I'll be back later to check it out and see if I can access the device.
Peace
Click to expand...
Click to collapse
Scotch-Irish actually, red beard to prove it, lol. You shouldn't need to update your adb If you have adb, and on windows, and it's old, try this: open command prompt from your start menu. type "cd C:\android-sdk-windows\tools" (or just copy paste that with no quotes) then type "adb devices" and if it says "random numers phone" like "2222555555 HTC recovery" or whatever, you're good. Report back.
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
So now does it show your device?
sent from a series of tubes.
No it still wont execute the command
If it does, type "adb shell" enter "su" enter "flash_image recovery /sdcard/nameof yourrecovery.img"
Thanks il Duce. If I get adb running Ill try it and post back.
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
Hey TMcGuire, If you updated to the latest SDK, the new path for ADB is no longer \Tools (unless you moved a bunch of files) Try c:\androidsdk\platform-tools
TMcGuire17 said:
I updated the sdk because everytime I run that adb devices command I get a command not recognized as an internal or external command. Wanted to make sure there wasn't an issue with it being out of date. My directory is c:\androidsdk\tools\adb devices
The adb services is running
Click to expand...
Click to collapse
This is not the correct path. Try typing "cd C:\androidsdk\tools" enter, then try "adb devices" OH YEAH and do you know if you had usb debugging on in the phone settings? You may have to run the RUU if you didnt. That can be done from fastboot, but try the other command first, then the flash command.
Edit, platform tools like posted above mine, sorry I dont have the new sdk.
sent from a series of tubes.
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
so here is where Im at. fastboot lists my device. I've try to flash the rom from fastboot but no go. Tried to copy the ROM renamed update.zip to the sdcard via fastboot then I was gonna run update but it returned: sending '/sdcard' (72819 KB) FAILED (sounds familiar )(remote not allow)
TMcGuire17 said:
Thanks guys. Yes I have the new sdk and I did find the correct directory for the adb. I can run it now but still no device. Im not sure if I had debugging on or not I thought it did but.......ran adb shell device not found. How about a quick tut on fastboot!
Click to expand...
Click to collapse
look here:http://forum.xda-developers.com/showthread.php?t=958968
read the info, I think jasonmaloney put the zip you need near the end of the thread.
Read, tried failed. It wont push anything to the device. Always comes back as failed remote: not allow
First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Second, I take no credit for anything here except for writing the .bat file here used to do the work, as well as assembling the files as per the original post.
All credit goes to djmwj and his article found here:
http://rootzwiki.com/topic/8722-lenovo-ideapad-k1-rooting-guide-messy/
As the title states, it was very messy. The OP figured out how to make it go, but it was a bit fuzzy to follow. So, I thought I'd help folks out a bit and clean things up.
So, I took the instructions presented in the OP, and condensed them into one download with one .bat that does everything from start to finish, minus installing the respective drivers for ADB and NVFlash. However, the drivers are included in the download.
Instructions:
1. Extract K1Root.rar to the directory of your choosing.
2. Connect your tablet to your PC with the USB cable.
3. With your tablet off, press POWER+VOL_UP+VOL_DOWN until the screen turns on, but displays only black.
4. Windows should detect the device, but not install drivers.
5. Go into device manager, select the APX device, choose update drivers, and install the drivers from the aptly named NVFlash_Drivers folder.
6. Open up the NVFLASH_HOME folder and run the file K1Flash.bat
7. Make your desired choices when prompted, and enjoy.
Notes (PLEASE READ BEFORE USING):
THERE MAY BE BUGS! I used it on my own stuff before releasing, and all of the essential components work as they should, however, there may possibly be a minor hiccup somewhere in the script. This should not damage anything. If you have doubts, you're welcome to examine the .bat and check it for yourself.
Please be gentle. I am not a full-time developer. I just wrote this to help make the process simpler for people.
The OP suggests you download and read the partition table, and then name the backup files based on that. This script names the backup files based on the flash.cfg script referenced in the OP, which is what controls the flashes used anyway. So, there shouldn't be any irregularities, however, I can't speak for every device on the planet.
This does NOT use the latest OTA updates. The rooted files being flashed are the default ones from the original download. You can easily adapt this to any files generated from the latest OTA files by simply dropping them in the NVFLASH_HOME file.
To install the SU properly, you have to install ADB drivers midway through the script. There's probably a way around this, but I didn't find it to be too inconvenient.
The ADB drivers are also located in the NVFLASH_HOME folder. Just do like you did when installing drivers in step #5, but instead point to NVFLASH_HOME.
Um...um...
That should be it. Obviously, use at your own risk. Let me know if there are problems with the script, and I will fix them.
Oh, and party on, Wayne.
http://www.megaupload.com/?d=AG10XE25
EDIT:
Attached is an updated .bat file which fixes a few errors in the original script, plus adds more userability. Just extract to the NVFLASH_HOME folder and run.
digitalhigh said:
First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Click to expand...
Click to collapse
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.
gallahad2000 said:
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.
Click to expand...
Click to collapse
Wow. Yeah, I'm pretty sure the key used is just for the Ideapad. Thanks for pointing that out. My dumb a$$ must've blanked out and just used the group name when posting.
And just to be fair, the original poster does include everything needed to do stuff in windows as well - it's just very hard to discern from the post.
question
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.
jfkerekes said:
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.
Click to expand...
Click to collapse
We need to be able to root and unlock the bootloader first.
Does the root method work on the 121211 update?
Or is there a way to flash back to the older firmware?
the OTA update 12 12 11.... seems to be update.zip style with no .img files inside. just loose files like normal rom updates. doesnt seeem like you can drop the files in as suggested. or i have the wrong OTA....
oh and is this for LINUX as the OP or work in windows too??
Hi, I was wondering, is this procedure works for the Lenovo ThinkPad 1838-25U? I'm thinking to buy it to give a test ride, i sold my Transformer 101 to buy the Prime but it seems like Asus is taking vacations on the delivery shipments. Is this a good tablet? or is better to wait for another version?
READ THE POST
IDEApad not THINKpad. no it wont work.
First of all- thank you so much for creating this script! I have been putting off rooting this device due to the "messy" nature of the original post.
I was hoping you could help me troubleshoot, I have tried both the new K1 root application and the original .bat file. I know the drivers are working because the script makes it as far as creating and formatting partitions and successfully pushes the bootlooder.bin but then:
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
I've tried everything I can think of... any ideas?
Thanks again.
I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?
taiz said:
I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?
Click to expand...
Click to collapse
Yes you have to roll-back to 04 stock and then apply the OTA's
Backup of the stock lenovo .apks!
File 1:http://www.mediafire.com/?r7iskr3wrfx4u01
File 2:http://www.mediafire.com/?fymdv9e9kmj332s
File 3:http://www.mediafire.com/?w33k205ej4fpbcl
A big thanks to Khanning who was nice enough to walk me through the adb commands and bear with me when I couldn't get adb over usb to work.
This may fix your issues http://forum.xda-developers.com/showpost.php?p=21309379&postcount=50
Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App
maek_it_happen said:
Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App
Click to expand...
Click to collapse
It means you are not in APX mode. Read the PDF and follow the instructions for installing the APX drivers. This should fix your issues.http://forum.xda-developers.com/show...9&postcount=50
I just completed step 3 flashing the image went fine up to bootloader .bin sent successfully ...then it says
File not found recovery.img
Failed executing command 2147473647 Nverror 0x4
Command failure : create failed
Edit the link u posted is not working and the drivers are installed
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Sent from my HTC EVO 3D X515a using XDA App
maek_it_happen said:
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Click to expand...
Click to collapse
Glad to hear it worked for you.
TD
I recently got this device and looking for a way to root this device without having to roll back to the factory default rom and then having to update again using OTA.
Question, am I in luck, is that at all possible or do I have to really rollback and reinstall everything again?
Thanks!
Sent from my K1 using Tapatalk
Anyone have the root? Megaupload is down forever.
BLUF (Bottom Line Up Front) Both the CF and SuperRoot auto-root's would give me "No such file or directory" errors in reference to fastboot when I knew damn well fastboot was present and working!
I don't have 10 posts and therefore I cannot post this in the actual CF-Auto-Root thread where this might help someone. However, If you happened to be having the same issue I had, I hope you find this.
I assume I cant post links to things either so, we'll skip that and hope people can google-along with me.
I should say that I am mostly to blame for my own issue since I read through several different rooting methods and I tried to quilt together pieces from each. Sometimes I think I'm smarter than I actually am when I should really just follow directions.
Here's how I went about it:
1. I pulled "adb" and "fastboot" from the webpud8 PPA (no issues)
2. I used "fastboot oem unlock" to unlock the bootloader (no issues)
3. I tried two separate auto-root methods and the Nexus-toolkit (NOTHING WORKED!)
My solution:
After pulling most of my hair out I began to realize the scripts were trying to reference a "fastboot-linux" file from the auto-rooter-specific files. In the case of CF-Auto-Root it was looking for "CF-Auto-Root-mako-occam-nexus4/tools/fastboot-linux". I don't know why the referenced "fastboot-linux" was throwing errors but I did know I had "fastboot" installed and that it was working fine.
I ran the two pieces of CF's "root-linux.sh" script manually, substituting "fastboot" in place of "tools/fastboot-linux".
They looked like this (It's important the CF-Auto-Root folder is extracted into the Home directory):
sudo fastboot oem unlock
sudo fastboot boot ~/CF-Auto-Root-mako-occam-nexus4/image/CF-Auto-Root-mako-occam-nexus4.img
I'm no expert (but I did stay in a Holiday Inn....once), and I can't claim this wont send you further in the wrong direction - but it finally ended hours of frustration for me!
-Jerry
I could never get CF-Auto-Root to properly work with my Nexus 5. I could get the script to launch but I always get this error:
downloading 'boot.img'... ERROR: usb_write failed with status e00002ed
FAILED (command write failed (No such file or directory))
I'm now experiencing the same issue with my Nexus 6. I'm convinced it's an issue with my computer, at this point.
With the Nexus 5 on Lollipop the alternate method is simply to flash a modified boot image, flash TWRP, then install the SuperSU zip. I'm looking to see if there is a similar method for the Nexus 6.
Did you unzip the file and make sure you copied the image over to your platform tools with the best file before you run it.
The phone has been in consumers hands for like 2-3 days, why don't you just wait a bit until some early kinks are worked out. I'd say in like 1-2 weeks all these root, etc issues will be much more seemless.
Pilz said:
Did you unzip the file and make sure you copied the image over to your platform tools with the best file before you run it.
Click to expand...
Click to collapse
Yeah. I moved it to the folder where I put all the factory images when I flash those without issue. I just tried throwing it into the platform tools folder under sdk and get the following error:
... INFODevice already unlocked!
FAILED (remote failure)
cannot load 'image/CF-Auto-Root-shamu-shamu-nexus6.img'
I've been using fastboot commands forever but am beyond frustrated that I cannot figure this out.
eep2378 said:
The phone has been in consumers hands for like 2-3 days, why don't you just wait a bit until some early kinks are worked out. I'd say in like 1-2 weeks all these root, etc issues will be much more seemless.
Click to expand...
Click to collapse
Very true. I'll just enjoy the phone for now and wait it out.
That's weird I had no issues with the bat file. You could flash the image and then su from what I remember and that should work
Pilz said:
That's weird I had no issues with the bat file. You could flash the image and then su from what I remember and that should work
Click to expand...
Click to collapse
think that's essentially what I did on the Nexus 5. I'll give that a try.
EDIT: is SuperSU 2.16 the latest that is in the Auto Root for the Nexus 6?
sn0warmy said:
think that's essentially what I did on the Nexus 5. I'll give that a try.
EDIT: is SuperSU 2.16 the latest that is in the Auto Root for the Nexus 6?
Click to expand...
Click to collapse
2.27 is the latest beta and is a significant change since it doesn't patch the kernel. However it is a BETA and not 100% stable...but I think Chainfire will release it fairly soon (next few days).
Try the toolkit. ??
nexus6R3plicant said:
Try the toolkit. ??
Click to expand...
Click to collapse
The toolkit doesn't work on a Mac. I'm just gonna hold off a bit longer. The only real reasons I want to root is to adjust DPI and adjust gamma settings. Aside from that I'm loving the phone so I'm not in a huge hurry.
sn0warmy said:
The toolkit doesn't work on a Mac. I'm just gonna hold off a bit longer. The only real reasons I want to root is to adjust DPI and adjust gamma settings. Aside from that I'm loving the phone so I'm not in a huge hurry.
Click to expand...
Click to collapse
Download a mint or ubuntu Linux and put it on a usb stick and boot into it but don't install unless you want it ....install adb and fastboot etc and you're good to go
nexus6R3plicant said:
Download a mint or ubuntu Linux and put it on a usb stick and boot into it but don't install unless you want it ....install adb and fastboot etc and you're good to go
Click to expand...
Click to collapse
WAY to much work to simply root the phone. :laugh:
When I get some more time I'll just flash the modified boot image, flash TWRP recovery and install SuperSU (once it's out of beta). That should do the trick.
sn0warmy said:
WAY to much work to simply root the phone. :laugh:
When I get some more time I'll just flash the modified boot image, flash TWRP recovery and install SuperSU (once it's out of beta). That should do the trick.
Click to expand...
Click to collapse
Why not just pull the image file and fastboot-mac binary from the zip and run this in the terminal.
Code:
fastboot-mac boot <image>.img
Where <image> is the name of the image file.
Should work as long as they are in the same directory.
Wugs nexus root toolkit is updated and works fine
I gave in and installed Parallels back on my Mac and used Wug's toolkit, which worked perfectly. I typically hate using toolkits because I think it's best to always know ADB and Fastboot commands. But in this case, it did the job for me.
Thanks guys!
sn0warmy said:
Yeah. I moved it to the folder where I put all the factory images when I flash those without issue. I just tried throwing it into the platform tools folder under sdk and get the following error:
... INFODevice already unlocked!
FAILED (remote failure)
cannot load 'image/CF-Auto-Root-shamu-shamu-nexus6.img'
I've been using fastboot commands forever but am beyond frustrated that I cannot figure this out.
Very true. I'll just enjoy the phone for now and wait it out.
Click to expand...
Click to collapse
Did you get a fix for this issue?
I'm getting the same error.
I unlocked my bootloader by running a separate command. do i need to relock the bootloader and run the script again.
I hate to lose all of my info
I found the issue to the error:
... INFODevice already unlocked!
FAILED (remote failure)
cannot load 'image/CF-Auto-Root-shamu-shamu-nexus6.img'
Looking at the errors and in the script, the script is looking for the a specific folder structure.
After extracting the chainfire package as instructed, I created two folders that I needed (your folder may differ).
I'm using Ubuntu should work for any other linux.
May work for window, but i don't know.
Folder structure is such, my folders are on my desktop ubuntu.
~/Desktop/Nexus6/tools
here should be the fastboot-linux file that is part of the package
~/Desktop/Nexus6/image
here put the CF-Auto-Root-shamu-shamu-nexus6.img file for rooting
~/Desktop/Nexus6
here should be the script root-linux.sh
I ran the script and now have root no issues with any errors.
Sony rolled out Android Pie 9 50.2.A.0.352 for Xperia XA2 Ultra 2 days ago. I was wondering if I proceed with the update from my rooted Oreo, will I have any working Root for Android 9 for my phone?:silly:
Only a few regions has gotten Pie so far. Makes it hard to work on getting root when most of us are still waiting.
Edit: XA2 Ultra H3223 USA just got Pie today.
Looking for this one too hoping on of this days root method will come out ..
anyone tried using magisk ? the root method last time in Oreo ? want to try it out but i'm afraid my phone will get bricked
danger
qhuinzy_09 said:
Looking for this one too hoping on of this days root method will come out ..
anyone tried using magisk ? the root method last time in Oreo ? want to try it out but i'm afraid my phone will get bricked
Click to expand...
Click to collapse
You're rightly afraid. Steer clerar of magisk. Wait for a proper rooting method, or perhaps don't root at all.
This update is already a danger (see the previous brick wave), I would wait until things calm down.
XA2 Ultra owner, not updating. Staying on Android 8 for a good while.st
ish4d0w777 said:
You're rightly afraid. Steer clerar of magisk. Wait for a proper rooting method, or perhaps don't root at all.
This update is already a danger (see the previous brick wave), I would wait until things calm down.
XA2 Ultra owner, not updating. Staying on Android 8 for a good while.st
Click to expand...
Click to collapse
yeah mate Heard the brick update in russia just waiting for the proper Root method hope it will come out soon..
But the pie update is Really Good ! over all 9/10 and also noticed the battery is far longer now :good::good:
yes guys sony xa 2 ultra root in original rom normal the steps is the same of classic all time in all others rom idk if i make a deference but me use this step 1. run adb in my pc and write fastboot boot twrp-3.2.3-1-discovery.img step2. in twrp first install addonsu-16.0-arm64-signed.zip this file take of line age os 16 idk if this make the deference but me install first this file , so step 3. install magisk and reboot phone no install twrp in phone just restart and phone work very well in original rom pie9 H4213_Customized GR_1313-7447_50.2.A.0.352_R1B i hope help good luck to root your xa 2 ultra
malamas said:
yes guys sony xa 2 ultra root in original rom normal the steps is the same of classic all time in all others rom idk if i make a deference but me use this step 1. run adb in my pc and write fastboot boot twrp-3.2.3-1-discovery.img step2. in twrp first install addonsu-16.0-arm64-signed.zip this file take of line age os 16 idk if this make the deference but me install first this file , so step 3. install magisk and reboot phone no install twrp in phone just restart and phone work very well in original rom pie9 H4213_Customized GR_1313-7447_50.2.A.0.352_R1B i hope help good luck to root your xa 2 ultra
Click to expand...
Click to collapse
Strange! I was thinking exactly the same process would've been as you've mentioned but then I intended to wait for some expert reviews or suggestions. So you are saying that you did the root exactly the way Android 8 Oreo was rooted as in the process you mentioned? So how far has it been with Android 9 with Root access with you ?
root
noob_coder said:
Strange! I was thinking exactly the same process would've been as you've mentioned but then I intended to wait for some expert reviews or suggestions. So you are saying that you did the root exactly the way Android 8 Oreo was rooted as in the process you mentioned? So how far has it been with Android 9 with Root access with you ?
Click to expand...
Click to collapse
im not sure if understand you exacly your question but my phone work super fast and very stable just follow my steps and you done 100% safe
im try post some photos in my phone to see is real
Easy-Peasy Interactive root
_/easy[+EASY-PEASY+]easy\_
ii-I/n/T_e r-A-c t_I\v\E-ee i have conjured up a simple tool for rooting the xa2 ultra. nothing special, all you do is download the zip, extract it, and run the .bat file, and follow along in the cmd prompt window. its interactive so you will have to select a few options while in recovery. its really easy. bootloader must be unlocked. make sure to read the read me files, and also follow along with the command prompt.
hope someone tries it out. i would like some opinions. im not new to computers, but im new to scripting.
any feedback would be appreciated. go to the ftp site listed below and download Also stock android 9.0 is included, its seperate from the tool. extract the zip open folder and double click newflasher.exe its all set up. just select no on the 2 options that come up before the flashing, put your device in flashmode
ftp://
192.161.
227.
73
v1nd1cta_d3b3llat0tlr said:
_/easy[+EASY-PEASY+]easy\_
ii-I/n/T_e r-A-c t_I\v\E-ee i have conjured up a simple tool for rooting the xa2 ultra. nothing special, all you do is download the zip, extract it, and run the .bat file, and follow along in the cmd prompt window. its interactive so you will have to select a few options while in recovery. its really easy. bootloader must be unlocked. make sure to read the read me files, and also follow along with the command prompt.
hope someone tries it out. i would like some opinions. im not new to computers, but im new to scripting.
any feedback would be appreciated. go to the ftp site listed below and download Also stock android 9.0 is included, its seperate from the tool. extract the zip open folder and double click newflasher.exe its all set up. just select no on the 2 options that come up before the flashing, put your device in flashmode
ftp://
192.161.
227.
73
Click to expand...
Click to collapse
strange that when I unzip a 1.8GB or so zip it just ends up with 2 small files (bat and readme) (even tried pulling the constituent files out from the zip independently). Also the batch file won't run due to windows security (understand running .bat is always risky no matter how good one's intentions might be)
mac231us said:
strange that when I unzip a 1.8GB or so zip it just ends up with 2 small files (bat and readme) (even tried pulling the constituent files out from the zip independently). Also the batch file won't run due to windows security (understand running .bat is always risky no matter how good one's intentions might be)
Click to expand...
Click to collapse
hey, thanks man, im new to this so i really apprecite it. i unzipped the 1.8gb zip, left it for download, and also left the unzipped folder and unhid everything. i left a NOTE to do explain a little better, not much, but its a little more than i am now. i changed permissions on my end, so it should be ok. as long as everything stays together in the same directory, for example the desktop,...... it doent have to be that folder, but it cant be in any other folder either, as long its all on the desktop, its good. i figure you already know that, but it makes me feel better to let you know. the .bat extracts 3 other .zip, one .zip is a usb driver and it installs it also. you can hit no, cmd will read access denied, but in this script its not considered an error, so it will continue. it will also connect to adb automatically and push 2 files, .img, .zip, to the device. if there is a problem with adb connecting, it will give notice, prompt, and when hit enter it will kill adb server and exit cmd. if everything is ok,it will boot the recovery .img automatically, given you press enter to give it permission. once in recovery it prompts instructions for the user, and a new instruction will show after every enter. well, i guess i did explain it better than i did in that NOTE.
hope i dont sound to retarded and noobish, and i hope you give it another go.
again thank you, much appreciated
.
v1nd1cta
noticed your bat file has the zip file in system32 directory
the bat file does not work due to the paths I am guessing. Why would the zip want to be in system 32 windows directory?
any update? a safe way to root in android 9?
v1nd1cta_d3b3llat0tlr said:
hey, thanks man, im new to this so i really apprecite it. i unzipped the 1.8gb zip, left it for download, and also left the unzipped folder and unhid everything. i left a NOTE to do explain a little better, not much, but its a little more than i am now. i changed permissions on my end, so it should be ok. as long as everything stays together in the same directory, for example the desktop,...... it doent have to be that folder, but it cant be in any other folder either, as long its all on the desktop, its good. i figure you already know that, but it makes me feel better to let you know. the .bat extracts 3 other .zip, one .zip is a usb driver and it installs it also. you can hit no, cmd will read access denied, but in this script its not considered an error, so it will continue. it will also connect to adb automatically and push 2 files, .img, .zip, to the device. if there is a problem with adb connecting, it will give notice, prompt, and when hit enter it will kill adb server and exit cmd. if everything is ok,it will boot the recovery .img automatically, given you press enter to give it permission. once in recovery it prompts instructions for the user, and a new instruction will show after every enter. well, i guess i did explain it better than i did in that NOTE.
hope i dont sound to retarded and noobish, and i hope you give it another go.
again thank you, much appreciated
.
Click to expand...
Click to collapse
ftp not working btw
There only seems to be Magisk root for up to 50.1.A.13.83 (Oreo)... Which is a massive pain because there have been tons of updates since, including Android Pie. I check this site loads and still nothing towards rooting for Pie.
So, not sure if this helps, but magisk seems to install fine in pie, but so far I'm having a ton of issues regarding freezes and reboots. Will search for a kernal fix, anyone have a clue to this? Just thought I'd inset my 2¢ into this and see if anyone has any insight to this. Thanks guys you do great work ?