Error 07 when aplaying any ROM - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

I'm trying to apply Nougat 7.1 ROM to my Galaxy tab 10.1. every time i try i get error 07 and the install aborts, and it's not only that ROM, every ROM I've tried it's the same.
the only ROM that have taken was cm-10-20121030-EXPERIMENTAL-p4wifi.zip, from galaxyhacks.com but after trying aosp-6.0-p4wifi-20160806.zip, that wont take any more. Please help.
Don't bother I got myself, wrong twrp ups.

Update your Recovery to the lasted TWRP from decatf.

Related

[Q] Issue with installing custom Rom on GT-P7510

I have read all the instruction i can find on installing a custom ROM on Galaxy Tab 10.1 wifi, and once i get to the point of installing zip with ROM it fails. I dont know why its failing, and i think i am missing something. I have TWRP recovery installed and was trying to update with CM 10.1 or 11 but neither would work.
If someone could eith provide a detailed list of steps, i can see if i missed something or maybe someone else has encountered this problem and can advise. When i install from zip it tried so install and then an few seconds later is says failed and then i have to restore using NANDROID backup to have atleast a working tablet
Thanks for the help
Maybe you have an old version of TWRP. For cm11 you need version 2.6.3 or later.
imagn said:
I have read all the instruction i can find on installing a custom ROM on Galaxy Tab 10.1 wifi, and once i get to the point of installing zip with ROM it fails. I dont know why its failing, and i think i am missing something. I have TWRP recovery installed and was trying to update with CM 10.1 or 11 but neither would work.
If someone could eith provide a detailed list of steps, i can see if i missed something or maybe someone else has encountered this problem and can advise. When i install from zip it tried so install and then an few seconds later is says failed and then i have to restore using NANDROID backup to have atleast a working tablet
Thanks for the help
Click to expand...
Click to collapse
Try updating your twrp to a newer version for your tab. If that falis you could try using cwm. I've used it to install my roms including cm11 and other kitkat roms that supposedly require twrp without any errors.

Bricked Samsung Galaxy S3 GT-i9300 TRIED EVERYTHING, BUT CANNOT UNBRICK. pls help :s

So I recently got my hands on an international Samsung Galaxy S3. The device is bricked. I've already had a lot of experience with unbricking this device and I've always done it succesfully. However this time everything fails.
The situation: Currently running Clockworkmod Recovery 6.0.4.6, which is (more or less) the latest for this device. I've got an 8 GB micro SD-card, so flashing custom roms should work just fine. Unfortunately though, this is not the case. I've tried several roms already: cyanogenmod 10, 11, 12, 13, Blisspop, Blekota, Revolutionary android HD, S5-rom, Archidroid, Archiport, ParanoidAndroid... and they all fail to be flashed correctly through CWM. Some of them come with the Aroma-installer. The wizard launches succesfully and I've managed to install Archiport and Blekota with it. At the end of the wizard I get the prompt that the rom installed correctly. But when I reboot the device afterwards... still bricked!
I've also tried to install roms via Odin (3.07, 3.09, 3.10 .... ) but none of them installed right. Odin says "NAND Write start...." and then "FAIL!" Everytime, or Odin just crashes.
The only clue I can think of is Clockworkmod that's causing all these conflicts... I've had more succes in the past by using TWRP or PhilzTouch. So I tried to flash these other recoveries via Odin, which fails every time with every version of the recovery. I also tried to flash it using CWM. Here I get the message that the zip installed correctly, but when I reboot into recovey again I'm still running CWM.
Like I said, I've tried EVERYTHING. It's very unusual that NOTHING works.
Am I missing something?
Thanks
Brick in what sense????
Below is URL for your device please do a search before making/creating new thread, Requested to search before making any thread
Samsung S3 - http://forum.xda-developers.com/galaxy-s3
and for Troubleshooting http://forum.xda-developers.com/galaxy-s3/help
Still having problem please leave a post

Coming from Oreo, cant install Nougat

