Hello dear community,
I have a 9th generation Fire 7 with OS 7.3.1.7 from a good friend.
The device is to be bricked.
Professionally I am an IT system electronics technician and as a hobby I am a tecnican-freak, but this is where I reach my limits.
I have already opened the device and tried the hardware method, but I also get an error message in the terminal. So that I cannot unlock the device or the bootloader.
With MTK-SU this is no longer possible with the OS as I have already read and tested.
My question is, is it still possible to crack the device with this build (date 12/20/20)?
Or am I doing something wrong?
Linux installation
mustang
magisk
everything followed as described in these instructions https://forum.xda-developers.com/t/fire-7-2019-mustang-unbrick-downgrade-unlock-root.3944365/
A reasonable instruction video would be desirable if something like that exists
I'm from Germany so sorry if the English is a bit broken
But I hope there is some way to help me
Many Thanks
Edit:
regularly at Check GPT it breaks off see on pic 2
sudoers said:
Hello dear community,
I have a 9th generation Fire 7 with OS 7.3.1.7 from a good friend.
The device is to be bricked.
Professionally I am an IT system electronics technician and as a hobby I am a tecnican-freak, but this is where I reach my limits.
I have already opened the device and tried the hardware method, but I also get an error message in the terminal. So that I cannot unlock the device or the bootloader.
With MTK-SU this is no longer possible with the OS as I have already read and tested.
My question is, is it still possible to crack the device with this build (date 12/20/20)?
Or am I doing something wrong?
Linux installation
mustang
magisk
everything followed as described in these instructions https://forum.xda-developers.com/t/fire-7-2019-mustang-unbrick-downgrade-unlock-root.3944365/
A reasonable instruction video would be desirable if something like that exists
I'm from Germany so sorry if the English is a bit broken
But I hope there is some way to help me
Many Thanks
Edit:
regularly at Check GPT it breaks off see on pic 2
Click to expand...
Click to collapse
What device is listed as a lsusb? If you can access the bootrom (MediaTek Phone 6227) you have hope
If you are willing to experiment I have a couple ideas I've been contemplating as I have a device I want to root also.
Basically two methods mirroring the original, a hardware method (involves probing SPI/UART) or software method leveraging finding a exploit in userspace. (linux or arm based)
WARNING: DO NOT PROCEED IF YOU WANT TO KEEP YOUR DEVICE
I HAVE NOT TESTED ANYTHING PERSONALLY!
I'm just spitballing from a perspective of a advanced Electronics engineer and Linux backround. (none in pentesting or ANDROID environments) Which is what we need.
The Mediatek vulnerability was a once in 5 years exploit and it seems unlikely to find another exploit that wide open.
For the hardware method you'd need a USB - > TTL/UART/SPI adaptor you could try to crack root but if there isn't even a login console then you are out of luck with that aspect.
Proposed software methods:
This might be made to work if compiled for arm32-bit
GitHub - liamg/traitor: :arrow_up: :fire: Automatic Linux privesc via exploitation of low-hanging fruit e.g. gtfobins, pwnkit, dirty pipe, +w docker.sock
:arrow_up: :skull_and_crossbones: :fire: Automatic Linux privesc via exploitation of low-hanging fruit e.g. gtfobins, pwnkit, dirty pipe, +w docker.sock - GitHub - liamg/traitor: :arrow_up: :fire: ...
github.com
If we can get a stock fireOS image we could run
GitHub - cruise-automation/fwanalyzer: a tool to analyze filesystem images for security
a tool to analyze filesystem images for security. Contribute to cruise-automation/fwanalyzer development by creating an account on GitHub.
github.com
or
GitHub - fkie-cad/FACT_core: Firmware Analysis and Comparison Tool
Firmware Analysis and Comparison Tool. Contribute to fkie-cad/FACT_core development by creating an account on GitHub.
github.com
Also found some shell scripts that don't need compilation.
GitHub - carlospolop/PEASS-ng: PEASS - Privilege Escalation Awesome Scripts SUITE (with colors)
PEASS - Privilege Escalation Awesome Scripts SUITE (with colors) - GitHub - carlospolop/PEASS-ng: PEASS - Privilege Escalation Awesome Scripts SUITE (with colors)
github.com
GitHub - pentestmonkey/unix-privesc-check: Automatically exported from code.google.com/p/unix-privesc-check
Automatically exported from code.google.com/p/unix-privesc-check - GitHub - pentestmonkey/unix-privesc-check: Automatically exported from code.google.com/p/unix-privesc-check
github.com
There's also Ghidra if you are a pro binary analyzer which might be the best bet but also the hardest.
-ANDROlD- said:
If you are willing to experiment I have a couple ideas I've been contemplating as I have a device I want to root also.
Click to expand...
Click to collapse
sudoers said:
My question is, is it still possible to crack the device with this build (date 12/20/20)?
Click to expand...
Click to collapse
Got a interesting idea i'm working on, todo with fbtool and unbrick on this particular type of Fire 7, requires compiling lineage, possibly a bit of reverse engineering - currently thinking about it still:
Fire 7 2020 mustang Brainstorming
Trying to brainstorm ideas for unbrick (firstly) of the new Fire 7 2020 Gen 9 models that feature 6.3.1.5 and were released post Feb 2020. Already have a method to downgrade this and many other devices (HD8 Onyx and HD 10 post patch Feb 2020)...
forum.xda-developers.com
The problem is that they secretly revised the hardware for that model .
After the first production run made in 2019 , without the public knowing
They started to lock down the whole tablet.
its not only software locked , its hardware locked on the chip .
Most people didn't realize they did this after the initial 2019 production run .
Any chance I get I advise people not to purchase a newer amazon tablet . especially
The gen 9 .
You can't go wrong with the tablet 7 , gen 7 .
every variant for that Amazon model is flashable . even the ones that need to be opened up
to do the hardware short .
It doesn't look good for the gen 9 model ,
Its locked down harder then Pam Anderson growing up in the 80s .
I've successfully downgraded from FireOS 7 using the hardware method. Latest magisk canary etc
CFKod said:
I've successfully downgraded from FireOS 7 using the hardware method. Latest magisk canary etc
Click to expand...
Click to collapse
That sounds good .
just curious , what year is that 9gen .
That could be more documentation on exactly what year model 7 , gen 9 could
be modded . maybe you found something different that could work after the
2019 batches that were shipped. Idk . I just know what I seen until know ,
but absolutely there could always be exceptions.
Chris.
Sure let
fleisch80 said:
That sounds good .
just curious , what year is that 9gen .
That could be more documentation on exactly what year model 7 , gen 9 could
be modded . maybe you found something different that could work after the
2019 batches that were shipped. Idk . I just know what I seen until know ,
but absolutely there could always be exceptions.
Chris.
Click to expand...
Click to collapse
Does that help? Registered 26th October 2019
CFKod said:
Sure let
View attachment 5854183
Does that help? Registered 26th October 2019
Click to expand...
Click to collapse
mtksu software method will never work on fire os7
However, you can use the hardware method, which installs twrp and allows for downgrade back to 6
Related
[UPDATE]2012-08-06 This is not the only way of getting Dongle's working on Android, If widgets are your thing and you doing feel confident working with system files etc then you may be better served using the ppp widget form draisberghof.de, these are the folks who piratically wrote the book on getting dongles working on linux and by extension android.
[UPDATE]2012-08-06 The source to libhuaweigeneric-ril ( github ) has been updated to include fixes made by omegaRed7 - This massively improves the fault tolerance upon RIL Startup, Tests were carried out on the E173s-1 but it should be beneficial to all modems ( I hope ).
[UPDATE]2012-07-28 As the Rom Version is quite old and it doesn't really require it's own rom I've extracted the files required to implement this functionality - Download Here, The Archive contains a README file with installation instructions
IMPORTANT - pppd permission need changing to 6755 also change to ownership to the root account ( Thanks to __DS__ ). you can do this through adb or terminal emulator
Code:
adb shell chown 0:0 /system/bin/pppd
adb shell chmod 6755 /system/bin/pppd
for this to function
[UPDATE]2012-06-25 Added Forked libhuaweigeneric-ril to Github Repo this includes all the changes I've made - Check This Post For Details
[UPDATE]2012-06-23 Added Github Repo - Check This Post For Details
[UPDATE]2012-06-16 THE DOWNLOAD LINK HAS BEEN UPDATED AS THE FILES IN /etc/system/usb_modeswitch WHERE NAMED INCORRECTLY[/UPDATE]
Hi Folks - This post is going to change fairly often, there is still more info to add, I just got bored with typing for now
The Sales Pitch
This rom aims to provides the same "hands free" approach offered by the Archos 3G Key and extends this functionality to Huawei Branded USB Modems.
Introduction
Here is a custom rom I've currently been hacking away at, if feels like I've had it under wraps for months.
That being the case. I'd like to thking on to enable Huawei USB Modems - This is still a WORK IN PROGRESS but It feels like i've been keeping it under wraps for months, So it's time to throw it out there for further testing. So Dongles at the Ready! It could get a little hacky
WARNING
The Full Size USB Slot has been known to fail from moderate use. As such I would recommend using an USB extensions cable for connecting devices.
VERY IMPORTANT NOTES - PLEASE READ
1. This is definitely not an every day use rom on any other device this woud have been deployed as a recovery flashable update. The reasoning behind the rom deployment is it's only one file to copy and youi're ready to go. It is also a tedious task to manually go through (especially on the 100th time
2. Please don't ask a me if a certain device will work or not. It is not helpful on a number of levels,
a) I simply don't know - I don't own the model in question. Further more you can figure it out yourself.
b) The Chances are that you could probably find out the answer without leaving the comfort of xda - The libhuaweigeneric-ril has been passed around xda like a <Insert Well Used Analogy Here> so a quick search of xda may turn up something useful to reassure you.
c) In reality though we are not going to know if your dongle is working until you "Try It Yourself".
3. if you find your device doesn't work then you need to gather all the relevant information to help get a feel of what's going on; See Below
SUPPORTED DEVICES
The theoretical list of supportted devices come from those devices supportted by usb_wwan and option kernelp drivers.
IMPORTANT NOTES - WHAT YOU NEED TO KNOW
In a perfect world you can download/flash the attached update file. Reload your SDE, Plug a USB 3G Dongle and have It connect and go about you day .
This is the ultimate goal and currently what happens on my own device
TROUBLESHOOTING
There's about a 25% based on my current test this won't happen. There are 2 main ways your connection attempt can fail.
1. The UsbStick has not switched to modem mode
2. The ppp connection script failed
Either Way it would be highly useful post the list of system properties, outputs of dmesg and also a full logcat aswell as the vendor/product id from lsusb,
some like this throught the adb
Code:
adb shell getprops
adb shell lsusb
adb shell dmesg
adb logcat -b radio -b system -b main -b events
Please have a glance over it before posting as It may contain information that you would not want others to see!
ROM DETAILS
Android Version: 4.0.3
Archos Version: SDE 4.06
Removed : Nothing
ADDITIONS
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
DOWNLOAD
3G Modem Redist Pack - For use with newer roms
Hotfile - archos.ext4.update.
INSTALL
Unpack zip and copy unpacked update file to the device
Code:
adb push archos.ext4.update /mnt/storage
restart device in sde mode
script should update automatically
KNOWN ISSUES
"3G Stick Connected" Icon remains in notification list after device disconnection.
pppd needs to be executed with elevated privileges.
pppd is not exiting correctly on some occasions and cause reconnection issues when using multiple sticks.
Thanks go to surdu_petru for the base sde, derAtem for his original work on the libhuaweigeneric-ril.so and pretty much every developer who has worked on these dongles with android, I think I've read every thread on XDA regarding this subject
Hi!
Thanks trevd!
I do not have this USB modem ....but you did a good job for those who have this modem ! Good luck...
i have a Huawei E160E
It is possible to add this modle on your rom ?
---------- Post added at 06:46 PM ---------- Previous post was at 06:23 PM ----------
For the buzz in FRANCE (and in the World :-= )
http://www.jbmm.fr/?p=28280
cajl said:
i have a Huawei E160E
It is possible to add this modle on your rom ?
Click to expand...
Click to collapse
Is this a new model ( released this year )? It may already be in there, The easiest thing to do is plug it in.
If you install this app you can find out what the product_id is and then we can find out for sure.
Thanks
no released in 2009
Device Class: Use class information in the Interface Descriptors (0x0)
Vendor ID: 12d1
Vendor Name: Huawei Technologies Co., Ltd.
Product ID: 03eb
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Rackham666 said:
Hi trevd.
Thanks for the work.
Before installing your rom, I'd like to know if my Huawei K3565 is or will be supported.
I can't remember when it was released, but it not a new one ; may be 2009 or 2010.
Click to expand...
Click to collapse
Hi Rackham666
I'd refer back to my first post, I've tried to make it a little more clear what this "rom" exactly is, more a testing ground, my apologises if that wasn't very clear at first glance, So to switch this query right back at you.
After installing my rom, I'd like to know if your Huawei K3565 is supported?.
For my usn dongle , is it ok for you ?
Okay.
I'll try your additions manually when [email protected] V3 will be released by Petru.
Get The Code
Hi Folks.
I've started a github repo if anyone wants to hack on this stuff.... It only contains the code for the hotplug service at the moment but I will obviously add more when I get chance and apply all the proper GPL licenses to it.
A personal word of note : C is not my first language by any stretch ( although it is fast becoming the case ) so If It causes any memory leaks or starts nuclear war I can't be held responsible, however if there is any noob coding errors in there then I'm ready to learn off those more knowledgeable than I. I have a feeling we have some hardcore developers lurking in Archos Development community
Equally If anyone has any fixes drop me a pm and I'll sort commit access on the repo or post them right here in the thread,
The code can be found here https://github.com/trevd
Hi Folks, Me Again!
Just to let you guys know I've added a forked libhuaweigeneric-ril to my github ( https://github.com/trevd )
It includes the changes I made to enable it to work the Archos.
You'll want to clone the ics branch if you want to compile yourself.
cajl said:
For my usn dongle , is it ok for you ?
Click to expand...
Click to collapse
???
I'm not sure I understand what you mean.... can you explain a little more
Thanks
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, I'm sorry if I'm bothering you but I've done the steps for installing this but when I get to sde menu nothing happens. You said script should install the update automatically but nothing happens. Is there something else I have to do?
Sorry again and thank you for your work
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
Hi Alahkel
You're not bothering me .... DO I really sound/come across as that grumpy/angry in my first post.... sometimes I get cranky when I don't get enough sleep.... too much time looking at code.... :laugh:
Thanks for having a go, Are you using the official SDE? and have you got a working SDE Rom already installed?
For now I would forget about the rom image and bear with me, I'm working on an installer APK which will probably better help with testing, I'll also put the manual installation method up for those who want to get dirty with adb.
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
alahkel said:
Hi, i succesfully installed your build then, btw running unoff sde. I have a huawei 170something, I don't remember the model, but it's working great with no problems, but using a otg cable only. I didn't get it to work using the big usb slot
Sent from my ARCHOS 101G9 using xda premium
Click to expand...
Click to collapse
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
trevd said:
That's great news Interesting that you couldn't/haven't got it working on the full size port... It should function the same as the official Archos Stick, You need to switch on the 3G Stick in the settings and the full size slot should "Just Work". I may have missed that little detail out
If that doesn't work your full size slot is maybe broken A not uncommon issue it seems. unfortunately.
Out of interest what network are you on?
I'm just working on the installer now so you won't be stuck with old archos versions.
Click to expand...
Click to collapse
Hi, thx for answering. Well of course I turn on the 3g key in settings for big-size usb and my huawei 3gkey is on indeed (led on key) but the tab doesn't recognize that o.o I'm on tim (italy ) Thank you
Sent from my ARCHOS 101G9 using xda premium
Hi trevd,
i'm guessing this won't work on CM9 by JackpotClavin, or would it? If yes, would i install it the same way as described?
Thanks in advance!
Edit: Sorry i'm obviously still running in 1st gear in the morning... There's no 3G support in the CM9 port so there's no way this would just "work"...
Edit2: And confirmation that i need more coffee: Saw your post in CM9 thread about the successful connection with Archos' 3G stick and a Huawei 3G stick, but only through the browser... Any progress on fixing things so the ppp connection is fully usable by other apps & services?
Hi, trevd!
how to launch the modem on a firmware 4.0.7?
I copy these files from your firmware
init.dongle.rc - initialization script, I wanted to avoid "polluting" any other init file too much
/lib/modules/usb_wwan.ko and /lib/modules/option.ko - USB Drivers for GSM modems
/system/lib/libhuaweigeneric-ril.so - A slightly tweaked version of DerArtem original huaweigeneric-ril
/system/etc/usb_modeswitch - the latest version of the usb-modeswitch-data
/etc/ppp - Added separate gprs scripts to retain compatibility with the Archos datakey
/system/bin/hotplugd - A new native android service; Manages Modeswitching and connection initialization for any Usb Device which has a valid configuration file present.
Click to expand...
Click to collapse
I change the init.rc file for init.dongle.rc start
but the Huawei E1550 modem doesn't work
what it is necessary to change still?
Thanks!
=========================
sorry, everything earned, it was necessary to update a modem firmware
Hi deman05
You were nearly there, init.dongle.rc is imported on the very first line of init.rc so you need both files.
You shouldn't have to do anything with the modem firmware as usb_modeswitch will handle turning the modem.
The files required are.
init.rc
init.dongle.rc
/lib/modules/usb_wwan.ko
/lib/modules/option.ko
/system/lib/libhuaweigeneric-ril.so
/system/bin/hotplugd
Also you need the full contents of the following directories
/system/etc/usb_modeswitch
/system/etc/ppp
/system/etc/chatscripts
I've attached the latest versions to this post (hopefully I've not missed anything), you will need to change the permissions on /system/bin/pppd.
chmod 6755 pppd
[EDIT] I did miss something, please see the first post for the correct download link.
The new version also handles a cold boot ( modem plugged in on startup ) scenario.
If you are still having issues please refer to the troubleshooting section in my original post
Thanks
Hi,
Here is CM-11 (Android 4.4.4) for the kindle fire hdx 7" (THOR). You need a rooted hdx 7" (Thor) device with a firmware < 3.2.4 (3.2.3.2 ideally) and a signed recovery.
Todo
Bluetooth not working
Wifi won't correctly load when disabled at boot, a reboot is required
Minimal headphone volume too loud -> fixed
Incorrect color format in some scenario's ? (YouTube) -> fixed
Changelogs/Downloads
cm-11-20150226-UNOFFICIAL-thor.zip
Updated to amazon 4.5.3 binaries
Fully disable radio for now (thanks Andy-Voigt)
Fix twrp fstab (enabling twrp was breaking system rom to boot)
CM sources updated to 20150226
cm-11-20150219-UNOFFICIAL-thor.zip
CM sources updated to 20150219
cm-11-20150219-UNOFFICIAL-thor.zip
fix minimal video/media volume too high (youtube...)
switch back to tablet build
CM sources updated to 20150110
cm-11-20150108-UNOFFICIAL-thor.zip
Fix thermal engine (should give better battery life and performances)
Fix a lot of proprietary services (proprietary logs, acdb-loader, ril loading ...)
Set media volume steps to 100 instead 15 (allow finer volume control essentially for jack output)
Lowered minimal screen brightness
CM sources updated to 20150108
cm-11-20150107-UNOFFICIAL-thor.zip
Build without "hacks" (add Cuber signing and custom updater-script generation)
CM sources updated to 20150107
Enable telephony (will probably not work)
cm-11-20150101-UNOFFICIAL-thor.zip
use patched boot/recovery, thanks to @vortox
fix wrong color format ! (major bug resolved)
switch to kernel sources
cm-11-20141218-UNOFFICIAL-thor.zip
minors fixes
cm-11-20141217-UNOFFICIAL-thor.zip
fix wifi not reloading
fix overlay/rotation screen tearing
cm-11-20141216-UNOFFICIAL-thor.zip
updated binaries to amz 4.5.2
properly use precompiled kernel and headers (amz 4.5.2)
fix minimal audio volume too high
add safestrap compatibility
Sources
android_device_amazon_thor
android_device_amazon_hdx-common
hardware_qcom_display-caf-hdx
hardware_qcom_audio-caf-hdx
hardware_qcom_media-caf-hdx
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
r3pwn said:
I'm sure the community here respects all of the work that you do. My post in the other thread was not intended to "get you in trouble". There are a set of rules that every user has to follow, regardless of their contributions to the community. That being said, when I was a newer member, I accidentally broke the rules a couple of times (nothing major) and didn't want the same to happen to someone else. (I never contacted @Divine_Madcat about your other thread, in case you were thinking I did.)
Click to expand...
Click to collapse
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Cpasjuste said:
Yep i was tinking to that... so I'm also sorry. The thing is i spent a lot, lot of time on this port, and Divine_Madcat didn't even give me the time to update the first thread with the needed files/informations and ignore my pm which was an offense to me. Well i have to complies to the rules too but was a little chocked on how the thread got mad. Well, let's hope it won't be the same here. So that said i have no problem with you !
Click to expand...
Click to collapse
While i am sorry you are upset, it was not a slight at you at all. While i do try to keep an eye on XDA while at work, my job does come first and foremost, and i was unable to handle anything here yesterday (what can i say, 12 hour work days suck). As it was, i have literally nothing against you; to be frank, the report on the thread was the first i had even seen.
From my perspective, we had a placeholder thread, which is not allowed, so it was closed. I fully intended to reopen it, but gave my reasons above...
Anyway, i do wish you luck, and i really dont have any ill will to you...
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
tuanda82 said:
So....
Do we have unlocked bootloader or a root exploit for amazon firmware 4.5.2 soon? And do you have plan to release another for Apollo?
Thanks
Click to expand...
Click to collapse
Nobody knows. But there are a few people working on "unlocks" (at least booting an unsigned kernel). Maybe also jcase releases his unlock (which I doubt because of legal issues).
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
URBANsUNITED said:
Hi!
I have rooted Kindle Thor. How do I install this nice piece of software?
Like the Nexus rom? Currently I am on 3.2.7...
Thanks
URBANsUNITED
Click to expand...
Click to collapse
You need to be on 4.5.2 and rooted.
cyablo said:
You need to be on 4.5.2 and rooted.
Click to expand...
Click to collapse
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
URBANsUNITED said:
Mmmmmhhh
Than this rom is basically usless
Who has a 4.5.2 Base and Rooted??? I would do it if I'll get the tools, no fear of a brick
Too bad. But Nevertheless Many thanks for the work and effort!
Click to expand...
Click to collapse
There are a few Users which do have an unlocked Bootloader, this Rom is only for these Users, as stated in the first Post.
I decided to make the rom available in case i loose interest in this device (or if i ever die soon). This way when (if) a root exploit is available then you'll be ready to use it.
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
openWeb74 said:
Ok... So if there IS a possibility to unlock the actual fireos, please give some hints, instead of publishings Roms that one or two users can install, the rest is completely helpless...
Sent from my Nexus HDX 7 using XDA Free mobile app
Click to expand...
Click to collapse
Sharing hundreds of hours of work is helpless/useless for you ?
You know what ? I actually spent the whole day on porting cm-10 to current exploitable kernel for YOU :/
Everybody chill , @openWeb74, i see your point @Cpasjuste , first let me thank you for all your work, I'm pretty sure its a great Rom!
What openweb said was that maybe we should concentrate our efforts in unlocking the bootloader so even greater support can come.
Unfortunately we, the rest of us common mortals (with locked bootloaders) cannot use it.
As you said, this would work if somebody would release the bootloader-unlock , so lets play the waiting game...
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
I really have to say sorry, if you dont know how to reproduce the hack... Mea culpa. It sounded like the hack is known, but cant be made public because of copyright issues or something like that... Then we have to wait. Nothing is secure when the right person gets a hdx... I have to say, that my actual hdx was rooted with towelroot, even easier than the nexus (less button combinations ) so i didnt expect amazon to be such a **** with newer firmwares.
Sent from my LG-D802 using XDA Free mobile app
Cpasjuste said:
The thing is I'm a common mortal like you :/ Like its said on first post, unfortunately, I do not have the tools nor the knowledge to reproduce the unlock, so I share what I can.
Click to expand...
Click to collapse
Sorry for nagging you about it, but — genuinely asking — how did you do it on your device in the first place?
dear Cpasjuste, thanks for your great work, and how to install this Rom ? I am newbie, so..
OK... So you are a newbie in reading too?
Sent from my Nexus HDX 7 using XDA Free mobile app
I may eventually move to another tablet as I'm loosing interest in this device (because cm is working fine [emoji14]). Would someone be interested to get my device (not for free )?
Have been busy porting the SM-T285 to OmniRom 5.1, would just like to post the progress so far:
I've managed to reach a point where I managed to get graphics working and bring up the Android Home screen, however I still need to fix wifi, bluetooth,cellular.
If anyone can point me to someone who has experience porting spreadtrum devices, esp the sc8830 please pm me.
Below is a semi working SM-T285 device tree that I am currently working on:
Device Tree:
https://github.com/jedld/device_samsung_gtexslte.git
jedld said:
Have been busy porting the SM-T285 to OmniRom 5.1, would just like to post the progress so far:
I've managed to reach a point where I managed to get graphics working and bring up the Android Home screen, however I still need to fix wifi, bluetooth,cellular.
If anyone can point me to someone who has experience porting spreadtrum devices, esp the sc8830 please pm me.
Below is a semi working SM-T285 device tree that I am currently working on:
Device Tree:
https://github.com/jedld/device_samsung_gtexslte.git
Click to expand...
Click to collapse
How is this coming along. I see you've been working on it right through last night. Any progress with the RIL?
TopTongueBarry said:
How is this coming along. I see you've been working on it right through last night. Any progress with the RIL?
Click to expand...
Click to collapse
I got rild working, now trying to get wifi up.
Current OMNIRom status for the SM-T285.
1. Phone/LTE Services - OK
2. Graphics (hwcomposer/gralloc) - OK with bugs
3. Wifi - Still need to fix wpa_supplicant issues OK (10/20/2016)
4. Bluetooth - Broken, stock uses a custom bluedroid lib, will need to reverse engineer bluetooth commands
5. Audio - OK
6. Accelerometer - OK
7. GPS - Not Tested
8. USB Services (adb, tethering) - OK
9. Camera - Broken
Will post ROM once I sort these issues out.
Looking forward to this. :good:
I've just switch to porting OMNIRom 6.0 to the SM-T285, screenshots here:
SM-T285 running marshmallow
ril got broken when moving from 5.1.1 unfortunately, so working to get it back on. However there are now no more graphical bugs, the SM-T285 actually runs impressively on the Marshmallow
A release should be happening this week, I hope I beat samsung to Marshmallow with this device
jedld said:
I've just switch to porting OMNIRom 6.0 to the SM-T285, screenshots here:
SM-T285 running marshmallow
ril got broken when moving from 5.1.1 unfortunately, so working to get it back on. However there are now no more graphical bugs, the SM-T285 actually runs impressively on the Marshmallow
A release should be happening this week, I hope I beat samsung to Marshmallow with this device
Click to expand...
Click to collapse
Awesome.
Just curious. Will safety net pass?
venomrat said:
Awesome.
Just curious. Will safety net pass?
Click to expand...
Click to collapse
Haven't tried, however I am led to believe that safetynet fails in general for all custom roms that is not based on stock like CyanogenMod or Omni.
Hello there, your work looks very good so far! Its good to see that someone finally takes care of the Tab A 7.0
Are u planning a T280 Release too?
Greetings
jedld said:
Have been busy porting the SM-T285 to OmniRom 5.1, would just like to post the progress so far:
I've managed to reach a point where I managed to get graphics working and bring up the Android Home screen, however I still need to fix wifi, bluetooth,cellular.
If anyone can point me to someone who has experience porting spreadtrum devices, esp the sc8830 please pm me.
Below is a semi working SM-T285 device tree that I am currently working on:
Device Tree:
https://github.com/jedld/device_samsung_gtexslte.git
Click to expand...
Click to collapse
Quick question, I have very little or no experience about porting a rom. How do you do it and what applications and guide do you use to port a rom? I have a SM-T350 and I'm going to port Cyanogenmod 14. Thanks for the reply, in advance.
ParadoXGodzillA said:
Quick question, I have very little or no experience about porting a rom. How do you do it and what applications and guide do you use to port a rom? I have a SM-T350 and I'm going to port Cyanogenmod 14. Thanks for the reply, in advance.
Click to expand...
Click to collapse
I don not personally have an all in one guide that I am following. There are various sites that provide bits and pieces of it, for CM, they have their own porting guide here: https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Unfortunately, the guide above is only good for creating an initial setup. To be able to make the rom work on your device, you are probably going to need a bit more, sites like android open source provides a brief overview of how the bits and pieces work at a low level:
https://source.android.com/devices/index.html
I also had to deal with SELinux, and this is the part where there is a lot of lacking tutorials.
Next is mostly device specific. The best case scenario is if your device already has a CM port available (previous version) or if a device with similar hardware has it. If the SM-T350 already has a CM port available somewhere then your job is going to be a bit easier. If not it is going to extremely hard depending on what sort of hardware you are dealing with. There are some hardware manufactures that provide good support like Qualcomm and those that aren't so good at it Spreadtrum *cough*. In my own experience with the SM-T285 there aren't many devices with CM around that sport the same hardware, the best I got going was a Samsung Galaxy Core (core33g) CM port that I found in github after looking really hard. The real challenge is figuring out how things work and what "changes" the specific manufacture did to existing aosp. There are times where you are forced to use the stock (proprietary) libs and attempt to shim(patch functions) them to work.
I already have experience compiling CM from source since I also have a Nexus 5 which has pretty good support. I also have several years experience as an Android Developer as well as prior dev experiences related to Java/C/C++. You should also be familiar with the languages used in building android namely C/C++, Java as well various scripts as well as dealing with linux as there would be times when you need to make modifications to backport/forwardport functions used by proprietary libraries.
jedld said:
I don not personally have an all in one guide that I am following. There are various sites that provide bits and pieces of it, for CM, they have their own porting guide here: https://wiki.cyanogenmod.org/w/Doc:_porting_intro
Unfortunately, the guide above is only good for creating an initial setup. To be able to make the rom work on your device, you are probably going to need a bit more, sites like android open source provides a brief overview of how the bits and pieces work at a low level:
https://source.android.com/devices/index.html
I also had to deal with SELinux, and this is the part where there is a lot of lacking tutorials.
Next is mostly device specific. The best case scenario is if your device already has a CM port available (previous version) or if a device with similar hardware has it. If the SM-T350 already has a CM port available somewhere then your job is going to be a bit easier. If not it is going to extremely hard depending on what sort of hardware you are dealing with. There are some hardware manufactures that provide good support like Qualcomm and those that aren't so good at it Spreadtrum *cough*. In my own experience with the SM-T285 there aren't many devices with CM around that sport the same hardware, the best I got going was a Samsung Galaxy Core (core33g) CM port that I found in github after looking really hard. The real challenge is figuring out how things work and what "changes" the specific manufacture did to existing aosp. There are times where you are forced to use the stock (proprietary) libs and attempt to shim(patch functions) them to work.
I already have experience compiling CM from source since I also have a Nexus 5 which has pretty good support. I also have several years experience as an Android Developer as well as prior dev experiences related to Java/C/C++. You should also be familiar with the languages used in building android namely C/C++, Java as well various scripts as well as dealing with linux as there would be times when you need to make modifications to backport/forwardport functions used by proprietary libraries.
Click to expand...
Click to collapse
Thanks for the info by the way. Can you add me on XDA-Developers so I can ask you any questions for going through the process of making your own rom? SM-T350 doesn't have any Cyanogenmod but only an EVERVOLV rom that has many bugs. Also do you have a tip or a link for Java/C/C++? I have no experience.
Thanks if you respond back!
So, for those who know don't know already, a new zero-day (CVE-2019-2215) was recently found that applies to a majority of devices that run Oreo and higher, and a PoC application created by Grant Hernandez has been made to demonstrate the potential of this exploit when it comes to rooting. The code of this PoC application has been released onto GitHub and you can check it out in the links below, and maaaaaybe this means that the code can be customized to work on Snapdragon Samsung devices (no idea about Exynos) as this has been tested only on Pixel 2 devices, and in my own attempt in running the app, the process hangs after a few seconds. Sadly, there are a good amount of downsides with this PoC, mainly that Magisk is installed in core-only mode, and installed without a patched boot image. According to Grant, installing other Magisk environments and or updating it can possibly cause DM-Verity and you'd need to do a clean install.
I just wanted to share this with you guys, maybe we can utilize this for the greater good, and hopefully get some stuff going for Samsung devices with this as the base.
PS: The October security update patches this vulnerability, so if you already updated, yikes.
Related links
https://github.com/grant-h/qu1ckr00t
https://github.com/kangtastic/cve-2019-2215/blob/master/cve-2019-2215.c
The PoC of Hernandez manipulates kernel data structures, the user process credentials, that are protected by Samsung real time kernel protection (RKP). Normally, the PoC should therefore not work on Samsung devices, or am I wrong with that?
The original PoC was reported to work on S8 and S9. But i fear this was only due to the PoC did not trigger RKP. Will have a look at the original PoC, to assess that ...
i think the Samsung Knox version is decisive. This document states, RKP only protects kernel data structures on selected devices: (search for Real-time Kernel Protection (RKP))
In the 2018 version this comment is missing, indicating newer Knox versions protect kernel data structures on all devices: (Search for Knox Deep Dive: Real-time Kernel Protection (RKP))
In this case the PoC of Hernandez will not work.
Sorry this is pretty unrelated, but would it be possible to use this on a new lg g8 on september patches? Haven't had any luck asking in forums over there hoping this forum is a bit more active. Thanks
antintin said:
Sorry this is pretty unrelated, but would it be possible to use this on a new lg g8 on september patches? Haven't had any luck asking in forums over there hoping this forum is a bit more active. Thanks
Click to expand...
Click to collapse
It's kinda active here but I wouldn't hold my breath waiting for help with an LG in a Samsung note 9 forum tbh.
If not, anyone can make a bount?
matheus_sc said:
If not, anyone can make a bount?
Click to expand...
Click to collapse
Surely they are already working on it. But it just takes some time. At the moment everything is working optimally despite fastboot. Even root is possible.
pittrich said:
Surely they are already working on it. But it just takes some time. At the moment everything is working optimally despite fastboot. Even root is possible.
Click to expand...
Click to collapse
I know i use xiaomi eu already. Only update is pain to ass
wait for it
Rumour has it some chinese dev is working on it
Any news?
matheus_sc said:
Any news?
Click to expand...
Click to collapse
Still no sign.... Orangefox also quiet...
The guy who made lots of xiaomi TWRP recoveries stopped developing.
... are kernel (or device/vendor) repos released for it?
This would help.
Do we have TWRP and/or released kernel sources from other Qualcom 888 based devices out there?
raupe said:
... are kernel (or device/vendor) repos released for it?
This would help.
Do we have TWRP and/or released kernel sources from other Qualcom 888 based devices out there?
Click to expand...
Click to collapse
This?
Xiaomi Mi 11 kernel source code is out, the device is codenamed "venus" - Gizmochina
Yesterday, Xiaomi announced Mi 11 as the world’s first smartphone powered by Qualcomm Snapdragon 888. The handset already went for pre-order soon after the launch and is set to go on sale for the first time on January 1. Ahead of its sale, the company has even released this device’s kernel...
www.gizmochina.com
I read on Xiaomi.eu somewhere that there are issues with how the partitions are made and TWRP is very difficult to make for this. They said it's gonna take either a very long time before a recovery is made, or maybe not even at all.
Danacy said:
I read on Xiaomi.eu somewhere that there are issues with how the partitions are made and TWRP is very difficult to make for this. They said it's gonna take either a very long time before a recovery is made, or maybe not even at all.
Click to expand...
Click to collapse
Yeah they changed everything over to GKI 1.0 and no one seems to be supporting it, although they found somewhere on a Chinese site a recovery that works (TWRP) if you boot it (don't flash it) and unencrypts the data. It's in the XDA forums now.
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
mslezak said:
[TWRP] [venus] TWRP Recovery for Mi 11
REMOVED! Use this instead : https://forum.xda-developers.com/t/recovery-11-official-teamwin-recovery-project.4374109/
forum.xda-developers.com
Click to expand...
Click to collapse
*justintime* said:
Still no sign.... Orangefox also quiet...
The guy who made lots of xiaomi TWRP recoveries stopped developing.
Click to expand...
Click to collapse
Yeah Mauronofrio is out, too much work for no return. He was pretty much the last standing open-source TWRP dev out there for tons of devices. The ones from China never get source released... Which would mean that someone would have to pickup the TWRP project and re-engineer it to fit the new GKI 1.0 then 2.0 platforms that run off that ACK. That's a lot of work. I'm talking about keeping the TWRP project open-source. It would very nice if Google stepped in since they are experts on the new format, but no such luck.
mslezak said:
Yeah they changed everything over to GKI 1.0 and no one seems to be supporting it, although they found somewhere on a Chinese site a recovery that works (TWRP) if you boot it (don't flash it) and unencrypts the data. It's in the XDA forums now.
Click to expand...
Click to collapse
Interesting, that would explain also the lack of custom ROMs? But I read that the source code is released, even before the device was launched. Isn't there GKI-support to be found in there?
Danacy said:
Interesting, that would explain also the lack of custom ROMs? But I read that the source code is released, even before the device was launched. Isn't there GKI-support to be found in there?
Click to expand...
Click to collapse
Yes they released source there are just no instructions anywhere on how to build the kernel #1 and the GKI modules #2 and combine into a build.
The new Xiaomi.eu weekly includes TWRP for Venus (Mi11) as well as Star (Mi 11 Lite 5G, Mi 11 Pro, Mi 11 Ultra, MIX FOLD) (it's a bootable TWRP, but persists after installation). Seems last week's has added Alioth (Mi 10S, Redmi K40). So I would expect a TWRP for Haydn to show up soon in the weekly Xiaomi.eu releases. Seems they forgot the haydn doesn't have TWRP yet so you can't actually install it! Tried the updater app no go, it can't boot to recovery because they don't have one yet, even though on Xiaomi.eu they say it's available, can't find it anywhere.
BTW the only TWRPs I can actually find are for Venus and Star.
haydn TWRP is not working: https://androidfilehost.com/?fid=14943124697586336730 remember: fastboot boot twrp-3.5.1-haydn.img ... although I tried everything, this TWRP just doesn't work - you boot right into the system after the fastboot boot step. Tried everything I can think of, always boots to system. Guess it's still a waiting game...
mslezak said:
Yes they released source there are just no instructions anywhere on how to build the kernel #1 and the GKI modules #2 and combine into a build.
Click to expand...
Click to collapse
Just one more question since this has been bothering me; what would be needed from Xiaomi? Instructions on how to build the kernel? Have they ever done this before about something like this? Like, is it a reasonable thing to ask them to release instructions? I know some people working there, I could forward the request.
Well I've run this by many many devs.
The issue with the GKI 1.0 and ACK is that you must download the entire AOSP build environment and make sure it works with the separate ACK (Android Common Kernel) and then properly loads the GKI modules from a separate build step. Together they make 1 kernel. This ACK per Linux Version and across vendors should be AOSP and identical. Therefore, a single build should work across all Linux 5.4 based kernels.
But... most devs are just skipping AOSP and inlining the GKI modules so they can have 1 build step. Not exactly what Google intended, but way less storage, and you can use Clang or GCC or whatever you want.
I think what OEMs are posting is merely the entire combined source code, no 2 step build process. Only a single file for the QGKI config portion. Which won't build your GKI modules as it comes. A build script for this (Q)GKI portion would be extremely beneficial.
If any OEM walks through the build steps 1) how to create only the QGKI modules and 2) how to assemble them into 1 kernel with the ACK, that would be great for devs. It just hasn't happened. So we get hacked kernels for the 888 running Linux 5.4.
The Generic Kernel Image (GKI) project | Android Open Source Project
source.android.com
mslezak said:
Well I've run this by many many devs.
The issue with the GKI 1.0 and ACK is that you must download the entire AOSP build environment and make sure it works with the separate ACK (Android Common Kernel) and then properly loads the GKI modules from a separate build step. Together they make 1 kernel. This ACK per Linux Version and across vendors should be AOSP and identical. Therefore, a single build should work across all Linux 5.4 based kernels.
But... most devs are just skipping AOSP and inlining the GKI modules so they can have 1 build step. Not exactly what Google intended, but way less storage, and you can use Clang or GCC or whatever you want.
I think what OEMs are posting is merely the entire combined source code, no 2 step build process. Only a single file for the QGKI config portion. Which won't build your GKI modules as it comes. A build script for this (Q)GKI portion would be extremely beneficial.
If any OEM walks through the build steps 1) how to create only the QGKI modules and 2) how to assemble them into 1 kernel with the ACK, that would be great for devs. It just hasn't happened. So we get hacked kernels for the 888 running Linux 5.4.
The Generic Kernel Image (GKI) project | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
OK, I see. Thank you for your reply. I am going to see how far I can get this. Tnx again!