Database Info

[HOW-TO] change your french orange dream firmware by a custom one...

Thanks to :
• JF for his recovery.img
• Arisme for the analysis of the dumped french orange firmware and his tools to customize the firmware
1) The tools
Unzip all the tools on one folder on your hard disk (c:\ModifDream for example)
SDK here :
http://developer.android.com/sdk/download.html?v=android-sdk-windows-1.1_r1.zip
fastboot here :
http://member.america.htc.com/download/web_materials/ADP/fastboot.exe
other tools here :
http://www.megaupload.com/?d=XMGZSYOM
You must copy thoses files on the microSD card :
- boot-root.img
- systemDEV.img
- dataDEV.img
- libhtc_ril.so (we need this patch from the original french firmware for a compatibility with the radio)
- wlan.ko (we need this patch from the original french firmware for a compatibility with wifi)
- busybox.asc
- trout-keypad-v3-franch-azerty.kcm.bin (with the ' and the ")
2) Backup of your dream.
We will use the JF recovery :
- Shutdown the dream
- plug it to the PC
- put your dream in fastboot mode
- On the PC, do :
cd\ModifAndroid
fastboot boot recoveryJF.img
- On the dream keyboard do ALT+B to backup your dream
- At the end of the backup do BACK+HOME to reboot
Ok the backup is done (NANDROID folder on your microSD card
3) Patch the boot for permanent root access throw adb
Put the dream in fastboot mode
Plug it to the PC
- On the PC, do :
cd\ModifAndroid
fastboot boot recoveryBoot.img
After the startup of your dream, do on the PC :
adb shell
mount /dev/block/mmcblk0p1 /sdcard
flash_image boot /sdcard/boot-root.img
reboot
4)Install of the new firmware and of all the patchs (ADP firmware)
Put the Dream in fastboot mode and plug it to the PC
- On the PC do :
cd\ModifAndroid
fastboot boot recovery-unyaffs.img
After the startup, do on the PC
adb shell
mount /dev/block/mmcblk0p1 /sdcard
mkdir /tmp/system
mkdir /tmp/data
mount /dev/block/mtdblock3 /tmp/system
mount /dev/block/mtdblock5 /tmp/data
cd /tmp/system
rm -rf * (dont be afraid by the error)
unyaffs /sdcard/systemDEV.img
cd /tmp/data
rm -rf * (dont be afraid by the error)
unyaffs /sdcard/dataDEV.img
cp /sdcard/libhtc_ril.so /tmp/system/lib/
cp /sdcard/wlan.ko /tmp/system/lib/modules/
cp /sdcard/trout-keypad-v3-franch-azerty.kcm.bin /tmp/system/usr/keychars/
cp /sdcard/trout-keypad-v3-franch-azerty.kcm.bin /tmp/system/usr/keychars/trout-keypad-v3.kcm.bin
cp /sdcard/trout-keypad-v3-franch-azerty.kcm.bin /tmp/system/usr/keychars/trout-keypad.kcm.bin
Do on the dream keyboatd ALT + W
After the startup, do on the PC (to have root and busibox) :
cd\ModifAndroid
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
dd if=/sdcard/busybox.asc of=/system/bin/busybox
chmod 4755 /system/bin/busybox
cd /system/bin/
busybox cp -s busybox cp
busybox sh
cat sh > su
chmod 4755 su
reboot
OK, that is finished!
After the startup you will have to sign in with your gmail account. To do it you have first to create an APN (MENU and then NEW APN)
5)Back to the orange firmware
If you need to come back to the orginal situtation, just copy system.img and data.img from your NANDROID backup at the root of your microSD Card and copy and rename the boot.img from this backup to boot-orange.img at the root of the card.
Put the dream in fastboot mode
Plug it to the PC
- On the PC do :
cd\ModifAndroid
fastboot boot recovery-unyaffs.img
After the startup, do on the PC :
adb shell
mount /dev/block/mmcblk0p1 /sdcard
mkdir /tmp/system
mkdir /tmp/data
mount /dev/block/mtdblock3 /tmp/system
mount /dev/block/mtdblock5 /tmp/data
cd /tmp/system
rm –rf * (don't be afraid by the error)
unyaffs /sdcard/system.img
cd /tmp/data
rm –rf * (don't be afraid by the error)
unyaffs /sdcard/data.img
On the dream keyboard do ALT + W
Put again the dream in fastboot mode
On the PC do
cd\ModifAndroid
fastboot boot recoveryBoot.img
After the startup do on the PC :
adb shell
mount /dev/block/mmcblk0p1 /sdcard
flash_image boot /sdcard/boot-orange.img
reboot
REMARK
You will find in the zip a tool : unyaffs. With this tool you can extract on your PC image like system.img or data.img. This is really interesting if you need some patch from the orginal firmware. Maybe italian users can use it to get their keyboard layout, update it (with an hex editor) and replace the french layout in this exemple with the italian one
To use this tool : unyaffs system.img or unyaffs data.img with your image on the same folder fo unyaffs

Ah ouais ca a l'air sport comme méthode.
Oh it's seems pretty hard to do .

Are you sure it's working ?????
Vraiment impressionnant... j'espère que cela fonctionne bien
Tous mes espoirs d'avoir un téléphone Dream fonctionnel vont devenir réalité...
Enorme...
Really impressing I hope that it works well
All my hopes to have a functional telephone Dream are going to become reality
Enormous...

Note that it looks complicated because all steps are shown to give a headstart to other modders.
You can build a simple update.zip from those instructions if you want the most "interesting" parts being
a) gaining root by booting an image
b) using unyaffs to restore the original firmware, since no official update.zip exists for it so far

