Database Users

[Q] Botlooped/Bricked Nexus 7 from build.prop mod recovery help?

Hello. I'm new to this forum and I joined because I was searchingother forums like nexus4nexus7 for a way for me to play Modern Combat 2 on my Nexus 7.
I couldn't find any threads specific enough to fit my needs. Perhaps I didn't look hard enough, but I figured I'd give it a shot.
To do this I decided to use the build.prop of a Nexus 4, because it has a Tegra 2 which the game supports, unlike the badass Tegra 3 quad core processor of the 7.
So I replaced the original build.prop, making a backup of the stock. I rebooted, and it never responded since.
I have used the bootloader screen, but accessing the recovery program from that just said, "no command." In no manner was fast boot or any other of the options doing anything to help me.
I am/was unlocked and rooted obviously, and I would really like to not lose my music.
I believe I have TWRP but I have no honest idea how to get to it.
I would appreciate a way to retrieve my files and restore it, or even better revert it back to it's glorious rooted days with no loss of data. Thanks for the help!

LouisMarshall said:
Hello. I'm new to this forum and I joined because I was searchingother forums like nexus4nexus7 for a way for me to play Modern Combat 2 on my Nexus 7.
I couldn't find any threads specific enough to fit my needs. Perhaps I didn't look hard enough, but I figured I'd give it a shot.
To do this I decided to use the build.prop of a Nexus 4, because it has a Tegra 2 which the game supports, unlike the badass Tegra 3 quad core processor of the 7.
So I replaced the original build.prop, making a backup of the stock. I rebooted, and it never responded since.
I have used the bootloader screen, but accessing the recovery program from that just said, "no command." In no manner was fast boot or any other of the options doing anything to help me.
I am/was unlocked and rooted obviously, and I would really like to not lose my music.
I believe I have TWRP but I have no honest idea how to get to it.
I would appreciate a way to retrieve my files and restore it, or even better revert it back to it's glorious rooted days with no loss of data. Thanks for the help!
Click to expand...
Click to collapse
As far as I know TWRP has a built in file manager, so just boot in the bootloader, select recovery with the volume up/down keys and press power to confirm. In TWRP you use the file manager to overwrite the build.prop with your backup / to delete the build.prop and copy the backup back. Should work (if you just replaced the build.prop and not anything else). No data will be lost when you try it
If it's not working I could upload a flashable .zip that replaces the build.prop with your old one :good:

mihahn said:
As far as I know TWRP has a built in file manager, so just boot in the bootloader, select recovery with the volume up/down keys and press power to confirm. In TWRP you use the file manager to overwrite the build.prop with your backup / to delete the build.prop and copy the backup back. Should work (if you just replaced the build.prop and not anything else). No data will be lost when you try it
If it's not working I could upload a flashable .zip that replaces the build.prop with your old one :good:
Click to expand...
Click to collapse
Thanks for your reply. Recovery does not work for me. It just says "no command" when I select it. Good Idea though.

LouisMarshall said:
Thanks for your reply. Recovery does not work for me. It just says "no command" when I select it. Good Idea though.
Click to expand...
Click to collapse
Is your bootloader unlocked? If yes, download the latest TWRP recovery image and boot in the bootloader. Then use fastboot to flash it
Code:
fastboot flash recovery twrp-recovery-image-name.img
That's it. Then you are able to use TWRP :good:

If your bootloader is unlocked, fastboot should work for you, I.e boot the device into fastboot mode, then flash TWRP recovery again by
fastboot flash recovery <recovery.IMG>
and after that a
fastboot reboot recovery
From there you are able to copy back your old build.prop file either by using the file manager or by using adb:
adb mount /system
adb cp /system/build.prop.back /system/build.prop
adb reboot
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
If your bootloader is unlocked, fastboot should work for you, I.e boot the device into fastboot mode, then flash TWRP recovery again by
fastboot flash recovery <recovery.IMG>
and after that a
fastboot reboot recovery
From there you are able to copy back your old build.prop file either by using the file manager or by using adb:
adb mount /system
adb cp /system/build.prop.back /system/build.prop
adb reboot
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It might have been a .bak
Also can you describe to me exactly how to boot into fastboot.
I am unlocked and rooted.
Is adb an external program? I have a mac at the moment.
- - - - - - - - - - - - - - - -
fastboot flash recovery <recovery.IMG>
fastboot reboot recovery
How do I enter these commands? With adb. Can I use adb on a mac? Thanks for your quick response.

