Database Users

status 7 error when updating roms? Bricked? **NOW Fixed!*

So it seems I have messed up my phone decently bad
decided to go back and reload everything from scratch but unfortunately flashed back a CWM version thats 3.0.1 and when I try to flash my old recovery (ICS CM9) it gives me error 7
I am guessing thats because I have to install 5.0 CWM can anyone explain to me how to do this?
Thank you so much all!
Yan
More Info:
Ok so heres the deal.
I was originally running CM9 from Nexus MV ICS rom with a Franco Kernel.
All was well and phone was rock solid for weeks since he released with everything working.
as the update came out I was told I should revert back to 2.3.6 and wait for the OTA update that way I could have the true OEM ICS. It is pretty much 90% of why I originally Rooted and unlocked my phone.
I used this link.
http://forum.xda-developers.com/showthread.php?t=1063664
and downloaded
Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
That I flashed using CWM
Phone rebooted fine but had no SuperUser file and seemed like it no longer was rooted so though if I go back and re-root it should be fine.
Went to.
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
and went straight to instruction 5) Open up a command prompt by typing “cmd” under Start->Search Programs and files.
Then type “cd \nexussrootnew” to browse into the directory in Windows. For Linux and Mac, should be similar to “cd /nexussrootnew“.
Then type “fastboot oem unlock“.
Thats when I went back to CWM 3.1.0.1 and tried to install any rom or backup and it just seems to give me Status 7 error.
I hate that I cant figure this out alone but I am a little lost.

Here's a link: http://forum.xda-developers.com/showthread.php?t=1382624
Use the search next time, it took less than 10 seconds for me to find the page.

063_XOBX said:
Here's a link: http://forum.xda-developers.com/showthread.php?t=1382624
Use the search next time, it took less than 10 seconds for me to find the page.
Click to expand...
Click to collapse
Actually I tried this originally
http://forum.xda-developers.com/showthread.php?t=1248760
Still get Status 7!
Sorry I usually search before just forgot to write that in!

