flashing modem with fastboot - Xperia Z2 Tablet Q&A, Help & Troubleshooting

I run FXP CM 12.1 on SG521 : great lean firmware! However, LTE does
not work.
So now I tried to flashtool flash (with Linux and MacOS, I have no
Micro$oft) latest stock modem from country (NL) the tablet came
from. I am in BE. For some reason even if detected, modem [BASEBAND
partitions] do not flash. The animated information to connect stays.
No big deal: I can try fastboot.
For the image files amss_fsg.sin amss_fs_2.sin amss_fs_1.sin
loader.sin I find partitions
fsg -> /dev/block/mmcblk0p21
modemst1 -> /dev/block/mmcblk0p19
modemst2 -> /dev/block/mmcblk0p20
Which one, by the way, is for loader.sin? And is it needed for modem?
So now I dd-ed these partitions as safety backup, they all have size 1572864
sin sizes are rather tiny
# ls -al amss_fsg.sin amss_fs_1.sin amss_fs_2.sin
-rw-r--r-- 1 root root 2200 Jun 18 20:04 amss_fs_1.sin
-rw-r--r-- 1 root root 2200 Jun 18 20:04 amss_fs_2.sin
-rw-r--r-- 1 root root 622564 Jun 18 20:04 amss_fsg.sin
Question: should I be brave and dd the sin files to their respective partition?
also, maybe I can try same using fastboot, but then: what partition name to use for flashing these 3 files with fastboot?
UPDATE: I managed to flashtool flash latest NL BASEBAND (one needs voldn for flashtool, I was doing volup, which is for fastboot).
BUT: still no LTE ... perhaps a FXP CM 12.1 restriction on SG521 ...

Related

[Kernel/RECOVERY] Sony Xperia Go ST27i, Kernel, CWM, GB KK v5.1 and ICS KKv6

