UPDATE: Posted more info in the Misc Android Development section - here.
Hi all, sorry if this is the wrong place to post but hopefully someone else with a rooted Sharp ADS1 can test this out, or even find this usefull - its been working for me for a few days so far and I'd like to share for testing.
I extracted the stock recovery image, used the clockworkmod builder site and have a (mostly) fully working CWM 6 for that device. I've been using it for about a few days, and it works nicely. It wont mount the USB storage on mines, the device was rooted with SuperOneClick.
Started when I saw a youtube video on how to get it into the stock recovery screen (hold Power and Sym while booting).
I was able to make a nandroid backup of my image, I already removed some bloatware from the device. I'm working on a CWM flashable zip of what I have, maybe someone else can do a fully stock image (mines is missing a few bits for a factory-reset).
I also extracted images of the all partitions on the device. I'm working on getting CyanogenMod (working with CM7 at the moment) running on this thing, still trying to figure what to compile it as lol. I managed to get the Kernel to compile, but I'm working on getting a Gingerbread ROM to use with this device.
Specs I noticed on this:
MSM7227/MSM7x27 cpu
Adreno 200 GPU
512MB RAM, 512MB ROM (200-ish accessible by user)
Hardware Keyboard
WiFI/Bluetooth/etc..
Wondering if theres a similar device I can try using their ROM and testing the zImage I compiled.
QUICK N DIRTY INSTRUCTIONS:
-Device must be rooted (use SuperOneClick 2.3.3)
-Copy the flash_image and CWM recovery image for the ADS1 onto the root of your SDCARD (to make things easy for now)
-Using ADB I remounted the sdcard by running the following (otherwise, you'll get permission denied even with/as root)
Code:
mount -o remount,exec /dev/block/vold/179:1 /sdcard
-I used flash_image from my sdcard (pushed it with ADB in Ubuntu), I took the CWM recovery.img file and also pushed that to the sdcard.
Code:
cd /sdcard
./flash_image recovery /sdcard/recovery.img
reboot
-As the phone reboots, hold Power and Sym and it should take you to the CWM Recovery screen after it blinks once.
Now you can do backups/restore images, clear dalvik, battery stats. Only thing that didnt work for me was mounting USB mass storage via Advanced menu. Once you get it installed, do a nandroid backup asap!
LINK TO CWM FILE (contains stock recovery.img, flash_image and clockworkmod in the CWM folder).
here
file is packed with 7zip.
I have more info on my findings on this lil device incase anyone is interested including partition mounting, etc.. root info recovery and system dump info also some random notes on the kernel.
I'm using this as a learning experience/hobby, and I'd like to share incase anyone was wondering what makes this thing tick lol. Have a nice day all!
EDIT:
heres a pic of mines booting into CWM for inspiration
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
system and nandroid backups
Didnt wanna wait to edit, but heres img files for all partitions on froyo - and here's a nandroid backup (should boot, but do a factory reset/wipe data/cache and dalvik in CWM and you''re like new).
Also, the new boot.img and splash,img flash when I put em in a CWM zip however no boot with a "quick" ported GB CM7 rom (still waiting for repo sync to finish ) - flashed a zte v9 as the hardware was similar (even running the grab proprietary files grabbed almost EVERYTHING - there were a few that were off). Hopefully someone can find this interesting for the device. There's a few others that looked promising, I'm taking a break for now tho lol
UPDATE:
Tried using a ROM kitchen to play with the stock rom, didn't work too well lol. I managed to restore a nandroid, but WiFi keeps showing as an error (think it may have had something to do with an option for tethering/wifi that I thought I said No to in the Kitchen's menu...). Also , the signed ROM from the Kitchen seemed to BJork the SuperUser/Root - gonna try flashing a SuperUser CMW zip (3.x)
Also, even with experimenting different roms - CWM is typically accessible via Power + Sym combo. No luck with ro.secure=0 in the stock boot.img - hopefully someone with more experience can help get something running on this lil thing. I'll keep moving forward anyways, have a few ideas of things to try out - albeiit somewhat limited, it's a start . Hope this is usefull to anyone trying to mod this sucker.
UPDATE:
Wifi's back, typing from the device. Restored to a old backup using CWM, on reboot toggled airplane mode and was able to see and join my SSID.
(another) UPDATE:
Looking at other models that seem to have similar hardware, Commtiva Z71, Spice MI300 and ZTE v9 (they have the MSM7227 600MHz/Adreno 200 GPU combo - other specs are very similar). Not sure what they have for sensors, etc.. but I found the ones on the ADS1
Code:
Sensors:
BMA150 Acceleration Sensor: 0.2mA by Bosch Sensortech
MS-3C (YAS529) Magnetic SEnsor: 4.0 mA by Yamaha Corp
MS-x Orientation Sensor: 0.0 mA by Yamaha Corp
ISL29011 Light Sensor: 0.0 mA by INTERSIL
ISL29011 Proximity Sensor: 0.0 mA By INTERSIL
random info from the "features" of the phone (build.prop related?)
Code:
Features:
android.hardware.location.network
android.hardware..wifi
android.hardware..telephony
android.hardware..location
android.hardware..touchscreen.multitouch
android.hardware..sensor.compass
android.hardware..camera
android.hardware..bluetooth
android.hardware..sensor.proximity
android.hardware..microphone
android.hardware..sensor.light
android.hardware..location.gps
android.hardware..camera.autofocus
android.hardware..telephony.gsm
android.hardware..sensor.accelerometer
android.software.live_wallpaper
android.hardware..hardware.touchscreen
glEsVers=2.0
Build Info/Kernel Config from Device.
I've attatched the system.info.gz and config.gz for the stock kernel dumped from my own device.
As far as some ROM testing I did earlier, CyanogenMod 6 for the Z71 (using the Sharp ADS1 boot.img) actually makes it past the Sharp logo and goes to the CyanogenMod boot animation, it stays there but its trying to load something lol. (Luckily I have a few nandroid backups, so flashing back to my previously rooted setup seems to work).
Maybe if I can find something that can work with this setup, then I can look at that device for something to base off to work with CM7. Fun learning experience so far. Going to try a ZTE V9 rom with the Sharp boot image and see what results from that (just trying to see what makes it past the initial boot logo). Might try swapping the build.prop in and see if that does anything lol (using the CM6 keys in their build.prop).
I'm guessing for the CM7 source (or AOSP), I'd have to find a device/manufacturer/device that I can base off for a working sharp/ads1 folder grabbing the needed proprietary files and libs.
Sharp fx plus no clockworkmod
My rooted sharp fx plus is now unable to boot up after doing some modification. I do not have the clockworkmod recovery, so I am unable to load any unsigned roms so I keep getting the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Can someone help me please. THANKS IN ADVANCE
rrkevon said:
My rooted sharp fx plus is now unable to boot up after doing some modification. I do not have the clockworkmod recovery, so I am unable to load any unsigned roms so I keep getting the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Can someone help me please. THANKS IN ADVANCE
Click to expand...
Click to collapse
Hi there, AFAIK you will need a custom recovery to load an unsigned .zip - I have not been able to find a way around that with the stock recovery. Unfortunately neither Sharp or PCD Phones has released a signed update.zip (or kernel sources for the ADS1) to restore it to stock from the sdcard.
Only thing I can think of is try using ADB logcat if possible to track where its looping, and maybe remedy it (remove/replace the offending apk or clear dalvik cache).
AmauryRR said:
Hi there, AFAIK you will need a custom recovery to load an unsigned .zip - I have not been able to find a way around that with the stock recovery. Unfortunately neither Sharp or PCD Phones has released a signed update.zip (or kernel sources for the ADS1) to restore it to stock from the sdcard.
Only thing I can think of is try using ADB logcat if possible to track where its looping, and maybe remedy it (remove/replace the offending apk or clear dalvik cache).
Click to expand...
Click to collapse
Thanks. I'll see if i can
rrkevon said:
Thanks. I'll see if i can
Click to expand...
Click to collapse
I might have found something, when I was rooting a Galaxy I997(?) - there was a modified 3e recovery that allowed loading unsigned images.
If theres a way to modify the ADS1 factory recovery to allow unsigned images, then there may be some hope. For the galaxy, it was replacing a recovery binary with the modified one in /bin and booting to that (rooted phone ofcourse).
If I have some time I'll dig mines up and flash it to stock and try from there.
If the phone is stuck in a bootloop, but has the filesystem mounted then there may be hope. I'll try to see whats possible this weekend maybe.
AmauryRR said:
I might have found something, when I was rooting a Galaxy I997(?) - there was a modified 3e recovery that allowed loading unsigned images.
If theres a way to modify the ADS1 factory recovery to allow unsigned images, then there may be some hope. For the galaxy, it was replacing a recovery binary with the modified one in /bin and booting to that (rooted phone ofcourse).
If I have some time I'll dig mines up and flash it to stock and try from there.
If the phone is stuck in a bootloop, but has the filesystem mounted then there may be hope. I'll try to see whats possible this weekend maybe.
Click to expand...
Click to collapse
I also tried using a signer software, however, it seems only part of the rom was signed. This was the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
Installation aborted.
I realize this is old, but so's my phone (ADS1) and apparently the links. All of AmauryRR's hosting links appear broken. I'm not running Windows, so SuperOneClick isn't much help.
ADB only sees:
List of devices attached
???????????? no permissions
Also, Volume-Down + Power from off doesn't appear to be the boot menu combination. I can't post in the developer section yet, so necroposting it is.
rrkevon said:
I also tried using a signer software, however, it seems only part of the rom was signed. This was the response:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
Installation aborted.
Click to expand...
Click to collapse
From what I remember, the recovery itself had to be modified to allow unsigned roms to work - Signing it yourself, I'm not sure if it'll give the recovery the "signature" its expecting.
nstewart said:
I realize this is old, but so's my phone (ADS1) and apparently the links. All of AmauryRR's hosting links appear broken. I'm not running Windows, so SuperOneClick isn't much help.
ADB only sees:
List of devices attached
???????????? no permissions
Also, Volume-Down + Power from off doesn't appear to be the boot menu combination. I can't post in the developer section yet, so necroposting it is.
Click to expand...
Click to collapse
Yeah, I had to drop my site for a while - I host it myself as a hobby with whatever I have to spare, and unfortunately funds weren't right. Just started a new job, so hopefully I'll be able to get my old site back up.
If you're running linux, IIRC you have to make sure the udev(?) permissions are correct for the device/user. Been a while, so bear with me lol (haven't had this phone in a while, since sharp wasn't helping with the source) - alternately, I think you can try running adb as root (sudo adb kill-server, then sudo adb) and it should recognize the device in terminal.
I can host the stuff for you if you want.
Sent from my SHARP-ADS1 using xda app-developers app
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.
Hi,
this is more an informative post than a question, as I found nothing googling "ASKS OTA", but if you have contradictory information I'll take it
I just tried to flash the latest I9505XXUHQK1 ROM (which has a very high changelist (& "quality base" ?), CL12538431 QB15647851, and which seems to be only released with T-Mobile CSC) with a non T-Mobile CSC (mainly to keep the Black Edition customization), and the extraction at the first boot (which is in recovery) fails, blaming a missing ASKS token :
Code:
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
E: ASKS OTA| Error, ASKS token doesn't exist.
E: ASKS OTA| Error, This is official binary. Failed.
Installation aborted.
E: ensure_path_unmounted failed to unmount /cache (Device or ressource busy)
E: ensure_path_unmounted failed to unmount /cache (Device or ressource busy)
In the T-Mobile CSC, there's an additional "SEC-INF/buildinfo.xml" which seems signed. The CSC itself seems to support a very few countries.
And of course, the CSC customizations are missing.
So the latest Black Edition ROM & CSC seems to be I9505XXUHQC1 (CL5978264 QB12742647) + I9505YXXHPL1 (you can get it with LUX region).
You can also get the La Fleur edition, QXX (I9505QXXHQC1).
I couldn't find the sources for I9505XXUHQC1 by the way, are they published ?
Well, after digging a bit more I found
https://forum.xda-developers.com/showthread.php?t=1633333&page=572 which seems to relate to https://source.android.com/security/apksigning/v2
and https://android.stackexchange.com/q...curity-software-and-device-protection-manager
So this doesn't seems to be specific to T-Mobile as I thought (the "This is official binary. Failed." is weird however), but I guess there's no non-T-Mobile CSC compatible with QK1 yet.
I've seen lot's of folks getting messed up while flashing ROMs on the Mi A1, probably because of the A/B partitioning system (maybe) so, I've made a video on how to flash custom ROMs on Mi A1!! You can watch it here! :good:
Direct Link:https://youtu.be/Ufdn8ql5Lso
Thank you!
Works fine if you have TWRP already installed ...
But coming from Stock there is no TWRP.
Maybe you can add the missing parts (unlock bootloader, install TWRP ...)
good day.
I think i need a little help. I tried to Install 4 different ROMs (Resurrection remix, dotOS, Aospextended, BootleggersROM) through the methods described here.
i always get the following error message.
Skiping digest check:no digest file found
step1/2
error applying update: 7 (errorcode::kInstallDeviceOpenError)
Updater proceess enden with ERROR: 1
Error Installinga zip file '/sdcardTWRP/ROMs/AospExtended-v5.3-tissot-2018-0325-0858-OFFICIAL.zip'
updating partition details...
...done
I do know what to do, I cant find any information about the error on the web.
can you please help me?
I want to repurpose my old S7 (Exynos) as a Server. From what i read, PostmarketOS is the only way to run pure Linux on the S7. Sadly, i have not been successful at booting.
I followed the Installation "guide" from this wiki page.
The installation process in itself works fine. I first flash the kernel using
Bash:
pmbootstrap flasher flash_kernel
while in download mode, then i switch into TWRP (ADB Sideload) and run
Bash:
pmbootstrap install --android-recovery-zip && pmbootstrap flasher --method=adb sideload
The image should be installing correctly, atleast there are no errors and everything seems to look "normal".
Although, when booting, it gets stuck at the PostmarketOS Loading screen and is not booting (SSH over USB does not work)
Going back into TWRP reveals that it has problems mounting the /system partition
"Failed to mount '/system' (Device or Resource is busy)"
I've been trying so many things, but the outcome is always the same
I tried:
* WSL2 Ubuntu
* VirtualBox XUbuntu
* Debian Live Install
* Sending the recovery zip on my phone using USB and then installing it from there
I've been stuck at this for 3 days now, and i have no idea what else i could try...
Any help would be appreciated.
Here's my last_kmsg
I have the same device, but I''ve been stuck for 5 days Also same cryptic-nothing-to look-at last_kmesg, it just stops. Did you make any progress? Most people here are more familiar with Android ROMs. I think we're better off taking this to postmarketOS's Gitlab issues.
I can install Lineage OS 18.1 from some post here on XDA just fine. But I don't want Android on the device, I want to build it as a LAMP server to serve Moodle. Internet and electric power are a mess here, distributed is the way to go. But I'm not going anywhere if I can't show some POC.
I think it's something to do with DM-Verity being tripped, or is it no-verity? I'm following this to restore it to stock and start over with the postmarketOS howto.. The install logs look clean, I must have done this more than 50 times now.. from what I understand reading the logs, seems like it's a partition issue. Kernel just stops ... I confirm the kernel is booting successfully by making it continuously vibrate with :: pmbootstrap initfs hook_add maximum-attention
I'm trying this download PIT part now:
How To Use PIT Files On Odin For Flashing Samsung Device - MTKArena
If you need to change the partition of the firmware and want to use the PIT files for your device, you are in the place. We will share how to use PIT files on
mtkarena.com
any prog @nonick @Xirado ?