Completely wiped my device... Need HELP to recover!!! - Nexus 7 Q&A, Help & Troubleshooting

Hi Guys,
I did the most stupid thing and wiped everything on my device including the internal storage . Now i am stuck in TWRP recovery and i am not able to push files to /sdcard to flash a new rom and boot my device.
Can anyone help me???? i dont have any files on my storage now , but TWRP recovery is working fine. i tried
"adb push adb push C:\Users\Admin\Desktop\pa_grouper-2.10-06SEP2012-221306.zip /sdcard/"
please help me recover my Nexus 7.
Thanks a lot.

Download google factory image
Boot into fast boot (all3 buttons) then in terminal on computer use fastboot flash all nakasi-stock file name.tar.gz
Sent from my Nexus 7 using xda app-developers app

Harry GT-S5830 said:
Download google factory image
Boot into fast boot (all3 buttons) then in terminal on computer use fastboot flash all nakasi-stock file name.tar.gz
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi Harry GT-S5830,
Thanks , i am still in recovery , does it has to be factory image? can i just flash any custom rom , since that was my main purpose.
Just confirming the step:
* go into bootloader and then fastboot flash all <filename>
will that work?
EDIT: " fastboot flash all " didnt work.
i got the error :
asi-jro03d-factory-e102ba72.tgz
sending 'all' (257604 KB)...
OKAY [ 32.790s]
writing 'all'...
FAILED (remote: Invalid Partition Name.)
finished. total time: 32.820s
Please help.

Nexus toolkit has an option to restore to stock.
Use that.

Harry GT-S5830 said:
Download google factory image
Boot into fast boot (all3 buttons) then in terminal on computer use fastboot flash all nakasi-stock file name.tar.gz
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
well i just recovered the tablet using stock image via the fastboot commands.
i cant believe i erased internal storage. Big lesson learnt , never do two things at once ... at least when you are flashing a rom
Thanks everyone for their help, just wondering is there no way for us to push zip files to /sdcard folder via fastboot or recovery???

smartanks said:
well i just recovered the tablet using stock image via the fastboot commands.
i cant believe i erased internal storage. Big lesson learnt , never do two things at once ... at least when you are flashing a rom
Thanks everyone for their help, just wondering is there no way for us to push zip files to /sdcard folder via fastboot or recovery???
Click to expand...
Click to collapse
Its not in adb mode
Sent from my Nexus 7 using xda app-developers app

Related

[Q] Nexus 7 wont boot fully

I bought a nexus 7 today, rooted it no problems, but i changed the pdi settings to 160 to see if i could get the tablet ui, and now it wont boot fully, i can get into recovery and all but it wont boot past the google splash screen :/ HELP!
Here is stock build.prop for JRO03D, you can try pushing it via adb only other thing I can think of is complete reflash with the factory image
good luck
Is there a way to get the image onto the table in recovery?
Pretty sure you flash that image in fastboot
Sent from my Nexus 7 using Tapatalk 2
yes you use fastboot to flash the image via cmd prompt on your PC
I apologise, I've never had to use ADB or fastboot before, do you just give the file location and then it'll flash it on the tablet?
if you can get to recovery, try plugging the tablet with cable to a pc and mount the storage and move a rom over to it and flash it?
i dont have a nexus 7 yet but that would be my fix for a phone
Beagan said:
Is there a way to get the image onto the table in recovery?
Click to expand...
Click to collapse
adb push
adb is enabled in clockwork recovery. There's no way to mount the "sdcard" in recovery like you can on devices that have a physical SD card device.
I used nexus toolkit worked great!
Sent from my GT-I9100 using xda premium