NOTE: Use at Own Risk, I am not Responsible for any damages...... Hit Thanks if it works for you
NOTE: Do not turn on Battery Save mode when you have flashed KK v6.x Kernel, then phone will go into a bootloop immidiatly
Prerequesites:
Sony Firmware: 6.0.B.184 for GB and 6.1.1.B.1.10 for ICS
Installed Andoid SDK with platform-tools included, http://developer.android.com/sdk/index.html
Correctly installed modifed USB Drivers from Sony, follow this Thread if you got problems http://forum.xda-developers.com/showthread.php?t=1527159
Unlocked Bootloader, which implies the correct installation of the USB Drivers follow this Process http://unlockbootloader.sonymobile.com/unlocking-boot-loader
Get SU and Superuser from here http://androidsu.com/superuser/
Know how to put the phone into Fastboot mode
How too:
Now lets get started, these are the steps to get to the latest kernel with the recovery installed.
1. Flash the unlocked stock kernel "Kernel 6.0.B.184 ro.secure=0.elf" from the Android SDK Folder:
fastboot.exe -i 0x0fce flash boot Kernel 6.0.B.184 ro.secure=0.elf
fastboot.exe reboot
2. Install SU and Superuser to gain permanent Root
NOTE: This step is only needed once, you can flash a new kernel without the need to root the device again.
extract SU and Superuser from the downloaded zip files and push those via ADB to the unlocked /system folders from the SDK dir with the commadn below.
adb root
adb shell id (to see if you are root)
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb remount
adb install Superuser.apk
reboot the phone and check with a Rootchecker app if you successfully gained root.
3. Install Busybox From the Market.
Touch the Play Store icon and wait for ...... ...... ok just kidding
NOTE: Please check the Correct file size of the su file with ls -l /system/xbin/ it should be around 380 K in size or compare with the file from the zip archive
4. Flash the latest Custom Kernel "kernel.elf".
fastboot.exe -i 0x0fce flash boot Kernel with CWM gows io sio.elf
fastboot.exe reboot
5. Enter Recovery
Hit Vol+ after it vibrates on the Sony Logo , the Home Touchkey is the Enter Button......
Finally go for a full backup, yeah !!!!
NOTE: I never had to wipe or factory reset my phone while swapping kernels back and forth, trust me i flashed the phone a lot of times with a lot of self compiled kernels...
Appendix:
I build a Custom Kernel from this source http://developer.sonymobile.com/wpor...ads/opensource Open source archive for build 6.0.B.3.184 for KK v5.x and 6.1.1.B.1.10 for KK v6.x
here is my git https://github.com/krachlatte/
Thanks to the makers of the Android Kernel Kitchen 0.2.3, Flashtool, Superuser, aso....just to mention a few:
KeiranFTW for CWM
DOOMLORD for govenours
Championschwimmer For the Kernel Kitchen
jozinek
driversax
.... a s o i hope i did not forget anyone...
Thanks
Release Notes
Krachlattes Kernel (KK) v5.1
SSHTunnel Support
Iptables Support
Droidwall Support
I/O Schedulers added:
sio
Governours added:
interactive
minmax
smartass
smartass2
Krachlattes Kernel (KK) v6.3
gcc upgrade from 4.3.3 to 4.6
http://gcc.gnu.org/gcc-4.6/changes.html
SSA loop prefetching is enabled by default for the Cortex-A9 at -O3
Kernel Source code update to 6.1.1.B.1.10 found at sony dev page
Bootlogo fixed
I/O Scheduler added:
Simple I/O Scheduler (SIO)
Governour added:
smartassv2
Hotplug
The Hotplug governor performs very similarly to the OnDemand governor, with the added benefit of being more precise about how it steps down through the kernel's frequency table as the governor measures the user's CPU load. However, the Hotplug governor's defining feature is its ability to turn unused CPU cores off during periods of low CPU utilization. This is known as "hotplugging."
Obviously, this governor is only available on multi-core devices.
Screenshot showing up time, Juice defender installed, normal usage.....for 1 hour 10 minutes music via bluetooth and gps track recording at the same time yesterday, with kernel v6.2.
NOTE: Do not turn on Battery Save mode when you have flashed KK v6.x Kernel, then phone will go into a bootloop immidiatly
Flash it with:
fastboot.exe flash boot boot.img
Hi! If I use this will the contents on my phone ve deleted or will it stay intact? Tia!
Sent from my ST27i using Tapatalk 2
pls delete this
btw couldn't get a real root ...
i seem to have root but not working properly ... titanium wont get root privileges for example ..
hi guys,
for me it is still working fine as done in the thread above, just post your errors and I will try to look into it. NO SD Card issues at all. got this phone on friday morning and rooted it on friday at around 10pm.
Class 10 SD Card is much faster then with my old defy, when reading an writing files to the phone when it is connected to pc.
Titanium backup running fine....
Something to consider:
1. You need to extract the SU file and Superuser.apk from the zip file and install it via ADB, not push the whole zip via ADB.
2. Did you really unlock the bootloader as described on the sony pages?
3. Is the Android SDK and the modified SONY USB Driver installed correctly? the Dirver installation to get the phone into fastboot correctly was a bit frustrating.
krachlatte said:
hi guys,
for me it is still working fine as done in the thread above, just post your errors and I will try to look into it. NO SD Card issues at all. got this phone on friday morning and rooted it on friday at around 10pm.
Class 10 SD Card is much faster then with my old defy, when reading an writing files to the phone when it is connected to pc.
Titanium backup running fine....
Something to consider:
1. You need to extract the SU file and Superuser.apk from the zip file and install it via ADB, not push the whole zip via ADB.
2. Did you really unlock the bootloader as described on the sony pages?
3. Is the Android SDK and the modified SONY USB Driver installed correctly? the Dirver installation to get the phone into fastboot correctly was a bit frustrating.
Click to expand...
Click to collapse
Hello - yeap - pushed it from the extracted folder - no error messages received in the cmd prompt. all went fine.
2. also yes - the phone is unlocked - actually when tried unlocking for the second time it told me it's already locked
3. I have all the sdk's installed for android and am running the fastboot from the platform-tools directory so all should be there ...
yet - root checker says I have root - but titanium backup or any other program seem to run at first but then I get an error that The phone was not granted with root privileges. Also I cannot install busybox - starts installing and fails at the end for some reason ...
Any ideas?
could you post your screenshot?
did you start with a clean install, i mean did you flash another kernel before installing this one?
where are you from, means what build do you have installed?
could you create a ftf file with flashtool, if it is different from my build ?
krachlatte said:
could you post your screenshot?
did you start with a clean install, i mean did you flash another kernel before installing this one?
where are you from, means what build do you have installed?
could you create a ftf file with flashtool, if it is different from my build ?
Click to expand...
Click to collapse
Will post a screenshot later on tonight as I am not at home with my laptop and phone.
I created an ftf file using the downloaded files from pc companion, decrypted them and made a new ftf file, which was flashed onto the device. I believe this is considered a clean install ?
I am located in Bulgaria but need to check the build version exactly. Just confirmed that the details on the screenshot match all 100% with what the phone.
I have tried flashing another kernel indeed again prepared for .184 from this thread here : http://forum.xda-developers.com/showthread.php?t=1829729 but without any luck - at the end I managed to flash the kernel from this thread here, and then followed the procedure as described above - all seems good and superuser seems to be giving permission to applications - alas no luck.
I can even upload the ftf file if needed. all else seems to be running fine (some slowdowns though - lag or smth - was not present with 162.)
krachlatte said:
Hi Guys,
here is what i did, i just bought a Sony Xperia Go, i am coming from a defy running cm7 and cm9 with root.
i just extracted the kernel from the official Sony update that i graped from the cache folder and converted that file via flashtool to a working ftf file, followed by extracting the kernel and ramdisk and modified the default.prop file to ro.secure=0, afterwards i repacked the the extracted zimage and ramdisk to a working kernel this file is attached to this post "Kernel 6.0.B.184 ro.secure=0.elf". the kernel is complete stock nothing included. just flash it via fastboot with: (unlocked Bootloader needed, see sonys pages for this also for usb driver installation)
fastboot.exe -i 0x0fce flash boot Kernel 6.0.B.184 ro.secure=0.elf
fastboot.exe reboot
next I included SU and Superuser via ADB, you can download an extract SU and Superuser from here http://androidsu.com/superuser/
adb root
adb shell id (to see if you are root)
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb remount
adb install Superuser.apk
Thanks to the makers of the Android Kernel Kitchen 0.2.2, Flashtool, Superuser, aso....
my major question is when will we see CM9 or CM10 ported to this device.
Click to expand...
Click to collapse
Im on .184 now with so many apps installed.. Do I have to flash a clean .184 before flashing this kernel or its ok to just flash it? What would I lose if I flash this?
Sent from my ST27i using Tapatalk 2
wbgenetic said:
Will post a screenshot later on tonight as I am not at home with my laptop and phone.
I created an ftf file using the downloaded files from pc companion, decrypted them and made a new ftf file, which was flashed onto the device. I believe this is considered a clean install ?
I am located in Bulgaria but need to check the build version exactly. Just confirmed that the details on the screenshot match all 100% with what the phone.
I have tried flashing another kernel indeed again prepared for .184 from this thread here : http://forum.xda-developers.com/showthread.php?t=1829729 but without any luck - at the end I managed to flash the kernel from this thread here, and then followed the procedure as described above - all seems good and superuser seems to be giving permission to applications - alas no luck.
I can even upload the ftf file if needed. all else seems to be running fine (some slowdowns though - lag or smth - was not present with 162.)
Click to expand...
Click to collapse
i would recommend to flash the ftf file you generated from the cache and then flash the kernel i provided. had serveral issues with the kernel you are referencing to, my sd card corrupted with it and i had to start from scratch
krachlatte said:
i would recommend to flash the ftf file you generated from the cache and then flash the kernel i provided. had serveral issues with the kernel you are referencing to, my sd card corrupted with it and i had to start from scratch
Click to expand...
Click to collapse
will backup first (since it's my fiancee's phone I don't really wanna lose all contact photos (again)) and then will post results. Thanks.
wbgenetic said:
I can even upload the ftf file if needed.
Click to expand...
Click to collapse
Here are the checksums for the FTF I got from decrypting the firmware downloaded by PC Companion:
CRC-32: d65b0f0f
MD4: e2b001459ef3818cb68c323b6c8fdc38
MD5: 3a35a92ff63c13701637dff2a9019d7c
SHA-1: 310b4b677666ce8a0074ac48b3f29673cc61409d
It would be interesting to know if yours is different. If yes, maybe the reason for your problems is that you got a different regional firmware which is not perfectly compatible with the kernel from this thread.
Does anyone know where I can upload a 270 MB file without registering? I could try uploading my FTF (not sure it would go through, though).
I will run a md5 over mine later,
root checker screenshot
Gesendet von meinem Iconia A500 mit Tapatalk
when thinking about hashing, it does not work because the files have got a different name so the hashes will be different.
here is a screenshot with what i got from the 3 cached files when i have decrypted them with flashtool
cheers
krachlatte said:
I will run a md5 over mine later,
root checker screenshot
Gesendet von meinem Iconia A500 mit Tapatalk
Click to expand...
Click to collapse
when I run the root checker it runs fine - try installing busybox or try to uninstall something with root uninstaller for example
Lebenita said:
Here are the checksums for the FTF I got from decrypting the firmware downloaded by PC Companion:
CRC-32: d65b0f0f
MD4: e2b001459ef3818cb68c323b6c8fdc38
MD5: 3a35a92ff63c13701637dff2a9019d7c
SHA-1: 310b4b677666ce8a0074ac48b3f29673cc61409d
It would be interesting to know if yours is different. If yes, maybe the reason for your problems is that you got a different regional firmware which is not perfectly compatible with the kernel from this thread.
Does anyone know where I can upload a 270 MB file without registering? I could try uploading my FTF (not sure it would go through, though).
Click to expand...
Click to collapse
flashed it clean, followed the instructions to the point - and still - cant even run titanum backup. root checker however still says i'm root! tell me what the problem is now ... grrrr! all that happened was that I now need to rearrange all data ...
---------- Post added at 09:34 PM ---------- Previous post was at 09:30 PM ----------
here's what I get from the superuser trying to update itself or whatever to give you an example... at first it seeems to grant user rights but then ... http://a6.sphotos.ak.fbcdn.net/hphotos-ak-ash4/418841_4289626354485_1820163401_n.jpg
+ here's the folder cache I used (see attached)
here I hope this will help as well :
all seems fine but Root Access : no access
am I pushing a wrong SU :? what could be the reason for this ?
Hi,
i think i found your problem, it loosk like you did not include the loader.sin
20/014/2012 19:14:46 - INFO - Decrypting FILE_279161669
20/014/2012 19:14:59 - INFO - Decrypting FILE_279160643
20/015/2012 19:15:00 - INFO - Decrypting FILE_279066729
20/015/2012 19:15:00 - INFO - Decryption finished
20/016/2012 19:16:30 - INFO - Starting bundle creation
20/016/2012 19:16:30 - INFO - Adding loader.sin to the bundle
20/016/2012 19:16:30 - INFO - Adding kernel.sin to the bundle
20/016/2012 19:16:31 - INFO - Adding system.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding fotakernel.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding modemfs.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding partition-image.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding simlock.ta to the bundle
20/016/2012 19:16:40 - INFO - Adding prcmu.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding apps_log.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding modem.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding userdata.sin to the bundle
20/016/2012 19:16:41 - INFO - Adding cache.sin to the bundle
20/016/2012 19:16:41 - INFO - Finished bundle creation
cheers
krachlatte said:
Hi,
i think i found your problem, it loosk like you did not include the loader.sin
20/014/2012 19:14:46 - INFO - Decrypting FILE_279161669
20/014/2012 19:14:59 - INFO - Decrypting FILE_279160643
20/015/2012 19:15:00 - INFO - Decrypting FILE_279066729
20/015/2012 19:15:00 - INFO - Decryption finished
20/016/2012 19:16:30 - INFO - Starting bundle creation
20/016/2012 19:16:30 - INFO - Adding loader.sin to the bundle
20/016/2012 19:16:30 - INFO - Adding kernel.sin to the bundle
20/016/2012 19:16:31 - INFO - Adding system.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding fotakernel.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding modemfs.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding partition-image.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding simlock.ta to the bundle
20/016/2012 19:16:40 - INFO - Adding prcmu.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding apps_log.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding modem.sin to the bundle
20/016/2012 19:16:40 - INFO - Adding userdata.sin to the bundle
20/016/2012 19:16:41 - INFO - Adding cache.sin to the bundle
20/016/2012 19:16:41 - INFO - Finished bundle creation
cheers
Click to expand...
Click to collapse
here we go step by step :
could be it - flashing now with all 3 files selected and making sure loader.sin is on ..
here is the log :
21/017/2012 00:17:28 - INFO - Device connected in flash mode
21/017/2012 00:17:42 - INFO - Selected Xperia GO ST27i_6.0.B.3.184_Bulgaria.ftf
21/017/2012 00:17:42 - INFO - Preparing files for flashing
21/017/2012 00:17:47 - INFO - Please connect your device into flashmode.
21/017/2012 00:17:48 - INFO - Opening device for R/W
21/017/2012 00:17:48 - INFO - Reading device information
21/017/2012 00:17:48 - INFO - Phone ready for flashmode operations.
21/017/2012 00:17:48 - INFO - Start Flashing
21/017/2012 00:17:48 - INFO - Flashing loader
21/017/2012 00:17:49 - INFO - Loader : S1_Root_3065 - Version : R5E006 / Bootloader status : ROOTED
21/017/2012 00:17:49 - INFO - Flashing partition-image.sin
21/017/2012 00:17:49 - WARN - This file is ignored : simlock.ta
21/017/2012 00:17:49 - INFO - Flashing kernel.sin
21/017/2012 00:17:50 - INFO - Flashing fotakernel.sin
21/017/2012 00:17:52 - INFO - Flashing modemfs.sin
21/017/2012 00:17:53 - INFO - Flashing prcmu.sin
21/017/2012 00:17:53 - INFO - Flashing modem.sin
21/017/2012 00:17:55 - INFO - Flashing apps_log.sin
21/017/2012 00:17:55 - INFO - Flashing system.sin
21/019/2012 00:19:36 - INFO - Log written to C:\Flashtool\flashtool_2012-08-20_12-06-56.log
21/019/2012 00:19:51 - INFO - Flashing userdata.sin
21/020/2012 00:20:02 - INFO - Flashing cache.sin
21/020/2012 00:20:03 - INFO - Ending flash session
21/020/2012 00:20:03 - INFO - Flashing finished.
21/020/2012 00:20:03 - INFO - Please wait. Phone will reboot
21/020/2012 00:20:03 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
21/020/2012 00:20:04 - INFO - Device connected in flash mode
Phone reboots after cable is unplugged and plugged in .. Once loaded I directly reboot into fastboot mode and ..time for some kernel loading ...
Fastboot mode on :
C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe -i 0x0fce flash
boot "Kernel 6.0.B.184 ro.secure=0.elf"
sending 'boot' (4708 KB)...
(bootloader) USB download speed was 20606kB/s
OKAY [ 0.251s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x0000d000-0x00014fff
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 0.374s]
finished. total time: 0.636s
C:\Program Files\Android\android-sdk\platform-tools>fastboot.exe reboot
rebooting...
finished. total time: 0.005s
C:\Program Files\Android\android-sdk\platform-tools>
Phone reboots and now time to push the SU ...
I switch on USB debugging and wait till device is recognized with adb devices ....
C:\Program Files\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
CB5A1KS3PC device
Then I start running the required commands (now trying with SU 3.1.3 for arm devices). (last time it was with 3.2).
C:\Program Files\Android\android-sdk\platform-tools>adb root
adbd is already running as root
C:\Program Files\Android\android-sdk\platform-tools>adb shell id
uid=0(root) gid=0(root)
C:\Program Files\Android\android-sdk\platform-tools>adb remount
remount succeeded
C:\Program Files\Android\android-sdk\platform-tools>adb push su /system/xbin/su
2596 KB/s (85096 bytes in 0.032s)
C:\Program Files\Android\android-sdk\platform-tools>adb shell chown 0.0 /system/
xbin/su
C:\Program Files\Android\android-sdk\platform-tools>adb shell chmod 06755 /syste
m/xbin/su
C:\Program Files\Android\android-sdk\platform-tools>adb remount
remount succeeded
C:\Program Files\Android\android-sdk\platform-tools>adb install Superuser.apk
2801 KB/s (1500526 bytes in 0.523s)
pkg: /data/local/tmp/Superuser.apk
Success
C:\Program Files\Android\android-sdk\platform-tools>
Then I start testing to see If I have root or not ...
Same thing - phone says rooted -all points to rooted phone - but: in root checker I get : like on the screenshot : Root access : no access ... what could be the reason ? btw after testing with root checker - phone starts running slow as hell .. ...
(oh and here is the budle creation log:
21/011/2012 00:11:20 - INFO - Decrypting FILE_279166356
21/012/2012 00:12:01 - INFO - Decrypting FILE_279160643
21/012/2012 00:12:07 - INFO - Decrypting FILE_279066729
21/012/2012 00:12:07 - INFO - Decryption finished
21/012/2012 00:12:58 - INFO - Starting bundle creation
21/012/2012 00:12:58 - INFO - Adding loader.sin to the bundle
21/012/2012 00:12:58 - INFO - Adding kernel.sin to the bundle
21/012/2012 00:12:58 - INFO - Adding system.sin to the bundle
21/013/2012 00:13:12 - INFO - Adding fotakernel.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding modemfs.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding partition-image.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding simlock.ta to the bundle
21/013/2012 00:13:13 - INFO - Adding prcmu.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding apps_log.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding modem.sin to the bundle
21/013/2012 00:13:13 - INFO - Adding userdata.sin to the bundle
21/013/2012 00:13:14 - INFO - Adding cache.sin to the bundle
21/013/2012 00:13:15 - INFO - Finished bundle creation
))
i used this su binary http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
could you upload your ftf file somewere so that i could extract your stock kernel and unlock it for you?
it looks like you got a diffrent regional image....
i also compiled a Customer kernel from sony source for the phone, i will upload this kernel later in the evening today.
krachlatte said:
i used this su binary http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip
could you upload your ftf file somewere so that i could extract your stock kernel and unlock it for you?
it looks like you got a diffrent regional image....
i also compiled a Customer kernel from sony source for the phone, i will upload this kernel later in the evening today.
Click to expand...
Click to collapse
no problem - will upload the ftf in the evening as well - as I am not in front of the home PC right now.
** also any suggestion on backuping all settings on the phone :? I am tired of losing all settings with each flash ... and unfortunately the best backup tool I know (titanium) requires a proper root

