Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
bohemianRhapsody said:
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
Click to expand...
Click to collapse
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
root is easy
bohemianRhapsody said:
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
Click to expand...
Click to collapse
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
it0 said:
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
Click to expand...
Click to collapse
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Lukas_a_1996 said:
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Click to expand...
Click to collapse
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
it0 said:
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
Click to expand...
Click to collapse
Thanks for the reply . I tried to run the command in impactor but whatever i do i get "Signature bugs unavailable" could it be that i have the wrong ADB drivers installed or is my Impactor setup wrong?
Edit: yeah im running 4.1.2 Build A1001231
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
All the adb commands basically work but nothing works with impactor i just get error
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
Bump!
How to Root Medias N05e
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
nguyenbuulam said:
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
Click to expand...
Click to collapse
There is a way for temp root N05E, basically u can use pm disable command or other su stuff. But u cannot mount system rw right now.
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
How to enter recovery mode?
Despite starting this thread, in the end I never did bother to attempt rooting.
Anyway, unfortunately now the phone refuses to boot. Not triggered by anything obvious, haven't installed any new software recently, etc. Just hung one day and then when I removed and re-inserted the battery, it won't get any further than the "docomo" splash screen. I.e. the OS doesn't appear to be getting bootstrapped at all. The "docomo" splash screen appears and disappears then the phone sits there with both screens powered up but blank.
As it happens, I had ADB Debug enabled in the developer options at the time, so I've tried to see if I can adb shell into the device, but no luck. Not surprised as it's clearly not getting far enough into the boot for that to work.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
bohemianRhapsody said:
Despite starting this thread, in the end I never did bother to attempt rooting.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
Click to expand...
Click to collapse
In recovery mode, clear cache, etc..
To get there hold volume down and power at the same time,then you'll see the broken android then wait/ press vol down a couple of times to see the menu.
GRbit said:
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
Click to expand...
Click to collapse
did you ever figure out the recovery keys?
hamishhhhs said:
did you ever figure out the recovery keys?
Click to expand...
Click to collapse
No I didn't(
I'm actually sold this phone and lost interest in the topic.
GRbit said:
No I didn't(
I'm actually sold this phone and lost interest in the topic.
Click to expand...
Click to collapse
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
hamishhhhs said:
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
Click to expand...
Click to collapse
Sorry, but this was too long time ago. Nothing left
GRbit said:
Sorry, but this was too long time ago. Nothing left
Click to expand...
Click to collapse
how would j be able to get the files from my phone?
hamishhhhs said:
how would j be able to get the files from my phone?
Click to expand...
Click to collapse
I dunno man.
I've already described (in the first post you have quoted) what I achieved with this github repo https://github.com/android-rooting-tools/android_run_root_shell . That's all I've got.
Related
dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Simplest way i know.
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
is3od said:
dears,
i have rooted 3G Xoom (MZ601).. 3.0.1
now i want to update it to 3.1 or 3.2
and i want to activate the US market ..
please, any one can guide me to do it ..
Click to expand...
Click to collapse
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer File name: SDK ADB.zip File size: 359.93 KB put them all in a folder called rootxoom or something.
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
His Xoom is 3G there is no OTA update to 3.2 for 3G.
I really would not relock and go back to stock. He's rooted and that's more than half the battle.
is3od, the method I posted is for non-US Xooms as long as they are rooted.
i'll try it
prowlex said:
1. Relock your zoom and go back to stock:
http://forums.androidcentral.com/xo...stboot-official-system-images.html#post708799
2. Update through the system update on your xoom.
3. Once you get up to 3.2 unlock and reroot your xoom:
http://forum.xda-developers.com/showthread.php?t=1170760
+ this way now you can reset it back to stock completely if you ever need too. Step by step guides are very easy to follow. Mostly copy and paste commands into notepad if your lazy like me. The whole process takes maybe 20 minutes.
Click to expand...
Click to collapse
thank you for your help... today i'll try it and will inform you about the result.
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
first i will relock my xoon then i'll update it ..
thank you,
prowlex said:
incase you dont have sdk installed put all files in a folder on your C:/ directory with a name you can find. Youll need these in addition to be able to use adb on your computer put them all in a folder called rootxoom or something.
Click to expand...
Click to collapse
ok
thanks...
k66473 said:
Dear friends
Could you please confirm that above tutorial can be applied for 3G version of xoom?
I see some of guide with noted that applying for wifi version only.
Regards,
Click to expand...
Click to collapse
it should be, because my Q is for 3G Xoom.
is3od said:
it should be, because my Q is for 3G Xoom.
Click to expand...
Click to collapse
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
thanks a lot
okantomi said:
You have ignored my posts which are for non-US 3G Xoom. Pleease check them again. I was not the one to tell you to go back to stock, unroot and relock. Please don't do that...no need.
Just try to follow the guide I posted in #3. Good luck.
Click to expand...
Click to collapse
I really appreciate your help .. thanks a lot ..
adb devices returns no devices
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Make sure USB Debugging is checked under Settings/Applications/Development. If it is checked, then there is something wrong with your drivers.
big flamingo said:
I have followed the tutorial after reading through it several time to unlock and root stock xoom 3.2. when i get to the adb devices command it returns me to the prompt with no devices returned or shown. i have android sdk windows in root of C:. i have rootboot.img, superuser.apk & su binary in a xoom folder in my downloads folder. i open the cmd in the download folder wherein resides rootboot.img, superuser.apk & su binary and type adb devices and nothing. i can see the xoom in explorer so i assume the usb drivers are there. i do have a yellow flag in other devices in device manager-other devices that says MZ604. but i can find no drivers anywhere for it though i have scoured the web for 2 days. i am at a loss as i have tried to perform this root for 2 days using all of my adb noob skills, but have had no luck as of yet. any suggestions? win7, stock xoom 3.2 wifi, pretty computer savvy except for adb
Thanks for any help as i only have 4 days of return left in case of brickage, which i am not so sure i would do inasmuch as it would be my fault...
Click to expand...
Click to collapse
Check the thread you started...people have answered there.
okantomi said:
Hi ,
I think you can go directly from 3.01 to 3.2 using this guide:
http://forum.xda-developers.com/showthread.php?t=1183416
If you don't already have ClockworkMod recovery v3.2.0.0 R4c installed, pay attention to post #7.
Good luck!
Click to expand...
Click to collapse
I'd like to do the same as OP, update a rooted stock 3.0.1 euro 3G to 3.2 - I've already come across the thread you link to, but there's something I don't get.
pienut (user whose post you linked to) is saying that he went from 3.0.1 to 3.2, but in step 3 he writes:
Step 3 - Install 3.2 EURO rom:
Just copied the Euro 3.2 update from this post to my SD Card and flashed it from recovery.
Just to be sure, I did a full wipe after flashing.
Click to expand...
Click to collapse
Am I missing something, or is the SD card not disabled in 3.0.1? I know it is for me, afaik it only started working with 3.1 and up. I can't wrap my mind around going from 3.0.1 -> 3.2 using the SD card method, and yet it's mentioned in quite a few more threads and posts.
Ideally, I'd like to update to the Xoom ROM 2.1 Hammerhead (http://forum.xda-developers.com/showthread.php?t=1203635), but in those instructions, too, step 2 says
Download the 2.1 rom zip file and place it on your external sdcard
Click to expand...
Click to collapse
How, if I can't access it in the first place? Should I install 3.1 first before I install Hammerhead? If so, do you know about any step-by-step I can follow?
Sorry to jump in on this thread like this... it was the closest I could find related to my problem after hours of searching and reading. Thanks.
Alright, I figured it out on my own... I took a leap of faith and installed the ClockworkMod Recovery 3.2.0.0 (R4c), booted to recovery, and in there it's possible to mount the SD card under mounts and storage > mount usb storage. It will then appear in Windows as an external drive (as usual).
Yay, learned something new today. Now on to the next battle
Does anyone know if Z4Root will work on this tablet? Thanks!
I've been looking for one for 3 days now, I tryed onclickroot and z4root or something like that,, cant find anything Anyone please help!!
I'm still waiting for my tablet to be delivered...I'm gonna try SuperOneClick (crosses fingers)
I got one of these for my daughter for xmas. I spent a few days trying to root it with no luck. I'm not intimately familiar with android (some unix experience), but I tried all the options I could find for rooting Allwinner a10 devices. At first I ran into problems with adb unable to recognize the device for most one-click methods. I downloaded the android tools and was able to connect with the included adb. After studying the scripts, they all use the "adb root" command to gain root access on the device and copy the necessary files. Unfortunately, this command fails using adb from the tools. At first I thought this was due to my adb version, but after doing some research I think it is actually due to the device kernel. I believe it requires reflashing or some exploit to be able to gain root. I was able to install root explorer and I can browse all the necessary directories but I can't modify or copy the necessary files into them. Busybox told me there was an older version installed, but wouldn't let me install a newer version (again I think due to the permissions). Also, superuser would say it installed but the su binary did not show up on the bin directory. As the necessary directories are all owned by root, I couldn't figure out a way to modify the permissions...
I wound up returning the FileMate and got a Lenovo IdeaTab. Got that rooted in no time.
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
ferny_dx said:
sorry i never saw this post i've bought 2 of these and i rooted them,
i wish i could get a better build for them though, too many app crashes and the internet connectivity sucks
i used a method by Bin4ry called root with restore, v17 worked any ways i have the zip if you would like it
Click to expand...
Click to collapse
Screw it, here it is for future reference.
How'd you do it!?!?
ferny_dx said:
Screw it, here it is for future reference.
Click to expand...
Click to collapse
FileMate Clear T720
Thank you very much for being the only person ever to have posted in regards to this tablet. I just got mine for christmas and have been trying to get it rooted. I've tried a lot of those one-click methods, and I've even tried this Bin4ary method. but it just hangs up on "daemon started sucessfully*"
Can you please direct me to the filemate drivers (if needed)
also, I have usb debugging endable, allowing 3rd party (not secure) files enabled. and pulling my hair out (enabled).
Thanks again.
Also, I'm running windows 7 and 8, (((maybe i should try win7))) hmm. i'll get back to you on that. Anyhow, any advice would be greatly appreciated, since returning it doesn't sound very fun.
jiberish05 said:
FileMate Clear T720
pulling my hair out (enabled)..
Click to expand...
Click to collapse
I laughed so hard. ok your going to have to install drivers by force,
first off do you happen to have android sdk installed? if you don't there is another way but its going to sound weird,
if you do have the android SDK installed:
1. go to your computer manager (by opening explorer, right click on the "computer" group on the left column and select manager)
2. look for any unrecognized item that appears, ( it will most likely be labeled "Clear" with a faded icon and a "?" sign on top
3. right click and choose "Update drivers", it will give you options, choose "Browse my computer for driver software", another option screen will show,
4. at the bottom of the window there will be an option that says "let me pick from a list of device drivers on my computer"
5. on the screen that appears there should be an option that says "ADB Interface", choose this
6. choose "Google, Inc.">"ADB Testing Interface version x.x.x.x" (I chose version 2.1.0.0)
that should do it next time you plug in the tablet try running ddms or open the cmd and type in "adb devices" (assuming you have adb installed) and it should show.
if this helps just hit the thanks button
[edit] I am running windows 8 btw [/edit]
ADB interface doesn't show up
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
jiberish05 said:
Thank you very much for getting me farther, however I dont see ADB interface. I'm looking into it right now. I just re-installed the sdk drivers and will keep at it.
BTW, is it even worth doing this? the main reason I want to do it, is so i can connect my ps3 remote via bluetooth, and possibly a little overclocking. Have you had any luck OC it?
Thanks again Much appreciated:good:
Click to expand...
Click to collapse
open up SDK manager and go to Extras>"Google USB Drivers"
also install everything in the "Android 4.0 (API 14)" section, I have other options installed if this still doesn't work.
its worth it just for the extra stuff that root comes with like titanium backup, but you cant over clock, if you go any higher than 1200 MHz it will lock up and you have to force it to reset.
cyberkeeper1 said:
HERE is the link to root as provided earlier
Click Here to download ADB universal drivers. they should work better than the google USB drivers.
---------- Post added at 12:20 AM ---------- Previous post was at 12:11 AM ----------
this seems kind of spammy. What backs up my claim is that you dont have more than 5 posts...
Click to expand...
Click to collapse
Thanks for the link to my post on android central, the link in that post just comes back the xda thread
Root MANY ANDROID! [Upd: 20.11.2013] - Added Z1 Root
Sent from my XT862 using Tapatalk
Rooted Filemate Clear
I just wanted to confirm I have also rooted the Clear with the Bin4ry v33 exploit using option 1. Although I received the following error:
remote object '/system/bin/ric' does not exist
.
Going to copy files to it's place
Rebooting again, please wait!
Could Not Find C:\Documents and Settings\Graham School\My Documents\Downloads\Ro
ot_with_Restore_by_Bin4ry_v33\ric
Restoring previous Backup! Please select the RESTORE MY DATA option now on your
device!
SuperSu installed and root apps working.
Rooted With Kingo
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, no problem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Jfender1005 said:
I just bought one of these cheap to play with and used Kingo to root it. Worked first time, lem. The only issue I am having is that the SuperSu binaries are failing to update but root is still working. Titanium is working and Root Explorer so I can debloat. Hope that helps is anyone is still trying to use these
Click to expand...
Click to collapse
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Kingoroot
cyberkeeper1 said:
please tell me where in the world you got the Kingo root?
As far as being unable to update binaries, try to find a custom recovery and install. From there, you can inject them via su-binary update.zip and bam!
Click to expand...
Click to collapse
http://www.kingoapp.com/android-root.htm
That is the link for the Kingo site. The first time I saw it on here there was some question about whether it was safe becase it is not open source and used a Chinese SuperSu app. I felt safe using it on a tablet because I do no banking on it or anything, but the newest posts I have seen are that Kingo is safe. Hope that helps. And if you know where to find a custom recovery that will work with this app please let me know.
how to make a flashable rom/firmware from the images from romdump.
need it for my rk3188 tablet.
thanks
th3f33 said:
how to make a flashable rom/firmware from the images from romdump.
need it for my rk3188 tablet.
thanks
Click to expand...
Click to collapse
Depends
Whats The Main Device
Screen DPI
Kernel
Droid Version
Pranto Roy said:
Depends
Whats The Main Device
Screen DPI
Kernel
Droid Version
Click to expand...
Click to collapse
Device is:
Skyworth skypad x7010 , rk3188 quad, 2gb ram, 8gb storage
DPI - 160
Kernel - i dont know, still using the stock...
running on jellybean 4.1.1
th3f33 said:
Device is:
Skyworth skypad x7010 , rk3188 quad, 2gb ram, 8gb storage
DPI - 160
Kernel - i dont know, still using the stock...
running on jellybean 4.1.1
Click to expand...
Click to collapse
Is It The main device's or your's??
Pranto Roy said:
Is It The main device's or your's??
Click to expand...
Click to collapse
its mine,
i have stock images from rom dump
but it is soft bricked as of now.. due to some build.prop errors or maybe when i set the cpu minimum frequency state...
.
th3f33 said:
its mine,
i have stock images from rom dump
but it is soft bricked as of now.. due to some build.prop errors or maybe when i set the cpu minimum frequency state...
.
Click to expand...
Click to collapse
If Both Build.prop 's are of same droid version replace it with your phone's
cpu won't Matter
thanks for the replys
Pranto Roy said:
If Both Build.prop 's are of same droid version replace it with your phone's
cpu won't Matter
Click to expand...
Click to collapse
yeah i would really like to do that, to keep my save files in some rpgs i played, but i had this problem where i cant access the tablet thru adb, although i am rooted, usb debugging is on, and have installed the right / working/ correct adb drivers for my device although i was supposed to be able to do it before, i dunno what had happened to it,
maybe it happened somewhere during my initial setup of factory restore - root - clear bloat apps - clear cache - factory restore,
but i can access the tablet with adb when it is turned off, but even though i can access it with adb, cant seem to push any file anywhere, and cant use SU command, it just goes blank, and adb root / adb remount not working too, adb root says cannot run in production build and remount is not having permission.
i also checked the default.prop and it says
ro.secure=1
ro.debuggable= 1
when i check the adb devices when the tablet is off, it says
name - device
no access to recovery mode anymore, can only access the device in off state and flash state, (rkbatchtool flash state - green)
whenever i try to push the recovery button (Power + Volume Up, used to be working before i flashed the incorrect recovery) it ends up in the flash mode.
when the device is turned on and stuck in grey screen after logo, it can be detected in the windows as android adb interface but adb devices doesnt detect the tablet, even after i restart the adb thru adb kill-server adb start-srver
th3f33 said:
yeah i would really like to do that, to keep my save files in some rpgs i played, but i had this problem where i cant access the tablet thru adb, although i am rooted, usb debugging is on, and have installed the right / working/ correct adb drivers for my device although i was supposed to be able to do it before, i dunno what had happened to it,
maybe it happened somewhere during my initial setup of factory restore - root - clear bloat apps - clear cache - factory restore,
but i can access the tablet with adb when it is turned off, but even though i can access it with adb, cant seem to push any file anywhere, and cant use SU command, it just goes blank, and adb root / adb remount not working too, adb root says cannot run in production build and remount is not having permission.
i also checked the default.prop and it says
ro.secure=1
ro.debuggable= 1
when i check the adb devices when the tablet is off, it says
name - device
no access to recovery mode anymore, can only access the device in off state and flash state, (rkbatchtool flash state - green)
whenever i try to push the recovery button (Power + Volume Up, used to be working before i flashed the incorrect recovery) it ends up in the flash mode.
when the device is turned on and stuck in grey screen after logo, it can be detected in the windows as android adb interface but adb devices doesnt detect the tablet, even after i restart the adb thru adb kill-server adb start-srver
Click to expand...
Click to collapse
Complex Problems
Don't Think Can Be Solved At Home
Contact Customers Care
RE:
well i dont think i can do that because
skyworth is a chinese company, and they dont have a good support for the tablets they've released, i cant understand chinese/cantonese/mandarin too
in our local provider, i also have used the most of my warranty,
rooting/flashing the tablet voids the warranty
even though i had sucessfully made them replace my first tablet due to soft-bricking it, all i did is made the tablet bootable only to flashmode, and they didn't even understand/tracked what i had done, all they did was mark the device as faulty mobo then replaced it with a new one,
so right now i am asking for the online community in some help on how to restore it,
oh btw i have the stock romdump images of it. during the state where it is 100% working.
Pranto Roy said:
Complex Problems
Don't Think Can Be Solved At Home
Contact Customers Care
Click to expand...
Click to collapse
can you instruct me on how to make an update.zip that will replace the build.prop with my default build.prop from what ive learned, it is possible to make one right?
th3f33 said:
can you instruct me on how to make an update.zip that will replace the build.prop with my default build.prop from what ive learned, it is possible to make one right?
Click to expand...
Click to collapse
Possible But Can't Say If It Will Work.
Upload Your Build.prop
I'll Be Quite Late Though
Pranto Roy said:
Possible But Can't Say If It Will Work.
Upload Your Build.prop
I'll Be Quite Late Though
Click to expand...
Click to collapse
here it is.. oh i forgot to rename it to build.prop, it is a backup made weeks ago..
'well i've tried adding an update.zip and I dont think i can use it anyways, i think i need to find a way to flash the romdumps that i have.'
th3f33 said:
here it is.. oh i forgot to rename it to build.prop, it is a backup made weeks ago..
'well i've tried adding an update.zip and I dont think i can use it anyways, i think i need to find a way to flash the romdumps that i have.'
Click to expand...
Click to collapse
Allow Me 24 Hours
As Its Mid-Night In My Country I'll Do It Tomorrow
Pranto Roy said:
Allow Me 24 Hours
As Its Mid-Night In My Country I'll Do It Tomorrow
Click to expand...
Click to collapse
ok its already 2:51 am here, cant sleep without my tab running
still reading a lots of forum topics related to my problem...
RE:
I got my access back to the device thru adb
what i did was added the dev id of my device in the adb_usb.ini
now i can push files back to it
now i need to it to the working state
Does anyone have any information on how to root this phone?
It is a tracfone running Android 4.1 with 1ghz qualcomm cpu.
Thanks.
I'm also looking for someone who might have some pointers on how to root this phone or install KitKat apps from Nexus 5 dump!!!
I know it is a low end phone but there are lots of people in the Tracfone world who are now able to get Android phones and are NEW to the smartphone universe.
Thanks.
I'm thinking of buying this phone. As a low end Android, how does it hold up? And if you want to root it, try Bin4ry's root method here. Just be careful.
Tried Bin4ry on ZTE Valet but it failed to root
I've had the phone a couple of days so far and while I'm by no means a qualified reviewer of smartphones, I do like the ZTE Valet. I'm too cheap to pay the $70-100 USD/month for a post-paid service that I don't need.
After searching the forums and seeing that no one reported trying to root the phone, I took a brave pill and tried the Bin4ry method (v31). I got the same message that many users reported - after rebooting, it fails to mount and copy the necessary files. Both the new standard method and the old method failed. It did no apparent harm to the phone - just didn't work. Here's some details on the phone I have:
Android version 4.1.1
Kernel 3.4.0-perf [email protected]
Thanks for any ideas or advice.
I just picked one up at Kmart for $80 today and am checking things out, trying to see about rooting it. My Hisense Sero 7 Pro tab is rooted and running great with a DoPa custom ROM.
I also purchased one of these and am happy so far. I have a question on the magnetic and rotation sensor. They seem to show up as installed as ak8962 devices but apps like 'my android sensors' don't show any data being returned. are they just not actually installed?
thanks
sam
gberpa said:
I just picked one up at Kmart for $80 today and am checking things out, trying to see about rooting it. My Hisense Sero 7 Pro tab is rooted and running great with a DoPa custom ROM.
Click to expand...
Click to collapse
samcoinc said:
I also purchased one of these and am happy so far. I have a question on the magnetic and rotation sensor. They seem to show up as installed as ak8962 devices but apps like 'my android sensors' don't show any data being returned. are they just not actually installed?
thanks
sam
Click to expand...
Click to collapse
The rotation of the device changes the screen from portrait to landscape and 'maps', 'Gas Buddy' seems to show the right direction for magnetic north. I haven't had much time to check yet. AAMF, I haven't activated or transferred my number to the 'phone' yet as am deciding if is a 'keeper'. So far, I think it is as I can use WiFi and 'turn off' mobile data by option. Now checking things like battery life in standby.. Haven't found an option to shut WiFi when screen is off like in my JB 4.2.1 and HC 3.1 devices. Only seem to be able to turn WiFi on or off or see an option for airplane mode.
I agree - the screen rotates (how - I don't know ) I would assume gas buddy is using GPS to find north.
sam
gberpa said:
The rotation of the device changes the screen from portrait to landscape and 'maps', 'Gas Buddy' seems to show the right direction for magnetic north. I haven't had much time to check yet. AAMF, I haven't activated or transferred my number to the 'phone' yet as am deciding if is a 'keeper'. So far, I think it is as I can use WiFi and 'turn off' mobile data by option. Now checking things like battery life in standby.. Haven't found an option to shut WiFi when screen is off like in my JB 4.2.1 and HC 3.1 devices. Only seem to be able to turn WiFi on or off or see an option for airplane mode.
Click to expand...
Click to collapse
Any update on this?
It isn't looking good so far..
http://androidforums.com/zte-valet/799676-ill-help-find-root-method-if.html
They have tried a bunch of stuff so far.
sam
Unkn0wn0ne said:
Any update on this?
Click to expand...
Click to collapse
samcoinc said:
It isn't looking good so far..
They have tried a bunch of stuff so far.
sam
Click to expand...
Click to collapse
I'm going to get my hands on the phone soon. I'll proceed to attempt to get a recovery or something compiled for it if I can. First, I'd have to dump the rom and kernel which might require root access, but we will see. Once we have a recovery we can port CyanogenMod over to it.
Also I think I know why it's crashing, but I can't be sure until I can test it out myself.
Unkn0wn0ne said:
I'm going to get my hands on the phone soon. I'll proceed to attempt to get a recovery or something compiled for it if I can. First, I'd have to dump the rom and kernel which might require root access, but we will see. Once we have a recovery we can port CyanogenMod over to it.
Also I think I know why it's crashing, but I can't be sure until I can test it out myself.
Click to expand...
Click to collapse
Wish you luck..just got my replacement unit from TracFone after the first one's screen froze.
oooops. Sorry posted in wrong thread.
ZTE Valet Z665c - obtaining temporary root
After trying numerous root methods (Bin4ry, Framaroot, ...), I stumbled on a method of getting temporary root using Cydia Impactor. Cydia Impactor appears to be partially successful. First of all, please note that all credit goes to those involved with Cydia Impactor and the discovery of the original exploits (do a search if you want).
This method might seem a little convoluted, but it works reliably for me. Note that I use a Linux machine so you might have to adapt the steps to work on another platform.
Prerequisites:
1. Menu -> System settings -> Developer options -> USB debugging ->Enabled.
2. Menu -> System settings -> Developer options -> Stay awake ->Enabled (to keep the telnet session from going to sleep).
3. telnet (I am running on Ubuntu, but some sort of telnet program is needed).
4. Cydia Impactor
5. phone is connected to your wifi.
Steps:
1. Run the "Cydia Impactor" to "# drop SuperSU to /system/xbin/su". See what happens.
2. It failed for me giving an error related to not being able to remount /system or not being able to create /system/xbin/su.
3. In Cydia Impactor, run "# start telnetd as system on port 2222". You don't need to bother to telnet in. Just let it finish and then proceed to the next step.
4. In Cydia Impactor, run "# start telnetd as root on port 22". Let it finish.
5. Telnet into your phone from a terminal on your computer: "telnet 192.168.1.117 -l root 22". Note that the ip address is likely different on your network, e.g., 192.168.1.xxx.
6. If everything worked OK, you should be presented with a root prompt ("~ #"). I have busybox (obtained from the Bin4ry exploit download) that I adb pushed to /data/local/tmp. The command "/data/local/tmp/busybox whoami" tells me I am indeed root.
OK - now the bad news for me. I proceed to try to install su but remount fails. If I issue the command:
~ # mount -o rw,remount /system
~ #
A root prompt is returned with no error message suggesting that it successfully remounted /system. Woohoo! But a "mount" command (or cat /proc/mounts) says it is still "ro" or read only. Darn. Does it appear that ZTE has crippled the mount command in some way? Now the question is how to permanently install root? I have poked around and at least was able to make a backup to my sdcard using bzip2
This should at least help as a first step. Others including myself have posted elsewhere on this phone. At this point, I'm not willing to risk flashing anything. I'm a noob so I'm hoping someone who is more familiar with the permissions and that sort of thing can complete the root and post a solution.
Thanks.
Awesome!
These findings are great, I'd be willing to check this out soon. (Linux box is down do to hardware issue. ).
If we can obtain root the remounting issue can definitely be fixed. Also, does busybox have the premissions to run?
Try this:
Code:
mount | grep system
That will give you somewhere within the text the partition that is registered as /system . Then:
Code:
mount -o rw,remount [PARTITION-THAT-COMMAND-RETURNED-HERE-MINUS-BRACKETS] /system
See if that works. But anyways, if it doesn't it can still be rooted! (just temporarily, but it is no longer an 'unrootable' device)
Note: I am not responsible for what happens using those commands.
a little more info in response to your questions
Dear Unkn0wn0ne,
I had messed around with it and also tried something like you suggested, e.g.:
mount -o rw,remount,relatime,data=ordered -t ext4 /dev/block/mmcblk0p19 /system
Also tried it with the "-n" option to avoid a write to mtab although I don't remember seeing mtab while purusing the file system.
Hadn't noticed that busybox was available under /system/bin:
~ # ls -al /system/bin/busybox
-rwxr-xr-x 1 root shell 1075144 Jul 19 11:20 /system/bin/busybox
~ #
Could be that it has a more limited command set than the one I put in /data/local/tmp. A lot of the commands under /system/bin have a symbolic link to toolbox.
Note that the telnet connection needs to be made over wifi and not the one available over usb. I got the ip address from my router's client list.
Oh yes - thanks for the reminder. Forgot to include the disclaimer about harming the phone or voiding the warranty.
Hope it works out well for you. Glad to hear your encouraging remarks.
Awesome!
Alright so that didn't work. This guy over here has a suggestion (he has scene your thread): - I can't publish links so I'll pm the link to you.
Also if busybox is symbolically linked you'd have to tell it specifically to call to the busybox pushed over via adb to: /data/local/tmp/busybox and not the stock.
In this case: /data/loocal/tmp/busybox/mount
Also the disclaimer is a must. There will always be that person that tries to blame it on someone else.
Note: I am not responsible for whatever happens using the information provided in this post.
karmmisht said:
After trying numerous root methods (Bin4ry, Framaroot, ...), I stumbled on a method of getting temporary root using Cydia Impactor. Cydia Impactor appears to be partially successful. First of all, please note that all credit goes to those involved with Cydia Impactor and the discovery of the original exploits (do a search if you want).
This method might seem a little convoluted, but it works reliably for me. Note that I use a Linux machine so you might have to adapt the steps to work on another platform.
This should at least help as a first step. Others including myself have posted elsewhere on this phone. At this point, I'm not willing to risk flashing anything. I'm a noob so I'm hoping someone who is more familiar with the permissions and that sort of thing can complete the root and post a solution.
Thanks.
Click to expand...
Click to collapse
I attempted this myself on my Windows 8 machine. I had to enable telnet, but that was easy. I had to reararange the command to "telnet root 192.168.x.xxx:22" (xxx is my IP). It keeps giving me the error "Connect failed."
Any thoughts out there?
try putty
Ph0enix_216,
I tried to connect from a Windows 7 machine and it works using putty for telnet (www.putty.org, a great program). Be sure to set the Connection->Data->Auto-login name to root.
well the guy in the other thread bricked his it sounds like...
http://androidforums.com/zte-valet/799676-ill-help-find-root-method-if-3.html
They tried to modify the mmcblk0p16 boot image and re-copy it back. It seemed to re-copy but then didn't boot with a verify error.. (I am paraphrasing - and don't really understand what they where doing )
sam
Ph0enix_216 said:
I attempted this myself on my Windows 8 machine. I had to enable telnet, but that was easy. I had to reararange the command to "telnet root 192.168.x.xxx:22" (xxx is my IP). It keeps giving me the error "Connect failed."
Any thoughts out there?
Click to expand...
Click to collapse
PreambleI oft find in various forums that people are so filled with the milk of human kindness that they just can't wait to help, ( or may gain a few more badges~) ignoring everything but the heading.
And in doing so ask foolish questions.
So, please DO READ to the end.
UPDATE
Thanks to @ jwoegerbauer I now know I can't install the Lantern APK via recovery. I must use ADB which I have previously tried but failed.
Obviously, therefore I do not know what I am doing with ADB.
My tasks focus now is to install Lantern APK via ADB with the devices , tools and systems already mentioned. (below)
Unless someone, somewhere knows where I can find a Lantern ZIP file which I can flash. (seems I am good at that now at least~)
Please DO read everything below ladies and gents, my sense of humour and patience does have a limit~
Mobile Device DetailsSamsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in briefTo install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?During one of my many attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
I am happy with that, seems no big deal for me, I was able to successfully install the new OS + Gapps. And it is one less APP to install
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!
thebic said:
Mobile Device DetailsSamsung note 3 originally 9006 Chinese ROM
Rooted via Odin to 9005
Upgraded to Lineage ROM 18
Uploaded pico Gapps
Uploaded Magisk v23
Desktop Machine
Asus P5BSE / Core2 Duo E4400 @ 2.00GHz / 4GB ram / 2TB storage / Linix; Zorin Core 15.3
Project in briefTo install Lantern. (getlantern.org)
Lantern is usually installed via Google play store.
Google is blocked in China.
Downloaded Lantern APK to upload to phone via recovery from SD card.
Recovery does not show the APK in the SD card.
Stuck.
Further info - useful?During one of my attempts to install Lineage following a blog, I wiped the disk in error.
I also suspect I removed the backup of the original Samsung system as when I tried to reboot, TWRP mentioned there was no O/S.
Nothing I could do restored the original.
What was it Macbeth said about being in blood stepped so far?
On my final install of Lineage 18 I seem now to have their Recovery, not TWRP.
Seems no big deal for me, I was able to successfully install the new OS + Gapps.
I also have Magisk installed, the device is in dev mode and - seemingly rooted. (although the App does not explicitly say so)
Using a borrowed SIM card I can connect to the China mobile network system.
I now have a fully functional, working , English language device with Lineage 18.
Brilliant!
My last task is to figure out how to get the Lantern App sorted.
I have downloaded the APK from their official site, several others as well as a supposedly zip file.
Saved to SD card, visible when viewed on Linux, invisible when card is installed in mobile.
I really do not know quite how to proceed from here.
If I have missed anything, sorry, please ask.
Huge thanks to RAIZ from this forum for getting me to this stage and the guys who made Lineage 18 so darn easy to install and seemingly impossible to mess up.
And boy oh boy, believe me, I have really tried over the past few months~!
Click to expand...
Click to collapse
What recovery are you using? Have you tried different recoveries?
What version of twrp are you running?
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
Yeah you could use adb sideload in twrp.
jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Click to expand...
Click to collapse
Hehe, I can verify your first statement!
Do you have a link you can direct me to please as to how to do it via ADB in Lineage recovery as I did try that (side loading) via TWRP and it threw back an error. I can't recall but I think it was permissions or similar?
Sorry, I forgot to mention that in my post.
Thx for your constructive feedback - much appreciated.
P
Re-read my cited post: I've edited it.
jwoegerbauer said:
An APK will never get installed via Recovery.
You typically install an APK ( sideload method ) by means of ADB.
Code:
adb devices
adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
Click to expand...
Click to collapse
Ohhhhh Kayyyyyy - coping.
Just.
You have added code?
Before I go ahead and destroy New York, I use that where?
How?
and errr... why?
I am guessing in Terminal, but I am not really sure what I am trying to achieve here.
Sorry, not arguing or being difficult, I just find it helps me if I know what EXPECTED outcomes are. Just in case it isn't what I should expect. :>(
Thx for your patience.
p
I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.
jwoegerbauer said:
I think the understandable answer is given here:
adb install - Android ADB Shell Commands Manual
adbshell.com
Of course it's required ADB got installed on Windows computer if not done yet: if not then you may use the installer script linked to in my signature.
Click to expand...
Click to collapse
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.
thebic said:
Thx not so helpful.
I've edited my post with a preamble, please check it when you have time.
Have a nice weekend.
Click to expand...
Click to collapse
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$
I seem to be going in ever decreasing circles.
Please help me out- what is protocol.
Do I keep updating my progress - or lack of- here, in this dialogue, or should I continue to update my original post?
Which one best communicates to everyone where I am at?
Cheers
thebic said:
[email protected]:~$ adb install test.apk
can't find 'test.apk' to install
[email protected]:~$
Click to expand...
Click to collapse
You forgot to add the exact file directory.
Keno_I said:
You forgot to add the exact file directory.
Click to expand...
Click to collapse
Did it work after adding the file directory?
You are right.
I am not sure how this forum works, so it was more of a post to jwoegerbauer.
Anyway, even opening the folder with terminal and using adb install lantern-installer failed with a CLOSE error message. I guess that meant close as in shut not closes as in almost!
I can, using Lineageos recovery access ADP on my phone with the instruction: " now send the package you want to apply to the device with "adb sideload <filename>"
However that triggers a screed of data in terminal which, frankly, is well beyond my rudimentary level of comprehension.
I have tried following 3 other on line tuts which suggest using ADB on my computer. All goes well until the instruction: <adb devices> which returns:
$ adb devices
List of devices attached
In other words, computer can't find phone!
I initially tried it in DOWLOAD mode, with the usual "download in progress, do not disconnect source."
Then reading the tuts again, none mentioned download mode so I tried with just the device attached to the machine in normal phone usage mode. Checked that SAMSUNG was visible and I could open the folders but again failed. ( sorry I forget what that error message was)
So far the most positive has been the direct ADB via Lineageos, but I have no idea where to go from there.
It is knocking on 37* here, too hot to think so I am taking a break.
Thx for your latest efforts.
Cheers
P
OK Finally!
[email protected]:~$ adb devices
List of devices attached
438f904d device
[email protected]:~$ adb install /home/bicyu/Sam-upgrade/lantern-installer/lantern-installer.apk
Performing Streamed Install
Success
[email protected]:~$
I have read so many posts all end with the <adb devices> and on each one I see zilch.
So, for anyone else in this boat, here is my solution.
In developer OPTIONS on your LINEAGEos device scroll down to
DEFAULT USB CONFIGURATIONVery likely it is set to FILE TRANSFER - mine was.
Change it to USB TETHERING
Then enter < adb devices> in terminal.
You should then see your Android listed.
Proceed with: adb install <FULL-PATHNAME-OF-APK-ON-PC-HERE>
You should see a SUCCESS flag!
NOTES: This works in Lineageos ROM on Linux, ( Ubuntu / Zorin O/S)
I dunno about others.
You need to have dev options activated.
Change the USB setting back when done, otherwise it tends to mess up your Internet! (did mine anyway!)
This is the best background tut to ADB I found.
He talks about a USB3 bug which, apparently, creates the same problem - maybe THAT is your issue? It was that article which put me on the USB CONFIG train.
Hope this helps someone.
A REALLY HUGE thank you to jwoegerbauer for putting me
on the right track - wrong train, - but right track.
Cheers mate!
Glad to hear you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.
Yep! Well good luck
jwoegerbauer said:
Glad to here you solved it.
Only to have mentioned it, there is a workaround - as always because many ways leads to Rome:
Copy the APK of interest onto MicroSD-card, plug the card into phone, afterwards using any File Manager application that is installed on phone, navigate to the location on MicroSD where the APK file is located and finally double-click on the APK file: this will install the APK.
Click to expand...
Click to collapse
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p
thebic said:
NOW he tells me!
That was where I began 2+ weeks back, downloading to SD card and trying to find a way inside the phone to do it. Never thought of File Manager! Duh~
Take care buddy, enjoy your weekend, wherever you are.
p
Click to expand...
Click to collapse
Aroma File Manager, how nostalgic~
Now to wait till a mod closes this post