Related
Edit: HERES WHAT YOU SHOULD DO IF YOU GET AN OTA UPDATE NOTIFICATION. DON'T UPDATE YET READ THIS:
http://forum.xda-developers.com/showpost.php?p=6558259&postcount=6
Here's what you should do if you already updated:
http://forum.xda-developers.com/showpost.php?p=6558291&postcount=726
Original post:
I honestly don't know how though myself. I figure its good if anyone happens to get the update but doesn't know how to dump it. Anyone who does have knowledge want to post or post a link to where you can learn how to do it? It'll help get this thing out faster if someone happens to get it.
In a nutshell, you need to unlock the bootloader, install the custom recovery menu and then finally perform a nandroid backup. Sorry, I'm on my phone so I can't give you all the links but they are found in the sticky threads.
You can then upload it for everyone to download or use the Android Basic Kitchen to make it into an update.zip so that it can be flashed by anybody with a rooted Nexus One.
Oh well that doesn't apply to me. I'm not rooted yet. At least I know that much now... we'll need someone rooted to dump it.
What about getting a link for update.zip? Anyway to figure that out? Should we wait before we update if we get the notification so we can get the url?
Well boys, Chris over at AndroidPolice could use some of our help. I emailed him bout 20 minutes ago, and here's his reply...
//
I don't know the steps for doing so, actually, I was planning on walking through the steps to get a dump, if possible. If you can get someone at XDA to put a list of steps together for either getting the URL or grabbing a system dump, I'll post them up on the blog.
Warmest regards,
Chris
----------------------------
Chris Dehghanpoor
Associate Editor, androidpolice.com
//
Let's hook the man up with some steps eh?
chowlala said:
Let's hook the man up with some steps eh?
Click to expand...
Click to collapse
Yeah lets do this. Posted in the main thread on 2.2 to see if someone can do this. You might want to go to a separate thread if that doesn't get any responses so more people see this.
Just to be clear, if you get an OTA notification do the following:
1) Say install later
2) Install Log Collector from the Market (its written by Xtralogic)
3) Open said app and select ok
3) Email it to futurerheza at gmail dot com
4) Press home
5) Go Menu->settings->About Phones->System Updates
6) From here you will be able to install Froyo
and i will try to find link, and share with u guys.\
can you email this to him
To get the link, install the SDK and run adb logcat before you start the update. It will most likely show up there. Just press CTRL+C to stop logcat.
Another method is to install Andro Shark that can be found in this forum. It will dump all traffic (when you run the app and start the service). This way you will get both the link and with the help of tcpflow you can even extract the entire update.zip from the created pcap-file.
For Nandroid, boot to fastboot mode (power+volume down and select fastboot).
Run "fastboot oem unlock" and agree to the terms of voided warrenty.
Download Amon_Ra's recovery or Clockwork recovery from here or modaco.
In fastboot mode, run "fastboot boot name-of-recovery-image.img".
Select Nandroid backup.
the best would be a nandroid image, but you have to flash a custom recovery image that supports nandroid.
Then you do the following (I already posted this somewhere):
-make a nandroid backup for you
-wipe everything (data/cache/...)
-make a new nandroid backup (before rebooting) <- this is the needed backup for us
-restore the first backup for you
Thanks guys. I'm at work right now, and have to get a few things done - I'll post this info up in a few minutes.
chowlala said:
Let's hook the man up with some steps eh?
Click to expand...
Click to collapse
Someone over on the other thread posted a how to on dumping the image which should work for anyone rooted. Update.zip will have to come from a log and someone not accepting the update right away.
This is what he should do:
http://forum.xda-developers.com/showpost.php?p=6558291&postcount=726
also if anyone does get the update, i can offer my help via google talk momohammed20 to help dump the update!
I read someplace on this forum about a procedure that allows one to do a full flash from Linux as a last resort. But I have been unable to relocate it. Can somebody point to this procedure?
Thanks in advance.
Hi,
http://forum.xda-developers.com/showthread.php?t=1971266
But I think this tutorial is for standart U8800 only.
Anybody done it before? As lollipop really suck big times, i rather stick with kitkat.
Im using Yoga tablet 2 830LC
If u do please help to provide detail tutoria
Many thanks in advance.
you must have root before continuing, go and download these two files, you will need them later:
1. your archive with the files for restoring the 830LC bios (while the name says 830F the bios is identical with the 830LC /i have checked/ so you can use it with no worries, DO NOT EXPERIMENT however with other files)
2. the 830LC stock rom
now go and follow the steps provided here (what you need to do, especially in step A can very easy hardbrick your device if not careful), after you complete step A in the post, follow the step B using your stock rom downloaded (at 2. above) the intel flash tool and the drivers are in the "tools" folder of the already downloaded stock rom so you only need the two archives/files already downloaded. the 830F has the same kitkat bios as 830LC (all base model numbers share the same bios eg: 830L(C) bios = 830F, but not different numbers, ie 1050F has not the same bios with 1380F)
be careful, and do not experiment, especially the step A (flashing the bios) can very easy hardbrick your device (with no software recovery possible) and you will have to send it at lenovo for repairing... if you are not sure of something better ask
TODO:
update with something more straightforward (and safer for the casual user)
Thank you very much, this is a very big help, very much appreciated.
jasonalice said:
Thank you very much, this is a very big help, very much appreciated.
Click to expand...
Click to collapse
no no, i thank you... it's not every day that i get the chance to chat with someone who talks on a 8" phone (there's also a 10" one you know? and while no official rom exist if you buy a 13" tab i will mod an existing one to make the calls work on that for you)
Thanks pal.
One more favor, does 'Root ghe yoga 8/10' meyhod work for 830LC as well?
Just need to clarify to avoid bricking mt tab.
Thanks again.
ya
option T3 for kitkat
Sorry, im new to all this thing, any detail tutorial how to downgrade the bios in section A
many thanks
jasonalice said:
Sorry, im new to all this thing, any detail tutorial how to downgrade the bios in section A
many thanks
Click to expand...
Click to collapse
what details you need? just do exactly as it says in step A, but then again if you still need details maybe it's safer for you to stay on Lollipop or try to find other ways to downgrade
it's just a matter of moving around some files and typing some commands in the android shell (you have a terminal installed?)
Installed terminal emulator, but don't know how to use.
jasonalice said:
Installed terminal emulator, but don't know how to use.
Click to expand...
Click to collapse
you should stay on lollipop until some form of official downgrade will appear
if you don't know how to use a term most likely you will brick your tab
Thanks for you advice
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
permutations said:
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
Click to expand...
Click to collapse
Have you tried booting to recovery from bootloader and regaining an ADB connection? This should be all you need.
permutations said:
Can someone suggest another forum where I can go for help?
The last 5 or 6 times I've posted questions here, I've gotten no answers at all. I really need help. My tablet was bricked because I lost ADB connection while updating the system partition. I know there is a way around this - I have a custom recovery and an unlocked bootloader - but I need help from someone who knows more than I do. No one here is going to help me, I know. Where do I go? Where can I find someone knowledgeable and helpful?
Click to expand...
Click to collapse
The more information you provide, the better. Please provide more information regarding your device so that your thread can be placed in the correct forum.
Magnum_Enforcer said:
The more information you provide, the better. Please provide more information regarding your device so that your thread can be placed in the correct forum.
Click to expand...
Click to collapse
I was updating my Nexus 10 tablet - had gotten to the system partition - when I lost the ADB connection. I've since learned that's a problem with newer Macs (I was connected to Windows through Parallels). Here's a link to a thread about that:
https://code.google.com/p/android/i...Stars Reporter Opened&groupby=&sort=&id=65301
Because of the lost connection, the system partition did not flash and my tablet is bricked. There is no operating system so it can't boot into Android, but it can boot into the Bootloader and Recovery mode. All the other partitions are fine.
I have a custom recovery (TWRP) and an unlocked bootloader, but I'm at a loss to figure out how to flash the system.img file. I can't boot to Android so I can't connect through ADB in Fastboot mode to flash the ordinary way. I am connected through ADB when I'm in Recovery mode, but I can't use the flash command in Recovery mode. Nor can I figure out a way to make TWRP flash the partition by running it as a zip file - mainly because I can't figure out what the update.zip file should consist of. There was an OTA update file on my device when I started the manual update (manual updates fail), but I didn't look at it and didn't save it.
I tried pushing the system.img file to the Nexus 10 using the Linux dd command, but that doesn't work with the system partition, which uses a special format. The details are explained here, but I don't fully understand it:
http://www.modaco.com/forums/topic/327661-how-to-backup-the-systemimg-bootimg-and-recoveryimg/
After spending about 8 hours on this last night, I believe the only way I can fix it is to create an update.zip file that uses a Linux script to flash the system partition, but this is way beyond my skill set and I can't find a model for how to do this anywhere. All tutorials I've found for creating zip files for flashing are for installing apps, not flashing a system partition - which is even more complicated than flashing, say, a boot partition. Nor can I find an update.zip file from someone's cache (sure wish I'd saved mine) to use as a model. I'm looking for someone with this kind of high level knowledge who can give me guidance - or someone who can refer me to someone who has this kind of knowledge.
I solved this problem.
Preamble
Hello, all.
Soooo I've never posted on this forum before. I've mainly leeched the invaluable info for my personal gain. I'm sure many a googler has come here trying to figure out how to root their phone. And I'm sure many a "swimmer" in Schitz Creek has come here via Google to figure out how to save their device from what had been perceived as an upgrade. I'm speaking, of course, of trying to root/unlock a phone and finding said phone "bricked".
Well, it’s time to give back.
Because yesterday, I was neck deep in Schitz Creek. After a series of dumb decisions and a lack of knowledge, I bricked the phone I’d bought for my wife’s birthday. I was just trying to be able to delete the Asus bloatware and install titanium backup and greenify. By the way, since when did Facebook become a system app? How is this a thing? Anyways, my wife deserves better battery life. And it’s fun to feel like Cyber MacGuyver by rooting a phone. But the situation went awry. My wife kept telling me that everything was going to be alright, but I know the limitations of my knowledge.
Brief aside: I'm decently computer/phone savvy, but I would, in no way, consider myself an advanced user. Sure, to my family, I'm a computer wizard. But that doesn't mean a whole lot. To them, opening up a command prompt in Windows is seen as an act of magic. And I haven't had my planeswalker spark yet. However, I have successfully rooted, and in most cases unlocked the bootloader, for several phones (HTC desire, Galaxy S3 [three different models over three years], Asus Zenfone 5, LG G4 [once pre-motherboard-death and once post (after a downgrade)], and now the ZE552KL). So I know how to at least fumble my way around adb, fastboot, odin, and various recoveries. As long as you’re at this level, or willing to learn, then you should be able to follow these instructions. End aside.
Mistakes not to make
Let’s get down to brass tacks. I made two big mistakes that you shouldn’t make. Both mistakes stemmed from the basic mistake of using a root method other than this one: https://forum.xda-developers.com/zenfone-3/help/guide-how-to-root-zenfone-3-ze552kl-t3471524
The problem with not using this EXACT method is that some of the files/programs which you need to use have specific versions which will ensure an easypeasy root. Honestly, if you properly follow the instructions in the above post, you will most likely not run into any problems. The only addition I can make is that instead of steps 6 and 7, you might find it easier to install SuperSU.zip through TWRP instead of pushing and sideloading.
Mistake 1: Not using the proper TWRP file and SuperSU file
For some reason, there are multiple versions of these files. Your SuperSU file should be 4.8MB. Using the wrong SuperSU will break the dm-verity. Your TWRP should NOT be the latest experimental version. It should be the one from November or earlier of 2016. Using the wrong TWRP will leave you unable to use the touchscreen. Trust me. I know from experience.
Mistake 2: KEEP TWRP READ ONLY
Disabling read only has no current benefits. It will just break the dm-verity. Your device will still be able to be written to if you keep TWRP read only. I have no idea why it’s called “read only”.
How to unbrick the phone
I’m sure some of you skipped straight to here. While I can’t blame you, please at least read the above paragraph. It will help you.
First I will describe the situation the phone was in, and then I will explain how I saved it. Before I continue, I want to give a big shout out to Niemer. Without their helpful post, I would’ve had no idea what to do. Thanks!
Situation the phone was in
--TWRP could not be used because the touchscreen wasn’t working.
--The dm-verity was messed up (i.e. “not started in enforcing mode").
Before you look at the solutions, make sure that your phone shows up in the windows device manager as an ADB device/ASUS ADB device/ADB composite device/etc. no matter which step you’re in. Google it to figure out how if you don’t already know.
The solution
Part 1 - Create and flash a system image which will restore your dm-verity
step 1. download the latest system “update” from the asus drivers website. I have a WW version of the phone, so I downloaded “WW_V13.20.10.152”. It’s a 1.76GB file, so be patient. I haven’t tested this method with other versions of the phone, but they should work in theory.
step 2. go into the updater script file (META_INF → com → google → android → updater-script). Open it with notepad ++.
step 3. delete from the beginning of the file up until the line “ui_print("Target: asus/WW_Phone/ASUS_Z012D:6.0.1/MMB29P/13.20.10.152-20161222:user/release-keys");”
The code that you are deleting checks to make sure that your phone is the proper model. But there is a good chance that it will mistakenly identify your phone as a phony. So we need to get rid of this code.
step 4. save the updater-script file
step 5. create a copy of the modified system update zip file. You should now have two 1.76GB files (or maybe slightly different if your phone is a CN, JP, or other model. Once again, I have a WW version of the phone). Name one of the files “realupdate.zip” and name the other “dmsaver.zip”. The names aren’t actually important.
step 6. enter dmsaver.zip. delete these four files: file_contexts, system.new.dat, system.patch.dat, and system.transfer.list. Exit out of the file. It should now be about 60MB.
step 7. turn on your ZE552KL and enter fastboot mode
step 8. in a cmd screen from your main folder (i.e. the one with adb, fastboot, and all the other files, including the ones you just created), type in the command “fastboot flash system dmsaver.zip”
step 9. if successful, you have just restored the dm-verity. You should now no longer get that sinister red text which has been ruining all your fun.
Part 2 - Install a proper version of TWRP
(This is only important if your version of TWRP won’t let you do anything because you can’t use your touch screen)
Download the version of TWRP that is included in the how-to-root post I linked to above. Also, you can download the oldest version (NOT the newest) from a sharing website which is linked to in a post on the ASUS website. It’s not in english though. Flash it to your phone in fastboot mode using the “fastboot flash recovery” command. Make sure you turn your phone off before turning it back on, or your recovery might not activate correctly.
Part 3 - Install a new version of your system.
Go into TWRP and install the zip file “realupdate.zip” that you created in Part 1 - step 5.
Part 4 - Root your phone
Follow the instructions in the link I posted earlier. It comes from this website, so you know it’s good. This time, though, you probably don’t need to unlock the bootloader
Part 5 - Breathe a sigh of relief
Parting words
I really hope this guide can be of assistance to you. The full procedure for fixing “my” phone wasn’t really recorded anywhere (although once again, big shout out to Niemer for their post). I went through hundreds of iterations of seemingly random fastboot, recovery, and adb actions before everything worked out. Because of this, I feel quite fortunate to have saved the phone, and I really wanted to give back. This community has been super helpful to me over the last seven years, and this is my chance to reciprocate. I sincerely hope that this post will help you.
I hope I didn’t forget anything. I have a sneaking suspicion that I did. In any event, if you have any questions, please post them, and I’ll try to be of assistance. Happy rooting!
thank you man but i start Part1 step8 "fastboot flash system dmsaver.zip" it's successful then i go into TWRP and install the zip file “realupdate.zip” dm-verity show again.
Thank again.
Raw firmware
I have the same issue. My phone was branded "tim italy". When i bought it, I flashed the WW version via asus flash tool, and I'm currently able to update till the last M version, which is the ......152.
If i try to update to Android N, my phone will not boot, giving me the corruption message and shutting down after 10 seconds. I also tried to perform the dm restore procedure; the dm error disappeared but the system is stuck on the Asus boot screen
I believe that the only solution is to flash a Nougat RAW firmware via asus Flash tool. Does Anyone have a download link for the N version ?
thank you, you helped me, now im on N
I guess the version matters then. So be careful with which firmware you download/install. If anyone has success with other versions, please share how you did it
I am stuck on Step 8. i put the 2 zips in where my adb and fastboot is located, and then proceed to type 'fastboot flash system...' and then it wont let me flash, any help?
Device Locked
When I flash the dmsaver.zip, receive the error "FAILED (remote: not allowed in locked state)". Apparently this with the bootloader locked, but I already unlocked before. Someone can help me unlock the bootloader again?
Further hyperlinks & solution ideas
Check out my solution and Ideas in those in links I posted in this thread at 4th of septembre 2017:
https://forum.xda-developers.com/ze...-zenfone-3-zoom-ze553kl-t3657239#post73661437
The hyperlinks in my post might also be useful, I hope.
Would be glad about your feedback, if it helped! :good:
how do you update the script file ..can u just post the file that u made somehow or email it or attach it to a message?
cant get it to work followed the instructions still getinf error code 7 trying to install lineage os
If you have lineage OS version not is a zip file but all the images (boot.img, system.img, ...) then you could try to flash the images through ADB...
if someone have the no verity issue, can you try a method for me please?
it consists on:
re-flash the rom kernel via fastboot
and run:
Code:
fastboot oem reset-dm-verity
Followed all the steps and twrp still has no touch function.
Tried all different twrp versions.
OS Version is a key
Hi everybody that has the same issue, I hope you read that so you can fix your problem.
So what I did was downloading old version of OS that autor mentioned "WW-13.20.10.152". It is necessary to download this version even if there are more newer versions. Then follow tutorial and you should be fine.
So again, thanks OP for posting this. You helped me a lot!