Getting error 7 upon flashing custom rom - Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot

Good morning everyone,
I was finally able to get out of my previous situation (bricked phone) thanks to your help, i can now fully load my phone (Samsung Galaxy A5 SM-A500FU).
I wanted to go back to modding right again cause i really dislike the samsung software (i actually have stock 6.0.1 firmware).
I flashed TWRP 3.0.2 with odin, and then tried to flash Cyanogenmod 13 taken from the proper thread. Tried to flash it, got error 7. I try to get information on that error and discovered it should be about rom version not right for my model. I was already sure i was trying to flash the correct rom, but i downloaded it again to be 100% sure. same error. Followed a guide who told me to edit some script file and remove some text lines, did it. Still error 7. Tried to flash with that "signature option" unselected. Still error 7.
Also tried to flash Cyanogenmod 12. something for my device, still error 7.
Do you have any clue on how to get out from this situation? maybe trying a different recovery?
I never had this kind of error, and i flashed dozens of time on multiple devices
Thank you in advance as always for your patience

Dharmost said:
Good morning everyone,
I was finally able to get out of my previous situation (bricked phone) thanks to your help, i can now fully load my phone (Samsung Galaxy A5 SM-A500FU).
I wanted to go back to modding right again cause i really dislike the samsung software (i actually have stock 6.0.1 firmware).
I flashed TWRP 3.0.2 with odin, and then tried to flash Cyanogenmod 13 taken from the proper thread. Tried to flash it, got error 7. I try to get information on that error and discovered it should be about rom version not right for my model. I was already sure i was trying to flash the correct rom, but i downloaded it again to be 100% sure. same error. Followed a guide who told me to edit some script file and remove some text lines, did it. Still error 7. Tried to flash with that "signature option" unselected. Still error 7.
Also tried to flash Cyanogenmod 12. something for my device, still error 7.
Do you have any clue on how to get out from this situation? maybe trying a different recovery?
I never had this kind of error, and i flashed dozens of time on multiple devices
Thank you in advance as always for your patience
Click to expand...
Click to collapse
When u get the error, go to ADVANCED and "Copy log" to sdcard, upload here and maybe we can help :good:

TheAbraham696 said:
When u get the error, go to ADVANCED and "Copy log" to sdcard, upload here and maybe we can help :good:
Click to expand...
Click to collapse
Here you go, sir

Dharmost said:
Here you go, sir
Click to expand...
Click to collapse
If i'm right error it's caused by broked signature in zip cuz u edited for skip devicename assert. So u need to sign again the zip or delete all files in "rom.zip/META-INF", only files! No the "com" folder.
And r u doing a factory reset before install?
Enviado desde mi SM-J710F mediante Tapatalk

TheAbraham696 said:
If i'm right error it's caused by broked signature in zip cuz u edited for skip devicename assert. So u need to sign again the zip or delete all files in "rom.zip/META-INF", only files! No the "com" folder.
And r u doing a factory reset before install?
Enviado desde mi SM-J710F mediante Tapatalk
Click to expand...
Click to collapse
I'm sorry sir, i'm not sure i fully understood your message :
The attached lo was a result of flashing the regular custom rom (not the edited one), don't remember if i had the signature option ticked or not. What are You suggesting me To do? On this try i didn't resect factory (no dalvik or cache ) But i di reset those 3 in previous tries And always got error 7

Dharmost said:
I'm sorry sir, i'm not sure i fully understood your message :
The attached lo was a result of flashing the regular custom rom (not the edited one), don't remember if i had the signature option ticked or not. What are You suggesting me To do? On this try i didn't resect factory (no dalvik or cache ) But i di reset those 3 in previous tries And always got error 7
Click to expand...
Click to collapse
You need to put in phone/sdcard the rom without any edition, do a factory reset, then flash

TheAbraham696 said:
You need to put in phone/sdcard the rom without any edition, do a factory reset, then flash
Click to expand...
Click to collapse
This is what i did the first time i tried to flash, didn't worked. I tried again, and incredibly the thing worked itself out. I have no idea what happened honestly, but now i'm back on track!
Thank you so much for assistence

Related

[Q] SW Rev Check Fail fused 2 Binanary 1