Really Great Job...
I have try this rom...
It's pretty good... YOU'RE THE KING OF THE ANDROID FRENCH PHONE
I have some problems with synchro (no 3G) and the img files are in English...
Could you help me to put this in French ???
Thanks in advance.
Best Regards

ADP firmware is an German/English firmware. You won't find a french firmware with a good google sync...
For the 3G have you created the new APN as described ?
For the APN :
name : orange
apn : orange
user : orange
pwd : orange
MCC : 208
MNC : 01
type : default

It's working....
Do you think it will be possible to made my own Firmware making a build with the French translations ???
Thanks in advance

You could translate the free (i.e. non Google) apps. But it's going to be a lot of work, when Cupcake is coming in a few months.

After i hacked my dream, following all the steps, my calendar app shuts down all the time...so i went back to orange firmware and my calendar is ok, but no synchro as it's expected to do with this firmware.
Anyone has same issue ? ideas ?
Oh, and before i went back to orange firmware, IM app and voice search were activated oO
Anyway, good job guys !

Problem
That finnish but I got a problem I am block by google account, my sim card is not reconize. I was maybe forget an step, but wich one ?
please help me
thx for that job

have you created the new apn as described ?

yes
yes I create orange apn like describe but It never ask me pin code ;-(

hum hum.. have you done the line cp /sdcard/libhtc_ril.so ...

I think yes, because I just copy/paste all command line, so that one were paste (I hope), if not what can I do ?
thx

i am surfing with my dream so it is not easy to write a specific process... so do again the step 4 and, please. do it line after line to be sure that all is ok...

ok I will try now to do step 4 and tell you if it is good. Or I will go on orange rom
thx geek78

is it normal
/tmp/system # rm –rf *
rm: cannot remove '–rf': No such file or directory
rm: app: is a directory
rm: bin: is a directory
rm: etc: is a directory
rm: fonts: is a directory
rm: framework: is a directory
rm: lib: is a directory
rm: lost+found: is a directory
rm: media: is a directory
rm: sounds: is a directory
rm: usr: is a directory
rm: xbin: is a directory
/tmp/system #

no, do again rm -rf * (dont forget the space after -rf)

yes It is what I do (I just copy and paste) so I keep space, but you said don't worry with error ;-)
The error is maybe here because all the process is ok, just an error in this command line.
I retry
thx

It smelt very good, you are a king, ****ing process, who do what you ask him ;-)
It first view all is good, I just need to do some configuration.
Thanks geek78 and have good night
See yu

modify vold.fstab in rfs file

Hello, I have an i9003 which only has external memory (sd card), I removed the nand as it was faulty and caused the phone to loop restart and stuff.
I had to root it and modify the vold.fstab file to make use of the SD card as internal phone memory. My question is: is there a way to modify the content of the vold.fstab directly in the .rfs image before flashing? I read mounting on linux there are problems with permissions and this is a read only file.