Please help! Stuck on

Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Zehlek said:
Please help, I downloaded ChameleonOS Rom for Mako and I was on PA. I did a backup in TWRP and after I wiped data and cache I tried tp flash CHAOS ROm. It said success but it won't boot passed Google and If I try to restore PA it says failed and now I have no rom to flash to boot up and also I can't turn on debug to use ADB.
Click to expand...
Click to collapse
i'm not on twrp at the moment but you may be able to try this
you may also try the nexus toolkit
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Zehlek said:
Nexus 4 toolkit says device not found when trying to push file to device. It shows serial under fastboot mode but not ADB Mode. Is that because I can't turn on debug?
Click to expand...
Click to collapse
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
efan3719 said:
hmm... can you try setting the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot? might be able to get you back to square one.
if you can get into twrp you might be able to run adb commands from the recovery even if you didnt have it enabled before using the toolkit.
Click to expand...
Click to collapse
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Zehlek said:
That might work, how do I set the current status to "Soft-Bricked/Bootloop" and do the Flash Stock + Unroot?
Click to expand...
Click to collapse
On the main screen of the nexus tool kit there is a radio button option you can click for it.
Sent from my Nexus 4 using xda premium
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
This guy sounds like he knows what he's doing.
Sent from my Nexus 4 using xda premium
exb0 said:
not sure what you're trying to do, but if you just want to get the device up and running again..
- Download recovery with sideload
- Go into fastboot
- Use CMD to navigate to your Nexus Toolkit folder,
- Execute " fastboot flash recovery recovery.img ", assuming the image you downloaded was renamed to recovery
- Go into recovery, choose flash with sideload
- Back to CMD, type "adb-toolkit sideload *zipnamehere.zip*" , assuming your adb is named adb-toolkit
reboot, profit.
Click to expand...
Click to collapse
It says fastboot is not recognized as an internal command
In twrp, it keeps saying starting adb sideload feature
i posted this in another thread. try this...
1. First make sure that you have fastboot driver installed.
2. Power down your Nexus 4 (hold the power button until it shuts off) before rebooting into fastboot mode. You can do this by holding down the the Volume Down and Power buttons simultaneously.
3. Connect your device to your computer. Open up a terminal or command prompt, and navigate to the folder containing the fastboot program.
4. Type fastboot devices into the command line, and you should then see your device’s ID, which means fastboot is setup correctly. if not, check to make sure Google Nexus 4 drivers are installed correctly.
5. now open Nexus 4 toolkit and Flash Google Factory stock Rom. Once you are back to stock continue on from there...
Good Luck!
Zehlek said:
It says fastboot is not recognized as an internal command
Click to expand...
Click to collapse
my bad, it's fastboot-toolkit. But since you have a recovery with sideload already, just download a rom that's working, put it in your nexus 4 toolkit folder, rename it to flash.zip, and type in CMD
"adb-toolkit sideload flash.zip"
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Zehlek said:
Thank you all for your help. What I had to end up doing was extracting the factory image and flash boot, system, and use data IMG files manually with nexus 4 toolkit. My Nexus 4 is alive. Again thank you all very much
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
efan3719 said:
Glad to here it. My heart sank when I read your issue. Happy to see it resolved.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you. I was beginning to panic when I saw there nothing working that would transfer a rom to my sdcard. Again thank you for all your help
Sent from my Nexus 4 using Tapatalk 2

[Q] Nexus 10 stuck on Google logo

