Related
First off, This is not a release, it is a work in progress
As we haven't heard anything back in a while from any of the Devs, and I find myself with some free time, I'm gonna take a shot at porting CWM from the sources of the Epic4g version as well as the SGS version that had better keymappings.
If anyone who still has Clockwork installed could look under the advanced options and try using the key mapping feature to give me the keymaps of the hard buttons, that would be greatly appreciated, as I'm back on a stock recovery.
sduvick said:
First off, This is not a release, it is a work in progress
As we haven't heard anything back in a while from any of the Devs, and I find myself with some free time, I'm gonna take a shot at porting CWM from the sources of the Epic4g version as well as the SGS version that had better keymappings.
If anyone who still has Clockwork installed could look under the advanced options and try using the key mapping feature to give me the keymaps of the hard buttons, that would be greatly appreciated, as I'm back on a stock recovery.
Click to expand...
Click to collapse
i will have more time later, but i tried this real quick, and for each key i press, it gives a number. do you need the # for every key?
yeah, that's what i'm looking for. if you can give me a list in the format:
<button name> : <Number>
that would be greatly helpful. Those numbers are what map to keys in Clockwork/android, so all I have to do is change some numbers in the build and remap a partition in fstab.
sduvick said:
yeah, that's what i'm looking for. if you can give me a list in the format:
<button name> : <Number>
that would be greatly helpful. Those numbers are what map to keys in Clockwork/android, so all I have to do is change some numbers in the build and remap a partition in fstab.
Click to expand...
Click to collapse
ok, unfortunately I can't get into CWM anymore, after a few failed Odin attempts. would have to successfully Odin and then reroot.
Sent from my HTC Vision
Ill be more than happy to help get things moving...
1 - 16
2 - 17
3 - 25
4 - 33
5 - 41
6 - 49
7 - 2
8 - 10
9 - 18
0 - 67
q - 68
w - 65
e - 3
r - 11
t - 19
y - 27
u - 35
i - 43
o - 51
p - 59
a - 20
s - 28
d - 36
f - 44
g - 52
h - 60
j - 5
k - 13
l - 21
DEL -4
SEARCH -45
z - 53
x - 61
c - 6
v - 14
b - 22
n - 30
m - 38
SMILE - 54
ENTER - 29
L SHIFT - 15
ALT - 23
@ - 56
, - 48
SPACE - 63
. - 64
? - 32
MICROPHONE - 40
R SHIFT - 46
VOL UP - 42
VOL DN - 58
JUMP KEY - 7
HOME - 8
MENU - 66
BACK - 34
CAMERA - 39
POWER - 26
TRACKBALL (push) - 50
Also, if it helps, this is a cheat sheet to navigate with current buttons
BACK - VOL DN
UP - CAMERA
DOWN -6
SELECT - MIC
Hope this helps
great work, this should be what I need!
In trying to build, my laptop is failing to build otatools... apparently it can't build on x86 for whatever reason. I have however changed the keymaps according to @jahnbodah's testing, to what should work with vol being up and down, power or touchpad as accept, and the back button as back. I also remapped the /sdcard partition in recovery.fstab to where ours is (according to my phone) as /dev/block/vold/179:1
I will attach the build files (still labeled as epic4g) if anyone who has a good build environment (Devs, anyone?) can compile this for us?
This is not a working flashable release, don't even try to flash this.
sduvick said:
In trying to build, my laptop is failing to build otatools... apparently it can't build on x86 for whatever reason. I have however changed the keymaps according to @jahnbodah's testing, to what should work with vol being up and down, power or touchpad as accept, and the back button as back. I also remapped the /sdcard partition in recovery.fstab to where ours is (according to my phone) as /dev/block/vold/179:1
I will attach the build files (still labeled as epic4g) if anyone who has a good build environment (Devs, anyone?) can compile this for us?
This is not a working flashable release, don't even try to flash this.
Click to expand...
Click to collapse
If you tell me how to do what is needed I will be more than happy to do so, or point me to some online tutorials.
What software is needed? I am running win7 x64
Awesome Job man!! Glad to see some real dev work going on! sduvick....your my hero!
We're not anywhere yet, it still needs someone with a 64bit computer to compile it, as after some testing, as I thought, I can't run a 64bit vm on a 32bit computer, even though that's what koush told me to do haha.
how would I build this? I have my 64-bit system set up to compile Cyanogen and AOSP, I'm not really schooled in how to set up a build, I just follwed the instructions specifically for Cyanogen and AOSP.
feel free to pm me if you have time and are able to advise.
Sent from my HTC Vision
I tried to compile this ( for a friend ) but it isnt working because the vendors are not setup for the epic4g
I can try to compile one shortly here... Just waiting to sync up with the sources to compile the otatools since I'm running this in a VM...
I really appreciate all the people jumping in on this! Hopefully between all of us we can get it figured out?
Ok, so it took longer since I had other priorities, but I was able to compile a recovery img successfully for the sk4g..
I've taken the build files that sduvick created and modified the vendor on them so it would compile properly..
If anyone is brave enough, maybe we can test this?! I would test it, however it is my girl's phone and don't have it with me at the moment...
Here's the DL links for the recovery zip, recovery.img, and the build files that I used to compile it..
Recovery zip (signed w/SignApk):
Download link removed
Recovery zip (unsigned):
Download link removed
Build Files:
Download link removed
Recovery img:
Download link removed
I would try it, but I can't risk a brick
Sent from my SGH-T839 using XDA App
I am currently soft bricked so I don't have too much to lose, but I can only get into stock recovery so I guess it would have to be signed just right? otherwise, could I perhaps Odin the tar file I extracted from the build files.tar.gz?
Sent from my HTC Vision
I looked around other recoveries and as far as I can tell the stock recovery doesn't require the zip to be signed..
brenix said:
I looked around other recoveries and as far as I can tell the stock recovery doesn't require the zip to be signed..
Click to expand...
Click to collapse
ah ok, i tried flashing it and did get an error, "signature verification failed".... same thing happened with the signed ROM from the other thread here.
Hmm... Ok maybe I was wrong about the signing... Here is the same zip, but signed using SignApk... maybe this will work?? Thanks for giving it a shot yogi2010
Download link removed
Does anyone have this tablet? I can't find this tablet on the website.
I want to know if this tablet can be upgraded to v3.0 or higher when ics comes on CyanogenMod?
Technical Specifications
Weight: 426 gr
Dimensions: 202 x 140 x 11 mm
CPU Samsung Cortex A8 1.0 GHZ
OS: Android 2.2
WiFi 802.11 b/g/n
Bluetooth
Capacitive Multi Touch Screen
7" TFT-LCD Display
SDRAM 512 MB
4 GB Internal Memory
Micro SD/SDHC slot (Up to 32 GB)
G-Sensor
Mini-HDMI port out
Mini-USB port
Microphone
Adobe Flash Compatible
Camera: 2 MP
2 Stereo Speakers
I've the exact same question about the Cyanogen Mod.
Also, I would like to know if it's possible to perform a COMPLETE back up (root or nand backup) without this mod. (without nandroid backup)
The device is also released as the BQ DaVinci. That company released a firmware update to Gingerbread a couple of days ago.
However, I'm a bit reluctant to install it, because it'll change the splash screen and who knows what else.
The update procedure seems to be different from other devices: you have to put a folder called SDFUSE on the root of the SD-card and reboot. The folder contains these files:
SDFUSE
--> ramdisk-uboot.img
--> sdfuse.txt
--> system.img
--> u-boot.bin
--> zImage
Does anyone have any idea on how to reverse-assemble these files (i.e. extract or replace boot splash screen,...)
Mahalaleel said:
I've the exact same question about the Cyanogen Mod.
Also, I would like to know if it's possible to perform a COMPLETE back up (root or nand backup) without this mod. (without nandroid backup)
The device is also released as the BQ DaVinci. That company released a firmware update to Gingerbread a couple of days ago.
However, I'm a bit reluctant to install it, because it'll change the splash screen and who knows what else.
The update procedure seems to be different from other devices: you have to put a folder called SDFUSE on the root of the SD-card and reboot. The folder contains these files:
SDFUSE
--> ramdisk-uboot.img
--> sdfuse.txt
--> system.img
--> u-boot.bin
--> zImage
Does anyone have any idea on how to reverse-assemble these files (i.e. extract or replace boot splash screen,...)
Click to expand...
Click to collapse
There is not much help here..
I think we can forget an answer to our question
From experience I can say 2.3.4 DaVinci upgrade works fine on BeBook Live, even Angry Birds Space is now playable!
Indeed so, I discovered that as well.
But... still no possibility to upgrade to a custom ROM apparently?
AGSO Somx 7 GS20 has same format for their ROMs. In my understanding:
zImage - linux kernel compressed
u-boot-config - ???
ramdisk-uboot.img - ram disk image for loading
system.img - image of /system disk
To convert other ROMs into this format you have to get kernel and ramdisk images from boot.img, then make system partition image (create virtual disk with same size, make filesystem on it, move all /system files to the disk).
After some researching:
zImage - linux kernel gzip-compressed (just kernel, with empty initramfs inside) with built-in unpacker code at start
u-boot-config.bin - u-boot loader and/or its config (perhaps, stage 2 loader as S5PC110 has two-stage loader)
ramdisk-uboot.img - initramfs image (initramfs archive by cpio, then gz [output name "ramdisk"], then mkimage from u-boot distribution)
system.img - image of /system disk (ext4, not compressed)
BQ put ICS (Android 4.0) online for the BQ DaVinci, works fine also (booting takes a bit). Definitely a good idea if you still are using the device, Skype and so on works smooth!
See Post #2 for current known stock partition parameters for various devices. Your contributions for missing devices are welcome and appreciated. Cheers!
Introduction
This guide / reference aims to be a complete article on customizing, resizing and/or re-ordering the internal partition layout on most (any?) Android MTD-based device. I have seen many questions around the various forums on how to get more internal data so I thought I'd share my developments. Hopefully this will become a valuable resource for kernel builders/hackers.
The guide is especially valuable (and, in the case of my kernel builds, originally designed for) the Xperia 2011 line, but from what I know it could be applied to nearly any Android device where kernel source/flashing is possible.
I would like to gather stock partition information for various devices and place them into Post #2. If you can at least give me your Partition Info from ATAG (see "Gathering information" section), I can create a reference for all kernel developers. Thank you!
Requirements
Android SDK
Ability to build a kernel (this guide does not teach that)
Ability to flash a kernel (unlocked bootloader, etc)
Bootloader which exposes Partition info via ATAG on startup (see "Gathering information" section)
Device which uses MTD Partition Map (Don't know how to check this, I think most Android devices do anyway)
Warning
As far as I know, following this guide and using precise calculation that you double and triple check before flashing will not result in a hard brick - however I can not guarantee it. Some devices may have "obscure" partition maps or some "protected" sectors for one reason or another, and modifying these *may* result in either a hard-brick (unlikely) or a permanent inability to restore your device to 100% stock (very likely) for warranty and/or DRM purposes. You have been warned. I/we/anyone may not be held accountable for any of these events should they occur, for you are doing this at your own risk and with your own responsibility.
Gathering information
The first thing you'll want to do for the sake of accuracy is to flash to a 100% stock firmware. In the case of Xperia 2011 devices, flash the latest stock FTF for your device.
With the stock firmware now installed, the second thing you will need to do is to flash a custom kernel that is rooted and has busybox installed. In most cases, a CM7/9/10 kernel will do nicely.
Power-off your device. Execute the following command from shell/console, and then press enter:
Code:
adb wait-for-device && adb shell dmesg
After pressing enter, the console will wait at the prompt as intended. Now, power on your device and immediately plug in the USB cable. I assume the ADB drivers are already installed.
Shortly (5-15 seconds) you should see a mass output from the kernel followed by a return to your shell prompt. If you don't, either your kernel or bootloader does not support it. Try a different kernel. If you still don't, then sorry but I think we can't do it for your device.
Scroll right to the top of the dmesg output, you should see something similar to this:
Code:
<6>[ 0.000000] Initializing cgroup subsys cpu
<5>[ 0.000000] Linux version 2.6.32.9-KRsH ([email protected], Linaro 4.7) (gcc version Linaro 4.6.2 20111004) #8 PREEMPT Thu Oct 25 15:57:27 EST 2012
<4>[ 0.000000] CPU: ARMv7 Processor [511f00f2] revision 2 (ARMv7), cr=10c53c7d
<4>[ 0.000000] CPU: VIPT nonaliasing data cache, VIVT ASID tagged instruction cache
<4>[ 0.000000] Machine: zeus
<6>[ 0.000000] Partition (from atag) system -- Offset:2e4 Size:9c4
<6>[ 0.000000] Partition (from atag) userdata -- Offset:ca8 Size:be0
<6>[ 0.000000] Partition (from atag) cache -- Offset:1cb4 Size:32c
<6>[ 0.000000] Partition (from atag) appslog -- Offset:1888 Size:42c
<4>[ 0.000000] Memory policy: ECC disabled, Data cache writeback
...see those "Partition (from atag)" lines? That's what we need! Copy this information down and move on to the next section.
Additional verification and hidden partitions (optional)
As far as I know, this is only possible with Xperia 2011 devices. If you know of a method for other devices, please let me know.
We can additionally verify the ATAG information and map extra "hidden" partitions such as boot (kernel) by examining the SIN files inside an FTF. I will assume that you know how to use Flashtool already as I won't go into much detail here.
First, we need to enable the development features of Flashtool. In the program folder, open "config.properties" and edit/add the line like so:
Code:
devfeatures=yes
Next, extract your stock FTF bundle with any ol' ZIP extractor, load Flashtool, and select "Tools" > "SIN Editor", and open a particular SIN file that you want to verify/unhide. In this example, we will open system.sin. The "Partition Info" field is what we want. Behold:
Code:
STOCK SIN:
system: 0400000001000080E4020000C4090000
-- --|------||------|
| | | |
type? (elf/yaffs) _/ | | \____ byte-reversed size
| |
unknown ____/ \____________ byte-reversed offset
The second last 8-bytes are the offset and the last 8-bytes are the size. By "byte-reversed" I mean that you read each byte from end to beginning, but not swap the bytes themselves. Thus the size above, reading "C4090000" is actually "000009C4". And as you can see, this matches 100% to our ATAG of 9c4 for system size. Correct sir! Additionally, the offset of "E4020000" > reversed to "000002E4" also matches.
So now, we can open "kernel.sin" and do the same, because we also want to partition "boot" (why not?). In this device (Xperia Play/Xperia Neo L), kernel.sin gives us 03000000220000808002000064000000 which means that the size is 64 and the offset is 280.
Calculations
From the partition info via ATAG, we can now build "stock" mtdparts information to apply to our kernel. Using the example(s) above, we can now build this information:
Code:
system : [email protected]
userdata : [email protected]
cache : [email protected]
appslog : [email protected]
boot : [email protected]
Note the syntax of size@offset. Next, we must convert the hex values to decimal, then multiply by 128 (I do not know if 128 is the same multiplier for all devices, please double check and let me know). This will give us the exact sizes and offsets in kilobytes.
Code:
system : [email protected]
userdata : [email protected]
cache : [email protected]
appslog : [email protected]
boot : [email protected]
Alright, so that is a 100% stock partition map for this device - except we also have the boot (kernel) mapped now too. Here is a (crappy) visual representation of it:
Code:
reserved | boot | /system | /data | appslog | /cache |
first 80MB | 12.5MB | 312.5MB | 380MB | 133.5MB | 101.5MB |
Note: Not to scale :)
You may have noticed that the order we (and ATAG) lists the partitions in does not match the actual order of the partitions. It is quite important to retain the order of the partitions as specified in ATAG, because that's the order they will be mapped in. I.e. system will remain mtdblock0 and cache will remain mtdblock2. Any extra partitions should always go after these defaults.
Formatting for kernel
To specify the mtdparts parameter for the kernel to use is trivial. Doing this will over-ride the ATAG map (from bootloader) and everything in the system - including Recovery - will see your map from the kernel. Search your default config file in your kernel for the value "CONFIG_CMDLINE" and you should find a value like this :
Code:
CONFIG_CMDLINE="console=ttyMSM2,115200n8 androidboot.hardware=semc"
Using the information we have above about our partition map, we add a new parameter here with "mtdparts=msm_nand:". The syntax is as follows:
Code:
mtdparts=msm_nand:[size]@[offset](name){,[size]@[offset](name)}{...}
Remember that we converted our size and offsets to kilobytes (for better readibility) so we need to specify size unit of k. The new parameter, from our above examples, becomes this:
Code:
mtdparts=msm_nand:[email protected](system),[email protected](userdata),[email protected](cache),[email protected](boot)
Don't forget to retain the order! And so, our full line looks like this:
Code:
CONFIG_CMDLINE="console=ttyMSM2,115200n8 androidboot.hardware=semc mtdparts=msm_nand:[email protected](system),[email protected](userdata),[email protected](cache),[email protected](boot)"
NOTE: Depending on your kernel, you may also need to enable the following line in your config:
Code:
CONFIG_MTD_CMDLINE_PARTS=y
And we're all done. If you build your kernel now, you will be able to mount (or at least dd from) the appslog and boot partitions.
Resizing partitions
This is somewhat trivial, the most difficult part is probably over - but this step can be tedious, albeit not very complicated. Anybody with an above average IQ would have already figured this out - we simply change the size of one partition and adjust the offsets of it's following partitions to accommodate for the change. Here is one good example that I use for the MIUI ROM for the Xperia Play and Neo L, compared to the stock examples shown above:
Code:
mtdparts=msm_nand:[email protected](system),[email protected](userdata),[email protected](cache),[email protected](boot)
...and a visual representation of this new map:
Code:
reserved | boot | /system | /data |/cache|
first 80MB | 12.5MB | 280MB | 639MB | 8MB |
Note: Not to scale :)
Hopefully that's enough to make sense. Remember to verify your modified partitions. This can easily be done by adding the size+offset of a partition, giving the offset of the next partition. E.g. in this mod, userdata ends at 1036288 (654848+381440) which matches the offset for the next partition - cache.
Troubleshooting/Recovering from modified partitions
In some cases, your new kernel may not boot. A common issue is that the kernel logo will show, and the device will shortly reboot (kernel bootloop). This can be solved by formatting your partitions with fastboot after flashing the new kernel, usually system and userdata are all that is needed:
Code:
fastboot format system
fastboot format userdata
If you wish to return to a stock partition layout, sometimes flashing a non-modified kernel is not enough. You may get stuck on kernel logo even after formatting system and userdata. In this case, flashing a stock Firmware and setting your phone back to scratch should result in a 100% original device. But if your phone is still bricked, sorry but it's not my fault. You probably did something wrong.
#####
OK, that's the guide done for now. Any questions or suggestions on the guide, please let me know! Also, refer to post #2 for some stock partition map reference.
Finding Stock Partition Info For Your Device
Three methods:
Most reliable - See the section "Gathering info" above to get it from ATAG
Only shows size without offset - do "cat /proc/mtd" from adb shell. Can be used to test if you're on stock partitions or not, or to verify partition is big enough for update ZIP's (with sed/grep).
Xperia 2011 Only - Examine SIN header as outlined above. This method is difficult to determine mtd block order but I'm 99% sure the order is same for all Xperia 2011 devices (system=mtd0, userdata=mtd1, cache=mtd2).
Stock Partition Parameters for Various Devices
Xperia 2011 Range:
Code:
[B]anzu (Arc) (LT15) (HDPI):[/B]
(03) kernel - [email protected] ([email protected]) (unmapped)
(04) system - [email protected] ([email protected])
(05) amss - [email protected] ([email protected]) (unmapped)
(06) amss_fs - [email protected] ([email protected]) (unmapped)
(08) adsp - [email protected] ([email protected]) (unmapped)
(09) userdata - [email protected] ([email protected])
(10) vendor - [email protected] ([email protected])
(0B) fota0 - [email protected] ([email protected]) (unmapped)
(0C) fota1 - [email protected] ([email protected]) (unmapped)
mtdparts=msm_nand:[email protected](system),[email protected](userdata),[email protected](cache),[email protected](appslog),[email protected](amss),[email protected](amss_fs),[email protected](adsp),[email protected](fota0),[email protected](fota1),[email protected](boot)
[B]ayame (Arc S) (LT18) (HDPI):[/B]
(03) kernel - [email protected] ([email protected]) (unmapped)
(04) system - [email protected] ([email protected])
\ this is odd, there is 2048k unallocated between boot and system (SEMC made a mistake?)
(05) amss - [email protected] ([email protected]) (unmapped)
(06) amss_fs - [email protected] ([email protected]) (unmapped)
(08) adsp - [email protected] ([email protected]) (unmapped)
(09) userdata - [email protected] ([email protected])
(10) vendor - none
(0B) fota0 - [email protected] ([email protected]) (unmapped)
(0C) fota1 - [email protected] ([email protected]) (unmapped)
mtdparts=msm_nand:[email protected](system),[email protected](userdata),[email protected](cache),[email protected](boot),[email protected](amss),[email protected](amss_fs),[email protected](adsp),[email protected](fota0),[email protected](fota1)
[B]haida (Neo V) (MT11) (HDPI):[/B]
[I]Same as ayame (Arc S) (LT18)[/I]
[B]hallon (Neo) (MT15) (HDPI):[/B]
[I]Same as anzu (Arc) (LT15)[/I]
[B]iyokan (Pro) (MK16) (HDPI):[/B]
[I]Same as ayame (Arc S) (LT18)[/I]
[B]mango (Mini Pro) (SK17) (MDPI):[/B]
??
[B]satsuma (Active) (ST17) (MDPI):[/B]
??
[B]smultron (Mini) (ST15) (MDPI):[/B]
??
[B]urushi (Ray) (ST18) (HDPI):[/B]
??
[B]phoenix (Neo L) (MT25) (HDPI):[/B]
[I]Same as anzu (Arc) (LT15)[/I]
[B]zeus/zeusc (Play) (R800) (HDPI):[/B]
[I]Same as anzu (Arc) (LT15)[/I]
R800a (and probably i/at, but not x) has unallocated vendor partition. Needs one-time flash of Vendor-enabled FTF (e.g. phoenix or anzu) to allocate it otherwise the vendor map will present I/O errors.
Reserved again (just in case)
Thanks for the info. You have used the same for MIUI for Neo L and Play and we have good internel memory..
Thanks for sharing
Very nice work mate! (Especially for using ATAGs...)
I just started the related thread:
"[DEV][REF] El Grande Partition Table Reference"
To collect detailed partition info from various devices...
E:V:A said:
Very nice work mate! (Especially for using ATAGs...)
I just started the related thread:
"[DEV][REF] El Grande Partition Table Reference"
To collect detailed partition info from various devices...
Click to expand...
Click to collapse
Heh nice! Yours looks a bit more hardcore than mine, I've never used any of those tools
I started this guide so I can port kernels to various devices for Xperia 2011 range, and also to help other devs appeal the users who crave for more internal partition space. But so far, none of these people seem to have the patience to lend a hand with gathering data
Xperia Arc (anzu - LT15i_4.1.B.0.587_Generic Global World)
Code:
SIN name HEX [email protected] DEC (in k) SIZE
amss.sin: ??? E4 @ 10 29184 @ 2048 28Mb
amss_fs_anzu.sin: ??? 68 @ F4 13312 @ 31232 13Mb
adsp.sin: ??? 6C @ 15C 13824 @ 44544 13Mb
fota0.sin: ??? 5C @ 1C8 11776 @ 58368 11Mb
fota1.sin: ??? 5C @ 224 11776 @ 70144 11Mb
kernel.sin: boot 64 @ 280 12800 @ 81920 12Mb
system.sin: system 9C4 @ 2E4 320000 @ 94720 312Mb
userdata.sin: userdata BE0 @ CA8 389120 @ 414720 380Mb
vendor.sin: vendor 42C @ 1888 136704 @ 803840 133Mb
I've been talking to wedgess about the use of the cache partition... been poking around and he pointed me in your direction... so, here we go! :highfive:
[NUT] said:
Xperia Arc (anzu - LT15i_4.1.B.0.587_Generic Global World)
Code:
SIN name HEX [email protected] DEC (in k) SIZE
amss.sin: ??? E4 @ 10 29184 @ 2048 28Mb
amss_fs_anzu.sin: ??? 68 @ F4 13312 @ 31232 13Mb
adsp.sin: ??? 6C @ 15C 13824 @ 44544 13Mb
fota0.sin: ??? 5C @ 1C8 11776 @ 58368 11Mb
fota1.sin: ??? 5C @ 224 11776 @ 70144 11Mb
kernel.sin: boot 64 @ 280 12800 @ 81920 12Mb
system.sin: system 9C4 @ 2E4 320000 @ 94720 312Mb
userdata.sin: userdata BE0 @ CA8 389120 @ 414720 380Mb
vendor.sin: vendor 42C @ 1888 136704 @ 803840 133Mb
I've been talking to wedgess about the use of the cache partition... been poking around and he pointed me in your direction... so, here we go! :highfive:
Click to expand...
Click to collapse
Awesome, thanks for the partition info. I *hope* to get all Xperia 2011 device info so I can build Turbo Kernel for all. From what I can see, Arc partitions are identical to Play and Neo L. So maybe all Xperia 2011 devices are the same.
Since the cache partition is not an FTF file, it goes after vendor - so offset would be 940544 (kb). The size I am not sure and might vary per device. /proc/mtd (or /proc/partitions) should tell you.
Also, you can remove vendor partition - because all ROM's just mount it to the folder at /system/vendor so any vendor files you need can go into system partition, and then you can remap/reclaim vendor.
CosmicDan said:
Awesome, thanks for the partition info. I *hope* to get all Xperia 2011 device info so I can build Turbo Kernel for all. From what I can see, Arc partitions are identical to Play and Neo L. So maybe all Xperia 2011 devices are the same.
Since the cache partition is not an FTF file, it goes after vendor - so offset would be 940544 (kb). The size I am not sure and might vary per device. /proc/mtd (or /proc/partitions) should tell you.
Also, you can remove vendor partition - because all ROM's just mount it to the folder at /system/vendor so any vendor files you need can go into system partition, and then you can remap/reclaim vendor.
Click to expand...
Click to collapse
Might be different for the Arc S (ayame) ... i'm looking into the official firmware release now to confirm... but as i used a FTF for my LT15i to gain size on my userdata a while back this is what i get from the dmesg ATAG lines...
Code:
system 9C4 @ 2E4 320000 @ 94720 312Mb
cache 32C @ FA4 103936 @ 512512 101Mb
userdata D20 @ 12D0 430080 @ 616448 420Mb
Seeing cache between system and userdata ... but no vendor partition anymore
I also notice my endpoint at 918Mb of 1000MB (as sony states in their whitepaper: 1GB) that would be inside the phone ... lost space or do you know a reason perhaps?
[NUT] said:
Might be different for the Arc S (ayame) ... i'm looking into the official firmware release now to confirm... but as i used a FTF for my LT15i to gain size on my userdata a while back this is what i get from the dmesg ATAG lines...
Code:
system 9C4 @ 2E4 320000 @ 94720 312Mb
cache 32C @ FA4 103936 @ 512512 101Mb
userdata D20 @ 12D0 430080 @ 616448 420Mb
Seeing cache between system and userdata ... but no vendor partition anymore
I also notice my endpoint at 918Mb of 1000MB (as sony states in their whitepaper: 1GB) that would be inside the phone ... lost space or do you know a reason perhaps?
Click to expand...
Click to collapse
1GB = 1024MB, not 1000MB
Well on stock zeus/phonex, as the OT shows, boot + system + data + appslog (vendor) + cache = 940MB. Along with the ~80MB of reserved data at the beginning for radio/baseband and such, that comes to 1020MB. I assume the last missing ~4MB of the full 1GB is reserved for remapping bad blocks (i.e. wear-leveling).
That FTF is completely weird, just like the 420MB space mod for some devices is actually dangerous (size of one partition overlaps the offset of another by about 20MB). If you visualize your map you just showed, there is some wasted space after /system map. Anyway, the cache partition on zeus board goes right at the end, after vendor. So yeah the maps are obviously different, however I think the 1020MB NAND size is possibly the same for all msm-7x30/Snapdragon S2 SoC devices (not just Sony).
Could you ensure you have flashed a 100% original/genuine FTF file and get full ATAG information again?
CosmicDan said:
1GB = 1024MB, not 1000MB
Click to expand...
Click to collapse
well... thats open for debate in some way, GB != GiB. For me 1GB should be 1024Mb though ...
CosmicDan said:
Well on stock zeus/phonex, as the OT shows, boot + system + data + appslog (vendor) + cache = 940MB. Along with the ~80MB of reserved data at the beginning for radio/baseband and such, that comes to 1020MB. I assume the last missing ~4MB of the full 1GB is reserved for remapping bad blocks (i.e. wear-leveling).
Click to expand...
Click to collapse
most likely yes... sounds fair atleast...
CosmicDan said:
That FTF is completely weird, just like the 420MB space mod for some devices is actually dangerous (size of one partition overlaps the offset of another by about 20MB). If you visualize your map you just showed, there is some wasted space after /system map. Anyway, the cache partition on zeus board goes right at the end, after vendor. So yeah the maps are obviously different, however I think the 1020MB NAND size is possibly the same for all msm-7x30/Snapdragon S2 SoC devices (not just Sony).
Click to expand...
Click to collapse
i've been playing around with wedgess' kernel:
Code:
system 9C4 @ 2E4 320000 @ 94720 312Mb
userdata 1258 @ CA8 601088 @ 414720 587Mb
cache 40 @ 1F00 8192 @ 1015808 8Mb
EOD: 1024000 1000Mb
Thats what i am using now, thanks to your guide
{
"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"
}
CosmicDan said:
Could you ensure you have flashed a 100% original/genuine FTF file and get full ATAG information again?
Click to expand...
Click to collapse
Will report back with the defaults from the stock rom later... going to bed now... 7:36am here now... haven't been sleeping yet :silly:
Yeah true, the whole kilobyte/kibibyte thing.... they still display KB/MB instead of KiB/MiB in most things even though they're in 1024 unit (shell listings, file explorer properties, etc.) but storage vendors do use true 1000 units, 32GB SDCard for example... but then the software doesn't so it's stupid and confusing So yeah, most people have not adopted it, thus it's better to assume that all KB/MB/etc measurements are done in powers of 1024 still.... because they're old school
I wonder, in pther Android ROM's is it corrrect? In MIUI/Turbo UI it shows 639MB in Storage (instead of MiB) so I assume even Android OS itself is also "wrong" haha. Titanium Backup is the *only* app I know of that shows sizes in power of 1000.... and that confuses a lot of people.
CosmicDan said:
Yeah true, the whole kilobyte/kibibyte thing.... they still display KB/MB instead of KiB/MiB in most things even though they're in 1024 unit (shell listings, file explorer properties, etc.) but storage vendors do use true 1000 units, 32GB SDCard for example... but then the software doesn't so it's stupid and confusing So yeah, most people have not adopted it, thus it's better to assume that all KB/MB/etc measurements are done in powers of 1024 still.... because they're old school
I wonder, in pther Android ROM's is it corrrect? In MIUI/Turbo UI it shows 639MB in Storage (instead of MiB) so I assume even Android OS itself is also "wrong" haha. Titanium Backup is the *only* app I know of that shows sizes in power of 1000.... and that confuses a lot of people.
Click to expand...
Click to collapse
Code:
SIN name HEX [email protected] DEC (in k) SIZE
amss.sin: ??? E4 @ 10 29184 @ 2048 28Mb
amss_fs_anzu.sin: ??? 68 @ F4 13312 @ 31232 13Mb
adsp.sin: ??? 6C @ 15C 13824 @ 44544 13Mb
fota0.sin: ??? 5C @ 1C8 11776 @ 58368 11Mb
fota1.sin: ??? 5C @ 224 11776 @ 70144 11Mb
kernel.sin: boot 64 @ 280 12800 @ 81920 12Mb
LT15i: anzu
system.sin: system 9C4 @ 2E4 320000 @ 94720 312Mb
userdata.sin: userdata BE0 @ CA8 389120 @ 414720 380Mb
vendor.sin: vendor 42C @ 1888 136704 @ 803840 133Mb
cache 330 @ 1CB4 104448 @ 940544 102Mb
EOD: 1044480 1020Mb
LT18i: ayame
system.sin: system C80 @ 2F4 409600 @ 96768 400Mb
cache 360 @ 1CB4 110080 @ 506368 107Mb
userdata.sin: userdata D20 @ 12D0 430080 @ 616448 420Mb
EOD: 1046528 1022Mb
MK16i/a: iyokan
system.sin: system C80 @ 2F4 409600 @ 96768 400Mb
cache 360 @ 1CB4 110080 @ 506368 107Mb
userdata.sin: userdata D20 @ 12D0 430080 @ 616448 420Mb
EOD: 1046528 1022Mb
your welcome
Great thanks. It seems the anzu has 2MB unused... is that your device? If so, do you know how to use dd? Can use dd to dump partition, if its mapped bad it will give I/O error.
Sent from Xperia Play (R800a) with Tapatalk
CosmicDan said:
Great thanks. It seems the anzu has 2MB unused... is that your device? If so, do you know how to use dd? Can use dd to dump partition, if its mapped bad it will give I/O error.
Sent from Xperia Play (R800a) with Tapatalk
Click to expand...
Click to collapse
Yep, I have the anzu, and I know how to use dd... Will test that some time later would it be possible to dump all of the nand flash?
Sent from my LT15i using xda app-developers app
[NUT] said:
Yep, I have the anzu, and I know how to use dd... Will test that some time later would it be possible to dump all of the nand flash?
Sent from my LT15i using xda app-developers app
Click to expand...
Click to collapse
Sure, should be. Say you wanted to dump entire flash to one image, just add another partition to mtdparts parameter with offset 0 and size of 1020MB (in anzu case). Then you can dd from that new mtdblock device to sdcard. But I think you may get lots of I/o errors on the first 80MB, I am really not sure. Just make sure you don't try to write to it LOL.
Also I think our devices need bs=4096 (4KB) because that is the sector size of our nand chip.
EDIT: Maybe there is some unused space at the end of that first 80MB, I am not sure. Because baseband and adsp firmware is less than 80MB.
Sent from Xperia Play (R800a) with Tapatalk
CosmicDan said:
Sure, should be. Say you wanted to dump entire flash to one image, just add another partition to mtdparts parameter with offset 0 and size of 1020MB (in anzu case). Then you can dd from that new mtdblock device to sdcard. But I think you may get lots of I/o errors on the first 80MB, I am really not sure. Just make sure you don't try to write to it LOL.
Also I think our devices need bs=4096 (4KB) because that is the sector size of our nand chip.
EDIT: Maybe there is some unused space at the end of that first 80MB, I am not sure. Because baseband and adsp firmware is less than 80MB.
Sent from Xperia Play (R800a) with Tapatalk
Click to expand...
Click to collapse
From what i know from using dd: it does a byte4byte copy, in any sector size you like but in any case it will read what the disk says there is, as long as there is a disk... so the o/i errors should only occur on those parts that are either damaged or non existent...
I'll do a partition as last option in the config_cmdline grabbing the theoretical maximum of 1024Mb and see if it will fly.
As the NAND flash chip has no logic that makes it a disk like entity other then direct access through MTD software logic (hence yaffs2 as filesystem of choice) i strongly doubt it will use the last 2/4Mb in the end as wear leveling buffer...
[NUT] said:
I'll do a partition as last option in the config_cmdline grabbing the theoretical maximum of 1024Mb and see if it will fly.
Click to expand...
Click to collapse
Well... it doesn't ... it craps out on the first sector it seems, but even if i skip the first sector it still doesn't want to go, probably because the partition size was wrong in the first place, but it's strange anyway.
Building a new testkernel with [email protected] which is one less in size, if 0 counts as the first, the last probably didn't exist
EDIT: nope, that one didn't fly either... dunno why, dd isn't very elaborate on it's errors
[NUT] said:
Well... it doesn't ... it craps out on the first sector it seems, but even if i skip the first sector it still doesn't want to go, probably because the partition size was wrong in the first place, but it's strange anyway.
Building a new testkernel with [email protected] which is one less in size, if 0 counts as the first, the last probably didn't exist
EDIT: nope, that one didn't fly either... dunno why, dd isn't very elaborate on it's errors
Click to expand...
Click to collapse
I think that beginning part is "read-protected" in userspace, I'm not sure. I will def. like to try this but my linux machine is awaiting repairs, I want to see if I can write to the amss (SBL) partition. Probably not though
CosmicDan said:
I think that beginning part is "read-protected" in userspace, I'm not sure. I will def. like to try this but my linux machine is awaiting repairs, I want to see if I can write to the amss (SBL) partition. Probably not though
Click to expand...
Click to collapse
I would agree with you, except if I skip the first 92 Mb of the NAND with dd it still doesn't read... maybe the 'read-protection' foils that plan as well... I don't know ...
Quadrant ~ 5000.
Antutu ~ 14000.
http://consumer.huawei.com/en/mobile-phones/features/g740-l00-en.htm
Rooting:
1. Install latest Framaroot 1.6.1 from here http://forum.xda-developers.com/showthread.php?t=2130276
2. Launch and choose Gandalf. It will be rooted in a second.
3. Reboot and enjoy.
Battery screenshots, 100% to 8%, GREAT screen on time, 5h 41m.
Here is the partition table, i've backuped the recovery.img using this command dd if=/dev/block/mmcblk0p14 of=/sdcard/recovery.img bs=4096 but when trying to generate cwm recovery here http://builder.clockworkmod.com/ it failed.
If anyone is interested in getting a working cm with this device, i can provide the necessary files from my device.
[email protected]:/ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Model: MMC SEM08G (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 17.4kB 280kB 262kB sbl1
2 280kB 542kB 262kB sbl2
3 542kB 1066kB 524kB sbl3
4 1066kB 1328kB 262kB rpm
5 1328kB 2377kB 1049kB tz
6 2377kB 4474kB 2097kB aboot
7 4474kB 6571kB 2097kB aboot2
8 6571kB 6579kB 8192B ssd
9 8389kB 12.6MB 4194kB fsg
10 12.6MB 16.8MB 4194kB modemst1
11 16.8MB 21.0MB 4194kB modemst2
12 21.0MB 54.5MB 33.6MB oeminfo
13 54.5MB 122MB 67.1MB fat16 modem
14 122MB 138MB 16.8MB recovery
15 138MB 155MB 16.8MB recovery2
16 155MB 159MB 4194kB misc
17 159MB 164MB 4194kB splash
18 164MB 172MB 8389kB ext4 persist
19 172MB 180MB 8389kB tombstones
20 180MB 181MB 655kB pad
21 185MB 197MB 12.6MB boot
22 197MB 466MB 268MB ext4 cust
23 466MB 667MB 201MB ext4 cache
24 667MB 1741MB 1074MB ext4 system
25 1741MB 2923MB 1183MB ext4 userdata
26 2923MB 7818MB 4895MB fat32 grow
Click to expand...
Click to collapse
Hello, a just installed an app from the playstore that bricked my yumo. It just show the orange logo and doesn't boot up. Anybody knows where can i download the firmware to reinstall it or should i go to for repair? Tried factory reset from recovery but still nothing. Thanks.
ione2380 said:
Hello, a just installed an app from the playstore that bricked my yumo. It just show the orange logo and doesn't boot up. Anybody knows where can i download the firmware to reinstall it or should i go to for repair? Tried factory reset from recovery but still nothing. Thanks.
Click to expand...
Click to collapse
If factory reset doesn't work, return it for repair, there isn't a custom recovery for it yet, if it was i would backup my device and give you the backup for a restore. I've checked the huawei website, there isn't a firmware to download from them.. so no luck this way. What app did you install?
Ask orange for the firmware maybe they will give it if we will have future problems...
I have tested it successfully with a Huawei Ascend G740 from Yoigo (Spain).
Thank you!
GeekRMX said:
Thank you!
I have tested it successfully with a Huawei Ascend G740 from Yoigo (Spain) following this tutorial
Great device!
Click to expand...
Click to collapse
why do you post a link with the same method described by me in the op over 2 weeks ago? please remove the link because it's advertising.
ione2380 said:
Hello, a just installed an app from the playstore that bricked my yumo. It just show the orange logo and doesn't boot up. Anybody knows where can i download the firmware to reinstall it or should i go to for repair? Tried factory reset from recovery but still nothing. Thanks.
Click to expand...
Click to collapse
Try the Nandroid backup / rrestore method. This method is used for backing up the original ROM and recover it when something wrong occures.
I assume that you do not have a backup image of your original ROM.
What you can do is ask someone to do a full Nandroid Backup of their Huawei G740/Orange Yumo and send it to you or get a custom working ROM.
I suggest flashing the custom ROM or someones else's Nandroid Backup using ADB.
search google for : simple-adb-backup-backs-up-your-android-phone-from-the-desktop-no-root-required
search google for: nandroid-backup-restore-for-android-4-2
After you solve this, if you solve it please post how you did it step by step.
full nandroid backup requires a cwm recovery which we do not have for yumo/g740, if we had i could have helped him.
also the bootloader is locked...
i think he sent it to service.
I had no other way but sent it to service. I don't know why but they gave me a new one? Maybe orange doesn't have firmware either?
For anyone who has root just stay away from an app called srs manager from google play. It will brick your yumo.?
Sent from my Note 3 SM-N9005 using Tapatalk.
ione2380 said:
I had no other way but sent it to service. I don't know why but they gave me a new one? Maybe orange doesn't have firmware either?
For anyone who has root just stay away from an app called srs manager from google play. It will brick your yumo.?
Sent from my Note 3 SM-N9005 using Tapatalk.
Click to expand...
Click to collapse
Did it came also with 4.1.2? Of course they have it because it is customized with lots of orange applications.
Yes, still 4.1.2
Send from my Note 3.
hey all,i just upload full backup from my orange yumo,the backup is compatible in TWRP recovery tool https://docs.google.com/file/d/0B4VVn6aokJwXVmFSOUlmcmlfT3c/edit
can you add please twrp recovery for our orange yumo ?
Well..there more to do..yumo has locked bootloader. This will have to be unlocked first,then we can talk about custom recovery. I'm interested in this too.
Sent from Omega pwd GT-I9505/smart phones,dumb people.
kimitza said:
Well..there more to do..yumo has locked bootloader. This will have to be unlocked first,then we can talk about custom recovery. I'm interested in this too.
Sent from Omega pwd GT-I9505/smart phones,dumb people.
Click to expand...
Click to collapse
we know that bootloader is locked, you can try this method to unlock it, http://www.huaweidevice.com/worldwide/servicePolicy.do?method=getUnlockStep .. maybe it works...
True,it can be done, but as long as we don't have an image with the original firmware,i'll take no chances. it's my gf's phone )..
I need some files
Hey all.I need some folders from main root ..Can anyone zip the following folders ""/system/app""and ""/xbin""from main sistem?i deleted some files and i dont want to send it back in service.You can use ES file explorer
emilutzzu said:
Hey all.I need some folders from main root ..Can anyone zip the following folders ""/system/app""and ""/xbin""from main sistem?i deleted some files and i dont want to send it back in service.You can use ES file explorer
Click to expand...
Click to collapse
/system/app https://mega.co.nz/#!Wddw2RqQ!Iszumj2H3mCzGnefl7mKhiAhSkZ79fJh_G3i64wwoeE
/system/xbin https://mega.co.nz/#!DE0VFYYa!ZV-2Tg4ZmFvDc9ZviMIi0kp6-alpASvY2lI3m4-uupY
there is no /xbin folder
to unlock bootloader send a mail to [email protected] with this content:
Dear sir/madam,
I tried applying for a bootloader unlock code at unlock url which I cannot post because of XDA forum restricting me, but my device (Ascend G740) was not listed. I supply the data via this mail in the hope to get a bootloader unlock code via this way instead.
Product Model: Huawei Ascend G740-L00
SN: xxxxxxxxxxxxxxxxxxx
IMEI: xxxxxxxxxxxxxxxxx
ProductID: xxxxxxxx
I hope to hear from you soon.
Yours sincerely,
Click to expand...
Click to collapse
filling your details in a couple days shall receive an answer with the unlock code and podreis follow the process explained on the website of huawei
PS: it works, I already have unlocked
i just go a new update, from L00V100R001C109B140_JB to L00V100R001C109B146_JB, still 4.1.2, don't know the changes because they are not specified.
ClockworkMod Based Recovery 6.0.4.7, Swipe Enabled For Galaxy Core
Donate and support Galaxy Core Development
| [ Info ] |
Recovery built/compiled from Cyanogenmod recovery sources, with swipe ability to make the
operation without hardware keys. Recovery is Android 4.4 Compatible. Yes it is for every rom.
| [ Installation ] |
Method 1 :
via ClockworkMod Recovery
Method 2 :
via Odin
| [ Compatibility ] |
Android 4.2 (CM , stock)
Android 4.3 (CM , stock)
Android 4.4 (CM , stock)
| [ Download ] |
From DevDB : Download
XDA:DevDB Information
ClockworkMod Based Recovery 6.0.4.7, a Tool/Utility for the Samsung Galaxy Core
Contributors
ankur850, koush
Version Information
Status: Stable
Stable Release Date: 2014-03-02
Beta Release Date: 2014-02-18
Created 2014-02-12
Last Updated 2014-03-02
| [ Credits / Thanks ] |
koush for hard work on codes of CWM.
CyanogenInc for Cyanogenmod
Me for making this stuff.
Sandeep Kumar for risking his device. but his device is safe
ankur850 said:
| [ Credits / Thanks ] |
koush for hard work on codes of CWM.
CyaogenInc for Cyanogenmod
Me for making this stuff.
Click to expand...
Click to collapse
Great work... Thanks for ur Recovery.. It will definitely be useful in future
*If someone builds 4.4 Rom :-/
Sent from my GT-I8262 using Tapatalk
Is this working on I8260???
Sent from my GT-I8260 using xda app-developers app
weim1 said:
Is this working on I8260???
Sent from my GT-I8260 using xda app-developers app
Click to expand...
Click to collapse
awesome work rep dev ^_^
anyone tried ?
ankur850 said:
anyone tried ?
Click to expand...
Click to collapse
Gonna try it today, I will submit feedback
Sent from my GT-P7320 using xda app-developers app
Tried on i8260 with I8260XXAML3 stock rom, but blackscreen after galaxy core i8262 logo.
Guys do you have a separate recovery partition? Can I get the size of all the partitions in your phone please?
mmcblk0 - 7456 MB
mmcblk0p1 - 0 MB
mmcblk0p2 - 0.2 MB
mmcblk0p3 - 20 MB --- MODEM
mmcblk0p4 - 0 MB
mmcblk0p5 - 1 MB
mmcblk0p6 - 1 MB
mmcblk0p7 - 2 MB
mmcblk0p8 - 12 MB --- BOOT
mmcblk0p9 - 3 MB
mmcblk0p10 - 3 MB
mmcblk0p11 - 4 MB
mmcblk0p12 (mounted as /persist) - 7.9 MB. Filesystem - EXT4
mmcblk0p13 - 12 MB --- RECOVERY
mmcblk0p14 - 4 MB
mmcblk0p15 - 4 MB
mmcblk0p16 (mounted as /efs)- 11.8 MB. Filesystem - EXT4
mmcblk0p17 - 24 MB
mmcblk0p18 - 4 MB
mmcblk0p19 - 0.5 MB
mmcblk0p20 - 2 MB
mmcblk0p21 (mounted as /system) - 1281.8 MB. Filesystem - EXT4
mmcblk0p22 (mounted as /cache) - 709.5 MB. Filesystem - EXT4
mmcblk0p23 - 320 MB --- PRELOAD
mmcblk0p24 (mounted as /data) - 4913.2 MB. Filesystem - EXT4
mmcblk1p1 -- EXT SDCARD
Emulated (mounted in /storage/sdcard0) - 4863.2 MB. Filesystem - FUSE.
not working black screen in recovery mode
shrisangram said:
not working black screen in recovery mode
Click to expand...
Click to collapse
Same for me.
MirXas said:
Same for me.
Click to expand...
Click to collapse
ok, thanks for reporting the issue, although cwm 6.0.4.7 is not my priority right now.
You already got a working cwm for flashing upto android 4.3.
Maybe i'll try to fix the issue on later time when you need it.
Hey folks, Recovery is now stable, as i announced in thread. So now you can use it.
Some basic features : Swipe functions, left-right-up-down to do operation in recovery, without hardware keys
Happy flashing !
Working perfectly on GT-I8260.
thanks, stable at i8262 Fully Worked
i8260, flashed with Odin
Result: recovery loop
ji_llona said:
i8260, flashed with Odin
Result: recovery loop
Click to expand...
Click to collapse
seems like you landed to recovery every time when you select reboot. right ?
ji_llona said:
i8260, flashed with Odin
Result: recovery loop
Click to expand...
Click to collapse
Try flashing again, it must work.