still confused when reading the first post,
cause i don't know what should i do....
SE:s service partners flashing software whit that they flash the phones whrn you send them to be maintenanced etc etc...
http://emma.extranet.sonyericsson.com/documents/emma_user_guide.pdf
Whos the first one registering on EMMA team ?
Does it help for rooting the X10? I registered for access. In the manual they write it will up to a week, till a local administrator will give me access.
Well, i got my doubt's... Acording to the manual, it seems to work bit like VAG immobilizer softing... You log in to the manufacture's main computer, and the data needed comes straight from there over the line... Donno if there's any possibility to "stab" the SEUS update file inorder to get the needed result... :/
I'll keep you on update, if I will get registered...Thanks for your info...
I'd love to get a developer firmware...
biktor_gj said:
I'd love to get a developer firmware...
Click to expand...
Click to collapse
thats nice. do you think we care? Leave this forum open for root discussion.
net_vampire32 said:
thats nice. do you think we care? Leave this forum open for root discussion.
Click to expand...
Click to collapse
No need to be rude.
I'd love to get a developer firmware...
Click to expand...
Click to collapse
thats nice. do you think we care? Leave this forum open for root discussion.
Click to expand...
Click to collapse
Funny given the fact it was my idea to open this thread in the first place...
By the way, I said that because it would make it easier to be able to root the device and have a chance of getting a bootloader with less restrictions, but hey, if you don't care...perfectly fine for me, I really don't care what you do think either. (yes, sorry, I know what you always say, don't feed the trolls... I just couldn't resist myself)
Back on topic, all htc phones used to have the serial port shared with the handsfree/usb plug, does anybody know where is the serial port for this phone is? I'd need a full dmesg and check what the bootloader says through serial when it starts... That's how haykuro found a hole for 32A Magic..
I know part of the main board is designed by htc, so unless SE removed it from the final design it should be there somewhere... maybe on the audio jack?
-------------------------------------
Sent via the XDA Tapatalk App
biktor_gj said:
...
Back on topic, all htc phones used to have the serial port shared with the handsfree/usb plug, does anybody know where is the serial port for this phone is? I'd need a full dmesg and check what the bootloader says through serial when it starts... That's how haykuro found a hole for 32A Magic..
...
Click to expand...
Click to collapse
Do dmsg via adb shell... it works.
Ciao Angelo
I know nothing when it comes to rooting, but I do know Android is linux, and the X10 runs kernel 2.6.29, I found an exploit for this kernel but I don't know if it's possible to use on our Android OS??
Here's the link, hope it helps in some way......
http://www.milw0rm.com/exploits/8369
(Update)
Here's one more:
http://www.milw0rm.com/exploits/8678
sorry rough day
biktor_gj said:
Funny given the fact it was my idea to open this thread in the first place...
By the way, I said that because it would make it easier to be able to root the device and have a chance of getting a bootloader with less restrictions, but hey, if you don't care...perfectly fine for me, I really don't care what you do think either.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Blowtoke said:
I know nothing when it comes to rooting, but I do know Android is linux, and the X10 runs kernel 2.6.29, I found an exploit for this kernel but I don't know if it's possible to use on our Android OS??
Here's the link, hope it helps in some way......
http://www.milw0rm.com/exploits/8369
(Update)
Here's one more:
http://www.milw0rm.com/exploits/8678
Click to expand...
Click to collapse
Hi,
the first one will surely not work (a needed configuration option is not set) the other one looks promising.
From balsat -
I'm messing around with a 2.6.29 exploit for the HTC tattoo, it might work on the X10 if they haven't closed the hole.
Root exploit
I uploaded the m7 file to /data/local/bin with "adb push m7 /data/local/bin/m7" opened a shell on the phone with "adb shell" changed the permissions with "adb chmod 755 /data/local/bin/m7" and started the exploit with "cd /data/local/bin" "while `true` ; do /data/local/bin/m7; done" after a while i got this output :
usage: reboot [-n] [-p] [rebootcommand]
exit!
reroc/8446/cmdline[ WIN! 8446
EIP: 70000484 Instruction executed: e01858cd
Wrote shellcode e0400000 line 0
Wrote shellcode e3a07023 line 1
Wrote shellcode ef000000 line 2
Wrote shellcode e0400000 line 3
Wrote shellcode e3a07017 line 4
Wrote shellcode ef000000 line 5
Wrote shellcode e0433003 line 6
Wrote shellcode e28f0014 line 7
Wrote shellcode e50d0008 line 8
Wrote shellcode e50d3004 line 9
Wrote shellcode e24d1008 line 10
Wrote shellcode e24d2004 line 11
Wrote shellcode e3a0700b line 12
Wrote shellcode ef000000 line 13
Wrote shellcode 7379732f line 14
Wrote shellcode 2f6d6574 line 15
Wrote shellcode 2f6e6962 line 16
Wrote shellcode 6873 line 17
Wrote shellcode 0 line 18
[ Overwritten 0x70000484
But i still got NO root, id tell me :
$ /system/bin/id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1011(a db),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt ),3003(inet)
And it somehow ****s with the PATH :
$ ls
ls: not found
$ Cannot set process group (Operation not permitted) at 225
Maybe a hardcore coder can change the program so it will work!?
Click to expand...
Click to collapse
I tried the code this came from myself (before seeing this) and it seems to do something, however I've yet to figure out what the code actually does.
I think since this code works on the tattoo,if someone who know what result we are trying to obtain (other than root I mean) explains it, someone (maybe even myself) could probably get it to work on the SE X10.
Hi, that exploit had to be run inside of a while (don't ask me why, that's what it says in the original exploit @milw0rm and on the post on tattoo forum). It goes over and over, I think until it makes a buffer overflow, then dump you into a root shell.
I didn't get it to work, my theroy is SE patched it (that's why I said on my first post on this thread to notice the build date of the kernel). The real problem we're facing is kernel version 2.6.29 is one year old, and what a lot of android phones have, but the compilation date is March 2010, so they might have patched all the holes people have found until then, so the m7 won't work.
Though maybe it just needs some little modification and I'm completely wrong... wich is absolutely possible too
I just bought some 3.5" 4pin jacks to see if we have a shared serial port on the audio jack... will post if I found something in there!
EDIT: be careful guys,this phone is quite delicate,first try and battery calibration went nuts.. fixed already,but thought you should know...
@net_vampire32: no worries, we all have them sometimes..
How do you compile the shoryuken.c exploit on Windows? Otherwise also on Linux? I would like to try it on my X10.
Till now I haven't got my account for Emma. So I'm still waiting....
For compilig use the Android-NDK (NOT SDK!). Create an Android.mk and Application.mk
If you need an example Android.mk and Application.mk write an PN.
-Bin4ry
This exploit cannot be used because the X10 linux kernel is patched.
I downloaded the X10 kernel sources from the SE web site and I checked the ptrace.c file in the kernel folder. Unfortunately, it is patched.
However, because SE provides the X10 kernel source code, we can easily check if an exploit can be used or not.
mimok said:
This exploit cannot be used because the X10 linux kernel is patched.
I downloaded the X10 kernel sources from the SE web site and I checked the ptrace.c file in the kernel folder. Unfortunately, it is patched.
However, because SE provides the X10 kernel source code, we can easily check if an exploit can be used or not.
Click to expand...
Click to collapse
Hmmm... I ran the m7 exploit twice in two shells. Both quits with an error like @edude03 posted before. So you got no chance to type in commands like id, ls -l , cat.... But if you have got busybox you can excute some more options. So I typed in /data/local/busybox vi /default.prop
My Bash opened it with no problems, but if I'd like to edit via vi, I get errors. On Linux sometime vi sucks also, too. In that cases it's becaus of wrong interpreting the input devices, like keyboard...
Can someone please checkout?
@ardf69
How it can be patched? The exploit works on that kernel -> Linux matthew-desktop 2.6.29-020629-generic #020629 SMP Tue Mar 24 12:03:21 UTC 2009 i686 GNU/Linux
And my X10 Kernel is from -> Linux localhost 2.6.29-rel #2 PREEMPT Wed Mar 10 16:53:36 JST 2010 armv7l GNU/Linux
Please comapre these two dates! Or am I wrong?
Bin4ry said:
For compilig use the Android-NDK (NOT SDK!). Create an Android.mk and Application.mk
If you need an example Android.mk and Application.mk write an PN.
-Bin4ry
Click to expand...
Click to collapse
Thanks Bin4ry! I will try first on my own Thanks for your support!
Related
Okay I posted this also in the Themes forum for Nexus but I wanted to see if anyone could assist. Someone in the theme forum asked about the bootanimation.zip that shows us the cool animation during boot, while reading this it reminded me of the behold 2. See below
What are the permissions for bootanimation.zip if they were left open to non root then this may-b a way to get root with unlocking the bootloader. This would be the same approach that was used to root the behold 2 where the "try3" file was renamed to play_logo . play_logo then was used to root and after root was opened it would make play_logo_real play which was the boot animation. I may be wrong but couldnt this be a possibility. Thanks, any help is appreciated. Im wondering if Zinx could chime in...
How are you going to write to the bootanimation.zip without root? Further, do you intend to replace the recovery or update custom roms? I am just trying to figure out the purpose of root and flashing other customized images.
seraph1024 said:
How are you going to write to the bootanimation.zip without root? Further, do you intend to replace the recovery or update custom roms? I am just trying to figure out the purpose of root and flashing other customized images.
Click to expand...
Click to collapse
You can always write if I am not mistaken using the low-level write dd if/of command. We would use the bootanimation.zip to run the root command. An example is in the Samsung Behold 2 it was done as follows:
Example
echo "#!/system/bin/sh
/data/local/try3 /system/bin/sh
mount -o rw,remount /dev/st9 /system
cat /system/bin/sh > /system/bin/su
chmod 04755 /system/bin/su
/system/bin/playlogo_real" > /system/bin/playlogo
Click to expand...
Click to collapse
This is how it was done. I am wondering if the same can be done on the nexus using bootanimation.zip as it executed at startup. We would basically modify the bootanimation.zip to the above and add a line for it to execute the boot image. By gaining root this way we would still be able to put on a custom recovery and roms without unlocking the bootloader in theroy. The try3 file was created by Zinx and used by Maxisma to bring root to the behold 2. I am pretty sure this may work on the Nexus 1. I hope this helps.
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
seraph1024 said:
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
Click to expand...
Click to collapse
Okay XDA is back up. Yes I can test. Oh man if this works there will be absolutely no need to unlock the boot loader... Thanks
seraph1024 said:
Ok. I don't have a locked phone that I can play with at the moment. I'll make up a package for you tomorrow. Can you test it for me?
Click to expand...
Click to collapse
Hey Seraph1024 take a look at this. Its too big for XDA so I put it up on pastebin. http://pastebin.com/f62780d32 Its what is contained in the try3 file. Zinx used it in flashrec
No joy.
Code:
$ getprop | grep product.model
[ro.product.model]: [Nexus One]
$ pwd
/data/local
$ ls -al try3
-rwxrwxrwx 1 0 0 74512 Jan 25 13:26 try3
$ id
uid=2000(shell) gid=2000(shell)
$ ./try3 /system/bin/sh
[1] Killed ./try3 /system/bin/sh
$ id
uid=2000(shell) gid=2000(shell)
Exploit does not work.
I was that close to rooting today until i saw this now its made me double think again lol I've been waitin for a custom rom by cyanogen until i rooted, and since its pretty much almost here i was going to root. bah guess i'll wait until CM gets released!
flak0 said:
You can always write if I am not mistaken using the low-level write dd if/of command.
Click to expand...
Click to collapse
You can't on this phone. There are two ARM cores - one running the low-level stuff (bootloader, radio) and the other running Linux.
Without the engineering bootloader (or some exploit) we don't have access to the baseband ARM core, and therefore don't have access to its MMU, which is programmed to deny read/write access to protected areas of the flash - such as the bootloader and splash screens. Even with root, Linux can't access that stuff.
It's going to be really hard to find a kernel exploit for the N1 to get root. Most exploits involve mapping memory to the zero page and then triggering a null pointer de-reference bug in the kernel. But the N1's kernel won't allow such mappings.... I believe the minimum address for mmap on the N1 is around 64k. (It's in the kernel config.)
This is a tough nut to crack.
The behold root was done that way because there's no way to flash the partitons on it.
You still need root in the first place to write to that file. The droid guys have been looking a while for a new root exploit but didnt find one. The problem is that all known exploits have been closed in 2.1.
We need to wait for someone to find a new one that works. Then this would be a real posibility, and there' no need to hijack playlogo.
for what its worth, if you need a lab rat i do not have my phone rooted yet and i am willing to test some things if anyone needs...
i dont plan on rooting it until the ball really gets rolling with everything and until I am 100% satisified with the phones performance
kam187 said:
You still need root in the first place to write to that file.
Click to expand...
Click to collapse
That's what I though. And like it was posted earlier, I don't think there is a exploit since this phone is done differently. I am busy for the next couple of days but if anyone want to "try", I'll make up something but I really doubt any of the old stuff will work on this phone.
Hello guys anD GIRLs. semi-N00B here. tehehe. I say semi because I spent the last week learning evvvverything i could about "rootin'" my Area. phew, there's a lot to learn ... but I like to be fairly sure of how things work before I attempt nething./ I just have 1one question, before I do this to my DEVice... How do I flash a rom to my phone if the Aria doesn't support flash? Is there a guide to modifying flash lite for this? I can't find it.
Thanks in advance. Luv yas.
WTF NOOOOB!! YOU POSTED IN THE WRONG SECTION!! UGH. THIS SHOULD FREAKING BE POSTED IN DEVELOPMENT...i swear..noobs..anyways on a lighter note
welcome to the wonderful world of android!! im pretty new myself but have been trying to do this too. ive been reading various wikis and have come up with this(beware i am about to attempt this this weekend myself)
1)you need to be on froyo 2.2 (att official)
2)you need to pull out flashlite.apk using the android sdk
3)you need to decompile flashlite.apk with baksmali
4)you need to delete the flash files and replace them with romflash.txt
5)recompile with smali and rename it to romflash.apk
6)push it with adb
7)FLASH ROMS AND SCORE!!!!
good luck!! and hope to see moar of u around the forums!
YAY ROM FLASHERZ
ps. does anyone know what cm7 is? can you explain it to me? the guides arent telling me enough...
ps.s to the OP-heres a wonderful guide if smali is to complicated. this tool can help you decompile flash lite and works wonders!!
miui-au. co m/ add-ons/ apktool/(cant post links yet..sorr)
I'm not sure what Megamansrighthandman is talking about, but it isn't correct.
It sounds like both of you are confused about the use of the word "flash". Be careful with the terminology. When someone talks about "flashing a ROM", that simply means installing a ROM. It has nothing to do with Adobe Flash or HTC's Flash Lite. I understand the confusion though. I hope this clears things up.
The process for setting up your phone to be able to install custom ROMs basically breaks down to these steps:
1) "Root" the phone. This is accomplished by using the Unrevoked tool from a computer. There is more information about this in the other sections of this forum. This can only be done on phones that do NOT have the official Android 2.2 update installed. If you have 2.2, you can't root without special hardware.
2) Once "rooted", you can download ROM files and install them through the Clockwork recovery. Installing a ROM is generally referred to as "flashing" (there is a reason it is called this, but it has nothing to do with Adobe Flash).
Wait!! I need 2.1 not 2.2?? I had 2.1 but updated because megamanstightgland told me too. can I still use his methode, since i started already? i was at step 2 and didnt know how to pull out nething (im a girl so i never had to do that b4 tehehe) i didnt want too ask two many noob questions, so i ended up to googling searching his steps to figure out how to do some of them. (i think he meant abd not sdk) here's what I did after updating to 2.2....
[email protected]:~$ sudo su
[sudo] password for luvsmyBfdick:
[email protected]:/home/luvsmyBfdick# sh abd pull flashlite.apk
sh: Can't open abd
[email protected]:/home/luvsmyBfdick# dm -f pull abd out -m flashlite.apk /system/data
dm: command not found
[email protected]:/home/luvsmyBfdick# chmod -v remount adb pull* flashlite.apk /homo/user/system
chmod: invalid mode: `remount'
Try `chmod --help' for more information.
[email protected]:/home/luvsmyBfdick# --help
--help: command not found
[email protected]:/home/luvsmyBfdick# -x <85> /tools/win/usb drivers -r/w flashlite.apk
bash: syntax error near unexpected token `85'
Do you think there is a problem with my permission? I have a flash drive (not adobe) with updated permissions on it, but i canot currently find it.
ps. it's not like i wasnt prepare. i installed linux yesterday in my computer cause i read it make this easier... just trying to surprise my boyfriend with a rooted area for his birthday sunday. thanks so much for the help so far guys. your great!
now im readin that i have to be in root on my phone, not just my computer, to do meganmanswhitechesttanned's methode. i really need to help with one of you geeks. ;(
This is the most random troll thread I've ever seen.
drumist said:
This is the most random troll thread I've ever seen.
Click to expand...
Click to collapse
I couldn't agree more.
I had a so-called "wtf-moment". Apparently a girl with this PC: luvsmyBfdi[email protected] wants to be taken seriously with a question...
I'm thinking this is some weird troll thing...
Closed.
Anyone know how to root a Sharp SH-02E (ICS 4.0.4)? Even a temporary root is fine, I only want to install a particular apk in /system/app.
Many thanks.
I am looking for the Sharp Aquos Zeta root also, not for me but for my friend
I'll subscribe here and repost if I find something somewhere else.
Try this
http://forum.xda-developers.com/showthread.php?t=1886460
:thumbup:
DPK
Sent from my Android Smartphone
dkmali said:
Try this
http://forum.xda-developers.com/showthread.php?t=1886460
:thumbup:
DPK
Sent from my Android Smartphone
Click to expand...
Click to collapse
Tried and failed.
There's a discussion on a Japanese BBS that I think is onto something. Unfortunately there's a stupid rule here that means I can't post a link to it. The page title is '【ROM焼き】docomo AQUOS PHONE ZETA SH-02E root1' and it should be the top result on Google for 'sh-02e root'. The fun starts at post 75.
If we can just get ROOT and Custom Recovery on this device - it simply becomes the most powerful and advanced communicator in the world.. However no root - no life..
Two things:
Any luck with a custom recovery yet?
And can anyone dump the kernel and stock rom?
Happy to give it a crack...
Sent from my SPH-L900 using Tapatalk 2
Updating Aquos Phone
jaseli said:
Tried and failed.
Click to expand...
Click to collapse
Did you manage to get update 01.00.05 anyhow flashed outside Japan?
http://www.nttdocomo.co.jp/support/utilization/product_update/list/sh02e/index.html
jauhien said:
Did you manage to get update 01.00.05 anyhow flashed outside Japan?
http://www.nttdocomo.co.jp/support/utilization/product_update/list/sh02e/index.html
Click to expand...
Click to collapse
it is currently impossible to upgrade this phone out of Japan.
i am still on 01.00.03
I have a sh203 and I would like to root my phone also
>_<
Arrgh, this is so frustrating. You look on the 2ch thread and you can see they've done it. Temp root, MIYABI permanent root, they've done it all. The instructions aren't too hard to follow but I cannot for the life of me find the password (キーワード) required to download the files from axfc.net. If I had those files I could root the phone and post a guide here in English. For goodness sake it's staring me right there in the face and there's not a thing I can do about it. And of course because this is XDA, I can't even post you a link to the thread. It's the same thread title as earlier. You want to start from post 542 onwards, if you want a try yourself.
WithLoveFromExIA said:
Arrgh, this is so frustrating. You look on the 2ch thread and you can see they've done it. Temp root, MIYABI permanent root, they've done it all. The instructions aren't too hard to follow but I cannot for the life of me find the password (キーワード) required to download the files from axfc.net. If I had those files I could root the phone and post a guide here in English. For goodness sake it's staring me right there in the face and there's not a thing I can do about it. And of course because this is XDA, I can't even post you a link to the thread. It's the same thread title as earlier. You want to start from post 542 onwards, if you want a try yourself.
Click to expand...
Click to collapse
yes , please guide me how to root the phone permantly , thanks a lot !!
OK I've made some progress. I've got a temporary root, and am three hex numbers away from a full root. You'll need
The Sharp USB drivers, that are on Sharp's developer site.
ADB, as usual
The guide itself, which I can't like to. Post 672 on the 2ch thread.
The extra files, likewise. Post 680.
.
It's well written and pretty straightforward. Only minimal use of Google Translate will be necessary.
In the guide you'll find three lines of the form
Code:
./acdbwritevalue <address> <value>
where <address> and <value> are hexadecimal numbers.
The problem is that the guide is written for build number 01.00.05, the latest one. Unfortunetely I'm stuck on 01.00.03, so while the <value> numbers are the same, the <address> numbers are differrent, and I need to find the right ones. If you're on 01.00.05 feel free to go through the guide and share your results. Alternatively, if you know how to force the phone to update without being in Japan on Docomo, please share that too.
WithLoveFromExIA said:
OK I've made some progress. I've got a temporary root, and am three hex numbers away from a full root. You'll need
The Sharp USB drivers, that are on Sharp's developer site.
ADB, as usual
The guide itself, which I can't like to. Post 672 on the 2ch thread.
The extra files, likewise. Post 680.
.
It's well written and pretty straightforward. Only minimal use of Google Translate will be necessary.
In the guide you'll find three lines of the form
Code:
./acdbwritevalue <address> <value>
where <address> and <value> are hexadecimal numbers.
The problem is that the guide is written for build number 01.00.05, the latest one. Unfortunetely I'm stuck on 01.00.03, so while the <value> numbers are the same, the <address> numbers are differrent, and I need to find the right ones. If you're on 01.00.05 feel free to go through the guide and share your results. Alternatively, if you know how to force the phone to update without being in Japan on Docomo, please share that too.
Click to expand...
Click to collapse
Although I haven't got SH02E, I have found some extra files, which was mentioned in the Japanese guide for root, expect Busybox, enjoy.
The best phone of 2013 on the worse company in the world
Tommi_Vercetti said:
Although I haven't got SH02E, I have found some extra files, which was mentioned in the Japanese guide for root, expect Busybox, enjoy.
Click to expand...
Click to collapse
Thanks a lot. Luckily I came to Japan for Vacation and was able to find someone else to lend me a Usim card to update. DoCoMo are worse than Motorola, Apple and ATT when it comes to restricting your phone. Hell, I can't even use the native FM function without DoCoMo. How can Sharp expect to come out of the hole of bankruptcy when doing this sort of business? Look at the crappy Samsung company. Awful phones that everyone buys because they decided to be "untied" to companies at the beginning and for that reason they owned the market.
If Japan is really serious into getting its technological market back, better start uncopying the USA practice of enslaving their phones and tablets to telecomunication companies.
It's a shame that the best phone right now, the Sharp Aquos Zeta Sh-02e, with its awesome new screen and specs, is going to the trash as if it was a failure, just because they don't make deals with companies outside Japan.
16MPixel CAMERA!!! IGZO ultra clear screen!!! Quad Core!! 2gb Ram!! all the specs of all the other phones plus like 30 that none of them have!! A total shame, Sharp!
Find it carefully and you will find a good guy have written a script for temp root, I used the script to have my SH-02E rooted.
And, as far as I can read the topic, the unlock file is for NAND crack and may write to recovery area.
I don't test that coz of warranty, the reason I want to root is to put some message backup back(something like LINE) and remote control (VNC server for example)
And, yes, you can find the temp root solution for both 1.0.4 and 1.0.5, but no 1.0.3, good luck!
Do you have some files for rooting sh02e 1.00.04
rotalume said:
Find it carefully and you will find a good guy have written a script for temp root, I used the script to have my SH-02E rooted.
And, as far as I can read the topic, the unlock file is for NAND crack and may write to recovery area.
I don't test that coz of warranty, the reason I want to root is to put some message backup back(something like LINE) and remote control (VNC server for example)
And, yes, you can find the temp root solution for both 1.0.4 and 1.0.5, but no 1.0.3, good luck!
Click to expand...
Click to collapse
Do you have some files for rooting sh02e 1.00.04, I think many guys here are needing the solution
Hi rotalume
thanks for the note... can i ask a favor? i really need some help to install the SH-02E driver in windows.
tried to download the file from sharp's web, but after executing the install exe file, a bundle of unreadable signs come out, and i check my device manager, there is not SH-02E USB handler or SH-02E modem. I just want to make use of Helium (backup) to extract / restore apps and data...
thank you for your help in advance.
P.S. I guess to get the temp root script pushed to SH-02E, this driver is essential as well.
thanks again
jaseli said:
Hi rotalume
thanks for the note... can i ask a favor? i really need some help to install the SH-02E driver in windows.
tried to download the file from sharp's web, but after executing the install exe file, a bundle of unreadable signs come out, and i check my device manager, there is not SH-02E USB handler or SH-02E modem. I just want to make use of Helium (backup) to extract / restore apps and data...
thank you for your help in advance.
P.S. I guess to get the temp root script pushed to SH-02E, this driver is essential as well.
thanks again
Click to expand...
Click to collapse
The one you've installed is not ADB Driver, check ADB driver at developer site(I'm to young to post a link )
File name will be given as this form : usb_driver_SHARP_r6.10.zip
Download and extract, then install the driver by device manager.
And, I've used Carbon before but in vain coz of ADB driver(the author had told me), I don't know if this issue has been solved.
For the files, sorry guys, I've found someone at other forums has used them for commercial purpose(it's a shame that ppl of my country is included), so the best I can give is to tell you the clue.
You can post your question and I will do my best, but no file will be provided atm.
Downloaded Sharp Aquos Zeta ADB drivers for SH-02E
rotalume said:
File name will be given as this form : usb_driver_SHARP_r6.10.zip
Click to expand...
Click to collapse
I was able to find and download that driver by just selecting the name you wrote and making a search on Googl. It was the very first result. thanks a lot. Although I would love the name of the script or the title of the page you downloaded it from.
Thanks a lot.
"Blobs" are the files specific to each device that we need in order to compile custom ROMS that work on our device. The process of finding them is tedious and slow... I have been picking away at them for months when I have time. There are over 600 files so far! But there are also references to files that are not being found. They are either missing, or they are not located where they are expected to be located. This is where I need help.
So, if you want to help, go HERE:
https://github.com/mightysween/android_vendor_motorola_payton
and look through the proprietary-files.txt file for anywhere that it says "warning".... and then search inside of the firmware (working on 8.0+ now, not 7.1 please) and try to track down the file that it says is missing [obviously, you will need a system dump, or to search on a rooted device]. If you find it, please post below like this:
LINE NUMBER OF THE WARNING (from github)
PATH TO THE MISSING FILE (relative to /system... in other words, don't inlude your own local path)
Once this file is complete, we can use it to automatically pull the correct vendor files into our build environments... having a working recovery, active kernel developement and completed vendor blobs should open us up to more development efforts.
Also, if anyone has done any testing and knows of other proproetary files that are needed, please post them here so I can include them.
My time at the computer to work on this is really limited, so I have only identified a dozen or so daemons that definitely call for proprietary libs... I am sure there are more
I would love to pitch in on this but have zero experience with anything related to development. Do you think I could still be of help? Sounds like a basic enough task that it wouldn't be too difficult. Let me check and see that I understand the process.
Went to github and looked at proprietary-files.txt. The first warning I found was in line 49: "blob file libpn553_fw.so missing or broken". Then searched for that file in my device's system folder using ES File Explorer with Root Explorer enabled.
So is this what you're looking for?
49
/system/vendor/firmware/libpn553_fw.so
---------- Post added at 14:31 ---------- Previous post was at 14:07 ----------
I'd like to contribute in some way but if this is best not left to a complete noob then I totally understand
mightysween said:
Also, if anyone has done any testing and knows of other proproetary files that are needed, please post them here so I can include them.
My time at the computer to work on this is really limited, so I have only identified a dozen or so daemons that definitely call for proprietary libs... I am sure there are more
Click to expand...
Click to collapse
Do you have a link to a system dump?
TheBassDude said:
I would love to pitch in on this but have zero experience with anything related to development. Do you think I could still be of help? Sounds like a basic enough task that it wouldn't be too difficult. Let me check and see that I understand the process.
Went to github and looked at proprietary-files.txt. The first warning I found was in line 49: "blob file libpn553_fw.so missing or broken". Then searched for that file in my device's system folder using ES File Explorer with Root Explorer enabled.
So is this what you're looking for?
49
/system/vendor/firmware/libpn553_fw.so
---------- Post added at 14:31 ---------- Previous post was at 14:07 ----------
I'd like to contribute in some way but if this is best not left to a complete noob then I totally understand
Click to expand...
Click to collapse
Thanks, that is all there is to it
Just time consuming (especially after the first 500)...lol
QWZR said:
Do you have a link to a system dump?
Click to expand...
Click to collapse
Nah, too big to conveniently upload... but if you are rooted, you can use the phone to search
mightysween said:
Nah, too big to conveniently upload... but if you are rooted, you can use the phone to search
Click to expand...
Click to collapse
Mine gets here next week
mightysween said:
Nah, too big to conveniently upload... but if you are rooted, you can use the phone to search
Click to expand...
Click to collapse
If you have root on the system you can find the files for, you should be able to find any given filename with:
find / -name "filename" -print
And it should output any filenames that match. I don't have time at the moment to dig into this any more, but would this resolve much of it?
ebrandsberg said:
If you have root on the system you can find the files for, you should be able to find any given filename with:
find / -name "filename" -print
And it should output any filenames that match. I don't have time at the moment to dig into this any more, but would this resolve much of it?
Click to expand...
Click to collapse
Any way that works is fine by me
I am on the road a lot and just don't have enough time to sit and work on it... so it is taking months. I bet a few people helping could finish it in a matter of hours.
I am hoping to have a few hours next week to work on it. But the sooner this is done, the sooner I can shift to trying to compile Lineage OS with working hardware.
BTW, Lineage *does* compile if I comment out all the stuff causing make errors... not much works, obviously.
The next step will be compiling with these blobs, then logging all the new errors and chasing down all the additional broken symlinks... and then adapting the kernel as needed.
Then, MAYBE we can get a base Lineage tree up and open up the X4 to building for other roms. I know someone started a skeleton tree for Carbon already on Github... they are likely just waiting for the completed device tree, too.
mightysween said:
Thanks, that is all there is to it
Just time consuming (especially after the first 500)...lol
Click to expand...
Click to collapse
ebrandsberg said:
If you have root on the system you can find the files for, you should be able to find any given filename with:
find / -name "filename" -print
And it should output any filenames that match. I don't have time at the moment to dig into this any more, but would this resolve much of it?
Click to expand...
Click to collapse
I don't own this device yet, but I was thinking of getting one. I figured this might help you all out (you'll need to be running linux):
First, let's get a list of all the files on the phone, to make searching faster.
Code:
adb shell
su
find / > /sdcard/allfiles.txt
exit
exit
adb pull /sdcard/allfiles.txt
Now you should have allfiles.txt on your machine. Also grab the proprietary-files.txt, and then run this:
Code:
grep -Po '(?<=(blob file )).*(?= missing or broken)' proprietary-files.txt | xargs -I @ grep "@" allfiles.txt
That should find the paths of all the missing files (except the ones marked "wildcard")
BLuFeNiX said:
I don't own this device yet, but I was thinking of getting one. I figured this might help you all out (you'll need to be running linux):
First, let's get a list of all the files on the phone, to make searching faster.
Code:
adb shell
su
find / > /sdcard/allfiles.txt
exit
exit
adb pull /sdcard/allfiles.txt
Now you should have allfiles.txt on your machine. Also grab the proprietary-files.txt, and then run this:
Code:
grep -Po '(?<=(blob file )).*(?= missing or broken)' proprietary-files.txt | xargs -I @ grep "@" allfiles.txt
That should find the paths of all the missing files (except the ones marked "wildcard")
Click to expand...
Click to collapse
Thanks, I had recently completed this, but your code worked fantastic for double checking, and actually helped me find one that I had missed :good:
Now, on to identifying any more daemons that need proprietary files... and then assembling the tree itself... PROGRESS!
PHASE 1 is complete!
https://github.com/mightysween/android_vendor_motorola_payton
I am 99% sure that this is only ~75% of what will be needed to actually build LOS15. But it is a good foundation to work off of now.
My plan is to start attempting to compile LOS and take error logs to chase down the remaning missing stuff. LOTS to be done still to get to that point...hoping for some other builders/devs to materialize here and help out
Hi! Just a question: it´s mandatory to use A/B partition scheme to build a custom ROM for this device or it will be possible to use a traditional partition scheme and free up some GBs of internal storage for use?
christianrj said:
Hi! Just a question: it´s mandatory to use A/B partition scheme to build a custom ROM for this device or it will be possible to use a traditional partition scheme and free up some GBs of internal storage for use?
Click to expand...
Click to collapse
It would seem that we will still be stuck with A/B, as the bootloader does the initial check of the active slot. Perhaps there may be some clever ways around this in the future...but nothing I will be tackling.
mightysween said:
It would seem that we will still be stuck with A/B, as the bootloader does the initial check of the active slot. Perhaps there may be some clever ways around this in the future...but nothing I will be tackling.
Click to expand...
Click to collapse
You would probably need a custom kernel to do it properly. The bootloader passes a kernel param (androidboot.ro.boot.slot_suffix) specifying which slot to use. In the absense of a kernel param, the value is read from the ro.boot.slot_suffix build property.
That being said, you might be able to just repartition your device to only have 1 slot, flash your ROM, and use
Code:
fastboot --set-active=_a
. If your ROM has disabled OTA updates from the OEM, you should be fine.
I'm going to get an X4 in the coming weeks. I'd like to help with this soon. I'm a seasoned developer by trade and can collab on GitHub. Hope to be able to start working with you soon. :good:
I don't know if any of you have seen this article, but it seems promising that it might not be too difficult to achieve for this device:
https://www.xda-developers.com/xiaomi-redmi-note-4-project-treble/
Hariiiii said:
I don't know if any of you have seen this article, but it seems promising that it might not be too difficult to achieve for this device:
https://www.xda-developers.com/xiaomi-redmi-note-4-project-treble/
Click to expand...
Click to collapse
@vache at the Moto G5 Plus forums has already managed it using the /oem partition which is otherwise unused for custom ROMs
Hariiiii said:
I don't know if any of you have seen this article, but it seems promising that it might not be too difficult to achieve for this device:
https://www.xda-developers.com/xiaomi-redmi-note-4-project-treble/
Click to expand...
Click to collapse
Cool... seems it may be possible. Will follow the progress on the Redmi and G5 devices
navenedrob said:
I'm going to get an X4 in the coming weeks. I'd like to help with this soon. I'm a seasoned developer by trade and can collab on GitHub. Hope to be able to start working with you soon. :good:
Click to expand...
Click to collapse
The more I am reading about enabling Treble, the more I think it is entirely possible.... and probably the best direction to focus our efforts.
Seems like we have partitions that could be used as /vendor. I am reading up on exactly how the Treble vendor partition is set up. Tricky, but not implausible.
EDIT: Actually, none of the partitions we could potentially re-purpose for /vendor are big enough. So, it may be harder on this device than on others. It may require repartitioning.
I'm so I'm just kind of putting this information out there I haven't got to go through it yet on the breakthrough of this knowledge I figured I should just make a post so people can get into it as quickly as possible it does look like the phone is running the same recovery set up as the sm8250 at least it has an entire file directory based on that number there's a lot of interesting files in therehow I got to them = (adb shell [then] cd ./sys/module/ [then] ls --color=auto -a [you should see all the files/dirs]) anyways I'm going to keep doing what I do and try to figure out this thing Happy hunting good luck people
AkayamiShurui said:
I'm so I'm just kind of putting this information out there I haven't got to go through it yet on the breakthrough of this knowledge I figured I should just make a post so people can get into it as quickly as possible it does look like the phone is running the same recovery set up as the sm8250 at least it has an entire file directory based on that number there's a lot of interesting files in therehow I got to them = (adb shell [then] cd ./sys/module/ [then] ls --color=auto -a [you should see all the files/dirs]) anyways I'm going to keep doing what I do and try to figure out this thing Happy hunting good luck people
Click to expand...
Click to collapse
can you do me a favor and pull the file from your that is called "oplus_locking_strategy" ... this may be to a bootloader unlock. For some reason i dont have this file on mine, but also my bootloader i unreachable... id appreciate it thx...
( a simple "adb pull ./sys/module/oplus_locking_strategy /sdcard/oplus_locking_strategy" should do it... then if you can dm me that would be spectacular! thx)
beatbreakee said:
can you do me a favor and pull the file from your that is called "oplus_locking_strategy" ... this may be to a bootloader unlock. For some reason i dont have this file on mine, but also my bootloader i unreachable... id appreciate it thx...
( a simple "adb pull ./sys/module/oplus_locking_strategy /sdcard/oplus_locking_strategy" should do it... then if you can dm me that would be spectacular! thx)
Click to expand...
Click to collapse
I can do you better I can give you the suppository to the phone models so you can just download every file from the phone it even has a link to build the phone with twerp plus it has to build tree files as well >Dumpfiles<
i think i have what you are referring to... i downloaded the original source for our phone, but it does me no good with a locked bootloader because the source does not include the android signing keys. If it did that would be VERY BAD for oneplus cuz anyone could forge updates packages. but afaik that file is not in the source build. i believe it is an after - addon offered to carriers
I can send you a copy
AkayamiShurui said:
I can send you a copy
Click to expand...
Click to collapse
dm sent