Hi I've done stupid thing for myself:
i tried flashing 4.4.2 stock rom. coming from 4.2 (i think) did the usual format data/cache. then rebooted then it loops on google logo. I can go to recovery mode.
So are you rooted? Custom recovery? Looking to flash stock? What bootloader do you have? Ota flash? Fastboot flash?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hoygl3n said:
Hi I've done stupid thing for myself:
i tried flashing 4.4.2 stock rom. coming from 4.2 (i think) did the usual format data/cache. then rebooted then it loops on google logo. I can go to recovery mode.
Click to expand...
Click to collapse
Read this fourm I just help this user recover from the same thing!!
http://forum.xda-developers.com/showthread.php?t=2663286
lj50036 said:
Read this fourm I just help this user recover from the same thing!!
http://forum.xda-developers.com/showthread.php?t=2663286
Click to expand...
Click to collapse
demkantor said:
So are you rooted? Custom recovery? Looking to flash stock? What bootloader do you have? Ota flash? Fastboot flash?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
hi i followed all the instruction till CMD and tried typing fastboot
and nothing came up.
This will help
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
This will help
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I still cant get fastboot up. ive used minimal fastboot and/or SDK Package. also changed the path for environmental variables.
So more info will help, usually the more info you give the faster your issues can be fixed
Are you in bootloader mode? I take it your using windows, what version? Has adb or fastboot ever worked before? When you type
fastboot devices
You get nothing? Can you post a screen shot of terminal, of environmental variables? Are all proper drivers installed? Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? Are you using factory USB cable?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
So more info will help, usually the more info you give the faster your issues can be fixed
Are you in bootloader mode? I take it your using windows, what version? Has adb or fastboot ever worked before? When you type
fastboot devices
You get nothing? Can you post a screen shot of terminal, of environmental variables? Are all proper drivers installed? Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? Are you using factory USB cable?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry about that.
im in fastboot mode with power and both volumes pressed. i can also go into recovery mode TWRP v2.5.0.0
also rooted and yes windows 7 64 bit. recovery mode or fastboot mode . it doesnt recognized my nexus.
not sure if i have the right drivers. i cant find any drivers to download for nexus 10
Does anything pop up in device manager when tablet is plugged into USB while in fastboot, recovery or os? - No
and yes im using nexus 10 OEM cable.
i really appreciate the time to help me out with this issue.
Its no problem,
The SDK should have the drivers you need, or you can install the universal drivers made by koush or a number of others as well. Just Google search or a search xda for terms like
Nexus 10 drivers
Universal android drivers
Android naked drivers
You will find many that will work just fine for you
If in cmd you type
fastboot
And you see a list of commands than you know you have it installed
When you type
fastboot devices
And you see your serial number your good, if just a blank line then you need to get tab to communicate, this is most often a driver issue. If you can't find ones that work let me know and I'll link some to you, also you may need to uninstall old drivers and than manually install new ones, windows doesn't always do the best job of picking the correct drivers
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Its no problem,
The SDK should have the drivers you need, or you can install the universal drivers made by koush or a number of others as well. Just Google search or a search xda for terms like
Nexus 10 drivers
Universal android drivers
Android naked drivers
You will find many that will work just fine for you
If in cmd you type
fastboot
And you see a list of commands than you know you have it installed
When you type
fastboot devices
And you see your serial number your good, if just a blank line then you need to get tab to communicate, this is most often a driver issue. If you can't find ones that work let me know and I'll link some to you, also you may need to uninstall old drivers and than manually install new ones, windows doesn't always do the best job of picking the correct drivers
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
finally found the driver that works and now
i get R32D2009DAT
Im assuming thats serial number whats the next step
Google search
Android factory images
Here you will download the correct one, latest manta for the nexus 10
Then extract the contents of the zip
Now if you want to keep custom recovery that's a good idea but if you want KitKat you will need stock or at least update to the newest twrp (as you current one won't flash kk)
So if you want twrp then google search
Twrp recovery manta
And then find the latest image, 2.6.x?
Oh and its a good idea to check md5sum for both the zip from android source and for the recovery image, both will tell you what it should be in download screen and there are many ways to check, just google search
Windows md5
There is both official and none official, I personally use Linux command line and can't recall the name of the program I use for windows off hand
Also note that the following commands will wipe all from tablet, it is good to do this but if there is anything real important back it up first
Now from fastboot, enter these commands
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now find the bootloader image you extracted from the android .zip
fastboot flash bootloader nameofbootloader.img
Now if you want stock find the system image
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now find the twrp recovery image
fastboot flash recovery nameofrecovery.img
Here you can boot to new recovery and install superuser or just boot to pure stock, or if you want one of the many great custom ROMs you can boot to recovery and use adb sideload to flash one
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
google search
android factory images
here you will download the correct one, latest manta for the nexus 10
then extract the contents of the zip
now if you want to keep custom recovery that's a good idea but if you want kitkat you will need stock or at least update to the newest twrp (as you current one won't flash kk)
so if you want twrp then google search
twrp recovery manta
and then find the latest image, 2.6.x?
Oh and its a good idea to check md5sum for both the zip from android source and for the recovery image, both will tell you what it should be in download screen and there are many ways to check, just google search
windows md5
there is both official and none official, i personally use linux command line and can't recall the name of the program i use for windows off hand
also note that the following commands will wipe all from tablet, it is good to do this but if there is anything real important back it up first
now from fastboot, enter these commands
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
now find the bootloader image you extracted from the android .zip
fastboot flash bootloader nameofbootloader.img
now if you want stock find the system image
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
now find the twrp recovery image
fastboot flash recovery nameofrecovery.img
here you can boot to new recovery and install superuser or just boot to pure stock, or if you want one of the many great custom roms you can boot to recovery and use adb sideload to flash one
sent from my nexus 4 using xda premium 4 mobile app
Click to expand...
Click to collapse
never mind its fixed
you are the man!
Thank you so much!

Help - I'm stuck in a bootloop 4 circles !

