[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE][SIZE=+2]Specific to[/SIZE]
{
"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"
}
MOTO E 2015
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
Please keep discussion focused, on questions pertaining to this Device
List of supporters...
... @abhishekr700
.. @SG3
...To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. Thank you!
Supporters: If you want to be put on or off the list, just make a request to me through PM
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
[FAQ] Frequently Asked Questions For Moto E (2015)
[INDEX] Moto E 2015 - ROMs, Kernels, MODs, GUIDES
Please look for a similar [HELP THREAD] when visiting another device forum.
Dont forget to press the Thanks button for me !!! :good:
[Q] Custom Rom cm12.1 on sprint moto e 2015 LTE problems
Flashed cm12.1 9/27/2015 build 54 onto sprint LTE x1526.
Wifi cannot get DHCP IP address and keeps on "obtaining IP" stage.
Wireless data is with boost, and I would appreciate some help on how to change it to sprint.
searched google but didn't find the answers. Thanks in advance!
Flash stock recovery for ota upadte problem.
abhishekr700 said:
Many people are joining xda on daily basis. Some of them join the forum to get custom ROMs while some join in order to get some of their problem that they are facing with their phones solved.
There are dedicated threads for ROMs but what about HELP/QUESTIONS??
People generally straight away start a new thread to get their doubts solved. But this can lead to chaos in the forum.
I'm creating this thread as an alternative to *New Threads* that aim to resolve a question.
Not only this, this thread can also become a Database kind of place where people can look if their question is already solved or not...
I request all members of the MOTO E 2015 sub-forum to help and answer some questions posted here if they can.
I hope you guys get the idea behind this thread...
Click to expand...
Click to collapse
I have the xt1511 but it's GSM (I am using a sim card.) I rooted it not knowing a lot of things like nandroid backups existed and were a good idea.
There is a system ota update for it. After a lot of searching I found that I need the stock recovery for that upadte to work. I searched and found this,
http://forum.xda-developers.com/moto-e-2015/orig-development/recovery-stock-recovery-5-0-2-t3123084
I assumed it would work because mine is GSM not CMDA. I renamed the stoc recovery image to stock.img because I want to use this,
http://www.xda-developers.com/simple-recovery-switcher/
I am following the root guide to use ADB to flash the recovery image and am getting an error.
"<bootloader> Image size exceeded partition limits
<bootloader> Preflash validation failed
FAILED <Remoat failur>"
Any idea as to how I can fix this. Here is a video showing exactly what I am doing. https://youtu.be/2BjRnLsddRU
Fastboot Reason : UTAG bootmode configured as "fastboot" mode.
Hi Abhi..,
i need your help,my MotoE2 is rooted and stuck in fastboot mode pressing any buttons say boot up failed...
while trying to install stock rom some command failed like "fastboot flash partition gpt.bin" gives
<bootloader> preflash validation failed
<Failed> Remote failure.
and "Fastboot flash system syste....Img0" goes OKAY in CMD while on phone screen throws "hab check failed for primary gpt
Failed to verify hab image Priamry gpt"
rest of command goes OKAY.
finally it says "UTAG mode configured as "fastboot mode"
bootup failed....
what to do????
Contacts; [email protected]
+91 7204393558
TRY not using the bin files....I dont think you have to flash bootloader again when you are just restoring stock...
Please press the thanks for further help...
MotoE seems bricked,stuck in bootloader mode,facing hurdles installing stock rom !
executing "fastboot flash partition gpt.bin" throws
target reported max download size of 299892736 bytes
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.156s
Executing "fastboot flash system system.img_sparsechunk.0"
gives this,seems okay..
target reported max download size of 299892736 bytes
sending 'system' (253883 KB)...
OKAY [ 8.979s]
writing 'system'...
OKAY [ 14.149s]
finished. total time: 23.128s
BUT ON PHONE SCREEN I GET THIS !:
" hab check failed for primary_gpt
Failed to verify hab image primary_gpt"
Help me please guys...#MotoE2
---------- Post added at 10:46 AM ---------- Previous post was at 10:40 AM ----------
Hi Abhishek...help me fix my issues.i'M trying hard but all in vain.
my mai:[email protected]
MbNo.: 7204393558
---------- Post added at 11:29 AM ---------- Previous post was at 10:46 AM ----------
The Commands that prevents successful completion are :
C:\Downloads\RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml>fastboot flash partit
ion gpt.bin
target reported max download size of 299892736 bytes
sending 'partition' (32 KB)...
OKAY [ 0.094s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.263s
C:\Downloads\RETUAWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml>fastboot flash motobo
ot motoboot.img
target reported max download size of 299892736 bytes
sending 'motoboot' (2184 KB)...
OKAY [ 0.123s]
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.232s
Fix please..anybody
@vivekanand149 Dude, why the heck are you trying to flash a Moto G 2nd gen ROM onto your phone?!
If you're using an XT1521 (the Indian 4G model), use this ROM: http://www.filefactory.com/file/1ve...XI22.50-53.1_cid7_subsidy-DEFAULT_CFC.xml.zip
Otherwise, find your model number here: http://www.filefactory.com/folder/752fdb49361c7f62/?sort=filename&order=ASC&show=100&page=1
You need to use the same ROM as your phone's model number!
Also when flashing you need to use MFASTBOOT NOT FASTBOOT.
:beer:
Sent from my XT1528 using XDA Free mobile app
I got two refurbished unlocked moto e 2015 lte phones. One worked well. The other has all the system apps crashing. I didn't discover this until after the return policy expired as I was away on holiday.
I've unlocked the bootloader and when I try to flash recovery through fastboot, I get the following failure:z
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 299892736 bytes
sending 'recovery' (10832 KB)...
OKAY [ 0.359s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.389s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I am using the correct recovery. I have usb debugging on...bootloader is unlocked. Device id shows up in fastboot/adb.
Any ideas? What can I do? Re-format the recovery partition? What exact commands would I use?
Stuck...please help!!!! Thanks
Hi. I just received the OTA notification. I downloaded and installed it but after rebooting stills saying 5.0.2. When I check for update it says Software up to date. What went wrong? The phone is retail latam. Thanks.
Still I get same error bro when executin "fastboot flash system sparcechunk....IMG"
Gives:failed to verify hab partition...
"
Sent from my 2014818 using XDA Free mobile app
---------- Post added at 01:11 PM ---------- Previous post was at 01:02 PM ----------
Which rom version does Indian MotoE2 uses? How do I know that?
I'll download that bro.
mfastboot NOT fastboot.
Notice the 'm' in the command.
Motorola stock firmware files have multiple sparsechunk pieces (i.e. img.spareschunk.0,1,2,3), fastboot doesn't allow proper flashing of each of the pieces but Mfastboot does.
Google the command...easy to obtain.
Sent from my XT1528 using XDA Free mobile app
Will try bro.Thanks a lot
---------- Post added at 03:52 PM ---------- Previous post was at 03:34 PM ----------
Will using mfastboot correct all these:
" hab check failed for primary_gpt
Failed to verify hab image primary_gpt"
After fastboot flash system sparcechunk.img0
Help #MotoE2
vivekanand149 said:
Will try bro.Thanks a lot
---------- Post added at 03:52 PM ---------- Previous post was at 03:34 PM ----------
Will using mfastboot correct all these:
" hab check failed for primary_gpt
Failed to verify hab image primary_gpt"
After fastboot flash system sparcechunk.img0
Help #MotoE2
Click to expand...
Click to collapse
Hope so!
Sent from my XT1528 using XDA Free mobile app
Hi bro out of these 3 version that suits my model xt1506 which 1shd I go for. Given I'm using Indian version MotoE2(3g)
Sent from my 2014818 using XDA Free mobile app
Link to download XT1506
Hi abhishek thank for suggestion,can you give me exact workable link to download MotoE2 Image (e.g xt1506:indian version) cannt download from firefactory link,doesn't work!
---------- Post added at 06:05 AM ---------- Previous post was at 05:50 AM ----------
Hi buddy thank for suggestion,can you give me exact workable link to download MotoE2 Image (e.g xt1506:indian version) cannt download from firefactory link,doesn't work!
Link plz for XT1506
Hi Abhishek,will u plz give me a exact link where i can dwonload XT1505(stock firmware MotoE2)link i got not working showing error!
pedrojgim said:
Hi. I just received the OTA notification. I downloaded and installed it but after rebooting stills saying 5.0.2. When I check for update it says Software up to date. What went wrong? The phone is retail latam. Thanks.
Click to expand...
Click to collapse
The OTA update will only be a small update for example a bugfix etc. That's the reason why ur version isn't upgraded.
Sent from my GT-S7562 using XDA Free mobile app
imei 0
Is there anyway to recovery or write imei to phone with locked bootloader?
Can't download,tried 20+ times,failed!
bro the link you gave work bt i have to download it from browser && it gives slow speed not more than 20-30 kbps, i tried 20+ times,failed many times after 80-90% completion!!!downloading form any download mangaer doesn't work.Can u give me any DRIVE LINK OR OTHER LINKS i want need xt1506 version.Dont know whether European/British work on my model of MotoE2.i'm pissed off!
Help plz
Related
Good day,
I've tried so many times with diffrent method to root my HTC Legend, but I always fail...
this is the info of my phone and please somebody help me.
:::: info of boot menu ::::
Legend PVT SHIP S-ON
HBOOT-1.01.0000
MICROP-0816
TOUCH-PANEL-SYN07_0105
RADIO-7.13.35.05
:::: Phone Software info ::::
Android version
2.2
Baseband version
47.51.35.17U_7.13.35.05
Kernal version
2.6.32.17-g309229af
[email protected] #1
Wed Dec 1 15:10:40 CST 2010
Build number
3.15.707.3 CL291292 relase-keys
software number
3.15.707.2
Browser version
webkit 3.1
This is what I get when I reach the "step1-windows.bat" and "step2-windows.bat"
{
"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"
}
I think I'm stuck at "step2-windows.bat" and I tried my best to solve this problem, but I couldn't!!!!
PLEASE HELP ME
DON'T GIVE ME TOUTORIAL HOW TO ROOT FROM WEBSITE
BECAUSE I TRIED ALL OF THEM
Thanks in advance
como'n guys for god sake!!!!!
this is xda-developers and I can't believe that no one knows how to help me out !!!!
waiting for a reply
Sry just got a sgs 2 so my mind has been away from my Legend support, what guide you using?
Sent from my Legend using xda premium
50-3 said:
Sry just got a sgs 2 so my mind has been away from my Legend support, what guide you using?
Sent from my Legend using xda premium
Click to expand...
Click to collapse
I tried all what's in forum here
Modoco, HBOOT 1.01 and all what's avilable
But still not rooted
Any hints pelaaaaaaaaaaaaaaase
Sry you said step 2, which step 2?
Sent from my GT-I9100T using xda premium
OP: scratch step2. this might help. post here after following instructions:
copy update.zip from here to your sd
disconnect your phone from pc, reboot to recovery
on the red ! screen, press vol+ & power button simultaneously
apply update.zip from the blue menu
if a yellow/orange menu pops up, you're most likely rooted already. you can then install any rom of choice from there or restore a backup. HTH
You cannot root your device while using FroYo. I'm surprised that you did not read the requirements for rooting the device. You must downgrade the firmware to 1.31 from 2.1 before you can root.
Read this thread first: http://forum.xda-developers.com/showthread.php?t=725430
LiViD said:
You cannot root your device while using FroYo. I'm surprised that you did not read the requirements for rooting the device. You must downgrade the firmware to 1.31 from 2.1 before you can root.
Read this thread first: http://forum.xda-developers.com/showthread.php?t=725430
Click to expand...
Click to collapse
Finally, something helpful.... so you'r telling me that there is no way to root a froyo version !??
actually, I tried this method also few days a go but still not getting close because I got this error message
c---rw---- 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0
any other procedure for downgrading
maxq1 said:
OP: scratch step2. this might help. post here after following instructions:
copy update.zip from here to your sd
disconnect your phone from pc, reboot to recovery
on the red ! screen, press vol+ & power button simultaneously
apply update.zip from the blue menu
if a yellow/orange menu pops up, you're most likely rooted already. you can then install any rom of choice from there or restore a backup. HTH
Click to expand...
Click to collapse
I tried the fake recovery but also didn't work !!!!
I believe the fake recovery will not work in a phone with a factory rom, I think the phone has to be rooted in order to lunch the fake recovery
thanks for passing by
50-3 said:
Sry you said step 2, which step 2?
Sent from my GT-I9100T using xda premium
Click to expand...
Click to collapse
this step is the second and final step in applying the batched files
after downloading the root folder for legend which is "r4-legend-root"
first step is: connect the phone with USB in HBoot and apply "step1-windows.bat"
Second step: connect the phone with USB while in recovery mode and apply "step2-windows.bat"
I think at step two there is a problem!!!! as shown in the picture above
Which rooting guide??? Most have a step 2
Sent from my GT-I9100T using xda premium
50-3 said:
Which rooting guide??? Most have a step 2
Sent from my GT-I9100T using xda premium
Click to expand...
Click to collapse
Itried all what's in the forum, no thing works with me !!!!
could it be because of a driver problem or a damaged ADB tools!!!
Quick question were you in recovery for step 2?
Sent from my GT-I9100T using xda premium
From the screen capture. I suspect you do not have the driver installed correctly.
Edit: Ignore my comment above.
Since you have passed step 1, your driver works just find.
The next thing to look at is "You MUST have HTC Sync version 2.0.33 not a newer version for step2 to work".
Hi!
I used this tut:
http://theunlockr.com/2010/06/07/how-to-root-the-htc-legend/
I found the answer in the comments - but I can't find it no more. I had the same problems. then it worked.
Good luck!
Rooting issue @ batchfile #2
Hi guys
First of all.. I'm not sure if it's done to bump someone elses post like this. (if not: I'm sorry )
But I'm also stuck at step2 (after following this guide: wiki.rootzwiki.com/HTC_Legend)
this is what I get:
C:\r4-legend-root>step1-windows.bat
Legend Root Step 1
Erasing cache and rebooting in RUU mode...
erasing 'cache'... OKAY
... OKAY
About to start flash...
< waiting for device >
sending 'zip' (121756 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
sending 'zip' (121756 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
Rebooting to bootloader...
rebooting into bootloader... OKAY
Step 1 complete - now use the bootloader menu to enter recovery mode.
To do this, press the power button, wait a few seconds, then use the volume keys
and power button to select the RECOVERY option.
C:\r4-legend-root>step2-windows.bat
Legend Root Step 2
Pushing required files to device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Pushing update file to device sdcard - this may take a few minutes...
error: device not found
error: device not found
Now wipe and apply rootedupdate.zip from the recovery image menu.
error: device not found
Click to expand...
Click to collapse
Then I found this post - which brought me to the update.zip work around.
Here I got the following error:
E:can't open /cache/recovery/command
Install from sdcard
finding update package
opening update package
verifying update package
e: failed to verify whole file signature
E: signature verification failed.
Installation aborted.
I've been struggling with this device for ages.
So any help would be very much appreciated!
[SIZE=+2]This thread has been created for Questions & Answers/Troubleshooting[/SIZE]
[SIZE=+2]Specific to LiquidSmooth Togari-GPE[/SIZE]
{
"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"
}
LiquidSmooth Togari-GPE
Please feel free to share issues, questions and offer help
It is always best to thank a ROM OP, in lieu of simply posting "Thank you".
Please keep discussion focused, on the topic described in the OP
Will revolution kernel work for this ROM?
CCJ22 said:
Will revolution kernel work for this ROM?
Click to expand...
Click to collapse
Is there not one in the ROM?
no I dont think revolution will work,you could try DoonLords one?
blueether said:
Is there not one in the ROM?
no I dont think revolution will work,you could try DoonLords one?
Click to expand...
Click to collapse
I didn't look to see if there was one. A bit new to this. So far, I've gotten as far as unlocking the bootloader following your guide.
CCJ22 said:
I didn't look to see if there was one. A bit new to this. So far, I've gotten as far as unlocking the bootloader following your guide.
Click to expand...
Click to collapse
Open the zip in 7zip etc and pull out the boot.img and save in the firmware folder of flashtool
boot the phone into fastboot mode (hold the vol up key when connecting to PC while powered off)
hit the flash icon in flashtool and select fastboot
change to the correct dir and select boot.img
click open and it should flash a kernel with recovery
flash rom from recovery as instructed in OP
blueether said:
Open the zip in 7zip etc and pull out the boot.img and save in the firmware folder of flashtool
boot the phone into fastboot mode (hold the vol up key when connecting to PC while powered off)
hit the flash icon in flashtool and select fastboot
change to the correct dir and select boot.img
click open and it should flash a kernel with recovery
flash rom from recovery as instructed in OP
Click to expand...
Click to collapse
Holy **** something that makes sense for once. OK I am going to try this
---------- Post added at 07:29 PM ---------- Previous post was at 07:14 PM ----------
Here is what I got back from flashtool
08/018/2014 17:18:27 - INFO - <- This level is successfully initialized
08/018/2014 17:18:27 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
08/018/2014 17:18:28 - INFO - Device disconnected
08/018/2014 17:18:49 - INFO - Device connected in fastboot mode
08/019/2014 17:19:20 - INFO - Selected null
08/019/2014 17:19:20 - INFO - Flash canceled
08/026/2014 17:26:03 - INFO - Selected system (system.img or system.sin): C:\Flashtool\firmwares\boot.img
08/026/2014 17:26:03 - INFO - Flashing selected system
08/026/2014 17:26:04 - INFO - Please check the log before rebooting into system
08/027/2014 17:27:01 - INFO - Device will now exit fastboot mode and start booting into system
08/027/2014 17:27:02 - INFO - Device disconnected
The section where it says check the log before rebooting into system, there is no log on my phone.
And phone currently stuck on google logo as if it's trying to boot up.
---------- Post added at 07:36 PM ---------- Previous post was at 07:29 PM ----------
Well the good news is, it looks like it took a boot.img finally.
Bad news is that it's stuck on the google startup
CCJ22 said:
Holy **** something that makes sense for once. OK I am going to try this
---------- Post added at 07:29 PM ---------- Previous post was at 07:14 PM ----------
Here is what I got back from flashtool
08/018/2014 17:18:27 - INFO - <- This level is successfully initialized
08/018/2014 17:18:27 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
08/018/2014 17:18:28 - INFO - Device disconnected
08/018/2014 17:18:49 - INFO - Device connected in fastboot mode
08/019/2014 17:19:20 - INFO - Selected null
08/019/2014 17:19:20 - INFO - Flash canceled
08/026/2014 17:26:03 - INFO - Selected system (system.img or system.sin): C:\Flashtool\firmwares\boot.img
08/026/2014 17:26:03 - INFO - Flashing selected system
08/026/2014 17:26:04 - INFO - Please check the log before rebooting into system
08/027/2014 17:27:01 - INFO - Device will now exit fastboot mode and start booting into system
08/027/2014 17:27:02 - INFO - Device disconnected
The section where it says check the log before rebooting into system, there is no log on my phone.
And phone currently stuck on google logo as if it's trying to boot up.
---------- Post added at 07:36 PM ---------- Previous post was at 07:29 PM ----------
Well the good news is, it looks like it took a boot.img finally.
Bad news is that it's stuck on the google startup
Click to expand...
Click to collapse
My log looks like this when flashing a boot.img
Code:
09/026/2014 13:26:14 - INFO - Device connected in fastboot mode
09/029/2014 13:29:57 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\charles\Downloads\RevolutionKernel-ZU-v1.1.img
09/029/2014 13:29:57 - INFO - Flashing selected kernel
09/029/2014 13:29:59 - INFO - sending 'boot' (12102 KB)...
09/029/2014 13:29:59 - INFO - OKAY [ 0.461s]
09/029/2014 13:29:59 - INFO - writing 'boot'...
09/029/2014 13:29:59 - INFO - OKAY [ 0.813s]
09/029/2014 13:29:59 - INFO - finished. total time: 1.274s
09/029/2014 13:29:59 - INFO - FASTBOOT Output:
sending 'boot' (12102 KB)...
OKAY [ 0.461s]
writing 'boot'...
OKAY [ 0.813s]
finished. total time: 1.274s
09/029/2014 13:29:59 - INFO - Please check the log before rebooting into system
09/030/2014 13:30:02 - INFO - Device will now exit fastboot mode and start booting into system
09/030/2014 13:30:02 - INFO - Device disconnected
so it looks like it's not flashing?
---------- Post added at 03:15 PM ---------- Previous post was at 02:54 PM ----------
maybe it's worth going to the commandline to flash see http://forum.xda-developers.com/showthread.php?t=2579005
blueether said:
My log looks like this when flashing a boot.img
Code:
09/026/2014 13:26:14 - INFO - Device connected in fastboot mode
09/029/2014 13:29:57 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\charles\Downloads\RevolutionKernel-ZU-v1.1.img
09/029/2014 13:29:57 - INFO - Flashing selected kernel
09/029/2014 13:29:59 - INFO - sending 'boot' (12102 KB)...
09/029/2014 13:29:59 - INFO - OKAY [ 0.461s]
09/029/2014 13:29:59 - INFO - writing 'boot'...
09/029/2014 13:29:59 - INFO - OKAY [ 0.813s]
09/029/2014 13:29:59 - INFO - finished. total time: 1.274s
09/029/2014 13:29:59 - INFO - FASTBOOT Output:
sending 'boot' (12102 KB)...
OKAY [ 0.461s]
writing 'boot'...
OKAY [ 0.813s]
finished. total time: 1.274s
09/029/2014 13:29:59 - INFO - Please check the log before rebooting into system
09/030/2014 13:30:02 - INFO - Device will now exit fastboot mode and start booting into system
09/030/2014 13:30:02 - INFO - Device disconnected
so it looks like it's not flashing?
---------- Post added at 03:15 PM ---------- Previous post was at 02:54 PM ----------
maybe it's worth going to the commandline to flash see http://forum.xda-developers.com/showthread.php?t=2579005
Click to expand...
Click to collapse
I'll try command line
Patiently Waiting...
It appears you might be the first confirmed ZU GPE owner to root??
Sitting back and watching it all unfold.
My ZU Gpe:
C6806, KOT49H.S2.2052, 4.4.2
I only want to root so i can install Xposed Framework... But I don't want anything about my stock ROM to be negatively affected.
digitalbenny said:
It appears you might be the first confirmed ZU GPE owner to root??
Sitting back and watching it all unfold.
My ZU Gpe:
C6806, KOT49H.S2.2052, 4.4.2
I only want to root so i can install Xposed Framework... But I don't want anything about my stock ROM to be negatively affected.
Click to expand...
Click to collapse
No, there was a rus when they first cone out, and I think one or two even bricked them in the first few days trying to flash things or even raw write to the sd card with dd
Regardless, after a thorough search I have found no definitive answer to successful root of a GPe
Sent from my C6806_GPe using Tapatalk
digitalbenny said:
Regardless, after a thorough search I have found no definitive answer to successful root of a GPe
Sent from my C6806_GPe using Tapatalk
Click to expand...
Click to collapse
Agreed, I haven't found ONE person either.
Except myself at this point.
I actually thought I bricked my device at one point. A-lot of trial and error. There needs to be a better thread for us GPE owners on how to root I will admit.
Took me 2 days (not literally but roughly between stopping for work, eat, ect...)
Where usually it would only take me 30 minutes to root a device.
CCJ22 said:
Agreed, I haven't found ONE person either.
Except myself at this point.
I actually thought I bricked my device at one point. A-lot of trial and error. There needs to be a better thread for us GPE owners on how to root I will admit.
Took me 2 days (not literally but roughly between stopping for work, eat, ect...)
Where usually it would only take me 30 minutes to root a device.
Click to expand...
Click to collapse
was there anything wrong with the instruction I wrote? anything that needs changing? anything you would add?
I can write up those instructions again as a guide thread if nothing need adding.
Oh you don't need root to flash a ROM just unlocked BL and recovery
blueether said:
was there anything wrong with the instruction I wrote? anything that needs changing? anything you would add?
I can write up those instructions again as a guide thread if nothing need adding.
Oh you don't need root to flash a ROM just unlocked BL and recovery
Click to expand...
Click to collapse
Nope yours are the one that helped cause the other "official" instructions were fairly worthless.
OK guys did any of you successfully flash liquid on your gpe device? Seeing as the mod locked the Dev thread
Sent from my Nexus 5 using Tapatalk
deadman96385 said:
OK guys did any of you successfully flash liquid on your gpe device? Seeing as the mod locked the Dev thread
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Bit rough locking the thread...
There should be nothing in there that could hard brick the GPe phone is there? I thought I've seen someone that has even flashed a ZU kernel to their GPe and the worst that happened was a boot failure. I'ts not as if you are flashing FTFs with different partition layouts, the .zip should be using named partitions - thus relativity safe?
Are you pulling the device tree from CM?
I just built a Carbon build for the GPe (CM device tree) and it boots and runs well except for MMS and incoming calls by the sounds from a tester.
Good luck getting it unlocked.
ps I cant test my or your GPe builds as I don't have one either.
pps See http://forum.xda-developers.com/showthread.php?t=2644346&page=3 for CM11 and Carbon on the GPe, and maybe pm @CCJ22 and see if they want to test liquid
blueether said:
Bit rough locking the thread...
There should be nothing in there that could hard brick the GPe phone is there? I thought I've seen someone that has even flashed a ZU kernel to their GPe and the worst that happened was a boot failure. I'ts not as if you are flashing FTFs with different partition layouts, the .zip should be using named partitions - thus relativity safe?
Are you pulling the device tree from CM?
I just built a Carbon build for the GPe (CM device tree) and it boots and runs well except for MMS and incoming calls by the sounds from a tester.
Good luck getting it unlocked.
ps I cant test my or your GPe builds as I don't have one either.
pps See http://forum.xda-developers.com/showthread.php?t=2644346&page=3 for CM11 and Carbon on the GPe, and maybe pm @CCJ22 and see if they want to test liquid
Click to expand...
Click to collapse
Yes i pulled from the cm tree, and yeah nothing in it could hardbrick the device, and thanks for the suggestion ill send a pm.
PM received, will flash and test on GPE.
[TUT] unlock bootloader, TWRP, root xperia m4 aqua [complete step]
check first by this code use phone dialler
*#*#7378423#*#* , if bootloader unlocked = yes , so you can root it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
must download it first
1. flashtool -0.9.18.4-windows > https://mega.nz/#!ThcRmQwD!x_X-U6g8bsucC5d6O5z0U7KK2W69LzrkVbBqfIubhdI
2. adb > https://mega.nz/#!ywUwFLpK!LmlAnwl8AS27wJzNjqBF7vpfvJHSz5pGer-XHOIVF6o
3. twrp > https://mega.nz/#!r8EWGQDD!nYOAC4HuQbYPx1SVl5J7pQnch_h8clEKaCP4uHuAXVg
4. supersu > https://mega.nz/#!C89nzC4L!F6yFyCqexTmi_EWQv9mTB-C1Mz_aKIS4-sBdULURJ7g
1. go to http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
2. chose type "M" and finish this until get key
3. save key code in file "txt" and rename it "ulcode.txt"
4. install flashtool -0.9.18.4-windows
5. activation USB debug in mobile first
6. connect mobile to PC via USB (DON'T UNPLUG te USB before DONE)
7. run flashtool wait until finish, chose option on top "devices>check drivers"
copy the devices code , my code is "YT911335HE"
INSTALLING TWRP
1. go to C:/flashtool/custom/mydevices/(here), create a new folder and rename with your device code
2. copy ulcode.txt and paste in your device code folder
3. close flashtool
4. create a new folder in C:/(here) rename it "adb" then extract file "adb tool fastboot xperia m4 aqua.zip" and copy file "recovery.img" in C:/adb/(here)
5. run flashtool and chose flash icon, click "fastbood mode" > OK , click "mode>reboot into flashtool mode (via ADB)".wait until finish
6. chose BLU icon wait until finish, unplug the mobile usb from PC and plug with hold Vol- , now chose unlock
7. go to folder "adb", typed cmd at addres bar (to open CMD)
8. paste this code "fastboot flash recovery recovery.img" in CMD, and ENTER, wait until finish
(unplug mobile and plug again with hold vol+ button if ADB tell waiting device)
This if finish intalling TWRP
DONE, TWRP installed but not ROOTED
ROOT
1. run TWRP by press " power and Vol- ", after you see logo sony, release "power" and press " vol- " twice, wait until finish
2. in TWRP mode connect it via USB to PC and send file "UPDATE-SuperSU-v2.46.zip"
3. install "UPDATE-SuperSU-v2.46.zip" by TWRP, wait until finish
DONE, TWRP installed and ROOTed
enjoy it
original source
http://forum.xda-developers.com/m4-aqua/general/guide-t3130092
http://forum.xda-developers.com/m4-aqua/development/recovery-twrp-touch-recovery-sony-m4-t3229873
trying this now. Will update with outcome.
*update*
I cannot get further than the CMD, this is my error:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30050 KB)...
OKAY [ 1.010s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.015s
*UPDATE*
This tutorial works just needed some help with the Bootlocker.
Primal09 said:
trying this now. Will update with outcome.
Click to expand...
Click to collapse
good luck
Primal09 said:
trying this now. Will update with outcome.
*update*
I cannot get further than the CMD, this is my error:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30050 KB)...
OKAY [ 1.010s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.015s
Click to expand...
Click to collapse
same error here. any solution?
Primal09 said:
trying this now. Will update with outcome.
*update*
I cannot get further than the CMD, this is my error:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30050 KB)...
OKAY [ 1.010s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.015s
Click to expand...
Click to collapse
i think your internal not enough
check the update , i am sory to lte give manual step image :good:
Primal09 said:
trying this now. Will update with outcome.
*update*
I cannot get further than the CMD, this is my error:
c:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (30050 KB)...
OKAY [ 1.010s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.015s
Click to expand...
Click to collapse
As i know that happens if you're Bootloader isn't unlocked, i have the same problem. (My BL cannot be unlocked :/)
CoreyHUN said:
As i know that happens if you're Bootloader isn't unlocked, i have the same problem. (My BL cannot be unlocked :/)
Click to expand...
Click to collapse
ah ya,you right ?
CoreyHUN said:
As i know that happens if you're Bootloader isn't unlocked, i have the same problem. (My BL cannot be unlocked :/)
Click to expand...
Click to collapse
It says that it is unlocked though.
Primal09 said:
It says that it is unlocked though.
Click to expand...
Click to collapse
are u sure that it is unlocked? there are 3 kinds of status:
Bootloader unlock allowed: No - u can't unlock BL
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
Bootloader unlocked: Yes - BL is unlocked
silencar said:
are u sure that it is unlocked? there are 3 kinds of status:
Bootloader unlock allowed: No - u can't unlock BL
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
Bootloader unlocked: Yes - BL is unlocked
Click to expand...
Click to collapse
agree with you ?
silencar said:
are u sure that it is unlocked? there are 3 kinds of status:
Bootloader unlock allowed: No - u can't unlock BL
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
Bootloader unlocked: Yes - BL is unlocked
Click to expand...
Click to collapse
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
This is what mine said before I unlocked the bootloader.
Then I unlocked it using the method in this tutorial.
in me it's work, follow the step carefully
Primal09 said:
Bootloader unlock allowed: Yes - u can unlock BL, BUT its not unlocked yet
This is what mine said before I unlocked the bootloader.
Then I unlocked it using the method in this tutorial.
Click to expand...
Click to collapse
this tutorial i made becouse i never done to root, i try the other tutorial and error
.
so i try with my own metode (this tutorial) and yoi xan see the TWRP in my mobile phone. it's work
Primal09 said:
This is what mine said before I unlocked the bootloader.
Then I unlocked it using the method in this tutorial.
Click to expand...
Click to collapse
ok, u've checked ur BL status before the procedure, but its more important whats the status after the unlock procedure - did u recheck it afterwards? Does it now show that it is unlocked?
silencar said:
ok, u've checked ur BL status before the procedure, but its more important whats the status after the unlock procedure - did u recheck it afterwards? Does it now show that it is unlocked?
Click to expand...
Click to collapse
This is what I get when I check the status.
It did not have Rooting Status the last time if I remember correctly.
Primal09 said:
This is what I get when I check the status.
Click to expand...
Click to collapse
"unavailable" doesn't sound that good
and I have to correct myself - there are 4 kinds of Status:
...
4. UNAVAILABLE
sth went wrong with the unlocking .. for now u have to get the BL status to 'unlocked' (I dont know how)
when this is done, the rooting procedure has to be redone and should work then.
--- Update: ---
what I have found, somebody with the same problem in this thread http://forum.xda-developers.com/m4-aqua/general/guide-t3130092/post63328460
xperia m4 aqua said:
Hi XDA...
Another note, remember to remove the 0x on the bootloader code when creating ulcode file, I proceeded with it in place and it gave me "Rooting Status: Unavailable"
It has been pointed out on this thread how to recover, but if someone runs into this problem: you have plug in the phone again in flash mode (vol down then plug in), click BLU, when relock wizard appears, go back to ulcode file and edit the 0x out, then relock, then unlock again (hope this helps someone new to xperia world like me )
Click to expand...
Click to collapse
It may help u .. or u will find the solution in the mentioned thread
so there is still hope for u
thanks a lot for this tutorial ! work great for me..
what for xposed ? the phone is able to receive it ?
amaeli said:
thanks a lot for this tutorial ! work great for me..
what for xposed ? the phone is able to receive it ?
Click to expand...
Click to collapse
can you send screen shoot? . just make sure if this metode work great ?
ianthok said:
can you send screen shoot? . just make sure if this metode work great
Click to expand...
Click to collapse
I'm not allowed to post screenshot on thread, sended to you at Private message
amaeli said:
I'm not allowed to post screenshot on thread, sended to you at Private message
Click to expand...
Click to collapse
well done ?
I tried to root this phone and it then wouldn't boot. Then I tried flashing stuff mainly using fastboot to get it to boot again. Nothing seems to be working or flashing properly. all kinds of different errors when flashing.
Sideloading an ots results in errors as well.
I don't think it's hard bricked cause fastboot works but the phone is not accepting anything.
Is there a proper method to flashing this phone ? Flashing back to stock that is.
I can install a custom rom but can't flash back to stock.
I've never ever had a problem flashing any other phone until this one. And why is Motorola so unfriendly ??
rogerrulez said:
I tried to root this phone and it then wouldn't boot. Then I tried flashing stuff mainly using fastboot to get it to boot again. Nothing seems to be working or flashing properly. all kinds of different errors when flashing.
Sideloading an ots results in errors as well.
I don't think it's hard bricked cause fastboot works but the phone is not accepting anything.
Is there a proper method to flashing this phone ? Flashing back to stock that is.
I've never ever had a problem flashing any other phone until this one. And why is Motorola so unfriendly ??
Click to expand...
Click to collapse
Bootloader is unlocked?
sd_shadow said:
Bootloader is unlocked?
Click to expand...
Click to collapse
Yes.
rogerrulez said:
Yes.
Click to expand...
Click to collapse
Do you have a Windows 7 pc?
Sent from my sailfish using XDA Labs
---------- Post added at 03:10 AM ---------- Previous post was at 03:07 AM ----------
Did you try following this?
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-install-official-oreo-t3768712
Sent from my sailfish using XDA Labs
sd_shadow said:
Do you have a Windows 7 pc?
Sent from my sailfish using XDA Labs
---------- Post added at 03:10 AM ---------- Previous post was at 03:07 AM ----------
Did you try following this?
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-install-official-oreo-t3768712
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
Windows 10 but I think my laptop is win7.
Yeah I tried that before I think. And that didn't take either.
If you have a Windows 7 pc, try RSD Lite and the firmware from link that i just posted
RSD Lite links in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my sailfish using XDA Labs
rogerrulez said:
Windows 10 but I think my laptop is win7.
Yeah I tried that before I think. And that didn't take either.
Click to expand...
Click to collapse
I can try it again tho.
sd_shadow said:
If you have a Windows 7 pc, try RSD Lite and the firmware from link that i just posted
RSD Lite links in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I have tried rsd lite as well but it gives decompress file size errors.
sd_shadow said:
If you have a Windows 7 pc, try RSD Lite and the firmware from link that i just posted
RSD Lite links in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I just tried this method again and this was the result with just trying to flash the bootloader:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (7792 KB)...
OKAY [ 0.228s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image rpm failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image pmic failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.513s
rogerrulez said:
I just tried this method again and this was the result with just trying to flash the bootloader:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (7792 KB)...
OKAY [ 0.228s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image rpm failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image pmic failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.513s
Click to expand...
Click to collapse
What does the complete text on the phone say?
Sent from my PH-1 using XDA Labs
sd_shadow said:
What does the complete text on the phone say?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
What do you mean ? The info on the bootloader screen ?
rogerrulez said:
I have tried rsd lite as well but it gives decompress file size errors.
Click to expand...
Click to collapse
The decompression error is likely a bad download
Sent from my PH-1 using XDA Labs
---------- Post added at 03:30 AM ---------- Previous post was at 03:29 AM ----------
rogerrulez said:
What do you mean ? The info on the bootloader screen ?
Click to expand...
Click to collapse
Yes
Sent from my PH-1 using XDA Labs
sd_shadow said:
The decompression error is likely a bad download
Sent from my PH-1 using XDA Labs
---------- Post added at 03:30 AM ---------- Previous post was at 03:29 AM ----------
Yes
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rogerrulez said:
View attachment 4485429
Click to expand...
Click to collapse
Is that pic too small ?
That would be great if i could read any of that.
Sent from my PH-1 using XDA Labs
sd_shadow said:
That would be great if i could read any of that.
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
rogerrulez said:
Click to expand...
Click to collapse
When I upload the pic it gets downsized to 9.8k How can I upload and use a larger photo ?
rogerrulez said:
When I upload the pic it gets downsized to 9.8k How can I upload and use a larger photo ?
Click to expand...
Click to collapse
Save to google drive, and share
Sent from my PH-1 using XDA Labs
---------- Post added at 03:52 AM ---------- Previous post was at 03:51 AM ----------
And select create link
Sent from my PH-1 using XDA Labs
sd_shadow said:
Save to google drive, and share
Sent from my PH-1 using XDA Labs
---------- Post added at 03:52 AM ---------- Previous post was at 03:51 AM ----------
And select create link
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
https://drive.google.com/file/d/1gNDW2VSr5lEWzT6wHqwDIPtNiGyMeIag/view?usp=sharing
I just tried flashing one of those files in rsd lite and gave this error again:
Failed flashing process. 3/32 flash partition "gpt bin"
Hi there,
The phone data was somehow disabled for no reason, I tried to enable mobile data and roaming, but it did not work.
In addition,
- "Developer options" was also disabled -- the options in "Developer options" disappeared within second after I entered it and the screen went blank, except "Developer options" remaining on the top;
- centre (homescreen) and right (opened apps) buttons in the navigation on the bottom of the phone were stuck, but left button (return) was still working.
To fix this issue, I booted into recovery mode and tried
- wiping cache and dalvik cache;
- repairing and resizing system, vendor, userdata, cache, dalvik cache partitions;
- (re)mounting the above 5 partitions,
but to no avail.
I checked the debloater and made sure that no system apps were removed via debloater.
I changed vendor partition to "ext2" and back to "ext4". And I rebooted the device to system, which subsequently booted into fastboot mode instead.
How to fix it?
Recovery is still usable.
Thanks in advance.
May you need any further information, please feel free to contact me.
Regards,
change of file system is same as formatting. restore vendor from backup
aIecxs said:
change of file system is same as formatting. restore vendor from backup
Click to expand...
Click to collapse
Unfortunately, I do not have vendor backup of this OS...
Would it be possible to flash / reinstall
- vendor.new.dat.br;
- vendor.patch.dat;
- vendor.transfer.list;
from the rom
or other ways to fix it?
Why do you have TWRP in first place? Next time backup beforehand, thats the purpose of TWRP
you need to convert into raw vendor.img first
https://github.com/xpirt/sdat2img
Code:
brotli --decompress vendor.new.dat.br -o vendor.new.dat
python sdat2img.py vendor.transfer.list vendor.new.dat vendor.img
then you can flash from fastboot or adb
Code:
fastboot flash vendor vendor.img
or flash the whole ROM from stock recovery and start from scratch.
python sdat2img.py vendor.transfer.list vendor.new.dat vendor.img
produced an error
Code:
File "sdat2img.py", line 1
Python 3.11.1 (v3.11.1:a7a450f84a, Dec 6 2022, 15:24:06) [Clang 13.0.0 (clang-1300.0.29.30)] on darwin
^
SyntaxError: invalid syntax
maybe wrong line encoding, or that python is too new? can't tell you why it failed. probably not your fault. ask in support thread. https://forum.xda-developers.com/t/...-7-o-unpack-re-pack-android-dat-files.2978952
meanwhile you can send me link to firmware so I can convert for you.
Following hours of work, I was finally able to reboot into system after flashing vendor.img created by sdat2img.
Thank you very much for your help.
Code:
Sending sparse 'vendor' 1/1 (414215 KB) OKAY [ 9.252s]
Writing 'vendor' OKAY [ 68.242s]
Finished. Total time: 78.368s
But the issues remained in the system newly accessible
- I cannot use data network;
- two buttons (centre and right) at the bottom are not usable either.
I used the same method to restore system.img.
adb push failed
Code:
adb: error: failed to copy 'system.img' to '/dev/block/bootdevice/by-name/system': remote write failed: No space left on device
system.img: 1 file pushed, 0 skipped. 32.3 MB/s (3221225472 bytes in 95.099s)
But fastboot flash system system.img was ok.
Code:
Sending sparse 'system' 1/3 (515380 KB) OKAY [ 13.746s]
Writing 'system' OKAY [ 4.438s]
Sending sparse 'system' 2/3 (510053 KB) OKAY [ 13.414s]
Writing 'system' OKAY [ 3.462s]
Sending sparse 'system' 3/3 (264688 KB) OKAY [ 7.015s]
Writing 'system' OKAY [192.959s]
Finished. Total time: 240.702s
But even after system.img was restored back, data and navigation bar problems were not solved.
the adb error 'No space left on device' is strange. I guess it tried to copy a file into a dir (/dev/block/bootdevice/by-name/system/system.img) instead of writing partition. maybe some bug in adb. I have never tested. but it seems bootloader is unlocked so you can just flash from fastboot, as you finally did.
you can try to flash other partitions from stock firmware, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msadp. exist there some txt or xml file with mapping, partition label = file name?
if that doesn't help, maybe it is related to bootloader unlocking?
https://forum.xda-developers.com/t/how-do-i-recover-the-imei-after-unlocking-the-bootloader.4536397
aIecxs said:
the adb error 'No space left on device' is strange. I guess it tried to copy a file into a dir (/dev/block/bootdevice/by-name/system/system.img) instead of writing partition. maybe some bug in adb. I have never tested. but it seems bootloader is unlocked so you can just flash from fastboot, as you finally did.
you can try to flash other partitions from stock firmware, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msadp. exist there some txt or xml file with mapping, partition label = file name?
if that doesn't help, maybe it is related to bootloader unlocking?
https://forum.xda-developers.com/t/how-do-i-recover-the-imei-after-unlocking-the-bootloader.4536397
Click to expand...
Click to collapse
In the stock rom, it seems that there were not many flashable files, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msad...
{
"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"
}
that is only update ROM. what you need is full firmware for blank flash.
I re-downloaded and extracted the rom and it seems it is just the same.
yes, that's the difference between update ROM and full firmware. crystal ball says, you want firmware for OnePlus2?
https://www.full-repair-firmware.com/p/oneplus-2.html
or Xiaomi maybe?
https://xiaomifirmwareupdater.com/miui
there is always two files. smaller one is OTA update ROM (tag: recovery)
bigger file is full ROM/firmware bundle (tag: fastboot)
wenyendev said:
In the stock rom, it seems that there were not many flashable files, like apdp, bluetooth, dpo, fsc, fsg, hypod, modem, msad...
View attachment 5814327
View attachment 5814329
View attachment 5814331
View attachment 5814333
Click to expand...
Click to collapse
It looks like what you're showing is a custom ROM, you may need to flash a stock ROM, that contains a stock vendor image too, to fix things.
yeah we might able to provide link, but OP won't tell us what device brand/model he's talking about...