mihahn said:
Is your bootloader unlocked? If yes, download the latest TWRP recovery image and boot in the bootloader. Then use fastboot to flash it
Code:
fastboot flash recovery twrp-recovery-image-name.img
That's it. Then you are able to use TWRP :good:
Click to expand...
Click to collapse
Just tried booting into bootloader. Now I have this eternal ant race going on.
I can no longer access fastboot. And it seems the same goes for my bootloader.
Uhm any other ideas. I had no Idea how to boot into bootloader... so I followed this guys intruction from android forums, "Hold Vol Up + Vol Down + Power until it shuts off, then Vol Down + Power to boot into bootloader." It's like static but with lines. This is a new problem, is it not only a software, but a hardware issue now? Or is it just not charged? Thanks a million for your help so far
***It seems it was a problem with the charge... its fine now. Can get into bootloader ***

Did your pc detect the device?
Turn off your device and turn on during the google logo press and hold volume down +power until you see android ley down. Then try vol up or down to see recovery hit power. Good luck
Sent from my SPH-D710 using xda premium

LouisMarshall said:
***It seems it was a problem with the charge... its fine now. Can get into bootloader ***
Click to expand...
Click to collapse
Now that you are able to get in the bootloader, just flash the recovery image and try replacing the build.prop
Sent from my Nexus 4 running Android 4.2.2

mihahn said:
Now that you are able to get in the bootloader, just flash the recovery image and try replacing the build.prop
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
Okay... How do I flash the Recovery Image? Thank

evobb10 said:
Did your pc detect the device?
Turn off your device and turn on during the google logo press and hold volume down +power until you see android ley down. Then try vol up or down to see recovery hit power. Good luck
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It won't detect it. When I select recovery it says, "No Command" huh

LouisMarshall said:
Okay... How do I flash the Recovery Image? Thank
Click to expand...
Click to collapse
Either you use a toolkit for Mac to flash the recovery or you install fastboot and adb (android sdk) for Mac on your PC. Then there will be a program named fastboot. You download the recovery.img, place it in the same directory where fastboot is and type in the fastboot console:
Code:
fastboot flash recovery recovery.img
To boot into bootloader turn off the device and press power and volume down at the same time
If it's too hard with fastboot, use a toolkit for Mac like I said. Should work too
Btw you need the build.prop backup as a build.prop (in your sdcard) or build.prop.bak (then just delete the build.prop and rename the build.prop.bak if renaming is possible in TWRP file manager). Then reboot and it should work :good:
Sent from my Nexus 4 running Android 4.2.2

mihahn said:
Either you use a toolkit for Mac to flash the recovery or you install fastboot and adb (android sdk) for Mac on your PC. Then there will be a program named fastboot. You download the recovery.img, place it in the same directory where fastboot is and type in the fastboot console:
Code:
fastboot flash recovery recovery.img
To boot into bootloader turn off the device and press power and volume down at the same time
If it's too hard with fastboot, use a toolkit for Mac like I said. Should work too
Btw you need the build.prop backup as a build.prop (in your sdcard) or build.prop.bak (then just delete the build.prop and rename the build.prop.bak if renaming is possible in TWRP file manager). Then reboot and it should work :good:
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
I have the adb and fastboot programs from the sdk on my mac and know how to execute them, but when I use "adb devices" it can't detect it. As long as it can't detect it, it seems like both of your methods are obsolete. I have to be in bootloader for it to recognize the nexus 7 right? I'll try your method regardless and report back. Thanks so much for your help!!
Should I use TWRP or CWM Recovery images? Or if neither which?

LouisMarshall said:
Should I use TWRP or CWM Recovery images? Or if neither which?
Click to expand...
Click to collapse
Use TWRP because it should have a file manager built in
Sent from my Nexus 4 running Android 4.2.2

mihahn said:
Use TWRP because it should have a file manager built in
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
Yes I used TWRP and it does have a file manager (THANK YOU!) ... but it doesn't seem to see the build.prop and build.prop.bak in the system folder... Does it have root permission? Can I refresh? You've been great so far! xD So close!