Hi I just tried to flash Android 4.4.4 without wiping & losing root using Nexus Root Toolkit
as per this link trendblog.net/flash-android-4-4-4-without-wiping-and-loosing-root/
I had slimkat 4.4.4 and tried to put stock 4.4.4 on this
After success messages the toolkit told me to wait for it to boot up but I am stuck on the four circles.
I have no recovery !!!
What can i do ?
Stop using took kits. They're nothing but trouble. Flash the factory image in fastboot and start over
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
k500zm said:
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
Click to expand...
Click to collapse
First Google 15 second adb install xda. That'll set up fastboot on your PC. Then download the factory image. Google nexus 4 factory image. Extract that using 7-zip or winrar. In there is a flash-all.bat. just double click it. It will wipe your device so backup off the device first
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
k500zm said:
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
Click to expand...
Click to collapse
Here is an excellent guide how to use fastboot:
http://forum.xda-developers.com/showthread.php?t=1907796
It is guide for Nexus 7, but the proceeding is just identic like with all other Nexus devices.
tetakpatalked from Nexus 7 flo
Thanks guys. I am in a bit of a panic here.
couple of questions
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Also is it possible to get my files from the device before I wipe ?
I never used fastboot before - but I'm gonna learn fast now !
k500zm said:
Thanks guys. I am in a bit of a panic here.
couple of questions
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Also is it possible to get my files from the device before I wipe ?
I never used fastboot before - but I'm gonna learn fast now !
Click to expand...
Click to collapse
You say you can't boot into recovery? That's going to be a problem retrieving data
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Is there no way to get cwm back on there ?
k500zm said:
Is there no way to get cwm back on there ?
Click to expand...
Click to collapse
Maybe, you'll need fastboot for that too. Download the latest image file from here. Rename it recovery
http://techerrata.com/browse/twrp2/mako
We'll go from there. You're going to learn a lot more than you bargained for
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
k500zm said:
Thanks guys. I am in a bit of a panic here.
couple of questions
Click to expand...
Click to collapse
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Click to expand...
Click to collapse
Correct, but I'm not sure for the bootloader mode. I don't own a N4. Rather charge your battery first, it should work.
Also is it possible to get my files from the device before I wipe ?
Click to expand...
Click to collapse
If you're lucky, ADB might work even in bootloop if USB debugging was enabled in the developer options. As you didn't wipe, there is a small chance ADB pull might work.
IMHO the best you can do is to flash any custom recovery like TWRP or PhilZ with fastboot. The recovery.img file must be saved in the same folder where fastboot.exe is.
I assume Google USB driver is properly installed?
Fastboot must work, check in the guide I posted link for in my first post here how to check that fastboot commands are working. If "fastboot devices" returns "(your N4 serial No) fastboot" and your custom recovery is saved in proper folder, enter in CMD:
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
After that, enter recovery mode, there is another chance your ADB pull function might work. The phone should charge in recovery mode.
To install SlimKat again, format: system, data, cache, dalvik cache (TWRP) or choose factory reset and "clean to install new ROM" in PhilZ. Then flash ROM and Gapps, best with ADB sideload.
tetakpatalked from Nexus 7 flo
Ok I'm all ears and eager to learn
Ok downloaded - renamed to 'recovery.img'
k500zm said:
Ok I'm all ears and eager to learn
Ok downloaded - renamed to 'recovery.img'
Click to expand...
Click to collapse
Did you install fastboot with the 15 second adb install?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
I have installed Android SDK manager and the 15 sec drivers
I have android bootloader interface in my xp device manager
k500zm said:
I have installed Android SDK manager and the 15 sec drivers
Click to expand...
Click to collapse
OK, we'll try with that. Put your recovery image in the same folder as fastboot.exe. Open a command window in that folder, shift right mouse click in a open area in that folder
Plug your device into the USB port. Type
fastboot devices (return) in the cmd window
Is your device recognized? If it is then in the cmd window type
fastboot flash recovery recovery.img
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
ok - this is what I got...
C:\adb>fastboot devices
fastboot
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.703s
C:\adb>
Ok I have TWRP started on my device [ i use cwm though will my nandroid backup be compatible with twrp ?]
k500zm said:
ok - this is what I got...
C:\adb>fastboot devices
01...... fastboot
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.703s
C:\adb>
Click to expand...
Click to collapse
That sounds excellent, mate! Now try to reboot into the recovery mode
BTW: it isn't recommended to write down your device's serial No in worldwide public forum, it is your privacy in fact. Best edit your post now and remove big part of it (I also did it im my quote of your post)
tetakpatalked from Nexus 7 flo
k500zm said:
Ok I have TWRP started on my device [ i use cwm though will my nandroid backup be compatible with twrp ?]
Click to expand...
Click to collapse
Good job. The nandroid won't be compatible. Let me see if I can find a cwm image. Now that you know how to use fastboot
Sent from my Nexus 5 using XDA Free mobile app
I have a nandroid backup from cwm just before i fcud up - is there any way to restore this ?
Thanks for your help so far geezers