Xperia Tablet Z Bricked - PLEASE help!

Hi.
I'm far from experienced when it comes to flashing, but I've flashed a handful of devices without any serious problems (one or two bootloops, but nothing serious). This time though my Xperia Tablet Z is in pretty bad shape and I REALLY need your help!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
tp_88 said:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
Most firmware on xda are kernel only, search xda for xperia flashtool, its different from emma and should solve your problem seeing as you can still got flashmode
Run flashtool
menu devices
check update
double click relevant device
select device tab
select branding [vmo_us/ca/pr for north american]
double click version column
right click and download: will take a while to download the files, NOTE will fail on creating bundle (i think the '/' throws it off)
go to menu tools
bundle
create
source folder, navigate to where flashtool was installed, theres a folder called fimrware, sub folder downloads, sub folder sgp311_vmo_us
fill out fields (SGP311_vmo_us)
select everything and hit the > button, it will now create a firmware bundle that you can use to flash in flash mode (.ftf file should be almost 1GB in size)
press flash button in flashtool (looks like lightning)
flashmode, should default to where your bundle is, if not, source folder navigate to where bundle is
select firmware (make sure nothing is excluded, if you want to just flash kernel then excluded everything but kernel, ditto for system)
flash: WARNING THIS WILL PROBABLY WIPE YOUR DEVICE BACK TO FACTORY
Attach USB to computer, hold volume down while plugging USB into tablet, you now are in flash mode
n.b. place the tablet into flash mode last cause you only have 15 good sec before it drops out of flash mode and it takes some time for tge tool to prep the files for flashing
Try to flash a ftf that will relock your bootloader. Then flash desired firmware. It will wipe all the data present on your tablet. Your tablet will be resurrected after that..
SteelPicori said:
Most firmware on xda are kernel only, search xda for xperia flashtool, its different from emma and should solve your problem seeing as you can still got flashmode
Run flashtool
menu devices
check update
double click relevant device
select device tab
select branding [vmo_us/ca/pr for north american]
double click version column
right click and download: will take a while to download the files, NOTE will fail on creating bundle (i think the '/' throws it off)
go to menu tools
bundle
create
source folder, navigate to where flashtool was installed, theres a folder called fimrware, sub folder downloads, sub folder sgp311_vmo_us
fill out fields (SGP311_vmo_us)
select everything and hit the > button, it will now create a firmware bundle that you can use to flash in flash mode (.ftf file should be almost 1GB in size)
press flash button in flashtool (looks like lightning)
flashmode, should default to where your bundle is, if not, source folder navigate to where bundle is
select firmware (make sure nothing is excluded, if you want to just flash kernel then excluded everything but kernel, ditto for system)
flash: WARNING THIS WILL PROBABLY WIPE YOUR DEVICE BACK TO FACTORY
Attach USB to computer, hold volume down while plugging USB into tablet, you now are in flash mode
n.b. place the tablet into flash mode last cause you only have 15 good sec before it drops out of flash mode and it takes some time for tge tool to prep the files for flashing
Click to expand...
Click to collapse
Thanks for responding. Unfortunately I am getting the same kind of error with the firmware I downloaded through Flashtool according to your instructions above.
"14/016/2014 22:16:58 - ERROR - Processing of kernel.sin finished with errors.
14/016/2014 22:16:58 - INFO - Ending flash session
14/016/2014 22:16:58 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80080012 ";
Almost instantly after connecting my device.
jogen1980 said:
Try to flash a ftf that will relock your bootloader. Then flash desired firmware. It will wipe all the data present on your tablet. Your tablet will be resurrected after that..
Click to expand...
Click to collapse
Where do I get one of those?
tp_88 said:
Thanks for responding. Unfortunately I am getting the same kind of error with the firmware I downloaded through Flashtool according to your instructions above.
"14/016/2014 22:16:58 - ERROR - Processing of kernel.sin finished with errors.
14/016/2014 22:16:58 - INFO - Ending flash session
14/016/2014 22:16:58 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80080012 ";
Almost instantly after connecting my device.
Click to expand...
Click to collapse
What branding are you using, is this for SGP311, what is the size of the ftf file
its a problem with the kernel, try flashing the stock kernel you see posted in xda
did u install CM via
fastboot flash boot boot.img
fastboot flash system system.img
did you install dual recovery?
make sure bootloader is unlocked
EDIT: Tried to exclude one content after the other, and found out the following if it can help:
amss_fs_2.sin - works
amss_fs_1.sin - works
amss_fsg.sin - works
apps_log.sin - works
loader.in - works
partition-image.sin - works
b2b.sin - works (works most of the time, but fails once in a while)
cache.sin - FAILS (Has worked one time, but usually fails)
kernel.sin - FAILS
fotakernel.sin - FAILS
system.sin - FAILS
The log also says: "SGP311 - CB5A1RB3DX - 1272-8342_R2D - Unknown: Aug 14 2014/23:32:54 - GLOBAL-WIFI16G_10.5.1.A.0.283"
I'm trying to flash: "Selected Bundle for Sony Xperia Tablet Z (SGP311). FW release : 10.5.1.A.0.292. Customization : Customized_NCB"
SteelPicori said:
What branding are you using, is this for SGP311, what is the size of the ftf file
its a problem with the kernel, try flashing the stock kernel you see posted in xda
did u install CM via
fastboot flash boot boot.img
fastboot flash system system.img
did you install dual recovery?
make sure bootloader is unlocked
Click to expand...
Click to collapse
I'm guessing you're talking about the bundle, and it's: "FW release : Selected Bundle for Sony Xperia Tablet Z (SGP311). FW release : 10.5.1.A.0.292. Customization : Customized_NCB" (so yes, it's for the SGP311) | That was the only Nordic I saw in the list, so I picked that one. I now see that my device is listed as GLOBAL though, if that makes any difference?
I used this guide, but used the CM.zip för the Wifi model: http://forum.xda-developers.com/showpost.php?p=51850985&postcount=1
So I flashed the boot.img through fastboot if I remember correctly, which gave me CVM. I then wiped data/cache in CVM, and installed CM11.zip and GAPPS.zip (through CVM). No errors during installation, then dead upon reboot.
Not quite sure what you mean by dual recovery, I used CVM which I got through the boot.img in the CM11.zip.
I have tried to relock and unlock bootloader in Flashmode and it should be off. When I hit BLU it run-key say: "Relock" and the log say: "Loader : S1_Root_5ca3 - Version : APQ8064_30 / Boot version : S1_Boot_Lagan_1.1.1_1 / Bootloader status : ROOTED"
EDIT: The size of the tft is 0,97GB.
This is the debug-info for the part when kernel.sin fails, if that can be of any help:
14/053/2014 22:53:35 - DEBUG - Writing packet to phone
14/053/2014 22:53:35 - DEBUG - OUT : CommandID : 9 / Flags : false,true,false / Data length : 1 / Data CRC32 : [EE, 0E, 61, 2C]
14/053/2014 22:53:35 - DEBUG - Reading packet from phone
14/053/2014 22:53:35 - DEBUG - IN : CommandID : 9 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:35 - INFO - Processing kernel.sin
14/053/2014 22:53:35 - DEBUG - kernel.sin : header size : 1608
14/053/2014 22:53:35 - INFO - Checking header
14/053/2014 22:53:35 - DEBUG - Sending part 1 of 1
14/053/2014 22:53:35 - DEBUG - Writing packet to phone
14/053/2014 22:53:35 - DEBUG - OUT : CommandID : 5 / Flags : false,true,false / Data length : 1608 / Data CRC32 : [B3, D9, 0A, 70]
14/053/2014 22:53:35 - DEBUG - Reading packet from phone
14/053/2014 22:53:35 - DEBUG - IN : CommandID : 5 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:35 - INFO - Flashing data
14/053/2014 22:53:35 - DEBUG - Number of parts to send : 16 / Part size : 524288
14/053/2014 22:53:35 - DEBUG - Sending part 1 of 16
14/053/2014 22:53:36 - DEBUG - Writing packet to phone
14/053/2014 22:53:36 - DEBUG - OUT : CommandID : 6 / Flags : false,true,true / Data length : 524288 / Data CRC32 : [BA, 13, 65, 3C]
14/053/2014 22:53:36 - DEBUG - Reading packet from phone
14/053/2014 22:53:36 - DEBUG - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - DEBUG - Sending part 2 of 16
14/053/2014 22:53:36 - DEBUG - Writing packet to phone
14/053/2014 22:53:36 - DEBUG - OUT : CommandID : 6 / Flags : false,true,true / Data length : 524288 / Data CRC32 : [34, D2, 71, 38]
14/053/2014 22:53:36 - DEBUG - Reading packet from phone
14/053/2014 22:53:36 - DEBUG - IN : CommandID : 6 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - DEBUG - Sending part 3 of 16
14/053/2014 22:53:36 - DEBUG - Writing packet to phone
14/053/2014 22:53:36 - DEBUG - OUT : CommandID : 6 / Flags : false,true,true / Data length : 524288 / Data CRC32 : [F6, 5C, 35, 5A]
14/053/2014 22:53:36 - DEBUG - Reading packet from phone
14/053/2014 22:53:36 - DEBUG - IN : CommandID : 6 / Flags : true,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - DEBUG - Writing packet to phone
14/053/2014 22:53:36 - DEBUG - OUT : CommandID : 7 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - DEBUG - Reading packet from phone
14/053/2014 22:53:36 - DEBUG - IN : CommandID : 7 / Flags : false,false,false / Data length : 64 / Data CRC32 : [41, 42, 40, 29]
14/053/2014 22:53:36 - ERROR - Processing of kernel.sin finished with errors.
14/053/2014 22:53:36 - INFO - Ending flash session
14/053/2014 22:53:36 - DEBUG - Writing packet to phone
14/053/2014 22:53:36 - DEBUG - OUT : CommandID : 4 / Flags : false,true,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - DEBUG - Reading packet from phone
14/053/2014 22:53:36 - DEBUG - IN : CommandID : 4 / Flags : false,false,false / Data length : 0 / Data CRC32 : [00, 00, 00, 00]
14/053/2014 22:53:36 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x80080012 ";
tp_88 said:
I'm guessing you're talking about the bundle, and it's: "FW release : Selected Bundle for Sony Xperia Tablet Z (SGP311). FW release : 10.5.1.A.0.292. Customization : Customized_NCB" (so yes, it's for the SGP311) | That was the only Nordic I saw in the list, so I picked that one. I now see that my device is listed as GLOBAL though, if that makes any difference?
I used this guide, but used the CM.zip för the Wifi model: http://forum.xda-developers.com/showpost.php?p=51850985&postcount=1
So I flashed the boot.img through fastboot if I remember correctly, which gave me CVM. I then wiped data/cache in CVM, and installed CM11.zip and GAPPS.zip (through CVM). No errors during installation, then dead upon reboot.
Not quite sure what you mean by dual recovery, I used CVM which I got through the boot.img in the CM11.zip.
I have tried to relock and unlock bootloader in Flashmode and it should be off. When I hit BLU it run-key say: "Relock" and the log say: "Loader : S1_Root_5ca3 - Version : APQ8064_30 / Boot version : S1_Boot_Lagan_1.1.1_1 / Bootloader status : ROOTED"
EDIT: The size of the tft is 0,97GB.
Click to expand...
Click to collapse
well your not going get anywhere if kernel, fotakernel and system fails
i would personally try vmo_eu4 or vmo_eu2 to see if that helps, i know NCB works on north american models cause ive flashed that on my one.
bootloader can only be unlocked via fastboot not flashmode
SteelPicori said:
bootloader can only be unlocked via fastboot not flashmode
Click to expand...
Click to collapse
My bad, I meant Flashtool. Don't remember if it was fastboot or flashmode, but you might be right. It seemed to work when I relocked it though, because SUS then recognized it (but said it couldn't fix it). After that I reverted the process with Flashtool again. And now the log says bootloader status: ROOTED and the BLU-funktion asks me if I want to Relock the device etc, so it should be unlocked.
I'm downloading the firmwares you recommended atm. Unfortunately I don't see it making any difference.
Tried VMO_EU4 now, same result (failed)
tp_88 said:
Tried VMO_EU4 now, same result (failed)
Click to expand...
Click to collapse
Same with EU2 I'm afraid. Any other suggestions?
tp_88 said:
Same with EU2 I'm afraid.
Click to expand...
Click to collapse
what operating system are you using, are you running flash or flash64, im a little stumped to be honest
try drop into fastboot mode
fastboot flash boot boot.img from AICP reboot and see if you can get into recovery
did you ever try to install twrp in the past using the adb shell?
SteelPicori said:
what operating system are you using, are you running flash or flash64, im a little stumped to be honest
try drop into fastboot mode
fastboot flash boot boot.img from AICP reboot and see if you can get into recovery
did you ever try to install twrp in the past using the adb shell?
Click to expand...
Click to collapse
Windows 8.1 Pro 64-bit. I'm running "Sony mobile flasher by Androxyde".
What's an AICP reboot?
I tried to flash the boot.img from the CM11.zip again yesterday and it said it was successful, but it didn't change anything. Still dead. Also tried to flash the CM11.zip through fastboot after that, same thing, no errors but didn't change anything. But I'll try it again in a second.
No, I haven't.
EDIT: Same thing, everything goes well in fastboot:
C:\Fastboot>fastboot flash boot boot.img
sending 'boot' (10030 KB)...
OKAY [ 0.319s]
writing 'boot'...
OKAY [ 0.491s]
finished. total time: 0.816s
But nothing changes.
tp_88 said:
Windows 8.1 Pro 64-bit. I'm running "Sony mobile flasher by Androxyde".
What's an AICP reboot?
I tried to flash the boot.img from the CM11.zip again yesterday and it said it was successful, but it didn't change anything. Still dead. Also tried to flash the CM11.zip through fastboot after that, same thing, no errors but didn't change anything. But I'll try it again in a second.
No, I haven't.
Click to expand...
Click to collapse
if on win 8.1 64bit you need to use the flashtool64 not flashtool
aicp is android ice cream project, its a rom, uses twrp recovery rather than cwm
WELL I'LL BE DAMNED!
I turned flashed the boot.img again, turned it off and tried again and almost had a heart-attack when to screen lit up with the Sony-logo. I managed to get into recovery (CVM) aswell.
Now that I'm in recovery again, what should I do? Although I like CM11 alot I'm not too keen on trying to flash that again for obvious reasons. I have the OMNIROM-zip downloaded aswell, should I try that or what do you think?
Also, I just thought of something. I tried rooting the device with multiple different techniques, but don't think any of them actually worked, so my device might have been unrooted when I flashed CM (although with unlocked BL of course) could that have been the problem? I didn't think you needed root to flash, but like I said I'm pretty novice at this stuff.
tp_88 said:
WELL I'LL BE DAMNED!
I turned flashed the boot.img again, turned it off and tried again and almost had a heart-attack when to screen lit up with the Sony-logo. I managed to get into recovery (CVM) aswell.
Now that I'm in recovery again, what should I do? Although I like CM11 alot I'm not too keen on trying to flash that again for obvious reasons. I have the OMNIROM-zip downloaded aswell, should I try that or what do you think?
Click to expand...
Click to collapse
omni is good, aicp is based on omni, just remember to grab gapps and super user and wipe cache, dalvik and factory wipe before flashing
SteelPicori said:
omni is good, aicp is based on omni, just remember to grab gapps and super user and wipe cache, dalvik and factory wipe before flashing
Click to expand...
Click to collapse
Like I said I wasn't rooted before, can that be what caused all of this? Should I just flash SuperSU before that ROM this time?

