Develop Bugs

[Q] Root fail help

First I searched for a help thread and this is my last resort.
this morning i tried to root my evo using this guide http://forum.xda-developers.com/showthread.php?t=838448
log >
It failed
------------ AutoRoot.bat Begin - v2.2 - Sun 02/06/2011 17:09:19.48
------------
Params=1'' 2'' 3'' 4'' 5'' 6''
Phone SN is HT0CWHL07773
Checking for ADB...
PLEN='1' PSTATE='device' RETURNTO='start' STEP='start'
PING ADB State Changed '1' out of '1'. ADB State is 'device' expected 'device'
Found the phone connected as 'device'.
Checking MTD configuration...
dev: size erasesize name
mtd0: 00c00000 00040000 "wimax"
mtd1: 00100000 00040000 "misc"
mtd2: 00480000 00040000 "recovery"
mtd3: 00340000 00040000 "boot"
mtd4: 15e00000 00040000 "system"
mtd5: 0a000000 00040000 "cache"
mtd6: 1aa00000 00040000 "userdata"
'check.bat mtd' returned 'new'
MTD data being saved for phone 'HT0CWHL07773'
'dev: size erasesize name mtd0: 00c00000 00040000 "wimax" mtd1:
00100000 00040000 "misc" mtd2: 00480000 00040000 "recovery" mtd3:
00340000 00040000 "boot" mtd4: 15e00000 00040000 "system" mtd5:
0a000000 00040000 "cache" mtd6: 1aa00000 00040000 "userdata" '
Firmware version '3.70.651.1'
Version Major '3'
Version Minor '70'
Battery is at 100 percent.
Checking for root...
UID is 'shell'
Installing exploit...
pkg: /data/local/tmp/AutoRoot.apk
Success
1364 KB/s (767044 bytes in 0.549s)
adb: Product directory not specified; use -p or define ANDROID_PRODUCT_OUT
Sending Intent...
Starting: Intent { act=android.intent.action.MAIN
cmp=com.autoroot.getroot/.getroot }
Checking for root...
UID is 'shell'
Checking for root...
UID is 'Got Root!'
Checking for needed files...
Pushing res\flash_image to /data/local/flash_image...
1375 KB/s (76044 bytes in 0.054s)
Pushing res\mtd-eng.img to /sdcard/mtd-eng.img...
2490 KB/s (655360 bytes in 0.257s)
Pushing res\URFSOFF.zip to /sdcard/URFSOff.zip...
2929 KB/s (225014 bytes in 0.075s)
Pushing res\URFSON.zip to /sdcard/URFSOn.zip...
2447 KB/s (225551 bytes in 0.090s)
Pushing res\PC36IMG_UD.zip to /sdcard/PC36IMG.zip...
1577 KB/s (179274182 bytes in 110.963s)
Flashing misc partition...
Rebooting in to bootloader...
Verifying bootloader status...
hBoot version '2.10.0001'
Version Major '2'
Version Minor '10'
Bootloader shows Firmware version '1.17.651.1'
Version Major '1'
Version Minor '17'
hbpreupdate set at '11'
Security is 'on'
Waiting on operator to flash the PC36IMG.zip and reboot into the recovery.
Checking for ADB...
PLEN='1250' PSTATE='recovery' RETURNTO='b2recovery' STEP='recoveryboot'
PING ADB State Changed '1' out of '1250'. ADB State is 'fastboot'
expected 'recovery'
PING ADB State Changed '357' out of '1250'. ADB State is
'disconnected' expected 'recovery'
PING ADB State Changed '362' out of '1250'. ADB State is 'recovery'
expected 'recovery'
Found the phone connected as 'recovery'.
Found the Recovery, proceeding to makenandroid...
Pushing amon_ra_1.8-mod to /...
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
Recovery type is 'stock'
adb server is out of date. killing...
* daemon started successfully *
- exec '/system/bin/sh' failed: No such file or directory (2) -
phone showes s-on
hboot-2.10.0001
radio-2.15.00.11.19
try to boot get the evo red ! screen
I know now that I need to run the ruu to restore it. so I fond this http://forum.xda-developers.com/showthread.php?t=874251
what do I do with these files how do I "run the ruu"
bricked phone here please help, my searches are sending me in circles. if someone could point me in the right diretion that would be much appreciated

run the ruu.exe on your computer and should work from there

