Related
Now that the official Nexus 10 ClockworkMod Recovery 6.0.1.6 images have been released the recovery images are obsolete, thanks to everyone has tested the images I released, and all the feedback ! The official recovery images can be found here.
Here is Clockworkmod Recovery 6.0.1.5 (Non-Touch) and 6.0.1.5 (Touch) for the Nexus 10 ! I extracted the stock recovery.img from the Nexus 10 Factory Image then ran it through clockworkmod builder.
Update: Hopefully fixed recovery.fstab mount points that were causing reboots when accessing "Mounts and Storage" options.
It can be downloaded from here:
Non-Touch Version
https://docs.google.com/open?id=0B1S0LCuXCnnmNFgyeHhGQ0Z0cEk
Touch Version
https://docs.google.com/open?id=0B1S0LCuXCnnmbnNpMW9Sc0RSU0E
This has not been tested yet on an actual device I need testers willing to test the recovery image and report back there findings!
It can be tested by flashing the recovery using fastboot to avoid bricking your device if it doesn't work use the fastboot boot command only flash it when it has been thoroughly tested!
Code:
fastboot boot recovery /path/to/<recovery>.img
fastboot reboot
Once again thanks to POORCOLLEGEGUY and all the rest of the XDA news writers for featuring this on the portal on November 15, 2012!
Damn! Already! I can not wait to get my nexus 10.
Once it has been tested working well are there any plans for the touch version to be released?
I've been looking forward to this. Thanks
Good work, thanks! If something does go wrong can we just use fastboot to flash back the stock recovery?
EniGmA1987 said:
Once it has been tested working well are there any plans for the touch version to be released?
Click to expand...
Click to collapse
Yup I intend to try and release a touch version latter today if people want to test that as well :good:!
dr9722 said:
Good work, thanks! If something does go wrong can we just use fastboot to flash back the stock recovery?
Click to expand...
Click to collapse
Absolutely!
Definately bring it!! I test this for sure as soon as it comes in!
CWM for nexus 10
is there any news if CWM for nexus 10 is working nice?
Got my Nexus 10 this morning.
Initially the touch version seemed to be working but when I clicked "Mounts and storage", it displayed the menu for a few seconds and then the tablet rebooted.
Now it won't boot Gets stuck on the Nexus logo. Guess it's not as safe as it seemed!
piit79 said:
Got my Nexus 10 this morning.
Initially the touch version seemed to be working but when I clicked "Mounts and storage", it displayed the menu for a few seconds and then the tablet rebooted.
Now it won't boot Gets stuck on the Nexus logo. Guess it's not as safe as it seemed!
Click to expand...
Click to collapse
Did you flash the recovery or just boot it with the fastboot boot recovery /path/to/<recovery>.img command?
piit79 said:
Got my Nexus 10 this morning.
Initially the touch version seemed to be working but when I clicked "Mounts and storage", it displayed the menu for a few seconds and then the tablet rebooted.
Now it won't boot Gets stuck on the Nexus logo. Guess it's not as safe as it seemed!
Click to expand...
Click to collapse
Like Kevster said did you just boot from it using fastboot or did you flash it using fastboot. Either way I appreciate the feedback, sounds like I have to try and fix the mount points.
Sent from my SCH-I535 using xda premium
Edit: Can you provide any error messages you get or try connecting your tablet to the computer and use ADB to get a locate output
The-Kevster said:
Did you flash the recovery or just boot it with the fastboot boot recovery /path/to/<recovery>.img command?
Click to expand...
Click to collapse
I just booted recovery using the command above... Strange.
Anyway, all is well after re-flashing factory image.
---------- Post added at 03:13 PM ---------- Previous post was at 03:09 PM ----------
shimp208 said:
Like Kevster said did you just boot from it using fastboot or did you flash it using fastboot. Either way I appreciate the feedback, sounds like I have to try and fix the mount points.
Click to expand...
Click to collapse
Further to my reply above - CWM did show 4-5 essages about "Cannot mount <path to what looked like a file>"
Sorry I didn't write it down... Stupid me
Also, after it wouldn't boot I was lazy to debug so I didn't try attaching to adb logcat. I just wanted to play with my new toy
piit79 said:
I just booted recovery using the command above... Strange.
Anyway, all is well after re-flashing factory image.
---------- Post added at 03:13 PM ---------- Previous post was at 03:09 PM ----------
Further to my reply above - CWM did show 4-5 essages about "Cannot mount <path to what looked like a file>"
Sorry I didn't write it down... Stupid me
Also, after it wouldn't boot I was lazy to debug so I didn't try attaching to adb logcat. I just wanted to play with my new toy
Click to expand...
Click to collapse
I understand we all want to play when we get new things . Again thank you for testing, like I said sounds like I need to fix the mount points.
Sent from my SCH-I535 using xda premium
shimp208 said:
I understand we all want to play when we get new things . Again thank you for testing, like I said sounds like I need to fix the mount points.
Click to expand...
Click to collapse
Not sure if it is of any use but this is what "mount" shows in console:
Code:
/dev/block/platform/dw_mmc.0/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/efs /factory ext4 ro,nosuid,nodev,noatime,data=ordered 0 0
And
ls -l /dev/block/platform/dw_mmc.0/by-name/
Code:
lrwxrwxrwx root root 2012-11-15 09:37 boot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-11-15 09:37 cache -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-11-15 09:37 efs -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-11-15 09:37 metadata -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-11-15 09:37 misc -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-11-15 09:37 param -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-11-15 09:37 recovery -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-11-15 09:37 system -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-11-15 09:37 userdata -> /dev/block/mmcblk0p9
piit79 said:
Not sure if it is of any use but this is what "mount" shows in console:
Code:
/dev/block/platform/dw_mmc.0/by-name/system /system ext4 ro,relatime,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/cache /cache ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/userdata /data ext4 rw,nosuid,nodev,noatime,nomblk_io_submit,errors=panic,data=ordered 0 0
/dev/block/platform/dw_mmc.0/by-name/efs /factory ext4 ro,nosuid,nodev,noatime,data=ordered 0 0
And
ls -l /dev/block/platform/dw_mmc.0/by-name/
Code:
lrwxrwxrwx root root 2012-11-15 09:37 boot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-11-15 09:37 cache -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-11-15 09:37 efs -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2012-11-15 09:37 metadata -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-11-15 09:37 misc -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-11-15 09:37 param -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-11-15 09:37 recovery -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-11-15 09:37 system -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-11-15 09:37 userdata -> /dev/block/mmcblk0p9
Click to expand...
Click to collapse
Thank you very much for providing this information :highfive:! I was able to use this information to rebuild the recovery images (Touch and Non-Touch Versions) and fix the recovery.fstab mount points, they ones that were orginally generated in the first ones I ran through clockwork builder were wrong which was what caused your tablet to reboot when selecting the mounts and storage option.
Just received this good news...
Scheduled For Early Delivery On:Friday, 11/16/2012, By End of Day
Originally Scheduled For Delivery On:Monday, 11/19/2012, By End of Day
This has never happened with anything ive ever ordered before lol
i mean seriously and i didn't have to pay more to get it early? Pure awesomeness
I will be trying this out as soon as i get my nexus in tomorrow. Will let you know if i run into any issues.
In the non-touch-version (which I prefer), I was unable to access the "Apply zip from sdcard" menu. After selecting "Advanced Options", the N10 rebooted.
The touch version showed "Unable to mount /sdcard" when trying to access "Apply zip from sdcard" and rebooted 10-20 seconds after that.
No luck here either.
I'm running
adb boot D:\recovery-clockwork-touch-unofficial-6.0.1.5-mantaray.img
(this doesn't break the device or cause any future issues BTW!)
It rebooted into recovery but reboots on its own 10-20 seconds later.
Also adds a "Nexus 10" device to device manager but non of the drivers I have work. I have the SDK drivers and samsung drivers for mobile phones.
I need to root this device already
I suspect that root is going to be needed to fix the problems as I'm guessing it's encountering permission problems when accessing and manipulating files and directories necessary for recovery to perform it's various functions.
Sent from my SCH-I535 using xda premium
There are tools that do this automatically for you, but to date they only work on Windows and as a general rule of thumb it is a bad idea to blindly run scripts found on the internet on your computer, even if the author doesn't mean any harm, things can go wrong. Furthermore it is generally a good idea to actually learn how your device works rather than just using tools that do everything for you.
However if you do not feel up to the task, and are running Windows, you can use this automated tool instead if you want.
Fair warning: Flashing your TA partition is dangerous stuff, do this wrong and you can most certainly hard-brick your device. I will not take any responsibility at all for anything you deem might have (or might not have) been a result of these procedures, be it bricked devices, lost DRM-keys, your milk going sour, your computer exploding, your friends computer exploding, repetitive stress injury, the loss of any limbs and/or digits or literally anything else.
General requirements before getting started:
Android SDK platform-tools (namely ADB)
Rooted Sony Xperia Z1
For this guide I am going to assume you know how ADB works and that you know how to get access to ADB in your preferred operating system.
Backing up your TA partition
For this part you will need both a locked and rooted Xperia Z1. Ok, you don't actually need a locked device, but the most common reason for backing up this partition is to keep your DRM-keys intact, and this means your device needs to be locked.
Steps:
Open your favourite terminal emulator
Acquire a shell with your device (adb shell)
Acquire a root shell with your device (su)
cd /sdcard/
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
Verify that the hashes match!
Leave root shell (exit)
Leave device shell (exit)
adb pull /sdcard/TA.img TA.img
Use your favourite tool to verify the hash hasn't changed after copying to your computer (openssl md5 TA.img)
Put this file (and the hash) in a safe place, this is your TA backup.
Restoring your TA partition
For this part you will need your TA partition backup and the matching rooted Xperia Z1 (literally the exact same device you got the backup from). You will also need to restore an unmodified stock boot partition (a boot partition from any ROM claiming to work on locked bootloaders will do fine) prior to restoring the TA partition backup, otherwise you will not be able to boot after restoring the TA partition. Also, do not attempt this with someone elses TA partition, I haven't personally tried it but I am told you will hard-brick your device! It sucks but if you've lost your DRM keys then you will not be able to recover them.
Steps:
Open your favourite terminal emulator
adb push TA.img /sdcard/TA.img
Acquire a shell with your device (adb shell)
Acquire a root shell with your device (su)
cd /sdcard/
If you have the hash you read during the backup procedure stored, now is a good time to verify that it still matches the backup
dd if=TA.img of=/dev/block/platform/msm_sdcc.1/by-name/TA
md5 /dev/block/platform/msm_sdcc.1/by-name/TA TA.img
Make absolutely certain that the hashes match!
If they don't, DO NOT REBOOT YOUR DEVICE!
Leave root shell (exit)
Leave device shell (exit)
Done!
Good luck! If I have helped you, please click the thanks button!
there is a good reason why there is a script to do this...
the TA is VERY VERY DANGEROUS AREA... any minor mistake and you WILL BE LEFT with bricked device...
DO NOT TRY MANUAL WAY!
one small mistake in the partition layout (command typo) and you might wipe the bootloader or corrupt the partition table...
please i strongly advise that you DO NOT play with TA...
FYI this is the partition layout for the Z1:
Code:
[email protected]:/ # ls -l /dev/block/platform/msm_sdcc.1/by-name
ls -l /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-21 17:03 DDR -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-21 17:03 FOTAKernel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-21 17:03 LTALabel -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-21 17:03 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-21 17:03 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-21 17:03 alt_aboot -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-21 17:03 alt_dbi -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-21 17:03 alt_rpm -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-21 17:03 alt_s1sbl -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-21 17:03 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-21 17:03 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-21 17:03 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-21 17:03 boot -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-21 17:03 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1970-01-21 17:03 dbi -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-21 17:03 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-21 17:03 modemst1 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-21 17:03 modemst2 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-21 17:03 ramdump -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-21 17:03 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-01-21 17:03 s1sbl -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-21 17:03 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-21 17:03 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-21 17:03 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-21 17:03 userdata -> /dev/block/mmcblk0p25
thanks to @yeeson for fetching this info!
DooMLoRD said:
there is a good reason why there is a script to do this...
the TA is VERY VERY DANGEROUS AREA... any minor mistake and you WILL BE LEFT with bricked device...
DO NOT TRY MANUAL WAY!
one small mistake in the partition layout (command typo) and you might wipe the bootloader or corrupt the partition table...
please i strongly advise that you DO NOT play with TA...
FYI this is the partition layout for the Z1:
Code:
<partition layout for Xperia Z1>
thanks to @yeeson for fetching this info!
Click to expand...
Click to collapse
Thanks for the info mate, though I do understand your point I would like to point out that running random scripts on sensitive areas is in my opinion much more dangerous than actually knowing what you are doing, and really isn't something that should be promoted in general (I understand why it is in this case). I personally trust myself not to make those kinds of mistakes much more than I do some random person on the internet. Especially when options aren't provided for operating systems other than Windows I feel that this guide is still needed.
We should be teaching people, not simply providing a solution (to something which someone who doesn't know what he is doing should even be tinkering with to be honest).
Had forgotten about the named symlinks, thanks for that! Updated tutorial.
OMG !!! So many partitions. Is there a place where to find their purpose ?
One question please: waht does "TA" stand for ?
And finally: I agree... Such informations are HIGHLY dangerous in unexperienced hands. Sooooo easy to brick a phone...
bbkdhumm said:
OMG !!! So many partitions. Is there a place where to find their purpose ?
One question please: waht does "TA" stand for ?
And finally: I agree... Such informations are HIGHLY dangerous in unexperienced hands. Sooooo easy to brick a phone...
Click to expand...
Click to collapse
Aw come on guys, it's not that difficult of a guide to follow is it? Besides, how do you become experienced without ever trying? After all, this is a fairly technical forum.
Did you never notice posts by novices having problems following guides?
Envoyé depuis mon GT-I9300 avec Tapatalk 4
Rekoil said:
Aw come on guys, it's not that difficult of a guide to follow is it? Besides, how do you become experienced without ever trying? After all, this is a fairly technical forum.
Click to expand...
Click to collapse
I do agree with you completely.
When playing with partitions, manual way is the best way. And this is development forum. All possible info should be here. Noone should discourage you from posting any info, if you are warning the people that it's dangerous.
I seem to remember a time when people wouldn't host kernels or recoveries as update-able zips, because it didn't drive any knowledge into the users. Then, if something went wrong, they were ill equipped to deal with it. I'm all for automated tools, but see absolutely nothing wrong with sharing the manual know how.
Linux is best for all mods
Although I appreciate your efforts in creating this thread. I advice users to use this automatic tool and full of safety checks. It worked for me. And another thing, this is used to backup and restore your bootloader unlock status, drm keys and warranty!
http://forum.xda-developers.com/showthread.php?t=2292598
Greetings
Option58 said:
Although I appreciate your efforts in creating this thread. I advice users to use this automatic tool and full of safety checks. It worked for me. And another thing, this is used to backup and restore your bootloader unlock status, drm keys and warranty!
http://forum.xda-developers.com/showthread.php?t=2292598
Greetings
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2292598 said:
"Mac and Linux will not be supported."
Click to expand...
Click to collapse
Yeah, great option for Mac and Linux users.
Option58 said:
And another thing, this is used to backup and restore your bootloader unlock status, drm keys and warranty!
Click to expand...
Click to collapse
So does the manual method. In fact, I learned how to do it manually from studying that tool.
Rekoil said:
Yeah, great option for Mac and Linux users.
So does the manual method. In fact, I learned how to do it manually from studying that tool.
Click to expand...
Click to collapse
No one will ever learn without trying new things.
You can even break a phone by flashing it with proven programs not reading instructions carefully, so I find it OK to give the opportunity for the users not using windows especially as you have given good warnings.
Anyone have noted that in 5.34 commercial&journalist version ta file it's cust-reset.ta and in central europa simlock.ta?
Do I have to make a new TA backup after I have updated to .534 ?
Planet X said:
Do I have to make a new TA backup after I have updated to .534 ?
Click to expand...
Click to collapse
no
@ OP why /platform/msm_sdcc.1/by-name/TA why not point directly the mmcblk0p1 TA partition?
e.g.
This:- dd if=/dev/block/mmcblk0p1 of=TA.img
Instead of:-dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
I'm just nitpicking lol
Shaky156 said:
@ OP why /platform/msm_sdcc.1/by-name/TA why not point directly the mmcblk0p1 TA partition?
e.g.
This:- dd if=/dev/block/mmcblk0p1 of=TA.img
Instead of:-dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=TA.img
I'm just nitpicking lol
Click to expand...
Click to collapse
Both are fine, but in case a new phone comes to market that for some reason puts boot image at /dev/block/mmcblk0p1 and TA at /dev/block/mmcblk0p2 or something like that, I thought it was best to just point to the symlink instead, so as to definitely make it future proof.
Thank you for this thread. I have backed up my TA for my new Z1 and stored it away.
malty
Planet X said:
Do I have to make a new TA backup after I have updated to .534 ?
Click to expand...
Click to collapse
Desperanto86 said:
no
Click to expand...
Click to collapse
How sure is that? I noticed that my TA did change with the update to .534 (based on md5sum). Can I freely mix-and-match my different TA backups (from the same device of course) with whatever (official) kernel version? Are they perhaps forward-compatible only (perhaps for downgrade prevention or something) and I should really keep the oldest one?
iconoclastnet said:
How sure is that? I noticed that my TA did change with the update to .534 (based on md5sum). Can I freely mix-and-match my different TA backups (from the same device of course) with whatever (official) kernel version? Are they perhaps forward-compatible only (perhaps for downgrade prevention or something) and I should really keep the oldest one?
Click to expand...
Click to collapse
TA is CONSTANT like IMEI!
EDIT: Here's the recovery thread.
Original post:
So, let me preface this with the following statements:
I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices
So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-06 07:55 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6
I then used:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img
I then used the CWM Recovery Builder to build a basic recovery.
I took that image, pushed to /sdcard/rec.img and tried the following as root:
Code:
flash_image recovery /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
So I tried dd instead:
Code:
dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16
Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.
I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.
So if someone wouldn't mind pointing me in the right direction, that would be awesome.
Nobody?
METDeath said:
Nobody?
Click to expand...
Click to collapse
If you could upload the recovery.img, boot.img, as well as the output of "cat /proc/partitions", I'll have a custom recovery for you in as long as it takes for my computer to build it!
Also, if you could get me /proc/config.gz, that would be awesome.
cooldudezach said:
If you could upload the recovery.img, boot.img, as well as the output of "cat /proc/partitions", I'll have a custom recovery for you in as long as it takes for my computer to build it!
Also, if you could get me /proc/config.gz, that would be awesome.
Click to expand...
Click to collapse
Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.
It was literally two days outside of the return to store window too.
METDeath said:
Sadly, I was going to sell the phone... did a factory reset, that didn't end up so well. So fighting with ZTE to get it repaired (boot loop, displays ZTE logo then black screen). I can get the phone into FTM mode, but not recovery. I even made it a point to flash the original factory.img after every failed attempt.
It was literally two days outside of the return to store window too.
Click to expand...
Click to collapse
If you still have the phone, I can probably still save it. I've already saved 4 devices that are based on the same hardware this phone is (ZTE Awe, ZTE Sourcex2, ZTE Warp4g), and they were worse off
Especially if you can get into FTM mode, that means the boot.img is still functioning properly, just there is something causing the phone to loop. I'm assuming it loops while trying to get into recovery? Where did you get the factory.img?
---------- Post added at 11:53 AM ---------- Previous post was at 11:43 AM ----------
METDeath said:
So, let me preface this with the following statements:
I'm using Windows 7 x64 (Will eventually install a Unbuntu VM and set up a CM10.1 fork for a ROM)
I have not done this before, ever. I've always been the guy that just follows guides of proper devs to root my devices
So, I first needed to find the recovery partition, I found this thread. My by-name folder was in msm_sdcc.1
Code:
ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-01-06 07:55 aboot -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-01-06 07:55 boot -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1970-01-06 07:55 cache -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-01-06 07:55 fsg -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-01-06 07:55 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-01-06 07:55 misc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-01-06 07:55 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-01-06 07:55 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-01-06 07:55 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-01-06 07:55 persist -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-01-06 07:55 recovery -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-01-06 07:55 rpm -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-01-06 07:55 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-01-06 07:55 sbl2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-01-06 07:55 sbl3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-01-06 07:55 splash -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-01-06 07:55 ssd -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-01-06 07:55 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-01-06 07:55 tombstones -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-01-06 07:55 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-01-06 07:55 userdata -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-01-06 07:55 ztecfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-01-06 07:55 ztelk -> /dev/block/mmcblk0p6
I then used:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/recovery.img
I then used the CWM Recovery Builder to build a basic recovery.
I took that image, pushed to /sdcard/rec.img and tried the following as root:
Code:
flash_image recovery /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
flash_image /dev/block/mmcblk0p16 /sdcard/recv.img
error scanning partitions: No such file or directory
So I tried dd instead:
Code:
dd if=/sdcard/rec.img of=/dev/block/mmcblk0p16
Then attempted to reboot into recovery with adb... no dice, I then redump the recovery to see if it's still ~8MB instead of 16MB. Nope, back to 16MB.
I also tried using fastboot flash recovery while it was in the bootloader, also failed with the same results.
So if someone wouldn't mind pointing me in the right direction, that would be awesome.
Click to expand...
Click to collapse
I figured I'd go ahead and answer you problems/questions here.
First off, flash_image isn't going to work, stop using it. Second, fastboot flash doesn't work on this line of devices, again, stop using it.
When using dd, you should always zero out the partition first to make sure you aren't leaving behind anything from what was there before:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p16
The reason it's 'back' to 16MB, is because that is the size of the partition. It's just got a lot of 0's on the end. Everytime you pull it, it will always end up as a 16MB image. If you still have a copy of the stock recovery.img you pulled, I would appreciate a copy
cooldudezach said:
If you still have the phone, I can probably still save it. I've already saved 4 devices that are based on the same hardware this phone is (ZTE Awe, ZTE Sourcex2, ZTE Warp4g), and they were worse off
Especially if you can get into FTM mode, that means the boot.img is still functioning properly, just there is something causing the phone to loop. I'm assuming it loops while trying to get into recovery? Where did you get the factory.img?
---------- Post added at 11:53 AM ---------- Previous post was at 11:43 AM ----------
I figured I'd go ahead and answer you problems/questions here.
First off, flash_image isn't going to work, stop using it. Second, fastboot flash doesn't work on this line of devices, again, stop using it.
When using dd, you should always zero out the partition first to make sure you aren't leaving behind anything from what was there before:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p16
The reason it's 'back' to 16MB, is because that is the size of the partition. It's just got a lot of 0's on the end. Everytime you pull it, it will always end up as a 16MB image. If you still have a copy of the stock recovery.img you pulled, I would appreciate a copy
Click to expand...
Click to collapse
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
Thanks! So does your phone boot normally, or does it bootloop? I wasn't sure when you wrote that if you were just referring to the recovery boot or not. FTM is integrated with boot.img, which is why i am confused lol.
I'm just trying to figure out what's wrong exactly so I can get your phone up and running.
If you want to hop into irc chac #zte8930 on freenode, that's where I hang out, and where the devs for this group of phones also hangout.
For anyone looking in on this, the problem was fixed and there is now a PhilZ CWM for the phone.
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
is that can be use？i want to transplant a msm8960 device's rom so i need a custom recovery.
chongbos said:
is that can be use？i want to transplant a msm8960 device's rom so i need a custom recovery.
Click to expand...
Click to collapse
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
METDeath said:
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
Click to expand...
Click to collapse
so..can i flash this .img to my z995? is that offical or custom?
ATTACHED FILES
zte 995 stock recovery.zip - [Click for QR Code] (6.83 MB, 9 views)
thanks.sorry for my poor english!
---------- Post added at 10:13 AM ---------- Previous post was at 10:09 AM ----------
METDeath said:
Since I'm not the creator of the port I won't post it here, and it's on another Androidforums so not sure how XDA feels about linking to another forum. There is a group of guys creating ports for lots of MSM8960 devices over there though.
Click to expand...
Click to collapse
oh,i have been focus on this forum for a long time,and now i have found it.thank u a lot.
---------- Post added at 10:24 AM ---------- Previous post was at 10:13 AM ----------
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
btw.
can u help me?
i have an old device GT-i9008L.it's a custom-made device from GT-i9003.
For now im willing to transplant a custom rom so im making a custom recovery before it.
but i cant let recovery mount SDcard...maybe i dont know how to editor it.
can u help me?only transplant i9003's custom recovery can take it easy.
thanks. sorry for my poor english!
chongbos said:
so..can i flash this .img to my z995? is that offical or custom?
ATTACHED FILES
zte 995 stock recovery.zip - [Click for QR Code] (6.83 MB, 9 views)
btw.
can u help me?
i have an old device GT-i9008L.it's a custom-made device from GT-i9003.
For now im willing to transplant a custom rom so im making a custom recovery before it.
but i cant let recovery mount SDcard...maybe i dont know how to editor it.
can u help me?only transplant i9003's custom recovery can take it easy.
thanks. sorry for my poor english!
Click to expand...
Click to collapse
The attached is the official recovery for the ZTE Z995 Overture (code name becky) that was sold in the US, so it's in English, it's also not a flashable zip as it's just the output of the dd command from the shell compressed into a zip file for smaller size.
I'm afraid I'm not able to help much with creating your own custom recovery as I'm not a developer. Perhaps you should create your own thread with more details on your phone.
Your English is actually better than some native English speakers, so keep up the practice and good work!
METDeath said:
The attached is the official recovery for the ZTE Z995 Overture (code name becky) that was sold in the US, so it's in English, it's also not a flashable zip as it's just the output of the dd command from the shell compressed into a zip file for smaller size.
I'm afraid I'm not able to help much with creating your own custom recovery as I'm not a developer. Perhaps you should create your own thread with more details on your phone.
Your English is actually better than some native English speakers, so keep up the practice and good work!
Click to expand...
Click to collapse
hah，it's really funny to met u.
i will back contact u~~~~
thanks.
Hmmmm METdeath, perhaps you could enlighten me (pm) the whereabouts of said recovery and other useful info.
If wanted a custom recovery and ROM on this phone since day 1 . I kinda gave up on any hope for it. Please any information to lead me in the correct direction would be greatly appreciated.
METDeath said:
For anyone looking in on this, the problem was fixed and there is now a PhilZ CWM for the phone.
Click to expand...
Click to collapse
Where is a link to this recovery?
Does anybody know where to get a firmware for new ZTE devices, like Z995, Z993, z740 etc?
Hello Help PLZ!!
Hello, I have a softed bricked zte overture z995. I saw in one of your replies you are familiar with reflashing this ROM. Is there any possible way that you can help guide me in fixing this problem? I'm not too familiar with all the concepts. I will be forever grateful!!! THanks!
~Caleb
METDeath said:
Well, I dumped the stock img with dd, I am fairly sure I still the stock recovery (sooo many files, hopefully this is it, however, looking at the file size when zipped it may not be).
I also PM'd one of the guys from the root thread who may be able to help with .img files as well.
I still have the device, I'm using Win7 primarily, but have an Unbuntu VM that I was going to use to attempt to build a CM10 port for the phone.
Also, I have a fairly decent CPU (AMD Phenom II x6 2.8) so I don't mind doing the build work.
Click to expand...
Click to collapse
Updated first post with the URL to the recovery.
Hi friends,
I lost imei on my moto g5 because I had installed oreo 8.1 rome on it.
while I was trying to fix the imei on its stock rom that I had flash after flashing oreo 8.1.
I thought dhob -> /dev/block/mmcblk0p20
and hob -> /dev/block/mmcblk0p19 are the two files that contain all the data of IMEI and network.
so I searched on web and foun these two files of some other moto device. I went ahead and flashed these two files onto my file. which actually didn't resolve the issue. but gave me some more issue. now after doing this fingerprint stoped working.
Then I went ahead and ran fastboot clear all command from the cmd in fast boot thinking that it might remove these two file that I have flashed. but by doing that I lost wifi as well.
now the situation is this that there is no imei on my moto g5, wifi is not working, finger print senser is not working.
so finally i relocked the boot loader and thought maybe I will take it to service center and they will fix it. but they found that it is out of warranty and asked for money which is 80% cost of the mobile phone. actually they are telling me to replace the mother board.
I know there should be someone on XDA who can actually help me. I understand I have messed it real bad. But I really need this phone.
so this is my final request to all XDA members and all DEV's out there please help me.
According to my knowledge I will need the back up of some files from a working moto G5 cedric, That I can flash to my moto g5 cedric:
here are the files that I need:
aboot -> /dev/block/mmcblk0p4
abootBackup -> /dev/block/mmcblk0p11
dhob -> /dev/block/mmcblk0p20
fsc -> /dev/block/mmcblk0p22
fsg -> /dev/block/mmcblk0p21
hob -> /dev/block/mmcblk0p19
misc -> /dev/block/mmcblk0p30
modem -> /dev/block/mmcblk0p1
modemst1 -> /dev/block/mmcblk0p17
modemst2 -> /dev/block/mmcblk0p18
persist -> /dev/block/mmcblk0p29
rpm -> /dev/block/mmcblk0p5
Here is the script to take the back up:
This one is for about. please make the changes accordingly to take the backup for others:
adb shell su -c "dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4.img"
you will have to use this script on fastboot in cmd. while your phone is turned on and first you will have to give fastboot root access.
Again This is a request someone please please please help.....:crying::crying::crying:
If you need any help in taking backup please reply I will surely help with that.
Requirements:
- Device has to be rooted, with USB debugging enabled.
- Motorola fastboot (see attachment).
- ADB installed, minimal or the full ADK.
You can search the forum to find how to meet these requirements or for the terms described in this post beginning here:
http://forum.xda-developers.com/show....php?t=2558638
Weirdly when I backed up the /dev/mmcblk0p29 persist partition it was 8MB, meanwhile when I backed up the /dev/block/bootdevice/by-name/persist it was 32MB
As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
Code:
[I][B]tune2fs -l /dev/block/sda12
tune2fs -l /dev/block/sda13[/B][/I]
sda12 is system_a, sda13 is system_b
Example of untouched system:
Code:
Filesystem created: Wed Dec 31 17:00:00 2008
Last mount time: n/a
Last write time: Wed Dec 31 17:00:00 2008
Mount count: 0
Maximum mount count: -1
Last checked: Wed Dec 31 17:00:00 2008
How to fix - reflash system.img with the same version as currently running (or reflash everything with newer ROM):
Option #1
- download full OTA zip (not the incremental one, size must be above 1gb)
- and this Windows tool https://androidfilehost.com/?fid=818070582850510260
- extract both and put payload.bin into payload_input folder. Then run payload_dumper.exe. Once it completes the job, you'll find all images which can be flashed via fastboot.
- flash system.img to the active partition
- install OTA update
Option #2
- set A as active partition
- download, extract and run flash_all_except_data_storage.bat from stock Fastboot ROM
- root with Magisk patched boot.img and apply OTA with the usual Magisk A/B OTA procedure
Before flashing, backup your important data, one can be never sure enough.
flash_all_except_storage.bat = flash_all_except_data_storage.bat
I have a few questions about this method of yours.
1) I downloaded the fastboot rom from this thread but I can't find the payload.bin mentioned in the first method. Did I download the right thing? All I can see are *.img files and system.img is there too. Can I flash that one?
2) I have both TWRP and magisk installed currently. Will I lose them if I follow your method? How should I go if I wanted to keep them?
3) Of course you advice us to make a backup beforehand. Can you tell me or link me a guide about how to backup and restore properly with the new A/B partion in the way?
I'm sorry for asking this much, but all the guides I'm following are either confusing or with conflicting info.
Thank you for the help, I just can't wrap my head around this dual partion thing :s
SirAugustin said:
I have a few questions about this method of yours.
1) I downloaded the fastboot rom from this thread but I can't find the payload.bin mentioned in the first method. Did I download the right thing? All I can see are *.img files and system.img is there too. Can I flash that one?
2) I have both TWRP and magisk installed currently. Will I lose them if I follow your method? How should I go if I wanted to keep them?
3) Of course you advice us to make a backup beforehand. Can you tell me or link me a guide about how to backup and restore properly with the new A/B partion in the way?
I'm sorry for asking this much, but all the guides I'm following are either confusing or with conflicting info.
Thank you for the help, I just can't wrap my head around this dual partion thing :s
Click to expand...
Click to collapse
1. Fastboot ROM can be used straight away (Option #2).
2. Well, the point of this guide is to restore phone to stock images, so you can install OTA update. TWRP can't be kept. You can flash Magisk without TWRP though.
3. Titanium backup pro is my #1 backup tool for years, except very few exceptions it can backup and restore all apps and their settings. Data partition is only one, so you might have luck using TWRP backup - I haven't tried it.
Thank you kindly for all the info. These days I will try the method you described. ?
_mysiak_ said:
As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
Code:
[I][B]tune2fs -l /dev/block/sda12
tune2fs -l /dev/block/sda13[/B][/I]
sda12 is system_a, sda13 is system_b
Example of untouched system:
Code:
Filesystem created: Wed Dec 31 17:00:00 2008
Last mount time: n/a
Last write time: Wed Dec 31 17:00:00 2008
Mount count: 0
Maximum mount count: -1
Last checked: Wed Dec 31 17:00:00 2008
How to fix - reflash system.img with the same version as currently running (or reflash everything with newer ROM):
Option #1
- download full OTA zip (not the incremental one, size must be above 1gb)
- and this Windows tool https://androidfilehost.com/?fid=818070582850510260
- extract both and put payload.bin into payload_input folder. Then run payload_dumper.exe. Once it completes the job, you'll find all images which can be flashed via fastboot.
- flash system.img to the active partition
- install OTA update
Option #2
- set A as active partition
- download, extract and run flash_all_except_data_storage.bat from stock Fastboot ROM
- root with Magisk patched boot.img and apply OTA with the usual Magisk A/B OTA procedure
Before flashing, backup your important data, one can be never sure enough.
Click to expand...
Click to collapse
I tried method 1, OTA installation still shows Error message
What next?
oseraphaels said:
I tried method 1, OTA installation still shows Error message
What next?
Click to expand...
Click to collapse
If you are running custom kernel, flash the stock boot.img to boot partition as well.
oseraphaels said:
I tried method 1, OTA installation still shows Error message
What next?
Click to expand...
Click to collapse
Was your system partition mounted as RW in the first place? Is it still untouched? Some apps with root access can still mount it as RW, even if you reflash system.img.
Frank.G said:
If you are running custom kernel, flash the stock boot.img to boot partition as well.
Click to expand...
Click to collapse
I have stock boot img running, still ota install failed
---------- Post added at 10:25 AM ---------- Previous post was at 10:22 AM ----------
_mysiak_ said:
Was your system partition mounted as RW in the first place? Is it still untouched? Some apps with root access can still mount it as RW, even if you reflash system.img.
Click to expand...
Click to collapse
I fastboot flash_all.bat , I think this should mount all ROM segments, including system partitions
I fast boot flashed the latest ROM v11.0.15 and it works perfectly.
_mysiak_ said:
Was your system partition mounted as RW in the first place? Is it still untouched? Some apps with root access can still mount it as RW, even if you reflash system.img.
Click to expand...
Click to collapse
I can't find any apps that may be mounting system partition.
Is there a way to find out?
oseraphaels said:
I can't find any apps that may be mounting system partition.
Is there a way to find out?
Click to expand...
Click to collapse
Yes, compare the last mount timestamp and Magisk log. You will see which app used root access at that time.
oseraphaels said:
As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
sda12 is system_a, sda13 is system_b
Example of untouched system:
I tried method 1, OTA installation still shows Error message
What next?
Click to expand...
Click to collapse
Flash ota ROM in recovery
Rajendran Rasa said:
Flash ota ROM in recovery
Click to expand...
Click to collapse
Thank you very much
I fastboot flashed the latest ROM and my device works perfectly
Hi,
I have similar issue. My current version is V11.0.1.0.QFQEUXM. The system update show can't install update.
I get the stock version of V11.0.1.0.QFQEUXM fastboot room, and get the system.img. Then I flash it into my current active slot - b. After reboot, I still get can't install update.
The specific error is W update_engine: [0615/084826.432657:WARNING:mount_history.cc(66)] Device was remounted R/W 1 times. Last remount happened on 2020-05-15 10:30:34.000 UTC.
The remount is cause by TWRP.
Is there other suggestion?
Flash ota ROM in recovery
Click to expand...
Click to collapse
Tried to sideload V11.0.2.0.QFQEUXM OTA.zip, but error also.
Thanks.
JackVoo said:
Hi,
I have similar issue. My current version is V11.0.1.0.QFQEUXM. The system update show can't install update.
I get the stock version of V11.0.1.0.QFQEUXM fastboot room, and get the system.img. Then I flash it into my current active slot - b. After reboot, I still get can't install update.
The specific error is W update_engine: [0615/084826.432657:WARNING:mount_history.cc(66)] Device was remounted R/W 1 times. Last remount happened on 2020-05-15 10:30:34.000 UTC.
The remount is cause by TWRP.
Is there other suggestion?
Tried to sideload V11.0.2.0.QFQEUXM OTA.zip, but error also.
Thanks.
Click to expand...
Click to collapse
You've found the culprit already.. Do NOT use TWRP to flash images, it must be done via fastboot.
_mysiak_ said:
You've found the culprit already.. Do NOT use TWRP to flash images, it must be done via fastboot.
Click to expand...
Click to collapse
Hi, the remount is at 15-May. Which I try to fix this issue.
I use fastboot to flash the system.img, but it still mentioned about "remount R/W".
After that, I boot into stock recovery and sideload the OTA.zip, still fail
Thanks
JackVoo said:
Hi, the remount is at 15-May. Which I try to fix this issue.
I use fastboot to flash the system.img, but it still mentioned about "remount R/W".
After that, I boot into stock recovery and sideload the OTA.zip, still fail
Thanks
Click to expand...
Click to collapse
You probably forgot to flash something (or used incorrect image). Just download the latest fastboot image, switch to slot A and flash it all (except storage).
Try flashing with V11.0.1.0.QFQEUXM boot.img and system.img at slot A and B, still couldn't update.
Will try to flash all with the V11.0.2.0.QFQEUXM.
Update status:
I finally solve this issue.
I flash the new fastboot ROM into slot A, my current active is slot B.
Thanks for help.
help please
doing these steps will erase my data like factory reset?
if yes, then how can i install ota without losinig any data
_mysiak_ said:
As this questions pops up every single month, I'm putting this information into a separate topic. It is for everyone who followed the Magisk A/B OTA update guide and OTA update still fails to install. https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md
The usual culprit is TWRP - if you booted into TWRP and allowed system modifications (even once), OTA update won't install. The second common suspect is one of apps with root access, which might have tampered the system partition (AdAway or some other old apps).
Use these commands as root from ADB shell or terminal emulator on the phone and look for mount count (has to be 0) and last mount time (must be n/a). Anything else means that system partition has been mounted as R/W and you MUST reflash stock system.img manually.
Code:
[I][B]tune2fs -l /dev/block/sda12
tune2fs -l /dev/block/sda13[/B][/I]
sda12 is system_a, sda13 is system_b
Example of untouched system:
Code:
Filesystem created: Wed Dec 31 17:00:00 2008
Last mount time: n/a
Last write time: Wed Dec 31 17:00:00 2008
Mount count: 0
Maximum mount count: -1
Last checked: Wed Dec 31 17:00:00 2008
How to fix - reflash system.img with the same version as currently running (or reflash everything with newer ROM):
Option #1
- download full OTA zip (not the incremental one, size must be above 1gb)
- and this Windows tool https://androidfilehost.com/?fid=818070582850510260
- extract both and put payload.bin into payload_input folder. Then run payload_dumper.exe. Once it completes the job, you'll find all images which can be flashed via fastboot.
- flash system.img to the active partition
- install OTA update
Option #2
- set A as active partition
- download, extract and run flash_all_except_data_storage.bat from stock Fastboot ROM
- root with Magisk patched boot.img and apply OTA with the usual Magisk A/B OTA procedure
Before flashing, backup your important data, one can be never sure enough.
Click to expand...
Click to collapse
Thanks for the post.
When i ran flash system.img is says partition unknown!