chriz74 said:
Hello, I have an i9003 which only has external memory (sd card), I removed the nand as it was faulty and caused the phone to loop restart and stuff.
I had to root it and modify the vold.fstab file to make use of the SD card as internal phone memory. My question is: is there a way to modify the content of the vold.fstab directly in the .rfs image before flashing? I read mounting on linux there are problems with permissions and this is a read only file.
Click to expand...
Click to collapse
sudo mkdir /mnt/sys
sudo mount -o loop system.rfs /mnt/sys
sudo gedit /mnt/sys/etc/vold.fstab
sudo umount /mnt/sys

ganeshbiyer said:
sudo mkdir /mnt/sys
sudo mount -o loop system.rfs /mnt/sys
sudo gedit /mnt/sys/etc/vold.fstab
sudo umount /mnt/sys
Click to expand...
Click to collapse
Thanks, the problem is that I get an error writing to file. I believe vold.fstab is read only. Solution?
** (gedit:2599): WARNING **: Hit unhandled case 0 (Error writing to file: Input/output error) in parse_error.
I got this error logged in as root.

chriz74 said:
Thanks, the problem is that I get an error writing to file. I believe vold.fstab is read only. Solution?
** (gedit:2599): WARNING **: Hit unhandled case 0 (Error writing to file: Input/output error) in parse_error.
I got this error logged in as root.
Click to expand...
Click to collapse
Don't login as root.
use sudo command instead.

the result is the same with sudo. The system can't write file to rfs.

[Q] Question about RO /system/bin

Hello XDA need your support.I am trying to fix a bootloop but I cannot run the ADB SHELL - exec '/system/bin/sh' failed: No such file or directory (2) - when I try to insert the sh file with adb push it sends me Cannot Copy "Read-Only" system
I know I can unlock the /system with the shell codes but my urgent question is how I can insert this sh file because android cant find it
And the most important is then the ADB SHELL is needed for fastboot commands
Any Ideas ?

Guide to replace kinguser with supersu

hey guys,
get this files then, you will find MRW folder inside the zip file , put that mrw in internal memory card
• Send the extracted folder "mrw" to the internal storage of your device and make sure that this folder contains 4 files
• Open Terminal emulator and type :
Su
• Allow root permission
• Type :
sh /sdcard/mrw/root.sh
(put space after sh , then /sdcard/mrw/root.sh)
• It might display some error ignore these errors, at the end it will launch supersu or open supersu manually.
• Update SU binary normal, then reboot
ALSO DELETE THE KINGUSER.APK ( superuser.apk) from /system/app manually, before reboot
and its done , i checked nicely , its working awesome
link for replacer files :- https://drive.google.com/file/d/0B7I...ew?usp=sharing
dont flash these files , (method working on lollipop 5.0, work on kitkat , jellybean also )
CREDIT : 1) Chainfire for awesome SUPERSU ( PLS DONATE HIM AND SUPPORT HIM> http://www.chainfire.eu/),
2) edwuard
3)ME
4) MY PARENTS and WIFE CLAIRE

File Missing
It's show to check the URL. Have you deleted the file ?

nope , the link is working , still i attach files here ,
vasansrine said:
It's show to check the URL. Have you deleted the file ?
Click to expand...
Click to collapse
check the attachment

is it safe
I am runing on android lollipop xolo prime please tell me is it safe
---------- Post added at 08:02 AM ---------- Previous post was at 07:20 AM ----------
So so so thanks I am trying to this this for year but now I have done with your amaging post I can't believe I so fear to doing this but successing I am so happy now thank thank you very much

Interesting. What do the am and pm commands do?

Seems to have worked on my Amazon Fire (KFFOWI/Ford), but I may have left Kingroot installed before rebooting

com.kingroot.kinguser:services
This method works. I tried it myself. The downside is that Kingroot will leave residual files and services even after you have enforced SUPERSU and updated it's binaries. Anyone know where I could locate KSysService and com.kingroot.kinguser:service?