i dont have a ruu.exe does this "ruu.exe" have to be version specific?
further more where can i find a ruu.exe, and what mode should the phone be in to use the ruu.exe?

Hetrochromia said:
i dont have a ruu.exe does this "ruu.exe" have to be version specific?
further more where can i find a ruu.exe, and what mode should the phone be in to use the ruu.exe?
Click to expand...
Click to collapse
You can find the ruu in the same post that you downloaded that from. It should have given you instructions on exactly what to do when it failed as well. You just download it and run it.

ok thanks
fond the ruu here "cant post forum rules"
RUU to restore 3.70.651.1
turned phone on with power vol down
selected hboot USB
phone connects to pc
device manager shows "android bootloader interface"
run ruu.exe
error 170 can not find phone
tried this next
turned phone on with power vol down
selected recovery
phone shows red !
phone connects to pc
device manager shows "MY HTC"
run ruu.exe
error 170 can not find phone
any input?

dont select recovery just run it like that

When in the bootloader select fastboot, it should then change from hboot in blue to fastboot usb in red. Once you see that it should recognize your phone.
It looks like something was interfering with it talking to your phone, pdanet and apps like that can cause it but usually it's easier to just try with a different computer.
Sent from my PC36100 using XDA App

thanks that did it
now im going to do a fresh install of windows 7 on a laptop and retry the root

[q] can one of you gurues explain this to me plese

I AM TRYING TO MAKE A FOLDER. TO MAKE A CUSTOM SPLASH SCREEN BUT I DON'T KNOW HOW TO COMPLETE THIS STEP....[Open a command or terminal window and CD to your nbimg folder.
Type in the following command: nbimg -F splash1.bmp -w 480 -h 800
If successful, nbimg should have created an nb file called 'splash1.bmp.nb'.
Rename 'splash1.bmp.nb' to 'splash1.img'.]... I HAVE THE "NBIMG" FOLDER. AND MY CONVRTED IMAGE. I JUST DON'T KNOW TO "CD" TO IT OR WHEN TO TYPE IN THE COMMAND AFTER THAT TO COMBINE THE TWO.....USING COMMAND LINE IS LIKE FRENCH TO ME... PLEASE HELP..

mbancroft41 said:
I AM TRYING TO MAKE A FOLDER. TO MAKE A CUSTOM SPLASH SCREEN BUT I DON'T KNOW HOW TO COMPLETE THIS STEP....[Open a command or terminal window and CD to your nbimg folder.
Type in the following command: nbimg -F splash1.bmp -w 480 -h 800
If successful, nbimg should have created an nb file called 'splash1.bmp.nb'.
Rename 'splash1.bmp.nb' to 'splash1.img'.]... I HAVE THE "NBIMG" FOLDER. AND MY CONVRTED IMAGE. I JUST DON'T KNOW TO "CD" TO IT OR WHEN TO TYPE IN THE COMMAND AFTER THAT TO COMBINE THE TWO.....USING COMMAND LINE IS LIKE FRENCH TO ME... PLEASE HELP..
Click to expand...
Click to collapse
Ok I see no one has answered this so I'll try to take a stab at it.
I've never made a custom splash screen, however, I know my way around a command prompt. I'm assuming that your nbimg folder is on the root of your C:/ drive correct?
If that is so then in a fresh command prompt and type "cd c:\nbimg" now you should be in that folder. If its in a different folder like..idk.. programs files. then you would type cd c:\program files\nbimg, ya see?
Now that your in that folder type "nbimg -F splash1.bmp -w 480 -h 800". Hope that helps out some, if there is anyone else that can shed some more light please take this by the horns.

no actually its in my user \down load folder. should i save it to the root of my c: drive. ....or i would have to figure out what the command for my "downloads" file is ... but I think i'll move it to the root. cause you already gave me the command for that thanks........and yes your the first one to answer on three different fourms i have the same question in..... so thanks so much for your help...

mbancroft41 said:
no actually its in my user \down load folder. should i save it to the root of my c: drive. ....or i would have to figure out what the command for my "downloads" file is ... but I think i'll move it to the root. cause you already gave me the command for that thanks........and yes your the first one to answer on three different fourms i have the same question in..... so thanks so much for your help...
Click to expand...
Click to collapse
Your very welcome. If you can move it to the root of the C: drive then Id do it.
If not then right click in your nbimg folder and click properties and look at your location (ex. C:\users\download). Now, just CD-change directory to that folder with the addition of \nbimg. so it'd look like "C:\users\download\nbimg". Its a little more work but it will give you a little more command prompt experience.