How to Unlock Bootloader and Root M4 Aqua E2363 indian version Running marshmallow

I Recently Update my Xperia M4 Dual Sim Model E2363 to marshmallow but i am not able to root it
I also tried to unlock it bootlooder and even after being successfull i am not able to install Custom Recovery
Log In Flash tools
Phone ready for flashmode operations.
10/057/2016 21:57:41 - INFO - Opening TA partition 2
10/057/2016 21:57:41 - INFO - Current device : E2363 - YT9115MB7A - 1295-2357_R2C - 1296-1835_26.3.B.0.131 - GENERIC_26.3.B.0.131
10/057/2016 21:57:41 - INFO - Closing TA partition
10/057/2016 21:57:41 - INFO - No loader in the bundle. Searching for one
10/057/2016 21:57:41 - INFO - Processing loader.sin
10/057/2016 21:57:41 - INFO - Checking header
10/057/2016 21:57:41 - INFO - Flashing data
10/057/2016 21:57:43 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_207 / Bootloader status : NOT_ROOTABLE
10/057/2016 21:57:43 - INFO - Max packet size set to 512K
10/057/2016 21:57:43 - INFO - Opening TA partition 2
10/057/2016 21:57:43 - INFO - Start Reading unit 00 00 08 B2
10/057/2016 21:57:43 - INFO - Reading TA finished.
10/057/2016 21:57:43 - INFO - Closing TA partition
10/058/2016 21:58:06 - INFO - Unlocking device
10/058/2016 21:58:06 - INFO - Opening TA partition 2
10/058/2016 21:58:06 - INFO - Writing TA unit 000008B2. Value : 37 41 41 43 38 42 32 43 34 38 36 31 44 34 41 36
10/058/2016 21:58:06 - INFO - Closing TA partition
10/058/2016 21:58:07 - INFO - Unlock finished
10/002/2016 22:02:05 - INFO - Ending flash session
10/002/2016 22:02:05 - INFO - You can now unplug and restart your device
ScreenShot while installing Custom Recovery
Not able to post screenshot here
Here is the error i face while installing custom recovery
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30268 KB)...
OKAY [ 1.060s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.073s
Can someone provide me proper method to root and unlock my Xperia M4 Aqua
diamondfdk said:
I Recently Update my Xperia M4 Dual Sim Model E2363 to marshmallow but i am not able to root it
I also tried to unlock it bootlooder and even after being successfull i am not able to install Custom Recovery
Log In Flash tools
Phone ready for flashmode operations.
10/057/2016 21:57:41 - INFO - Opening TA partition 2
10/057/2016 21:57:41 - INFO - Current device : E2363 - YT9115MB7A - 1295-2357_R2C - 1296-1835_26.3.B.0.131 - GENERIC_26.3.B.0.131
10/057/2016 21:57:41 - INFO - Closing TA partition
10/057/2016 21:57:41 - INFO - No loader in the bundle. Searching for one
10/057/2016 21:57:41 - INFO - Processing loader.sin
10/057/2016 21:57:41 - INFO - Checking header
10/057/2016 21:57:41 - INFO - Flashing data
10/057/2016 21:57:43 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_207 / Bootloader status : NOT_ROOTABLE
10/057/2016 21:57:43 - INFO - Max packet size set to 512K
10/057/2016 21:57:43 - INFO - Opening TA partition 2
10/057/2016 21:57:43 - INFO - Start Reading unit 00 00 08 B2
10/057/2016 21:57:43 - INFO - Reading TA finished.
10/057/2016 21:57:43 - INFO - Closing TA partition
10/058/2016 21:58:06 - INFO - Unlocking device
10/058/2016 21:58:06 - INFO - Opening TA partition 2
10/058/2016 21:58:06 - INFO - Writing TA unit 000008B2. Value : 37 41 41 43 38 42 32 43 34 38 36 31 44 34 41 36
10/058/2016 21:58:06 - INFO - Closing TA partition
10/058/2016 21:58:07 - INFO - Unlock finished
10/002/2016 22:02:05 - INFO - Ending flash session
10/002/2016 22:02:05 - INFO - You can now unplug and restart your device
ScreenShot while installing Custom Recovery
Not able to post screenshot here
Here is the error i face while installing custom recovery
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30268 KB)...
OKAY [ 1.060s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.073s
Can someone provide me proper method to root and unlock my Xperia M4 Aqua
Click to expand...
Click to collapse
What's your bootloader status now? Even if Flashtool showed, that the unlock is finished, It doesn't mean that your bootloader is unlocked. Check the status of your bootloader, by typing this code in your dialer *#*#7378423#*#* , chose service info and then Configuration, and you will se there Rooting status. If it says it's unavailable, than It's not unlocked properly, or you can't unlock it, because it's . bootloader unlock allowed: NO , so that means, you cant unlock your bootloader. If your bootlader status shows Bootloader unlocked: Yes than, your bootlader is unlocked. In that case, you need to check the option OEM Unlocking in developer settings, it is supposed to be turned on. If you don't have that option in developer settings, then you need to flash different firmware (some firmware for different region/branding, doesn't have this option in developer settings). Flash the latest one. For example, Marshmallow has this option in developer settings.

Custom recovery succesfully flashed, still on stock recovery after.

Hi all.
I got a problem.
I tried to flash a custom recovery (TRWP 3.0) made for my phone (Huawei G6-u10).
I entered the bootloader and I got all drivers on my pc.
This is what I did:
fastboot flash recovery TWRP.img
target reported max download size of 536870912 bytes
sending 'recovery' (12798 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 1.265s]
finished. total time: 1.683s
Then I did this:
fastboot reboot
Succesfully booted into android I did this:
adb reboot recovery
It reboots to the stock recovery.
WHY does this happen?!
I tried multiple times, holding power button instead of the command, power button with vol + and even disconnecting the battery cable.
nothing worked. I tried other recovery's as well, even other stock recovery's didnt work.
I did not modify the recovery partition, only internal sdcard, userdate, system, misc, cache and cust (all after the recovery and boot partition).
This is the same if I want to flash the userdata partition, it says the flash is succesful, but it did nothing. Only flashing system works.
My second idea was to try the DD command.
I tried (in adb shell) this:
dd if=/storage/sdcard1/TWRP.img of=/dev/block/mmcblk0p19
The result was succesful, but I got still the stock recovery!
Then I checked my bootloader if its unlocked.
proof here:
fastboot oem get-bootinfo
...
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) Root State: ROOT
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.063s]
finished. total time: 0.064s
I dont know whats the problem here, why I dont have the custom recovery I just installed succesfully?
My partition table:
# parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Model: MMC H4G1d (sd/mmc)
Disk /dev/block/mmcblk0: 3909MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 17.4kB 542kB 524kB sbl1
2 542kB 574kB 32.8kB sdi
3 4194kB 4227kB 32.8kB DDR
4 8389kB 8901kB 512kB rpm
5 8901kB 9413kB 512kB tz
6 9413kB 15.1MB 5726kB aboot
7 15.1MB 16.2MB 1049kB pad
8 16.2MB 83.3MB 67.1MB oeminfo
9 83.3MB 87.5MB 4194kB modemst1
10 87.5MB 91.7MB 4194kB modemst2
11 92.3MB 193MB 101MB fat16 modem
12 193MB 197MB 4194kB fsg
13 197MB 197MB 1024B fsc
14 197MB 197MB 8192B ssd
15 197MB 231MB 33.6MB ext4 log
16 235MB 302MB 67.1MB bkbootup
17 302MB 310MB 8389kB ext4 persist
18 310MB 323MB 12.6MB boot
19 323MB 340MB 16.8MB recovery
20 340MB 370MB 30.3MB ext4 cust
21 370MB 375MB 5000kB ext4 cache
22 375MB 380MB 5000kB misc
23 380MB 1480MB 1100MB ext4 system
24 1480MB 3869MB 2389MB ext4 userdata
25 3869MB 3909MB 40.1MB fat32 grow msftres
Does somebody know what I am doing wrong?