Probably you need to mount /system first, because in recovery normally no system and/or data partitions are mounted automatically. There is an option innTWRP, too, to mount /system.
Sent from my Nexus 7 using xda app-developers app

LouisMarshall said:
Yes I used TWRP and it does have a file manager (THANK YOU!) ... but it doesn't seem to see the build.prop and build.prop.bak in the system folder... Does it have root permission? Can I refresh? You've been great so far! xD So close!
Click to expand...
Click to collapse
All the other folders in the system folder are present and only the build.prop is missing?
If you can't go on by mounting system and data like the guy above said, I could upload a flashable .zip which flashes the old build.prop back
Please tell us on which Android version you were before (4.1.2/4.2.2) and which model you own (wifi only/3g) :good:
Sent from my Nexus 4 running Android 4.2.2

mihahn said:
All the other folders in the system folder are present and only the build.prop is missing?
If you can't go on by mounting system and data like the guy above said, I could upload a flashable .zip which flashes the old build.prop back
Please tell us on which Android version you were before (4.1.2/4.2.2) and which model you own (wifi only/3g) :good:
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
I have the WiFi only model. It was running on 4.1.2. I'll try mounting system first because looking back I can't even browse the root directory. I see a flashable zip that would be nice... well I only had data and cache mounted! Yes the build.prop is showing up! And the .bak! I fixed it LOVE you guys. Thanks a million you guys were a great help! DDD

AndDiSa said:
Probably you need to mount /system first, because in recovery normally no system and/or data partitions are mounted automatically. There is an option innTWRP, too, to mount /system.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks that was what I was missing

LouisMarshall said:
I have the WiFi only model. It was running on 4.1.2. I'll try mounting system first because looking back I can't even browse the root directory. I see a flashable zip that would be nice... well I only had data and cache mounted! Yes the build.prop is showing up! And the .bak! I fixed it LOVE you guys. Thanks a million you guys were a great help! DDD
Click to expand...
Click to collapse
Great it works again! Enjoy your device now
And next time please don't play with system files if you don't know exactly what you are doing or simply do a nandroid backup before (in TWRP or cwm) which you can restore if something goes wrong

No os installed

Guys help me!
I install android 4.3 on my phone, however I did not do the backup and by mistake I've downloaded the wrong rom, now my phone a message appears in the bootloader "in the OS installed"
I'm desperate with my phone only in recovery mode, please help me fix!

sprafael said:
Guys help me!
I install android 4.3 on my phone, however I did not do the backup and by mistake I've downloaded the wrong rom, now my phone a message appears in the bootloader "in the OS installed"
I'm desperate with my phone only in recovery mode, please help me fix!
Click to expand...
Click to collapse
Do you have a custom recovery installed? If so, load a .zip rom and push it via custom recovery...
.... If not, use ADB to push a reflash of a clean install of 4.3
instructions here my thread
http://forum.xda-developers.com/showthread.php?t=2376681

More info.what Phone mark modelo etc ?
Sent from my XT910 using Tapatalk 4 Beta

mc704 said:
Do you have a custom recovery installed? If so, load a .zip rom and push it via custom recovery...
.... If not, use ADB to push a reflash of a clean install of 4.3
instructions here my thread
http://forum.xda-developers.com/showthread.php?t=2376681
Click to expand...
Click to collapse
i do not have a custom recovery, the only thing it has in the cell and the image I downloaded wrong, my phone is in recovery screen that comes with it when I turn the volume button, after that I do not know what else to do, because I have no how to transfer the image to the correct cell to update, so I need to know how to transfer the image to the correct device

sprafael said:
i do not have a custom recovery, the only thing it has in the cell and the image I downloaded wrong, my phone is in recovery screen that comes with it when I turn the volume button, after that I do not know what else to do, because I have no how to transfer the image to the correct cell to update, so I need to know how to transfer the image to the correct device
Click to expand...
Click to collapse
if you are able to boot to recovery. you have to be in fast boot...
you can either use fastboot to flash over
or
boot into recovery and apply a rom via ADB sideload