ok... now that it is explained.. it sounds simple.. thanks again

ok.. command line read: c:\users\my name> .. I typed in about three different things but i got it to read: "c:\>" with out the quotations of course by typing in. " cd c:\ "..... but cant get it to the file.....when i type "nbimg" it says " 'nbimg' is not recognized as an internal command opperate program or batch file........ i have relocated the said file to the root of my C drive like u suggested...any ideas????????

ok played around for a while and got it i think.... I found out how to type command in right.. and it spit a whole bunch of stuff back to me.....to bad you cant copy and paste from cmd line window.. cause i sure aint typing all that.. thanks for your help. alot of thanks been waiting two days to get some kinda answer....

mbancroft41 said:
ok played around for a while and got it i think.... I found out how to type command in right.. and it spit a whole bunch of stuff back to me.....to bad you cant copy and paste from cmd line window.. cause i sure aint typing all that.. thanks for your help. alot of thanks been waiting two days to get some kinda answer....
Click to expand...
Click to collapse
You can copy and paste my friend!!! Right click and click paste

c:\nbimg>nbimg -f splash1.bmp -w480 -h800
=== nbimg v1.1
=== Convert NB <--> BMP splash screens
=== (c)2008 Pau Oliva - pof @ xda-developers
nbimg: unknown option -- f
Usage: nbimg -F file.[nb|bmp]
Mandatory arguments:
-F <filename> Filename to convert.
If the extension is BMP it will be converted to NB.
If the extension is NB it will be converted to BMP.
Optional arguments:
-w <width> Image width in pixels. If not specified will be autodetec
.
-h <height> Image height in pixels. If not specified will be autodete
d.
-t <pattern> Manually specify the padding pattern (usually 0 or 255).
-p <size> Manually specify the padding size.
-n Do not add HTC splash signature to NB file.
-s Output smartphone format.
NBH arguments: (only when converting from BMP to NBH)
-D <model_id> Generate NBH with specified Model ID (mandatory)
-S <chunksize> NBH SignMaxChunkSize (64 or 1024)
-T <type> NBH header type, this is typically 0x600 or 0x601
awasome it was just done different then the normal right click and right click paste.so the info it sent back to me is it saying its missing something or did it create the file

sounds like it completed

[Discounted] [ONSCREEN KEYBOARD] [20-oct-2012] Linux on your Kindle Fire

