THIS THEME IS ONLY FOR THE BELL ATRIX. IT REQUIRES YOU TO HAVE A DEODEXED SYSTEM.
Disclaimer: I am not responsible for any softbricking that may happen to your device. I have tested it on my phone only.
I am releasing a Gingerbread theme I made for the Bell Atrix . Please let me know if you find any bugs that I haven't so far.
The next version will have the carrier removed from the notification bar, but for now its just invisible because of the black text.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
CWM install zip (OLYEM U4 1.4.2):
BellGingerbread1.3-CWM.zip
Manual install files (OLYEM U4 1.4.2):
BellGingerbread-V1.3.zip
_________________________________________
Old Versions (Bell 0.37.4):
BellGingerbread-V1.2(with scripts).zip
Installation:
First you need to have deodexed your system files. This can be done by following the instructions in this thread:
[script][SCRIPT] OLYEM_U4 1.4.2 Telstra/Bell FULL Deodex for OLYEM 1.4.2
OR
[script] Deodexed files for Bell for Bell 0.37.4.
CWM
1. Download the CWM zip
2. Place the still compressed zip onto your SD card
3. Boot into recovery and install zip
Manual
1. Download the manual files package and extract it
2. Put the files from the install files directory in the root directory of your SD card
3. Run this code in ADB
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp -f /sdcard/framework-res.apk /system/framework/
cp -f /sdcard/services.jar /system/framework/
cp -f /sdcard/blur-res.apk /system/framework/
sync
reboot
Uninstall:
For CWM method:
1. Download the CWM backup BellGingerbread1.3-CWM-BACKUP.zip
2. Follow instructions for CWM install but use the backup zip
For manual method:
1. Download backup files BackupFilesBell-OLYEM1.4.2.zip
2. Follow instructions from the manual install but use the backup files
For install script (V1.2 Only):
1. Run RESTORE.BAT
Extras:
Gingerbread Keyboard: [MOD] Gingerbread Keyboard on Atrix!
Nexus Boot Animation (Much better then the Telstra one):
1. Download the bootanimation.zip
2. Put the bootanimation.zip in the root directory of your SD card
3. Run this code in ADB
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp -f /sdcard/bootanimation.zip /system/media/
sync
reboot
Chnagelog:
1.3 (Newest Version)
- OLYEM U4 1.4.2 Support
- Darker notification pulldown
1.2
- Added transparent notification pulldown
- Removed lock screen animation
1.1
- Added Gingerbread animations
1.0
-Original Release
Cool, I like. Are you planning on maybe making a couple different themes too?
Sent from my MB860 using XDA App
Thank you soo much! I have been waiting for something to start happening with the bell atrix's.
3 requests which im not sure are possible...
-different animations
-gingerbread screen off animation (looks like turning of a tv)
-power controls in pulldown menu??
Keep it up. Gonna try this as soon as i get home. Im assuming there is a thread on how to deodex system.
For now I'm going to keep working on this theme, maybe I'll make more later. I'm adding animations in the next version which should be out soon, and I am looking into the power controls in the notifications menu. Unfortunately its not possible to get the shutoff animation, I liked it a lot on my Desire Z, but that was actually running gingerbread.
script please or CWM
would you be able to make a script for this theme or a CWM update.zip for easy installation thanks and keep up the good work. im so happy that someone is finally creating something for the bell atrix.
Silent8Strike said:
For now I'm going to keep working on this theme, maybe I'll make more later. I'm adding animations in the next version which should be out soon, and I am looking into the power controls in the notifications menu. Unfortunately its not possible to get the shutoff animation, I liked it a lot on my Desire Z, but that was actually running gingerbread.
Click to expand...
Click to collapse
alright, i look forward to it
erik10002 said:
would you be able to make a script for this theme or a CWM update.zip for easy installation thanks and keep up the good work. im so happy that someone is finally creating something for the bell atrix.
Click to expand...
Click to collapse
i don't know what the OP's plan are, but i'd be happy to throw together a script that can do this for everyone
i haven't messed around making CWM stuff yet, so i can't promise anything there, but probably later tonight i'll post a script that can do this
we need more devs like you guys. gives me confidence in the community. Keep up the good work.
raybond25 said:
i don't know what the OP's plan are, but i'd be happy to throw together a script that can do this for everyone
i haven't messed around making CWM stuff yet, so i can't promise anything there, but probably later tonight i'll post a script that can do this
Click to expand...
Click to collapse
that would be awesome, i tried to do it through adb this morning but wasn't working for me and a script makes installing anything a heck of a lot easier.
also i have [THEME] Black Bar Bell. (Gingerbread) by toughbax on my phone, will there be any problems installing this over it?
thanks
Im gonna try the zip tonight. No rush but you think it will be up tonight?
erik10002 said:
that would be awesome, i tried to do it through adb this morning but wasn't working for me and a script makes installing anything a heck of a lot easier.
also i have [THEME] Black Bar Bell. (Gingerbread) by toughbax on my phone, will there be any problems installing this over it?
thanks
Click to expand...
Click to collapse
No, there will be no problems installing over, because you completely replace both files that are used to create the other theme. The script will be up around 10 tonight probably, got a bunch of things to do at school tonight.
Sent from my MB860 using XDA App
blunted09 said:
Im gonna try the zip tonight. No rush but you think it will be up tonight?
Click to expand...
Click to collapse
I won't upload a flashable .zip for use with cwm because I don't know how, maybe in the future, just not tonight. However, I will be uploading a .bat file later tonight around 10, so you will just be able to run that off of your pc.
Sent from my MB860 using XDA App
Awesome, I will wait for the bat file and try it tonight. Thanks again.
Sent from my MB860 using XDA Premium App
I'll see what I can do about making a zip to flash in cwm tonight when I get home from work in a few hours.
Silent8Strike said:
I'll see what I can do about making a zip to flash in cwm tonight when I get home from work in a few hours.
Click to expand...
Click to collapse
well, i just got a script working, and it makes a backup for the user too, i'm just about to make a recovery script that will restore the backup to the device, just in case the user doesn't like the theme, or if something happens to make it brick
i soft-bricked myself once because i made an absolutely retarded typo in my script the first time, and copied the files to the wrong directory, lmfao. that's fixed now obviously
raybond25 said:
well, i just got a script working, and it makes a backup for the user too, i'm just about to make a recovery script that will restore the backup to the device, just in case the user doesn't like the theme, or if something happens to make it brick
i soft-bricked myself once because i made an absolutely retarded typo in my script the first time, and copied the files to the wrong directory, lmfao. that's fixed now obviously
Click to expand...
Click to collapse
ALL DONE - install script will create a backup of your current (soon to be old) theme before installing new theme. Restore script will re-install your old theme to your device.
MUST BE DEODEXED STILL, JUST BECAUSE ITS A SCRIPT DOESN'T CHANGE THAT.
*NOTE* if the script runs through and says "Device not found" under everything, its probably because USB debugging got interrupted. I ran into this a whole bunch of times, and ran into device not found a few, but whenever that happens, if you simply run the script again right after, it will work (has been replicated by myself).
If you run into any problems further than that easily fixable one, you're probably not deodexed and rooted. If you have further problems feel free to PM me.
with the new bell SBF that was leaked will this still work? thanks
raybond25 said:
ALL DONE - install script will create a backup of your current (soon to be old) theme before installing new theme. Restore script will re-install your old theme to your device.
MUST BE DEODEXED STILL, JUST BECAUSE ITS A SCRIPT DOESN'T CHANGE THAT.
*NOTE* if the script runs through and says "Device not found" under everything, its probably because USB debugging got interrupted. I ran into this a whole bunch of times, and ran into device not found a few, but whenever that happens, if you simply run the script again right after, it will work (has been replicated by myself).
If you run into any problems further than that easily fixable one, you're probably not deodexed and rooted. If you have further problems feel free to PM me.
Click to expand...
Click to collapse
thanks man!! so where can i get the script from? i don't see any links
erik10002 said:
with the new bell SBF that was leaked will this still work? thanks
Click to expand...
Click to collapse
to be honest i'm not sure about that .sbf
unless you've already flashed it and can confirm that it works, then i would recommend that your wait until it's confirmed.
also - this will work with the new .sbf provided we can get root for the new Bell firmware. i would suggest waiting until root is completed to update, just so you can keep adding mods like this to it.
and yes - this theme should work on the new sbf, if you're on it and have root access.
aliafi90 said:
thanks man!! so where can i get the script from? i don't see any links
Click to expand...
Click to collapse
yeah, uploading now will edit this post with link in 2mins
EDIT: heres the link
Related
I was trying to root NT 1.4.2 8gb, rooted with the Market. And then I tried to root it to CM7, my NT was dead.
With Nook Recovery Flasher.apk., I rebooted, insert SD(...zip), when I tried to backup, it was dead. Then I tried again whithout backup, at first, it worked, but stopped during installing(updating... then stopped). And never boot again.
If i turn on, i can see 'N' logo with black screen, but no process. How can I reboot my NT? I want it to be the very factory setting. -.-;; Or can I find factory-base recovery file anywhere?
edit: Wait you have an 8gb tablet? Have you tried to flash 1.4.2 with cwm?
yes...
I have an 8g NT that was 1.4.2.
any backup file or booting file? please...
Good! Use cwm to flash 1.4.2 update. see if that works
thanks !!
for the quick and helpful response!!
but where can i find it? (sorry, I am not expert.)
any link? i've tried, but i can't.
and is it *.img? if so it will be OK.
but it cannot be booted, so i cannot use Nook Recovery Flasher.apk.
http://forum.xda-developers.com/showpost.php?p=24164043&postcount=1
.. read the ATTENTION 8GB USERS and apply it, and also read the READ ME (link)
~ Veronica
lavero.burgos said:
http://forum.xda-developers.com/showpost.php?p=24164043&postcount=1
.. read the ATTENTION 8GB USERS and apply it, and also read the READ ME (link)
~ Veronica
Click to expand...
Click to collapse
Wait wait wait, not to get off topic or anything. But is the 1.4.2 update, the same thing for both 8gb and 16gb nooks?/
---------- Post added at 02:26 PM ---------- Previous post was at 02:25 PM ----------
firstgleam said:
for the quick and helpful response!!
but where can i find it? (sorry, I am not expert.)
any link? i've tried, but i can't.
and is it *.img? if so it will be OK.
but it cannot be booted, so i cannot use Nook Recovery Flasher.apk.
Click to expand...
Click to collapse
Have you made a bootable sdcard?? Make you sure have at least a 2gb microsd.
soshite said:
Wait wait wait, not to get off topic or anything. But is the 1.4.2 update, the same thing for both 8gb and 16gb nooks?
Click to expand...
Click to collapse
Yes stock 1.4.2 works for both, remember 8GB NT came with 1.4.2 it is why devs base on 1.4.2 mlo, uboot, etc files to make their hacks that work for both models.
~ Veronica
Huh~
I cannot do it.
I tried several times, but failed.
My situatuion;
1. Cannot boot
2. If i try to boot, i can see only 'n' logo with black screen
3. I can boot with SD to CM7(Team-B-CM7SD-Alpha_final). In this case, I can do nothing with NT. but I can enjoy CM7 in SD.
4. I tried several times,especially, i can see sometimes <booti: bad boot img>.
How and where can i start?
firstgleam said:
I cannot do it.
I tried several times, but failed.
My situatuion;
1. Cannot boot
2. If i try to boot, i can see only 'n' logo with black screen
3. I can boot with SD to CM7(Team-B-CM7SD-Alpha_final). In this case, I can do nothing with NT. but I can enjoy CM7 in SD.
4. I tried several times,especially, i can see sometimes <booti: bad boot img>.
How and where can i start?
Click to expand...
Click to collapse
It's the stupid script in Barnes & Noble's file. Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip
Now, on your "update" folder, navigate over to /META-INF/com/google/android/
And edit "updater-script" with notepad or something, and delete these two lines:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Click to expand...
Click to collapse
Sweet amirite? Save it, and then move everything inside "update" onto the update.zip folder we just made. Don't move the folder, move the contents.
Then put that in the sdcard, boot into clockworkmod again and try to flash update.zip
The reason I have you do all that is because it's signed. At least that's what I think is going on, because I can't edit the files from within the zip itself.
I can't get into clockworkmod.
I can't make booting.
Always I failed.
I can just see 'N' logo....
But you said you tried to flash the update in cwm? ??
firstgleam said:
I cannot do it.
I tried several times, but failed.
My situatuion;
1. Cannot boot
2. If i try to boot, i can see only 'n' logo with black screen
3. I can boot with SD to CM7(Team-B-CM7SD-Alpha_final). In this case, I can do nothing with NT. but I can enjoy CM7 in SD.
4. I tried several times,especially, i can see sometimes <booti: bad boot img>.
How and where can i start?
Click to expand...
Click to collapse
Did you follow my instructions to the T? What errors do you get if any when flashing stock recovery or the B&N stock 1.4.2 update. zip?
If you can boot into cm7 or @meghd00t cwm recovery from sdcard all you have to do is use dd to flash stock recovery and then run the update from another sdcard.
Don't try random unbrick methods, you can make it worst, your problem is not to go and mess with advanced methods. At list yet. But if you have messed around even more since then your boot block can get damaged. Go safe first.
~ Veronica
Sent from my BNTV250A using xda premium
---------- Post added at 10:43 AM ---------- Previous post was at 10:25 AM ----------
soshite said:
It's the stupid script in Barnes & Noble's file. Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip
Now, on your "update" folder, navigate over to /META-INF/com/google/android/
And edit "updater-script" with notepad or something, and delete these two lines:
Sweet amirite? Save it, and then move everything inside "update" onto the update.zip folder we just made. Don't move the folder, move the contents.
Then put that in the sdcard, boot into clockworkmod again and try to flash update.zip
The reason I have you do all that is because it's signed. At least that's what I think is going on, because I can't edit the files from within the zip itself.
Click to expand...
Click to collapse
CWM update.zip and B&N update.zip structure is different, so by naming B&N software update "update.zip" (meant to only be booted and flashed from sdcard) wouldn't be right and i doubt it could be flashed in CWM...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
However if you want to convert a B&N update.zip to CWM update.zip you just need:
* META-INF folder
* system folder
* boot.img
* romrestore.zip
But most likely when you attempt to reboot to stock unrooted 1.4.2 you will get bootloop, so it why is better to flash rooted roms in CWM so there is no conflict between unrooted ROM and CWM custom recovery. B&N Stock unrooted 1.4.x ROMS need stock recovery
~ Veronica
lavero.burgos said:
Did you follow my instructions to the T? What errors do you get if any when flashing stock recovery or the B&N stock 1.4.2 update. zip?
If you can boot into cm7 or @meghd00t cwm recovery from sdcard all you have to do is use dd to flash stock recovery and then run the update from another sdcard.
Don't try random unbrick methods, you can make it worst, your problem is not to go and mess with advanced methods. At list yet. But if you have messed around even more since then your boot block can get damaged. Go safe first.
~ Veronica
Sent from my BNTV250A using xda premium
---------- Post added at 10:43 AM ---------- Previous post was at 10:25 AM ----------
CWM update.zip and B&N update.zip structure is different, so by naming B&N software update "update.zip" (meant to only be booted and flashed from sdcard) wouldn't be right and i doubt it could be flashed in CWM...
However if you want to convert a B&N update.zip to CWM update.zip you just need:
* META-INF folder
* system folder
* boot.img
* romrestore.zip
But most likely when you attempt to reboot to stock unrooted 1.4.2 you will get bootloop, so it why is better to flash rooted roms in CWM so there is no conflict with the custom recovery. Stock unrooted 1.4.x ROMS need stock recovery
~ Veronica
Click to expand...
Click to collapse
All it will do is replace the recovery.img and all the other files. B&N updates not only flash /system but /recovery and /bootloader too if I remember correctly.
soshite said:
All it will do is replace the recovery.img and all the other files. B&N updates not only flash /system but /recovery and /bootloader too if I remember correctly.
Click to expand...
Click to collapse
Is why nooktablet_1_4_2_update.zip needs to be flashed from sdcard as it was meant to.
~ Veronica
lavero.burgos said:
Is why nooktablet_1_4_2_update.zip needs to be flashed from sdcard as it was meant to.
~ Veronica
Click to expand...
Click to collapse
That's what I`ve been saying :3
Sent from my NookTablet using XDA
thanks, lots of helps.
I'm not alone.
(but... mm... my knowledge is poor and so Engilsh.)
I can boot with Team-B-CM7SD-Alpha_final only with SDcard.
So I can see CM7 and use CM7.
BUT I can't access PC, PC and NT do not recognise each other so I cannot modify anything.
If I try to reboot with any other method, it will be fialed.
I tried meghd00t-r4, but just can see <booti: bad boot img...>.
I will try again today.
Then I will report.
Thanks anyway.
I Really appriciate.
soshite said:
That's what I`ve been saying :3
Sent from my NookTablet using XDA
Click to expand...
Click to collapse
i dont think so 'cause you were giving other instructions: " Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip"
---------- Post added at 12:16 PM ---------- Previous post was at 12:09 PM ----------
firstgleam said:
thanks, lots of helps.
I'm not alone.
(but... mm... my knowledge is poor and so Engilsh.)
I can boot with Team-B-CM7SD-Alpha_final only with SDcard.
So I can see CM7 and use CM7.
BUT I can't access PC, PC and NT do not recognise each other so I cannot modify anything.
If I try to reboot with any other method, it will be fialed.
I tried meghd00t-r4, but just can see <booti: bad boot img...>.
I will try again today.
Then I will report.
Thanks anyway.
I Really appriciate.
Click to expand...
Click to collapse
Alright this "BUT I can't access PC, PC and NT do not recognise each other so I cannot modify anything." needs to be fixed, you need to get adb working if you want to unbrick your device is a must now these days until @meghd00t release a new powerful tool meant to be ran from sdcard so better let's troubleshoot that first.
Boot into CM7 or CWM from sdcard and let us know where are you stuck in setting adb up. what errors or notifications do you get if any.
Oh BTW which model do you have 8GB or 16GB? that's very important
[HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Videos - Tutorial
~ Veronica
lavero.burgos said:
i dont think so 'cause you were giving other instructions: " Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip"
Click to expand...
Click to collapse
The reason I had him unzip it is because the file is signed, but he needs to opt out two lines so that it can be flashed in cwm. This is what I said:
It's the stupid script in Barnes & Noble's file. Go ahead and unpack the 1.4.2 update into a folder, name it like "update" or something. Onto your computer by the way! Make a new zip, just call it update.zip
Now, on your "update" folder, navigate over to /META-INF/com/google/android/
And edit "updater-script" with notepad or something, and delete these two lines:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Click to expand...
Click to collapse
Sweet amirite? Save it, and then move everything inside "update" onto the update.zip folder we just made. Don't move the folder, move the contents.
Then put that in the sdcard, boot into clockworkmod again and try to flash update.zip
The reason I have you do all that is because it's signed. At least that's what I think is going on, because I can't edit the files from within the zip itself.
Click to expand...
Click to collapse
acclaim_update.zip itself can be flashed in cwm as well. You just have to edit the updater-script in its folder. For whatever reason, B&N's updater script has device set to blaze. ????
-.-
thank you, Veronica and other guys^^
I will try again.
I have to go business trip with my boss.
-.-
It will be a sort of nightmare this weekend.
See you on the next week days.
Hi all,
Just to share this script for convenience. It's mainly for those who use AllShare Cast dongle but prefer custom kernel/recovery. You need to edit the script settings to provide the path of your prefered stock kernel/recovery (get from sammobile.com or from the list below). Please remember to extract the *.img if it's an archive. Refer below for details.
Notes:
If you're upgrading the script, just remember to copy over the script settings 'Begin Settings' to 'End Settings'. Custom kernel/recovery settings are no longer needed as of v0.2. Existing images will be retrieved directly from device, so you can upgrade custom kernel/recovery without modifying the script settings.
Stock kernel/recovery images:
MF2-BOOT-RECOVERY-N7100.zip.
MF2-BOOT-RECOVERY-N7105.zip.
AllShare Cast compatible Custom ROMs:
(N7100) Moon Rom V9 - confirmed by xastunts.
(N7105) JD€VIL S€RI€S INT€RNΔTIΩNΔL {roms} T€AM ZΩDIΔC - confirmed by alexdr1.
Change log:
v0.1 - 1st release (-:
----------------------
Script is to perform a one step click from custom to stock kernel/recovery while also reseting the flash counter using CF's TriangleAway. The system will stay stock but rooted until the next reboot. E.g. I would run custom kernel/recovery for daily use, I'll execute the script once if I need to use the AllShare Cast dongle, then just reboot when done to auto revert back to custom kernel/recovery.
As long as your phone is supported by TriangleAway, this script should work. Tested only on stock rom, you will have to find out if your custom rom works with AllShare Cast dongle. Until someone managed to figure out how to enable this, we need to have stock kernel/recovery to use the AllShare Cast dongle.
Script requires root, also needs busybox and Chainfire's TriangleAway, both installer available from Google Play Store. Optionally you can get the Script Manager app to create a widget shortcut of this script to the home screen. Finally, I'm not responsible to any risk taken by you for using this script.
v0.2
----------------------
Get images from device, custom settings no longer needed.
Skipped TA flash kernel to speed up initial reboot.
Direct SU execution, incase not running as root.
Improve path with spaces and script clean up.
v0.3
----------------------
Revised device detection for custom roms.
Script preview:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Running with Script Manager app:
Click to expand...
Click to collapse
Hi,
I was looking for something like this...
I will try it later and let you know if this worked on custom rom... I am using omega v17
Thanks
lonelime said:
Hi,
I was looking for something like this...
I will try it later and let you know if this worked on custom rom... I am using omega v17
Thanks
Click to expand...
Click to collapse
Great, maybe I can add to a list of working custom roms...
yeeeesss!!!
if this **** works ur the maaaan!! im gonna test this first thing tmr morning just gonna need to sleep this night out for now. im running moon rom v9 with floating windows and if i can make my allshare cast work with this script its gonna rock!!
Nazar78 said:
Great, maybe I can add to a list of working custom roms...
Click to expand...
Click to collapse
please help me find the boot img and recovery file needed for this! thank you!
xastunts said:
please help me find the boot img and recovery file needed for this! thank you!
Click to expand...
Click to collapse
https://www.dropbox.com/s/34q64494pgw0crz/MF2-BOOT-RECOVERY-N7100.zip
Nazar78 said:
https://www.dropbox.com/s/34q64494pgw0crz/MF2-BOOT-RECOVERY-N710en i0.zip
Click to expand...
Click to collapse
thanks for the boot image and the recovery img file! i just been thinking abit about this and i would like if you perhaps could explain how to use this step by step.
you said that after youre been running this script and wants to go back to ur custom rom and kernel again you only needs to reboot and it takes u right back to where you where. how does it nows which kernel and recovery i used? does it back it up?
when i look at this picture you attached here at "the begin settings" its a path for stock kernels /sdcard/document/backups/bla bla bla and then/boot.img
and same for the recovery but /recovery.img at the end.
and next is custom kernel/recovery image path.
kernel /sdcard/download/perseus-alpha-n7100/boot.img
and recovery /sdcard/download/twrp/openrecovery/recovery.img
i made the file folders shorter just to understand and explain it more quicker i know this is the very correct file folders.
u understand my point right? there is a 2 file needed for stock kernel and recovery boot.img, recovery.img
and 2 more files for the custom kernel and recovery boot.img, recovery.img.
in the zip file you attached there is only 1 set of 2 files boot.img, recovery.img.
so my question is what do i do with this files then??
if you just please could explain step by step. like
step1 install busy box
step 2 install triangle away
step 3 run script manager and add script
step 4 execute script and done
something like this! thank you for your effort and sorry if it sounds like i complain to much i just want to make sure we dont brick our devices
doing something wrong here! thanks!!
haha no problem, u got it all right about the files and steps. The zip files I posted contains stock kernel and recovery from latest N7100 MF2 rom (so u don't have to download the 1GB full rom from sammobile). Sorry for the short description, did all those scripting and posting on the phablet :crying: Also sorry for the long paths, its binded to my external sdcard and its how I organize my files
Below are the detailed steps:
1) Install busybox (Usually custom kernel has this, but not the latest. Recommended to install at /system/xbin/ because rom may go haywire if installed in /system/bin/).
2) Install the ultimate magic, TriangleAway from Chainfire (Launch the TA app at least once to download the flash kernel).
3) Settings 1 & 2 are your preferred STOCK kernel/recovery full path (the ones I posted from dropbox). Filenames doesn't have to be boot/recovery.img. You can place them anywhere even in external sdcard
4) Settings 3 & 4 are your preferred CUSTOM kernel/recovery full path (extract the *.img from the tar or zip you got from the developer). Filenames doesn't have to be boot/recovery.img. You can place them anywhere even in external sdcard
5) Setting 5 is the busybox path where you installed earlier.
6) Optionally install Script Manager and add this script to run as root(SU). You can add a widget to this script onto your home screen for easy script execution.
how does it nows which kernel and recovery i used?
Click to expand...
Click to collapse
It doesn't know, this is where settings 1 to 4 being used. It's to use tell the script that I want to use these stock and custom kernel/recovery images during the operation. So remember to update the settings if you update to a newer kernel/recovery in the future.
How it works it that, you use your custom kernel/recovery daily, then at one time you need to use AllShare Cast, all you need is just to run the script once. It will flash the stock kernel/recovery (from settings 1 & 2), reboot and let TriangleAway reset the counter and bootup with the stock kernel/recovery (again from settings 1 & 2), . When you are done with the AllShare Cast, just reboot. Your custom kernel/recovery (from settings 3 & 4), will be auto restored.
The long winded way to make AllShare Cast works is to manually flash stock kernel/recovery, reset counter using TriangleAway in recovery mode, use AllShare Cast, then reflash custom kernel/recovery again. This script cuts the hassle into 1 :laugh:
Nazar78 said:
haha no problem, u got it all right about the files and steps. The zip files I posted contains stock kernel and recovery from latest N7100 MF2 rom (so u don't have to download the 1GB full rom from sammobile). Sorry for the short description, did all those scripting and posting on the phablet :crying: Also sorry for the long paths, its binded to my external sdcard and its how I organize my files
Below are the detailed steps:
1) Install busybox (Usually custom kernel has this, but not the latest. Recommended to install at /system/xbin/ because rom may go haywire if installed in /system/bin/).
2) Install the ultimate magic, TriangleAway from Chainfire (Launch the TA app at least once to download the flash kernel).
3) Settings 1 & 2 are your preferred STOCK kernel/recovery full path (the ones I posted from dropbox). Filenames doesn't have to be boot/recovery.img. You can place them anywhere even in external sdcard
4) Settings 3 & 4 are your preferred CUSTOM kernel/recovery full path (extract the *.img from the tar or zip you got from the developer). Filenames doesn't have to be boot/recovery.img. You can place them anywhere even in external sdcard
5) Setting 5 is the busybox path where you installed earlier.
6) Optionally install Script Manager and add this script to run as root(SU). You can add a widget to this script onto your home screen for easy script execution.
It doesn't know, this is where settings 1 to 4 being used. It's to use tell the script that I want to use these stock and custom kernel/recovery images during the operation. So remember to update the settings if you update to a newer kernel/recovery in the future.
How it works it that, you use your custom kernel/recovery daily, then at one time you need to use AllShare Cast, all you need is just to run the script once. It will flash the stock kernel/recovery (from settings 1 & 2), reboot and let TriangleAway reset the counter and bootup with the stock kernel/recovery (again from settings 1 & 2), . When you are done with the AllShare Cast, just reboot. Your custom kernel/recovery (from settings 3 & 4), will be auto restored.
The long winded way to make AllShare Cast works is to manually flash stock kernel/recovery, reset counter using TriangleAway in recovery mode, use AllShare Cast, then reflash custom kernel/recovery again. This script cuts the hassle into 1 :laugh:
Click to expand...
Click to collapse
Thanks alot for this I will try this ASAP when I get back home.
edit.. im trying and wait for comments soon as soon as its done testing.
Nazar78 said:
haha no problem, u got it all right about the files and steps. The zip files I posted contains stock kernel and recovery from latest N7100 MF2 rom (so u don't have to download the 1GB full rom from sammobile). Sorry for the short description, did all those scripting and posting on the phablet :crying: Also sorry for the long paths, its binded to my external sdcard and its how I organize my files
Below are the detailed steps:
1) Install busybox (Usually custom kernel has this, but not the latest. Recommended to install at /system/xbin/ because rom may go haywire if installed in /system/bin/).
2) Install the ultimate magic, TriangleAway from Chainfire (Launch the TA app at least once to download the flash kernel).
3) Settings 1 & 2 are your preferred STOCK kernel/recovery full path (the ones I posted from dropbox). Filenames doesn't have to be boot/recovery.img. You can place them anywhere even in external sdcard
4) Settings 3 & 4 are your preferred CUSTOM kernel/recovery full path (extract the *.img from the tar or zip you got from the developer). Filenames doesn't have to be boot/recovery.img. You can place them anywhere even in external sdcard
5) Setting 5 is the busybox path where you installed earlier.
6) Optionally install Script Manager and add this script to run as root(SU). You can add a widget to this script onto your home screen for easy script execution.
It doesn't know, this is where settings 1 to 4 being used. It's to use tell the script that I want to use these stock and custom kernel/recovery images during the operation. So remember to update the settings if you update to a newer kernel/recovery in the future.
How it works it that, you use your custom kernel/recovery daily, then at one time you need to use AllShare Cast, all you need is just to run the script once. It will flash the stock kernel/recovery (from settings 1 & 2), reboot and let TriangleAway reset the counter and bootup with the stock kernel/recovery (again from settings 1 & 2), . When you are done with the AllShare Cast, just reboot. Your custom kernel/recovery (from settings 3 & 4), will be auto restored.
The long winded way to make AllShare Cast works is to manually flash stock kernel/recovery, reset counter using TriangleAway in recovery mode, use AllShare Cast, then reflash custom kernel/recovery again. This script cuts the hassle into 1 :laugh:
Click to expand...
Click to collapse
i got this error cant execute permission denied! and also error file doesnt exist. pls have a look at the screen shot and maybe u know whats wrong. thanks buddy!
edit **** i thought i did this slow and good but i got it wrong at the adress. i post as soon as it works.
edit i have tripple checked and the adress is correctly written to adress the boot img and recovery.img . now i need ur help!
pls help me when you get back online nazar thank you.
Do u have spaces in the path for any of the 4 settings? For instance the one I saw in you screenshot moon_image/recovery.img?
Please paste here from begin settings to end settings...
Nazar78 said:
Do u have spaces in the path for any of the 4 settings? For instance the one I saw in you screenshot moon_image/recovery.img?
Please paste here from begin settings to end settings...
Click to expand...
Click to collapse
the adress is 100 % correct but if u dont believe me i can try put them straight on phone and also straight on extsd and try both methods. u dont think its about the permissions? it said about it in the beginning of the errors.
Nazar78 said:
Do u have spaces in the path for any of the 4 settings? For instance the one I saw in you screenshot moon_image/recovery.img?
Please paste here from begin settings to end settings...
Click to expand...
Click to collapse
i tried put the files directly on phone main folder. look at the screens pls. it must be the permissions.
I see the issue...
recoveryc= "/storage....
Should not have a space between = and "... Its how shell script works. Maybe u accidentally paste the space there.
recoveryc="/storage...
Nazar78 said:
I see the issue...
recoveryc= "/storage....
Should not have a space between = and "... Its how shell script works. Maybe u accidentally paste the space there.
recoveryc="/storage...
Click to expand...
Click to collapse
i test this right away! i will let u know!
okay we got past that thing now! but this time a new error it says ERROR: are you running as root?
and ofcourse my phone is rooted.
SU checked?
View attachment 2113308
Nazar78 said:
SU checked?
View attachment 2113308
Click to expand...
Click to collapse
nope it wasnt! i think u forgot to tell me that. and my new problem is ERROR: please install and run cfs triangleaway at least once to get the flash kernel..
do u think u can help me with that? i got the triangle away apk from google, but i have started the app and pressed reset flash counter it was 40 and now its 0 so that part worked. maybe i just need the flash kernel now? maybe u can pls send me the flash kernel?
edit actually i got it here on xda but i searched from google to find it. TriangleAway-v3.00.apk
6) Optionally install Script Manager and add this script to run as root(SU). You can add a widget to this script onto your home screen for easy script execution.
I did :laugh:
Once u launch TriangleAway for the 1st time, it will auto download the flash kernel. Now that u already reset the counter, u can continue run the script.
Can u confirm its there?
/data/data/eu.chainfire.triangleaway/files/eu.chainfire.triangleaway.flashkernel.n7100
Nazar78 said:
6) Optionally install Script Manager and add this script to run as root(SU). You can add a widget to this script onto your home screen for easy script execution.
I did :laugh:
Once u launch TriangleAway for the 1st time, it will auto download the flash kernel. Now that u already reset the counter, u can continue run the script.
Can u confirm its there?
/data/data/eu.chainfire.triangleaway/files/eu.chainfire.triangleaway.flashkernel.n7100
Click to expand...
Click to collapse
i can confirm that i dont have that file there! in my /data/data/eu.chainfire.triangleaway/files/ there is only one png file triangleawaysr.png
if you send me that file and i put it in that folder it might even not work as the program itself should know the file is there. but i could try that if u dont mind.
---------- Post added at 09:26 PM ---------- Previous post was at 09:17 PM ----------
Nazar78 said:
6) Optionally install Script Manager and add this script to run as root(SU). You can add a widget to this script onto your home screen for easy script execution.
I did :laugh:
Once u launch TriangleAway for the 1st time, it will auto download the flash kernel. Now that u already reset the counter, u can continue run the script.
Can u confirm its there?
/data/data/eu.chainfire.triangleaway/files/eu.chainfire.triangleaway.flashkernel.n7100
Click to expand...
Click to collapse
could you please send me that file? and ps oh! i see ur thanks meeter keeps increasing! i wonder why!! ds
DISCLAIMER:
No one is responsible if you brick your phone or it doesn't boot!
BIG CREDITS TO ZROICE FOR THE SCRIPT, OR THIS WOULDNT BE POSSIBLE.:
Video for the noobs(Thanks DiabeticSwag:
CLICK HERE FOR VIDEO.
Before We Start:
- When I use the term "sdcard" that means the phones built in storage.
- If you are currently on MJ5 and want to restore,incase you made a mistake click here, CLICK HERE TO RESTORE PHONE TO MI9 IF YOU BRICKED MJ5
- VIDEO Tutorial is coming whenever codeman05 finishes it. He is my new partner in this.
Downloads-In Order:
- Download Kn0x0ut from this link,
- Download The second file you need (if flashing international base rom) from this link,
Extras:
-NOT required.Just extras, Att csc files
Requirements:
- Rooted Rom
- Busybox installed. Check by downloading the app in the playstore.
- Basic ADB knowledge
- Windows pc
THERE ARE 2 SETS OF INSTRUCTIONS, BE SURE TO FOLLOW THE INSTRUCTIONS PER ROM BASE YOU WILL BE FLASHING!!
Installation:
Flashing T-Mobile Rom Instructions:
SAME AS DIRECTIONS FOR INTERNATIONAL ROM INSTRUCTIONS, BUT DONT DO STEPS 6-8.
Flashing International Rom Instructions:
MUST use Kn0x0ut 1.03.Link in beginning of this post.
1) Odin to a fresh start and root,NOT REQUIRED (any rooting firmware should work of course).
2) Download rom of choice
3) Copy & Extract Kn0x0ut 1.03 to /sdcard
3) Extract Rom and Copy "system" and "data" to /sdcard/kn0x0ut/ extract_files_here
4) Execute this
adb shell
su
mount -o rw,remount /system
cd /sdcard/kn0x0ut
sh kn0x0ut.sh new_rom
Click to expand...
Click to collapse
5) Manually reboot
6) Copy "system" from "Fixforeverything" to /sdcard/kn0x0ut/extract_files_here
7) Execute this
adb shell
su
mount -o rw,remount /system
cd /sdcard/kn0x0ut
sh kn0x0ut.sh install
Click to expand...
Click to collapse
8) Manually reboot
After that, everything is working for me,except "Language & Input" in settings...which I will try fixing.
WIFI works
Contacts works
Camera works
Credits:
-Codeman05 for testing/code manager.
-KingRedHot for organizing this post.
-Original developer for script.
-Bri315317 for more testing
-Raiderman for wifi fix
-DiabeticSwag for video
IF YOUR WIFI WONT EVEN TURN ON, FOLLOW THIS :
Raiderman said:
Got it working......ficken A! These were my steps...
Started with Stock odin image
New_Rom SweetRom, from the international forum ( Had nothing working)
Installed fix (still nothing working)
New_Rom X-note (Wifi and NFC came alive, Camera FC)
Install fix again (Camera, wifi, nfc working. Contacts FC)
Opened playstore, and contacts started working again.
Click to expand...
Click to collapse
Hmm seems legit. Think I'll wait for someone else to try it though. Would be nice to see some Roms float to the att forums
Sent from my SAMSUNG-SM-N900A using Tapatalk
Im thinking of building my own rom with this but I wanna confirm if I can port a t-mobile rom to our phone. Much faster.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Until they figure out how to unlock the bootloader, you will never be able to flash any ROM to this phone regardless of the method since flashing a ROM requires irt to be flashed to the boot rom which also holds the bootloader and is currently locked tighter then Obamas death grip on the US.
Well we can actually modify system files its just the boot.img that we cant mess with. I have faith
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Hm. They are saying as long as you can mount the root directory writable this is an option....
We are waiting for the Safestrap to come out. Then we will flash
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
But the more options avaliable the better. You never know, one of these workarounds may lead to a way to unlock the bootloader.
This might work if we run tb fixer right before trying this. Since it fixes the selinux flags.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Someone within 14 day or who can recover a hard/soft brick be the hero and try it
Sent from my SAMSUNG-SM-N900A using Tapatalk
MrPlNK said:
Someone within 14 day or who can recover a hard/soft brick be the hero and try it
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
That would be nice...
Solarenemy68 said:
Until they figure out how to unlock the bootloader, you will never be able to flash any ROM to this phone regardless of the method since flashing a ROM requires irt to be flashed to the boot rom which also holds the bootloader and is currently locked tighter then Obamas death grip on the US.
Click to expand...
Click to collapse
Ha ha Obama sucks
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
We'll never know at this rate. I dont have the balls to try it
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I'm still running MI9 and have the one click to go back if i need too. I am going for it! i have downloaded X Note an in process of copying it over to my SD card. Will report back shortly. Wish me luck!
Edit: 1st attempt ended up in boot loop with the script complaining of a lot of stuff not found. Will one click back and try again.
Edit 2: 2nd attempt was for the gold! now running Xnote 5.1 using the Kn0x0ut script with a few minor changes...
Do not try this if you are running MJ5!!!
Only attempt if you are able to One-click back to MI9!!!
1st Extract the kn0x0ut folder to your sdcard.
2nd Download rom and extract the data and system folder to the "put_files_here" folder
Launch ADB and allow it to connect to phone. USB debugging must be on
Enter the following in the console and grant SU permission when prompted on the device.
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
cd /sdcard/kn0x0ut
sh kn0x0ut.sh new_rom
Wait for finish, then manually reboot by holding the power button until it reboots.
Most likely you will need to enter your APN manually.
Please press thanks if this helped you!
One damn brave soul! Thanks a lot man. Wish i still had MJ5 could of done something to get a custom rom running. Can't do warranty exchange as i got Spigen glas.tr on it. Now I will need to explore my option on getting MJ5!
bri315317 said:
I'm still running MI9 and have the one click to go back if i need too. I am going for it! i have downloaded X Note an in process of copying it over to my SD card. Will report back shortly. Wish me luck!
Edit: 1st attempt ended up in boot loop with the script complaining of a lot of stuff not found. Will one click back and try again.
Edit 2: 2nd attempt was for the gold! now running Xnote 5.1 using the Kn0x0ut script with a few minor changes...
Do not try this if you are running MJ5!!!
Only attempt if you are able to One-click back to MI9!!!
1st Extract the kn0x0ut folder to your sdcard.
2nd Download rom and extract the data and system folder to the "put_files_here" folder
Launch ADB and allow it to connect to phone. USB debugging must be on
Enter the following in the console and grant SU permission when prompted on the device.
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
sh kn0x0ut.sh new_rom
Wait for finish, then manually reboot by holding the power button until it reboots.
Most likely you will need to enter your APN manually.
Please press thanks if this helped you!
Click to expand...
Click to collapse
appdroid said:
One damn brave soul! Thanks a lot man. Wish i still had MJ5 could of done something to get a custom rom running. Can't do warranty exchange as i got Spigen glas.tr on it. Now I will need to explore my option on getting MJ5!
Click to expand...
Click to collapse
You need to be on MI9
MJ5 would be very risky!!!
Anyone still running MI9 and has the one click files could try this with minimal danger i believe.
bri315317 said:
I'm still running MI9 and have the one click to go back if i need too. I am going for it! i have downloaded X Note an in process of copying it over to my SD card. Will report back shortly. Wish me luck!
Edit: 1st attempt ended up in boot loop with the script complaining of a lot of stuff not found. Will one click back and try again.
Edit 2: 2nd attempt was for the gold! now running Xnote 5.1 using the Kn0x0ut script with a few minor changes...
Do not try this if you are running MJ5!!!
Only attempt if you are able to One-click back to MI9!!!
1st Extract the kn0x0ut folder to your sdcard.
2nd Download rom and extract the data and system folder to the "put_files_here" folder
Launch ADB and allow it to connect to phone. USB debugging must be on
Enter the following in the console and grant SU permission when prompted on the device.
Code:
adb shell
su
stop
mount -o rw,remount /system/ /system/
sh kn0x0ut.sh new_rom
Wait for finish, then manually reboot by holding the power button until it reboots.
Most likely you will need to enter your APN manually.
Please press thanks if this helped you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
So.......?
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
---------- Post added at 07:17 AM ---------- Previous post was at 07:14 AM ----------
Sorry quoted the wrong post.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Told you guys, I have faith and it worked.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Holy ****!! Nice. What do u mean running m19? I'm sorry I just got the note 3 to test. Thanks.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
zounduser said:
Holy ****!! Nice. What do u mean running m19? I'm sorry I just got the note 3 to test. Thanks.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
MI9 is the build version for the att version. Recently MJ5 was released and would be very risky to try this while on MJ5.
Sent from my SM-N9005 using Tapatalk
Hi everyone.
The Japanese version of LG G2 DoCoMo L-01F has the special "ccsecurity" access control system.
That has prevented us from rooting!
So we used the CVE-2013-6282 vulnerability to take root.
Here is the automagic rootkit for you!
WARNING
ROOTING WILL DISABLE YOUR WARRANTY.
YOU MAY BE UNABLE TO GET SUPPORT FROM THE DOCOMO SHOP.
YOU MAY BRICK YOUR PHONE.
YOU MAY BE UNABLE TO GET OFFICIAL UPDATES.
Download
L-01F Rootkit ver8 androidfilehost
How to use
Basically run the batch and read instructions!
PROTIP
Do not attempt to do official updates.
Install busybox from the Google Play.
Push the volume up button with the power button to boot to recovery menu.
Take backup from recovery.
Unrooting
If you just want to disable root, use the uninstall root option of the supersu app.
If you want to wipe all data and have a clean rom , write tot/kdz from this thread.
Credit
fi01 for adapting CVE-2013-6282 rootkit github
Tohno for helping me make L01F11k rootkit.
thecubed for bump.
blastagator for twrp source.
And many testers!
Helping you
Many people has sent me help requests about the root relating things. This post should answer all common helps.
Q. The rootkit shows error"cannot stat ..... No such file or directory".
A. The folder name you put the rootkit in is likely Japanese. Place the rootkit in C drive root or some other English-named path.
Q. My games! Lovelive Puzzles&Dragons etc not playable after rooting. Why?
A.It detects root. It is a cheat prevention system of some games and apps. Use the rootcloak. If that is not working and you really want to play that game, then you have to unroot.
Q. My phone does't boot anymore. It stucks on the "docomo" logo.
A.Hold your power button for about 20 seconds to force shutdown. Then hold your power button and the volume up button at the same time to boot up to the recovery. Then restore your phone from the backup file you took.
Q.What do I need for the FOTA update?
A.Stock boot.img and recovery.img and system files.
Q. I did the FOTA update and recovery is looping.
A. That's because you forgot to unroot and the custom recovery is still there. The fix is included in my rootkit. Thanks to antond57.
Q. I did the FOTA update and some error screen came up and the update failed.
A. This indicates that you have modified your system too much to be updated. This is often caused by the xposed framework.
First, you need to root your phone again.
Second, download and install the system installer, boot installer, recovery installer from this thread.
Q. I cant find and install the LG adb driver for the recovery.
Try using the pdanet driver.
reserved
reserved
my phone is not booting up, so how can I download the system.img to my phone ?
also, if I use adb push system.img will that work ?
before rooting/installing ninjakernel. I would like to have a failsafe if I do something wrong and run into problems/bootloop etc. how do I backup the stock rom of our phones and reload it in case I run into problems?
[EDIT] never mind. figured it out. nandroid backup in cwm recovery.
what I meant was how to back up apps and data and launcher layout. but I guess I can just do that with mybackup and nova launcher backup and android sync.
sent from my LG G2 with tapatalk pro
bepari220 said:
my phone is not booting up, so how can I download the system.img to my phone ?
also, if I use adb push system.img will that work ?
Click to expand...
Click to collapse
I figured out that the "adb push" command can only send file up to 2GB
So please zip compress the system.img with your PC. It should shrink to 1.9GB. And then adb push it.
Then use the"unzip" command in your twrp to unzip it, and flash it by the "dd" command.
so to confirm. I download rootkit to pc, ninjakernel.zip to device. usb debugging on, connection to charge only. plug into pc, run root.exe will root device, install cwm recovery and boot into recovery. then I take nandroid backup in recovery and don't reboot but install from zip the ninjakernel then reboot. finished. yes?
sent from my LG G2 with tapatalk pro
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
also, I don't need to wipe nothing for the kernel?
sent from my LG G2 with tapatalk pro
supersonicninja said:
I figured out that the "adb push" command can only send file up to 2GB
So please zip compress the system.img with your PC. It should shrink to 1.9GB. And then adb push it.
Then use the"unzip" command in your twrp to unzip it, and flash it by the "dd" command.
Click to expand...
Click to collapse
so what would be the dd command if I push the image to /sdcard/system.img
oh ! I'm such a noob :silly:
bepari220 said:
so what would be the dd command if I push the image to /sdcard/system.img
oh ! I'm such a noob :silly:
Click to expand...
Click to collapse
All linux and windows commands are friendly to a noob! They have help. Type
Code:
dd --help
to see it.
In your case. You have to use these three commands.
First, zip compress system.img and name it to system.zip or something. Place it with the same folder as the adb.exe in your pc and open the adb shell and type these commands.
Code:
adb push system.zip /sdcard/
This sends the file over the USB cable.
Code:
unzip system.zip
This unzips the file.
Code:
dd if=/sdcard/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
This copies the file.
The "if=" means "input file" so where to copy from. And the "of=" means "output file" so where to copy to. Pretty obvious.
rooted now. working so far. thanks. great work
sent from my LG G2 with tapatalk pro
I was wondering about the bloatware on our phones. what's safe to freeze/delete. like the lg and docomo bloat. please advise
sent from my LG G2 with tapatalk pro
hay @supersonicninja
I did everything you said, but when I give the unzip command it just shows that it is unzipping...but after 1 hour it still shows that it is unzipping, whats wrong ?
all these happened after I flashed Ninja Kernel on my L01F10c (rooted, xposed installed) Stock Rom. My phone is not booting up
My Phone Condition :
1. Can go to recovery TWRP Touch.
2. Phone Storage 20994 MB
3. Full Wiped including Internal Memory
4. ADB Push works
5. Sideload also works
6. If I press power button : gets stuck at docomo logo with notification LEDs flashing nothing else.
I have all the stock .img files (L01F10c). I also have the L01F11k.kdz file.
Please advise how can I bring my phone back to life
bepari220 said:
hay @supersonicninja
I did everything you said, but when I give the unzip command it just shows that it is unzipping...but after 1 hour it still shows that it is unzipping, whats wrong ?
all these happened after I flashed Ninja Kernel on my L01F10c (rooted, xposed installed) Stock Rom. My phone is not booting up
My Phone Condition :
1. Can go to recovery TWRP Touch.
2. Phone Storage 20994 MB
3. Full Wiped including Internal Memory
4. ADB Push works
5. Sideload also works
6. If I press power button : gets stuck at docomo logo with notification LEDs flashing nothing else.
I have all the stock .img files (L01F10c). I also have the L01F11k.kdz file.
Please advise how can I bring my phone back to life
Click to expand...
Click to collapse
If you have the .kdz file, you can extract it for the .dll and the flashable dz file.
See this thread
got my phone working...but can't pull down notification bar down works fine on Landscape mode...maybe it's just my bad luck...
Hello there - I tried rooting using the zip file in the OP but it seems like there are files missing from the f10 folder. I'm not sure whether the files in the f11 folder are the same or not, so I didn't try to copy them over to the f10 folder. Could you let me know how to proceed? Many thanks!
mn147 said:
I was wondering about the bloatware on our phones. what's safe to freeze/delete. like the lg and docomo bloat. please advise
sent from my LG G2 with tapatalk pro
Click to expand...
Click to collapse
Freezing/deleting system apps are not a good idea. Some apps are called from the system framework. So if you delete apps, the framework may try to start the deleted app infinitely, causing severe CPU usage and battery drain.
help me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root LG G2 L-01F
I still do not understand how to root.
supersonicninja said:
reserved
Click to expand...
Click to collapse
pls fix the signal in the slim rom.
I tried rooting my phone . installed LG driver as well. but everytime i press option 3 and enter the command windows closes with flashing red screen.
any idea why is this happening. i copied the files in C drive.
Alright we have a CM9 for locked bootloader but we don't have CM10 and the people that want to help don't have a clue about where to begin.
I really didn't want to make a new thread but so much stuff is scattered in several places on this subject, and I don't feel like jacking peoples thread to answer "how to stuff".
artas182x already ported a 2nd-init (rom and recovery) for L9, so we just have to figure out the right settings to make CM10 boot.
Please read this thread http://forum.xda-developers.com/showthread.php?p=36706378
The only CM10 I have so far is from markolino631 http://forum.xda-developers.com/showthread.php?t=2313036
ROM
http://www.mediafire.com/download/fdka03ulxtxn1pg/cm-10-20130611-UNOFFICIAL-p760.zip
One of the first things you will need to learn is how to make a boot.tar or recovery.tar for locked bootloader.
How to make a boot.tar or recovery.tar
Things you will need Linux OS or cygwin (for windows), osm0sis's mkbootimg (Android Kitchen has it all set and ready to go), and last but not least a brain
okay you want to make a boot.tar, well we first need to get our hands on the boot.img. So I'll just use a stock boot.img for this example, but we really need CM10 boot.img.
I am using cygwin and Android Kitchen for this example.
First navigate to advance options (#0) select number #12 (in advanced options) and select option "a"(Extract kernel+ramdisk from boot.img/recovery.img in any folder).
Place the boot.img inside the new folder it specifies and hit enter. Afterwards you will have a "zImage" file and a "boot.img-ramdisk" folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: the Kitchen will get rid of the boot.img (so don't place your only boot.img copy in that folder).
Click to expand...
Click to collapse
Now exit the Kitchen (just press Ctrl+c) and navigate to the new folder with cygwin (shorten the folder name if you want, like I did in my example).
Code:
Kuma [email protected] /home/Kuma/Kitchen
$ [B]cd bootimg_stock/boot.img-ramdisk/[/B]
Once in the "boot.img-ramdisk" folder we are all set to make the boot.tar
However, lets check the permission on all the files in that folder.
So type ls -ln and make a note of the permission for each file, without the proper permission it won't work for sure.
Another thing, if using cygwin make sure you move a folder properly. If you just move a folder (with Window explorer) you may loss the correct permission for those files. However, if you just change the name of a file it doesn't effect the permissions. I'll try and elaborate some more later.
Click to expand...
Click to collapse
Now type tar cvf boot.tar ./* and a new boot.tar will be created in that folder.
Code:
$ tar cvf boot.tar ./*
./charger
./data/
./default.prop
./dev/
./fota.rc
./init
./init.goldfish.rc
./init.lge.early.rc
./init.lge.rc
./init.lge.ril.rc
./init.lge.usb.rc
./init.lgep769board.rc
./init.post_boot.sh
./init.rc
./init.trace.rc
./init.u2.rc
./init.usb.rc
./lgdms.fota.rc
./lgdms.fota_update.rc
./proc/
./res/
./res/images/
./res/images/charger/
./res/images/charger/battery_0.png
./res/images/charger/battery_1.png
./res/images/charger/battery_2.png
./res/images/charger/battery_3.png
./res/images/charger/battery_4.png
./res/images/charger/battery_none.png
./res/images/charger/battery_overheat.png
./res/images/charger/battery_trickle_ani_01.png
./res/images/charger/battery_trickle_ani_02.png
./res/images/errorlogo.png
./sbin/
./sbin/adbd
./sbin/e2fsck_static
./sbin/lge_fota
./sbin/mke2fs_static
./sbin/resize2fs_static
./sbin/ueventd
./sbin/wallpaper
./sys/
./system/
./ueventd.goldfish.rc
./ueventd.lgep769board.rc
./ueventd.rc
Kuma [email protected] /home/Kuma/Kitchen/bootimg_stock/boot.img-ramdisk
$
Once you made your boot.tar (and made the changes you wanted) you can place the boot.tar in the system (/system/bootstrap/) with the correct permissions
Code:
chmod 755 /system/bootstrap/boot.tar
I already made a couple of recoveries and modified ram disk using this method.
For recovery type tar cvf recovery.tar ./*
I'll be posting some more stuff but i really have my hands full.
kuma82 said:
Alright we have a CM9 for locked bootloader but we don't have CM10 and the people that want to help don't have a clue about where to begin.
I really didn't want to make a new thread but so much stuff is scattered in several places on this subject, and I don't feel like jacking peoples thread to answer "how to stuff".
artas182x already ported a 2nd-init (rom and recovery) for L9, so we just have to figure out the right settings to make CM10 boot.
Please read this thread http://forum.xda-developers.com/showthread.php?p=36706378
The only CM10 I have so far is from markolino631 http://forum.xda-developers.com/showthread.php?t=2313036
ROM
http://www.mediafire.com/download/fdka03ulxtxn1pg/cm-10-20130611-UNOFFICIAL-p760.zip
One of the first things you will need to learn is how to make a boot.tar or recovery.tar for locked bootloader.
How to make a boot.tar or recovery.tar
Things you will need Linux OS or cygwin (for windows), osm0sis's mkbootimg (Android Kitchen has it all set and ready to go), and last but not least a brain
okay you want to make a boot.tar, well we first need to get our hands on the boot.img. So I'll just use a stock boot.img for this example, but we really need CM10 boot.img.
I am using cygwin and Android Kitchen for this example.
First navigate to advance options (#0) select number #12 (in advanced options) and select option "a"(Extract kernel+ramdisk from boot.img/recovery.img in any folder).
Place the boot.img inside the new folder it specifies and hit enter. Afterwards you will have a "zImage" file and a "boot.img-ramdisk" folder.
Now exit the Kitchen (just press Ctrl+c) and navigate to the new folder with cygwin (shorten the folder name if you want, like I did in my example).
Code:
Kuma [email protected] /home/Kuma/Kitchen
$ [B]cd bootimg_stock/boot.img-ramdisk/[/B]
Once in the "boot.img-ramdisk" folder we are all set to make the boot.tar
However, lets check the permission on all the files in that folder.
So type ls -ln and make a note of the permission for each file, without the proper permission it won't work for sure.
Now type tar cvf boot.tar ./* and a new boot.tar will be created in that folder.
Code:
$ tar cvf boot.tar ./*
./charger
./data/
./default.prop
./dev/
./fota.rc
./init
./init.goldfish.rc
./init.lge.early.rc
./init.lge.rc
./init.lge.ril.rc
./init.lge.usb.rc
./init.lgep769board.rc
./init.post_boot.sh
./init.rc
./init.trace.rc
./init.u2.rc
./init.usb.rc
./lgdms.fota.rc
./lgdms.fota_update.rc
./proc/
./res/
./res/images/
./res/images/charger/
./res/images/charger/battery_0.png
./res/images/charger/battery_1.png
./res/images/charger/battery_2.png
./res/images/charger/battery_3.png
./res/images/charger/battery_4.png
./res/images/charger/battery_none.png
./res/images/charger/battery_overheat.png
./res/images/charger/battery_trickle_ani_01.png
./res/images/charger/battery_trickle_ani_02.png
./res/images/errorlogo.png
./sbin/
./sbin/adbd
./sbin/e2fsck_static
./sbin/lge_fota
./sbin/mke2fs_static
./sbin/resize2fs_static
./sbin/ueventd
./sbin/wallpaper
./sys/
./system/
./ueventd.goldfish.rc
./ueventd.lgep769board.rc
./ueventd.rc
Kuma [email protected] /home/Kuma/Kitchen/bootimg_stock/boot.img-ramdisk
$
Once you made your boot.tar (and made the changes you wanted) you can place the boot.tar in the system (/system/bootstrap/) with the correct permissions
Code:
chmod 755 /system/bootstrap/boot.tar
I already made a couple of recoveries and modified ram disk using this method.
For recovery type tar cvf recovery.tar ./*
I'll be posting some more stuff but i really have my hands full.
Click to expand...
Click to collapse
what if the permissions of the files are not the same as the permissions thats in your screenshot?
just tried to make a rom and got a security error again. IDK what im doing wrong
This is sick. So once we have a boot.tar, do we just drop it onto a CM10 ROM for say, the P760? That seems all too easy and probably wrong.
Sent from my Nexus 7 using Tapatalk
ThEuNdYiNg1 said:
what if the permissions of the files are not the same as the permissions thats in your screenshot?
just tried to make a rom and got a security error again. IDK what im doing wrong
Click to expand...
Click to collapse
Need exact steps, or I won't be able to help.
More than like you aren't using a stock jellybean boot.img, that's why you are getting the security error.
Ilxaot said:
This is sick. So once we have a boot.tar, do we just drop it onto a CM10 ROM for say, the P760? That seems all too easy and probably wrong.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I wish it was that easy there are several other files that need to be replaced from stock, like libs and stuff.
I don't have the time to troubleshooting.
Building the rom from source is the best route, but my computer is crap.
If I knew how, I could try. I have a decent setup. The problem for me is that I have no history in development, only tweaks. And, I don't know how to make a ROM for an unlocked bootloader, so I get the feeling that if I look for help, I'll find results for unlocked bootloader ROMs and end up botching the ROM.
Sent from my Nexus 7 using Tapatalk
kuma82 said:
Need exact steps, or I won't be able to help.
More than like you aren't using a stock jellybean boot.img, that's why you are getting the security error.
I wish it was that easy there are several other files that need to be replaced from stock, like libs and stuff.
I don't have the time to troubleshooting.
Building the rom from source is the best route, but my computer is crap.
Click to expand...
Click to collapse
first thing is i download p760 cm10 and took the boot.img and decompiled it with cygwin i edited the names so instead of it saying init.lgep760board or whatever is it i changed it to p769 and i also changed in one of the files the name file for the .usb file to p769. then i made the boot.tar with your instructions. the recovery and everythin else is from the cm9 rom, i just took the bootstrap folder from there and put it in the cm10 rom
The stock boot.img is from your tweaked rom and i also copied all of the libs and things thats required to be modded like you did with cm9 for the p769 since my phone is a p769 and not a p760
ThEuNdYiNg1 said:
first thing is i download p760 cm10 and took the boot.img and decompiled it with cygwin i edited the names so instead of it saying init.lgep760board or whatever is it i changed it to p769 and i also changed in one of the files the name file for the .usb file to p769. then i made the boot.tar with your instructions. the recovery and everythin else is from the cm9 rom, i just took the bootstrap folder from there and put it in the cm10 rom
The stock boot.img is from your tweaked rom and i also copied all of the libs and things thats required to be modded like you did with cm9 for the p769 since my phone is a p769 and not a p760
Click to expand...
Click to collapse
I'm no expert, but that sounds about right. D:
Sent from my Nexus 7 using Tapatalk
I've been experimenting with porting different versions of CM (10.1 and 11), AOKP and PacMan (so basically Android 4.3 and 4.4). Didn't got them booting, but the recoveries did work and didn't give a Security Error.
Permissions in the files are important (the files you need to edit usally need 0755). You need to replace the boot.img of the ROM for the stock one and use the replaced boot.img to create a boot.tar. You also need to add a line to the updater-script that changes the permissions of the /system/bootstrap to 755, so the 2nd init script can access to them.
You also need to replace the e2fsck in /system/bin (and add the e2fsck.bin, which is the original binary). The kernel executes e2fsck to check the file system at boot, so it's the perfect candidate to launch the 2nd init process (since the original kernel executes this binary always at boot).
If you get the correct permissions in the files, the correct files replaced and edited, you may get past the Security Error. I'm now investigating why it hangs on the LG logo. I think I'm not building the boot.tar correctly, and that's why the 2nd init is unable to jump to it.
krashprocess said:
I've been experimenting with porting different versions of CM (10.1 and 11), AOKP and PacMan (so basically Android 4.3 and 4.4). Didn't got them booting, but the recoveries did work and didn't give a Security Error.
Permissions in the files are important (the files you need to edit usally need 0755). You need to replace the boot.img of the ROM for the stock one and use the replaced boot.img to create a boot.tar. You also need to add a line to the updater-script that changes the permissions of the /system/bootstrap to 755, so the 2nd init script can access to them.
You also need to replace the e2fsck in /system/bin (and add the e2fsck.bin, which is the original binary). The kernel executes e2fsck to check the file system at boot, so it's the perfect candidate to launch the 2nd init process (since the original kernel executes this binary always at boot).
If you get the correct permissions in the files, the correct files replaced and edited, you may get past the Security Error. I'm now investigating why it hangs on the LG logo. I think I'm not building the boot.tar correctly, and that's why the 2nd init is unable to jump to it.
Click to expand...
Click to collapse
so i basically need to replace that with stock file and it should work?
This thread may be of use.
http://forum.xda-developers.com/showthread.php?t=2725842
Sent from my LGMS769 using Tapatalk
ThEuNdYiNg1 said:
so i basically need to replace that with stock file and it should work?
Click to expand...
Click to collapse
No, you need the modified 2fsck, pull it from my tweak stock rom or somewhere else, like artas182x l9recovery apk. Another thing don't use the bootstrap files for CM9. Pull it from my rom as well.
Just so you know, I made the changes you are talking about (changing 760 to 769) and it didn't work. For some reason the data partition wouldn't mount. I'll give y'all some logcats later.
Sent from my LGMS769 using XDA Premium 4 mobile app
Hey Kuma, thanks so much for the guide. I'm getting stuck at the LG logo screen (before the boot animation). Obviously adbd is not getting started since I'm pretty sure my boot.tar is somehow wrong. Is it possible to still grab the logcats out of the device? I can still access the recovery (and replace it with different CWM for L9 versions). Thanks in advance.
And it's not just a matter of replacing a file AFAIK. It involves a few more steps until you get at least past the Security Error. I didn't get any of my ports to boot the actual OS, but at least the recovery works.
krashprocess said:
Hey Kuma, thanks so much for the guide. I'm getting stuck at the LG logo screen (before the boot animation). Obviously adbd is not getting started since I'm pretty sure my boot.tar is somehow wrong. Is it possible to still grab the logcats out of the device? I can still access the recovery (and replace it with different CWM for L9 versions). Thanks in advance.
And it's not just a matter of replacing a file AFAIK. It involves a few more steps until you get at least past the Security Error. I didn't get any of my ports to boot the actual OS, but at least the recovery works.
Click to expand...
Click to collapse
Best of luck to y'all! If we can manage at least a CM 10, that would be awesome! Of course, we may run into bugs but that is the norm on the nightlies.
Sent from my LG-P769 using XDA Premium 4 mobile app
krashprocess said:
Hey Kuma, thanks so much for the guide. I'm getting stuck at the LG logo screen (before the boot animation). Obviously adbd is not getting started since I'm pretty sure my boot.tar is somehow wrong. Is it possible to still grab the logcats out of the device? I can still access the recovery (and replace it with different CWM for L9 versions). Thanks in advance.
And it's not just a matter of replacing a file AFAIK. It involves a few more steps until you get at least past the Security Error. I didn't get any of my ports to boot the actual OS, but at least the recovery works.
Click to expand...
Click to collapse
I thought adb wasn't working but it was. I just kept trying and it started working. It's probably not working because you need to install android platform sooner. I noticed a driver was popping up but Windows didn't know what to do with it. So I manually installed it, not at a computer right now, so I'm not sure what the actually drive its called.
Sent from my LGMS769 using XDA Premium 4 mobile app
kuma82 said:
I thought adb wasn't working but it was. I just kept trying and it started working. It's probably not working because you need to install android platform sooner. I noticed a driver was popping up but Windows didn't know what to do with it. So I manually installed it, not at a computer right now, so I'm not sure what the actually drive its called.
Sent from my LGMS769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll have to check on Windows. I use Debian and OS X to do these things (which doesn't requires drivers), but since I needed Windows to flash the KDZs I have a computer available. I'll see if I can get past the LG screen soon!
BTW I have some builds that don't give Security Error, although they don't boot. If someone wants me to upload them to take a look, I can do it with no problem.
http://forum.xda-developers.com/showthread.php?t=2728404 this rom can work on locked bl?? this rom is based on v20o kernel stock and we make only the boot.tar for work thus rom on locked bl?
inviato dal mio l9 che diventerà g2
Thank i well try
Duckscreen said:
Thank i well try
Click to expand...
Click to collapse
I hope you mean you're going to use this information to look into porting and not flashing this using 2nd init cwm.
Sent from my LG-P769 using XDA Premium 4 mobile app
salvatore46 said:
http://forum.xda-developers.com/showthread.php?t=2728404 this rom can work on locked bl?? this rom is based on v20o kernel stock and we make only the boot.tar for work thus rom on locked bl?
inviato dal mio l9 che diventerà g2
Click to expand...
Click to collapse
This doesn't have stock kernel. It uses a cm kernel....
more help
The instructions on extracting the stock boot.img is important. The .rc files are running commands and are looking for specific files to execute. For example this command is found in the init.rc for V10F (LGMS769)
Code:
service mdnsd /system/bin/mdnsd
class main
user mdnsr
group inet net_raw
socket mdnsd stream 0660 mdnsr inet
disabled
oneshot
Maybe the rom won't boot because it's missing an important command that required by the kernel.
I have noticed that not all service commands actually have a script to run.
For example in init.goldfish.rc
Code:
service qemu-props /system/bin/qemu-props
class core
user root
group root
oneshot
service qemud /system/bin/qemud
socket qemud stream 666
oneshot
/system/bin/qemu-props
and
/system/bin/qemud
are not in the stock system.