IMEI 0

Hello
released boot loader
I rooted with magisk
I put some roms miui, havoc, aosp...........
But when I went back to stock rom, I had no signal and imei 0 on my xt1941-3 deen BR
I downloaded all versions of the RETBR deen, not the version of android 8.1 solved.
link download Roms
https://mirrors.lolinet.com/firmware/moto/deen/official/
I used the commands standards:
Code:
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
I changed the imei using root and substratum with the IMEI CHANGER free.apk, I was able to successfully change the imei, but still no signal.
I have no backup of the EFI folder and when I install the stock rom it does not create this folder.
I downloaded Partitions Backup.apk
I have the partitions:
MODEM1
MODEM2
MODEMST1
MODEMST2
*I downloaded them but I couldn't find the files
.nv_data.bak
.nv_data.bak.md5
and neither the others that are created at each boot nv_data.bin, nv_data.bin.md5 and
.nv_state
I saw some tutorials using WriteDualIMEI (W + G_eMMC) .exe or Qualcomm_Smartphone_Write_IMEI_Tool_v1.01.exe applications but my phone doesn't recognize in the device manager as (qualcomm port com8) appears as (android device, motorola adb interface)
Any tips? Please I need help! lost my cellphone
In this forum of moto g4 explains well, how to proceed, but I do not have the files, if someone can help me, I give a donation.
dhob.bin.bak
https://forum.xda-developers.com/mo...859068&usg=ALkJrhgE4aZYFO7uWHYr-X-2l6ucpltAXg

Categories

Resources