hi!
This is my manual for how to install linux on your Kindle Fire.
there are some some steps you should to do.
1. Assure you have working adb and fastboot.
2. Download the follwing files: kernel (http://narod.ru/disk/59236733001.2e2d29e2c7bd762bd285ddf22a9c3fc6/boot1.img.html), bootloader (http://www.mediafire.com/?l6aaqgsdkiksfw0), and linux rootfs (new image has been uploaded.[url]http://depositfiles.com/files/mkpjrbixe
) , COTR recovery (http://narod.ru/disk/59880845001.8639567518823dcc1a9e4d51161ad75b/recovery_CTOR.img.html)
3. unpack these files and place them to adb & fastboot directory
4. reboot your kindle into fastboot.
5. boot CWM recovery by fastboot boot recovery_COTR.img
6.it's very important step. be careful with your sdcard partition.
now you'll resize it and make partition for Linux installation.
type the following in command line (windows/msdos) (terminal (linux/mac)):
~$: adb shell
then parted /dev/block/mmcblk0
then resize
then 12
then 2309 (start?)
then 5680 (end?) (it takes some time to resize partition)
then mkpart 13 5680 7597
then mkpart 14 7597 7609
then type quit
then mke2fs -T ext4 /dev/block/mmcblk0p13
then parted /dev/block/mmcblk0 name 14 linuxboot
then parted /dev/block/mmcblk0 name 13 linux
after doing this do the following:
mount sdcard storage to computer
now you must format sdcard partition.
in Windows select "Format" in main menu.
then place deb.img file to storage (it also called sdcard)
after copying debian image select safely remove in tray, but don't disconnect your kindle from computer.
on the screen tap Unmount button.
then type in command line: adb shell
then cd /mnt/sdcard/
then dd if=/deb.img of=/dev/block/mmcblk0p13
it took me about 20 minutes.
after that reboot into fastboot and type the following:
fastboot flash linuxboot boot1.img
fastboot flash bootloader u-boot.bin
7. all done.
8. enjoy
videos of how-to:
http://www.youtube.com/watch?edit=vd&v=4DBELK0cCpI
http://www.youtube.com/watch?edit=vd&v=F-IjFgBVHVM
there are images and video:
http://www.youtube.com/watch?v=NEXxSxhLoOI
{
"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"
}
Thanks to:
Hascode
Seishuku
And others

If it's plug and play I would love to try it out.
Sent from my MB855 using xda premium

rbeavers said:
If it's plug and play I would love to try it out.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
what does you mean by p`n`p?

rbeavers said:
If it's plug and play I would love to try it out.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
you should follow guide by seishuku to install this. i simply solved some causes for myself. i think that my vision of this debian setup is rather good.
i also working on touchscreen bug and wifi.
later i`ll add suspending by power button and ability to managing sound volume and screen brightness

I was downloading it. But it looks kind of hard to install
Sent from my Amazon Kindle Fire using XDA Premium HD app

Very good job .
Envoyé depuis mon GT-I9000 avec Tapatalk

partition layout
link to download deb.img: http://depositfiles.com/files/aq1vtxbr0
after downloading my image you should make the same partition layout.
simply reboot your kindle in fastboot and boot it from CWM recovery (it contains program parted( partition manager). you should know how to use it).
after repartitioning select "reboot into fastboot" in reboot options in "reboot options"
and flash debian partition with my image (i called mine as "linux"(flash command is: fastboot flash linux deb.img))).
also you must install the seishuku's bootloader http://www.mediafire.com/?l6aaqgsdkiksfw0
and make empty partition to flash kernel (it must be named linuxboot link to download is:http://upwap.ru/2675690) (partition number for debian should be 13!!!!)
you MUST flash bootloader ONLY after flashing debian image!!!
because every when you flash bootloder you update partition scheme in bootloader configuration.
MacBook-Aroslav:~ yaroslav$ adb shell
~ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 11.0MB 10.5MB dkernel
4 11.0MB 212MB 201MB ext4 dfs
5 212MB 229MB 16.8MB recovery
6 229MB 296MB 67.1MB ext4 backup
7 296MB 307MB 10.5MB boot
8 307MB 312MB 5243kB ext4 splash
9 312MB 849MB 537MB ext4 system
10 849MB 2041MB 1192MB ext4 userdata
11 2041MB 2309MB 268MB ext4 cache
12 2309MB 5680MB 3371MB fat32 media msftres
13 5680MB 7597MB 1917MB ext2 linux
14 7597MB 7609MB 12.0MB linuxboot
(parted)
after doing all this you`ll get fully working deabian tabletop
installing is easy)
enjoy)
just for fun.

a little later i`ll make a detailed guide how to install this if you have stock kindle.
it'll be simple, so beginners colud follow my future guide and install debian and make dualboot for android and debian

a little later i`ll make a detailed guide how to install this if you have stock kindle.
it'll be simple, so beginners colud follow my future guide and install debian and make dualboot for android and debian
I will continue to fix bugs and add features and improve performance

Please feel free to ask any questions about this topic

Someone needs to try booting Chromium on it!
BTW, you still need OTG, correct?

Jessical said:
Someone needs to try booting Chromium on it!
BTW, you still need OTG, correct?
Click to expand...
Click to collapse
yes of course.
you still need OTG. but. but. i`m working on wifi and touchscreen. also i want not to use OTG with kbd and mouse.

He would be nice if you could make a video about how to install it
Sent from my Amazon Kindle Fire using XDA Premium HD app

jsisaev said:
what does you mean by p`n`p?
Click to expand...
Click to collapse
I can flash it, and it works ;')
Sent from my MB855 using xda premium

rbeavers said:
I can flash it, and it works ;')
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
you can flash this using dd or fastboot. i recommend you to reboot in recovery, place deb.img to sdcard and do the folowing: open a terminal. do adb shell (your kindle must be in recovery). then change current directory to /sdcard and enter this: dd if=deb.img of=/dev/block/mmcblk0p13

Do you need a keyboard or can you use the on-screen one?

FroyoShark said:
Do you need a keyboard or can you use the on-screen one?
Click to expand...
Click to collapse
i'm searching onscreen keyboard.
at once i got touchscreen working correctly.

I`ll upload new image tomorrow

After installing it on my Fire, I have a few questions, One: Do you have the mouse bugout fixed? Two: Am I going to have to download a big IMG again? And three: Can you make a DSL port after this one is perfected?
Also, Can you fix it to support OTG please?

