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 everyone!
You may or may not know me, however I have secretly been working behind the scenes with ChiefzReloaded to learn how Android works. Together we have been trying to develop new ways to root the Slide, primarily because we both landed in a sticky situation that left us both without root and without a way to revert to root.
After many long hours of trying to restore my phone, I have now ported the exploid exploit to the MyTouch Slide! This means that you can gain root on any version of the Slide, INCLUDING the latest OTA! However, this isn't necessarily "easy" as in the One-Click Root program, but there are reasons for this. While Android is running we cannot write to /system and even if we force Linux to let us, the NAND protection will prevent Linux from completing the write!
To get started, please see the bottom of this post for the link and download it. You will want to download it to your computer and not your phone's SD card. Also, you will need the tools from the Android SDK. I would suggest extracting the file from my zip at the bottom of this page into the Android SDK's tools directory.
Extract the zip
Make sure your phone is in USB debugging mode AND you are in "Charge Only" mode.
Connect your phone to your computer.
Make sure you're in the same directory as where exploid is extracted before continuing to the next step.
Issue the following command: adb push exploid /sqlite_stmt_journals. Note: It MUST be in that directory - NO exceptions.
Run: adb shell
Run: cd /sqlite_stmt_journals
Run: chmod 0755 exploid
Run: ./exploid
Toggle your phone's Wifi (on or off, however you wish to do that).
Now (again) run: ./exploid (if prompted for a password enter: secretlol)
The next line should now begin with a pound (#) - if not, then something isn't setup right. Make sure to follow the directions verbatim. If you suspect you did follow them correctly, please reply to this post letting me know.
You should now be root! At this point you can do many things, but if you're looking to flash a custom ROM, continue to these instructions:
[NEW 10/18/2010:]
Steps 1-12 are intended to get you the ability to flash mtd0.img (which previously required using the SimpleRoot method) by gaining root inside of Android. By following the instructions in the rest of this section, it will allow you to flash a ROM or S-OFF your device:
The files you need are at: http://forum.xda-developers.com/showthread.php?t=703076- download both files linked in there (ESPRIMG.zip and SlideEng-package.zip)
Extract the contents of SlideEng-package.zip to a place of your choosing on your computer.
Place the entire (unextracted) ESPRIMG.zip on your SDcard.
Now push the files 'flash_image' and 'mtd0.img' that you just extracted from SlideEng-package.zip to /data/local using 'adb push'. (Noob? Instead of using 'adb push', install Droid Explorer and, using that utility, copy the 'flash_image' and 'mtd0.img' files to /data/local on your Slide)
Now I'm going to assume your phone is at root prompt (#) using steps 1-12. So now do (without typing the '#' symbols in front of both lines - they're just there to remind you that you need to be at a '#' prompt):
Code:
# cd /data/local
# chmod 04755 flash_image
# ./flash_image misc mtd0.img
Before you reboot make sure that the ESPRIMG.zip is on your SDcard!
Now turn off the phone.
Then press Volume-Down + Power.
The phone will power on and after about 5 minutes of verifying ESPRIMG.zip it will ask you if you want to flash it.
Press Volume-Up for 'YES' and wait until it finishes (ABSOLUTELY DO NOT POWER DOWN WHILE IT'S STILL FLASHING!!!).
Now when you go into recovery it should allow you to 'Apply update.zip from sdcard' (booting into Clockwork). If you don't have the Clockwork update.zip, here it is: http://www.4shared.com/file/OTRU7T3y/update_2.html (rename to update.zip after downloading since it's currently update_2.zip, then place it on your sdcard).
[/NEW 10/18/2010]
[NEW 12/30/2010]
Optional: Now that you're rooted you might want to disable all flash memory protections so you can permanently flash Clockworkmod (recovery - no more using an update.zip!) as well as other random things. Check here for details: http://forum.xda-developers.com/showthread.php?t=798168
[/NEW 12/30/2010]
CREDIT GOES TO:
[*] ChiefzReloaded! (For helping me learn the intricacies of Android and patiently answering all of my questions)
[*] 743C (For developing the original exploit)
Source code: (Yes, it's hackish. I was just trying to figure out why the system kept rebooting and haven't cleaned up the code since) download
DOWNLOAD:
http://www.4shared.com/file/CZsxSq-f/exploid.html
DONATE:
(Anything helps!)
(Some people may wonder why this is special compared to the One Click Root application. What's important is that One Click Root doesn't work on Slides running production/retail software, likely the same problem I had to fix to get exploid to work in my version.)
Thats whats up!!
If you be trollin then YOU BES TRAWLLIN
But if not then good job nb!
Sent from my T-Mobile myTouch 3G Slide using XDA App
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
falken98 said:
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
Click to expand...
Click to collapse
Sure, I was getting around to that - and I understand your concern. I'll post it in a second.
falken98 said:
Can you provide the source? No offense, but I tend not to run homebrew C programs that I didn't compile myself.
Thanks for all the work!
Click to expand...
Click to collapse
You think nb is distributing a virus disguised as a root method?
Waaaaaat
Sent from my T-Mobile myTouch 3G Slide using XDA App
r0man said:
You think nb is distributing a virus disguised as a root method?
Waaaaaat
Click to expand...
Click to collapse
It is a bit funny, but I do understand his concern. I've posted the source code into the original post. Compiling it should result in the same hash as the binary I posted.
Good to see this I suggested this in another thread glad to see it in use thanks a bunch
nbetcher said:
It is a bit funny, but I do understand his concern. I've posted the source code into the original post. Compiling it should result in the same hash as the binary I posted.
Click to expand...
Click to collapse
Ill take a look at it when I get home.
ilostchild said:
Good to see this I suggested this in another thread glad to see it in use thanks a bunch
Click to expand...
Click to collapse
I actually had to do a lot of work on it. It doesn't quite work the same as the original exploid simply because the original exploid crashes the entire system and reboots. This causes the rootshell to never be committed to NAND and thus you get no where. I had to keep playing with things until I found a different method that works. It took several hours of me being upset with it, but watched the latest Burn Notice, came back to it, and BAM I had a stroke of genius.
where is rootshell? i can't exicute rootshell nor can i "cp" any files from sdcard however i do have a # instead of a $
Armyjon88 said:
where is rootshell? i can't exicute rootshell nor can i "cp" any files from sdcard however i do have a # instead of a $
Click to expand...
Click to collapse
Ignore that portion of the instructions provided by the program. As I stated, this is not intended for non-developers at this point. The # is your indication that you're running as root.
I am headed to work, but I don't usually have much going on there - I will be setting up a much cleaner system/environment for non-developers to work with and perma-root their phones with over the next few hours. Stay tuned!
Sweet
Sent from my T-Mobile myTouch 3G Slide using XDA App
having # and running as root as stated before u can actually follow with eng and then custom recovery and ur choice's rom..pls correct me if im wrong..thanx
statuzz said:
having # and running as root as stated before u can actually follow with eng and then custom recovery and ur choice's rom..pls correct me if im wrong..thanx
Click to expand...
Click to collapse
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
nbetcher said:
Ignore that portion of the instructions provided by the program. As I stated, this is not intended for non-developers at this point. The # is your indication that you're running as root.
I am headed to work, but I don't usually have much going on there - I will be setting up a much cleaner system/environment for non-developers to work with and perma-root their phones with over the next few hours. Stay tuned!
Click to expand...
Click to collapse
Let me know if you want to work together on some kind of one-click root app for the Slide. If the commands work through the terminal on the phone itself rather than via adb, I could probably make this into an app already, but since you're working on a more non-developer-friendly version, I'll just wait until that's out
televate said:
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
Click to expand...
Click to collapse
I'm delaying the release of my non-developer program for another couple hours.
As far as what you said above, all you need to do after gaining the # prompt is (in a separate window):
adb push flash_image /data/local
adb push mtd0.img /data/local
(switch back to your # adb shell, then type
cd /data/local
chmod 04755 flash_image
./flash_image misc mtd0.img
Then reboot and apply the ESPRIMG.zip. All of these files are found on the same post that I referenced in my OP. These instructions are all in that same page.
televate said:
i'm also wondering the same thing, because i got the exploid working, and i have the # in the shell, but when i go to follow the instructions to flash the eng-release, i can't cd to any different dirs, nor can i push any files to the phone. i have the ESPRIMG.zip copied to my sdcard, so could i just reboot into recovery and flash the nbh from there? any help is appreciated.
Click to expand...
Click to collapse
Im also stuck since im not sure if you can update to eng from the ota..But first i want to personally thank the OP & CR for providing this.
This would be great for a One Click method
this would be nice to work into a one click root!
And This did work for me!
Does this root method gets /system moumted when android running?In short do we finaly get metamorph and root explorer working?
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.
I see random postings from others that also have the Motorola Electrify and was hoping to start a thread where Electrify owners could post a little information as to those things already developed for the Photon that work (or do not work) for our sister phone. Personally, I was a little apprehensive about diving in and applying mods haphazardly without some other brave soul taking the leap first.
I can confirm that the AIO root method by shabbypenguin (LINK) works on the Electrify and I would have commented in that thread, but my noobness on this site did not allow me to do so in the dev topics. I actually saw another Electrify owner's post confirming this, not on xda, but rather in comments on the youtube AIO root Video Instructions (thanks qbking77).
I had previously tried the root with dock method by edgan, but was unsuccessful.
My hope is that mods will allow this post to continue and that other Electrify users might find it useful and likewise contribute.
Thanks
note: I have started to add some links in post #3 below to some Electrify-specific information.
I thought I would mention that my local US Cellular has promotional pricing (-25%) on the HD Dock and Vehicle Navigation Dock for the Electrify which retail for $100 and $60 respectively. I have no idea if these are compatible with those made for the Photon, or vice versa.
Here is some basic info from the About Phone screen for the Motorola Electrify:
Motorola Electrify model MB853
Stock System version 45.1.167.MB853.USC.en.US
Android Version 2.3.4
Baseband Version n_01.10.00s.xj
Webtop Version WT-1.2.0-131-4
Kernel Version 2.6.32.9-00010-ge26b22b
[email protected]#2
Build number 4.5.1A_SUN_USC_16.7
PRL Version 15112
---------------------------
LINKS:
Link to Motorola Electrify kernel.img: HERE
Link to Stock (USC) Motorola Electrify System Dump (not cwm flashable)
and Deodexed version (cwm flashable - by shabbypenguin) in dev forums.HERE
Team US Cellular Electrify Forum - for confirmation of working mods, many originally posted on XDA.
Stock Motorola Electrify SBF File - for unrooting and re-locking bootloader
Motorola Owner's Forum for ELECTRIFY
Motorola Product Support page for ELECTRIFY
Motorola Media Link for Windows
ZumoCast for Windows by Motorola
If there is other information that might assist devs in determining compatibility for projects already developed or in development, please advise (but please be specific, as I take my noobivity seriously).
try flashing cwm, i would imagine youll be fine from that. but the big test will be if my kernel works/boots yall's phone
A full system dump would be great...
Requirements:
- Rooted Electrify
- Android SDK
Instructions:
- Connect via adb and issue the following commands:
Code:
adb shell
su
busybox tar czvf /sdcard/systemdump.tgz /system
exit
exit
adb pull /sdcard/systemdump.tgz
- Upload systemdump.tgz to a file sharing host like MultiUpload, Filesonic, etc. and post the link here.
Thanks!
actually a better way to do it would just use dd so i could get stock kernel and see if there is any if at all differences.
Question...is 4G Wimax and on Sprints /Clears wimax network?...im just hoping this phone and the photon in japan on kdd may give some hints or help with fixing the broke wimax when unlocked and also gsm radio rom that will work in the us
Sent from my MB855 using XDA App
Well, now I understand why I'm over here posting in the "General" section and not the development threads
I've spent the last several hours reading and installing the SDK only to discover I can't even figure out how to get it configured properly. I will succeed, but I'm too tired right now to continue and have other things to do later today. I'll try to provide more information as soon as I can get back to it.
And thanks Beach_Head and shabbypenguin for your interest and assistance.
just cheat, in the AIO root there is adb.exe and two dll files, toss them in your user's folder ( C:/Users/yourusernamehere) then you can just hit teh windows key and r. type in cmd hit enter, and you will be in command prompt in a directory with adb available (no sdk installing needed )
Beach_Head said:
A full system dump would be great...
Requirements:
- Rooted Electrify
- Android SDK
Instructions:
- Connect via adb and issue the following commands:
Code:
adb shell
su
busybox tar czvf /sdcard/systemdump.tgz /system
exit
exit
adb pull /sdcard/systemdump.tgz
- Upload systemdump.tgz to a file sharing host like MultiUpload, Filesonic, etc. and post the link here.
Thanks!
Click to expand...
Click to collapse
I get an error using the "busybox tar czvf" entry:
tar: invalid option --z
BusyBox v1.18.0.git multicell binary
??
I'll be away from the computer the rest of the day till late. Thanks again for the help. BTW, following shabbypenguin's adb "cheat" and got command window, but did not realize I needed to open superuser on the device to accept permissions (kept getting denied - duh)
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/eletricfykernel.img
upload that for me please
you can then use dd to copy the rest of the phone
It looks like your BusyBox build doesn't include gzip. Where'd you get it from?
Anyway, download Busybox by Stericson from Market and install a newer BusyBox build.
That command will work guaranteed...
Thanks!
drenner99 said:
I get an error using the "busybox tar czvf" entry:
tar: invalid option --z
BusyBox v1.18.0.git multicell binary
??
I'll be away from the computer the rest of the day till late. Thanks again for the help. BTW, following shappypenguin's adb "cheat" and got command window, but did not realize I needed to open superuser on the device to accept permissions (kept getting denied - duh)
Click to expand...
Click to collapse
drenner99 said:
Well, now I understand why I'm over here posting in the "General" section and not the development threads
I've spent the last several hours reading and installing the SDK only to discover I can't even figure out how to get it configured properly. I will succeed, but I'm too tired right now to continue and have other things to do later today. I'll try to provide more information as soon as I can get back to it.
And thanks Beach_Head and shabbypenguin for your interest and assistance.
Click to expand...
Click to collapse
You have been a positive contributor, and so I proudly give you your first "Thanks."
shabbypenguin said:
adb shell
su
dd if=/dev/block/mmcblk0p11 of=/sdcard/eletricfykernel.img
upload that for me please
you can then use dd to copy the rest of the phone
Click to expand...
Click to collapse
Here is the file you requested from the Electrify (electrifykernel.zip)
hopefully it contains what we're looking for....
Beach_Head said:
It looks like your BusyBox build doesn't include gzip. Where'd you get it from?
Anyway, download Busybox by Stericson from Market and install a newer BusyBox build.
That command will work guaranteed...
Thanks!
Click to expand...
Click to collapse
@Beach_Head, Thanks again. I did as you suggested and installed the newer busybox (1.19.2), but I still get the invalid option ("z") error when I enter the command
"busybox tar czvf /sdcard/systemdump.tgz /system"
from your code, and am then presented with a list of valid options, "z" not being one of them. Are we sure the czvf part of that line is as you intended? I'm still willing to give it a go if it will produce info that is helpful (see post immediately above with kernel.img file).
Thanks once again.
deedscreen said:
You have been a positive contributor, and so I proudly give you your first "Thanks."
Click to expand...
Click to collapse
I am truly humbled and can only say, you're welcome!
Yes. The z switch is for gzip...
Anyway, can you try without the z swicth.
So: busybox tar cvf /sdcard/systemdump.tgz /system
And then just zip it up again via WinRar or 7Zip before you upload it here...
Thanks!
drenner99 said:
@Beach_Head, Thanks again. I did as you suggested and installed the newer busybox (1.19.2), but I still get the invalid option ("z") error when I enter the command
"busybox tar czvf /sdcard/systemdump.tgz /system"
from your code, and am then presented with a list of valid options, "z" not being one of them. Are we sure the czvf part of that line is as you intended? I'm still willing to give it a go if it will produce info that is helpful (see post immediately above with kernel.img file).
Thanks once again.
Click to expand...
Click to collapse
I'm a moto electrify rooted and bootloader unlocked user.
Everything seems to work (as far as the root/unlock), but shabby's kernals are somewhat unstable on the electrify. Broken wi-fi is my only concern, and even with the wi-fi fix we haven't been able to run it.
one of my issues - now this isn't specifically about shabby's kernal or anything like that, but more of setcpu. Setcpu doesn't give me the option to scale, unfortunately.
my kernels are unstable on the photon so thats nothing new
what wifi fix? wifi is busted in rc2 due to modules needing to be updated. they arent part of the kernel they are instead loaded by the rom but they need to have the config file from the kernel in order to make them properly and thats where its all failing
shabbypenguin said:
my kernels are unstable on the photon so thats nothing new
what wifi fix? wifi is busted in rc2 due to modules needing to be updated. they arent part of the kernel they are instead loaded by the rom but they need to have the config file from the kernel in order to make them properly and thats where its all failing
Click to expand...
Click to collapse
Is there anything I can get you to fix the wifi in rc 2?
"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.