Download CWM 5.0.2.0 and rename the .img to recovery.img
(i'll assume you have phone drivers and everything working, and fastboot)
Put the recovery.img into the same directory as your fastboot.exe
Boot into your bootmanager (vol up+power)
Plug phone into PC
Open up CMD prompt and change to the directory where you have fastboot.exe
(cd c:\android\tools) for example
type in:
> fastboot flash recovery recovery.img
reboot to recovery

seriosbrad said:
Download CWM 5.0.2.0 and rename the .img to recovery.img
(i'll assume you have phone drivers and everything working, and fastboot)
Put the recovery.img into the same directory as your fastboot.exe
Boot into your bootmanager (vol up+power)
Plug phone into PC
Open up CMD prompt and change to the directory where you have fastboot.exe
(cd c:\android\tools) for example
type in:
> fastboot flash recovery recovery.img
reboot to recovery
Click to expand...
Click to collapse
I tried that and unfortunately it gives me an error when I try it
says
"Error: cannot load recovery.img"
Used the download from this link!
http://forum.xda-developers.com/showthread.php?t=988686&highlight=recovery
Looks like someone else is having the same issue as me.
http://forum.xda-developers.com/showthread.php?t=996914&page=4

Try to just boot the newer cwm recovery with fastboot
Fastboot boot recovery recovery name.img

albundy2010 said:
Try to just boot the newer cwm recovery with fastboot
Fastboot boot recovery recovery name.img
Click to expand...
Click to collapse
Same error as earlier....
Can Not load
Darn this is frustrating!

sspikey said:
Same error as earlier....
Can Not load
Darn this is frustrating!
Click to expand...
Click to collapse
SWEET just got this phone to boot up again! No network right now for some reason but wifi works!
Here is what I used.
http://forum.xda-developers.com/showthread.php?t=884093
Where should I go from here? Ideas? I am guessing I have to install super user Zip through the current 3.0XX CWM right?
MORE PROGRESS!!!!!
Got CWM 5.0.2.0 loaded on to it by flashing the IMG through CMD
Worked after what I did earlier!
Progressing forward!!!!
Final cherry on top of the cake!!!
works perfectly again accepted my nandroid backup and shes running at 100%
ah feels good!

please help me i am also having the same problem i tried everything nothing seemed to work out and please check my thread ( http://forum.xda-developers.com/showthread.php?t=1533346 ) thnx.

[Q] Wipe device and install factory image via adb?

N4 is broken, but I can use adb commands by going into recovery mode. I'd like to fully wipe the device and install the JWR66Y factory image (which is currently saved on my PC as a .tar file). I'm kind of an adb newb/idiot. I would greatly appreciate any guidance here.
Thanks!

Can you use fastboot to flash stock?
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
Swyped from my Nexus 4 using Tapatalk 4

ddb540 said:
N4 is broken, but I can use adb commands by going into recovery mode. I'd like to fully wipe the device and install the JWR66Y factory image (which is currently saved on my PC as a .tar file). I'm kind of an adb newb/idiot. I would greatly appreciate any guidance here.
Thanks!
Click to expand...
Click to collapse
Hey you might want to look at the Google Nexus Toolkit. You can sideload a file if you already have a custom recovery installed.
http://forum.xda-developers.com/showthread.php?t=1995688
Good luck!

Lord Yurij said:
Can you use fastboot to flash stock?
http://androidforums.com/android-sy...e-how-flash-nexus-factory-image-manually.html
Swyped from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!

ddb540 said:
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!
Click to expand...
Click to collapse
How did the command "fastboot system" even work?
When you flash an image, the command is the following:
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash userdata userdata.img
Etc.
Anyways, you could have simply downloaded a rom, boot in recovery, use "adb push" to copy the file on your phone, then install it normally through your recovery.

abaaaabbbb63 said:
How did the command "fastboot system" even work?
When you flash an image, the command is the following:
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash userdata userdata.img
Etc.
Anyways, you could have simply downloaded a rom, boot in recovery, use "adb push" to copy the file on your phone, then install it normally through your recovery.
Click to expand...
Click to collapse
Sorry, I typed incorrectly. Yes, I did fastboot flash system system.img, etc.

ddb540 said:
Thank you for the response. Was able to push the jwr66y image to the device using adb in recovery mode. Then, did the following:
fastboot boot boot.imdg
fastboot system jwr66y.imdg
fastboot erase userdata
fastboot erase cache
fastboot reboot
Now device is stuck in boot loop. Suggestions?
Thanks!
Click to expand...
Click to collapse
Try to go into recovery and wipe the caches and do a data factory reset, that will probably work.

Convert a tar.md5 file to .img
gee2012 said:
Try to go into recovery and wipe the caches and do a data factory reset, that will probably work.
Click to expand...
Click to collapse
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,

AHLASSICH said:
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,
Click to expand...
Click to collapse
Odin? That's for samsung mate. Won't work here. You need to download the factory images and extract it to get stock recovery. Or just head over to general section and there are thread for flashable stock recovery/modem/kernel. There is also a guide on how to use adb, a very detailed one at that. I'm sure you won't have trouble following it. Just read carefully and do it. All the things you need are given in that thread.
Edit: Guide - http://forum.xda-developers.com/showthread.php?t=2010312

AHLASSICH said:
Most flashable files come as a tar.md5 for use with odin. What do you do with a tar.md5 file if you want to flash it with adb? It appears that adb requires .img files.
My reason for wanting an .img file is that I tried flashing a stock recovery with odin and got an "MD5 Error, Binary is invalid". I have no idea what that means. I just figured I would try the adb approach since I need to learn adb anyway.
I would rather solve the "MD5 Error, Binary is invalid" error and proceed with odin. Since I am a noob, I don't know exactly how to proceed. Can anyone help me resolve this?
Thanks,
Click to expand...
Click to collapse
1. Make sure you have Android SDK installed. if not download here.
2. Download Nexus 4 factory rom from here.
3. Unzip the factory rom [occam-kot49h-factory]. If you dont know how to unzip. Download and install Winrar. Open the file with Winrar and Extract it somewhere in your computer.
4. Turn off your phone
3. Hold Volume up + Power; once it loads up to bootloader; connect it to your computer
5. The file [occam-kot49h-factory] you extract it early; in there you should see a file flash-all-bat. Open it [run it as admin if you are running Vista/7/8] and let it do its magic. Your phone will factory reset.

http://www.wugfresh.com/nrt/
go to this website, download the toolkit, and connect your nexus to computer on fastboot mode, do some few clicks, and boom, done

Getting no command when trying to get twrp working

Not sure if I am doing it right but how do you get twrp to show up on your phone? I unlocked bootloader and I think I flashed twrp correctly but when I try to go to recovery it says no command. Anyone else ran into this issue or know what is wrong? Thanks

While in Fast boot, use the volume buttons to navigate the menu to Recovery, then hit the power button to select it. It TWRP flashed correctly, it will boot into it.

Uncle Louie said:
While in Fast boot, use the volume buttons to navigate the menu to Recovery, then hit the power button to select it. It TWRP flashed correctly, it will boot into it.
Click to expand...
Click to collapse
Ok, so I am doing it right but it goes to no command. Not sure what the issue is.

itsyourboyL said:
Ok, so I am doing it right but it goes to no command. Not sure what the issue is.
Click to expand...
Click to collapse
I have the exact same issue, tried it with windroid and then just flashing it myself.

Try reinstalling TWRP and be sure to boot directly into it from fastboot. If you don't do that initially than the install won't stick.

swieder711 said:
Try reinstalling TWRP and be sure to boot directly into it from fastboot. If you don't do that initially than the install won't stick.
Click to expand...
Click to collapse
ye I feel like an idiot now, took me an hour to figure that out >.>

help
swieder711 said:
Try reinstalling TWRP and be sure to boot directly into it from fastboot. If you don't do that initially than the install won't stick.
Click to expand...
Click to collapse
So what does it mean when you say "boot directly into it". I have a moto x pure edition running marshmallow. I used Windroid and when flashing TWRP that's what I got, "no command".
The phone will boot normally but I'd like to complete this process.
Thank you.

davidkoby said:
So what does it mean when you say "boot directly into it". I have a moto x pure edition running marshmallow. I used Windroid and when flashing TWRP that's what I got, "no command".
The phone will boot normally but I'd like to complete this process.
Thank you.
Click to expand...
Click to collapse
Don't boot into system. If you do your phone tries to replace custom recovery with stock.
Flash twrp from fastboot. Then use the volume rocker and power key to choose boot recovery. Flash a systemless root from twrp, and it will stop getting replaced when you boot normally.

jason2678 said:
Don't boot into system. If you do your phone tries to replace custom recovery with stock.
Flash twrp from fastboot. Then use the volume rocker and power key to choose boot recovery. Flash a systemless root from twrp, and it will stop getting replaced when you boot normally.
Click to expand...
Click to collapse
Just so I understand how to do that....when the windroid asks if I want to reboot I say "no" and then by holding the volume down and power key I MANUALLY reboot into the bootloader to do this?
---------- Post added at 05:53 AM ---------- Previous post was at 05:04 AM ----------
jason2678 said:
Don't boot into system. If you do your phone tries to replace custom recovery with stock.
Flash twrp from fastboot. Then use the volume rocker and power key to choose boot recovery. Flash a systemless root from twrp, and it will stop getting replaced when you boot normally.
Click to expand...
Click to collapse
So this is my problem. ONce I have flashed TWRP and then use the volume key to got to "boot recovery" and press the power button THAT's when I get the "no command" error. What's going on?

davidkoby said:
Just so I understand how to do that....when the windroid asks if I want to reboot I say "no" and then by holding the volume down and power key I MANUALLY reboot into the bootloader to do this?
---------- Post added at 05:53 AM ---------- Previous post was at 05:04 AM ----------
So this is my problem. ONce I have flashed TWRP and then use the volume key to got to "boot recovery" and press the power button THAT's when I get the "no command" error. What's going on?
Click to expand...
Click to collapse
How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery .img
(Replace with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
http://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Edit:
Don't forget to check md5. You could ve installing a corrupt file.

Here's the easy answer.
boot into bootloader, then:
fastboot flash recovery twrpfilename.img
THEN, do this:
fastboot reboot-bootloader
LAST, use volume rocker to select recovery. It should successfully boot TWRP now.
The trick is AFTER FLASHING, reboot back into bootloader, THEN boot into TWRP. Should do the trick.
Good Luck!
PS: the "No command" isn't an error -- it's stock recovery. If you hold down volume up and tap power, the stock recovery option appear. This is irrelevant though since you are flashing TWRP, but thought I'd add.

Hitti2 said:
How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery .img
(Replace with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
http://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Edit:
Don't forget to check md5. You could ve installing a corrupt file.
Click to expand...
Click to collapse
Ok this makes more sense. So my next question is "how do I check md5"?

davidkoby said:
Ok this makes more sense. So my next question is "how do I check md5"?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.fab.md5
Load up the file you want to check.
Copy md5 code or if there is an md5 file you can download it edit it with notepad to get the md5 code or u can load up the md5 file in the paste box of md5 checker.
Click check.
If the md5 matches you are good to install.
if the md5 mismatches, redownload.
Most android downloads comes with a md5 code underneath the download.
Sent from XT1575, TPXMM 2.5, Frankenclark 0.6

Hitti2 said:
https://play.google.com/store/apps/details?id=com.fab.md5
Load up the file you want to check.
Copy md5 code or if there is an md5 file you can download it edit it with notepad to get the md5 code or u can load up the md5 file in the paste box of md5 checker.
Click check.
If the md5 matches you are good to install.
if the md5 mismatches, redownload.
Most android downloads comes with a md5 code underneath the download.
Sent from XT1575, TPXMM 2.5, Frankenclark 0.6
Click to expand...
Click to collapse
makes sense but now when I boot to fastboot and go to my ADB fastboot directory and type fastboot flash twrp.img the system comes back with "error: cannot determine image filename for twrp.img"

davidkoby said:
makes sense but now when I boot to fastboot and go to my ADB fastboot directory and type fastboot flash twrp.img the system comes back with "error: cannot determine image filename for twrp.img"
Click to expand...
Click to collapse
Check the md5. Did u check it?
Sent from XT1575, TPXMM 2.5, Frankenclark 0.6

Hitti2 said:
Check the md5. Did u check it?
Sent from XT1575, TPXMM 2.5, Frankenclark 0.6
Click to expand...
Click to collapse
that I did not. Can it be checked on a PC?

davidkoby said:
that I did not. Can it be checked on a PC?
Click to expand...
Click to collapse
Yes. Look for a md5 checker for pc.
Sent from XT1575, TPXMM 2.5, Frankenclark 0.6

Hitti2 said:
Yes. Look for a md5 checker for pc.
Sent from XT1575, TPXMM 2.5, Frankenclark 0.6
Click to expand...
Click to collapse
ok did that and it came out ok. What do I do with the string hash that it output?

davidkoby said:
makes sense but now when I boot to fastboot and go to my ADB fastboot directory and type fastboot flash twrp.img the system comes back with "error: cannot determine image filename for twrp.img"
Click to expand...
Click to collapse
The correct syntax is:
fastboot flash RECOVERY twrp.img
You didn't tell fastboot which partition to flash the image file to.

samwathegreat said:
The correct syntax is:
fastboot flash RECOVERY twrp.img
You didn't tell fastboot which partition to flash the image file to.
Click to expand...
Click to collapse
Success! Thank you all. So how do I get this God-awful screen that says "your bootloader is unlocked" off of here using TWRP?

Hardbrick/total brick help me to understand my situation

Hello guys, my zenfone has the image "ASUS in search of incredible" on the center and upward has the written ""Fastboot Mode!!! long press power key to restart system""" in light blue!! i readed other similiar threads but i'm unable to resolve, i tried to download the official rom on the asus site and i follow threads of other models of zenfone 2 hardbricked in the Fastboot mode!
like this! ----((Type fastboot devices and hit Enter. Your device should appear.
13. Type fastboot flash fastboot droidboot.img (be very careful in writting this line). Hit Enter. Wait till it's done.
14. Type fastboot flash recovery recovery.img and hit Enter. Wait till it's done.
15. Type fastboot flash boot boot.img and hitEnter.))
I don't find those files (and files like system.img) in the zenfone 2 laser rom zip(UL-ASUS_Z00E-WW-13.10.7.1-user.zip) but only Boot.img ,system.new.dat... nothing useful.
I dowloaded a official recovery and twrp, i tried to flash the recovery.img and the boot.img and i try to reboot in bootloader mode but nothing, than i tried to flash the trwp.img but the process failed!
I've a Raw file image of the rom but i don't know if it possible to install it in fastboot and what is the right Command on fastboot!
This is all, i hope that someone can help me

Download stock recovery from here and flash with fastboot flash recovery name_of_recovery.img and download official firmware from official site.
Go in to recovery and wipe cache and data,after select update from adb,open adb and write this command:adb sideload name_of_firmware.zip or put firmware.zip in to sd and rename update.zip go in to recovery wipe cache and data and select update from sdcard and select update.zip

thank you for the response, after the flash of the original recovery, i tried to go in recovery with "volume - and power botton" but nothing only asus image, than i tried with fastboot command --->"fastboot boot recovery.img" and Failed( remote dtb not found)

Marlin92 said:
thank you for the response, after the flash of the original recovery, i tried to go in recovery with "volume - and power botton" but nothing only asus image, than i tried with fastboot command --->"fastboot boot recovery.img" and Failed( remote dtb not found)
Click to expand...
Click to collapse
Go in to fastboot,from adb flash stock recovery recovery (mm 16) and reboot in to recovery

Gabbro16Hz said:
Go in to fastboot,from adb flash stock recovery recovery (mm 16) and reboot in to recovery[/QUO
ok i did it, but the phone don't reboot in to recovery... this is the problem....
Click to expand...
Click to collapse

Marlin92 said:
Gabbro16Hz said:
Go in to fastboot,from adb flash stock recovery recovery (mm 16) and reboot in to recovery[/QUO
ok i did it, but the phone don't reboot in to recovery... this is the problem....
Click to expand...
Click to collapse
It's impossible,you nave unlocked bootloader?
Click to expand...
Click to collapse

Gabbro16Hz said:
Marlin92 said:
It's impossible,you nave unlocked bootloader?
Click to expand...
Click to collapse
i think no mate, because the phone it's not mine , i'm trying to help my friend that tried to root the phone but failed ahahahah ...
You know if is possible to unlock the bootloader now in fastboot mode and what is the command to write? thank you for the patience
Click to expand...
Click to collapse

Marlin92 said:
Gabbro16Hz said:
i think no mate, because the phone it's not mine , i'm trying to help my friend that tried to root the phone but failed ahahahah ...
You know if is possible to unlock the bootloader now in fastboot mode and what is the command to write? thank you for the patience
Click to expand...
Click to collapse
This is the solutionowload official Recovery and flash,go in to recovery and select adb sideload go in adb from pc and write:adb sideload Name_Of_Firmware.zip
Click to expand...
Click to collapse

Gabbro16Hz said:
Marlin92 said:
This is the solutionowload official Recovery and flash,go in to recovery and select adb sideload go in adb from pc and write:adb sideload Name_Of_Firmware.zip
Click to expand...
Click to collapse
nothing! My friend doesn't remember if he unlocked the bootloader, the phone doesn't go in recovery... So the problem is the unlocked bootloader or a locked bootloader?!
from your answer I understand that if it is unlocked i can go in recovery, so i assume that the bootloader it's locked and for this i can't go in recovery...
Click to expand...
Click to collapse

I'm with a similar problem, I did not do the unlock bootloader but I can install TWRP with no problems. But my biggest problem is the time of system.img where it appears the following error: error: file too large
i'm stuck in asus screen to :crying:
Sorry for my bad english

pudiim1 said:
I'm with a similar problem, I did not do the unlock bootloader but I can install TWRP with no problems. But my biggest problem is the time of system.img where it appears the following error: error: file too large
i'm stuck in asus screen to :crying:
Sorry for my bad english
Click to expand...
Click to collapse
same here! i converted the system.new.dat file in system.img and tried to flash it, but it appears the same error" file too large...
One question your phone after the flash of TWRP doesn't go in recovery right?

Marlin92 said:
same here! i converted the system.new.dat file in system.img and tried to flash it, but it appears the same error" file too large...
One question your phone after the flash of TWRP doesn't go in recovery right?
Click to expand...
Click to collapse
Recovery mode work's fine for my, but I can not install or via adb or via fastboot

pudiim1 said:
I'm with a similar problem, I did not do the unlock bootloader but I can install TWRP with no problems. But my biggest problem is the time of system.img where it appears the following error: error: file too large
i'm stuck in asus screen to :crying:
Sorry for my bad english
Click to expand...
Click to collapse
but if you can install the TWRP and you can go in to recovery, you can install with adb sideload the all file stock rom zip

Marlin92 said:
but if you can install the TWRP and you can go in to recovery, you can install with adb sideload the all file stock rom zip
Click to expand...
Click to collapse
I tried many, many zip files and i had different errors , the more I got the most was the following : Could not find ' meta- inf / com / google / android / update -binary ' in the zip file .

pudiim1 said:
I tried many, many zip files and i had different errors , the more I got the most was the following : Could not find ' meta- inf / com / google / android / update -binary ' in the zip file .
Click to expand...
Click to collapse
you've tried to clean all with the command " fastboot erase" boot,cache,system and userdata? i'm not sure if this work but in almost all guides recommended to erase old boot, cache, system & userdata partitions

I tried but no sucess

Stuck loading twrp

Hi,
When my S7 Edge boots up it jumps to twrp but it's stuck on the teamwin logo screen and does not advance to menu.
This happened after I tried to format the data partition to ext4 via twrp and it just got stuck there too so when I rebooted it landed in this situation.
Unfortunately reflashing twrp or reflashing the stock rom via ODIN does not work as COM3 is recognized but then when I press start it doesnt do anything....
Also tried the suggestion I read online of:
fastboot format cache
fastboot format userdata
These commands just get stuck on <waiting for device>.
Also tried adb shell recovery --wipe_data but it gets stuck at I:LANG: en
Any help will be much appreciated!
Thanks

This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
redirts1978 said:
Hi,
When my S7 Edge boots up it jumps to twrp but it's stuck on the teamwin logo screen and does not advance to menu.
This happened after I tried to format the data partition to ext4 via twrp and it just got stuck there too so when I rebooted it landed in this situation.
Unfortunately reflashing twrp or reflashing the stock rom via ODIN does not work as COM3 is recognized but then when I press start it doesnt do anything....
Also tried the suggestion I read online of:
fastboot format cache
fastboot format userdata
These commands just get stuck on <waiting for device>.
Also tried adb shell recovery --wipe_data but it gets stuck at I:LANG: en
Any help will be much appreciated!
Thanks
Click to expand...
Click to collapse

HELP!!!! cant get my phone to be recogniced by adb, I have the same problem,
if its on TWRP boot screen or RECOVERY (blue downloading.... screen) its the same!!!
please help
redirts1978 said:
This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
Click to expand...
Click to collapse

i have exactly the same problem but cant boot to twrp or to OS ...only download mode...tried to flash twrp again not worked now try to flash stock firmware via odin ....PLEASE HELP ME

Kackwuerstchen said:
i have exactly the same problem but cant boot to twrp or to OS ...only download mode...tried to flash twrp again not worked now try to flash stock firmware via odin ....PLEASE HELP ME
Click to expand...
Click to collapse
I don't know what are you doing wrong but when I was stuck in this situation, I flashed stock firmware from sammobile and it fixed the problem.
Make sure you downloaded correct firmware.

Hi,
I know, its quite long time you solved this, but in which mode should be phone to use adb commands?
redirts1978 said:
This is how I solved it in the end.
With cable connected I did:
1. adb push boot.img /external_sd
2. adb shell
3. dd if=/external_sd/boot.img of=/dev/block/platform/155a0000.ufs/by-name/RECOVERY
4. fastboot format cache
5. fastboot format userdata
6. adb shell recovery --wipe_data
7. adb fastboot recovery
Notes:
The boot.img was obtained from a downloaded stock rom image and by decompressing the AP file (just open it with 7Zip) and then you need to uncompress boot.img.lz4 with 7zip zstandard (look it up)
Step 1 took sometime to run since TWRP was stuck loading using a lot of CPU as phone was really really hot!
Sometime I needed to do a adb fastboot recovery and then quickly run and rerun command in step 1 until it succeeded.
Step 6 is redundant but is there just to be safe.
After this you are booted back to a stock recovery where you can use Odin to flash what you want.
In my case I flashed a stock rom and then flashed TWRP again.
Click to expand...
Click to collapse

dankovac1999 said:
Hi,
I know, its quite long time you solved this, but in which mode should be phone to use adb commands?
Click to expand...
Click to collapse
Same problem and question here