Starzie said:
After installing it on my Fire, I have a few questions, One: Do you have the mouse bugout fixed? Two: Am I going to have to download a big IMG again? And three: Can you make a DSL port after this one is perfected?
Also, Can you fix it to support OTG please?
Click to expand...
Click to collapse
otg is supported.
at once you may not to download new image. just do the following:
in file /usr/shrare/X11/xorg.conf.d/10-evdev.conf replace last section with the following:
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Option "SwapAxes" "yes"
Option "InvertY" "yes"
#Option "InvertX" "no"
Option "Calibration" "0 3950 0 2370"
#Option "IgnoreRelativeAxes" "yes"
Driver "evdev"
EndSection
after that reboot.
all done. you now have correctly working touchscreen

P6 state clarify and develop and brainstorming(recovery, boot, fastboot, kitchen)

Hi!
As I promiss, here is the thread for clarify and brainstorming for Ascend P6 avaible development.
First of all, clarify the bootloader and phone status.
Our phone is an "emulator". It is not running Android natively. It's just emulated, Android is running in QEMU. Similar like the real Android SDK.
Huawei patched the QEMU for running Android our MTK chipset.
Huawei take a tricky step. He did the RSA5 encrypt to not able to write any files to the partition system, without a digital signature of Huawei.
Xloader check this signature and if it missing, you won't be able to update. (We are s*cking @ here...)
Bootloader Unlock
It means, you able to send boot image and recovery img via fastboot. I think, our fastboot haven't got some instructions and permission.
DON'T FORGET YOU ARE IN AN EMULATED STATE!!!
If Huawei "unlock the bootloader", 2 way to get this( I think):
1. Modified fastboot, to able flash boot image via fastboot like this:
Code:
fastboot flash boot boot.img/recovery.img
or
Code:
flash_image boot boot.img/recovery.img
2. Ignore the whole system signature check. (which is best for we and able to running native Android but it won't be happen)
1 is a big step forward to custom kernel/Custom rom/CM/AOSP.(Of course second is bigger)
I'm just praying first at this moment.
Partitions.
ONE REAL partition are in the MTK NAND chip. Called: hi_mci.1.
The other partitions are NOT REAL! They are emulated. Just like you running LINUX in Virtualbox or something like this.
Those partitions:
/sdcard vfat /dev/block/platform/hi_mci.1/by-name/sdcard
/system ext4 /dev/block/platform/hi_mci.1/by-name/system
/cache ext4 /dev/block/platform/hi_mci.1/by-name/cache
/data ext4 /dev/block/platform/hi_mci.1/by-name/userdata length=-16384
/misc emmc /dev/block/platform/hi_mci.1/by-name/misc
/boot emmc /dev/block/platform/hi_mci.1/by-name/boot
/recovery emmc /dev/block/platform/hi_mci.1/by-name/recovery
/cust ext4 /dev/block/platform/hi_mci.1/by-name/cust
/uboot emmc /dev/block/platform/hi_mci.1/by-name/uboot
/splash2 ext4 /dev/block/platform/hi_mci.1/by-name/splash2
/modem/modem_image ext4 /dev/block/platform/hi_mci.1/by-name/modemimage
/usb vfat /dev/block/sda
For native Android, we need to repartition the hole NAND chip. I think, it is impossible.
BOOT
Android boot system need boot.img for booting. Which contain the kernel and some system specific files.
This is formatting the device own emulated partition. It contains the ramdisks, etc.
We have an Huaewei Update Extractor, which can be unpack the update.app.
We get boot.img, recovery.img. Good.
Our bootloader is UNLOCKED from the begining. I think, our fastboot haven't got some instructions and permission.
With dsiXDA Kitchen you able to unpack boot and recovery.img, modify it and repack.
Just after the B118 update, I hope Huawei unlock this feature. It is a good point to start.
The new driver for ADB/fastboot
To be continued...
And feel free to contribute!
Take a test and build boot.img from b122. Two modification in:
1. ro.secure=0
2. ro.debuggable=1
Is this mean, you get true root acces to everywhere.
See in attachment.
Of course, it won't be able to to push via fastboot, because the limitations our fastboot.

Hi!
After new firmware B118, nothing will be changed , because secure lock loader was not removed !
You can not push boot.img by fastboot , but you can easy flashed a new kernel by this command :
# dd if=/sdcard/boot.img of=/dev/block/mmcblk0p12
Click to expand...
Click to collapse
and your device will never boot cause you need a signed image !
I was able to flash by this command only the stock kernel !
Good luck !

There appears to be a signed flashable CWM recovery.img with scatter file for the ascend mate over at needrom - I know the P6 is pretty much the same device save the screen size so maybe it can be of some use ?
(assuming it it genuine and works).
Needs an app called SP Flash Tool which is for MTK chipsets.
http://www.needrom.com/mobile/ascend-mate-mt1-u06-s4ui/

lonespeaker said:
There appears to be a signed flashable CWM recovery.img with scatter file for the ascend mate over at needrom - I know the P6 is pretty much the same device save the screen size so maybe it can be of some use ?
(assuming it it genuine and works).
Needs an app called SP Flash Tool which is for MTK chipsets.
http://www.needrom.com/mobile/ascend-mate-mt1-u06-s4ui/
Click to expand...
Click to collapse
Hi!
Yes, you are right , seem they managed to signed a recovery.img to be flashed on partition /recovery !
As long as the loader is locked ( This phone is secure lock state ! ) I do not think it helps us....

surdu_petru said:
Hi!
Yes, you are right , seem they managed to signed a recovery.img to be flashed on partition /recovery !
As long as the loader is locked ( This phone is secure lock state ! ) I do not think it helps us....
Click to expand...
Click to collapse
Yeah maybe you're right, but a bit odd releasing what appears to be an asop based rom with a signed recovery and signed boot.img rom and no way to actually install it. maybe one day...

surdu_petru
What do you think about not removing the hole security, just removing the boot image security. Loader not check the boot image signature. You able to run custom kernel. But not able to change recovery. Only for boot.img. And with this and your method(Blueandroid), we can get custom roms like AOSP. And every time we can go back to stock with our stock recovery.

bukest said:
surdu_petru
What do you think about not removing the hole security, just removing the boot image security. Loader not check the boot image signature. You able to run custom kernel. But not able to change recovery. Only for boot.img. And with this and your method(Blueandroid), we can get custom roms like AOSP. And every time we can go back to stock with our stock recovery.
Click to expand...
Click to collapse
Nop, loader also check boot image signature , because I can not flash a custom kernel ( boot.img ) !
Edit :
I think, I'm not 100% sure, xloader partition is check signature for all partitions on boot !

Who have courage to try this?
Finding some usefull info.
How should our device look like(NAND)
xloader => /dev/block/mmcblk0p1 /first stage bootloader
round => /dev/block/mmcblk0p2
nvme => /dev/block/mmcblk0p3
misc => /dev/block/mmcblk0p4
splash => /dev/block/mmcblk0p5
oeminfo => /dev/block/mmcblk0p6
reserved => /dev/block/mmcblk0p7 /It’s the Huawei digital signature of the boot partition, checked by the bootloader.
reserved2 => /dev/block/mmcblk0p8
splash2 => /dev/block/mmcblk0p9
recovery2 => /dev/block/mmcblk0p10
recovery => /dev/block/mmcblk0p11 /stock recovery
boot => /dev/block/mmcblk0p12 /kernel+ramdisk
modemimage => /dev/block/mmcblk0p13
modemnvm1 => /dev/block/mmcblk0p14
modemnvm2 => /dev/block/mmcblk0p15
system => /dev/block/mmcblk0p16
cache => /dev/block/mmcblk0p17
cust => /dev/block/mmcblk0p18
userdata => /dev/block/mmcblk0p19
mmcblk0boot0
This is the second stage bootloader. Huawei in his UPDATE.APP files call this partition as FASTBOOT!!!!
So, someone in this forum sad, B118 FASTBOOT.IMG is the different size. It's true! B118 FASTBOOT.IMG size is smaller then B122.
I think, we found the trick!
Huawei not unlock the Xloader(1st low-level loader), just unlock the second stage loader which will allow to flash and boot custom boot.img and recovery.img!
Who have any courage, to do this:
1. Place attached FASTBOOT.IMG to sdcard/
2. Connect phone in MTP
3. Enable USB Debug.
4. CMD on PC with administrator privileges
5. Navigate to the folder which contain adb.exe
6. type: ADB.exe shell
7. type su
8.
Code:
# dd if=/sdcard/fastboot.img of=/dev/block/mmcblk0boot0
with fastboot.img from extract from Chinese B118! File attached.
If am I right, after this we are able to use it on any version(unicom/mobile) and version of firmware(B111,B112,B119,B122, etc...)
If anything went wrong, you need to reflash the hole UPDATE.APP. So, I recommend to place update.app file to sdcard/dload/
Maybe if some of you think is real, I will do!

delete

bukest said:
So, someone in this forum sad, B118 FASTBOOT.IMG is the different size. It's true! B118 FASTBOOT.IMG size is smaller then B122.
I think, we found the trick!
Huawei not unlock the Xloader(1st low-level loader), just unlock the second stage loader which will allow to flash and boot custom boot.img and recovery.img!
Click to expand...
Click to collapse
You can not flash a custom kernel on B118 ! Take a look here !

surdu_petru said:
You can not flash a custom kernel on B118 ! Take a look here !
Click to expand...
Click to collapse
And what boot.img he had flashed?
What happend when boot.img needed to signed but not just Huawei. Bootloader allow every digital signed boot.img(public key or something like this)?
Not parse the signature with one stored in the OEMINFO or RESERVED. Just only need to contain a digital signature in the front of the file, which mean, you are little bit better than a hobby weekend engineer.

bukest said:
And what boot.img he had flashed?
What happend when boot.img needed to signed but not just Huawei. Bootloader allow every digital signed boot.img(public key or something like this)?
Not parse the signature with one stored in the OEMINFO or RESERVED. Just only need to contain a digital signature in the front of the file, which mean, you are little bit better than a hobby weekend engineer.
Click to expand...
Click to collapse
Do you already signed a custom kernel with a private key ( not from Huawei ofcourse ), and your device was able to boot ?

surdu_petru said:
Do you already signed a custom kernel with a private key ( not from Huawei ofcourse ), and your device was able to boot ?
Click to expand...
Click to collapse
NOT. If you read a few post back, you will see it's just an idea. But I want to walk around fully all around aspect and all possibility.
Another idea.
What about Huawei check you are on P6-U06 or P6-U00?
And with B118 fastboot.img only flashed if you are on U00. Think about this.
But what happend if we push it manually...

Someone on P6-U00(Originally)!
Extract the boot.img from B118. Make a small modification. Flashed via fastboot. And if it doesn't work, we are able to write down, Bootloader is not unlocked.
Edited:
Attached for this an edited boot.img for B118.
Of course, NOT signed! just unpack original, edit(default.prop) and repack.

Bad news!
Permission denied!
[email protected]:/ $ dd if=/sdcard/fastboot.img of=/dev/block/mmcblk0boot0
dd if=/sdcard/fastboot.img of=/dev/block/mmcblk0boot0
/dev/block/mmcblk0boot0: cannot open for write: Permission denied
Click to expand...
Click to collapse
{
"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"
}

bukest said:
Permission denied!
View attachment 2431245
Click to expand...
Click to collapse
In the way you use the command, this answer " Permission denied!" is 100% correct !
Please, use "#" instead "$" ! Good luck !

surdu_petru said:
In the way you use the command, this answer " Permission denied!" is 100% correct !
Please, use "#" instead "$" ! Good luck !
Click to expand...
Click to collapse
Ohhhh, stupid me...
Forgot to get su!
Thanks surdu.
But after a little research I find some other info with FASTBOOT partition. I will write down later at the day(have go to work at the moment).

WARNING!!!!
Do not use that method!!!
mmcblk0boot0 partition maybe contain some other information!!!
Unique FOR YOUR DEVICE!!!
Just like wifi MAC adress, etc!
And on a running system, partition around 2MB!
First backup your current boot0 partition!
# dd if=/dev/block/mmcblk0boot0 of=/sdcard/mmcblkboot0.img
It means, if we push the 500k image to 2mb partition directly, you may damage 1,5MB data.
I think, with update.app method, you just install the image file, not pushing directly!

IDEA
If we backup xloader partition:
# dd if=/dev/mmcblk0p1 of=/sdcard/xloader.img
Edit it in hex to remove digital signature check.
Push back and pray...
If it works, you have totally unlock phone, but if not YOUR PHONE TOTALLY DEAD!

hex-editing the xloader.img ...
I also like to live dangerously

Android Smart TV Box M6 - AML8726-MX - G18REF - XBMC Native Linux - Hints

Hi guys,
I don't have access to ROM forum yet so I posted a thread here. My intention is to clarify the process of flashing native Linux with XBMC to this box.
The reference thread is:
http://forum.xda-developers.com/showthread.php?t=2418029
What started my doubts was the information on checking the MTD layout before proceeding with the update. I have checked mine via ssh and it is different from what is posted on the above thread.
Mine is:
Code:
dev: size erasesize name
mtd0: 00800000 00200000 "bootloader"
mtd1: 00400000 00200000 "ubootenv"
mtd2: 00800000 00200000 "logo"
mtd3: 00800000 00200000 "aml_logo"
mtd4: 00800000 00200000 "recovery"
mtd5: 00800000 00200000 "boot"
mtd6: 40600000 00200000 "system"
mtd7: 20000000 00200000 "cache"
mtd8: 10000000 00200000 "backup"
mtd9: 18c600000 00200000 "userdata"
which is same as the author's of this thread:
http://forum.xda-developers.com/showthread.php?t=2492843
I have also checked the contents of the zip file from the first cited thread (the "updater-script" file in particular) and it looks like the only MTD partitions that are modified are: boot, system and logo.
I want to build the system myself from sources using what is already available on the Internet (probably using croniccorey's repo).
That being said, my questions are:
1. Is it safe to update the box to Native Linux? Are mtd0 (bootloader) and mtd4 (recovery) partitions left intact during update? If so, there should be no risk of bricking the device.
2. How is booting to recovery done? What I have already found is that the detection of the pressed-during-power-on button is done in the bootloader phase. So if the bootloader stays at mtd0 of the NAND flash and I accidentaly erease that partition, I brick the device with no chance to get to recovery mode. Am I right?
3. Does AM8726-MX try to boot from other than default devices if NAND boot fails? If so, It would be possible to copy U-boot to SD card and start from there. I can't find the processor's datasheet neither the schematics of G18ref board.
4. Is there a way to find the offset of a particular MTD partition in running system with no source knowledge? Using cat /proc/mtd I only get partition sizes. Partitions may follow each other with unused space in between, so if my real MTD layout differs from what I have in the updated system, I may have troubles (e.x. I may overwrite the recovery partition writing to boot partition)
5. From the config file of G18ref board:
https://github.com/CoreTech-Develop...ter/arch/arm/configs/meson6_g18_mx2_defconfig
and the board configuration file:
https://github.com/CoreTech-Development/mx-common/blob/master/arch/arm/mach-meson6/board-m6g18.c
I can see that some NOR flash is used (CONFIG_AMLOGIC_SPI_NOR=y). If so, what about the fact that my bootloader has a partition on NAND (mtd0). Or maybe mtd0 and mtd1 belong to NOR flash and the rest (mtd2..9) are NAND partitions?
I am confused. Would appreciate help.
Regards, ak_dev.

So far I have found the answers for:
4. Is there a way to find the offset of a particular MTD partition in running system with no source knowledge? Using cat /proc/mtd I only get partition sizes. Partitions may follow each other with unused space in between, so if my real MTD layout differs from what I have in the updated system, I may have troubles (e.x. I may overwrite the recovery partition writing to boot partition)
Click to expand...
Click to collapse
Simply by finding it in dmesg, for example:
Code:
dmesg | grep -C 20 mtd
I have tried finding the info in /sys, but it looks like there is no offset information there
5. From the config file of G18ref board:
and the board configuration file:
I can see that some NOR flash is used (CONFIG_AMLOGIC_SPI_NOR=y). If so, what about the fact that my bootloader has a partition on NAND (mtd0). Or maybe mtd0 and mtd1 belong to NOR flash and the rest (mtd2..9) are NAND partitions?
Click to expand...
Click to collapse
No signs of SPI NOR flash in the system yet...
From dmesg, I can see that mtd0 and mtd1 are created on same NAND as other partitions.
But another question arised.
dmesg reports:
Code:
[ [email protected]] Creating 9 MTD partitions on "B revision NAND 8GiB MT29F64G08CBABA":
(...)
[ [email protected]] 0x000002400000-0x000002c00000 : "recovery"
(...)
But in the board-m6g18.c file there is a definition for recovery partition:
Code:
{
.name = "recovery",
.offset = 64*SZ_1M+40*SZ_1M,
.size = 8*SZ_1M,
}
64*SZ_1M+40*SZ_1M = 0x6800000
Why the offsets don't match? Wrong board config file? Don't think so...
And still, I can't find answers to other questions...