mc704 said:
if you are able to boot to recovery. you have to be in fast boot...
you can either use fastboot to flash over
or
boot into recovery and apply a rom via ADB sideload
Click to expand...
Click to collapse
how to apply the room via ADB SIDE load, because I saw that option, so I do not know how to use

sprafael said:
how to apply the room via ADB SIDE load, because I saw that option, so I do not know how to use
Click to expand...
Click to collapse
open command prompt with adb loaded
type adb sideload romname.zip
the rom should be in the same folder the adb/fastboot tools are located

mc704 said:
open command prompt with adb loaded
type adb sideload romname.zip
the rom should be in the same folder the adb/fastboot tools are located
Click to expand...
Click to collapse
the fastboot do you explain this link??
http://forum.xda-developers.com/showthread.php?t=2376681
I'm downloading the android SDK at this time
let's see if I understand
put the phone in adb sideload
will open the CMD in the fastboot folder,
type in adb sideload image-occam-jwr66v.zip

Flashable zip not factory image, try cm10
Sent from my Nexus 4 using xda app-developers app

I messed up my recovery

So I wanted to upgrade to twrp 2.6.3.3 and I dont know why for some reason when I went to their page I saw these instructions and thought I'd try them
_______________________________________________________________
Download the above file and place it in /sdcard on your device. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Make certain that you get this command right. Typing the wrong number could result in a brick!
_______________________________________________________________
Now everytime i try to reboot into recovery it does some kind of boot verification check errors and just turns off. I flashed cwm and it says it flashed recovery ok but I cant boot into recovery. What have I done? :0
Not even my lg flash tool works right. I get to the ready part and click the arrow, I put my device in download mode and plug in the usb cable to the pc and then in the lg flash tool it says download fail, device model is different?

Try reflashing 2.6.3.2...I'm having issues with new version too.
Sent from my VS980 4G using xda app-developers app

[Q] Boot doesn't go beyond rotating circles. Help!!

I tried to search, but in vain.
Hardware: Nexus 4
Software : Android 4.4.4
For reasons that are not clear to me the machine restarted and is stuck in those 4 rotating circles, and doesnt go beyond it. Tried multiple things such rebooting, rebooting into recovery and booting again, tried adb to see if it can see the machine in recovery mode, but to no avail.
Can someone please help? Thanks in advance.

Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Did you do anything, flash anything to get the boot loop? Boot loop can usually be cleared by doing a factory reset. But you'll have to reset up your phone afterwards
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot. Is there a way to press some button and hard reset it?

Concoran said:
This is a stock android and have no changes whatsoever except automatic update to 4.4.4. Only thing that is different is it is unlocked.
For last one week the phone kept complaining that it was unable to back up photos and videos. So I kept the wifi on over the night, and next morning I saw what i thought was it was trying to reboot but unable to do.
Is it possible to connect to machine while it is in recovery mode? My ADB can't discover the device either in recovery mode or while it is trying to boot.
Click to expand...
Click to collapse
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Can you get into the bootloader? If so you can flash a custom recovery. ADB won't work in the stock recovery.
Click to expand...
Click to collapse
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.

Concoran said:
I can get into bootloader - if you mean by pressing down volume button and powering on - so you see a few options such as 'Start', 'Restart Bootloader' et al.'
If I can get into this, what option do I have? How I can I some custom recovery such as TWRP?
Also, I saw a youtube video where a gentleman shows how to completely reset from Recovery mode (hold power button and press up volume key), but that doesn't seem to work for me.
Click to expand...
Click to collapse
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Yes, that's the bootloader. Google 15 second adb install xda and install that. Then download the latest version of this http://techerrata.com/browse/twrp2/mako
Rename it recovery and put it in the same directory as fastboot.exe which will be installed with the 15 second adb install
Open a Windows command prompt in the same directory as fastboot and then with your phone connected to the pc and in the bootloader type the command in the command window
fastboot flash recovery recovery.img
This will instal twrp to your phone
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?