Success on KFFOWI 5.1.2 via adb on Linux
I just tried this on KFFOWI with 5.1.2. It worked, but there were errors output by the script and I don't know if that's ok. It appears to be ok though. Here's what I did (on Linux):
Code:
$ unzip mrw.zip
$ cd mrw
$ adb shell
[email protected] $ cd /storage/emulated/legacy
[email protected] $ mkdir mrw
[email protected] $ exit
$ adb push busybox /storage/emulated/legacy/mrw/busybox
$ adb push root.sh /storage/emulated/legacy/mrw/root.sh
$ adb push su /storage/emulated/legacy/mrw/su
$ adb push Superuser.apk /storage/emulated/legacy/mrw/Superuser.apk
$ adb shell
[email protected] $ su
[email protected] # sh /storage/emulated/legacy/mrw/root.sh
The output looks like this (aparently errors are ok?)
Code:
---------------------------------------
---------- Made By : BEINGTEJAS -------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
Failure [DELETE_FAILED_INTERNAL_ERROR]
Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
rm: /system/app/Kinguser.apk: No such file or directory
Failure [DELETE_FAILED_INTERNAL_ERROR]
rm: /data/data/com.kingroot.RushRoot: No such file or directory
rm: /data/data/com.kingroot.master: No such file or directory
chattr: stat /system/bin/ddexe: No such file or directory
rm: /system/bin/ddexe: No such file or directory
chattr: stat /system/bin/install-recovery.sh-ku.bak: No such file or directory
rm: /system/bin/install-recovery.sh-ku.bak: No such file or directory
pkg: /sdcard/mrw/superuser.apk
Success
chattr: stat /system/usr/iku/isu: No such file or directory
rm: /system/usr/iku: No such file or directory
rm: /dev/reportroot: No such file or directory
chattr: stat /system/etc/install_recovery.sh: No such file or directory
rm: /system/app/Kinguser: No such file or directory
rm: /data/data-lib/king: No such file or directory
Then I followed through the install of SuperSU on the device, using the "normal" option and allowing it to remove the other SU that it detected. Finally, I rebooted the device and performed a quick test:
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # exit
[email protected]:/ $ exit
The SuperSU icon is on available, the KingUser one is gone. Accessing root goes through SuperSU so it looks ok. If any of those errors pose a problem though, let me know!

when i type su and enter, I get a message "Daemon is stop" and i cant get root access, i have tried to reinstall emulator, re-allow kinguser root, but nothing works, busybox is installed

Edit: NVM, got it working with the SuperTool
The script managed to remove Kingroot, but SuperSU normal binary installation still fails. Plus, the Rootchecker now says that the root is not properly installed.
Should I install Kingroot again in order to gain root and try SuperSU again?

Problems with ADB push and --sync+

I'm attempting to use adb's push command on Windows 10 in order to transfer files from my PC to my Oneplus 9 Pro. I installed adb by following the instructions here. When I attempt to do the file transfer, I receive a large number of error message for some of the files, that all look like this:
Code:
E:\>adb push Music /sdcard/Music
cannot lstat 'Music/??????': No such file or directory
cannot lstat 'Music/????? ??....flac': No such file or directory
cannot lstat 'Music/????? ????????? - ??????? ?????? (2011)': No such file or directory
cannot lstat 'Music/????????? ??????? ??? - 1990 - ??? ?? ??????': No such file or directory
cannot lstat 'Music/???? ? ????????.mp3': No such file or directory
cannot lstat 'Music/??? ?????? ?????.flac': No such file or directory
cannot lstat 'Music/??????? ????.mp3': No such file or directory
cannot lstat 'Music/??????': No such file or directory
cannot lstat 'Music/?????? ????.flac': No such file or directory
cannot lstat 'Music/?? ?????? ???? ??? ? ? ????? ?? ??????.mp3': No such file or directory
cannot lstat 'Music/??, ???????.mp3': No such file or directory
I have used adb with these exact same files before, when I was still running Manjaro, with no issues or error messages such as these, so I'm fairly confident the issue is not with the files themselves. Even more bizarrely, when I attempt to use the --sync command, it doesn't even recognize it as a command:
Code:
E:\>adb push --sync Music /sdcard/Music
cannot stat '--sync': No such file or directory
I've attempted to uninstall and reinstall adb, but the issues persists in spite of that. What possible solutions are there to this?

Youn have to name the fullpathname of folder Music on PC.

xXx yYy said:
Youn have to name the fullpathname of folder Music on PC.
Click to expand...
Click to collapse
I do have the full path name, Music folder is located in E:\Music and I open Command Prompt to E:\ drive. I also know it's the correct path name because some of the files do transfer, but a large number have errors as discussed above.