As the title suggests - everytime i try to connect my SG6 int to my linux pc i keep getting a .lib error - this has sporadically occured, never had it before - i can sometimes open the phone on the pc - but trying to ...copy,paste, or even delete items from phone results in this error - help needed....thanks upfront
Related
HI. Please help me! I wasn't able to modify an article on the WIKI (wiki.xda-developers.com).
All the time I press the "Edit" Button, FireFox give me the option to download the php file :?: :?: :shock: WEIRD
The address I was modifying was:
http://wiki.xda-developers.com/index.php?pagename=List of HimaUpgradeUt.exe Error Code
After trying it several times, I could get inside and edit the page, then I saved it, and now is BLANK!!!!
HEEEEELLPPPP
The contets of the page at the time of my edit were:
--------------------------
ERROR 100: MODEL ID ERROR
Definition: ROM image is not design for the device you are upgrading. It happens when you try to use Himalaya's ROM image into other HTC like MAGICIAN, BlueAngel or Alpine
Solution: Use appropriate ROM Upgrade image for your Device, no two device can share the same ROM
ERROR 101: CONNECTION ERROR
ERROR 102: CE IMAGE FILE CHECKSUM ERROR
ERROR 103: ROM IMAGE FILE NOT FOUND
ERROR 104: CANNOT OPEN ROM IMAGE FILE
ERROR 105: OPEN PORT FAILURE
ERROR 106: EXECUTE REMOTE COMMUNICATION PROGRAM FAILURE
WARNING 111: POWER ADAPTER NOT PLUGGED IN
ERROR 112: CE ROM UPDATE ERROR
ERROR 113: EXTENDED ROM UPDATE ERROR
ERROR 114: RADIO ROM UPDATE ERROR
ERROR 115: INVALID VERSION OF ACTIVESYNC
ERROR:116 GENERAL ERROR
ERROR 117: INVALID MODEL ID
ERROR 120: COUNTRY ID ERROR
ERROR 121: LANGUAGE ID ERROR
ERROR 122: EXTENDED IMAGE FILE CHECKSUM ERROR
ERROR 123: RADIO IMAGE FILE CHECKSUM ERROR
ERROR 130: CREATE CE ROM IMAGE ERROR
ERROR 131: ALLOCATE MEMORY ERROR
ERROR 132: WRITE DATA ERROR
ERROR 133: COMMUNICATION ERROR
ERROR 134: READ CE ROM IMAGE ERROR
ERROR 135: COMMUNICATION ERROR
ERROR 136: COMMUNICATION INTERRUPT
ERROR 137: COMMUNICATION ERROR
ERROR 150: ROM UPGRADE UTILITY ERROR
ERROR 200: WRITE EXTENDED ROM FAIL
Error 201: GET DEVICE DATA ERROR
This error is a bit misleading. The BAUpdate tool is trying to switch the phone into bootloader mode, and the phone for some reason is being uncooperative. This happens to me from time to time. The best, and quickest way around this is to force the phone into Bootloader manually. By pressing the record button, while doing a hard reset (Power + Reset) your phone will enter bootloader mode. You can verify this as the screen will say, Serial, and change to USB when you cradle it.
Once you cradle your phone, Windows will detect it as new hardware, and take a minute or two configure the right driver(Microsoft USB Sync). Once this is complete, you can run the BAUpgrade utility again, and this time you should get past error 201.
Error 202: READ IMAGE ERROR
ERROR 210: CREATE EXTENDED ROM IMAGE ERROR
ERROR 211: ALLOCATE MEMORY ERROR
ERROR 212: WRITE DATA ERROR
ERROR 213: COMMUNICATION ERROR
ERROR 214: READ EXTENDED ROM IMAGE ERROR
ERROR 215 COMMUNICATION ERROR
ERROR 216: COMMUNICATION INTERRUPT
ERROR 310: CREATE RADIO ROM IMAGE ERROR
ERROR 311: ALLOCATE MEMORY ERROR
ERROR 312: WRITE DATA ERROR
ERROR 313: COMMUNICATION ERROR
ERROR 314: READ RADIO ROM IMAGE ERROR
ERROR 315: COMMUNICATION ERROR
ERROR 316: COMMUNICATION INTERRUPT
ERROR 317: COMMUNICATION ERROR
Hi,
I tried it too & have simular probs in changing any wiki page @ the moment. IMHO there's something wrong on the serverside cause the text is still present but compilation into a page fails.
Try again later is my suggestion.
Cheers, M
Yup, I thought it was a temporary problem. Moreover, I'm having the same strange behaviour in some wiki links.
For instance:
http://wiki.xda-developers.com/index.php?pagename=BA_Versions
It is the first link on this page:
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Radio
Thanks for your answer. I'll try later........
oltp said:
Hi,
I tried it too & have simular probs in changing any wiki page @ the moment. IMHO there's something wrong on the serverside cause the text is still present but compilation into a page fails.
Try again later is my suggestion.
Cheers, M
Click to expand...
Click to collapse
If the problem persists you can always pm 'peter poelman' or another moderator, maybe they can fix it.
The way it is now, we'll have a very empty wiki soon. Luckily the preview shows the same errors & peolpe should be warned by that, so as long as people don't save any changes to a page...
Luckily, I think you can allways get an older version of the page.
Cheers
oltp said:
If the problem persists you can always pm 'peter poelman' or another moderator, maybe they can fix it.
The way it is now, we'll have a very empty wiki soon. Luckily the preview shows the same errors & peolpe should be warned by that, so as long as people don't save any changes to a page...
Click to expand...
Click to collapse
arieltools said:
Luckily, I think you can allways get an older version of the page.
Click to expand...
Click to collapse
Ok learned something again, I didn't know that.
Good afternoon. I've installed two different programs and after installation, trying to run them i get error messages, as follow :
1) Program EventCountdownV2.2.exe. After installation (either in device, or
storage card), when i run the program i get this error message :
There is an unexpected error in application EventCountdownV2.2.exe. Choose "End" and then run this program again or choose "Details" for more details.
Details :
EventCountdownV2.2.exe
InvalidCastException
in Microsoft.VisualBasic.CompilerServices.Conversions.ToDate()
in RFTEventCountdown.form1.ListBox1_SelectedIndexChanged()
in System.Windows.Forms.ListBox.OnSelectedIndexChanged()
in System.Windows.Forms.Control._InternalWnProc()
in Microsoft.AGL.Forms.CTL.ListBox.set_SelectedIndex()
in RFTEventCountdown.form1.form1_Load()
in System.Windows.Forms.Form.OnLoad()
in System.Windows.Forms.Form_SetVisibleNotify()
in System.Windows.Forms.Control.set_Visible()
in System.Windows.Forms.Application.Run()
in RFTEventCountdown.form1.Main()
2) Program iFonz-0.9.4.exe. After installation (either in device, or
storage card), when i run the program i get this error message :
There is an unexpected error in application iFonz.exe. Choose "End" and then run this program again or choose "Details" for more details.
The query string is incorrectly formatted.
It is not possible to show error message because it is not possible to find optional sources retention.
Details :
iFonz.exe
ArgumentException
The query string is incorrectly formatted.
It is not possible to show error message because it is not possible to find optional sources retention.
in Microsoft.WindowsMobile.PocketOutlook.AppointmentCollection.Restrict()
in iFonz.iFonz.SetTopAndBallons()
in iFonz.iFonz.iFonz_Load()
in System.Windows.Forms.Form.OnLoad()
in System.Windows.Forms.Form_SetVisibleNotify()
in System.Windows.Forms.Control.set_Visible()
in System.Windows.Forms.Application.Run()
in iFonz.iFonz.Main()
Can somebody help me ? Is there any idea why this hapen? Any solution ? I tried to update .NET Compact Framework 3.5 Redistributable (installation sucsseful), but no results. Still get errors.
Regards
Kostas
I have this issue :
- the phone just went dead one day, doesn`t switch on, doesn`t charge, can`t load preloader, nothing...dead.
- it has SPREADTRUM SC6825c chipset
- driver on PC correctly installed and up to date
- when I try flashing using RESEARCH DOWNLOAD TOOL, I get this error message : OPERATION FAILED or `Download size file larger then it`s partition`
- I have tried using several PACs, everytime same ERROR
- I have tried flashing one file after another, same ERROR
- Research download tool is 2.9.8004.
Does anyone have an advice what to try next ?
New User, so apologies if this post is in the incorrect format :fingers-crossed:
Sorry if TL,DR: but the more information on my issue I give you the less chance your advice encounters any variables.
Recently got into ethical Hacking / pentesting.
Wanting to use a nethunter ROM on my Nexus 5 so when I inevitably break something its replaceable and not my gaming rig.
I did the following:
- Installed Nexus Root Toolkit on my laptop.
-Unlocked the boot loader from this first.
-Then installed Root Permissions and TWRP
These initial steps seemed to have worked.
Boot loader marked as unlocked, SU app installed upon booting new ROM, checks as rooted, and TWRP was being interacted with on the next step.
I then selected the 'advanced' menu in the Nexus Root Toolkit.
And flashed the .zip file for the hammerhead nethunter build version 3.0
There was advice to do several things during this step which I have ignored due to not understanding the process.
- installing gapps. I believe the gapps version for hammerhead is 6.0 however it's listed purpose was to allow access to Google play apps which I have so I discarded this step.
- installing over cryogenmod 14.1 as my Android build is marshmallow 6.0.1. This is the advice I received on the official Kali site, that Nethunter was designed to be used over CM, and perhaps my issue as I flashed it over the stock OS for the phone.
Once the nethunter zip file was flashed through the root Toolkit, I rebooted my phone and logged on. After the initial setup I had all of the applications and the background for the KL Nethunter build, however I encounter a major issue trying to set them up.
When I go to set up the Chroot. I select download option, and then "full Chroot install".
I am then prompted with a message saying bad handshake / server error and I am unable to get past this stage.
The error message is " javax.net.sslSSL handshake exception" no valid pins found in chain.
I am not using a mobile carrier only Wi-Fi.
This is killing me because obviously it means I basically don't have nethunter lmao :laugh: really not funny but any human input you guys can offer with this challenge would be immensely appreciated. I want to begin hooking this up to a TP Link Wi-Fi receiver and I'm extremely demoralised by the fact I can't complete what is essentially " the easy bit ".
Disclaimer - I will follow any suggested links to the letter but for the record. I have combed YouTube. Google. XDA and several other sources for a fix to this. I am aware I need a Kali " arm-hf" file however can't find a repository for such a download or I would download it to the Sd and try to mount it manually!
I just pretty much completed the same process on my nexus 7 (2012) which resulted in me being stuck at the same point. Doing a search has lead me here for possible resolution to our issues.
"The error message is " javax.net.sslSSL handshake exception" no valid pins found in chain."
UPDATE:
I was able to locate the file within the zip file we had flashed to install kali.
Full path was /data/local/kalifs-full.tar.xz
I manually extracted and copied to /emulated/sdcard and ran the chroot wizard and chose to install from sd, it's extracting now.
I'll update once extraction has completed (this tablet has the slowest writes, ever..)
Here is the link to kali chroot.
8point6 said:
I just pretty much completed the same process on my nexus 7 (2012) which resulted in me being stuck at the same point. Doing a search has lead me here for possible resolution to our issues.
"The error message is " javax.net.sslSSL handshake exception" no valid pins found in chain."
UPDATE:
I was able to locate the file within the zip file we had flashed to install kali.
Full path was /data/local/kalifs-full.tar.xz
I manually extracted and copied to /emulated/sdcard and ran the chroot wizard and chose to install from sd, it's extracting now.
I'll update once extraction has completed (this tablet has the slowest writes, ever..)
Click to expand...
Click to collapse
build.nethunter.com/kalifs/kalifs-latest/kalifs-i386-full.tar.xz
I see they dropped support for the nexus 7 2012, likely due to lack of space. I was able to get a full extract done, but hope enough info has been relayed to get you and anyone else past the error we had received. If I pick up where I left off, I'll try to provide an update on this, tabled for now.
Cannot root & flash LineageOS 14.1 (v1awifi) with sequence in LineageOS wiki page
Presently I have an unrooted SM-P900
Android: v 5.0.2
Build: LRX22G.P900UES1CPL1
I am using a custom built desktop Windows 10 machine. At this point I don't know what else to try. I'm not a computer noob, but I am new to rooting and flashing Android ROMs. I'm hoping I can get help from the community.
The installation instructions I followed are on the Lineage OS wiki. I can't post the link because I have fewer than 10 posts here.
1. Success: Setup "adb" via instructions. Entered "adb devices" and got successful response.
2. Success: Enabled USB debugging on P900.
3. Success: Installed Heimdall Suite v 1.4.0. Found at Glassechidna website. Installed " Microsoft Visual C++ 2012 Redistributable Package (x86)" version 4. Typed "heimdall version" in 'Command Prompt' and got "1.4.0" in response.
4. Success: Next - 'Power' + 'Vol. Down' + 'Home' - to get into 'Download Mode' on the P900: Successful.
5. Success: Run "zadig.exe" [v2.0.0]. 'Options' menu, 'List all devices'. Found item called "Gadget Serial" that represents my tablet.
6. Success: In "zadig.exe", choose a 'driver' and click "Replace Driver" button.
a. The 'driver' options to choose from are: WinUSB (v6.1.7600.16385), libusbK (v3.0.4.0), libusb0 (v1.2.5.0).
b. In my efforts to be successful, I tried all 3 drivers.
7. FAIL: Test Heimdall Suite setup. Type "heimdall print-pit --verbose", if device reboots then Heimdall is installed and working correctly.
* This is the point in the installation process I can't get past. I get errors and my P900 does not reboot. In the 'Command Prompt' I see:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: Failed to initialise protocol!
** 'Verbose' mode returns more information than what I've shown. The 'Initializing protocol' step has failed with errors: -1, -7, -12 depending on the drivers I installed in Step 6. Those drivers are compiled into the "zadig.exe" program.
I have tried the following:
( 1 ) All three drivers in v2.0.0 of 'zadig.exe' listed above.
( 2 ) All four drivers in v2.3.701 of 'zadig.exe' which includes: WinUSB (v 6.1.7600.xxxx), libusb-win32 (v1.2.6.0), libusbk (v3.0.7.0), usb Serial (CDC).
( 3 ) USB 3.0 samsung cable in both USB 2.0 and USB 3.0 ports.
( 4 ) USB 2.0 Amazon cable in both USB 2.0 and USB 3.0 ports.
( 5 ) Repeated all previous steps with a Lenovo Ideapad Y470 laptop with Windows 10. Nothing different happened.
( 6 ) Reinitializing Android OS with Kies v3. Kies sees the P900. I can choose to 'update and reinitialize'. It presents a status bar showing it is downloading something. The tablet then goes into 'Download Mode'. But then I get an error that connection with the P900 was lost. Tried this with USB 2.0 / USB 3.0 cables and ports on desktop PC, same result.
My thoughts:
[ i ] There is a v1.4.2 of the Heimdall Suite. But only the source code is available. When I googled it I read of people having more success with that most recent version on other Android devices. But, I don't know the first thing about compiling the code into a Windows 10 executable. And I don't want to use Linux distro CD to run v1.4.2 because I know nothing about Linux OS.
[ ii ] I used 'Power' + 'Vol. Up' + 'Home' to reformat P900 into factory condition prior to all of these steps. But I thought that my tablet initially was 4.4.2 Android. I thought perhaps downgrading the Android OS to 4.4.2 might help, which is why I tried KIES. But even that does not work.
[ iii ] My initial motivation for doing this was to format my external SD card as internal. I know it will be slower, but that is ok. I just do not want to have storage limitations (I have 32 GB version). v 5.0.2 has immature options to achieve this on the P900. I couldn't simply format the external SD card as 'internal'. NO option to do so.
Thank you,
Bearacuda
UPDATE
I reached out to the LineageOS community on Reddit. AndyCGYan replied and told me he had compiled 1.4.2 windows versions of heimdall.exe and heimdall-frontend.exe. I asked him to share them with me. He did. In a command prompt I typed: "heimdall142 print-pit --verbose". The command prompt scrolled with a flurry of text and my SM-P900 rebooted from 'Download Mode'. It worked!
I'd feel better if the Glassechidna guy would compile his own software into a 1.4.2 windows product, but I'm grateful this guy responded.
Thanks AndyCGYan
UPDATE 2: SM-P900 flashed with TRWP and Lineage OS 14.1
I finished the process of flashing my SM-P900 to the Lineage OS v14.1 (20171125). Lineage OS v14.1 (20171202) gave the following error:
"adb: error: failed to get feature set: no device/emulators found"
But when I flashed the 20171125 version it worked. So I'm guessing there is a problem with the 1202 nightly.
The Windows compiled v1.4.2 version of Heimdall I received got me past the 1.4.0 print-pit problem. I don't have 10 messages posted here yet so I can't post the link to the files. But if you go to my post on Reddit in the Lineage OS forum you'll see the link. The person who made the files available to me said he'd keep the files there for others to download. Unless you compile them yourself, I don't know of anywhere else these can be obtained.
To clarify, here is the information regarding my SM-P900
Stock Android v5.0.2
Country: Cellular South (XAR)
PDA: P900UES1CPL1
CSC: P900XAR1CPL1
Kies 3.0 (to obtain most recent Windows Samsung device drivers)
ADB v1.0.39
Heimdall Suite (v1.4.0 with heimdall.exe (v1.4.2) and heimdall-frontend.exe (v1.4.2) replacing 1.4.0 versions)
TWRP v3.1.1-0-v1awifi
Lineage OS 14.1 - Android v7.1.2 - nightly version 20171125 (20171202 gave an error)
Open GApps - arm - v7.1 nano
addonsu - arm - v14.1
NOTE: Even though ADB was successfully setup, I was not successful pushing any files (TWRP, LineageOS, etc.) onto "/sdcard/". Trying so caused an error. I was able to:
( 1 ) remove my extSDCard (64gb Samsung) from the SM-P900,
( 2 ) plug it into my computer and copy over the TWRP, LineageOS, Open Gapps, and addonsu zip files to extSDCard
( 3 ) re-insert my extSDCard back into SM-P900
( 4 ) In TWRP recovery mode, there is an 'INSTALL' button that lets you select multiple zips from either internal or external SD storage. After selecting the zips on the extSDCard all of the files flashed over just fine.
NOTE: When the LineageOS instructions tell you to reboot into recovery mode just after flashing TWRP, what they mean is to press the "REBOOT" button which then leads to a submenu with a "RECOVERY" button. I initially thought the "REBOOT" button meant restarting the system so I didn't push it. Instead I tried pressing the Home + Vol. UP + Power button combination. But all that did was restart the SM-P900 into the stock v5.0.2. Which according the LineageOS instructions destroys the TWRP custom recovery. After repeating this step several times while trying variations of button pressing I finally hit the "Reboot" button and found the submenu of additional options: "System", "Recovery", "Download", etc...
Good Luck
Bearacuda said:
I reached out to the LineageOS community on Reddit. AndyCGYan replied and told me he had compiled 1.4.2 windows versions of heimdall.exe and heimdall-frontend.exe. I asked him to share them with me. He did. In a command prompt I typed: "heimdall142 print-pit --verbose". The command prompt scrolled with a flurry of text and my SM-P900 rebooted from 'Download Mode'. It worked!
I'd feel better if the Glassechidna guy would compile his own software into a 1.4.2 windows product, but I'm grateful this guy responded.
Thanks AndyCGYan
Click to expand...
Click to collapse
please can you share the 1.42 version with me? i am having the same problems
never mind in ended up using odin in the end with twrp. all good now
I'm not sure if there is a specific reason you proceeded using this method rather than using Odin as it was pretty painless to do it with Odin 3.10.6. This is what I did :
(I was already on Lollipop so I did not need to install a Lollipop bootloader.)
- Uploaded TWRP through Odin with auto-reboot and Reset Time unselected.
- I manually turned off the tablet after it was done flashing.
- I turned the tablet back on by pressing Vol.Up + Home + Power
- In TWRP : I swiped to allow modifications
- I made a backup
- I wiped everything except external storage
- I flashed Lineage OS and Magisk in one go.
I installed it without problems but this time it doesn't see my sd card I wonder why