Finally with help from people from many other forums Defy with BL7 was rooted.
For now we have no script to make it on the phone without wipe but I'm very happy that it's working.
Rooting Procedure
1. Wipe phone twice (2x make Wipe Data/Cache in stock recovery)
2. Flash 4.5.1-134 DFP-231 CN or 4.5.1-134 DFP-231 Retail.en.EU CEE (It doesn't matter what version of this two You flash but it must be the same with version from point 4).
3. Wipe again (Data/Factory Reset)
4. Flash rooted SBF 4.5.1-134 DFP-231 CN Rooted SBF Part.1, 4.5.1-134 DFP-231 CN Rooted SBF Part.2 or 4.5.1-134 DFP-231 Retail.en.EU CEE Rooted SBF
Thanks List:
- People from http://bbs.mfunz.com for ShellRoot and Rooted SBF
- coelho_ from XDA for help and translation ShellRoot procedure
- Joe31 from XDA for CEE Rooted SBF
- Math43 from XDA for links to CN Rooted SBF
- free2livefrom XDA for testing and helping with patching under linux
- and everyone who tried to help in this thread - THANK YOU
Old Post to let everyone know what we worked here.
Code:
I couldn't find any thread about rooting it and only few posts under roms threads so maybe we can start here. I was making backup of rooted DFP-231 en.EU but after this by mistake I restored 2.3.5 DFP-125 and I needed to reflash my Defy with full sbf of DFP-231 cause to make OTA I had to upgrade to BL7 so any chance to restore my backup is root full sbf DFP-231.
I was trying:
Root Tools:
- (XT800+)ROOT_MOTO_2.3.6
- Defy_2.3.6Root
- DooMLoRD_v4_ROOT-zergRush-busybox-su
- DROID 3 easy root script v7
- ME525 2.3.6 Root
- ROOT_MOTO_2.3.6
- root4defy134
- SuperOneClickv2.3.3-ShortFuse
- ZOC_FlashMasterV1.70
- unlockroot23-eng
- Motofail for Droid 4 and Razr
- SuperOneClick with new Exploit motofail hangs on 5th step
Downgrade to:
Every verion MB525, MB526, ME525, ME525+ starting from early versions of Eclair ending on DFP-2311 but only DFP-188 and DFP-231/DFP-2311 has BL7 and on all other verion phone is dead.
I was trying also modding sbf files by myself and few from Walter79 on DFP-188 thread and trying to force reflash under stock recovery but unfortunately still no luck and every time I had bootloader error or just dead phone.
From last few days I'm monitoring all German, Chinese, Spain and Russian forums about rooting this but still even no clue.
Only thing I learn is that every tool for root has problems with writing su app to phone so I think script to make it is wrong but I'm new in android and I have no idea how to edit it. I tried superuser under Ubuntu 11.04 also but I couldn't mount phone so another fail.
I'm screwed with BL7 so if someone have some ideas I'm opened for most options.
are you try this ...3 link attached from xda http://www.android-hilfe.de/2729429-post10.html
All tries to repack and pack back sbf ending with bootloader error.
and if you flash the su zip http://www.android-hilfe.de/2742491-post20.html
Signature Verification failed. Walter79 posted recovery from 4.5.1-134-DFP-74 for root with stock recovery but bootloader error after flash.
Someone (walter79 I think) was talking of a tweaked sbf that could do the trick. Basically to create this you need to
1) unpack the bl7 sbf to a folder and get cg39.smg.
2) Mount cg39.smg as ext4 in ubuntu (sudo mkdir /mnt && sudo mount cg39.smg /mnt -o loop).
3) Now place su binary(su) in /mnt/xbin and Superuser.apk in /mnt/app (To find these files look inside superonclick zip archive)
5) Set perm (sudo chmod +x /mnt/xbin/su)
6) Unmount (sudo umount /mnt)
7) Repack sbf.
8) Flash your phone with new sbf using Rsdlite
9) See if it's booting, if yes, let us know.
10) If no, reflash orginal sbf again.
Find most tools you need here : http://forum.xda-developers.com/showthread.php?t=966537
Ok, I'll try it and maybe it gonna work but I'm afraid that bootloader error shows after repacking sbf.
Chamelleon said:
Ok, I'll try it and maybe it gonna work but I'm afraid that bootloader error shows after repacking sbf.
Click to expand...
Click to collapse
If this fails with bl error it means that bl7 somehow checks the patency of mmcblk1p31 during boot. If that's the case then rooting these new sbf will be very very very difficult.
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
Edit : use motoandroidepacker 1.3 from http://and-developers.com/sbf
royale1223 said:
If this fails with bl error it means that bl7 somehow checks the patency of mmcblk1p31 during boot. If that's the case then rooting these new sbf will be very very very difficult.
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
Edit : use motoandroidepacker 1.3 from http://and-developers.com/sbf
Click to expand...
Click to collapse
Hi.
Yes it is like this,i tried a things above, the result is boot err.
Tried, mount CG39.smg (no moding) umount than flash, Bootloader err.
I could try 1 more thing, from rooted telephone (bl7) you can pull CG39.smg by ADB.
adb shell:
su
dd if=/dev/block/system of=/sdcard/CG39.smg
Edit this, than flash.
Thanks
Ok, I did what You said and used files from superuser site (bin su ofc) and unfortunately Bootloader error Err:A5,69,35,00,27 and after simple repack and build again without modification CG39.smg phone booting normally.
Joe31 said:
I could try 1 more thing, from rooted telephone (bl7) you can pull CG39.smg by ADB.
adb shell:
su
dd if=/dev/block/system of=/sdcard/CG39.smg
Edit this, than flash.
Thanks
Click to expand...
Click to collapse
Sorry but I don't understand what You just said cause I'm on Ubuntu from yesterday and it's my first contact with this system and to do thing with modding CG39.smg I needed to google how to copy something in Linux console so please explain steb by step what to and I'll try it if You can't.
Chamelleon said:
Sorry but I don't understand what You just said cause I'm on Ubuntu from yesterday and it's my first contact with this system and to do thing with modding CG39.smg I needed to google how to copy something in Linux console so please explain steb by step what to and I'll try it if You can't.
Click to expand...
Click to collapse
you can always go back and get your phone work with flashing this http://115.com/file/e7z2d0jd
it's a bl7
Chamelleon said:
Sorry but I don't understand what You just said cause I'm on Ubuntu from yesterday and it's my first contact with this system and to do thing with modding CG39.smg I needed to google how to copy something in Linux console so please explain steb by step what to and I'll try it if You can't.
Click to expand...
Click to collapse
It is only for people who have rooted phone.
Please who has rooted phone, help. (OTA update)
ADB:
Download sdk:LINK
http://www.change.org/petitions/motorola-mobility-inc-unlock-all-smartphone-bootloaders-2#
coelho_ said:
you can always go back and get your phone work with flashing this http://115.com/file/e7z2d0jd
it's a bl7
Click to expand...
Click to collapse
Not work!
Black screen!!
Ofc it's not working, it's bl6 file and if u flash it on BL7 it's like reflash DFP-231 with any other lower version except DFP-188.
Chamelleon said:
Ok, I did what You said and used files from superuser site (bin su ofc) and unfortunately Bootloader error Err:A5,69,35,00,27 and after simple repack and build again without modification CG39.smg phone booting normally.
Click to expand...
Click to collapse
Just to confirm : Did you use MotoAndroidDepacker 1.3? If it was MAD 1.2x, please repeat the steps with MAD 1.3.
I could see that you used a control to verify if depacker is working properly. That's smart. You could also try this: make a new sbf that only contains the modified cg39.smg. Delete other smg after depackin. Make sure that you use MAD 1.3. Good Luck.
OFC I did all on MAD 1.3 but I think that problem isn't in content of package but modding CG39 cause after rebuilding clean sbf everything working fine and as someone said after only mount and unmount CG39 without modding bios shows error.
Hi, new update for T-Mobile DFP-188 shows up and it's available here but already edited by uploader. I didn't installed it but I downloaded it and tried to modify it by myself. Added su, Superuser.apk and busybox from root4defy134 and added permissions for update script under rest of bin permissions but ofc after trying flash it by stock recovery, recovery shows error at verification. So maybe someone have any idea how to modify it to add root files and update?? Or maybe there isn't any chance to do it??
I want to talk about his attempt to gain root access. I have a PC installed eclipse and android SDK. If you try to copy any file in the System folder at once shows the error (read only filesystem). Today I tried to use the Kindle Fire Utility. Now, almost enable to copy the file to the section of System (ie it is copied by 99% and then gives an error). It seems to me that it might somehow help.
http://random.kennocha.com/kindle/utility/Kindle_Fire_Utility_v0.9.3.zip
Related
I've uploaded a new version (v1.2) of the modified RC30 update.
http://rapidshare.com/files/165227766/update_TC4-RC30_full_xda-dev_v1.2.zip
http://android-dls.com/forum/index.php?f=24&t=189&rb_v=viewtopic(see forum post for link to actual file)
You must have the modified recovery image installed before trying to install this.
Install as per usual - copy to sd card, rename to update.zip, reboot, enter recovery mode and hit alt+s.
(here's a guide on how to install in Italian - thanks Deedend!)
The primary new features in this version are
- adb shell now works in recovery mode
- a real su (instead of the setuid copy of sh in the last version)
- lots of new goodies in /system/xbin and /system/modules
Other things that have changed from v1.1
- This version has a kernel compiled by Saurik, with more core stuff "turned on", to support more modules (Specifically, /dev/mem and /dev/kmem are available now)
- new features in init
- support for mounting to loop devices
- move flag for mount
- mknod that can wait for a device
- chdir, chroot, usleep, include, trigger​- Changed the init.rc so that it will include /system/init.rc and /data/init.rc, so you can easily add new startup stuff, without having to rebuild/reflash boot.img
- Changed the boot-up recovery flash to look for a file at /data/recovery.img instead of /system/recovery.img, and also to delete recovery.img after a successful flash
- changed the "mount" symlink to be busybox's mount instead of toolbox's mount
- added an /etc/fstab file that busybox's mount can use, that lists the standard system partitions.
- changed the fingerprint back to the official RC30 fingerprint (don't want to let google know you're using a modified build)
- using a newer version of busybox
- moved busybox from /system/bin to /system/xbin
Note: A big thanks to Saurik (the "debian on Android" guy ) for all the changes to init and the kernel, as well as the modules in /system/modules. He also tweaked and recompiled a newer version of busybox. He recently posted his own update that I shamelessly stole this stuff from (with his permission )
It also includes the changes that were made in v1.0 and v1.1. namely
- set ro.secure=0, ro.debugable=1, and persist.service.adb.enable=1 in /default.prop, to enable adb to run as root
- Added the ability to mount to a loop in init
- Mount /system/xbin/xbin.cramfs into /system/xbin in init.rc
- Looks for a recovery image to flash at /data/recovery.img instead of /system/recovery.img, and deletes the recovery image after a successful flash
- added back in the telnetd command from RC29
-----
For those who have installed the stock RC30 update: no, you cannot install this update. You must have a modified recovery image installed to apply the update, and you have to have root access to install a modified recovery image. You can't get root access in stock RC30, so you can't install a modified recovery image, and so you can't install this update.
-----
im gonna try this on my stock rc28... let u know tha good tha bad n tha ugly
JesusFreke said:
.... You should be able to apply it no matter what RC you are on.....
Click to expand...
Click to collapse
My G1 is at RC30, would I be able to update it via SD card again to gain the root access?
-Pramod
pramods said:
My G1 is at RC30, would I be able to update it via SD card again to gain the root access?
-Pramod
Click to expand...
Click to collapse
No. If you're running stock RC30, and don't have my recovery image installed, you're out of luck, until another root exploit is found.
Does this include all the regular upgrades that the rc30 was going to bring like the battery fix ? And So i dont mess up how do i install the modified recovery image correctly ?
What mod we have to install it? since is not signed with google key it will not load on 29 at all.
usmc2k said:
Does this include all the regular upgrades that the rc30 was going to bring like the battery fix ?
Click to expand...
Click to collapse
Yes. It is identical to the stock RC30, except for the specific modifications I mentioned.
tritron777 said:
What mod we have to install it? since is not signed with google key it will not load on 29 at all.
Click to expand...
Click to collapse
You have to have the modified recovery tool on your phone, which has the test keys.
Thank YOU SO MUCH! i was afraid i wasn't going to see you. i try ed someone else's(mod) and I stuck in your recovery because i tryed to format partion md3(system) and restore it with the backup(for some reason i was stuck between RC29-30) the phone froze but i tell you your recovery is the S*** it Saved my A** Where's your donation account?(4real)
Do I still have to install the modified recovery image or is it included in ur version ?
usmc2k said:
Do I still have to install the modified recovery image or is it included in ur version ?
Click to expand...
Click to collapse
You have to have the modified recovery image already installed in order to install my modified update. And it will still be installed after you do the update.
JesusFreke said:
You have to have the modified recovery image already installed in order to install my modified update. And it will still be installed after you do the update.
Click to expand...
Click to collapse
So all i do is get the zip from ur post change it to a update... install it then change ur rc30 to update install it and im good to go ????
Thanks so much! It worked perfectly
humble said:
Thank YOU SO MUCH! i was afraid i wasn't going to see you. i try ed someone else's(mod) and I stuck in your recovery because i tryed to format partion md3(system) and restore it with the backup(for some reason i was stuck between RC29-30) the phone froze but i tell you your recovery is the S*** it Saved my A** Where's your donation account?(4real)
Click to expand...
Click to collapse
Glad I could be of service . If you want to donate, I would be happily surprised, and much appreciative.
usmc2k said:
So all i do is get the zip from ur post change it to a update... install it then change ur rc30 to update install it and im good to go ????
Click to expand...
Click to collapse
Yep . Assuming you have the modified recovery image installed already. If you don't, it will just say something to the effect that it couldn't validate the signature.
JesusFreke said:
Glad I could be of service . If you want to donate, I would by happily surprised, and much appreciative.
Click to expand...
Click to collapse
enjoy my friend, and your welcome
looks like telnetd command didn't survive
jriley60 said:
looks like telnetd command didn't survive
Click to expand...
Click to collapse
Why do you say that?
Code:
# ls /system/bin/t*
ls /system/bin/t*
/system/bin/telnetd
/system/bin/toolbox
/system/bin/top
weird i can't terminal in from the phone anymore.
jriley60 said:
weird i can't terminal in from the phone anymore.
Click to expand...
Click to collapse
You can't run telnetd just by typing it in on the keyboard anymore. You have to open a terminal (terminal emulator, pterminal, or with adb shell), and get root access if needed (su), and then type "telnetd &" (the & at the end tells it to run in the background)
this was a work-in-progress development project for porting CyanogenMod 9 (ICS/4.0.4) and ClockworkMod Recovery 5 to Allwinner A10 devices.
but my CM9 is obsolete now. if you want to get CM9, please refer other active projects.
currently here is only for my miscellaneous work for Allwinner A10 devices. if you have a question about development work for A10, you may post it on here. but I can't guarantee any answer.
* links to other active CM9/CM10 projects
http://forum.xda-developers.com/showthread.php?t=1821398 CM10 for many A10 tablets by Christian Troy
http://forum.xda-developers.com/showthread.php?t=1760929 CM9 for many A10 tablets by Christian Troy
http://www.slatedroid.com/topic/33820-ics-404-ivi-cm9-firmware-for-novo7-advanced-btgpsusb-audio/ for NOVO7 Advanced(1) by tsynik
* links to other active AOKP projects
http://forum.xda-developers.com/showthread.php?t=1760931 for many A10 tablets by Christian Troy
* How to install ClockworkMod Recovery 5
1. (if you don't have official ROM and flash tool,) make backup of recovery partition
2. download recovery.zip and unzip it
3. put install-recovery.sh and recovery.img(recovery.cpio for GB ROM) on /sdcard/ *1 *2
4. run install-recovery.sh from root shell or any apps which can run a script (terminal, gscript, etc)
e.g.
Code:
> adb shell
$ su
# sh /sdcard/install-recovery.sh
* How to boot recovery
1. put reboot-recovery.sh on /sdcard/ *1 *2
2. run reboot-recovery.sh from root shell or any apps which can run a script (terminal, gscript, etc)
e.g.
Code:
> adb shell
$ su
# sh /sdcard/reboot-recovery.sh
*1 if you are using CM9, install-recovery.sh and reboot-recovery.sh are already installed on /system/bin/. if you are not using CM9, you can put these scripts on your ROM.
*2 /sdcard/ is referred as "SD card" on Android, but it may not be physical/external "SD Card". please make sure files are placed on /sdcard/.
* How to boot recovery (alternative)
for ainol NOVO7 AdvancedII/Aurora/Elf
BACK + POWER
for other tablets, please find the way to boot recovery.
* How to control ClockworkMod Recovery 5
for ainol NOVO7 Advanced
VOL-: down, VOL+: up, POWER/MENU: select, BACK: back
for ainol NOVO7 AdvancedII/Aurora/Elf
VOL-/MENU: down, VOL+/HOME: up, POWER: select, BACK: back
* How to install CyanogenMod 9
1. download update.zip and put it on internal NAND flash or SD card (don't unzip it)
2. install ClockworkMod Recovery 5
3. reboot recovery
4. install update.zip
5. wipe data/factory reset *3
6. reboot
*3 only if you are upgrading from non-CM9 ROM (CM9 1st install)
reserved
reserved
Hi,
I was not shure if I should by the NOVO7 Advanced, but now as I see that there is (or will be) CM avaidable for it , I will buy it.
Thanks for porting
T
saulmrt said:
I was not shure if I should by the NOVO7 Advanced, but now as I see that there is (or will be) CM avaidable for it , I will buy it.
Thanks for porting
Click to expand...
Click to collapse
thank you for your message.
but I don't recommend to buy it because of my CM, unless you like/want to do porting work. my CM is not perfect at all.
I ordered it because I thin it is a good piece of hardware, you don't have to be afraid that it was only because of this port.
Well as soon as I have this tablet I will try to help with porting as good as I can.
Great work so far OP!
I have the Ainol Advanced waiting for me at the post office. There's already a healthy community over on slatedroid but it's always good to see CM getting ported!
thank you for your comments.
I wish I'll re-upload my files in this weekend...(it's not technical reason at all)
FILES! FILES!! My Kingdom for FILES!!!
i have been longing for it and i suggest to launch a new board for it. it's been a popular device in PRC, taiwan & hong kong already! please note that the 2.0.3 & 2.0.4 firmwares are quite buggy, and i would advise all to flash 1.8 modified version which is stable and can score 18XX at quadrant.
I've been trying to do this for my A10-based tablet too. Can you up the download links again? Maybe I can improve some things.
Edit: I'll upload a dump of the stock ROM soon. I also found a tool to (partially) extract the LiveSuite *.img files.
Edit 2: WiFi chipset of the tablet is a Realtek 8192CU, Freescale MMA7660 accelerometer & Goodix touchscreen.
FezzFest said:
I've been trying to do this for my A10-based tablet too. Can you up the download links again? Maybe I can improve some things.
Edit: I'll upload a dump of the stock ROM soon. I also found a tool to (partially) extract the LiveSuite *.img files.
Edit 2: WiFi chipset of the tablet is a Realtek 8192CU, Freescale MMA7660 accelerometer & Goodix touchscreen.
Click to expand...
Click to collapse
sorry, I need some time to prepare my site. it seems I don't have enough time on this weekend but I hope I'll get some time on next week.
I guess you are talking about this tool: http://www.mp4nation.net/forum/viewtopic.php?f=24&t=20476
I'll try it when I get enough time
and thank you for your information. if you want to add your tablet to my support list, I need more detail info (please see post#4). if you can do it yourself, please just wait for some day... I'll uploaded my git repo too.
(nothing is secret, just I need my free time!)
I found it on a different website, but I think it's the same tool.
This is a dump I made of the original partitions with dd:
boot.img: http://dl.dropbox.com/u/28680222/XDA/tablet/boot.img
misc.img: http://dl.dropbox.com/u/28680222/XDA/tablet/misc.img
rootfs.img: http://dl.dropbox.com/u/28680222/XDA/tablet/rootfs.img
recovery.img: http://dl.dropbox.com/u/28680222/XDA/tablet/recovery.img
system.img: http://dl.dropbox.com/u/28680222/XDA/tablet/system.img
I haven't included cache, data and internal sdcard because I don't think they are of any use for ROM development.
Edit: attached required output from commands in post #4. Find /sys doesn't work because adb can't find find
Hi fun thanks for the pm found my way here at last
i have not managed to get into stock recovery on the Excel so far so i have not made any kind of file dump or backup i will see how it goes and keep my eye on this thread i have root and terminal emulator i have installed superuser as an app from market
can i type a command to get into stock recovery or would you think there is no stock recovery
cheers
Recovery is also a mistery to me. I tried 'adb reboot recovery' but I guess that was too simple. There is a recovery partition (I created an image with dd above) but haven't found a way to boot into it. I'd love to know how the topic starter got clockworkmod working
Mitred said:
i have not managed to get into stock recovery on the Excel so far so i have not made any kind of file dump or backup i will see how it goes and keep my eye on this thread i have root and terminal emulator i have installed superuser as an app from market
can i type a command to get into stock recovery or would you think there is no stock recovery
Click to expand...
Click to collapse
hi.
stock recovery should work because it's necessary to run "factory reset" from setting menu on stock rom. (it's done automatically so we can't use it to enter recovery mode. I just explained about functionality)
and recovery is not necessary for now. what I need is not complete dump image. I just want to know hardware related things so tar archive is enough.
permanent root is not necessary too. sometimes rooting app makes brick, so I don't recommend it. I don't recommend to modify stock rom unless you have official rom and flash tool.
if adb shell is root shell, then rooting is not necessary at all. if adb shell is not running, or non-root user shell, temporary root is necessary to get root shell.
then, you already got root shell, right?
then, please check following commands are available in your rom, "tar" and/or "busybox".
FezzFest said:
Recovery is also a mistery to me. I tried 'adb reboot recovery' but I guess that was too simple. There is a recovery partition (I created an image with dd above) but haven't found a way to boot into it. I'd love to know how the topic starter got clockworkmod working
Click to expand...
Click to collapse
"adb recovery" doesn't work. I'll post how to enter recovery. please wait for a moment.
anyway, please tell me name of your tablet, or link to web, or photo.
if busybox is in your rom, "busybox find /sys" will work.
It's a Bmorn V11. The 'busybox find /sys' command indeed works, I have attached the output files to the zip file in this post.
FezzFest said:
It's a Bmorn V11. The 'busybox find /sys' command indeed works, I have attached the output files to the zip file in this post.
Click to expand...
Click to collapse
i'm guessing you are referring to the Bmorn V11 rebranded for Promedia ?
If so, keep in mind that there are 2 versions of this tablet, one with 3600 battery and one with 3200 battery, the 3200 version has the goodix_touch drivers.
Q. Why there is a need to repack the firmware?
A. As you may know, the stock kernel in the stock firmware has the emmc hard brick feature enabled which is believed to be the reason of 2 hard brick incident reported in the forum. And even worse, the emmc hard brick bug (mmc_erase) can be called @ anytime after the system is booted with a buggy kernel, which means that your device can immediately get bricked after the first reboot.
Q. So is it okay to flash the ROM via odin with a different bootloader (i.e. boot.img)?
A. Theoretically, yes. But the problem is that when we repack the odin package with a modified boot.img. The download counter will rise and a yellow triangle will appear on every boot.
Q. So is there any way to flash the stock bootloader but without letting it get booted?
A. Yes. There is a way to do so. After you have successfully flashed a package via odin, the odin bootloader (based on BCT partition) will invoke the recovery bootloader to finish the install process. And if you are not using the stock recovery, the process will get halted and then leave you at the recovery (CWM) screen. And then you can flash a kernel via CWM at this point.
Q. Is there anything that I should aware of?
A. Yes. Just like flashing any firmware, After flashing the ICS package, it is important for you to backup all the important files before flashing.
Guideline 1 [For people who is willing to use CWM6 (provided by Adam77Root)] (prefered way) :
1. Turn on your device and connect it to a computer
2. Place the kernel file, superuser file (which can be flashed via CWM) and new_sec_csc.zip into your internal SD card first and make sure all your important data on /sdcard are backed up (You are free to select any kernel but make sure the mmc erase part get disabled from the kernel completely)
3. Turn it off and remove the external sdcard from the device
4. Download the ICS firmware files which contains GB kernel and CWM6
5. Put the device into download mode and flash the above package via odin 3.07. Place the package file (*.tar.md5) into PDA part (You can now flash with pit file as well, however the internal sdcard data will get wiped so it is important for you to make a backup for important files before flashing) (DO NOT attemp to flash any ICS package via odin 1.85 as there is a high risk that the download process get stuck in odin v1.x series, and you have to unbrick your device with nvflash tool if error occurs)
6. After the device is restarted, it will get into recovery (CWM) mode. And the script provided by Samsung will be failed to execute due to a assert call. (Don't worry, you can execute the script again by using the patched new_sec_csc.zip)
7. Backup any important data in /sdcard (external sdcard) now if you didn't do so. You can do this @ 'Mount and storage' -> 'Mount USB devices'.
8. 'Wipe cache' and 'Wipe data / factory reset' (make sure you have all your important data on /sdcard backed up and your have removed your external sdcard device)
9. If the above stage has wiped your CWM flashable zip file as well, you can mount the device to a computer via mount menu and you can place the zip file to the phone as mass storage again.
10. Install the CWM flashable zip file (superuser, new_sec_csc.zip and your kernel file) from sdcard (For an unknown odd reason, all the packages you gonna install in this step will have signature verification error, but it is safe to proceed. Just switch off the signature verification from the menu or choose to 'Install untrusted package'.)
11. After you flashed kernel, you are free to flash anything and free to reboot now.
12. If you have used a pit file for flashing the package in odin, a message will be appeared in notification center telling you the filesystem on /sdcard cannot be recognized. Just click on it to format the sdcard and then you are free to use anything now.
13. If you are still afraid of breaking system integrity as you were not using the samsung recovery script to finish the update process, navigate to 'Options -> Back up and reset -> Factory data reset' and totally reset the device there.
P.S. If you accidentally pressed reboot the system now in CWM 6, don't worry, the system will not be able to boot into normal mode. And you can redo all the things since the beginning.
Update #1 : During testing the flash process, I have found that the repacked firmware cannot be flashed with odin 1.83. It is important to get all the ICS firmware being flashed with odin 3.07 (or 3.x sereis) instead v1.x series. Otherwise you have made a risk that your partition (PIT) table is messed up so srsly that you have to use nvflash tool to restore everything. I will tell this to cooleagle to get everyone knows of it.
XXLQ9 :
Stock package with GB kernel and CWM6 which is based on safe stock GB ZSLE6 kernel (just extract the file in the splited zip files) : http://www.mediafire.com/?uq5tg9o7nli04b2 and http://www.mediafire.com/?b5i571br0x07c38
CWM flashable package :
- Superuser CWM flashable package : http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.2-RC3-arm-signed.zip or Superuser-3.2-RC3-arm-signed.zip in attachments (But you will be unable to update with the 3.2 RC3 build, use 3.1.3 one if you want)
- My own kernel (flashable via CWM) : UnknownzD_Kernel_with_superuser.zip (with superuser, good for first time install) and UnknownzD_Kernel.zip in the attachments
- Patched Samsung install script (the one which failed to run) : new_sec_csc.zip in the attachments
Odin v3.07 : Odin307.zip in the attachments
Credits go to Adam77Root for his CWM image and someone(!?) who has uploaded odin 3.07 to xda forum. Will try to check his name later.
Short change log about my kernel (The longer one will get posted when I start another thread for it) :
4 IO scheduler added
Voodoo sound patch added
Full fp calculation based on hardware fp opcode only (which should makes the device consumes less energy while providing the same performance level)
MMC erase function tootally disabled
Default.prop get modified to increase the performance
Based on ICS 3.x kernel src code released by Samsung
If you gonna use my kernel, please make sure that you have efs_backup.img backed up safely after flashing my kernel package, as it contains your device's IEMI info, which can save you from future disaster as you can use the unbrick tool with it. You can backup the efs_backup.img by :
1. Flash my kernel in CWM
2. Mount and storage -> Mount USB devices
3. Copy the efs_backup.img from the sdcard to your own computer (it is vital for you as you can use the unbrick tool later)
Now I am stuck @ finding a proper file host to upload the files.
waiting for this!
Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2
Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.
coldbeermt said:
Rooted?
BusyBox?
Init.d?
Sent from an GT-I9103 with ICS and Tapatalk 2
Click to expand...
Click to collapse
You can root it on your own with superuser zip file. And busybox binary is not yet dropped into /sbin/ as I believe it comprise the system integrity back in GB kernel. Init.d will be supported in near feature. All the things that I changed is just inside the kernel and recovery and provide a safe envrionment for user to continue to flash their own desired kernel. Nothing more.
For kernel development, I will make a separate thread in dev section later.
Sorry I have to postpone the release as I have to repack everything with the nordic release (XXLQ9) now.
Ok, I'm sure you know I asked just for general information. I supposed your answer yet
Anyway, I'm sure its a good job. With the new version (nordic) I suggest you to upload releases to dropbox our something easier. Anybody could make a mirror in other servers later :thumbup:
Sent from an GT-I9103 with ICS and Tapatalk 2
UnknownzD said:
Sorry as mediafire.com only allows upload 200MB per file, I need to take some time to split the files into multiple zip, please wait for about 15 minutes.
Click to expand...
Click to collapse
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.
xlm13x said:
Man we r RC, we get premium hosting space from DevHost.
Check ur PM
Sent from my Galaxy Royale using Tapatalk 2.
Click to expand...
Click to collapse
Yea I just saw the PM, it is really useful for me tbh. Thanks for your help.
Okay after many hours of testing, I am happy to release the ICS XXLQ9 package with GB kernel and CWM 6 (based on the one posted by Adam77Root) that should be able to let you flash your own kernel after flashing it. Download links will be up shortly.
So after 5~6 times of srs bricking, I finally get it working correctly after working overnight.
Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.
UnknownzD said:
Ok I have released the ROM already, please try to use it if you know how to use the unbrick tool. This is because I want to ensure that the package can be flashed safely in Odin v3.x instead of v1.x series.
Click to expand...
Click to collapse
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??
vipul12389mehta said:
well as a bit newbie i am confused with all tuts floating on XDA
what i intend to is
1. flash Stock ROM via ODIN 1.8
2. flash CWM 5.x via ODIN 1.8
3. Flash ardatdat kernel via CWM
4. Now only i will wipe data thru CWM...
is this ok ?? i am concerned with Austrian firmware currently..rooting is not possible in nordic ROM due to system partition space...
can this be dangerous ??
Click to expand...
Click to collapse
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.
Nice work! Thanks!
Sent from my GT-I9103
nedooo said:
Rooting Nordic ROM is quite easy, that is if you are on GB (if you are on ICS you will have zero free space in system space), so when you are on GB you need CWM http://forum.xda-developers.com/showthread.php?t=1839900 use CWM to wipe data and format system.
Flash Nordic ROM (Odin), than CWM, go to http://androidsu.com/superuser/ and download binary only (ARM), now use CWM to install SU binary.
You need SU app from Play Store and you are rooted.
Click to expand...
Click to collapse
Basically the things you mentioned above are included in the package / guide already. Tbh this should not be dangerous. But I want more people to test it first because last time when I released the GB kernel, a lot of people complained about the things that do not occur on my phone.
oh btw about the zero free space in system space, I believe it is just a bug in the filesystem. You can fix it easily by using e2fsck, which is actually included in my kernel script.
This is just explanation about staying stock. Your work and effort is well above this. Thanks in name of all flash addicts
So after many times of tests, I guess it is safe to use the build already, just make sure you have everything backed up before updating (actually you should do this for any fimrnware update). If you have found any problem, just report the problem here. I will repack every stock firmware following the same method until Samsung acknowledge that the MMC_CAP_ERASE is removed from stock kernel.
If you have found your device bricked after using any ICS update (for example, unable to flash the device any more via odin protocol), please let me know via pm please so that I can guide you to fix your phone in IRC.
pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
Click to expand...
Click to collapse
When you are updating the ROM from GB to ICS better to wipe data or else you face some Force Closes and other issues....
pudup said:
What happens if I don't use data wipe and factory reset? I didn't so it for the CWM installation while upgrading from GB. Is it really necessary?
"I like spelling my name backwards"
Click to expand...
Click to collapse
The wiping cache part is actually a part of odin download process. Everytime when you flash a new firmware in odin, the odin bootloader will invoke some scripts stored in /cache within recovery mode, and then wipe out these scripts / the whole partition as they are no longer needed.
However the wiping /data part is actually an essential part of firmware update and you should do it on your own if you are using CWM based firmware. This is because if you flash a firmware via odin, the data partition gets wiped after the device rebooted.
tbh it should be safe if you didn't wipe the /cache partition but not for the /data partition. Just some usls scripts and T9DB left behind in /cache. But incompatible binaries may still stays in /data if you didn't wipe it.
Sent from my GT-I9103 using xda app-developers app
Hello guys!
I make my own ROOT (systemless, thanks for Chainfire) images for Moto X Style with Marshmallow (build MPH24.49-18). Its use "experimental" systemless SuperSU version 2.56 - more info on http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2. No need replace bootloader or recovery. Still need unlocked booloader.
Because TWRP didn't work in this version of bootloader (0xA048), I cooked "su.img" in a Linux box and used "/data/local/tmp" as bridge (accessible by ADB).
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it!
For use, you need
1) unlocked bootloader.
2) if your bootloader not unlocked, make sure you have copy of your data, because this process will erase your device.
3) install ADB and FASTBOOT on your pc using minimal ADB or Android SDK.
4) install ADB drivers from Motorola or Universal ADB.
5) download provided files.
6) download SuperSU ver. 2.56 from http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
Steps:
1) extract files in a folder of your choice (su.img, boot.img).
2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder.
3) enable USB debugging on Android.
4) connect your device on pc.
5) open a command prompt in a new folder.
6) type "adb push su.img /data/local/tmp" without quotes.
7) type "adb install Superuser.apk" without quotes.
8) now reboot your device into fastboot mode by typing "adb reboot bootloader".
9) type "fastboot flash boot boot.img" without quotes.
10) type "fastboot reboot" without quotes.
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
Ivan
Do I still need to unlock the bootloader in order to root this device
ivcarlos said:
2) write "boot.img" with fastboot.
Click to expand...
Click to collapse
What do you mean? Como assim?
Oh I see thanx partner
How can I copy "su.img"?
If no Root I can not copy into data/local/tmp.
Marccelllorzn said:
How can I copy "su.img"?
If no Root I can not copy into data/local/tmp.
Click to expand...
Click to collapse
Restart in bootloader
1) adb push su.img /data/local/tmp
2) fastboot flash boot boot.img
3) Install SuperSu ver 2.56 apk
would this work on xt1575 us? if not why?..... i mean .. why the indian MM would work 4 any variation and this one would not?
zittorb said:
would this work on xt1575 us? if not why?..... i mean .. why the indian MM would work 4 any variation and this one would not?
Click to expand...
Click to collapse
Yes, work with XT1575.
I dont test on another device, only on XT1572.
After 24h, no errors, work like a charm.
With this approuch you dont need to downgrade bootloader.
assuming that we need a "CLEAN", unrooted system for this as advised by @Chainfire in his instructional post regarding this experimental root method!
Instructions
You must absolutely re-flash your stock /system partition, or the separate root instances will interfere with each other. The installer for this experiment will not clean up old root files.
- Flash stock /system
- Flash the attached boot image
- Flash the attached SuperSU ZIP in TWRP
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
Also you should probably make a point of mentioning that this method is an experiment.
Aside from this, let me take my "high-visibility" jacket off, along with my "safety helmet" and say thank you very much for taking the time to do this for us all @ivcarlos! You are a gentleman!
Is Android pay confirmed working with this root method?
Sent from my XT1575 using Tapatalk
@bb12489
I dnt know because I dnt use this feature.
@Doktaphex
I dnt mentioned this - clean and unrooted system - because after apply OTA on XT1572, custom recovery (TWRP) didn't work anymore. By the way, I assume no root and clean system.
I know this method is "experimental", but it's best at this time, without downgrade bootloader (not safe).
Thanks for comments! I make this work because I need root and I dnt like to make heavy changes on smart...
In this way, I share for everyone.
ivcarlos said:
@bb12489
I dnt know because I dnt use this feature.
@Doktaphex
I dnt mentioned this - clean and unrooted system - because after apply OTA on XT1572, custom recovery (TWRP) didn't work anymore. By the way, I assume no root and clean system.
I know this method is "experimental", but it's best at this time, without downgrade bootloader (not safe).
Thanks for comments! I make this work because I need root and I dnt like to make heavy changes on smart...
In this way, I share for everyone.
Click to expand...
Click to collapse
Could you please give me the link that how you created modified boot.img ? I want to make it work on Indian XT1572
@gulshanstrider
I make boot image based on post of Chainfire (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344), with applying steps:
1) unpack stock "boot.img";
2) patch sepolicy;
3) edit "init.rc" and "init.environ.rc";
4) edit "file_contexts";
5) repack "boot.img".
Use Chainfire generated images with model.
Without TWRP, I cooked "su.img" in a Linux box, and use "/data/local/tmp" with bridge.
ivcarlos said:
@gulshanstrider
I make boot image based on post of Chainfire (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344), with applying steps:
1) unpack stock "boot.img";
2) patch sepolicy;
3) edit "init.rc" and "init.environ.rc";
4) edit "file_contexts";
5) repack "boot.img".
Use Chainfire generated images with model.
Without TWRP, I cooked "su.img" in a Linux box, and use "/data/local/tmp" with bridge.
Click to expand...
Click to collapse
wifi not working now please tell me how to revert everything back pleaseeee help !!!!
Shishir Singhal said:
wifi not working now please tell me how to revert everything back pleaseeee help !!!!
Click to expand...
Click to collapse
Your model is XT1575 or XT1572?
Shishir Singhal said:
wifi not working now please tell me how to revert everything back pleaseeee help !!!!
Click to expand...
Click to collapse
@Shishir Singhal
Whats your model and version?
I make this image for my XT1572 (BR, dual) and wifi working.
To revert back you must write back stock boot.img version. On first post I provided stock of XT1572 RETLA 6.0 (my base).
On my device no issues at all.
Not working on my XT1572
Didn't work on my XT1572 with Android 6.0.
Enable root option is disabled in SuperSU with a message saying that system-less root is currently not supported.
ivcarlos said:
@Shishir Singhal
Whats your model and version?
I make this image for my XT1572 (BR, dual) and wifi working.
To revert back you must write back stock boot.img version. On first post I provided stock of XT1572 RETLA 6.0 (my base).
On my device no issues at all.
Click to expand...
Click to collapse
Thank u for quick reply got it working by flashing NON-HLOS.bin now everything is working fine thank u soo much
roberto.marcal said:
Didn't work on my XT1572 with Android 6.0.
Enable root option is disabled in SuperSU with a message saying that system-less root is currently not supported.
Click to expand...
Click to collapse
What version of SuperSU you was installed?
You put "su.img" into "/data/local/tmp"?
If you enter in shell with ADB, ls command show "su" directory in root? Image was monted successfully?
*****Keep in mind that I or XDA or anyone else is not responsible for what happens to your device make sure you have a nandroid backup before proceeding
This is based on my personal experience I'm not a Dev
How to enable systemless root on mediatek !!!!
Step 1:
Get the booting of your phone via readback using spflashtool or dumping the ROM IMG !!
Step 2:
Unpack the boot IMG using mkbootimg or carliv IMG kitchen or Android kitchen !!!
Step 3:
Open the ramdisk folder and open the init.rc using notepad++
Step 4
Goto the line
Code:
export PATH /sbin:/system/bin:/system/xbin:/vendor/bin
**The line may vary but it will look similar !!!
Add the path of your su file at the end
Like I was t to install it at my data partition so
Add
Code:
:/data/bin
At the end of the line and save !!
Then change the permissions of /data/bin to 644 else apps won't be able to read the path due to insuffient permission !!!
Then repack the boot.img
Flash the bootimg via sp flash tool of flashify or any other method
Step 6:
***note use the su binaries of your CPU only
Like I used arm 7 binaries for my device !!
To know your CPU type
Download terminal emulator or use adb shell and type cat /proc/cpuinfo
Now using adb push copy the su file to the /data/bin folder or make a flashable zip to do the same !!
If you can't push via adb try doing it in adb supported recovery !!!
You might need to create the bin folder manually
And don't forget to set the permission to 0755 and reboot !!
Plz let me know if it works !!!
And also let me know if it doesn't !!!!
I can't post the flashable zip because I'm still new !!!
Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?
AlexZap said:
Can you post some more info for this? What mtk chipset is it tested with? What android version? When you repack the kernel image, do you use android headers or mediatek headers?
Click to expand...
Click to collapse
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....
kirito9 said:
Carliv Image Kitchen will repack the same way it was unpacked so you do not have to worry.
I also want more info for this because I'm not even finding the first link export .....
Click to expand...
Click to collapse
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header
AlexZap said:
the point is that the systemless installer is supposed to unpack and repack the kernel... and i dont know/dont think it can handle a mediatek header
Click to expand...
Click to collapse
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.
kirito9 said:
Ohh, it could be that it doesn't support Mediatek because I tried a systemless SuperSU and it didn't boot the MT6580 device. I had to flash the boot.img to fix.
Click to expand...
Click to collapse
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?
kirito9 said:
There isn't? Strange, then why when I flashed the SuperSU systemless zip from here it didn't boot but when flashed the SuperSU from here it did but said in SuperSU app, couldn't find the su binary.
Maybe I should push "su" to xbin folder or bin? What are your thoughts?
Click to expand...
Click to collapse
I think you need to read some more on how and why systemless root works and what it is for.
Regular root, the summer you installed, puts a bunch of binaries in the /system partition on your android phone, and while giving you root, it breaks a lot of things because it modifies the stock image, something that android doesn't expect to ever change except for system upgrades.
Systemless root fixes this. It does nothing to the system partition. It creates a mountable image and stores it in the /data partition that contains the su binary and whatever else is needed for root. It then modifies the boot image (the ramdisk that is packed with the kernel) so that on boot, it mounts this su image inside the already mounted system partition. This keeps the system partition stock, but at the same time, gives you root. Things like safetynet are unbroken and you can run things like android pay that check for a modified system image.
In order to do its magic, the systemless root installer has to be able to unpack and repack the boot partition. If you have a mediatek phone, you have about an 80% chance that your boot image is different then the rest of the android world. Mediatek phones have their own header in their images like boot and recovery (except for some very new devices). I am 95% certain that the systemless root installer does not know anything about mediatek headers. So it may unpack something, but clobber the boot image on repack. The author of this thread purports to have it working. I ask how. Is he one of the 20 or so percent without a mediatek header? Or did he do something else
AlexZap said:
.................
Click to expand...
Click to collapse
Yeah lol, first time working with android 6.0 and this systemless root. I know that's what the systemless root does, that's why after flashing the MT6580 device that I have, it didn't boot. Don't think the systemless supports this MT6580 as it uses it's own MTK header and not the standard AOSP.
Seems like OP as disappeared from this thread.
Sorry I took so long to respond
AlexZap said:
There is no reason systemless root shouldn't work on mediatek phones other then the different kernel headers. The OP says he got it working, which is why I posted my questions to him... but he has failed to respond.
Click to expand...
Click to collapse
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!
uttarayan21 said:
And yes I got the systemless root working on my Panasonic T41 running CM 12
The SuperSU installer doesn't work on mediatek 'coz in cannot unpack the boot.img with mtk headers so i did it manually but SuperSU tried to fix the placement of the binaries !!
So i used another superuser !!
Click to expand...
Click to collapse
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Sent from my KFTHWI using XDA Premium 4 mobile app
AlexZap said:
I have found that magisk works flawlessly on my Jiayu s3... it uses hybrid headers in the images... but magical does the unpack/repack just fine.
Click to expand...
Click to collapse
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:
uttarayan21 said:
Well but in my case when i tried it on CM 12.1 mtk6582
The phone got bricked !!
The SuperSU installer couldn't even get the boot image from my phone !! :crying: so i tried to modify the installer script with other tools but it was waaaay too complex for me so tried to do this instead with another superuser and it worked !!
I also had to modify the init.rc to start the daemonsu service !!! :good:
Click to expand...
Click to collapse
I think magisk is better at handling boot image formats.
AlexZap said:
I think magisk is better at handling boot image formats.
Click to expand...
Click to collapse
I agree with @AlexZap and i am using it and it is working perfectly
Sent from my Z14 using Tapatalk
Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")
MalikDrako said:
Does this work for the newer chipsets? I tried on Android 6.0 / MT6750, but I dont see the path export anywhere in the boot image (grep -nrw 'boot.img-ramdisk' -e "PATH")
Click to expand...
Click to collapse
magisk works flawlessly. no need to muck around, just flash it from twrp
Sent from my KFGIWI using XDA Premium 4 mobile app
AlexZap said:
magisk works flawlessly. no need to muck around, just flash it from twrp
Click to expand...
Click to collapse
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right
MalikDrako said:
I've been having trouble getting TWRP to run on this phone (black screen for a few seconds then it reboots into android), although I just discovered an unmodified repacked boot image wont boot, so either the phone is doing some verification that is failing or the tool I used cant repack it right
Click to expand...
Click to collapse
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.
AlexZap said:
any chance the boot loader is locked? usually flashing a bad image will brick your phone if the boot loader is locked, but you never know.
have you tried unpacking the boot image with carliv's image kitchen? it throws out a bunch of info on how the image is made. as long as it is repacked the same way (Carliv's tool does this automatically), it should work fine. unless whoever your phone manufacturer is somehow included another signature check... which is really really out of the ordinary.
Click to expand...
Click to collapse
I just tried Carliv's image kitchen, and both boot and twrp port worked first try
How to change Permissions?
i could not understand it
can u help me Please?