Related
Hey guys,
well this is my first post, and it's a help post! Normally i wanted to introduce myself because I want to start hacking / developing android apps etc. ... so I first had to get in touch with adb and so (I am no unix / programming newbie, study Media Informatics (BSc. 7th. semester).
So here is the problem...
The thing I was testing is how does the Android react with editing hosts and ads... Well I knew already that my Desire has no option to enter the system area! (And yes, I bought lots of apps, Launcher PRO, root explorer, SetCPU (even I knew I could get this here before), Beautiful Widgets and some more, etc. because I know what kinda work is behind all that Apps...
So I checked if my phone is connected in Recovery Mode, Developercheck in system done... Want to edit hosts files manually, so I had to create a symlink and save that host files elsewhere... so lets go...
adb devices -> wee here it is! lets go!
opend that adb shell and went on...
adb#mount /sdcard
adb#mount /system
adb#cp /system/etc
adb#cp hosts /sdcard/etc/hosts
adb#rm -r hosts
adb#ln -s /sdcard/etc/hosts hosts
adb#exit
adb reboot
All fine ... was waiting for the reboot... saw the htc logo, got a vibra check... and well, this is since then the problem... I see the htc logo, get the vibra check, and whoops, reboot!
If I go into the boot loader menu, it takes a while and then I see for a short time some lines which say sth. like "wrong image" or "image not found" ... dno how to pause, the clockwork error log doesnt help here much!
So... WHAT can I do to get my Desire back working?!
Aw, maybe usefull information... got a O2 Desire (Germany) and working atm on x64 Win7 machine...
=(
Greetings from germany
ctb
PS: At least I take it with some humor, even if I have no other mobile to use!
Oh and maybe that will help ...
factory reset doesnt work!
cache wipe didnt help
wiping davik also not...
Any ideas? (Loading atm the original RUU and will try that!)
Or is the last hope the next O2 Shop? *grin*
creativeby said:
Hey guys,
well this is my first post, and it's a help post! Normally i wanted to introduce myself because I want to start hacking / developing android apps etc. ... so I first had to get in touch with adb and so (I am no unix / programming newbie, study Media Informatics (BSc. 7th. semester).
So here is the problem...
The thing I was testing is how does the Android react with editing hosts and ads... Well I knew already that my Desire has no option to enter the system area! (And yes, I bought lots of apps, Launcher PRO, root explorer, SetCPU (even I knew I could get this here before), Beautiful Widgets and some more, etc. because I know what kinda work is behind all that Apps...
So I checked if my phone is connected in Recovery Mode, Developercheck in system done... Want to edit hosts files manually, so I had to create a symlink and save that host files elsewhere... so lets go...
adb devices -> wee here it is! lets go!
opend that adb shell and went on...
adb#mount /sdcard
adb#mount /system
adb#cp /system/etc
adb#cp hosts /sdcard/etc/hosts
adb#rm -r hosts
adb#ln -s /sdcard/etc/hosts hosts
adb#exit
adb reboot
All fine ... was waiting for the reboot... saw the htc logo, got a vibra check... and well, this is since then the problem... I see the htc logo, get the vibra check, and whoops, reboot!
If I go into the boot loader menu, it takes a while and then I see for a short time some lines which say sth. like "wrong image" or "image not found" ... dno how to pause, the clockwork error log doesnt help here much!
So... WHAT can I do to get my Desire back working?!
Aw, maybe usefull information... got a O2 Desire (Germany) and working atm on x64 Win7 machine...
=(
Greetings from germany
ctb
PS: At least I take it with some humor, even if I have no other mobile to use!
Click to expand...
Click to collapse
you should of done a nandroid in recovery first you could always try a hard reset, you could try removing the symlink too, im not sure if you should symlink to the sd card like that, maybe you should of used /data/ect/hosts or something like that.
*edit* sorry i didnt see you tried a hard reset an ruu will defo work, but its a bit extreme, your rooted arnt you? just flash the same rom from recovery
So you can access recovery? Just flash a new rom. Because you messed with /system a factory reset won't fix it. Or do a nandroid if you have one.
Hehe thanks for the replies!
Well, the idead of that nandroid backup came up in the second i rebooted... was to late! *giggle*
Okay so I have to learn how to flash a new rom... lets get it on! Hehehe!!!
Any recommendations for good roms?!
saw that coming!
creativeby said:
Hehe thanks for the replies!
Well, the idead of that nandroid backup came up in the second i rebooted... was to late! *giggle*
Okay so I have to learn how to flash a new rom... lets get it on! Hehehe!!!
Any recommendations for good roms?!
saw that coming!
Click to expand...
Click to collapse
theres only 2 worth having, auraxtsence for bling, and leedroid for stability
Weeeeeeeeeee it works again!!
Wow thank you so much for your help guys!
btw: leedroid rocks!
How to I Install Xposed on Rooted Amazon Fire TV 2? (Guide Please)
Do I download XposedInstaller_3.0_alpha4.apk? and xposed-v78-sdk21-arm64.zip?
Please Help
Could I Use Flashfire?
You can't install xposed since there is no custom recovery
Tried with Flashfire where no custom recovery is needed ? what version of xposed should i try?
No Luck with Flashfire and xposed v78-sdk22-arm 64. Going to have to wait for a fix
yeah I've had no luck, just have to wait I guess
ians325 said:
No Luck with Flashfire and xposed v78-sdk22-arm 64. Going to have to wait for a fix
Click to expand...
Click to collapse
Did you encounter boot loop or soft-brick when you attempted this?
z_thompsonpa said:
Did you encounter boot loop or soft-brick when you attempted this?
Click to expand...
Click to collapse
No
ians325 said:
No
Click to expand...
Click to collapse
Thanks! You prompted me to give this a shot after confirming that it wouldn't do any serious damage. I found some things out in the process that explain why this isn't working as of yet.
The Xposed zip you mentioned requires the following Linux GNU tools (or equivalent):
cut
find
head
sed
I suspect this is why it is failing, because I was able to backup my system partition and restore my backed-up system partition through FlashFire. (more on this later)
Sooo.. I thought why not go all the way and try to install BusyBox first? ..since this would fix the missing commands
Much to my surprise the Busybox install actually worked and I had the whole suite of linux commands at my disposal!!!
Things went south pretty quick, though, when I realized that SELinux was blocking my ability to run the following command:
I couldn't run this command:
Code:
mount -o remount rw /system
So, this would prevent a further attempt at installing Xposed through Flashfire, because it would have to mount the system partition as rw in order to modify the files and add the Xposed framework.
I ended up restoring my system partition after this fiasco using Flashfire. It re-enabled my ability to remount /system as rw and SELinux has seemed to calm down in the logs.
In conclusion:
Xposed requires Busybox
[*]SELinux enforces more policies when Busybox is installed
[*]Setting SELinux to Permissive has no effect
EDIT: **Details in my next post**
z_thompsonpa said:
Thanks! You prompted me to give this a shot after confirming that it wouldn't do any serious damage. I found some things out in the process that explain why this isn't working as of yet.
The Xposed zip you mentioned requires the following Linux GNU tools (or equivalent):
cut
find
head
sed
I suspect this is why it is failing, because I was able to backup my system partition and restore my backed-up system partition through FlashFire. (more on this later)
Sooo.. I thought why not go all the way and try to install BusyBox first? ..since this would fix the missing commands
Much to my surprise the Busybox install actually worked and I had the whole suite of linux commands at my disposal!!!
Things went south pretty quick, though, when I realized that SELinux was blocking my ability to run the following command:
Code:
mount -o remount rw /system
So, this would prevent a further attempt at installing Xposed through Flashfire, because it would have to mount the system partition as rw in order to modify the files and add the Xposed framework.
I ended up restoring my system partition after this fiasco using Flashfire. It re-enabled my ability to remount /system as rw and SELinux has seemed to calm down in the logs.
In conclusion:
Xposed requires Busybox
SELinux enforces more policies when Busybox is installed
Setting SELinux to Permissive has no effect
Click to expand...
Click to collapse
Nice work, have you seen this tidbit on BusyBox Github for SELinux?
https://github.com/ukanth/afwall/wiki/BusyBox#difference-between-selinux-and-non-selinux-busybox
There's also some decent results on Google that may offer some clues... https://www.google.com/search?q=SELinux+mount+system+as+rw+android&ie=utf-8&oe=utf-8
fldash said:
Nice work, have you seen this tidbit on BusyBox Github for SELinux?
https://github.com/ukanth/afwall/wiki/BusyBox#difference-between-selinux-and-non-selinux-busybox
There's also some decent results on Google that may offer some clues... https://www.google.com/search?q=SELinux+mount+system+as+rw+android&ie=utf-8&oe=utf-8
Click to expand...
Click to collapse
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.
keep up the good work
z_thompsonpa said:
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.
Click to expand...
Click to collapse
How are you restoring your system partition? Using that diff patcher (for root) with a USB A-A cable?
fldash said:
How are you restoring your system partition? Using that diff patcher (for root) with a USB A-A cable?
Click to expand...
Click to collapse
I haven't had to break out the USB A-A cable yet... thankfully (except for root of course).
I used Flashfire to backup my /system partition as RAW backup before I started all of this experimentation. I have just been restoring back to this known good state using Flashfire after each time I corrupt the system partition.
I intended on trying this method, and if it didn't work to fall back to the method mentioned in the root thread. I checked the logs last night and Flashfire seems to be succeeding at this task, at least.
Right now, I am picking through the Xposed installer script source and using the Flashfire logs to debug why it is failing. It appears to be a permissions issue, but a lot of the stdout/stderr is suppressed so its hard to tell exactly where. When I get home today, I am going to try to modify the installer script to produce more output so I can debug the issue further. If I cant figure it out, I'll post my findings either way.
I've fixed a few bugs in the flash script already, but it always errors on overwriting:
Code:
/system/lib/libart.so
It's throwing some error about read-only filesystem. (I'll post exact error later)
I've thrown in some checks to see if the /system mount is unmounting or something odd like that, but that's not it.
I've got a few guesses as to why, but I am not going to mention them until I have more solid evidence.
Any advice would help as well... I just wanted to post the update I promised.
z_thompsonpa said:
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.
Click to expand...
Click to collapse
z_thompsonpa said:
I've fixed a few bugs in the flash script already, but it always errors on overwriting:
Code:
/system/lib/libart.so
It's throwing some error about read-only filesystem. (I'll post exact error later)
I've thrown in some checks to see if the /system mount is unmounting or something odd like that, but that's not it.
I've got a few guesses as to why, but I am not going to mention them until I have more solid evidence.
Any advice would help as well... I just wanted to post the update I promised.
Click to expand...
Click to collapse
I think we should go another method. Use the tools in the root thread to just create an image with Xposed/root and just do a DIFF.
fldash said:
I think we should go another method. Use the tools in the root thread to just create an image with Xposed/root and just do a DIFF.
Click to expand...
Click to collapse
I think so... I am pretty sure its a dead end. I also tested using adb to write the files and it failed on /system/lib/libart.so, as well. It's, I believe, because the object is loaded in memory?? don't quote me on that... but loading through preloader, I think, would avoid this limitation as ART is not running.
So can anyone in here tell me if its possible to have xposed on fire tv 2 5.0.5 thats rooted and now has twrp recovery on ? I have tried to flash the xposed zip in recovery but when i reboot its stuck at amazon logo. Went back into recovery and flashed rbox's pre rooted 5.0.5 and booted normally. Id like to have (im sure many others would also) xposed and playstore, ive searched the forums but because rbox method is new there is no information on this subject now.
sconnyuk said:
So can anyone in here tell me if its possible to have xposed on fire tv 2 5.0.5 thats rooted and now has twrp recovery on ? I have tried to flash the xposed zip in recovery but when i reboot its stuck at amazon logo. Went back into recovery and flashed rbox's pre rooted 5.0.5 and booted normally. Id like to have (im sure many others would also) xposed and playstore, ive searched the forums but because rbox method is new there is no information on this subject now.
Click to expand...
Click to collapse
Use this method, I've slightly modified the text from another post & added it into a text file for you, this works a 100% but as usual I take no responsibility if you do any thing wrong & brick the Fire Tv2.
Enjoy & press that thanks button If this helped you
Thanks for this. I will try it shortly and report back if it works for me. I have stumbled upon another thread that the guys seem to be working on playstore issues, http://forum.xda-developers.com/fire-tv/help/q-guide-to-getting-google-play-rbox-t3310974
Made a guide here if anyone wants to install
http://forum.xda-developers.com/fire-tv/general/installing-xposed-fire-tv-2-guide-t3314142
Hi folks,
I need your help.
A few days ago I have received my brand new HTC 10. I updated to latest Android 7 Nougat and began to root remaining stock.
I followed the official guide and unlocked the bootloader, flashed latest TWRP (3.1.1.0) and SuperSU v.2.82SR1 and even got S-OFF by SunShine.
System is up an running and readily booting but...
Fact is I cannot mount /system in TWRP without the option "read-only". When I try to install apps via TWRP I get repeated messages saying "Failed to mount '/system' (Invalid argument) " and usually the apps do not install properly - flashed apps do not show up in the system after reboot.
In the system I have tried to rename a file audio_effects.conf (this is needed to install Viper4Android) in the folder /vendor/etc/ on the device but the folder is strictly read only. Any attempts to mount the folder as RW (using "adb shell", "su", "mount -o remount,rw /system" and similar) have failed. I have tried to gain access to files in the system folder using Root Explorer and Total Commander but the files remain strictly read only. I just get error messages trying to change file attributes, permissions,names).
SuperSU seems to work and according to Root Checker I am properly rooted but I doubt this. Somehow /system seems to be locked and not accessible.
Any ideas what I could do ?
Many thanks for your help ! :good:
Well, I simply flashed Viper10 ROM and the issue was gone.
Feel free to suggest solutions to the problem as somebody else might come accross this thread struggling with a similar issue. I believe the issue was caused by an incompatibility between the latest Android Nougat and the last available TWRP.
Buddha1979 said:
Well, I simply flashed Viper10 ROM and the issue was gone.
I believe the issue was caused by an incompatibility between the latest Android Nougat and the last available TWRP.
Click to expand...
Click to collapse
No, it's not an incompatibility issue.
Does anyone know what is causing this? I been running into a similar type issue where I get an error trying to flash ROM's. Tried to do a TWRP backup and it failed to back up data. I do a factory reset and data format and it seems to fix some things but still have trouble flashing ROM's. I was able to restore a nandroid but have ran into this issue a few times. I am on Viper magisk.
plz help a noob
LibertyMonger said:
Does anyone know what is causing this? I been running into a similar type issue where I get an error trying to flash ROM's. Tried to do a TWRP backup and it failed to back up data. I do a factory reset and data format and it seems to fix some things but still have trouble flashing ROM's. I was able to restore a nandroid but have ran into this issue a few times. I am on Viper magisk.
Click to expand...
Click to collapse
I also just recently updated to nougat and when i tried to root using the latest (TWRP 3.0.3-11) it seems I get stuck on a screen with red text that says, "This build is for development purpose only . Do not distribute outside of htc without htc's permission."
I know this is not the original question but was hoping someone with more experience could help instead of starting a new thread :/
Thanks much!
I just ran the latest Verizon RUU and I am still getting this error when trying to flash Viper10_5.9.0_MAGISK. Seems system is not mounting, I don't know I will appreciate any help Thank you.
Hi fellow developers,
I need to do modify my HTC 10's hosts file, but with the latest OTA update to Android 8.0, I find it impossible to make any functional changes to the hosts file. Does anyone have a clue?
I am rooted, and S-OFF with TWRP recovery.
In recovery, I have tried modifying all of these:
/system/etc/hosts
(which is only there normally when the phone is booted and running, I can't figure out where it's coming from)
/data/hosts
/data/data/hosts
None of these work.
Please help, if you know! I cannot find any information online, after hours of research and troubleshooting...
cheers,
Jordan
P.S. Despite S-Off and root, I find that many root procedures don't work when android is booted, disappointed, cannot understand why. Miss my One M8!
jorxster said:
Hi fellow developers,
I need to do modify my HTC 10's hosts file, but with the latest OTA update to Android 8.0, I find it impossible to make any functional changes to the hosts file. Does anyone have a clue?
I am rooted, and S-OFF with TWRP recovery.
In recovery, I have tried modifying all of these:
/system/etc/hosts
(which is only there normally when the phone is booted and running, I can't figure out where it's coming from)
/data/hosts
/data/data/hosts
None of these work.
Please help, if you know! I cannot find any information online, after hours of research and troubleshooting...
cheers,
Jordan
P.S. Despite S-Off and root, I find that many root procedures don't work when android is booted, disappointed, cannot understand why. Miss my One M8!
Click to expand...
Click to collapse
Hello mate.
Have u tried edit hosts file using any text editor? try get Root Explorer, navigate to /system/etc/ and mount R/W. select hosts file & edit.
aM- said:
Hello mate.
Have u tried edit hosts file using any text editor? try get, navigate to /system/etc/ and mount R/W. select hosts file & edit.
Click to expand...
Click to collapse
Thank you aM- for replying, someone hears my cry for help!
I tried to mount /system as read-write and instead got an "Error : The operation could not be completed".
This is frustrating, as again, I got S-OFF specifically for this purpose.
And SuperSU seems to function normally, asking me to grant permissions.
I had the same problem with a terminal editor, being unable to SU, permissions denied.
Are you on Android 8.0 Oreo as well?
jorxster said:
Thank you aM- for replying, someone hears my cry for help!
I tried to mount /system as read-write and instead got an "Error : The operation could not be completed".
This is frustrating, as again, I got S-OFF specifically for this purpose.
And SuperSU seems to function normally, asking me to grant permissions.
I had the same problem with a terminal editor, being unable to SU, permissions denied.
Are you on Android 8.0 Oreo as well?
Click to expand...
Click to collapse
Yes, I'm on Android 8.0. Have you check either your device rooted or not? if rooted, supposedly on terminal also should be no problem.
aM- said:
Yes, I'm on Android 8.0. Have you check either your device rooted or not? if rooted, supposedly on terminal also should be no problem.
Click to expand...
Click to collapse
I should be rooted.. I am unlocked and S-OFF.
I flashed SuperSU-v2.82-201705271822.zip from TWRP recovery.
I have the SuperSU app installed and it seems to run normally.
But I cannot "su" in a shell like you did, cannot mount /system partition as write, really, cannot do anything root.
Do you know what version of SuperSU you rooted yours with?
P.S. Android 8.0 as well, not 8.1 (which I presume hasn't rolled out to OTA yet)
jorxster said:
I should be rooted.. I am unlocked and S-OFF.
I flashed SuperSU-v2.82-201705271822.zip from TWRP recovery.
I have the SuperSU app installed and it seems to run normally.
But I cannot "su" in a shell like you did, cannot mount /system partition as write, really, cannot do anything root.
Do you know what version of SuperSU you rooted yours with?
P.S. Android 8.0 as well, not 8.1 (which I presume hasn't rolled out to OTA yet)
Click to expand...
Click to collapse
Currently I'm using SuperSU from here https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Navigate to system/bin
"su" file in there?
Sent from my HTC 10 using Tapatalk
Thanks so much aM- and fmedrano1977.
I've made progress. I reflashed my phone with the later SuperSU SR5 zip that you posted, wiped dalvik/cache, rebooted. Now I can "su", as well as mount /system/etc as read/write. Success!
There was a couple of catches, at least two or three other apps that don't seem to work with root anymore (like the previous file explorer I had, supposed to support root, but only "root explorer" worked after I bought it).
Now modifying my hosts file seems to have no effect, but I suppose that's another issue for another day. As it stands, I can now edit my hosts file thanks to your help.
Cheers!!
jorxster said:
Thanks so much aM- and fmedrano1977.
I've made progress. I reflashed my phone with the later SuperSU SR5 zip that you posted, wiped dalvik/cache, rebooted. Now I can "su", as well as mount /system/etc as read/write. Success!
There was a couple of catches, at least two or three other apps that don't seem to work with root anymore (like the previous file explorer I had, supposed to support root, but only "root explorer" worked after I bought it).
Now modifying my hosts file seems to have no effect, but I suppose that's another issue for another day. As it stands, I can now edit my hosts file thanks to your help.
Cheers!!
Click to expand...
Click to collapse
Glad to hear that. Happy modify system mate.
jorxster said:
Thanks so much aM- and fmedrano1977.
I've made progress. I reflashed my phone with the later SuperSU SR5 zip that you posted, wiped dalvik/cache, rebooted. Now I can "su", as well as mount /system/etc as read/write. Success!
There was a couple of catches, at least two or three other apps that don't seem to work with root anymore (like the previous file explorer I had, supposed to support root, but only "root explorer" worked after I bought it).
Now modifying my hosts file seems to have no effect, but I suppose that's another issue for another day. As it stands, I can now edit my hosts file thanks to your help.
Cheers!!
Click to expand...
Click to collapse
i was lead here from an answer for my question, i;m curious when getting the host file prepared ,the steps others helped you with,did your device data get deleted ?
Need help, folks:
my old Nexus7/2013 has dead USB port but long time ago I unlocked boot and flashed teamwin recovery 3.2.1.0
Problem: at this moment it has Marshmallow 6.0.1 (MOB30X) which is NOT rooted...
Is it possible - without adb / without connection to PC since USB port is dead - to flash it with old kitkat 4.4.4 (preferred) , or at least how to root it's current marshmallow 6.0.1?
/my original post had been edited for clarity
Nexus7-2013 said:
Need help, folks: my old Nexus7/2013 has dead USB port but long time ago I unlocked boot and flashed teamwin recovery 3.2.1.0 Problem: at this moment it has Marshmallow 6.0.1 (MOB30X) which is NOT rooted... Is it possible - without adb / without connection to PC since USB port is dead - to flash it with old kitkat 4.4.4 (preferred) , or at least how to root it's current marshmallow 6.0.1? /my original post had been edited for clarity
Click to expand...
Click to collapse
To root it is very simple, get Magisk, save it into the SDCARD folder, boot TWRP and install it. That's all.
Better yet, fix the damn USB port, it takes only a few minutes, then you can proceed as usual - https://forum.xda-developers.com/t/...r-request-failed.3493322/page-2#post-83468773
k23m said:
To root it is very simple, get Magisk, save it into the SDCARD folder, boot TWRP and install it. That's all.
Better yet, fix the damn USB port, it takes only a few minutes, then you can proceed as usual - https://forum.xda-developers.com/t/...r-request-failed.3493322/page-2#post-83468773
Click to expand...
Click to collapse
First of all, thank you for replying.
Yes I have tried latest Magisk 20.4, it starts and all good until this part:
...
- Checking ramdisk status
! Boot image patched by unsupported programs
! Please restore back to stock boot image
- Unmounting partititions
Update process ended with ERROR.... blah blah blah
Click to expand...
Click to collapse
Well, it is partially correctly beaching because previously I did have tried rooting with some outdated versions of supersu and magisk too, before I realized they're damn old (it was very late at night)
So, what's your suggestion in this case?
Oh, and for fixing USB port I will do it eventually, no problems here soldering anything, but i'm really not good with prying plastic covers... To cut it short, I already destroyed 2 covers and 1 screen on a nexus 6p and on another similarly held-by-glue-and-spit poorly designed device in the past when I was trying to open them. If it isn't hold together by screws I rather don't do it, at least not until I would really have to. Since this tablet is still working fine and is very useful for reading books or watching videos in bed before sleep, the only hardware-wise inconvenience is using damn wireless charger.
Yes, I am planning to fix USB port (and yes again - by resoldering whatever pins broke out there, and not by swapping entire usb daughter-board) but I want to do it when tablet's battery will start to give up too. That's when I will have no other choice but to open it up... But right now battery still gets 4-5hrs SoT, which is more than enough for me.
Nexus7-2013 said:
...I did have tried rooting with some outdated versions of supersu and magisk too, before I realized they're damn old (it was very late at night) So, what's your suggestion in this case?
....similarly held-by-glue-and-spit poorly designed device in the past when I was trying to open them. If it isn't hold together by screws I rather don't do it
Click to expand...
Click to collapse
I suggest to reflash the boot image. Get mob30x and unpack it completely to access this file:
Restock2\data\razor-mob30x\image-razor-mob30x.zip\boot.img
If the unpacking was done on a PC then transfer the boot.img to N7 via WiFi first.
Next boot TWRP, in the Install function switch to image mode and flash boot.img.
As for N7 disassembly, there is no glue involved, easy.
k23m said:
I suggest to reflash the boot image. Get mob30x and unpack it completely to access this file:
Restock2\data\razor-mob30x\image-razor-mob30x.zip\boot.img
If the unpacking was done on a PC then transfer the boot.img to N7 via WiFi first.
Next boot TWRP, in the Install function switch to image mode and flash boot.img.
Click to expand...
Click to collapse
I didn't realized you're the same person who posted "restock" (your path to img file ticked me off) that I read about in another thread! Thank you very much for making it and sharing it, though I can't use it yet obviously, but I have found in restock thread your mob30x-fix zip, which I have used on my N7 - just FYI it worked great and cleared all the old Goo junk apps when I tried it. Very useful tool. Thank you!
(also: leaving old Google Music app was excellent choice since it is useful for local files; and making skip button active on initial wifi setup screen is really very nice touch! You have no idea how many times I cursed damn Goo devs for greying out this option)
OK, mob30x image downloaded from Goo (terrible - they removed all the previous kitkat and lollipop images!), boot.img extracted and installed, rebooted, installed Magisk 20.4 . All went flawlessly.
So I guess - with your help - I have rooted mob30x without adb
Thank you again!
(root confirmed - i just installed my fav Android Firewall and it was granted superuser access - woo hoo! Now I can block ipv6 connections too)
Now, what about flashing kitkat on this tablet without usb port ... ?
Nexus7-2013 said:
Now, what about flashing kitkat on this tablet without usb port ... ?
Click to expand...
Click to collapse
It seems doable but I have not fully tested it. If you make a mistake you may be finally forced to fix the port ...
This method will not work with Android 5+:
- get razor-ktu84p-factory-2482a7d5.zip and extract boot.img and system.img to /sdcard/
- copy the attached android4-system-flash.zip to /sdcard/
- boot TWRP, do Wipe and flash the boot.img as usual
- in TWRP install android4-system-flash.zip which I estimate would take around 70 minutes
The image needs to be processed on the fly. It was so slow, I gave up and only did a partial flash...
Code:
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system ibs=1 obs=4M skip=40 count=10M
10485760+0 records in
2+1 records out
10485760 bytes (10.0MB) copied, 57.214905 seconds, 179.0KB/s
We need to remove 40 bytes from the beginning of system.img. The existing dd function has a subset of features and a faster option is not available. You could mod the image on PC and flash it much faster with an altered install zip:
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system bs=4M
Cheers!
EDIT
I have noticed a filesystem error with this method but there is another way. PM me if you really need it.