No acess to bootloader/Recovery

Hi Guys,
I had some problems with my beloved zenfone 2. Now i can´t enter in bootloader and recovery, but phone boots normaly.
The thing is it seems the partitions are cracked. My last hope was flashing a new recovery and bootloader with the images i got from this thread: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835 using some programs to flash direct from phone (Tried with "recovery flasher" and "rom installer") but on "rom installer" app shows #ERROR: cannot locate recovery partition:
The history was : I rooted my phone using the zenfone toolkit, then started a wipe cache partition, which didn´t work and i forced off. After that i can´t made any adb connection - i can go to bootloader but doesn´t find my device and can´t write anything - , but i made TWRP recovery work using the "tethered recovery" as show in http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532 and flash the original stock rom. ADB/fastboot still don´t work. After that i entered in TWRP again using the same method and inserted Superuser.zip there, rooting my device. After root i lost Bootloader, but still can go to recovery (using TWRP and CVM programs which have the option "reboot to recovery"), which was still useless since it recognize my phone but adb sideload still don´t work. I even tried the MOFD_update thing - copying the entire rom to sd card and renaming to MOFD update but it shows it can´t update. Then i tried to flash TWRP using the TWRP app and the only thing i did it was lost my recovey too.
Now when i try to go to bootloader only shows the UsB logo (the trident), The same happen if i try to go to recovery by apps.
I think i´ll have to fix partitions mannually, using only phone, but i have no ideia how. Can anyone know what can i do?
Thanks in advance
You broke your recovery. Cleaning cache from stock recovery take a LONG time on the ZF2. You have to be patient.
You're still good if you can get into fastboot though. Just execute
Code:
fastboot format cache
then boot back into recovery. When you're in fastboot, you need to run
Code:
fastboot devices
not adb. Recovery = ADB, bootloader = fastboot
Scratch all that. Reread your post. You've done some very inadvisable things. You should have just formatted from the bootloader instead of bothering to re-root. I have no idea what you've done now.
Trident logo means brick phone...be careful nextime
Mononon said:
You broke your recovery. Cleaning cache from stock recovery take a LONG time on the ZF2. You have to be patient.
You're still good if you can get into fastboot though. Just execute
Code:
fastboot format cache
then boot back into recovery. When you're in fastboot, you need to run
Code:
fastboot devices
not adb. Recovery = ADB, bootloader = fastboot
Scratch all that. Reread your post. You've done some very inadvisable things. You should have just formatted from the bootloader instead of bothering to re-root. I have no idea what you've done now.
Click to expand...
Click to collapse
Thanks Anyway. One thing i don´t understand is why my phone is booting normal. I know i´ll have issues when an update come, but it´s booting normaly
pato2015 said:
Trident logo means brick phone...be careful nextime
Click to expand...
Click to collapse
I hope i will have nextime...
you solved that? just need to reflash recovery.img if you can normally boot and use.
Sent from my ASUS_Z00A using XDA Free mobile app
ityoung said:
you solved that? just need to reflash recovery.img if you can normally boot and use.
Sent from my ASUS_Z00A using XDA Free mobile app
Click to expand...
Click to collapse
i´m trying to flash recovery.img from android. I can boot only for sistem. I can´t boot to bootloader or recovery. I´m trying a lot of apps which says it can flash a recovery from a running android, but none of them works
I also tried the Shuame like you said on another thread, but it doesn´t work. Thanks for your help
It might be possible to do something from a terminal window on your phone, but you would need to take advice from someone who knows what they are doing as I'm only theorizing rather than speaking from any position of knowledge.
Sent from my ASUS_Z00AD using Tapatalk
Is your bootloader unlocked?
dodongobongo said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No. The problems started on my second boot after rooting, i had no chance to unlock bootloader too. I think if i had i can flash a custom recovery using TWRP or CVM apps and flash everything else again, but no, i can´t do that either.
As said above use the terminal app to flash stock recovery by dd command
Make sure u give su before issuing dd
Copy stock recovery to sdcard
Open terminal give these commands one by one
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
reboot recovery
& u r done
Sent from my ASUS_Z008D using XDA Free mobile app
yakub234go said:
As said above use the terminal app to flash stock recovery by dd command
Make sure u give su before issuing dd
Copy stock recovery to sdcard
Open terminal give these commands one by one
su
dd if=/sdcard/recovery.img of=/dev/block/by-name/recovery
reboot recovery
& u r done
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
Thank you Sooo much.
Now i have my recovery back, is there a way i can get bootloader back again using commands like that ? (and one bootloader i can use adb\fastboot ?)
I assume now i can use adb/sideload or MOFUPDATE.zip way (inserting an flashable rom with this name in my memory card so the system will flash like an update when i enter in recovery), but i don´t know what exactly i need to do (and what archives i have to use) to have a bootloader again, considering all ways to unbrick zenfone 2 needs fastboot. If i do that with stock Asus rom i can download from asus site will i have bootloader (and acess to fastboot) again? I´m afraid to do that and lose my root acess and still have no fastboot option. With root at least i can use terminal. I´m really afraid of flashing something that really hardbrick my phone since i have no fastboot, only root.
Can i unlock bootloader using terminal ? Maybe it´s safe if i unlock bootloader and then wipe TWRP using only TWRP app. After that i can flash other rooms and always have TWRP to fix if something goes wrong.
Sorry if i´m bothering. And thank you soo much for your help
I assume u now have recovery working
adb sideload full stock rom
Download the one which is bootloader unlockable from the Asus website & make sure u r download the right file for device
Never flash anything with bootloader locked
Sent from my ASUS_Z008D using XDA Free mobile app
yakub234go said:
I assume u now have recovery working
adb sideload full stock rom
Download the one which is bootloader unlockable from the Asus website & make sure u r download the right file for device
Never flash anything with bootloader locked
Sent from my ASUS_Z008D using XDA Free mobile app
Click to expand...
Click to collapse
Thank you again. Sorry about my insecurities, but i´m still worry. I rooted my phone at first time using the rootkit, one step there says i have to click "checkbeforeaction.bat" which will say i can go with root if i see 1234567ABCDEF as my phone. After that i can´t use adb anymore.
I don´t know why my phone changed to 1234567ABCDEF, i´m not sure if this is the reason i can´t use ADB. After recover my recovery yesterday (thanks for you) i checked "adb devices" on sideload and still shows 1234567ABCDEF. Still afraid to flash a stock rom and the only thing will change is i lost my root.
Maybe it´s a silly questions, but To use sideload i need a .img or a .zip file ? the stock room will flash stock recovery and stock bootloader again? Will i see 1234567ABCDEF again? Can i sideload a pre-rooted room ?Can i sideload just droidboot.img, boot.img and recovery.img? will it be placed on correct place on my phone? I´m really afraid of doing something wrong again.
Sideload the zip file
It should be a full firmware not an ota
adb sideload thezipfilepathonthepc
& wait for it to finish (it takes long time)
& abt that serial no i think its fine
Sent from my Karbonn A1+ Super using XDA Free mobile app
yakub234go said:
Sideload the zip file
It should be a full firmware not an ota
adb sideload thezipfilepathonthepc
& wait for it to finish (it takes long time)
& abt that serial no i think its fine
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
i don´t understand your last phrase "&abt that serial no i think its fine"
You said never flash anything with your bootloader locked. I didn´t unlock my bootloader
Can i flash the image from this thread (item 3.1 method 1) ? http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
yakub234go said:
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
Didn´t work to...
Shows on computer:
"error: protocol fault <no status>
On phone
"you need adb 1.0.32 or newer to sideload to this device.
installation aborted.
E:file path: /cache/recovery/log
E:file path: /cache/recovery/last_log
E:file path: /cache/recovery/last_install
E:file path: /cache/recovery/last_locale
E:file path: /cache/recovery/log
E:file path: /cache/recovery/last_log
E:file path: /cache/recovery/last_install
E:file path: /cache/recovery/command
I´m pretty sure i have the correct adb
yakub234go said:
Don't worry abt anything just sideload the stock rom(u can download it from Asus website)
Sent from my Karbonn A1+ Super using XDA Free mobile app
Click to expand...
Click to collapse
Other thing that can be important:
When on adb sideload, if i request adb devices shows :
Emulator-5554 offline
0123456789ABCDEF sideload
Thats not my phone, again. What is that 012345ABCDEF thing ? can i fix that ?
Try using diff pc
& i forgot to mention u should unroot before flashing
Sent from my Karbonn A1+ Super using XDA Free mobile app

Categories

Resources