Concoran said:
My Biggest concern right now is not TWRP. I need to somehow get the machine to boot. It is stuck in those 4 circling things, and I need to somehow get the OS to work (or re-install if needed).
I am able to get to recovery where I see options to 'apply aupdate from ADB,' 'wipe data' and 'wipe partition'. I have wiped off everything, now I need to somehow get OS to install, and I don't know how. I tried using 'adb sideload 'image-occam-ktu84l.zip', but it fails.That file was extracted from occam-ktu84l-factory-0d3fd624.tgz from Android site.
Update: Great, now TWRP is installed. What next? I don't want CM at this point. Just stock Os. How do I get on to the machine?
Click to expand...
Click to collapse
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Adb side load this http://forum.xda-developers.com/showthread.php?p=47476426
Edit, you could also flash the .zip you mentioned in your post by
fastboot update your file.zip
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.

Concoran said:
Now that I have TWRP, how do I install CM? I would eventually like to return to stock, but at least for now, I need to get the phone going.
UpdateOk, the TWRP wasn't functioning well (swipe function wouldn't work), so got CWM recovery, and installed CM. CM too goes into infinite loop. Now I am completely stuck, I have no idea what else I can do.
Click to expand...
Click to collapse
Flash the factory image in fastboot
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
I installed both TWRP and CWM alternatively, installed factory images using flash-all.bat, install CM11. But in both cases, 1. factory image : The system get stuck in boot mode where those 4 circles keep rotating around each other, 2. In CM11, the arrow keep rotating indefinitely.
I don't know what else I can do.
Any pointers? Thanks in advance.
I am beginning to suspect hardware malfunction. In which case, is there a log somehow I can see?
As an Aside: 1. Adb refuses to see the device in fastboot mode. Not sure if this is an expected behavior. Fastboot can.
2. Stock Android USB Drivers never work. I had to get the WugFresh Development drivers.
This is Windows 8 environment.

jd1639 said:
Flash the factory image in fastboot
Click to expand...
Click to collapse
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics

Concoran said:
As I said earlier, both factory image and CM go into infinite loop at bootup. I have no idea what else to do.
Question now is to see if something is wrong with hardware. I don't know how to check that. Is there a way to do some diagnostics
Click to expand...
Click to collapse
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You probably have a failure of the emmc. What happens if you try to lock the bootloader and then reboot? Does it stay locked?
Click to expand...
Click to collapse
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.

Concoran said:
Yes, after locking (fastboot oem lock), bootloader the status says locked and I no longer see that unlocked icon when booting.
- At the moment I have CWM, and I see advanced options to format different folders which I have already done. But what I am not able to do is to use adb to copy the image-occam-ktu84l.zip to sdcard. Only way I have been able to install any zip is using sideload. Is that normal? I wonder if I am following right steps to begin with.
- Also, are there tools that can run and check if emmc has no bad sectors etc?
- In CWM I formatted whole log of folders, and now when CWM boots, it can't find /cache/recovery/* files. Which I take as a good sign - since old stuff is now gone. From here I don't know how to proceed. Any help - very thanful.
Click to expand...
Click to collapse
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you can side load you should be able to adb push a rom. When in recovery type adb devices. Does it show that your device is connected? Do you get an error?
Click to expand...
Click to collapse
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.

Concoran said:
I can sideload from adb. (adb sideload <filename>.zip while CMW is waiting for abd sideload). But can't push since adb doesn't recognize the device while in fastboot - the way fastboot can.
Click to expand...
Click to collapse
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
You have to be in recovery to run adb commands. The bootloader is only for fastboot commands. Try pushing while you're in recovery, not the bootloader.
Click to expand...
Click to collapse
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'

Concoran said:
Here 's what I see when I to sideload,
In CWM, I choose 'install from zip, which takes me to next page where i chose to select from sideload. I then start sideload from 'adb sideload occam-ktu84l-factory-0d3fd624.tgz' (sometime I use the extracted zip from that tgz),
Following is what I see on CMW,
'Restarting adb
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
installation aborted'
Click to expand...
Click to collapse
Ok, you can't use that file (tgz) in cwm, adb or fastboot. What you can do is extract it and then use the zip file. But, you'll have to boot into the bootloader and then use the command
fastboot update update.zip
Sent from my Nexus 5 using XDA Free mobile app

ASUS ZenFone ZE551ML Partitions List

Nothing

Wow, thanks for this useful info...
Can I make a system.img using this Terminal Command:
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img
After Customizing my ROM as I like it...?

