Related
Completely new to rooting, flashing so please excuse me if this is something really simple that I might be overlooking.
I've rooted my Nexus S I-902 on stock 2.3.4 rom. My goal is just to get voodoo color controls working via a kernel, but might also like a few other things like CIFS support.
So far I've only tried two different netarchy kernels suggested by others.
netarchy kernels I've tried...
EXPERIMENTAL CFS - netarchy-nexus-1.3.0.12-cfs-2.3.4-signed.zip
STABLE CFS - netarchy-nexus-1.3.2-cfs-2.3.4-signed.zip
I haven't tried actually flashing the zip via clockwork, but instead have extracted the netarchy.img files and used adb to boot the image.
fastboot boot netarchy.img
which loads the kernel and rom. I'm having wifi error issues doing this. Wifi just gives an error, but everything else seems to be ok.
What I'm wondering is by extracting only the IMG file above is that bypassing some included modules that might be needed that are not included in the zip file? If so is there an easy way just to test the whole kernel without actually flashing it first?
You need to flash the whole zip, you are only flashing the img which does not include the wifi modules
Sent from my Nexus S using XDA App
Edit:
i know there is a command to flash a kernel that will revert to stock on reboot but can not remember or find it in Google
if you are worried just do a nandroid backup before
bringonblink said:
You need to flash the whole zip, you are only flashing the img which does not include the wifi modules
Sent from my Nexus S using XDA App
Edit:
i know there is a command to flash a kernel that will revert to stock on reboot but can not remember or find it in Google
if you are worried just do a nandroid backup before
Click to expand...
Click to collapse
thanks..
ok, If I just did a Rom Manager backup which ran ClockworkMod Recovery for the backup. Is that the same thing as nandroid backup (guessing this is compatiable since there is a nandroid.md5 checksum file)?
I copied the backup on SD card over to my PC just in case.
So my guess is that I can then now FLASH any new kernel and if something goes wrong then I use Rom Manager or clockwork recovery to revert back to the original state of the file I backed up with Rom Manager above?!
This would then revert the new changes from any new Rom / Kernel I may have flashed correct?
What about applications or other data on the SD card (music, photos, app data, ect) That included in the backup too (file seems too small for that)?
kwhy said:
thanks..
ok, If I just did a Rom Manager backup which ran ClockworkMod Recovery for the backup. Is that the same thing as nandroid backup (guessing this is compatiable since there is a nandroid.md5 checksum file)?
I copied the backup on SD card over to my PC just in case.
So my guess is that I can then now FLASH any new kernel and if something goes wrong then I use Rom Manager or clockwork recovery to revert back to the original state of the file I backed up with Rom Manager above?!
This would then revert the new changes from any new Rom / Kernel I may have flashed correct?
What about applications or other data on the SD card (music, photos, app data, ect) That included in the backup too (file seems too small for that)?
Click to expand...
Click to collapse
Thats correct, and SD card is not touched when flashing, so need for it to be backed up
All flashed now and wifi working correctly. Colors changed finally back now how I liked them.
Thanks for the help.
Having the exact same issue unfortunately, first time rooting a phone. Followed the how-to from here http://forum.xda-developers.com/showthread.php?t=895545 and got everything going. Only kernel I put on it was from the stable 2.3.4 list here http://forum.xda-developers.com/showthread.php?t=936219&highlight=netarchy (tried both cfs and bfs). Went through recovery and re-tried it all, including a few factory resets with still no luck. 3g is kind of lousy out here and wifi helps a ton, do you have any other idea's to fix?
Have tried airplane mode toggling, factory reset, battery pulling, and reflashing everything in order, not sure what else to do
Could you connect your phone to PC & check for the logs over adb ? It's via the data-cable that your phone shipped with, download the android sdk (you could search the forum for detailed instructions on that) which houses the adb binary & issue these commands over the command prompt:
adb start-server
adb shell logcat
The second would produce fair amount of output on the screen including those related to WiFi. Also once you have enabled the Wifi on your phone, you could try the below command too:
C:\> adb shell lsmod
bcm4329 192346 0 - Live 0xbf07e000 <--- That's the wireless driver on board my phone which has a BroadCom wireless chip called bcm4329.
But should your phone instead produce no terminal output or an error in the "logcat", it would imply that the kernel essentially is missing the driver.
Hi all,
I am trying to make sense of how the android system is made up w.r.t to boot/kernel.
I have been looking at the .img files in the build (I built for the "passion" device), and have been googling around to find some more information about the various .img files.
I ran into a nice HOWTO in android-dls.com 's WIKI, titled HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images (I'm sorry, I'm a new user so XDA won't allow me to post links. I will try to modify my post a soon as I'm granted permission for that)
but I am afraid it is a little outdated:
I have several questions, but I will try to be brief, so I'll focus on
one of them, and if that works I'll proceed to the next questions, all related to "Android bringup for dummy embedded linux kernel experts".
I am fairly aware of differences between different linux
configurations, and I am very familiar with linux bringup concepts, so I will just use common examples from the linux world as my terminology. Hope it will be clear enough.
I understood that boot.img a combination of a kernel (e.g. bzImage in linux) and an initial ramdisk (e.g. initrd.gz), wrapped by some header, as in common linux kernel loading practice (piggy.o etc.).
Now, the aforementioned HOWTO says that the "recovery" image is built on
the same way, and that it is stored on the target's /system/
recovery.img .
I would assume that this would be compound of the ramdisk-
recovery.img, and some other kernel.
Now, the problem is that:
1. This /system/recovery.img does not exist from what I saw (on my
Motorola XOOM tablet)
2. What does exist is /system/boot-from-recovery.p , which is
created during the boot process in obj/PACKAGING/
recovery_patch_intermediates/recovery_from_boot.p .
I saw tons of posts referring to the files, all said that "in order to
replace the rescue disk image, this file needs to be renamed" - but I
am looking for a way to figure out what it is, and how to extract its
contents.
I assume /system/recovery.img is deprecated, is that correct?
3. I did not see any flash devices in /proc/mtd (which is strange).
I searched for hours before sending this post, so I would appreciate
your help. I also posted a similar message at the google android-building group, but it has not been answered yet, and I got the impression that these forums are more active and can help me get where I need.
If it is not the right place to ask the question please let me know -
I just assume this is a general android concept and not device
specific.
Thanks,
Ron
I meant of course /system/recovery-from-boot.p , and not recovery-from.boot.p
-R
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Well, it helped me. I'm new to rooting and just came across mention of this file. I am trying to learn 'why' as well as 'how'', so your post was informative.
Was going to ask a dumb question but I figured it out
i need to delet those files
bigrammy said:
Was going to ask a dumb question but I figured it out
Click to expand...
Click to collapse
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
recovery from boot p
ahmed morsy said:
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
Click to expand...
Click to collapse
Hey good day. Did you get your problem fixed...? I have an xt912 it has the same file. For days I've been trying to wipe the phone. Tryed rooting it. I tryed reprogramming it. And I got through with all of that. But everytime the phone boots up it goes back to the same state. Then I used a root browser and while exploring I saw this recovery from boot file. I need help. And I don't think I can downgrade the Motorola phones. Thanks in advance.
jman0 said:
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Click to expand...
Click to collapse
i have deleted it . then flash recovery ,, but it failed .. it wont even now go to stock recovery itself.. any help..
Does recovery from boot has to do anything with ota update applying ? or it will cause issues in system update ?
I have recovery-from-boot.p in my system and i cant root my phone i cant change the recovery img ... Help?
I hadn't had to deal with this for some time, perhaps because I've updated my devices (Nexus 4, Nexus 5, Nexus 7 '13) with the factory images, with "-w" removed from flash-all, then flashing CWM's recovery, ensure SuperSU was installed, then continuing. Today, I used the new OTA image on my Hammerhead/N5, and recovery-from-boot.p seems to be up to its old tricks again.
Solution is simple.
Flash your alternate Recovery in fastboot, fastboot flash recovery [recovery image file] . Boot into Recovery. Apply/install root app (typically via sideload). Mount /system. adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak. Reboot. Done. (If you're unfamiliar with fastboot, adb, and flashing new recovery partitions, you have some reading to do. Commence RTFM.)
I also used to have to move /system/etc/install-recovery.sh but that seems to be gone in Marshmallow. :} Or moved...?
well, after following a guide I have extracted the system.img from a pure-nexus ROM(The ROM I'm currently using), now I can see that "recovery-from-boot.p" file is responsible for recovery lock in my phone. I'll keep it short and straight to the question
"Can I remove this file and rebuild the .dat file and flash it?, so that I won't have any other problems at all"
I want to know if recovery-from-boot.p file is linked to anything other than just locking the recovery or re-flashing it innumerable times.
Hello there
I havent done any kind of rom building for well over a year now and it seems that the update script seems to have changed to updater script along with update binary.
can anyone give me information or point me somewhere where i can learn this new method and can the building of the updater script and binary be an automatic process? as if it can i will write some software to do that and post it here as there is no where i can find with this information so must be frustrating for those not in the know
also do the update packages still require signing?
does nobody seriously know about the updater script nor update binary? normally i would post in development forum where i would get an answer but get told off for posting there. At the end of the day once i know the format i will write an application that would do it all for you.
looking through several updater scripts i get the whole mounting partitions thing to then write information to. the whole symlink thing with busybox, every rom i unzip seems to have different symlinks, is there a reason for this or can i look to see what symlinks are needed for a certain rom? this so far seems to be the bit im strugglin with?any help will be thanked with a donation
Credit goes to developer, zroice, at the International Note 3 section for his work towards this.
DISCLAIMER: I AM NOT HELD RESPONSIBLE IF YOU BRICK/BOOTLOOP/ OTHERWISE INCAPACITATE YOUR DEVICE IN ANY WAY. YOU'VE BEEN WARNED!
This has been confirmed working for the AT&T Note 3 (Thanks to drakeymcmb and Bri315317) WITH SOME PROBLEMS. Therefore, probably with some changes, this *might* work for our device. I wanted to share the information here to simply see if anyone is able to confirm or deny this for the SGH-I337.
Original Thread: http://forum.xda-developers.com/showthread.php?t=2550120
AT&T Note 3 Thread: http://forum.xda-developers.com/showthread.php?t=2554411
OP from zroice:
zroice said:
Ladies and Gentlemen I present to you the
kn0x0ut Toolbox v1.03!
(notice the 0x0 reference! hehe)
This script allows you to install custom roms, and mods that you would normally have to flash with custom recovery.
,
But as we all know, if you want to keep knox warranty void at 0x0 you cannot use a custom recovery or kernel.
If your knox warranty is already void aka 0x1 then you can still use this tool but it wont bring back the warranty...
---
This kn0x0ut toolbox itself requires root! You will have to use "Root de la vega" or some other method to get rooted while keeping your warranty intact.
---
How to use:
Extract the download from below to your internal or external sd card.
Then browse into that directory with terminal or adb shell and type:
Code:
sh kn0x0ut.sh
or
Code:
sh kn0x0ut.sh help
and you will get all the commands supported currently.
---
Check post 2 for full command list!
To install a rom or other zip you will have to extract its contents to the "extract_files_here" subfolder of kn0x0ut and then run the install command.
Code:
sh kn0x0ut.sh install
or
Code:
sh kn0x0ut.sh new_rom
(this is the command to install a new rom basically, meaning: backup and clean base, clean dalvik, install rom, reboot)
or if you want to install a rom with all the mods currently available:
Code:
sh kn0x0ut.sh new_rom all_addons
NOTE: The install script looks inside the extract_files_here folder for data and/or system folders to be copied over to the system or data folder on your device respectively.
All other folders it finds will get "ignored" (they will be copied to a folder "not_installed" which is created if the script finds incompatible folders or files). After the seperation
of the data and system folder from the unsupported ones, some dangerous libs which cannot be copied while the system runs will get removed from the temporary installation
folder so to ensure that there is no crash during the copy process. Once these files are removed the safe files get copied to your system and the permissions get fixed with
my permission fixing script.
The files that have been installed will get moved into a subfolder called "installed" and into another subfolder with the date and time of the installation.
The files that could not be installed by the script in the first run get moved to "not_installed".
These files could still become installed if you copy or move them over to the extract_files_here folder again for a second run. But remember that a data and/or a system folder is expected by the script inside the extract_files_here folder - so you have to make sure the structure is alright if you do things like this.
---
Example:
X-Note has the following folders when extracted:
META-INF, data, system, xnote.
The data and system folder will get installed, while the metainf and xnote folder wont. Inside the xnote folder you will find stuff that would normally be installed by aroma through user choice.
If you look inside there at the acid mod folder for example, there will be a system folder. To install this mod with kn0x0ut in a second run, you would have to move that system folder back
to the extract_files_here folder and then run the install command again. Only things inside data or system folder will ever be installed. And even then you gotta make sure the folder structure is
as on the system or data partition itself. (so apks need to be inside ..../kn0x0ut/extract_files_here/data/app or ..../kn0x0ut/extract_files_here/system/app to be moved to the right folder, etc...
you get it. (if not you should not use it for stuff like that)
---
This is only version 1.03 - I got more ideas to integrate but I dont wanted to hold things back any longer...
A word of warning though:
This is made for lazy people (like myself) and not for dumb people! (aka: its made to save time and ease up things and should be used with caution to not mess up things)
(for example: dont clean_base or use new_rom without actually installing a new rom or you will most likely end up without system apps and device not booting correctly - like you wouldnt wipe system in a custom recovery without installing a rom...).
It can be used over adb or terminal, but if you install a rom (clean_base) the system ui gets stopped, so better do it over adb!
It basically does the steps I described in my guide to install custom roms on knox firmware in a script, plus some other nice little timesavers.
Dont worry about error messages that say files dont exist or that they already exist! (thats normal)
Feel free to check out the source code and suggest improvements or enhancements like new mods to integrate.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Interesting...but since it doesn't flash kernels we'd still only be able to use whichever ROMs are compatible with stock kernels? I wonder how different the libs used are between the s4 and note 3
prisonnet said:
Interesting...but since it doesn't flash kernels we'd still only be able to use whichever ROMs are compatible with stock kernels? I wonder how different the libs used are between the s4 and note 3
Click to expand...
Click to collapse
You're probably right. It would be preferable for someone on mf3 to test because they would have a way to odin back to stock.
This basically sounds like framework modification. It sounds as if it might be use-able with TW based type ROMs but I doubt CM, AOSP, AOKP, or MIUI ROMs will work. If it works, it should simplify modifying the framework because it allows Devs to create certain Pseudo-Roms with many modifications to be flashed all at one time via ADB instead of needing to do several individual changes.
Take a look at the P-ROM or Pseudo-ROM thread in Android development by Nottach. It seems to be the same concept just for MDL firmwares.
phobia09 said:
You're probably right. It would be preferable for someone on mf3 to test because they would have a way to odin back to stock.
Click to expand...
Click to collapse
I'd be interested to see if this works on MJ9 / MK2 since SafeStrap isn't available for those versions yet, but I don't think there's odin available for MK2. Might be a one-way trip to bricksville.
prisonnet said:
I'd be interested to see if this works on MJ9 / MK2 since SafeStrap isn't available for those versions yet, but I don't think there's odin available for MK2. Might be a one-way trip to bricksville.
Click to expand...
Click to collapse
That's the main reason I posted this. I wouldn't want to test since I'm on mk2. I was more hoping someone on mf3 could test it and then maybe see if we could somehow tweak it for mj9/mk2 users if necessary.
phobia09 said:
That's the main reason I posted this. I wouldn't want to test since I'm on mk2. I was more hoping someone on mf3 could test it and then maybe see if we could somehow tweak it for mj9/mk2 users if necessary.
Click to expand...
Click to collapse
Going to try this after work tonight. I'm still on MF3. Read through the kn0x0ut script and no changes need to be made for this to work on our device - the partitions listed are all the same. I'll try a 4.2.2 TW Rom, then 4.2.2 GPE, then upgrade to MK2 and try a 4.3 TW and 4.3 GPE rom.
I'd be more confident trying this on MK2 if it worked on MF3 without any problems.
prisonnet said:
Going to try this after work tonight. I'm still on MF3. Read through the kn0x0ut script and no changes need to be made for this to work on our device - the partitions listed are all the same. I'll try a 4.2.2 TW Rom, then 4.2.2 GPE, then upgrade to MK2 and try a 4.3 TW and 4.3 GPE rom.
I'd be more confident trying this on MK2 if it worked on MF3 without any problems.
Click to expand...
Click to collapse
I would definitely appreciate it. If we can somehow get in touch with the same individual who uploaded the mf3 tars we may be able to get a method to flash back to stock mk2. Then we would be all set up with a way to flash without waiting on bootloader unlock or custom recovery. Looking forward to what you find out.
phobia09 said:
I would definitely appreciate it. If we can somehow get in touch with the same individual who uploaded the mf3 tars we may be able to get a method to flash back to stock mk2. Then we would be all set up with a way to flash without waiting on bootloader unlock or custom recovery. Looking forward to what you find out.
Click to expand...
Click to collapse
We also might be able to restore MK2 if someone can back up their MK2 installation using this method: http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
Would it be possible to use this to downgrade from MF3 back to MDL?? This could be very awesome...
hexagonsunja said:
Would it be possible to use this to downgrade from MF3 back to MDL?? This could be very awesome...
Click to expand...
Click to collapse
Unfortunately not. That requires a whole different level of access which, to my knowledge, no one has been able to achieve yet. Think of this as a command-line version of safestrap, without the rom slot functionality.
Interesting. I've given up hope on unlocking the bootloader for the s4. Minds much better than mine have tried and failed. If there's a way to circumvent the bootloader problem completely, this could be the holy grail for ATT S4 users! I agree that we'd probably have to stick with stock kernel ROMs, much like SS does, but it does open up an avenue of options for users.
I would volunteer, but as far as I know, there's no way to flash back to stock MK2 just yet. I can root easily enough, but I'm not going to risk a brick until there's a known flash to stock method. >_>
prisonnet said:
Unfortunately not. That requires a whole different level of access which, to my knowledge, no one has been able to achieve yet. Think of this as a command-line version of safestrap, without the rom slot functionality.
Click to expand...
Click to collapse
Ah I see, I wonder if this is the first step though... I am currently on MF3 and rooted, so I would likely be willing to try this out once others report success. I am hesitant to brick my daily driver though...
Zephcemi said:
Interesting. I've given up hope on unlocking the bootloader for the s4. Minds much better than mine have tried and failed. If there's a way to circumvent the bootloader problem completely, this could be the holy grail for ATT S4 users! I agree that we'd probably have to stick with stock kernel ROMs, much like SS does, but it does open up an avenue of options for users.
I would volunteer, but as far as I know, there's no way to flash back to stock MK2 just yet. I can root easily enough, but I'm not going to risk a brick until there's a known flash to stock method. >_>
Click to expand...
Click to collapse
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck
prisonnet said:
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck
Click to expand...
Click to collapse
Good luck! If you can verify, I'll be getting a 4.3 GPE rom myself. Godspeed!
prisonnet said:
We also might be able to restore MK2 if someone can back up their MK2 installation using this method: http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
Click to expand...
Click to collapse
I think this would be awesome, I am much too ignorant to understand; Where/how is this script to be run? Terminal Emulator? ADB? Odin itself? If it's something relatively low risk (and assuming I'm capable of doing it) I'll attempt it because I'm on MK2.
prisonnet said:
I can verify that the script works on MF3. Just used it to remove then re-install the 4.2.2 GPE rom I was using with safestrap. I'm now going to upgrade to MK2 and try a 4.3 GPE rom...wish me luck
Click to expand...
Click to collapse
GOOD LUCK! Thanks again for your contribution! :fingers-crossed:
phobia09 said:
I think this would be awesome, I am much too ignorant to understand; Where/how is this script to be run? Terminal Emulator? ADB? Odin itself? If it's something relatively low risk (and assuming I'm capable of doing it) I'll attempt it because I'm on MK2.
GOOD LUCK! Thanks again for your contribution! :fingers-crossed:
Click to expand...
Click to collapse
Just in case, I'd make an odin backup using this script http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
That way you can return to the state your phone is in now if something goes wrong - it will probably take at least an hour, and is harder to restore than a backup would be in TWRP or similar, but at least it's possible.
If you do want to give it a shot (make a backup first!), all you need to do (which I'll be doing myself after my phone finishes updating to MK2) is extract this rom http://forum.xda-developers.com/showthread.php?p=47718525#post47718525 into the "put_files_here" folder of the kn0x0ut zip, then send the whole kn0x0ut folder somewhere to your phone, like /mnt/extSdCard or just /mnt/sdcard.
Then through adb (not terminal emulator because the GUI will crash - as expected - when you delete the rom you are currently running), do sh kn0x0ut.sh install and it should automatically install the rom in the "put_files_here" folder. I think there's a new update of the kn0x0ut script coming soon that allows flashing of straight zip files, but not sure when that will be released.
prisonnet said:
Just in case, I'd make an odin backup using this script http://forum.xda-developers.com/showpost.php?p=44917036&postcount=1
That way you can return to the state your phone is in now if something goes wrong - it will probably take at least an hour, and is harder to restore than a backup would be in TWRP or similar, but at least it's possible.
If you do want to give it a shot (make a backup first!), all you need to do (which I'll be doing myself after my phone finishes updating to MK2) is extract this rom http://forum.xda-developers.com/showthread.php?p=47718525#post47718525 into the "put_files_here" folder of the kn0x0ut zip, then send the whole kn0x0ut folder somewhere to your phone, like /mnt/extSdCard or just /mnt/sdcard.
Then through adb (not terminal emulator because the GUI will crash - as expected - when you delete the rom you are currently running), do sh kn0x0ut.sh install and it should automatically install the rom in the "put_files_here" folder. I think there's a new update of the kn0x0ut script coming soon that allows flashing of straight zip files, but not sure when that will be released.
Click to expand...
Click to collapse
@prisonnet Have you utilized this script on any previous versions? Actually used the tar ball to restore anything? I haven't tried and I'm a bit skeptical.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
brobinson2102 said:
@prisonnet Have you utilized this script on any previous versions? Actually used the tar ball to restore anything? I haven't tried and I'm a bit skeptical.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm making one right now to see if it can work, though i had to build the commands into my own batch file as running the script through ADB or Terminal Emulator didn't work. Currently compressing the files and then hopefully when i test them it will work, but i am highly doubtful that it will because i believe they need to be signed and i remember Aou creating something like this for MF3 in his neutered update thread and I believe it didn't flash.
DeadlySin9 said:
I'm making one right now to see if it can work, though i had to build the commands into my own batch file as running the script through ADB or Terminal Emulator didn't work. Currently compressing the files and then hopefully when i test them it will work, but i am highly doubtful that it will because i believe they need to be signed and i remember Aou creating something like this for MF3 in his neutered update thread and I believe it didn't flash.
Click to expand...
Click to collapse
I'm working on the same thing now. If the tar file doesn't work, my next step is to try manually flashing the backed-up system.img.ext4 with busybox dd. Someone correct me if I'm wrong, but ROMs contain boot.img and system files, since we can't flash boot.img without bricking that leaves system.img? I know safestrap doesn't flash boot.img; I assumed it just flashed the system - so I'm just trying to do that manually.
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
Just info :
"I have submitted my problem is on the web and social media owned IPRO but no response, I also have to ask in the thread "is concerned about this issue but no response. I do not know if I really make this thread in the forum Q & A if any anyone please notifications where should I post this thread, I hope anyone can help me here, if no input on how to make this a better thread again please write your comment"
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
Nano.nano said:
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
Just info :
"I have submitted my problem is on the web and social media owned IPRO but no response, I also have to ask in the thread "is concerned about this issue but no response. I do not know if I really make this thread in the forum Q & A if any anyone please notifications where should I post this thread, I hope anyone can help me here, if no input on how to make this a better thread again please write your comment"
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
Click to expand...
Click to collapse
I edit files and install Tweaks build.prop
Click to expand...
Click to collapse
more than likely, it is not booting because you made some bad edits to the build prop. i see this happen a lot.
you will need to find a stock firmware for your device and install it back to fix the problem.
use search terms like "(your device name) return to stock" to try and locate the files.
bweN diorD said:
more than likely, it is not booting because you made some bad edits to the build prop. i see this happen a lot.
you will need to find a stock firmware for your device and install it back to fix the problem.
use search terms like "(your device name) return to stock" to try and locate the files.
Click to expand...
Click to collapse
Thanks for your suggestions and answers, Before I made this thread I have searched from internet Stock firmware or stockrom for my device but I never found it, Is there any other way than to install stock rom or firmware to fix my device, or install a custom rom firmware or install other devices can be made in alternative
Nano.nano said:
Thanks for your suggestions and answers, Before I made this thread I have searched from internet Stock firmware or stockrom for my device but I never found it, Is there any other way than to install stock rom or firmware to fix my device, or install a custom rom firmware or install other devices can be made in alternative
Click to expand...
Click to collapse
you can try searching for a custom rom, that should fix it.
other than that, with no stock firmware, i dont see any way you could fix it.
no, you cant use files from another device, unless it specifically says its ok for your device (very rare, but happens occasionally)
bweN diorD said:
you can try searching for a custom rom, that should fix it.
other than that, with no stock firmware, i dont see any way you could fix it.
no, you cant use files from another device, unless it specifically says its ok for your device (very rare, but happens occasionally)
Click to expand...
Click to collapse
Thank you for your prompt response.
Similarity such as what should I look for when taking custom rom or files from other devices?
Nano.nano said:
Thank you for your prompt response.
Similarity such as what should I look for when taking custom rom or files from other devices?
Click to expand...
Click to collapse
look for it to say directly, it can be used on your device. thats the only way.
bweN diorD said:
because you made some bad edits to the build prop.
Click to expand...
Click to collapse
So there will be plenty of experiments,
CMIIW.
If this error in build.prop can I fix it with this way?:
-Take the backup file build.prop.bak with ADB
-Then Edit it by removing the code that previously I input
-And I input back into the system folder in my device with ADB
-And delete files that are in init.d
What a way as it could to improve my device, because I think if it's just damage build.prop file.
And if I use a custom rom whether he would change the system information such as kernel, android version, and whether he will change the code in the file build.prop and What it will also transform the tweaks in the init.d folder or even add to the pile? I think if a custom rom working to add code or tweaks both in build.prop or init.d I think it will worsen, CMIIW, because I think if true custom rom works like that then it is not a good solution
Nano.nano said:
So there will be plenty of experiments,
CMIIW.
If this error in build.prop can I fix it with this way?:
-Take the backup file build.prop.bak with ADB
-Then Edit it by removing the code that previously I input
-And I input back into the system folder in my device with ADB
-And delete files that are in init.d
What a way as it could to improve my device, because I think if it's just damage build.prop file.
And if I use a custom rom whether he would change the system information such as kernel, android version, and whether he will change the code in the file build.prop and What it will also transform the tweaks in the init.d folder or even add to the pile? I think if a custom rom working to add code or tweaks both in build.prop or init.d I think it will worsen, CMIIW, because I think if true custom rom works like that then it is not a good solution
Click to expand...
Click to collapse
1. i have no idea what CMIIW means
2. yes, if you have an original copy of the build prop or can remove edits from the current one, and can replace with adb, that would be good.
3. i would try fixing one thing at a time to see what actually caused the issue. init may or may not need to be fixed.
4. custom rom would clean and replace the entire system including kernel, so it should fix the issue. however, this is your choice, its not a bad option, just a different one.
bweN diorD said:
1. i have no idea what CMIIW means
2. yes, if you have an original copy of the build prop or can remove edits from the current one, and can replace with adb, that would be good.
3. i would try fixing one thing at a time to see what actually caused the issue. init may or may not need to be fixed.
4. custom rom would clean and replace the entire system including kernel, so it should fix the issue. however, this is your choice, its not a bad option, just a different one.
Click to expand...
Click to collapse
CMIIW is Correct Me If I'm Wrong.
Finally, I have two ways for the try, the title and content of this thread may be changed if it is successful.
Thank you for helping me
Thank you for patiently explained
Now I know what to do,
thank you for your participation
thank you very much :good:
no problem