hey
Could someone please please help me get my phone (sm-n9005) Back on. My phone has been off for the last 12 hours try to figure out how to restore back to stock. i am literrally pulling my hair out.
I keep getting this error message when restoring through odin SW REV CHECK FAIL: [ABOOT]FUSED 2 > BINARY 1
Please could someone tell me a fix for this i would really really really appreciate it.
Thank you
BUMP anyone pls
Are you trying to downgrade?
Little more info would probably help
SM-N9005 via Tapatalk 2
sewe said:
Are you trying to downgrade?
Little more info would probably help
SM-N9005 via Tapatalk 2
Click to expand...
Click to collapse
thanks for the reply
i just simply want to get the phone working
i orignally tried to flash from TGY hong kong firmware to BTU uk firmware, but that didnt work so i have tried to retry flashing the hong kong firmware
but odin gives me the [aboot] fused 2 > Binary 1 error
i tried doing emergency repair from kies too still gives me the same error
DjeMBeY said:
SW REV. CHECK FAIL : fused:2, Binary: 1 is when you try to downgrade aboot.mbn (bootloader) or try to flash incorrect system/csc etc..
If you get this message , just reboot in Download mode and flash correct package..
Click to expand...
Click to collapse
SM-N9005 via Tapatalk 2
sewe said:
SM-N9005 via Tapatalk 2
Click to expand...
Click to collapse
I am getting the same error when I try to flash back to the stock ROM and unroot my Verizon Note 3. I made the mistake of accepting the OTA update on my rooted device, did not have custom ROM or anything. The installation seemed to go okay but apparently wiped out the root. Everything was working fine but my root apps so I thought the device was essentially stock. I tried the Dela Vega Root method and it failed several attempts. So I tried flashing a stock ROM in Odin and I get the message you got. I tried downloading the stock ROM on two different occasions in case it was corrupted but still not working. Is my device bricked or is there something I can do? Any help would be appreciated.
Got my phone unbricked by following the directions in this thread. Installed pit file and my phone rebooted! Thank G-d! Was able to root with Kingo. De la vega root does not work with the firmware upgrade.
Back to life
I had same issue and restored it . Follow this : http://forum.xda-developers.com/showthread.php?t=2511880
Need Help
I need help too
Im having the same problem i have been trying for like 2 days now.
I tried to upgrade my phone to 4.4.2 but it didnt work and when i tried to flash back my old Rom im getting the same thing
"SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
need help want to fix my phone.
i tried three different roms and Odin came back with different errors. but errors the less.:crying:
Help:crying::crying::crying:
StarBoy007 said:
I need help too
Im having the same problem i have been trying for like 2 days now.
I tried to upgrade my phone to 4.4.2 but it didnt work and when i tried to flash back my old Rom im getting the same thing
"SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
need help want to fix my phone.
i tried three different roms and Odin came back with different errors. but errors the less.:crying:
Help:crying::crying::crying:
Click to expand...
Click to collapse
You cannot go back or restore an old ROM, you have upgraded to 4.4.2 with NA6 Bootloader, so you can ONLY Run NA6 Bootloader which means you are stuck on KitKat now..
Reflash Kitkat 4.4.2 Stock and you're good to go :good:
help
radicalisto said:
You cannot go back or restore an old ROM, you have upgraded to 4.4.2 with NA6 Bootloader, so you can ONLY Run NA6 Bootloader which means you are stuck on KitKat now..
Reflash Kitkat 4.4.2 Stock and you're good to go :good:
Click to expand...
Click to collapse
THanksfor the replay but the tjing is when i was installing kitkat Odin came up with an error and it failed so the upgrade didn't go through. So does it mean I'm stuck with kitkat. The thing is I tried 2 other kitkat and none of them worked. So when I tried to go back to my old ROM Odin always coming up. with errors. "FAIL (Auth)"
What does that mean..... :crying:
StarBoy007 said:
THanksfor the replay but the tjing is when i was installing kitkat Odin came up with an error and it failed so the upgrade didn't go through. So does it mean I'm stuck with kitkat. The thing is I tried 2 other kitkat and none of them worked. So when I tried to go back to my old ROM Odin always coming up. with errors. "FAIL (Auth)"
What does that mean..... :crying:
Click to expand...
Click to collapse
Yeah you'll have upgraded cause it'll have installed the Bootloader then tried the ROM before the failure. -
What model/region are you using ? Is it a HK note?
help
radicalisto said:
Yeah you'll have upgraded cause it'll have installed the Bootloader then tried the ROM before the failure. -
What model/region are you using ? Is it a HK note?
Click to expand...
Click to collapse
Ok no problem I understand
But I tried installing 4.4.2
But no luck it's not updating. Odin giving me errors every time
Do you have any idear when i can get a rom that can work for me
Plz
well i am using Hong Kong
1 Minute I will edit and give you link to fix your device :good:
Follow exactly these steps (I've fixed the second link.). Update progress.
METHOD
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
Thanks to @rinuvimal posting here
I've updated working links here:
METHOD
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://d-h.st/gb3
Download Sweet Rom and place it in ExtSDcard http://forum.xda-developers.com/showthread.php?t=2487425
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
rinuvimal said:
I've updated working links here:
METHOD
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://d-h.st/gb3
Download Sweet Rom and place it in ExtSDcard http://forum.xda-developers.com/showthread.php?t=2487425
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
Click to expand...
Click to collapse
@StarBoy007, after you try this out, please update your handset details and whether it worked for you. Cheers. Will help someone else!
thanks
rinuvimal said:
@StarBoy007, after you try this out, please update your handset details and whether it worked for you. Cheers. Will help someone else!
Click to expand...
Click to collapse
well first of all i wanna say thanks for the help. i really needed it. but sad to say the final part didnt go through. i did exactly what you said nut the phone got stuck in a boot loop at the Samsung note 3. i left it for one hour but it was still the same thing. so i took out the battery and wipe the phone clean with factory resent and rebooted the phone but the phone staid in the loop. i legit there over night and there is still no chang. any other advice.
:crying::crying::crying::crying::crying::crying:
StarBoy007 said:
well first of all i wanna say thanks for the help. i really needed it. but sad to say the final part didnt go through. i did exactly what you said nut the phone got stuck in a boot loop at the Samsung note 3. i left it for one hour but it was still the same thing. so i took out the battery and wipe the phone clean with factory resent and rebooted the phone but the phone staid in the loop. i legit there over night and there is still no chang. any other advice.
:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Try using PIT file, then re-flashing SweetROM, JackyawayROM or FlexKAT ROM
StarBoy007 said:
well first of all i wanna say thanks for the help. i really needed it. but sad to say the final part didnt go through. i did exactly what you said nut the phone got stuck in a boot loop at the Samsung note 3. i left it for one hour but it was still the same thing. so i took out the battery and wipe the phone clean with factory resent and rebooted the phone but the phone staid in the loop. i legit there over night and there is still no chang. any other advice.
:crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Don't worry, as long as you can get into recovery and download modes, there will be a solution, its only a matter of time before we zone in on a solution.
What CSC region phone do you have? Dial *#1234# and check what the CSC code is. Also how much storage do you have on your phone 16Gb or 32GB?
R
thanks
rinuvimal said:
Don't worry, as long as you can get into recovery and download modes, there will be a solution, its only a matter of time before we zone in on a solution.
What CSC region phone do you have? Dial *#1234# and check what the CSC code is. Also how much storage do you have on your phone 16Gb or 32GB?
R
Click to expand...
Click to collapse
well thanks..
i know that the problem is not that big anymore its just getting the right rom. well i cant dial anything so i cant check for the CSC but im wondering is there any other way to get the CSC region well the phone was bought officially in hong kong.
do you have links to the other roms you suggested earlyer that would be helpful.
thanks again.

[Q] Accidently closed TWRP

Hi guys, I will try and explain this as simple as possible.
I as trying to install cyanogenmod 11 on my phone, and everything seemed to go alright until I made a mistake. I used TWRP to first backup my stock rom on the phone, and then when I was supposed to reboot into the app, I accidently rebooted the phone.
Now the problem is that the phone does not have any OS installed, so what is happening is that it's trying to boot into an OS that's not there, and instead ends up being stuck on the Samsung logo. I can enter Odin mode just fine, but for the love of god I cannot seem to figure how to get back into the TWRP application, or if it is even possible.
I do have the backup of the ROM stored on my SD card, and I've now moved it over to my PC, but it still does not seem to help me in any way. I've trid to launch the Odin3 program on my pc, in an attempt to to try and launch in TWRP through that, but it has all been without any success, so now I come to this board of guinesses, asking for help!
As an added bit of information, this was my first time trying to install a custom rom, so yeah.. Puff..
- The lost Dane.
- Edit -
I tried to "flash" by doing what this link said, in the hopes that my phone would boot into the program, but alas, it only booted back to the logan saying "samsung Galaxy Note 3 SM-N9005" :/
http://forum.xda-developers.com/showthread.php?p=30694404
-- Edit Edit --
To make it super clear ... If I could get back into TWRP, I would be able to run my backup. I know how that app works, I just simply cannot get back into, and I do not know if it is even possible. I've searched and tried various guides to "flash TWRP through Odin" but it has all been without any success... :/
Thaelern said:
Hi guys, I will try and explain this as simple as possible.
I as trying to install cyanogenmod 11 on my phone, and everything seemed to go alright until I made a mistake. I used TWRP to first backup my stock rom on the phone, and then when I was supposed to reboot into the app, I accidently rebooted the phone.
Now the problem is that the phone does not have any OS installed, so what is happening is that it's trying to boot into an OS that's not there, and instead ends up being stuck on the Samsung logo. I can enter Odin mode just fine, but for the love of god I cannot seem to figure how to get back into the TWRP application, or if it is even possible.
I do have the backup of the ROM stored on my SD card, and I've now moved it over to my PC, but it still does not seem to help me in any way. I've trid to launch the Odin3 program on my pc, in an attempt to to try and launch in TWRP through that, but it has all been without any success, so now I come to this board of guinesses, asking for help!
As an added bit of information, this was my first time trying to install a custom rom, so yeah.. Puff..
- The lost Dane.
- Edit -
I tried to "flash" by doing what this link said, in the hopes that my phone would boot into the program, but alas, it only booted back to the logan saying "samsung Galaxy Note 3 SM-N9005" :/
http://forum.xda-developers.com/showthread.php?p=30694404
-- Edit Edit --
To make it super clear ... If I could get back into TWRP, I would be able to run my backup. I know how that app works, I just simply cannot get back into, and I do not know if it is even possible. I've searched and tried various guides to "flash TWRP through Odin" but it has all been without any success... :/
Click to expand...
Click to collapse
Did you hold volume up+home+power button to get into recovery mode?
In case your twrp get corrupted due to flashing failure previously
1. Download twrp from the following. 2.6.3.7 if you were running 4.3 or 2.6.3.8 if you were running 4.4.2(not sure if 2
6.3.8 is 4.3 compatible). For odin flashable use the one with .tar
http://www.techerrata.com/browse/twrp2/hlte
2. Get into download mode(vol down+home+power)
3. Link the downloaded .tar to pda in odin. Odin log should show 'added' once you connect phone to pc
4. Start the process. Once finish phone should boot into recovery automatically but it'll try to boot back into OS. Just hold vol up+home+power button to get back into recovery
Rosli59564 said:
Did you hold volume up+home+power button to get into recovery mode?
Click to expand...
Click to collapse
When I do that, I get an ultra short blue text appearing on the screen, before it goes into downloading mode, with a red text saying "Could not do normal boot." So it basically goes right into odin mode.
Thaelern said:
When I do that, I get an ultra short blue text appearing on the screen, before it goes into downloading mode, with a red text saying "Could not do normal boot." So it basically goes right into odin mode.
Click to expand...
Click to collapse
I edited my post. You need to reflash twrp
You are an absolute god. I wish I could show my appreciation, but I fear words isn't even enough to even begin.. I managed to get into TWRP now, though my backup rom doesn't show up anymore, but I suppose that's because I run a different version of TWRP than I did first? Idk, but really appreciate that you were able to get me back into TWRP.
Thaelern said:
You are an absolute god. I wish I could show my appreciation, but I fear words isn't even enough to even begin.. I managed to get into TWRP now, though my backup rom doesn't show up anymore, but I suppose that's because I run a different version of TWRP than I did first? Idk, but really appreciate that you were able to get me back into TWRP.
Click to expand...
Click to collapse
Yes if you know your previous twrp version than you can restore your old rom backup
---------- Post added at 08:44 AM ---------- Previous post was at 08:40 AM ----------
Thaelern said:
You are an absolute god. I wish I could show my appreciation, but I fear words isn't even enough to even begin.. I managed to get into TWRP now, though my backup rom doesn't show up anymore, but I suppose that's because I run a different version of TWRP than I did first? Idk, but really appreciate that you were able to get me back into TWRP.
Click to expand...
Click to collapse
Right you need your previous twrp version to use the backup
Hehe you can actually press the thanks button
Rosli59564 said:
Yes if you know your previous twrp version than you can restore your old rom backup
---------- Post added at 08:44 AM ---------- Previous post was at 08:40 AM ----------
Right you need your previous twrp version to use the backup
Hehe you can actually press the thanks button
Click to expand...
Click to collapse
I really do appreciate the help you've given, but I have one final request, and I really do hope it isn't too much to ask. Say I am unable to find the same version of TWRP, I will have to actually flash cyanogenmod onto my device. I don't think it should be too tough now that I've managed to launch into TWRP, because now I should be able to just put the rom on my SD card, and then install the files, no?
if it helps you, my device is SM-N9005, and I had 4.3 when I started this whole thing. Cheers!
- Edit.
I tried to download the Nighty build from CyanogenMod's own homepage, but when I try and install it, it says failed, giving me an erro that says "This package is for "hlexx" devices: This is a." That's all it says ... Hmfh. Sooooooooo... Yes! I'm in recovery mode now, but without any rom. :/
Thaelern said:
I really do appreciate the help you've given, but I have one final request, and I really do hope it isn't too much to ask. Say I am unable to find the same version of TWRP, I will have to actually flash cyanogenmod onto my device. I don't think it should be too tough now that I've managed to launch into TWRP, because now I should be able to just put the rom on my SD card, and then install the files, no?
if it helps you, my device is SM-N9005, and I had 4.3 when I started this whole thing. Cheers!
- Edit.
I tried to download the Nighty build from CyanogenMod's own homepage, but when I try and install it, it says failed, giving me an erro that says "This package is for "hlexx" devices: This is a." That's all it says ... Hmfh. Sooooooooo... Yes! I'm in recovery mode now, but without any rom. :/
Click to expand...
Click to collapse
Yes you can flash any cm based rom.
You can also flash any stock rom such as SweetRom/X-Note/BobCat as most developers still keeping 4.3 rom in their thread.
Thaelern said:
I really do appreciate the help you've given, but I have one final request, and I really do hope it isn't too much to ask. Say I am unable to find the same version of TWRP, I will have to actually flash cyanogenmod onto my device. I don't think it should be too tough now that I've managed to launch into TWRP, because now I should be able to just put the rom on my SD card, and then install the files, no?
if it helps you, my device is SM-N9005, and I had 4.3 when I started this whole thing. Cheers!
- Edit.
I tried to download the Nighty build from CyanogenMod's own homepage, but when I try and install it, it says failed, giving me an erro that says "This package is for "hlexx" devices: This is a." That's all it says ... Hmfh. Sooooooooo... Yes! I'm in recovery mode now, but without any rom. :/
Click to expand...
Click to collapse
Try this link: http://download.cyanogenmod.org/?device=hlte
Sent from my toaster
blackknightavalon said:
Try this link: [
Sent from my toaster
Click to expand...
Click to collapse
Will that work on the international version of the Note 3 ? I'm starting to believe that's the whole culprint of why I can't get it to work. :/
Thaelern said:
Will that work on the international version of the Note 3 ? I'm starting to believe that's the whole culprint of why I can't get it to work. :/
Click to expand...
Click to collapse
Believe so. It's because of updater script i guess as described in the link
http://forum.xda-developers.com/showthread.php?t=2600648&page=2
Try flashing chenglu's 6.0.4.5 recovery.
http://forum.xda-developers.com/showthread.php?t=2454079
Just the same as you did for twrp. I think i read somewhere that changing recovery helped some people.
The worst just download sweetrom/x-note/bobcatrom or any stock 4.3 based rom if you deperately need the phone to boot up
Rosli59564 said:
Believe so. It's because of updater script i guess as described in the link
Try flashing chenglu's 6.0.4.5 recovery.
Just the same as you did for twrp. I think i read somewhere that changing recovery helped some people.
The worst just download sweetrom/x-note/bobcatrom or any stock 4.3 based rom if you deperately need the phone to boot up
Click to expand...
Click to collapse
So after having spent the better half of the night, I actually managed to get my phone to boot into cyanogenmod 11 ! But that joy was shortlived when I came to realize that wi-fi wasn't working, and I couldn't get it to work. I tried to factory reset as I had read would help, but alas it did no good. I figured I should try and run back a stock 4.4.2 rom and just be done with it, but that was when I realized I had lost my root (?!) so that wasn't really a possibility either, next I set out to try and find a way to root my phone now running cyanogenmod 11. I found a file here on XDA called "CF-Auto-Root-hlte-hltexx-smn9005.tar" but whenever I try and flash that onto my phone, my phone just stays stuck saying "trying to enter into recovery mode" and does not really go anywhere from there. I can get back into recovery mode if I flash "n9005-cwm-recovery-6.0.4.5(1116)" onto the phone, like you said, but that still leaves me without root access, which I need to throw a rom onto my device?! Arrrgh, this is getting silly, I just wish I could go back to my backup/ default rom on the device, but I can't.
Thaelern said:
So after having spent the better half of the night, I actually managed to get my phone to boot into cyanogenmod 11 ! But that joy was shortlived when I came to realize that wi-fi wasn't working, and I couldn't get it to work. I tried to factory reset as I had read would help, but alas it did no good. I figured I should try and run back a stock 4.4.2 rom and just be done with it, but that was when I realized I had lost my root (?!) so that wasn't really a possibility either, next I set out to try and find a way to root my phone now running cyanogenmod 11. I found a file here on XDA called "CF-Auto-Root-hlte-hltexx-smn9005.tar" but whenever I try and flash that onto my phone, my phone just stays stuck saying "trying to enter into recovery mode" and does not really go anywhere from there. I can get back into recovery mode if I flash "n9005-cwm-recovery-6.0.4.5(1116)" onto the phone, like you said, but that still leaves me without root access, which I need to throw a rom onto my device?! Arrrgh, this is getting silly, I just wish I could go back to my backup/ default rom on the device, but I can't.
Click to expand...
Click to collapse
About the cf auto root make sure you flash the one for 4.3. I believe you flashed the one for 4.4.2.
Doesn't really matter whether you have root access or not as long as you can boot into custom recovery. Just flash any custom rom. It'll give you root anyway.
Still if you need root just make sure you flash cf auto root then flash twrp or chenglu recovery. Flash the one for 4.3 that's the most important
Rosli59564 said:
About the cf auto root make sure you flash the one for 4.3. I believe you flashed the one for 4.4.2.
Doesn't really matter whether you have root access or not as long as you can boot into custom recovery. Just flash any custom rom. It'll give you root anyway.
Still if you need root just make sure you flash cf auto root then flash twrp or chenglu recovery. Flash the one for 4.3 that's the most important
Click to expand...
Click to collapse
But when I have cyanogenmod 11 installed, is that then not 4.4.2 ? I suppose that's what's giving me trouble... I'll try and see if I can find the cf auto root for 4.3 and return back if I was successful or not. Again, thank you for being so patient..
-Edit
This seems to be the only one I can find; http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
And I've already tried that one 3 times, but every time I flash it, the phone reboots and keeps trying to enter into recovery mode, and is unable to do so before I've flashed n9005-cwm-recovery-6.0.4.5(1116) again
this is what it says;
"recovery booting...
Recovery is not seandroid enforcing
Set warranty bit : Recovery "
Thaelern said:
But when I have cyanogenmod 11 installed, is that then not 4.4.2 ? I suppose that's what's giving me trouble... I'll try and see if I can find the cf auto root for 4.3 and return back if I was successful or not. Again, thank you for being so patient..
-Edit
This seems to be the only one I can find; http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
And I've already tried that one 3 times, but every time I flash it, the phone reboots and keeps trying to enter into recovery mode, and is unable to do so before I've flashed n9005-cwm-recovery-6.0.4.5(1116) again
this is what it says;
"recovery booting...
Recovery is not seandroid enforcing
Set warranty bit : Recovery "
Click to expand...
Click to collapse
You flashed 4.4.2 cm rom but you're on 4.3 booloader. So you need to use cf auto root for 4.3 which is available here
http://forum.xda-developers.com/showthread.php?t=2466423
read third post(download section)
---------- Post added at 09:41 PM ---------- Previous post was at 09:34 PM ----------
Rosli59564 said:
You flashed 4.4.2 cm rom but you're on 4.3 booloader. So you need to use cf auto root for 4.3 which is available here
http://forum.xda-developers.com/showthread.php?t=2466423
read third post(download section)
Click to expand...
Click to collapse
Just enter download mode and reflash twtp. I saw there are 4 different versions for 4.3(2.6.3.0/2 6.3.5/2.6.3.6/2.3.6.7). Flash 1 by 1 and see if it can restore your backup
Rosli59564 said:
You flashed 4.4.2 cm rom but you're on 4.3 booloader. So you need to use cf auto root for 4.3 which is available here
http://forum.xda-developers.com/showthread.php?t=2466423
read third post(download section)
---------- Post added at 09:41 PM ---------- Previous post was at 09:34 PM ----------
Just enter download mode and reflash twtp. I saw there are 4 different versions for 4.3(2.6.3.0/2 6.3.5/2.6.3.6/2.3.6.7). Flash 1 by 1 and see if it can restore your backup
Click to expand...
Click to collapse
You really are a boss with a heart of gold! I used the file you linked me, ran it, and sure enough it installed and gave me root access. Believe it or not, but I am learning from this! The whole thing about bootloader being different from the rom version was new to me. But I am up and running with root access now, so now I hope it shouldn't be too hard to get a stock rom thrown in. I've kinda given up on my backup. I no longer care for the files I had before, now I just want the phone up and running with wifi.. X_ X
- Edit
Or do you have any clue as to what is causing wifi to not work? I really don't mind the rom at all, I quite like it, but where I live wifi is mandatory as it's a lowered area with mountains around me, meaning LTE really isn't viable while at home.
Thaelern said:
You really are a boss with a heart of gold! I used the file you linked me, ran it, and sure enough it installed and gave me root access. Believe it or not, but I am learning from this! The whole thing about bootloader being different from the rom version was new to me. But I am up and running with root access now, so now I hope it shouldn't be too hard to get a stock rom thrown in. I've kinda given up on my backup. I no longer care for the files I had before, now I just want the phone up and running with wifi.. X_ X
- Edit
Or do you have any clue as to what is causing wifi to not work? I really don't mind the rom at all, I quite like it, but where I live wifi is mandatory as it's a lowered area with mountains around me, meaning LTE really isn't viable while at home.
Click to expand...
Click to collapse
Not sure about the wifi problem but yes you're good to go with a new rom. Make sure to choose only for 4.3 bootloader else you will run into problem later
Rosli59564 said:
Not sure about the wifi problem but yes you're good to go with a new rom. Make sure to choose only for 4.3 bootloader else you will run into problem later
Click to expand...
Click to collapse
Could you be so kind and to link me to a rom that works for 4.3 bootloader? I am so paranoid I'll end up picking something for 4.4.2, like I was about to do now. :S
Thaelern said:
Could you be so kind and to link me to a rom that works for 4.3 bootloader? I am so paranoid I'll end up picking something for 4.4.2, like I was about to do now. :S
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2495688
Post 1 choose V6
Or
http://forum.xda-developers.com/showthread.php?t=2472301
Post 3
Or
http://forum.xda-developers.com/showthread.php?t=2498687
Post 1 v3.0
Or
http://forum.xda-developers.com/showthread.php?t=2498687
Post 2 V5
There's a lot more in developement section. Just take a look there. Most developers still providing link for 4.3
Rosli59564 said:
http://forum.xda-developers.com/showthread.php?t=2495688
Post 1 choose V6
Or
http://forum.xda-developers.com/showthread.php?t=2472301
Post 3
Or
http://forum.xda-developers.com/showthread.php?t=2498687
Post 1 v3.0
Or
http://forum.xda-developers.com/showthread.php?t=2498687
Post 2 V5
There's a lot more in developement section. Just take a look there. Most developers still providing link for 4.3
Click to expand...
Click to collapse
Alright.. Time to get things done right! So just being sure I do it alright. I pick this one; http://forum.xda-developers.com/show....php?t=2498687
Download the one for 4.3 bootloader, once download I place the zip folder on my SD card
- Then boot into Recovery mode, wipe phone clean, and then install the rom directly from inside of Recovery mode?

Having an impossible time flashing CM11 rom, been at it for hours please HELP

This used to be easy.
After 8 hours yesterday I think I managed to root the phone. CWM/TWRP will not install. At all, under any method. Rom manager, goo manager, I now get this stupid message that says that "an application attempted to access something unauthorized and has been blocked" over and over.
Just trying to flash CM11 rom. Guess I need to learn how to sideload or something? I physically can't get my phone to recovery mode other than the stock Android, which does not have the "flash zip from sdcard" option.
For the love of god help me. My phone stopped working around 2 pm yesterday and I seriously can't believe I'm about to be going into day 2 of this, so rather than drive myself crazy i'm going to wait for help
bump please help should be simple
Hi,
Please, don't panic! Panic is your worst enemy . First, give a good read here: http://forum.xda-developers.com/showthread.php?t=2419762. Then try again . It's very likely Knox is blocking your TWRP/CWM installation, that's why you receive this message.
All the best,
~Lord
XxLordxX said:
Hi,
Please, don't panic! Panic is your worst enemy . First, give a good read here: http://forum.xda-developers.com/showthread.php?t=2419762. Then try again . It's very likely Knox is blocking your TWRP/CWM installation, that's why you receive this message.
All the best,
~Lord
Click to expand...
Click to collapse
thanks
knox is disabled
root is gained
su is installed
rom manager and goo manager installed
when i downloaded the CM rom from goo manager and try to install it, the phone restarts in download mode and just sits there...
Damani311 said:
thanks
knox is disabled
root is gained
su is installed
rom manager and goo manager installed
when i downloaded the CM rom from goo manager and try to install it, the phone restarts in download mode and just sits there...
Click to expand...
Click to collapse
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord
XxLordxX said:
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord
Click to expand...
Click to collapse
tried flashing four different CWM tars, all are failing.
XxLordxX said:
Hi,
You need to flash the recovery via Odin . After flashing the recovery via Odin you'll be able to flash the ROM normally .
All the best,
~Lord
Click to expand...
Click to collapse
tried flashing four different CWM tars, all are failing.
also trying to flash TWRP
its just all failing on the install
Hi,
Please post your installation issue on the Galaxy S4 Help Thread there might be someone better than me to help you there. Also are you sure you're flashing the right files and using the right method? Did you try another USB Cable? Did you try another Odin version? It all can contribute to the fail.
~Lord
XxLordxX said:
Hi,
Please post your installation issue on the Galaxy S4 Help Thread there might be someone better than me to help you there. Also are you sure you're flashing the right files and using the right method? Did you try another USB Cable? Did you try another Odin version? It all can contribute to the fail.
~Lord
Click to expand...
Click to collapse
its the official samsung cable. and yes i tried others
tried other versions of odin as well
and different versions of both twrp and cwm
its crazy i tells ya xD
If it fails to flash true Odin, then you are doing something wrong.
- Different pc
- Reinstall drivers
- Different cable
- Different usb port
- Make sure kies is not running in the background
What are you running? Windows 8? Try a windows 7 pc.
Post the details of the error you are getting.
Also when the flash goes succesfull, but you still don't have a custom recovery, then uncheck auto-reboot.
can someone please link me to a guaranteed working version of a flashable recovery for odin ?
I know its a lot to ask but I've actually gone through almost that entire list you listed
tried diff cables
no kies runnning
on windows 7
drivers been installed twice
maybe i should try the other port, but in case that doesnt work can anyone just link me? sorry i've just never had this much problems with this, must be b/c of the new security knox update or w/e in oct of last year. Last June I did all this in about 15 minutes....
I had the same trouble with the knox crap yesterday, the only way I could get it rooted and/or with custom recovery was to use the Cyanogen windows installer, then when CM booted I then rebooted into recovery and installed a different rom from there. :good:
dwarfer66 said:
I had the same trouble with the knox crap yesterday, the only way I could get it rooted and/or with custom recovery was to use the Cyanogen windows installer, then when CM booted I then rebooted into recovery and installed a different rom from there. :good:
Click to expand...
Click to collapse
that's crazy
so where do i find this windows installer? i'm just trying to put CM on there so I suppose this would work
Hi i know youve already said said its officail cable but im saying try another different s4 cable. Because when i was installing recovery or anything it wouldnt let me (i thought i had original white s4 cable) but then i got my dads cable (hes gt s4) and it worked instantly. These fake cables are at large and its very very difficult to tell if its original.
Also like previous guy said using a different computer/laptop also helps i know because ive flashed my phones since day 1.
GL and plz let me know if u managed to fix it another way as its always good to try new options when others fail.
189cutter said:
Hi i know youve already said said its officail cable but im saying try another different s4 cable. Because when i was installing recovery or anything it wouldnt let me (i thought i had original white s4 cable) but then i got my dads cable (hes gt s4) and it worked instantly. These fake cables are at large and its very very difficult to tell if its original.
Also like previous guy said using a different computer/laptop also helps i know because ive flashed my phones since day 1.
GL and plz let me know if u managed to fix it another way as its always good to try new options when others fail.
Click to expand...
Click to collapse
alright it'd be awesome if someone can post a link to the files the work, for sure.
CM windows installer
CWM odin tar file
TWRP odin tar file
Damani311 said:
alright it'd be awesome if someone can post a link to the files the work, for sure.
CM windows installer
CWM odin tar file
TWRP odin tar file
Click to expand...
Click to collapse
http://www.cyanogenmod.org/ then click the start button and follow the instructions.
It will get you to download the installer (or http://dist01.slc.cyngn.com/CMInstaller.msi?t=1403660099360) the click it to run, It may download an update for itself, then it will download recovery, operating system, gapps, then start to install everything. About 300mb altogether.
That way you don't need the tar files, just search on this sight for flashable from recovery for the recovery files you want. (I use the touch versions myself).
dwarfer66 said:
http://www.cyanogenmod.org/ then click the start button and follow the instructions.
It will get you to download the installer (or http://dist01.slc.cyngn.com/CMInstaller.msi?t=1403660099360) the click it to run, It may download an update for itself, then it will download recovery, operating system, gapps, then start to install everything. About 300mb altogether.
That way you don't need the tar files, just search on this sight for flashable from recovery for the recovery files you want. (I use the touch versions myself).
Click to expand...
Click to collapse
thanks, but naturally this would be too easy
says: "not supported on your device"
a freaking S4 AT&T! what the ****?
From what I've read AT&T have locked bootloaders. Glad I have an unlocked Australian version!
Yeah so if anyone can still find a way to help me that'd be awesome. Wasted two days already and rather not be stuck with stock
Damani311 said:
Yeah so if anyone can still find a way to help me that'd be awesome. Wasted two days already and rather not be stuck with stock
Click to expand...
Click to collapse
So do you have an AT&T phone? If you do, you are in the wrong section of the forum.

N910F using TWRP (TRLTEXX) shows "Error 7" on all ROM flash attempts

As title says, all attempts to flash a custom ROM result in error 7, I have checked that my version of TWRP is up to date and the ROM is for TRLTEXX. I have also tried removing the 'assert' section in `updater-script`, which caused another error where the `update-binary` file cannot be found. Can anyone help me figure out why this is happening and how to fix it?
MinkShenanigans said:
As title says, all attempts to flash a custom ROM result in error 7, I have checked that my version of TWRP is up to date and the ROM is for TRLTEXX. I have also tried removing the 'assert' section in `updater-script`, which caused another error where the `update-binary` file cannot be found. Can anyone help me figure out why this is happening and how to fix it?
Click to expand...
Click to collapse
First, if you just bought this phone, what I would do is double check the phone is really 910f. What's it say behind battery? Also boot into download mode, what info does that tell you. When you plug into Odin what model does it say. Reason I say this, I've seen others buy what they thought were F but they were really 910p.
If all the info checks out, I would download twrp again just to make sure you got good file. Downloads can mess up rarely.
Let me know what this tells you.
Had the phone for about a year and a half now, battery cover, behind battery, about page, and download mode all say N910F, the same as the version of TWRP is supposedly for, I have flashed both 3.0.1.0 and 3.0.2.0 of TWRP using Odin with the same result, error 7 on all attempts of installing a ROM. The ROM I'm trying to install is the Resurrection Remix ROM for 6.0.1 TRLTEXX, but others have the same error.
MinkShenanigans said:
As title says, all attempts to flash a custom ROM result in error 7, I have checked that my version of TWRP is up to date and the ROM is for TRLTEXX. I have also tried removing the 'assert' section in `updater-script`, which caused another error where the `update-binary` file cannot be found. Can anyone help me figure out why this is happening and how to fix it?
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/note-4/general/efs-fix-invalid-argument-twrp-fix-t3489294
Trex888 said:
Try this
http://forum.xda-developers.com/note-4/general/efs-fix-invalid-argument-twrp-fix-t3489294
Click to expand...
Click to collapse
I'd rather not experiment considering it still boots into touchwiz fine.

Bootloop without reason!! Any solution except Factory Reset?

Hi everyone, I owns a Black, Made in China variant Mi A1, bought it almost 10 months ago so it's in brand new condition.
A night I was using it as regular, watching YouTube, It suddenly restarted automatically, and stuck on 'Android One' boot animation.
I wasn't doing any heavy or intensive task, was not having any issue except storage full. The device is on official stock rom and on June security patch with Android 8.1.
I've tried >?1. Apply update from ADB in recovery mode with June update, which gave me -> E: footer is wrong. E: signature verification failed. Installation aborted
>?2. Apply update from SD card with the same update as above, which gave me -> Couldn't mount SD card
Bootloader is locked, USB debugging is off, no custom recovery installed.
Is there any way to make it work again without erasing user data? I'm familiar with all kinds of Command Line Interface and with almost every tech term. Any help would be appreciated.?
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
ROGGGER3G said:
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
Click to expand...
Click to collapse
Hi,
i have also experienced the same issue recently and struggling hard to make it working again.
I have tried with MI flash but u need to have a bootloader unlocked as well. If not, flashing will not start.
Shashankjindal said:
Hi everyone, I owns a Black, Made in China variant Mi A1, bought it almost 10 months ago so it's in brand new condition.
A night I was using it as regular, watching YouTube, It suddenly restarted automatically, and stuck on 'Android One' boot animation.
I wasn't doing any heavy or intensive task, was not having any issue except storage full. The device is on official stock rom and on June security patch with Android 8.1.
I've tried >1. Apply update from ADB in recovery mode with June update, which gave me -> E: footer is wrong. E: signature verification failed. Installation aborted
>2. Apply update from SD card with the same update as above, which gave me -> Couldn't mount SD card
Bootloader is locked, USB debugging is off, no custom recovery installed.
Is there any way to make it work again without erasing user data? I'm familiar with all kinds of Command Line Interface and with almost every tech term. Any help would be appreciated.
Click to expand...
Click to collapse
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
ROGGGER3G said:
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
Click to expand...
Click to collapse
Does it work in locked bootloader? Btw thanks for the reply.
sipollo said:
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
Click to expand...
Click to collapse
Can you describe what in the data partition caused this? Because I've been using this device with 90% storage filled for months??*.
And I've factory reset the device as there was no other ways to make it work again but still I want to know what was the cause of the problem.
Shashankjindal said:
Can you describe what in the data partition caused this? Because I've been using this device with 90% storage filled for months??*.
And I've factory reset the device as there was no other ways to make it work again but still I want to know what was the cause of the problem.
Click to expand...
Click to collapse
When memory is almost full R/W errors can occur.
Maybe 90% you see is not including temporary-swap files, so that you are dangerously close to 100% storage filled.
sipollo said:
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
Click to expand...
Click to collapse
sipollo said:
When memory is almost full R/W errors can occur.
Maybe 90% you see is not including temporary-swap files, so that you are dangerously close to 100% storage filled.
Click to expand...
Click to collapse
Thank you for your answer & time, I'll be carefull in the future.
ROGGGER3G said:
I think only Miflash, with first nougat rom works for you. Save user data. Works for me, after I tried Lineage OS.
Click to expand...
Click to collapse
I have just softbricked my Mi A1 and need to flash the official rom with MiFlash, problem is that I can't find the right file to flash. Any tips to where I can download the official firmware? I'm looking for the zipped version, not an image. MiFlash can't read the images I've downloaded so far.
FantLarve said:
I have just softbricked my Mi A1 and need to flash the official rom with MiFlash, problem is that I can't find the right file to flash. Any tips to where I can download the official firmware? I'm looking for the zipped version, not an image. MiFlash can't read the images I've downloaded so far.
Click to expand...
Click to collapse
Here are some of the links where you can find the official rom in .zip format. Check if they are compatible with MiFlash tool-
https://firmwarefile.com/xiaomi-mi-a1
https://dhananjaytech.com/flash-stock-rom-mi-a1-through-twrp/
Here is the XDA thread- https://forum.xda-developers.com/mi-a1/development/rom-tissot-stock-oreo-8-0-rooted-t3735760.
I'll be happy if this was helpful.
Shashankjindal said:
Here are some of the links where you can find the official rom in .zip format. Check if they are compatible with MiFlash tool-
https://firmwarefile.com/xiaomi-mi-a1
https://dhananjaytech.com/flash-stock-rom-mi-a1-through-twrp/
Here is the XDA thread- https://forum.xda-developers.com/mi-a1/development/rom-tissot-stock-oreo-8-0-rooted-t3735760.
I'll be happy if this was helpful.
Click to expand...
Click to collapse
Great stuff thanks.
sipollo said:
Without reason? Probably THIS is the reason. I think your problem is related to data partition and a flash with Miflash can't help you. Only a factory reset can solve this.
Click to expand...
Click to collapse
There was another thread where someone proceeded to soft brick his device after downloading a file despite having low available storage.
barrack1 said:
There was another thread where someone proceeded to soft brick his device after downloading a file despite having low available storage.
Click to expand...
Click to collapse
Thank you for the help, there seems just no way to save user data, factory reset is the only option.
Shashankjindal said:
Does it work in locked bootloader? Btw thanks for the reply.
Click to expand...
Click to collapse
works

Categories

Resources