TWRP Flashable BootSplash ZIP and CMD/Terminal Option - Samsung Galaxy S10 Themes, Apps, and Mods

Just a simple TWRP Flashable BootSplash Zip for example to replace the warnings when you unlocked/rooted your device.
It will open up_param.bin and repack it with the jpg,s inside the zip.
Simply replace svb_orange.jpg , logo.jpg and booting_warning.jpg with a jpg of your own choice.
Make sure the images don't exceed 500kb, and keep exact same resolution (1440x3040 24bbp)
{
"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 ***
Script:
Code:
#!/sbin/sh
OUTFD=$2
ZIP=$3
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
cd /tmp
rm -rf arter97
mkdir arter97
cd arter97
unzip -o "$ZIP"
ui_print " - mounting data partition"
mount /data
if [ ! -e /data/media/0/up_param.bak ]; then
ui_print " - backing up current up_param to /sdcard/up_param.bak"
cat /dev/block/platform/13d60000.ufs/by-name/up_param > /data/media/0/up_param.bak
chown 1023:1023 /data/media/0/up_param.bak
chmod 664 /data/media/0/up_param.bak
fi
ui_print " - installing new logo.jpg"
chmod 755 tar
mkdir tartemp
cd tartemp
/tmp/arter97/tar -xf /dev/block/platform/13d60000.ufs/by-name/up_param
cp /tmp/arter97/logo.jpg .
chown root:root *
chmod 444 logo.jpg
touch *
/tmp/arter97/tar -pcvf ../new.tar *
cd ..
cat new.tar > /dev/block/platform/13d60000.ufs/by-name/up_param
ui_print " - installing new svb_orange.jpg"
chmod 755 tar
mkdir tartemp
cd tartemp
/tmp/arter97/tar -xf /dev/block/platform/13d60000.ufs/by-name/up_param
cp /tmp/arter97/svb_orange.jpg .
chown root:root *
chmod 444 svb_orange.jpg
touch *
/tmp/arter97/tar -pcvf ../new.tar *
cd ..
cat new.tar > /dev/block/platform/13d60000.ufs/by-name/up_param
ui_print " - installing new booting_warning.jpg"
chmod 755 tar
mkdir tartemp
cd tartemp
/tmp/arter97/tar -xf /dev/block/platform/13d60000.ufs/by-name/up_param
cp /tmp/arter97/booting_warning.jpg .
chown root:root *
chmod 444 booting_warning.jpg
touch *
/tmp/arter97/tar -pcvf ../new.tar *
cd ..
cat new.tar > /dev/block/platform/13d60000.ufs/by-name/up_param
ui_print " - unmounting partition /data"
umount /data > /dev/null 2>&1
ui_print " "
ui_print "finished"
ui_print "Edited for s10+ by Whiskey103"
cd /
rm -rf /tmp/arter97
sync
Installation method with terminal command without TWRP (pushing up_param.bin using dd cmd on phone):
Download up_param.bin
Place in root of internal memory
Open terminal on phone like Material Terminal for example:
command:
su
command:
dd if=/sdcard/up_param.bin of=/dev/block/platform/13d60000.ufs/by-name/up_param
Restore Stock ZIP
Or rename the up_param.bak on your SD into up_param.bin and use the dd cmd method to restore it.
Credits:
@Radzian - used his base zip and edited for s10
@ianmacd for pointing to the error in my first attempt.

Works perfectly:good::good::good:

bininga59 said:
Works perfectly:good::good::good:
Click to expand...
Click to collapse
Thx for the feedback and unknowingly being my guinea pig, or labrat.. Whatever you prefer
Couldn't test it myself but it worked on my S10+ and basically they have the same bootloader to an extent but still.

It's going great on the S10.
Now only an animated gif is missing.:laugh:

bininga59 said:
It's going great on the S10.
Now only an animated gif is missing.[emoji23]
Click to expand...
Click to collapse
Yea, that's something I will try in the future.
Iam still trying to work myself into this Samsung stuff.
Coming from HTC for almost a decade this Galaxy is basically putting me back in baby modus lol.
Small steps going forward, learning curve starting from zero here

I know you can do it. [emoji4]
Gesendet von meinem SM-G973F mit Tapatalk

It's nice that you already have screen S10 but I would prefer without Magisk. It is possible?
Edit.
It's ok. I used Paint and removed the Magisk stamp. Now it's fun because my wife looked at the phone strangely when he restarted and saw this warning triangle and exclamation points asking if I ruined my phone ha h

Installation method with terminal command without TWRP (pushing up_param.bin using dd cmd on phone):
Download up_param.bin
Place in root of internal memory
Open terminal on phone like Material Terminal for example:
command:
su
command:
dd if=/sdcard/up_param.bin of=/dev/block/platform/13d60000.ufs/by-name/up_param

Whiskey103 said:
Installation method with terminal command without TWRP (pushing up_param.bin using dd cmd on phone):
Download up_param.bin
Place in root of internal memory
Open terminal on phone like Material Terminal for example:
command:
su
command:
dd if=/sdcard/up_param.bin of=/dev/block/platform/13d60000.ufs/by-name/up_param
Click to expand...
Click to collapse
Thanks man

Before I install this, how do I revert to stock if I want/need to? Do the originals get backed up, and if so how do I restore them (other than reinstalling the whole firmware)?

Mr Anderson said:
Before I install this, how do I revert to stock if I want/need to? Do the originals get backed up, and if so how do I restore them (other than reinstalling the whole firmware)?
Click to expand...
Click to collapse
Rename up_param.bak on your SD card and rename up_param.bin.
Then you can push it back with the dd su command in OP

Not booting.
Hi Dev.
So i made a few changes to the images and flashed the zip file with twrp.
This did not work and now my phone is stuck at black screen not even booting, is there a way to flash the recovery zip via odin since that is the only thing I can boot into.
Thank you.

FdeKlerk said:
Hi Dev.
So i made a few changes to the images and flashed the zip file with twrp.
This did not work and now my phone is stuck at black screen not even booting, is there a way to flash the recovery zip via odin since that is the only thing I can boot into.
Thank you.
Click to expand...
Click to collapse
You can try flashing BL file from firmware zip with just up-param file in it with Odin.
Or your patched firmware fully with Home CSC to restore it without loosing data.
Not sure what you did to the zip to end up like this though.

When I try to download the up_param.bin from the OP I get following error:
https://www.whiskey103.nl/index1.php?dir=SamsungS10-Plus/BootSplash/s10/
Incorrect format for file ./languages/da.txt on line 7.
Format is "variable name[tab]value"
No problem downloading the Restore Stock zip
*********************************
Ok I managed to download the up_param.bin using Tor.
When I place the file in Internal Storage (NOT Root or SDcard) and type the commands using Material Terminal I get error:
No such file or directory???

Norup58 said:
When I try to download the up_param.bin from the OP I get following error:
https://www.whiskey103.nl/index1.php?dir=SamsungS10-Plus/BootSplash/s10/
Incorrect format for file ./languages/da.txt on line 7.
Format is "variable name[tab]value"
No problem downloading the Restore Stock zip
*********************************
Ok I managed to download the up_param.bin using Tor.
When I place the file in Internal Storage (NOT Root or SDcard) and type the commands using Material Terminal I get error:
No such file or directory???
Click to expand...
Click to collapse
But it should be in root of internal storage. Not sure where you placed it.

Whiskey103 said:
But it should be in root of internal storage. Not sure where you placed it.
Click to expand...
Click to collapse
I'm using Mixplorer and have tried to put the file in root of Root, root of Internal Storage but not root of SDcard.
Get the same error either in Root or Internal Storage???

Norup58 said:
I'm using Mixplorer and have tried to put the file in root of Root, root of Internal Storage but not root of SDcard.
Get the same error either in Root or Internal Storage???
Click to expand...
Click to collapse
No idea what you are trying, nobody reported that it isn't working.
You must be placing it in the wrong place.
Should be in root of INTERNAL SD card.

Sort of fix.
Whiskey103 said:
You can try flashing BL file from firmware zip with just up-param file in it with Odin.
Or your patched firmware fully with Home CSC to restore it without loosing data.
Not sure what you did to the zip to end up like this though.
Click to expand...
Click to collapse
I've been an idiot as always.
Flashing BL works however then one ends up with "custom recovery..." error.
So to fix this I had to flash full patched rom with CSC HOME and then when booted to recovery wipe dalvik, cache and system partition leaving data and internal storage and then after that I flashed my custom rom.
Once booted. It was if I never had any issues.

Finally something nice.
FdeKlerk said:
I've been an idiot as always.
Flashing BL works however then one ends up with "custom recovery..." error.
So to fix this I had to flash full patched rom with CSC HOME and then when booted to recovery wipe dalvik, cache and system partition leaving data and internal storage and then after that I flashed my custom rom.
Once booted. It was if I never had any issues.
Click to expand...
Click to collapse
So thanks to @Whiskey103 I was able to get this working.
For those that like something different, here you go.
Zip attached.

I`m on snapdragon s10 version and this method doesnt work.
My path is /dev/block/platform/soc/1d84000.ufshc/by-name/
After doing ` dd if=/sdcard/up_param.bin of=/dev/block/platform/soc/1d84000.ufshc/by-name/up_param ` i got feedback:
3215+0 records in
3215+0 records out
1646080 bytes transferred in 0.019 secs (86635789 bytes/sec)
Rebooting and i see no changes

Related

X8 Custom ROM

Because propoff2 got himself banned, I've decided to re-create his threads for you, hopefully with easier to follow instructions than before.
X8 Android 2.1-rus
X8 Android 1.6
Modified Image (x8.img)
Data.img
Busybox, Rootshell, Chargemon
(If for whatever reason any of the above links don't work, scroll down and see propc's post.)
Before moving on, decide whether you want to boot the rom from the sdcard or from the internal memory, then use the correct instructions to do so.
If you've tried this method and REALLY don't like the customized rom, then see this thread for how to install a clean, pre-rooted rom!
==BOOTING CUSTOM ROM FROM SD==
Before you begin, put chargemon, busybox, rootshell, x8.img and data.img onto the sdcard.
1. Flash 1.6 firmware to the phone.
2. Root the phone.
3. Copy the files rootshell, chargemon and busybox to /system/bin
(You can do this by putting the files on the sdcard, and using a file manager such as root explorer to copy the files into /system/bin. Command line instructions will be here soonish. This guide is still a WIP).
4. Chmod the files.
Code:
chmod 4755 /system/bin/rootshell
chmod 755 /system/bin/busybox
chmod 777 /system/bin/chargemon
5. Copy both x8.img (/system) and data.img (/data) to the sdcard.
6. Flash 2.1 kernel using this flashing utility. (The GUI version is perfectly fine to use.)
Remember to remove system.sin and userdata.sin from the flash files!
7. Reboot and hope it works.
==BOOT CUSTOM ROM FROM INTERNAL MEMORY==
Before you being, copy x8.img and busybox on to the sdcard.
1. Follow steps 1-2 from the instructions above.
2. Copy busybox to /data/local/tmp
Code:
cd /data/local/tmp
cat /sdcard/busybox > /data/local/tmp/busybox
3. Chmod busybox.
Code:
chmod 755 busybox
4. Using busybox, remount /system as rewriteable.
Code:
./busybox mount -o remount,rw /system
./busybox sh
5. Mount x8.img.
Code:
./busybox mkdir /data/local/tmp/1
./busybox losetup /dev/block/loop1 /sdcard/x8.img
./busybox mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1 /data/local/tmp/1
6. Remove the contents of /system. ADVICE: Remove the folders one by one, leave /system/bin and /system/app last! That way your phone is less likely to crash whilst doing this step. DO NOT TRY AND USE YOUR PHONE WHILE DOING THIS, YOUR PHONE IS CERTAIN TO CRASH! Make sure the phone is locked.
Code:
./busybox rm -rf /system/media
./busybox rm -rf /system/usr
./busybox rm -rf /system/etc
./busybox rm -rf /system/lib
./busybox rm -rf /system/xbin
./busybox rm -rf /system/framework
./busybox rm -rf /system/fonts
./busybox rm -rf /system/drm
./busybox rm -rf /system/build.prop
./busybox rm -rf /system/app
./busybox rm -rf /system/bin
7. Now copy the files into the phone's internal memory. Again, we have to copy these over one by one, as the phone WILL run out of memory during this process! Most important files go first.
Code:
./busybox cp -prfR /data/local/tmp/1/bin /system/
./busybox cp -prfR /data/local/tmp/1/xbin /system/
./busybox cp -prfR /data/local/tmp/1/etc /system/
./busybox cp -prfR /data/local/tmp/1/usr /system/
./busybox cp -prf /data/local/tmp/1/build.prop /system/
./busybox cp -prfR /data/local/tmp/1/lib /system/
./busybox cp -prfR /data/local/tmp/1/framework /system/
./busybox cp -prfR /data/local/tmp/1/fonts /system/
./busybox cp -prfR /data/local/tmp/1/drm /system/
./busybox cp -prfR /data/local/tmp/1/media /system/
./busybox cp -prfR /data/local/tmp/1/app /system/
Hopefully you won't run out of space until you try and copy /app over. No worries! Your phone will still start, and you can easily restore those files after.
8. Flash the 2.1 kernel, and userdata.
Unlike in the previous instructions, you only want to remove system.sin from the flash files! Put userdata.sin back if you've removed it!
9. Turn on your phone and just hope you didn't mess up!
==APPS ON SD==
See this thread: App2SD Mod (Moves dalvik cache to SD) Instructions
ARGH!! MY PHONE IS STUCK IN A ETERNAL REBOOT? WHAT DO I DO?!
Well, if you know for sure what you did, and don't fancy reflashing all over again, then just plug in your phone and use adb to shell into the phone. Quickly fix the problem before the phone reboots!
Just putting this out there: These instructions were roughly written up. If you're having issues, don't be afraid to ask! If you spot any mistakes, please let me know! I'll expand on these instructions later.
All credits go to pulpoff2, for figuring out this solution, and propc for re-uploading the files, discovering steps 6 and 7 in the internal memory instructions, and for helping me fix these instructions multiple times.
Thank you! I will try this as soon as the files are available.
Are there any downsides? Is everything working as before? What about the speed (when loading apps for example)?
Yes, there are a few downsides. While booting from the sdcard, you cannot mount the sdcard via the phone (you'll need to use a card reader, or push/pull files with adb). There may be some performance issues while booting from the sdcard aswell. The camera and the music player also don't work.
However, if you decided to put the rom into the phone's internal memory, all this is fixed! Absolutely no downsides. Unless you don't like the theme, then I guess that is a downside.
thanks for making a new thread, thread pulpoff2 was hacked by ****-arsehole people! maybe.
I don't think so. The site that he used to host the files has been redirected to an anti-muslim site, by the looks of it.
aktw
Thanks man! Really appreciate it! Now I just need your tut for internal memory. Thanks again!
ML
Edit: Can you add app2sd tutorial?
Much more concise internal flashing (for anyone who wants it)
Code:
adb shell
su
cd /data/local/tmp
cat /sdcard/ext/bin/busybox > /data/local/tmp/busybox
chmod 755 busybox
./busybox mount -o remount,rw /system
./busybox sh
/data/local/tmp/busybox mkdir /data/local/tmp/1
/data/local/tmp/busybox losetup /dev/block/loop1 /sdcard/x8.img
/data/local/tmp/busybox mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1 /data/local/tmp/1
/data/local/tmp/busybox rm -r /system
/data/local/tmp/busybox cp -prf /data/local/tmp/1/* /system
There, the internal memory instructions are up.
EDIT
ALL FILES NEEDED FOR ABOVE METHOD STATED BY a-k-t-w
Mediafire folder
http://www.mediafire.com/?2kk19r7u4x1w3\
duckload:
data.img
X8.img
X8 2.1 russian
Hotfile:
data.img
X8.img
X8 2.1 russian
ext.rar at the attachment
for external rom (if you use adb shell)
Code:
su [B]look at phone screen and press "allow"[/B]
cd /data/local/tmp
cat /sdcard/ext/bin/busybox > /data/local/tmp/busybox
chmod 755 busybox
./busybox mount -o remount,rw /system
./busybox cp -r /sdcard/ext/* /system/
chmod 755 /system/bin/busybox
chmod 777 /system/bin/chargemon
chmod 755 /system/bin/e2fsck
chmod 4755 /system/bin/rootshell
to mount x8.img
Code:
mkdir /data/local/tmp/1
cat /sdcard/ext/bin/busybox > /data/local/tmp/busybox
/data/local/tmp/busybox losetup /dev/block/loop1 /sdcard/x8.img
/data/local/tmp/busybox mount -t ext2 -o rw,noatime,nodiratime /dev/block/loop1
EDIT : a-k-t-w completed the instruction himself. LOL..i think i'll be here for support..
-there you go.
ext.rar and unyaffs uploaded
i'll help by uploading the firmware files on mediafire.
actually I need the firmware 2.1 unmodified, but I'm okay to waiting.
Thx before.
That can be done. You mean unmodified, but rooted, right?
propc said:
...
i'll help by uploading the files on mediafire.
Click to expand...
Click to collapse
Thank you very much!! You have the latest ROM right? I'll add these to the OP when you are done.
a-k-t-w said:
[highlight]Mod Edit: Sorry, but I had to remove the link to the former dev's site due to the nature of that link[/highlight]
Click to expand...
Click to collapse
Understood.
Edit: @propc, What is unyaffs used for?
will the custom ROM have Timescape???? Or it will be the non-customized Android version.....
sry if this is a stupid question....
and i am just a beginner, so want a ask, what to you mean by "Flash 2.1 kernel" how to do it.....what are the files?? what is 2.1 kernel file??
i am new here...sry!
a-k-t-w said:
That can be done. You mean unmodified, but rooted, right?
Thank you very much!! You have the latest ROM right? I'll add these to the OP when you are done.
Click to expand...
Click to collapse
I think it's the latest. btw, it's stable no worries
mohakrastogi said:
will the custom ROM have Timescape???? Or it will be the non-customized Android version.....
sry if this is a stupid question....
and i am just a beginner, so want a ask, what to you mean by "Flash 2.1 kernel" how to do it.....what are the files?? what is 2.1 kernel file??
i am new here...sry!
Click to expand...
Click to collapse
Sorrry, I'll edit the OP. What I mean is, flash the 2.1 firmware, but without the files system.sin and userdata.sin (if your doing the sdcard method). This is basically flashing the 2.1 kernel only. Hang in there, the files will be available for download soon.
The custrom rom does not have timescape. You may have to restore ALL apps as there are some missing that will prevent you downloading your providers settings. I'm not sure which it is, so my solution is restoring them all. :-S
propc said:
I think it's the latest. btw, it's stable no worries
Click to expand...
Click to collapse
Excellent! Thanks again for the help.
a-k-t-w said:
Sorrry, I'll edit the OP. What I mean is, flash the 2.1 firmware, but without the files system.sin and userdata.sin (if your doing the sdcard method). This is basically flashing the 2.1 kernel only. Hang in there, the files will be available for download soon.
The custrom rom does not have timescape. You may have to restore ALL apps as there are some missing that will prevent you downloading your providers settings. I'm not sure which it is, so my solution is restoring them all. :-S
Excellent! Thanks again for the help.
Click to expand...
Click to collapse
i'm uploading data.img, x8.img and russian 2.1(.sin files)
any other files that need to be upload?
using unyaffs, you can extract x8.img directly to /system
maybe needed for future
folder for needed files are up (uploading other files .....)
HERE
please help me when write a command i got a problem with copy file
screenshot:
{
"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"
}
this a file problem with copy:
/data/local/tmp/busybox rm -r /system/app/com.mizusoft.relaxandsleep.apk
/data/local/tmp/busybox cp -prf /data/local/tmp/1/bin/* /system/bin/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/drm/* /system/drm/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/fonts/* /system/fonts/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/framework/* /system/framework/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/lib/* /system/lib/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/usr/* /system/usr/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/xbin/* /system/xbin/
/data/local/tmp/busybox cp -prf /data/local/tmp/1/build.prop /system/build.prop
/data/local/tmp/busybox cp -prf /data/local/tmp/1/media/* /system/media/
Click to expand...
Click to collapse
but remove a system -rm -r work for all files. help me pls
What is this custom ROM I keep reading about? What exactly is different there, except for the theme? I would like to see a screenshot of the theme, btw. Is JIT enabled?
Uhh. Probably not. The difference is just the theme, and root on 2.1. Because you can't get root any other way, if I'm not mistaken.
novincobra said:
please help me when write a command i got a problem with copy file
screenshot:
this a file problem with copy:
but remove a system -rm -r work for all files. help me pls
Click to expand...
Click to collapse
My guess is that you didn't mount the x8.img properly?
Or my cp command could be wrong. OH! Don't copy each app one by one, just the folders!
Don't put /* at the end! That means you are copying the contents of the folder! You want the entire folder on /system !
Ok, this means we have to use this customized ROM to gain root. Thanks for clarifying.

[Q] I need help getting root back on HKTW 2.3.4 =/

I keep trying all these codes and cant seem to get it to work.....anyone know like the exact steps and full code to put in cmd for "moto-fastboot"? Ive downloaded and extracted the img file for CWM recovery to my external sd as well and cant get that going....i think i just keep inputting the commands wrong or something i havent messed with this much yet....
help please? lol
From http://forum.xda-developers.com/showthread.php?t=1139303
This method worked for me
I don't know if I am the only one who realized there's su binary already in the build. Anyway, this is a shorter route to have root working on your phone. This only works with the HKTW 2.3.4 build! And this instruction have only be tested by me. So, do take precautionary measures.
DOWNLOAD: http://dl.dropbox.com/u/6418171/SuperUser.zip
INSTRUCTIONS:
1. Extract the zip to your internal storage (i.e. /sdcard)
2. Get into the phone shell i.e.
adb shell
3. Then, type and press enter:
su
4. Lastly, copy and paste these whole chunk to your phone shell and press enter:
mount -o remount,rw /dev/block/mmcblk0p12 /system && cp /sdcard/SuperUser/su /system/bin/su && chmod 6755 /system/bin/su && cp /sdcard/SuperUser/SuperUser.apk /system/app/SuperUser.apk && mv /system/xbin/su /system/xbin/dosu
If there's no error with the output, you should have root access on your phone now. Tada! Do report of this works for you!
try this
http://forum.xda-developers.com/showthread.php?t=1139303
extract that zip and put it in your internal sd card.
then type this in cmd
C:\Users\Your Name>cd C:\android-sdk-windows\tools
then type "adb shell"
then "su"
then copy and paste this
mount -o remount,rw /dev/block/mmcblk0p12 /system && cp /sdcard/SuperUser/su /system/bin/su && chmod 6755 /system/bin/su && cp /sdcard/SuperUser/SuperUser.apk /system/app/SuperUser.apk && mv /system/xbin/su /system/xbin/dosu
and then hit enter. sometimes it does not work, just keep trying make youre youre on usb connection "none" not mass storage or phone portal.
also make sure usb debugging is on. if you get any type of error, its probably that adb is not coming up in this case just do the afterupdate bat. but you should be fine. just so you know i had to try that method like 3 or 4 times before it work. but it does work. credit goes all to arctu.
After doing root above I followed instructions from
http://forum.xda-developers.com/showthread.php?t=1138541
to get CWM Recovery working
Thanks, this method didnt work for me but it did get me on the right track. I had to go to http://briefmobile.com/motorola-atrix-4g-root and follow the cmd instructions for adb and it worked like a charm
Thanks again!
mburlingame said:
From http://forum.xda-developers.com/showthread.php?t=1139303
This method worked for me
I don't know if I am the only one who realized there's su binary already in the build. Anyway, this is a shorter route to have root working on your phone. This only works with the HKTW 2.3.4 build! And this instruction have only be tested by me. So, do take precautionary measures.
DOWNLOAD: http://dl.dropbox.com/u/6418171/SuperUser.zip
INSTRUCTIONS:
1. Extract the zip to your internal storage (i.e. /sdcard)
2. Get into the phone shell i.e.
adb shell
3. Then, type and press enter:
su
4. Lastly, copy and paste these whole chunk to your phone shell and press enter:
mount -o remount,rw /dev/block/mmcblk0p12 /system && cp /sdcard/SuperUser/su /system/bin/su && chmod 6755 /system/bin/su && cp /sdcard/SuperUser/SuperUser.apk /system/app/SuperUser.apk && mv /system/xbin/su /system/xbin/dosu
If there's no error with the output, you should have root access on your phone now. Tada! Do report of this works for you!
Click to expand...
Click to collapse
Everytime i try this i get "error cannot load recovery-en-goapk.img"
mburlingame said:
After doing root above I followed instructions from
http://forum.xda-developers.com/showthread.php?t=1138541
to get CWM Recovery working
Click to expand...
Click to collapse
ShawnXVIII said:
Everytime i try this i get "error cannot load recovery-en-goapk.img"
Click to expand...
Click to collapse
Are you in the right folder?
Sent from my MB860 using Tapatalk
I ran beforeupdate.dat and afterupdate.dat to root mine.
Here is the root thread in the dev section. I was unable to get the OP's method to work in that thread but I did link the 2 .dat files I used to root.
http://forum.xda-developers.com/showthread.php?t=1139303
ShawnXVIII said:
I keep trying all these codes and cant seem to get it to work.....anyone know like the exact steps and full code to put in cmd for "moto-fastboot"? Ive downloaded and extracted the img file for CWM recovery to my external sd as well and cant get that going....i think i just keep inputting the commands wrong or something i havent messed with this much yet....
help please? lol
Click to expand...
Click to collapse
[ROOT]The FLASHABLE zip file for ROOTing Atrix 2.3.4 HKTW(12)
http://forum.xda-developers.com/showthread.php?t=1140110

[Dev][Tool][Script to]Make ODIN flashable Roms ext4 devices

Hey fellas!!!
This is my first real contribution to my xda friends .I happy to share with you guys the script to make ODIN flashable rom for ext4 devices.
First of all I would like to say that this script currently supports only International variants of sgs2,sgs3 and SG Note.This is because I own only Note (similar to s2) and my friend has s3 which I used to make s3 compatible.I can support any devices if you guys can give me the required data
So now into the topic
In order to work with the script,you need the following:
A PC/Laptop with linux installed either as dualboot or in vm
A rooted Phone which supported by the script.
A usb cable
And of course you need your brain
Apart from the hardware,you will also need:
A stock rom from which you need to take the following:
cache.img
modem.bin
hidden.img
and a custom kernel(zImage) of you choice.(recovery.img and boot.img in case of s3)
Now download the script and do the following:
Extract ODIN-script.tar anywhere.
Run first_time.sh (Needed Only for the first time)
Put the above collected .img's,.bin and/or zImage inside ODIN-script directory
Connect your phone to PC/Laptop with usb debugging enabled.
Run the script and follow the instructions
Your Rom will be in the same directory in few mins
Note1:The Rom obtained by the above is not a full wipe rom.If you need to make it full wipe(factory reset),you need aditional empty data.img(for note/s2) or userdata.img(s3).I will upload data.img for Note.It "may" work on s2 too.But I havent tested.so its on your own risk
S3 users,I'm sorry I can help you .Because I dont know the size of /data partition to make an empty image.
Note2:You can always flash the rom with .pit and repartition.I have always used .pit to flash my rom.But still you are at your own risk.
Disclaimer:Do this at your own risk!!!I'm not responsible if you brick your phone.(Though you cannot if you do everything correctly )
Download link and changelog on next post.
And finally if you like my project and if you think you need to support me for future updates on this,Please do donate .And do not copy/edit/alter this work without my permission!!!
Download Links and changelogs
Changelog for v1:
Code:
[LIST]
[*]Initial release
[/LIST];)
Changelog for v2:
Code:
[LIST]
[*]Cleaned the code and redone entirely
[*]Added support for preload for some devices
[*]bug fixes
[/LIST]
Thanks to:
1.As-I9000 for zlibs and first_time.sh
vijai2011 said:
Reserved
Click to expand...
Click to collapse
Reserved!!!
really awesome...going to try now and let you know the feedback...
Ok...Thats good...Just an update...Dont add cache.img for now...It takes forever in recovery to flash....Found the issue and working on a fix
vijai2011 said:
Ok...Thats good...Just an update...Dont add cache.img for now...It takes forever in recovery to flash....Found the issue and working on a fix
Click to expand...
Click to collapse
thank you and i was about to test and i will refrain from doing that till you release the fix!
grgsiocl said:
thank you and i was about to test and i will refrain from doing that till you release the fix!
Click to expand...
Click to collapse
Hey...You can try it without cache.img as long as you have csc within you /system
But still if you have added cache.img,it will boot but only with couple of reboots and a looooong time in recovery
vijai2011 said:
Hey fellas!!!
Note1:The Rom obtained by the above is not a full wipe rom.If you need to make it full wipe(factory reset),you need aditional empty data.img(for note/s2) or userdata.img(s3).I will upload data.img for Note.It "may" work on s2 too.But I havent tested.so its on your own risk
[/COLOR]
Click to expand...
Click to collapse
If you needed FULL WIPE DATA - FACTORY RESET, you need to put the image cache file with the command wipe data...
as i9000 said:
If you needed FULL WIPE DATA - FACTORY RESET, you need to put the image cache file with the command wipe data...
Click to expand...
Click to collapse
Nope...instead I have added a empty data.img It will wipe off data...But didn't make it for s3 because I have heard s3 has /data and /sdcard combined.So if I make one for s3,it will wipe sdcard too.But need a confirmation on this
And I have fixed recovery issue too in v2 and it should be fine now.
Finally had a look on your script too.It also looks good.good job.nice work .May be we two can work together to make a kitchen???
Sent from my GT-N7000 using xda app-developers app
I used your script as guiding for customizing my own odin rom.
- I untarred my firmware.tar.md5
- $ simg2img system.img.ext4 system.raw
- $ sudo mount -t ext4 -o loop system.raw /tmp
I didn't change a thing and then repacked it
- make_ext4fs -s -l 512M -a system newsystem.img.ext4 /tmp
- chown 1000:1000 newsystem.img.ext4
- packed everything with $tar -H ustar -cvf out.tar *.img.* fat.bin
- signed the package md5sum -t out.tar >> out.tar
- mv out.tar out.tar.md5
I flashed it, had no problems, but after the flashing i see "failed to mount /system (invalid argument)
And as my system partition doesn't get mounted, i cant startup my phone.
Does anyone have a clue on what i could be doing wrong?
1bymany said:
I used your script as guiding for customizing my own odin rom.
- I untarred my firmware.tar.md5
- $ simg2img system.img.ext4 system.raw
- $ sudo mount -t ext4 -o loop system.raw /tmp
I didn't change a thing and then repacked it
- make_ext4fs -s -l 512M -a system newsystem.img.ext4 /tmp
- chown 1000:1000 newsystem.img.ext4
- packed everything with $tar -H ustar -cvf out.tar *.img.* fat.bin
- signed the package md5sum -t out.tar >> out.tar
- mv out.tar out.tar.md5
I flashed it, had no problems, but after the flashing i see "failed to mount /system (invalid argument)
And as my system partition doesn't get mounted, i cant startup my phone.
Does anyone have a clue on what i could be doing wrong?
Click to expand...
Click to collapse
If you did exactly what you posted,then,
1. You should not have got system.img.ext4 but system.img and so simg2img is simg2img system.img system.img.ext
2./temp in mount command would be your temp filesystem where system files are stored.Use a relative path like TempDir in your PWD
3. Are you sure the make_ext4fs line is correct?You said you used my script as reference and I have never used that command at all.Its like:
Code:
sudo ./mkuserimg.sh -s TempDir factoryfs.img ext4 ./temp 893386752B
(in mb is also fine)
where the numbers indicate the size of system partition in Bytes.Be sure to cd to ext4_utils before executing this command and should always be run as sudo as the mount is done as sudo.And donot include .ext4 at the end.Use just img.Works better.
4.again...chown should be sudo.As the img is owned by root and so you cannot chown it with basic user permissions.Simple user hierarchy
5.You did a blunder here in tar command if you put the original system.img and the newly packed img in the same directory.As the command will include all .img's which we donot want.
vijai2011 said:
If you did exactly what you posted,then,
1. You should not have got system.img.ext4 but system.img and so simg2img is simg2img system.img system.img.ext
2./temp in mount command would be your temp filesystem where system files are stored.Use a relative path like TempDir in your PWD
3. Are you sure the make_ext4fs line is correct?You said you used my script as reference and I have never used that command at all.Its like:
Code:
sudo ./mkuserimg.sh -s TempDir factoryfs.img ext4 ./temp 893386752B
(in mb is also fine)
where the numbers indicate the size of system partition in Bytes.Be sure to cd to ext4_utils before executing this command and should always be run as sudo as the mount is done as sudo.And donot include .ext4 at the end.Use just img.Works better.
4.again...chown should be sudo.As the img is owned by root and so you cannot chown it with basic user permissions.Simple user hierarchy
5.You did a blunder here in tar command if you put the original system.img and the newly packed img in the same directory.As the command will include all .img's which we donot want.
Click to expand...
Click to collapse
First of all, thanks for the reply.
second:
1. My phone is not rooted yet, it's a GT-S6500D aka Samsung galaxy tab. So I used a firmware.tar.md5 (that i have flashed to test and works)
and in this firmware.tar.md5 i have following files: boot.img, cache.img.ext4, fat.bin, hidden.img.ext4, recovery.img and system.img.ext4
So the system.img.ext4 wasn't a typo and the system.raw is just an arbitrary name i have chosen.
2. I don't get the mountpoint. Is this the mountpoint on the phone? of on my computer?
3. I have analysed the mkuserimg.sh script, and it is just a wrapper that flips the argument order. I have no clue why they made it..
So i doubt my problem would be in this line, but I will try, as i don't know what else can go wrong
4. chown should indeed be sudo, no doubt about that I just didn't type it here
5. I skipped this step a bit in the explanation, but i made the sure the directory only concluded the necessary files, naming the original files from step 1 or modified files.
6. I don't know if this could help, but if i unpack for example system.img.ext4 and repack it again, the new file will be bigger then the original one.. I was thinking maybe Samsung adjusted some things, but maybe i need some more arguments in my make_ext4fs command..
grtz
Fixed it!
The problem was that i was using a size of 512M without knowing where it came from.
I flashed the original firmware back to the phone, did a
Code:
adb shell "df /system "
to know what size my img needed to be. In my case it was a total size of 492M. So i used following command to make my system.img.ext4
Code:
make_ext4fs -s -l 492M -a system system.img.ext4 /system
Now trying to pack my own kernel in the boot.img
thanks for the support!
1bymany said:
Fixed it!
The problem was that i was using a size of 512M without knowing where it came from.
I flashed the original firmware back to the phone, did a
Code:
adb shell "df /system "
to know what size my img needed to be. In my case it was a total size of 492M. So i used following command to make my system.img.ext4
Code:
make_ext4fs -s -l 492M -a system system.img.ext4 /system
Now trying to pack my own kernel in the boot.img
thanks for the support!
Click to expand...
Click to collapse
Sorry for the late response .got a little busy.Happy that you solved it .Just an hint,you can use -h to see the size better readable by humans(In M and G) in df command incase you find its in kb or B
Sent from my GT-N7000 using xda app-developers app
Updated to v2
vijai2011 said:
Updated to v2
Click to expand...
Click to collapse
thanks man

Stuck on kindle fire screen

HI, I need help, my little brother installed ChainFire's 3D app on it I don´t know what it did but now it wont boot, to make things worst he tried to fix it doing a reset, fortunatelly (or not) I've checked root permissions with the Vroot and showed it still has root permissions, is there any way to to recover it?
?
SiulGM said:
HI, I need help, my little brother installed ChainFire's 3D app on it I don´t know what it did but now it wont boot, to make things worst he tried to fix it doing a reset, fortunatelly (or not) I've checked root permissions with the Vroot and showed it still has root permissions, is there any way to to recover it?
Click to expand...
Click to collapse
I have heard of that happening... Have you tried Google search chainfire 3d apk. Brick repair? Or forum search I have heard of it quite frequently so I know there has to be a fix here somewhere at xda ....
jimyv said:
I have heard of that happening... Have you tried Google search chainfire 3d apk. Brick repair? Or forum search I have heard of it quite frequently so I know there has to be a fix here somewhere at xda ....
Click to expand...
Click to collapse
thank you! I've found a thread here but every time I try to execute "cf3d_uninstall.sh" it shows "not found" I've already pulled "system/lib" and the file exist, am I doing something wrong?
{
"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"
}
[/url]
imagen jpg[/IMG]
SiulGM said:
thank you! I've found a thread here but every time I try to execute "cf3d_uninstall.sh" it shows "not found" I've already pulled "system/lib" and the file exist, am I doing something wrong?
[/url]
imagen jpg[/IMG]
Click to expand...
Click to collapse
Adb reboot?
jimyv said:
Adb reboot?
Click to expand...
Click to collapse
abd reboot??? already did the reboot, but still leads me to the "kindle fire" screen, tried to push the renamed files but is not allowed, is there any way to push files to system/lib ? or rename them using adb?
SiulGM said:
thank you! I've found a thread here but every time I try to execute "cf3d_uninstall.sh" it shows "not found" I've already pulled "system/lib" and the file exist, am I doing something wrong?
[/url]
imagen jpg[/IMG]
Click to expand...
Click to collapse
Use adb shell to manually remove (rm) the files installed. Open that bat script in a text editor & then manually do it from your platform tools or wherever you adb is setup to run from. You'll probably need to manually mount the system/lib folder to rw first.
---------- Post added at 10:39 AM ---------- Previous post was at 10:31 AM ----------
SiulGM said:
abd reboot??? already did the reboot, but still leads me to the "kindle fire" screen, tried to push the renamed files but is not allowed, is there any way to push files to system/lib ? or rename them using adb?
Click to expand...
Click to collapse
the rm command.
adb shell rm -r /system/lib/WhateverFileNameHere.so
Don't forget to mount RW first using:
adb shell
su
mount -o remount,rw /system
Though you may need to push busybox binary & applets to xbin first.
Also, if su access is giving you issues, you can try pushing the SuperSu binary first too.
GSLEON3 said:
Use adb shell to manually remove (rm) the files installed. Open that bat script in a text editor & then manually do it from your platform tools or wherever you adb is setup to run from. You'll probably need to manually mount the system/lib folder to rw first.
---------- Post added at 10:39 AM ---------- Previous post was at 10:31 AM ----------
the rm command.
adb shell rm -r /system/lib/WhateverFileNameHere.so
Don't forget to mount RW first using:
adb shell
su
mount -o remount,rw /system
Though you may need to push busybox binary & applets to xbin first.
Also, if su access is giving you issues, you can try pushing the SuperSu binary first too.
Click to expand...
Click to collapse
Thanks for your help, I'm sorry may be I'm not getting this, I'm new to adb,.. I tried and get this error
[/url]
subefotos[/IMG]
this is the text in the unistaller file, but how do I shoul execute this manually?
"#!/system/bin/sh
mount -o rw -o remount /dev/block/platform/msm_sdcc.1/by-name/system /system
stop
cat /system/lib/libGLESv1_CM_ORG_CF3D.so > /system/lib/libGLESv1_CM.so
chown 1000.1000 /system/lib/libGLESv1_CM.so
chown 1000:1000 /system/lib/libGLESv1_CM.so
chown system.system /system/lib/libGLESv1_CM.so
chown system:system /system/lib/libGLESv1_CM.so
chmod 644 /system/lib/libGLESv1_CM.so
cat /system/lib/libGLESv2_ORG_CF3D.so > /system/lib/libGLESv2.so
chown 1000.1000 /system/lib/libGLESv2.so
chown 1000:1000 /system/lib/libGLESv2.so
chown system.system /system/lib/libGLESv2.so
chown system:system /system/lib/libGLESv2.so
chmod 644 /system/lib/libGLESv2.so
#rm /system/lib/libGLESv1_CM_ORG_CF3D.so
#rm /system/lib/libGLESv2_ORG_CF3D.so
rm /system/lib/cf3d_uninstall.sh
rm /system/lib/cf3d_sh
reboot -f
reboot
reboot normal
toolbox reboot
busybox reboot -f
busybox reboot
busybox reboot normal"
SiulGM said:
Thanks for your help, I'm sorry may be I'm not getting this, I'm new to adb,.. I tried and get this error
[/url]
subefotos[/IMG]
Click to expand...
Click to collapse
Each line is a new entry, do not run them together. Try this:
adb shell
su
mount -o remount,rw /system
now open a second command prompt window & leave the first open. In the second window enter the following:
adb shell
su
rm -r /system/lib/*cf3d.so
rm -r /system/lib/libGLESv*.so
Now open the ota or rom version you are on & extract the original LibGLESv* files & go back to first window & type this
exit
exit
adb push libGLESv1_CM.so /system/lib/
adb push libGLESv2.so /system/lib/
adb shell
su
chmod 644 /system/lib/*.so
chown root.root /system/lib/*.so
reboot
Make sure to extract the original lib files to the working folder for adb, i.e., wherever it says you are in the cmd window, the PC folder you see at the start of the cmd window.
GSLEON3 said:
Each line is a new entry, do not run them together. Try this:
adb shell
su
mount -o remount,rw /system
now open a second command prompt window & leave the first open. In the second window enter the following:
adb shell
su
rm -r /system/lib/*cf3d.so
rm -r /system/lib/LibGLESv*.so
Now open the ota or rom version you are on & extract the original LibGLESv* files & go back to first window & type this
exit
exit
adb push libGLESv1_CM.so /system/lib/
adb push libGLESv2.so /system/lib/
adb shell
su
chmod 644 /system/lib/*.so
chown root.root /system/lib/*.so
reboot
Make sure to extract the original lib files to the working folder for adb, i.e., wherever it says you are in the cmd window, the PC folder you see at the start of the cmd window.
Click to expand...
Click to collapse
Well... I think I did something relly worng... it just shows "kindle fire" on gray... then the system recovery
[/url]
subir fotos online[/IMG]
SiulGM said:
Well... I think I did something relly worng... it just shows "kindle fire" on gray... then the system recovery
[/url]
subir fotos online[/IMG]
Click to expand...
Click to collapse
I can't really tell much from a cropped screen image...
At what point did you have issues? You downloaded & pushed the original libs before rebooting, right?
Just out of curiosity, who thought it would be a good idea to used drivers that have been out of development for nearly 3 years?
GSLEON3 said:
I can't really tell much from a cropped screen image...
At what point did you have issues? You downloaded & pushed the original libs before rebooting, right?
Click to expand...
Click to collapse
I think I've deleted system/lib... btw, is not cropped, that is the way is showed on screen
SiulGM said:
I think I've deleted system/lib... btw, is not cropped, that is the way is showed on screen
Click to expand...
Click to collapse
How did you do that? You need to set the viewable width & the cache scroll to be bigger. That way you can see everything you type.
GSLEON3 said:
How did you do that? You need to set the viewable width & the cache scroll to be bigger. That way you can see everything you type.
Click to expand...
Click to collapse
I relly don´t know... I think thats I did because of this screen
[/url]
subir imagenes gratis[/IMG]
so.. is there a chance for this to work again?
SiulGM said:
I relly don´t know... I think thats I did because of this screen
[/url]
subir imagenes gratis[/IMG]
so.. is there a chance for this to work again?
Click to expand...
Click to collapse
Try to adb push the original libGLESv files into the system/lib folder. You don't need to shell for that. Just adb push as indicated in the previous posts.
You also may need to try to adb mount
GSLEON3 said:
Try to adb push the original libGLESv files into the system/lib folder. You don't need to shell for that. Just adb push as indicated in the previous posts.
Click to expand...
Click to collapse
OH, I cant now adb is not working I know the kindle is detected because a PDA.net pop up, then I try to get adb shell and shows what´s on the image after a while it reboots to the system recovery
I got this when trying to copy what I pulled fron system/lib
[/url]
subir fotos[/IMG]
GSLEON3 said:
Try to adb push the original libGLESv files into the system/lib folder. You don't need to shell for that. Just adb push as indicated in the previous posts.
You also may need to try to adb mount
Click to expand...
Click to collapse
/lib does not exist, now I've lost su, is there a way to create /lib and then push all the files in? or did I killed it?
SiulGM said:
/lib does not exist, now I've lost su, is there a way to create /lib and then push all the files in? or did I killed it?
Click to expand...
Click to collapse
Yes, but you are going to have to mount first. You may need to use Linux. Unless you entered something not in the above posts, or accidentally hit enter before finishing the command line, lib can't go anywhere, at least not from any of those commands.
GSLEON3 said:
Yes, but you are going to have to mount first. You may need to use Linux. Unless you entered something not in the above posts, or accidentally hit enter before finishing the command line, lib can't go anywhere, at least not from any of those commands.
Click to expand...
Click to collapse
Hi! first I want to thank you for all your help on this! just installed Ubuntu, what should I do now?
I would say there is no hope. If you deleted the 'lib' folder, your Kindle cannot execute programs like the adb client. With Safestrap you could reflash the folder. But if you dont have Safestrap... You have a really big problem! . Maybe fastboot could help, but i dont know how
Sent from my GT-I9505

How to root Huawei MediaPad T1-701w ?

Hi!
I'm trying to root my Huawei MediaPad T1-701w but am in need of help... I've tried out nearly every 'one click root' app or PC program out there, but every single one fails. Huawei has hardened the kernel/android version and patched all known exploits to date (October 2016). The issue is that the variant of the MediaTab I have is pretty uncommon (T1-701w) so there is not a lot to find about it.
{
"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, I did find that the iovyroot might be able to root it, see https://forum.xda-developers.com/general/xda-assist/huawei-t1-701u-write-protection-t3418836 , but the current pre-compiled version of iovyroot is not compatible with my tablet (it needs new offsets).
I also tried downgrading, but I don't quite understand how to do so. I found one older ROM for my Mediatab variant which might contain more exploits according to 4PDA.ru, but how do I downgrade? The 'dload' method does not work. Also before downgrading, I want to dump my current ROM, which requires root, right?
Can anyone help me out here please?
Thank you!
If you have the most recent stock ROM of your device (oct. 2016), extract the file "boot.img" out of (UPDATE.APP) and put it here, and i'll send you back the rooted one, then follow the steps in the following thread to make it works:
https://forum.xda-developers.com/huawei-mediapad/general/root-root-mediapad-t1-10-t1-a21l-t3601136
=====
Here's the link for the stock ROM:
http://consumer.huawei.com/nl-en/support/downloads/detail/index.htm?id=80385
mann1 said:
If you have the most recent stock ROM of your device (oct. 2016), extract the file "boot.img" out of (UPDATE.APP) and put it here, and i'll send you back the rooted one, then follow the steps in the following thread to make it works:
https://forum.xda-developers.com/huawei-mediapad/general/root-root-mediapad-t1-10-t1-a21l-t3601136
=====
Here's the link for the stock ROM:
http://consumer.huawei.com/nl-en/support/downloads/detail/index.htm?id=80385
Click to expand...
Click to collapse
Many thanks for your reply! Please find the boot.img from the UPDATE.app of my ROM with header file (?) here: http://data.freek.ws/public/huawei_t1-701w/V100R001C232B009CUSTC232D001/
(It was too large to attach to this post, sorry).
Is PhilZ Touch 6 Recovery compatible with my tablet?
Many many thanks!! Kind regards.
Well, download the following zip file here
Both rooted and stock imgs are included.
I do not know if PhilZ recovery will work with your device or not, i don't have the same model.
Give it a try, you don't need full functions anyway , just the "install zip" one, BUT keep the stock "recovery.img" before you do, so you can go back to it in case philz didn't work.
Also you can try the CWM recovery fromhere, both ways are risky, but nothing serious i guess, you can go back to the stock recovery at any moment.
Tell me the results pls
GOOD LUCK
mann1 said:
Well, download the following zip file here
Both rooted and stock imgs are included.
I do not know if PhilZ recovery will work with your device or not, i don't have the same model.
Give it a try, you don't need full functions anyway , just the "install zip" one, BUT keep the stock "recovery.img" before you do, so you can go back to it in case philz didn't work.
Also you can try the CWM recovery fromhere, both ways are risky, but nothing serious i guess, you can go back to the stock recovery at any moment.
Tell me the results pls
GOOD LUCK
Click to expand...
Click to collapse
Many many thanks for your quick reply and effort
I manage dto flash the rooted boot.img without any problems, great !
Howevever, in your tutorial you write that I need to flash SuperSU in order to activate the rooting. But how can I flash it if I don't have custom recovery? PhilZ recovery sadly does not work, I tried
Stock recovery does not allow me to flash super su.
Many thanks
Kind regards.
You're very welcome
Try the following:
use command prompet and type:
adb root
if it works w/o any errors type:
adb shell
a new cm window will pop up with your device shell
[email protected]:/ $
type:
su
if the root works, the shell is gonna be:
[email protected]:/ #
If it works, download the superSu.apk file NOT the zip, restart the device,
then put SuperSU options "Default access: Grant" and check "Enable su during boot" then restart
mann1 said:
You're very welcome
Try the following:
use command prompet and type:
adb root
if it works w/o any errors type:
adb shell
a new cm window will pop up with your device shell
[email protected]:/ $
type:
su
if the root works, the shell is gonna be:
[email protected]:/ #
If it works, download the superSu.apk file NOT the zip, restart the device,
then put SuperSU options "Default access: Grant" and check "Enable su during boot" then restart
Click to expand...
Click to collapse
Once again thanks for your reply.
Hmm, the root doesnt seem to be working:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
U5MDU17327001608 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb root
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
/system/bin/sh: su: not found
But I did flash your rooted_boot.img.. What should I do?
Nope, it works very well, if it doesn't you would see an error after you type "adb root"
Just try to install superSU.apk directly like we do with any apk, then restart.
OR
If it didn't work, try this:
=========
adb devices
adb root
adb shell "mount -o remount,rw /system"
adb push su /system/bin/su
adb push superuser.apk /system/app
adb reboot
=========
put the superSu in the same folder with adb
mann1 said:
Nope, it works very well, if it doesn't you would see an error after you type "adb root"
Just try to install superSU.apk directly like we do with any apk, then restart.
OR
If it didn't work, try this:
=========
adb devices
adb root
adb shell "mount -o remount,rw /system"
adb push su /system/bin/su
adb push superuser.apk /system/app
adb reboot
=========
put the superSu in the same folder with adb
Click to expand...
Click to collapse
Thanks again for the help!
My tablet is a tough one I think. It says 'mount: Operation not permited'.
Any ideas?
Yep, your tablet comes with Spreadtrum SC7731G, and it's not easy to find a custom recovery for these chipsets.
But i'm sure the device is already rooted now, we just need a working custom recovery to flash the superSU, so pls keep the rooted boot.
===
I've googled some custom recoveries that are compatible with SC7731, so give them a try:
https://drive.google.com/file/d/0B8vhq1nCgRGdR3VmbE1RSWNRSjA/view
this is number 9 recovery img in this thread:
https://forum.xda-developers.com/showthread.php?t=2527663
=====
and here's another one:
http://www.mediafire.com/file/1j4uj3c4vk5rtcw/recovery.img
=====
BE CAREFUL,these ones are not tested on your device, so test them very carefully, one of them may work but with cranky touch function, try to use it just to flash the SuperSu ZIP file NOT apk.
mann1 said:
Yep, your tablet comes with Spreadtrum SC7731G, and it's not easy to find a custom recovery for these chipsets.
But i'm sure the device is already rooted now, we just need a working custom recovery to flash the superSU, so pls keep the rooted boot.
===
I've googled some custom recoveries that are compatible with SC7731, so give them a try:
https://drive.google.com/file/d/0B8vhq1nCgRGdR3VmbE1RSWNRSjA/view
this is number 9 recovery img in this thread:
https://forum.xda-developers.com/showthread.php?t=2527663
=====
and here's another one:
http://www.mediafire.com/file/1j4uj3c4vk5rtcw/recovery.img
=====
BE CAREFUL,these ones are not tested on your device, so test them very carefully, one of them may work but with cranky touch function, try to use it just to flash the SuperSu ZIP file NOT apk.
Click to expand...
Click to collapse
Thanks for your reply
Hmm, are you sure it's rooted? Because it keeps complaining about 'no permission' or is that caused due to incompatibility with my device?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.171s]
booting...
FAILED (remote: no permission)
finished. total time: 2.173s
Freekers1337 said:
Thanks for your reply
Hmm, are you sure it's rooted? Because it keeps complaining about 'no permission' or is that caused due to incompatibility with my device?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 2.171s]
booting...
FAILED (remote: no permission)
finished. total time: 2.173s
Click to expand...
Click to collapse
I guess it's compatibility issue.
1- flash the rooted boot
fastboot flash boot rooted_boot.img
===
2- flash one of the custom recoveries (don't boot them)
fastboot flash recovery recovery.img (use the right file name)
then restart
===
your device will start normally w/o any problem, there's no problem with the rooted boot.
then turn off the tablet and get into the recovery mode by (Vol. down + power buttons)
do not use the "adb reboot-bootloader" cm.
===
now the the recovery might work, and if it didn't, you will face the bootloader screen mode, type:
fastboot reboot
to restart your device, and flash the 2nd recovery img.
So sorry i don't have your device to try that myself.
mann1 said:
I guess it's compatibility issue.
1- flash the rooted boot
fastboot flash boot rooted_boot.img
===
2- flash one of the custom recoveries (don't boot them)
fastboot flash recovery recovery.img (use the right file name)
then restart
===
your device will start normally w/o any problem, there's no problem with the rooted boot.
then turn off the tablet and get into the recovery mode by (Vol. down + power buttons)
do not use the "adb reboot-bootloader" cm.
===
now the the recovery might work, and if it didn't, you will face the bootloader screen mode, type:
fastboot reboot
to restart your device, and flash the 2nd recovery img.
So sorry i don't have your device to try that myself.
Click to expand...
Click to collapse
Thanks for sticking with me
I tried both custom recoveries you sent me, but both fail with error: 'FAILED (remote: image is not a boot image)'.
I also tried creating my own recovery using these two tutorials: https://www.youtube.com/watch?v=w1Ap2YwmGVk & https://www.youtube.com/watch?v=hwMFBuCY-5k but I get the same error (image is not a boot image).
Grrrr, do you still have any ideas ?
Kind regards!
YVW, it's ok, no problem at all.
Pls do not use the command
fastboot boot recovery *.img to try the custom recovery, flash it directly with
fastboot flash recovery filename.img
usually custom recoveries even if they work fine give the same error when u try them with the "boot" command
mann1 said:
YVW, it's ok, no problem at all.
Pls do not use the command
fastboot boot recovery *.img to try the custom recovery, flash it directly with
fastboot flash recovery filename.img
usually custom recoveries even if they work fine give the same error when u try them with the "boot" command
Click to expand...
Click to collapse
I did flash it directly using: fastboot flash recovery xxxxx.img . That's when I got the 'image is not a boot image image' error
Well, we will try easy step, flash the rooted boot img then restart the device, then go to google play, and use the online install function to get superSU.apk, do not download it, just install it directly from the site
mann1 said:
Well, we will try easy step, flash the rooted boot img then restart the device, then go to google play, and use the online install function to get superSU.apk, do not download it, just install it directly from the site
Click to expand...
Click to collapse
I'm sorry, I can't find the online install function. I went to Google Play and installed SuperSU but as soon as it opens it says Device not rooter. After that it says no SU binary found and automatically closes..
Freekers1337 said:
I'm sorry, I can't find the online install function. I went to Google Play and installed SuperSU but as soon as it opens it says Device not rooter. After that it says no SU binary found and automatically closes..
Click to expand...
Click to collapse
It's ok, don't give up
Right now i run out of ideas, but give me some time to get my unrooted stock ROM back, to start the race toward rooting w/o custom recovery.
mann1 said:
It's ok, don't give up
Right now i run out of ideas, but give me some time to get my unrooted stock ROM back, to start the race toward rooting w/o custom recovery.
Click to expand...
Click to collapse
OK I'll wait for your reply.
Freekers1337 said:
OK I'll wait for your reply.
Click to expand...
Click to collapse
Hi
After long journey, i could say I've got an effective way to root your device and mine too w/o custom recovery, it works fine for me, hope it will be the same for you.
First you need to download the following files:
1- New rooted_boot img from here
2- Compressed folder mann1.zip from here
3- SuperSu.apk file from here
====
Now lets start,
1- Unzip the rooted img then flash it, (be careful it's not tested):
use the flash command NOT boot
Code:
fastboot flash boot rooted_boot.img
===
2- Unzip the file "mann1.zip" to get folder "mann1" then copy it directly into your device internal storage NOT the SD card. Put the the whole folder not the files inside.
===
3- Put SupeSU.apk into your SD card
===
If the rooted boot worked fine, restart your device in the normal mode (NOT the recovery or bootloader), and type the following commands one by one:
Code:
adb devices
adb root
adb shell
[I][COLOR="Red"]Now you supposed to see your root like that[/COLOR][/I]
[COLOR="Blue"][email protected]:/ #[/COLOR]
[COLOR="Red"]complete the commands in the shell:[/COLOR]
mount -o rw,remount /system
cat sdcard/mann1/busybox > /system/bin/busybox
cat /sdcard/mann1/su > /system/xbin/su
cat /sdcard/mann1/su > /system/xbin/daemonsu
cat /sdcard/mann1/su > /system/xbin/sugote
cat /system/bin/sh > /system/xbin/sugote-mksh
chown 0.1000 /system/bin/busybox
chmod 0755 /system/bin/busybox
chown 0.0 /system/xbin/su
chmod 0755 /system/xbin/su
chown 0.0 /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chown 0.0 /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chown 0.0 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d
pm install /sdcard/mann1/superuser.apk
am start -a android.intent.action.MAIN -n
eu.chainfire.supersu/.MainActivity >/dev/null
reboot
If everything run smoothly after rebooting you will find the SuperSu icon installed.
Do NOT run it now
Before that go to your SD card and install SuperSU.apk, from the device not via pc, then restart.
Now your device should be completely rooted , if SUperSu asked to updated via google, reinstall it OR let it updates by google play site.

Categories

Resources