Related
The dalvik bug console refuses connection with only this certain ROM in my sig. "Connection refused by the remote host". I have a backup of my last CoreDroid flash, and it connects as expected (I have it restored to the handset now, and am watching the log scroll away on the console). I installed adb and the dalvik console back when I was stock to use for screen shots. I have never had any issue with it. I have installed all the drivers that I believe are required, and have connected to adb with 3 other ROM's with absolutely no issue. So I have to believe this is nothing I have done.
So the question is, what attribute vs. a specific ROM would cause connection refusal to adb? Thank you.
meiguoguizi said:
The dalvik bug console refuses connection with only this certain ROM in my sig. "Connection refused by the remote host". I have a backup of my last CoreDroid flash, and it connects as expected (I have it restored to the handset now, and am watching the log scroll away on the console). I installed adb and the dalvik console back when I was stock to use for screen shots. I have never had any issue with it. I have installed all the drivers that I believe are required, and have connected to adb with 3 other ROM's with absolutely no issue. So I have to believe this is nothing I have done.
So the question is, what attribute vs. a specific ROM would cause connection refusal to adb? Thank you.
Click to expand...
Click to collapse
Make sure debugging is turned on
zelendel said:
Make sure debugging is turned on
Click to expand...
Click to collapse
Yes debugging is confirmed on. I have never had a problem in two months using adb. In this case it is a difference between two ROM's. I can restore CoreDroid v7 and connect as expected. On the ROM in my sig I cannot. I have restored them back to back and connection problem is only with this ROM.
I did find this thread on XDA where someone had a similar issue:
http://forum.xda-developers.com/showthread.php?t=647991&page=3
The fixed for this thread was to un-install and re-install HTC Sync.
Originally Posted by ccapasso
I have win 7 64 and here is what worked for me:
1. Uninstall HTC Driver (this will likely give you an error, you can ignore it)
2. Uninstall HTC Sync
3. Download and install PdaNet
4. Follow the directions when installing PdaNet
The end.
This worked for me. I just wish I found this thread earlier (didn't seem quite as easy to find as I would've thought). Thank you. Thank you. Thank you.
I'm going to try this later. I don't fully understand that while I have the latest drivers for adb, one ROM will connect and one will not...that is sort of what I am looking for, a more technical explanation as to why this would be so. Thanks.
The adb daemon (adbd) is run from the init.rc script. Perhaps it was left out of your ROM (I don't know which one because I have sigs turned off in my profile). This is part of the boot.img so if your using a different kernel, it may have issues with finding the adbd program.
Gene Poole said:
The adb daemon (adbd) is run from the init.rc script. Perhaps it was left out of your ROM (I don't know which one because I have sigs turned off in my profile). This is part of the boot.img so if your using a different kernel, it may have issues with finding the adbd program.
Click to expand...
Click to collapse
Thanks Gene Poole! This is exactly the type of information I was looking for. Another user that has this version of ROM confirmed the same issue on this ROM's thread. So the devs will know about it anyways. They have a place to post bugs on their website, but I kind of want to exhaust options before posting there. Here are my device stats:
[DEVICE] HTC Inspire "4G"
[NETWORK] AT&T 3.5G
[HOME LOCATION] Portland, OR USA
[ROM] Virtuous Unity v1.25.0
[RADIO] 12.39a.60.19U_26.06.06.30_M
[KERNEL] Unity V1
Unity V1 is the kernel that is packaged with the ROM. I could try Unity V2 as a kernel option. I will try this first, and if it doesn't work, try the method in the other thread of wiping and re-installing HTC sync and PdaNet. I'm a noob, but HTC sync has also been finicky with my Sense ROM setups as usually the only major functionality issue. Thanks again! You are always very helpful with your posts.
[Fixed]
Un-installing and re=installing the entire Android-sdk rectified the issues for this ROM. Why other ROM's would connect and Virtuous wouldn't with the previous install is unknown.
So I have a GB 2.3.6 SGS4G but I tried to flash something before that set it into a bootloop and I've been using http://forum.xda-developers.com/showthread.php?t=1822626. (Also just a side note- the above mentioned rom doesn't give root)
But that Rom changed my Kernal to the blastoffv2 kernel from here http://forum.xda-developers.com/showthread.php?t=1828171. Now my problem with this is this kernel doesn't support wifi unless I do
Your rom also must change to use wifi.
You will need to update /system/etc/wifi/wifi.conf, and replace anything that says 'dhd' with 'bcm4329'
Also the module path is: /lib/modules
instead of /system/lib/modules
Click to expand...
Click to collapse
Now I'm a newbie so I don't know how to update that whether I have to navigate through my phone with RootExplorer or what. Exactly how do i replace it?
I would flash another kernel but my SD card is malfunctioning and the phone reads it and can access it, but whenever I try to make changes on it by connecting it to the computer, it doesn't save the changes even though I safely remove everything.** (Most urgent please help!) So I can't use CWM_blue (5.xx) to flash it even if I have CWM.
Also I've spent the last 3 days with almost no sleep just trying to understand Android so please be kind and very specific :crying::crying:
Oh I forgot-- the problem with Odin to flash a new kernel is that Odin doesn't recognize my phone when I plug it in. I've tried using zadig to update my drivers after I plugged it in (download mode + usb debug). I've also tried switching the ports but it still doesn't work. I've tried with Odin 1.7 and Odin 1.85, any suggestions? Do I need a pit file for my phone? Do I require bootloaders for it do work? I'm trying to flash http://forum.xda-developers.com/showthread.php?t=1610528 and then going over to CM9.
I'll be kind
Don't whine
Describe with words, back up with a link. I don't want to have to click three things to figure out what you did
You shouldn't be flashing anything without backing up
You can transfer using adb to your phone. You do have it and Heimdall already installed, right?
"I tried to flash something before that set it into a bootloop" isn't terribly helpful. What ROM are you on now?
Without root, you're not going to be able to remount /system to change anything
Did you read, in big letters, in the post you linked, right in the first paragraph, "This [ROM] targeted towards people that need to go from ICS to stock"
Edit -- Anyone who posts not three, but in six threads on the same problem is beyond me.
Edit -- Copying the search request, http://forum.xda-developers.com/search.php?do=finduser&u=4495723, provides the desired search results, rather than copying the URL from the search results.
This is your third thread on the same issue!
sent from me
itzik2sh said:
This is your third thread on the same issue!
Click to expand...
Click to collapse
you get a big THANKS!
six threads on one issues is desperation, why not just lead the man by the hand? less clutter on your forums
first you need to understand that odin and heimdall use different drivers, odin uses default drivers, heimdall uses open source drivers. EX:
if you have heimdall drivers installed on the USB port you connected your phone to and you're trying to flash w/ odin, it will fail to communicate w/ the phone.
a great suggestion made, was use two different ports, one for heimdall, one for odin, so that a driver switch is not necessary. remember to use your motherboard usb ports, and not from a usb extension.
http://forum.xda-developers.com/showthread.php?t=1936294
post #4, by me, goes over my PERSONAL flashing procedure, i hope it helps
http://forum.xda-developers.com/showthread.php?t=1669364
may i also suggest AntonX's Barebone KJ6, it also comes w/ his kernel, which is 2.3.6 - rooted, UV/OC, voodoo sound, BLN(google the acronyms)to flash this as is, you need to have rooted CWM. May i suggest gremlin remover first? ^first link
http://forum.xda-developers.com/showthread.php?t=1828171
blastoffv2 is a great kernel, i edited my wifi file w/ script manager(google play), which requires root to edit, you must also change the permissions on the folder that contains the file before editing. edit the file, save it, and then return the folder permission settings to default manually.(long press folder in your-choice-root-file-manager, properties, change permissions)
xakuvo said:
why not just lead the man by the hand? less clutter on your forums
Click to expand...
Click to collapse
Because the information has already been provided in the other five threads, if you had read them. He already has been led by the hand. You made suggestions without knowing what had already been suggested, potentially counter to a path he might have successfully been on. More clutter in the threads.
Please let this thread die and direct any responses to one of the previous five threads.
jeffsf said:
Edit -- Anyone who posts not three, but in six threads on the same problem is beyond me.
Click to expand...
Click to collapse
Just for future reference jeff. XDA won't let you link to search results. I'm assuming that's what your "six threads" link was too. This is a new record for sure. I wish the OP luck in fixing this cause if you gotta ask that many times luck is what you'll need.
So I rooted my phone for the first time via Odin. And it worked -- after that, I tried to install a custom ROM (slim bean) -- I ended up uploading the non zipped version on my SD card. And I went through all the steps to install up until "format/system" to realize that I didn't have the zipped files.
Now my phone is stuck on the Samsung Icon. I just tried to use Odin to flash the stock gingerbread again, but there it gets stuck on "Setup Connection".
Please help! Total newb at this, and clearly it failed.
---
My phone wouldn't turn off even with Odin closing, so I took out the battery -- so now my startup screen is
"Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
How do I fix this?
That is kind of a secondary download mode.. odin or heimdall should detect your phone.
Make sure you have a good usb cable and maybe try switching usb ports.
Sent from my SGH-I997 using xda app-developers app
Right. To add to andros11's post, was the top left box yellow in Odin before you clicked start? Odin will acknowledge that your phone is connected immediately (the box should be yellow if you your phone is connected properly). Of course, make sure you have all of the appropriate drivers (i.e. download Kies for the Infuse).
Also, for future reference, I have a fix for situations like yours so you don't have to go back to stock. Basically, you can use adb to push the correct zip file to your sdcard. What you do is:
Download and install the Android SDK: http://developer.android.com/sdk/index.html
Make sure to install platform tools (a separate download from within SDK)
In Mac and Linux, open up Terminal. I can't remember how Windows works, sorry! Navigate to wherever the platform tools folder is. You have to do this using command line, so, cd <the/path/to/your/folder> (the easiest way is to just type cd, hit the space bar and then drag the folder to the Terminal window).
Once there, connect your phone to your computer. It can be in CWM or Download mode
Type in Terminal: adb devices
The next line - the response - should tell you if your phone is recognized. If it's blank, try again. If it's still blank, you might try disconnecting usb phone cable and reconnecting again. You might also try going into download mode.
Okay. Next type: adb push <here, just drag the zip file to your terminal window> /sdcard/
Give it time to push the file to the sd card. Repeat if necessary (if you have more than one zip)
Exit terminal, disconnect phone from computer, go back into recovery, navigate to the sdcard to flash and lo and behold! The proper zip file is there for you!
This might sound long, but it's so easy. Getting SDK set up is probably the biggest pain and it's not really that much of a pain!
You may want to give Heimdall a try rather than Odin.
Put the phone into download mode and try this:
http://forum.xda-developers.com/showthread.php?t=1331381
Thanks so much everyone. Seriously.
So, Whizzpopper -- I *think* I installed SDK, but since my phone still says, "Firmware upgrade encountered issue. Please select Recovery mode in Kies and try again." I tried connecting it to Kies -- and it says "connecting" but never connects.
And even if I try the key combo to get to Download Mode or Recovery, it never gets away from that Firmware message.
How can I just get out of that mode?
how to keep fb sync on custom rom?
Hi I am a fairly new member, I have been following different threads for a long time but have recently signed up, so if i am posting in the wrong thread I sincerely apologize. moving on...
I have been using the Aeon 1.4 rom for awhile now and have been loving it. I first downloaded the rom without the stock libs and found that it is much faster than the stock libs rom, even after manually removing most of my stock apps via sd maid pro. But it has been the only way to keep the option to share with FaceBook. and being able to add facebook in my accounts and sync are in system settings. system settings>accounts and sync>add account.
You won't be able to get out of there until you are able to flash with either odin or heimdall.
You may also try a tool called one-click unbrick (google it)
Sent from my SGH-I997 using xda app-developers app
andros11 said:
You won't be able to get out of there until you are able to flash with either odin or heimdall.
You may also try a tool called one-click unbrick (google it)
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
ONE CLICK UNBRICK HAS GOTTEN ME OUT OF THAT GODFORSAKEN FIRMWARE MESSAGE.
Thank. You. So. Much.
... Now to follow the rest of the steps to try and get it back to some sort of operating phone!
and please note that it would be best to uninstall kies- it has been a source of problems for a countless number of users.
Thank you so much for your help!
So the terminal adb push worked -- and I installed my ROM (went through all the installation wizard parts, etc.) but now at reboot, I'm still stuck at the Samsung logo.
What happened?
@andros11 -- I saw your comment on how to best get from GB to JB
http://www.android.gs/install-unoff...pdate-to-ice-cream-sandwich-4-0-3-custom-rom/
I tried to follow those instructions to install ICS first, (I was previously too eager and went straight to JB!) and still I'm stuck at the Samsung screen.
Anybody have any threads, recos to get my phone to bootup to any system?
Sorry for the newbness!
Enter download mode to Go back to stock gb and then work your way up again up to jb.
Sent from my SGH-I997 using xda app-developers app
To add to that, use qkster's link to get back to stock.
http://forum.xda-developers.com/showthread.php?p=23118134
Sent from my SGH-I997 using xda premium
Okay so I tried the Heimdall One Click Stock --
unfortunately, it stops working at the "clearing interface" stage -- says it failed. And I've changed the cables but still the same result.
You are on the right track... just that something is missing.
Be sure to get rid of kies.
Be sure you have the latest version of Java. http://www.java.com/en/
Use the link in post 13 that psal gave you - read at least posts 1 and 2 all the way through, then go through and perform each step.
The first time is a process, after that it is quick and easy. Thanks to qkster. :good:
Here is an award winning-less video of the process that you might want to watch as you may see a step in the video that you are missing. Hope this helps.
http://www.youtube.com/watch?v=sHyY7WHx4zc
Nothing in this world can take the place of persistence. Talent will not; nothing is more common than unsuccessful people with talent. Genius will not; unrewarded genius is almost a proverb. Education will not; the world is full of educated failures. Persistence and determination alone are omnipotent.
Calvin Coolidge
Hello -
I have done weeks worth of research in my spare time before finally caving in and asking for help. I believe my situation irritatingly enough is different than typical no os corrupt sd card issues and I have not been able to find a solution here or on the www unless I am forgetting something simple. Here's why:
I am S-Off
I have super cid
I have access to bootloader
I have access to recovery which is TWRP 2.3.1 and I can access terminal command
My card WONT MOUNT (meaning no fixing permissions, no wiping external sdcard or side loading)
If I reboot system, it freezes at the initial boot screen image with the Viper logo and the red developer caution statement below it
Fastboot and ADB do not recognize my phone and I have used every one click, script, and trick on this website and others using different drivers, Android SDK and all the different drivers I can find. No Dice.
I DO HAVE AN HTC EVO 4G LTE that I htc dev unlocked, s-off, supercid etc on this very laptop (Windows 7) this week so I have a pretty good idea what what doesn't work in terms of drivers/scripts with my current laptop configuration.
I have used Ubuntu as an installed desktop and as a live cd. This is as close as I have been to having my phone recognized in adb or fastboot. I was using the SD FIX see here http://forum.xda-developers.com/showthread.php?t=1942519 (What I don't get is why that thread was closed. Makes no sense to me that since a particular version of TWRP becomes available, that it would render that fix obsolete when its obvious how many scenarios can come up in particular with these HTC One Xs and not everyone is going to have a specific version of recovery. Anyway... this brings me to Ubuntu. And this is as close as I have been to success with getting back into my sdcard so I can command prompt/flash my way outta this mess. It was the only version of the SD fix I could find which of course was for Mac, Linux or Ubuntu. In terminal when the script would initialize it comes back as "Fastboot: Permissions Denied" or something to that effect. That was last night.. or errr.. this morning and I'm determined to do this.
Has anyone heard anything about a way to create a virtual sd card using AVD in an old version of the SDK? From what I can see it looks fairly simple. What I have dug up sounds easy enough but not sure why I haven't come across it here or anywhere else or nobody else has mentioned it? However, I am not a dev and perhaps it being a couple years old, counter measures have been put in place by these phone companies... lol we'll see... Thank you so much for your time.
I have attached a snap shot of my bootloader screen. Yes, I know the screen is cracked lol
The thread you linked to isn't closed, and if you visit the website the page is still up and running. The only problem I can see with that method is that you need to have fastboot working. Unfortunately the only other option I can think of needs fastboot working too, that is to flash TWRP 2.6 and use the advanced wipe feature to wipe/fix your corrupted sd card.
Have you uninstalled HTC drivers and then installed the latest drivers (4.10.xxxx I think)? Have you made sure your version of adb/fastboot is the latest?
Sent from my Evita
timmaaa said:
The thread you linked to isn't closed, and if you visit the website the page is still up and running. The only problem I can see with that method is that you need to have fastboot working. Unfortunately the only other option I can think of needs fastboot working too, that is to flash TWRP 2.6 and use the advanced wipe feature to wipe/fix your corrupted sd card.
Have you uninstalled HTC drivers and then installed the latest drivers (4.10.xxxx I think)? Have you made sure your version of adb/fastboot is the latest?
Sent from my Evita
Click to expand...
Click to collapse
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.
bportega said:
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.
Click to expand...
Click to collapse
Have you tried mounting the sd card in windows through twrp? If it's corrupted windows will pop up a box to format card. Do that. Then the sd card should work fine. Won't fix adb fastboot issues but it's one less problem to contend with
Sent from my iPhone using Tapatalk
bportega said:
Thought the thread was closed after the last comment on there. But yes you are correct regarding the website. That is how I was able to obtain the SD Fix I have now... although it is for Linux and isn't the one that was initially created for PC. The link to the Fix for PC is dead. However, I did just find a list of HTC drivers on XDA that could probably help a lot of peeps lol. Hopefully me! Here's that link: http://forums.team-nocturnal.com/in...le-internal-storage-on-the-htc-one-xxl/page-2
I'm going to uninstall current drivers again and start tinkering with these now. I sure wish I had TWRP 2.6 installed though. I will also double check the ADB and Fastboot drivers are the latest as well and get back to you on any changes. Thanks again.
Click to expand...
Click to collapse
How did you wipe your sd card to begin with? If you wiped it in the bootloader with the factory restore option then this will currupt your sd and the only option is to connect to your pc or computer and under my computer right click the drive of your phone and format the sd card that way and this will restore your sd card to working order but you must have all the right drivers installed for your phone. Which installing HTC sync will install all the right drivers
Sent from my HTC One XL using xda app-developers app
I had the same problem with my HTC ONE XL Evita with Hboot 1.14 S-ON Unlocked. Here are the steps I took to fix it - hope it helps (I run from a mac, so that's why the fastboot code looks the way it does)
I updated to TWRP 2.6.3.0 via Fastboot USB
./fastboot.osx flash recovery openrecovery-twrp-2.6.3.0-evita.img
I also extracted the Boot.img from CleanROM 6.5 and installed via Fastboot USB
./fastboot.osx flash boot boot.img
I then rebooted into TWRP recovery
Went to advanced wipe
wiped elements (cache / data / etc) independently
then performed factory reset
I was then able to mount to the iMac
Transferred CleanROM 6.5 in the TWRP folder
Was able to flash the ROM via TWRP
31ken31 said:
Have you tried mounting the sd card in windows through twrp? If it's corrupted windows will pop up a box to format card. Do that. Then the sd card should work fine. Won't fix adb fastboot issues but it's one less problem to contend with
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
If you mean literally plugging my phone into my pc...going into device manager, seeing if the sdcard is being picked up.. of course I have. I can freely go between recovery TWRP 2.3.1.0.0. and bootloader and I can even boot the system even tho there isn't an OS and get as far as the VIPER logo with the developers text below it in red. I have both windows and Ubuntu and I have tried everything. I have gone into what files and folders I do have on the phone and using terminal in recovery I have found all the proc contents in tact.. all the dev contents in tact and sub folders... all the usb folders and contents I believe are still there too. Including fastboot. HOWEVER, after days of trying every adb usb driver combination imaginable... including editing .inf files, and taking signature verification off win 7.. I still can't get my phone to be picked up when i plug it in. Every once in a while I will get the bell sound when I plug it in to a usb port but when I look in device manager nothing...but when I plug my evo 4g lte in its whamo... ding ding and no issues. As far as this phone goes...I see all the files and folders there but even even ran htc drivers in compatability mode with XP... nothing.
I am learning how to create virtual sdcard images and how I can potentially be able to attach it to a devices sdcard giving one the ability to transfer or delete files which could help some folks get back into their devices...Also, here is a really cool idea although still in its infancy and how you can mount an sdcard as an mtp device using a fuse filesystem based on libusb. https://github.com/hanwen/go-mtpfs So at this point there are options out there but only pretty heavy manipulation of data and extentions and stuff over my head lol..
dtonshel said:
I had the same problem with my HTC ONE XL Evita with Hboot 1.14 S-ON Unlocked. Here are the steps I took to fix it - hope it helps (I run from a mac, so that's why the fastboot code looks the way it does)
I updated to TWRP 2.6.3.0 via Fastboot USB
./fastboot.osx flash recovery openrecovery-twrp-2.6.3.0-evita.img
I also extracted the Boot.img from CleanROM 6.5 and installed via Fastboot USB
./fastboot.osx flash boot boot.img
I then rebooted into TWRP recovery
Went to advanced wipe
wiped elements (cache / data / etc) independently
then performed factory reset
I was then able to mount to the iMac
Transferred CleanROM 6.5 in the TWRP folder
Was able to flash the ROM via TWRP
Click to expand...
Click to collapse
Hey thanks. Yup. This is exactly what I need to do. It's just that last time I tried to run the sdfix script in terminal using ubuntu i ran into a permissions issue. fastboot-permission denied or something to that nature. Do you know what that means? Thanks tho I will give this a shot.
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