Hello: D
I have installed a stock rom and my intention is to remove the files odex, according to this tutorial http://forum.xda-developers.com/showthread.php?t=1466071 and when I enter the code (busybox cp / sdcard / done_app / * / system / app /) in the shell tells me that the device does not have enough memory or something and when I disconnected the phone and turned it on, the mobile freezes in the boot image.
According to the author of the tutorial you have to delete a file before replacing odex but then says it is not necessary, but I did not do so will have been the problem with my phone?
I did a factory data wipe my phone but was still unlit, so I had to install the stock rom again.
Some help so I would not happen again
Just use xUltimate if cmd seems tough.
TeamCooper Developer
TheMyth Developer
www.teamcooper.net
My mistake was I did not have busybox installed (well that's what I think)
Reflash stock ROM?
Sent from my GT-S5830 using Tapatalk
Related
About SD-Recovery: Based on boot strap recovery!
Stock Recovery signed with Test Keys for Flashing Update.zip to to Motorola Defy.
Version 1:
~ Must be Rooted & Have Superuser installed
~ SD-Recovery is installed to /sdcard/sd-recovery.sip or ( /mnt/sdcard/sd-recovery )
( Must have MoTo Phone Portal Turned before Using )
( Can be used with CwM Bootstrap recovery by renaming update-recovery.zip to sd-recovery.zip and placed on the /sdcard, just rename original to defy-sd or something for later use if needed )
~ ADB Debugging does not have to be turned Off
~ Capable of Flashing any update.zip for 2.2.1 Defy
~ Factory wipe & Wipe Cache fully working
~ Design to keep moto encryption from breaking
~ Working ADB Shell in Recovery + root access
~ Busybox installed
Update.zip must be signed like so: Please Google signapk
java -Xmx1024m -jar signapk.jar -w testkey.x509.pem testkey.pk8 update1.zip update.zip
For a Base start, please see this Update.zip:
http://eb-productions.proboards.com/index.cgi?action=display&board=mdd&thread=291
Market Download: https://market.android.com/search?q=defy+sd-recovery&c=apps
App .apk Download: http://www.multiupload.com/4FX5F14XXM
How it works?
Am i right in thinking this is like a fakeflash recovery? It will work even when rom bootloops with no access to 2nd init recovery thing?
defy wont flash .sbf bricked
hello im still struggling on how to fix my defy . please help i cant flash it, it always failed and im getting 0x7029...
when we recovery the phone ,we need cabel ??? thx
This is awesome, thank you!
Phone is a Star X19i
Now I'm looking at getting a system to allow me to back up the rom and re-flash if needed.
Post 4 has attachments of my boot, recovery and scatter files.
Old issue: (Solved)
Stupid thing I did I renamed the mtklockscreen.odex to mtklockscreen.odex1 just as a test in a half asleep phase to see if I would get the stock lockscreen loading.
Suffice to say the phone no longer boots.
Really don't think I can get into ADB and rename the file to get the phone booting again unless anyone knows a way.
Android was 2.3.6 and I asked the seller if it was possible to get the rom incase anything like happened which they didn't.
So anyone have any ideas?
I have attached the stock recovery and boot images made with cat and a scatter file I made to post 4.
As I have no idea about modifying these for hard root can anyone take a look?
I don't know the specifics of the phone, but if you can go into recovery mode maybe you can get adb working, or use a flashable zip to rename the file by installing it from recovery (just need to edit the zips' updater script)
dxppxd said:
I don't know the specifics of the phone, but if you can go into recovery mode maybe you can get adb working, or use a flashable zip to rename the file by installing it from recovery (just need to edit the zips' updater script)
Click to expand...
Click to collapse
I got into built in Factory mode and can see the file I renamed through ADB and android commander but cannot rename it back due to not having hard root access.
I also have a copy of the boot and recovery partitions 5 and 6 respectively I made in the adb shell yesterday as I was half looking at getting hard root access.
ren mtklockscreen.odex1 mtklockscreen.odex
ren: permission denied
I read you can do a custom recovery with root using SP Tools still so can anyone help me do this?
I know about system root etc and stuff and have flashed roms before on other tablets and have been a PC I.T tech (wouldn't think it due to the stupid mistake) but this recovery and scatter files etc is kinda new to me.
I have a scatter file now I just made if anyone is interested in helping me.
Yes I have a MTK6573 but the scatter file came from the MT6516 Rom Studio which I read works the same for the 6573.
Attached is also my stock boot and recovery partitions I made with cat yesterday if there usable to anyone to help.
Well I got it working and fixed.
I had to go into adb shell and su and mount the file system as writable, as I have used linux before I didn't know about android and what needed to be done and permission locks etc.
The stock boot, recovery and scatter files will remain on this thread if anyone wants to help create or find a recovery which can allow me to create backups and flash custom roms.
I may be able to provide a dump of android 2.3.6 for those that want it once I'm provided with a backup solution as I have read a few people wanting this updated android rom.
This got too close to what I would like liked with bricking this phone.
And I'm not comfortable unless I have a rom backup of this.
Rooting Advice: For anyone with a MTK6573 on Android 2.3.6 trying to root but having issues with super one click make sure you only turn on USB debugging after Android has loaded and just before you plug the usb cable in to run super one click.
I have seen a few thread and posters here about not being able to root the phone and this is the cause that debug needs to be switched on right before you connect and try to root.
Original seller has agreed to send the firmware and flashing stuff on cd for me so I can upload it for you all.
This is a win for MTK6573 Star X19i owners as I'll have the updated 2.3.6 Gingerbread firmware to release for you all root modify etc in a week or so.
Be careful with ROM studio. I believe it is not compatible with MT6573.
You want to read this: http://bm-smartphone-reviews.blogspot.com/2012_04_01_archive.html
cybermaus said:
Be careful with ROM studio. I believe it is not compatible with MT6573.
You want to read this: http://bm-smartphone-reviews.blogspot.com/2012_04_01_archive.html
Click to expand...
Click to collapse
That's what I read and did to get my scatter as I used cat then used the program linked in that thread to generate the scatter.
Hello,
I want to root my device with odin and chainfire. I know this basically leaves my recovery
untouched and modifies some system files so as to allow root apps to install themselves
in a way that they can run with root permssion.
1. I would like to know more about exactly what changes this kind of rooting does to the
device's file system.
2. I want to back up my ROM before this (not my data, just the program that factory
resets my device). That way, if I don't like something or something doesn't work I know
I can go back.
3. If once I root my device I install ClockworkMod as my recovery, does that mean my
old recovery is gone forever and I cannot get it back (not that I would probably need it
but just in case).
Can someone please help?
Thanks,
John Goche
johngoche99 said:
Hello,
I want to root my device with odin and chainfire. I know this basically leaves my recovery
untouched and modifies some system files so as to allow root apps to install themselves
in a way that they can run with root permssion.
1. I would like to know more about exactly what changes this kind of rooting does to the
device's file system.
2. I want to back up my ROM before this (not my data, just the program that factory
resets my device). That way, if I don't like something or something doesn't work I know
I can go back.
3. If once I root my device I install ClockworkMod as my recovery, does that mean my
old recovery is gone forever and I cannot get it back (not that I would probably need it
but just in case).
Can someone please help?
Thanks,
John Goche
Click to expand...
Click to collapse
1. It doesn't make any changes to the file system. Are you sure you're using the right term?
It tells you what it does here:
http://autoroot.chainfire.eu
2. You cannot back up your rom before rooting. You require a custom recovery to do this... unless the s3 toolbox does this??have a look. There is a nandroid over adb option
http://forum.xda-developers.com/showthread.php?t=1746680
Factory reset only manages /data I.e your stuff. It doesn't restore roms
3. The toolbox in 2. Can flash stock recovery
Sent from my GT-I9300 using Tapatalk 2
1. OK, so there's the ROM, and there's the filesystem. So it's not like in Unix where everything is a file.
I thought the ROM includes all the files which are part of the filesystem including /system/xbin and the
kernel. I thought the filesystem is part of the flashed ROM, not a separate thing.
2. I have adb installed. How do I do a nandroid over adb?
3. OK, so the default recovery just restores the /data partition.
johngoche99 said:
1. OK, so there's the ROM, and there's the filesystem. So it's not like in Unix where everything is a file.
I thought the ROM includes all the files which are part of the filesystem including /system/xbin and the
kernel. I thought the filesystem is part of the flashed ROM, not a separate thing.
2. I have adb installed. How do I do a nandroid over adb?
3. OK, so the default recovery just restores the /data partition.
Click to expand...
Click to collapse
1. File system = ext4, fat32, ntfs etc.
The ROM is a collection of files, within the /system partition and a kernel (boot.img). Of course there is a file system beneath this but its completely irrelevant to our discussions.
But cf auto root puts an app in /system/app and a binary in /system/bin. I suppose you're using "filesystem" in the way linux uses that to navigate to the /root of the OS.
2. Download the windows application I linked you to and follow the prompts to set up correctly. Then its a menu option
3. The stock recovery only WIPES the /data partition. It restores nothing
Sent from my GT-I9300 using Tapatalk 2
1. OK, the ROM is a collection of files. Now I'm in sync. So only two files are modified during the rooting process,
and app in /system/app (which does what?) and a binary in /system/bin (presumably a shell?).
2. Download the windows application I linked you to and follow the prompts to set up correctly. Then its a menu option
Where is the windows application you linked me. With all the clutter on the XDA pages I can hardly see it.
3. The stock recovery only WIPES the /data partition. It restores nothing
Thanks. Not sure why the data partition is not browsable with adb shell by default.
Thanks.
The su binary is the actual root. But you need a superuser app too. The app acts as a gatekeeper. When you run an app that requires root, superuser app opens and asks you if you want to allow or deny access to this app. Think of it as a level of protection
The link in my first post in my number 2. Answer is a specific thread for the windows application called unified toolbox. Just read all of post one. It tells you everything you need to know.
/data is protected because things that could otherwise be deleted can prevent android from booting up.
Not sure if you're familiar with Linux, but /data isn't quite the same as your home directory. That would be /sdcard. I suppose the Linux equivalent of /data would be /usr (although not really as despite their similarity, linux and android are not the same. Only really the kernel)
Sent from my GT-I9300 using Tapatalk 2
Hello everyone.
Guys, I am interested in turn the stock rom of my phone in a ready-to-install rom. I mean, roms usually are .zip files with scripts that writes the customized files to the system file, overwriting the old files. I want to know how to take the stock rom of my phone and turn it in a intallable .zip file, like a customized rom.
After a normal installing the phone would be like the phone with the original rom, without changes. Do you know what I mean?
I am interested in this for make changes and costumizations in the stock rom for then reinstall it. Normally, rom porting is made by taking a compatible rom (like CM) and taking the wished to port rom and changing directories like /system, /data, etc... Am I right? Well, if a would take the original rom of my phone and would turn it in a installable .zip, I could make ports, right?
Well, this is my doubt, how can I do this?
Up.
What's wrong? No one cares about?
Noob reporting here !
You can start by installing ADB (from android sdk).
When you have ADB correctly installed , you can "rip" your phone's complete /system partition by using the "adb pull /system system/" command.
This will rip /system to a subfolder called "system" (example c:/adb/adb.exe -> c:/adb/system)
I haven't come further myself, as i`m also in the learning (reading) phase.
you can use dsixda's kitchen for that, just use a firmware file for your phone, and extract that using the kitchen, after that you can use it to make a zip file
My “Xiaomi redmi note 3” is rooted, and busybox is installed. But I can’t convert any user app to system app. Even magisk module “Terminal Emulator App Systemizer” doesn’t work. I tried moving user app to Sytem/app using root explorer, it worked for a while but the app disappeared after rebooting. Is there any solution for it?
This problem is occurring in every custom ROM for me. HELP please.
Image : http://imgur.com/a/ZUkjG
Found a fix for this (Needs clean flash of ROM once) :
1) Go to recovery > wipe dalvik,system,data,cache,cust
2)select System partition only > Repair or Change file system > Repair file system > swipe to repair
3) Flash ROM
4) Relax and wait for phone to boot up,
Tested on Nitrogen OS(2017-05-12) , Pure Nexus and Resurrection Remix(2017-05-14)
Steps in screenshots - http://imgur.com/a/fp8HA