ponnuvelpandian said:
Wow, thanks for this useful info...
Can I make a system.img using this Terminal Command:
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img
After Customizing my ROM as I like it...?
Click to expand...
Click to collapse
Yes you can just like that but you will need to be rooted before using dd command.

Thank you so much for the new recovery images. Saved me a lot of hassle. But the link for .160 recovery is down

ImjuzCY said:
Thank you so much for the new recovery images. Saved me a lot of hassle. But the link for .160 recovery is down
Click to expand...
Click to collapse
Sorry about that, found a better place. Go ahead and use the new link for the stock recovery.

how can i do this ?

gamsheer said:
how can i do this ?
Click to expand...
Click to collapse
You need to be rooted 1st. The attach to a computer using linux or Windows. Then do a adb shell command, then su and you can use the dd command like I have written at the top.
Sent from my SM-T230NU using Tapatalk

mikerowes69 said:
You need to be rooted 1st. The attach to a computer using linux or Windows. Then do a adb shell command, then su and you can use the dd command like I have written at the top.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
my device rooted but
it is show me permissions denied
im sorry can you show me some images learn me how can i do this
sorry for my bad english

Can I backup partitions on an unrooted device but unlocked bootloader using fastboot?
I'll explain what I want. Currently, whenever there's a new Firmware, I have to find and then flash stock recovery, unroot, update firmware, flash TWRP, flash SuperSU, and then I can use the device again (to me ann unrooted device is barely useable ). What I'm trying to solve is having to find and download the stock recovery everytime. However, If I have to be rooted then I'll need to temporarily flash recovery, root the device, get the recovery partition using this method, and then flash TWRP. Obviously, this is a pretty big hassle that I'd prefer to avoid.

gamsheer said:
my device rooted but
it is show me permissions denied
im sorry can you show me some images learn me how can i do this
sorry for my bad english
Click to expand...
Click to collapse
Ok guy. His is a beginner session.
1. Make sure that adb debugging is turned on.
2. Make sure you have a cable connected with drivers installed
3. In a terminal or command prompt type the following adb devices. If nothing is returned adb debugging is not turned on. If a serial number returns you have a connection.
4. Only proceed if you have a connection. Type the command adb shell
5. Now if you have root installed type su. No su, means no root. Download a one click root for asus zenfone 2 ze551ml.
6. Now that you are root type the following command if to retrieve all of your fastboot partitions ls -la /dev/block/pci/pci0000:00/0000:00:01.0/by-name
7. This will tell you the location of the partition for recovery.
8. This command will package your stock recovery for your current firmware dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img
9. This command will restore your stock recovery any custom recovery you choose.
dd if=/sdcard/recovery.img of= /dev/block/mmcblk0p2
dd if=/sdcard/twrp.img of /dev/block/mmcblk0p2
It can even be a bin file or whatever you choose to name it. But the partition has to be correct and that is why it is important to find what the fasboot partitions names are and locations.
10. If using fastboot type adb reboot bootloader. Then type fastboot flash recovery recovery.img and it will say failed but it didn't fail if your bootloader is unlocked.
Sent from my SM-T230NU using Tapatalk

BobboVilla said:
Can I backup partitions on an unrooted device but unlocked bootloader using fastboot?
I'll explain what I want. Currently, whenever there's a new Firmware, I have to find and then flash stock recovery, unroot, update firmware, flash TWRP, flash SuperSU, and then I can use the device again (to me ann unrooted device is barely useable ). What I'm trying to solve is having to find and download the stock recovery everytime. However, If I have to be rooted then I'll need to temporarily flash recovery, root the device, get the recovery partition using this method, and then flash TWRP. Obviously, this is a pretty big hassle that I'd prefer to avoid.
Click to expand...
Click to collapse
This device you and all of choose only allows us to do find the vulnerability in the bootloader, and this is how it is packaged. Any other way would like a nexus or oneplus model is much easier. However asus choose to lock their bootloader and package their partitions. Now if you can rewrite their fasboot and that would be great. So root with a one click root. Then use the dd commands to package your stock recovery and life will go a lot easier, with future firmware updates, just remember to uninstall root for a ota and replace your custom recovery with your stock first before doing a adb sideload
Sent from my SM-T230NU using Tapatalk