Hey gentlemen,
so the case is. I was on Epic Rom (MIUI 10) and installed Cardinal-AOSP yesterday. I personally didnt liked it.
- Now i cant install Miui 9, 9.5 or 10 only Android 8 based system.
- Even tried installing one of my backups, but no luck here.
- Tried Masik, restart after 30-60 seconds of loading again.
- Flashed lazy-flasher also
My device has TWRP Exclusive 3.2.1-(5/7). What can cause the problems? Hope you can help me out with a solution.
Update: Managed to get Epic rom 8.7.6 almost working, now it says my data is encrypted and i have to reset the phone, and than boots into twrp.
maybe, just maybe ok? you have treble version of oreo rom. and you have to un-treble to use non-treble rom. just try it maybe can help you
Get this rom: https://sourceforge.net/projects/orangefox/files/mido/ (credits to this site:https://forum.xda-developers.com/re.../recovery-orangefox-recovery-project-t3775933) Download the R7 zip flash it and try again.
OKAY, after a day I got út Sáta was corrupted, and was in f2fs state. Had to change it to exFAT4 and then I could install EpicEom by Escobar, wiped everything then installed again. Works like a charm.
All done on TWRP-Exclusive.

Did I do everything wrong reinstalling Lineage ROM? Is it possible to save this phone?

Hello everyone,
I have made some mistakes:
I installed lineage os yesterday, everything worked well, installed some apps, and installed an app (banking app I didn't trusted), so I decided to make a reboot.
I probably didn't made a "clean" reboot. I just went into TWRP and wiped all folders, thinking to then install the OS again.
Thing is, when installing Lineage now I only get "error 7" and changing the Assert line in the zip, changes nothing. I tried to flash another ROM, "Light Rom" on the phone successfully, but it didn't started anymore and went into reboot loop.
I'm now a bit lost, since it was the first flash I did (hich was successfull the first time but I probably screwed up the second time.
Before every Flash, I always clean the Dalvik, Cache, Data and System folder.
I hace the latest TWRP Version, and also made sure to download the latest Lineage version.
What can I do now?
I'm flashing with Odin
When Trying to flash the normal Samsung firmware, I get the error msg:
SW Rev. Check Fail (Bootoader) Device: 12 Binary: 7
I also have no recovery. I know, I have probably done everything wrong I coould do wrong XD, this is going to be a lesson having no backup...
Can I even do something with the phone tho? Or is it just dead now and unusable?
Deleted member 11382503 said:
Hello everyone,
I have made some mistakes:
I installed lineage os yesterday, everything worked well, installed some apps, and installed an app (banking app I didn't trusted), so I decided to make a reboot.
I probably didn't made a "clean" reboot. I just went into TWRP and wiped all folders, thinking to then install the OS again.
Thing is, when installing Lineage now I only get "error 7" and changing the Assert line in the zip, changes nothing. I tried to flash another ROM, "Light Rom" on the phone successfully, but it didn't started anymore and went into reboot loop.
I'm now a bit lost, since it was the first flash I did (hich was successfull the first time but I probably screwed up the second time.
Before every Flash, I always clean the Dalvik, Cache, Data and System folder.
I hace the latest TWRP Version, and also made sure to download the latest Lineage version.
What can I do now?
I'm flashing with Odin
When Trying to flash the normal Samsung firmware, I get the error msg:
SW Rev. Check Fail (Bootoader) Device: 12 Binary: 7
I also have no recovery. I know, I have probably done everything wrong I coould do wrong XD, this is going to be a lesson having no backup...
Can I even do something with the phone tho? Or is it just dead now and unusable?
Click to expand...
Click to collapse
You get the 'SW Rev. Check Fail (Bootoader) Device: 12 Binary: 7' thing because you're trying to flash a older firmware, you can't downgrade.
Use samfirm or frija to download the latest stock rom of your csc.
And you got error 7 because u are using twrp 3.4 or 3.5, read first, flash after. Rom devs recommend twrp 3.3.1.0/.1

Bricked Galaxy A5 and stuck on recovery.

Hello. I have a Samsung Galaxy A5 from 2015. I was trying to install android 9 on it. But when i wanted to flash the lineage zip file, i've got a error. Updater process ended with ERROR: 7.
The same happens with gapps but with error 1. I can't use Magisk and other programs because the logo is bootlooping. And i can't turn on the phone( only recovery) i wanted to get the android 9 or 11. Now idk what to do with this phone. Thx for answers
To get rid off of all the modifications you made re-flash phone's Stock ROM.

Categories

Resources