mikerowes69 said:
Ok guy. His is a beginner session.
1. Make sure that adb debugging is turned on.
2. Make sure you have a cable connected with drivers installed
3. In a terminal or command prompt type the following adb devices. If nothing is returned adb debugging is not turned on. If a serial number returns you have a connection.
4. Only proceed if you have a connection. Type the command adb shell
5. Now if you have root installed type su. No su, means no root. Download a one click root for asus zenfone 2 ze551ml.
6. Now that you are root type the following command if to retrieve all of your fastboot partitions ls -la /dev/block/pci/pci0000:00/0000:00:01.0/by-name
7. This will tell you the location of the partition for recovery.
8. This command will package your stock recovery for your current firmware dd if=/dev/block/mmcblk0p2 of=/sdcard/recovery.img
9. This command will restore your stock recovery any custom recovery you choose.
dd if=/sdcard/recovery.img of= /dev/block/mmcblk0p2
dd if=/sdcard/twrp.img of /dev/block/mmcblk0p2
It can even be a bin file or whatever you choose to name it. But the partition has to be correct and that is why it is important to find what the fasboot partitions names are and locations.
10. If using fastboot type adb reboot bootloader. Then type fastboot flash recovery recovery.img and it will say failed but it didn't fail if your bootloader is unlocked.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
thank you very much its work fine my pro

gamsheer said:
thank you very much its work fine my pro
Click to expand...
Click to collapse
Your welcome
Sent from my SM-T230NU using Tapatalk

Thanks a lot

Can someone with a ZE551ML WW dump his factory.img and post it? I try to enable LTE bands on a ZE551ML TW and I want to compare this partition to find some possible differences...
Thanks

NicoAu said:
Can someone with a ZE551ML WW dump his factory.img and post it? I try to enable LTE bands on a ZE551ML TW and I want to compare this partition to find some possible differences...
Thanks
Click to expand...
Click to collapse
There was a new factory.img and droidboot.img in the last full firmware build.
Sent from my SM-T230NU using Tapatalk

Did any notice that there was a new fastboot with the latest build? I wrote to Asus Tech support that they need to change their bootloader to easily unlocked and relocked. If a lot more people write they will change the bootloader. So please write tech support and ask that the bootloader be changed or replaced and that your email goes out to everyone in support and writing the software.
Sent from my SM-T230NU using Tapatalk

mikerowes69 said:
There was a new factory.img and droidboot.img in the last full firmware build.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
Can you tell me where I can find this build?!? On asus website, I only see "UL-Z00A-WW-2.20.40.164-user.zip" with boot.img and droidboot.img in the archive...
Thanks

mikerowes69 said:
Did any notice that there was a new fastboot with the latest build? I wrote to Asus Tech support that they need to change their bootloader to easily unlocked and relocked. If a lot more people write they will change the bootloader. So please write tech support and ask that the bootloader be changed or replaced and that your email goes out to everyone in support and writing the software.
Sent from my SM-T230NU using Tapatalk
Click to expand...
Click to collapse
You do realize there would then be no more unofficial bootloader unlocker and your warranty would be instantly voided. It's really not that hard to unlock the bootloader the way it is and you can retain warranty unofficially unlocking it as they don't check for it while being serviced if you flash the black splashscreen. Plus it's only a matter of time until somebody figures out how to relock it.
P.S. If you can't figure out or take the time to learn how to unlock the bootloader, you're better off not modding your phone in the first place as your most likely going to do more harm than good.
Sent from my ASUS_Z00AD using Tapatalk

i snort flour said:
You do realize there would then be no more unofficial bootloader unlocker and your warranty would be instantly voided. It's really not that hard to unlock the bootloader the way it is and you can retain warranty unofficially unlocking it as they don't check for it while being serviced if you flash the black splashscreen. Plus it's only a matter of time until somebody figures out how to relock it.
P.S. If you can't figure out or take the time to learn how to unlock the bootloader, you're better off not modding your phone in the first place as your most likely going to do more harm than good.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Thanks guy for wasting my time as well as anyone else. If your on here you don't really care about warranty. You assume I don't know about unlocking or anything else. Please go bother someone else. Assuming makes an ass out of you.
Sent from my SM-T230NU using Tapatalk