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
Related
Hello,
I searched in many threads as I could and although I learned that mediatek phones were virtually "unbrikable", I'm afraid it keeps getting worse and won't do more without your expertise.
So a few days ago I was wiping my phone to install another rom and besides wiping data and cache, I also made the huge mistake of wiping SYSTEM... My phone now just boots into recovery and nothing else.
I have an Efox Smart e4, equals to no.1 s6 and hdc galaxy s4 according to other posts here. MTK 6589, 1gb internal, 1,84gb internal sd.
The first custom rom that i installed was Essefour no.1 s6 by iceman and also the touch recovery. The rom performed great but I wanted to solve the issue that the phone kept switching between sd external and internal randomly. Also, I wanted to merge the internal memory with the internal sd so I was gonna try another rom. With this problem, was even trying the stock rom but to no avail.
When I try to install the Smart e4 factory rom for cwm and I get status 7.
E:Resource type (image) failed to load
Installing /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
Checking for MD5 file
Skipping MD5 check: no MD5 file found.
... Writing boot...
assert failed: write_raw_image("/tmp/boot.img", "boot")
Error in /sdcard/SMART-E4_V1.0_V01_2013-10-29_CWM.zip
(Status 7)
Click to expand...
Click to collapse
Other roms it just fails.
Right now, my computer windows 8.1 x64 can't identify correctly my phone, only access the sd. So can't do any adb push. In download mode it identifies as lenovo composite interface?? and cdc serial, the last I can't install. In other modes, I get gt-9500 but with the yellow triangle.
I would really really appreciate any help, thanks!
Might try to just edit the updater-script and remove the asserts.
Reference this for more info: http://forum.xda-developers.com/showthread.php?t=2522762
But I think your issue is that since you wiped the system, there's no /tmp folder to store the boot.img. However, if the last rom and this rom can use the same kernel (boot.img) then removing the assert for the boot.img install might do it since wiping the system does not affect the kernel.
What happened to the other rom you know is working somewhat? Can you just reflash that?
Otherwise, you'll just have to find the official way to flash with the scatter file and all that.
I searched for that updater and there are no lines for assert on the stock rom. Also inside the main zip, there are zips for system, boot, recovery and logo...
I'm trying to install the stock rom to play it safe since it was the same that came with the phone. The previous rom I talked about, I deleted it and now the phone isn't recognized on the computer..
Since I don't know if they have the same kernels, is it safe to try and reinstall the custom rom?
As of using scatter and such, maybe I need other pc to get the drivers running again.
Will let you know
I got it!!
The zip from the stock rom wouldn't let me install the kernel (boot). Managed to install only the rom, and as you said the kernel wasn't the same.
Eventually I reinstalled the custom rom and afterwards flashed a completely different rom via spflash tools since it connected successfully to my computer this time.
As I'm already restoring apps and data, I think everything is working properly.
Once more, thank you very much
I have an MDK S4 and have been flashing custom roms all along.
It had been like a whole week since my last flash so I downloaded Chaos rom and wiped my data and went to install it just like I've done 100 times before with other roms. When I swipped on install it came up with a red "Failed" message. I thought this was odd, but I've had it happen before with corrupt/incomplete/errored downloads.
Since I had already wiped I went to go do a fresh install of the basic NG2 rom I was on prior to wiping and got another "Failed" message.
Flashed my recovery image (which thankfully worked.) I repeated the whole wiping/attempting to flash/restoring my recovery image cycle again hoping it would work the second time around... which it left me back on my recovery image.
Not sure what went wrong. Tried to update TWRP to a newer version through goo manager, but that doesn't seem to be working either.
Thoughts?
Worked perfectly. Thanks!
I unlocked the bootloader and rooted the phone, and flashed with resurrected remixed 8.1
Everything seemed good, but trying to install gapps would fail. Everytime I try to flash something it fails, gapps worked once but did not install play services.
I've never had some many problems, the phone does not have a sdcard. ROM manager is installed, and connected to wifi, but it cannot update, does not say why. I tried to get TWRP to work, now it says the phone is not rooted.
I flash SuperSU-v2.82-201705271822, it says success but there is no super user. SU when I run it says it is occupied.
Tried to wip cache etc, and flash stock or lineage, error 7. Tried to remove assert in the update script, than gives a error about footer.
I know I must be missing something. RR Oreo 8.1, no web browser, going to download and move via usb and install. Any suggestions are welcome.
i feel like breaking down at this Point
so where do i start i unlocked the bootloader and then downloaded the unofficial twrp, the rom i wanted to use didn't install because it was made for the official twrp got error 7 so i reflashed the official twrp to install it again but was unable to move any files and adb sideload failed something about using an old version this after it was stuck in starting sideloading feature (it failed when i tried to use commands) (even tried the sdk didn't work) so i wen't back to the unofficial twrp to install lineage apperantly this was an invalid format, so i wen't back to the official one again to try the first rom adb didn't work so i wen't back to the unofficial one, the one that did work was this one (i've reflashed recoveries over 6 times now including formatted in every conceivable way several times did i break it?
https://forum.xda-developers.com/mate-10/development/roms-openkirin-aosp-collection-t3828792
it installed completely fine
then i wen't to gapps
"insufficient space" even though it's pico and the phone is empty
then i tried to reboot i got the warning that no os is installed so i rebooted again reflashed the rom Everything wen't fine still no os installed warning this time i rebotted to system and just got a bootloop eventually emui offered to factory reset
so here i am now i can't flash any kind of rom and the more i try things the more i seem to break.
lineage unsupported format
aosp 9.0 error 7 (removing asset just made a new error about not finding update binary even though it's there
kirin treble installs fine but no os installed warning and bootloop
i used the dcunlocker Method so installing stock recovery or stock emui seems risky to me as it might relock the bootloader.
i am also unable to format either getting error 1 or 255 "can't format to remove encryption" and it still bootloops despite the rom installing fine
edit it finally worked to flash aosp 9.0 but then it got stuck on the Android setup screen looking for an update forever so i tried to enter twrp which ofcourse doesn't work on custom roms so i reflashed the official twrp which does work but now i can't put any files on the phone so i am trapped, sideloading does not work i just get an error that i use an outdated adb and on my pc the error says protocol fault protocol fault (no status)
so i can't put any files in it i can't do anything what i can do is reflash the custom twrp and get file transfer back but as soon as i flash Android pie again suddenly that twrp will no longer work so i am stuck completely
it's just not possible to fix this it's impossible no matter what i try it keeps giving all kinds of various errors i can't take it any more
Somehow I feel like a noob. I wanted to see what the new stock Android 10 was like, so I installed it via Odin. But now I can't get back to a custom ROM because TWRP fails to flash. The tablet's bootloader is still unlocked and I've enabled Dev mode. Download the latest twrp-3.4.0-3-gts4lvwifi.img.tar and put it in AP. When I click start, I get this error "Can't open the specified file (Line 1892)"
edit: Still don't know what I did wrong the first time, but I started over from scratch, flashed stock 10 again, vbmeta, twrp and it worked. Of course I let it boot and set Dev mode between each flash. Once into TWRP, formated data, wiped and install cDroid and gapps and it is now working.
lewmur said:
Download the latest twrp-3.4.0-3-gts4lvwifi.img.tar and put it in AP.
Click to expand...
Click to collapse
Glad you got it working. Figured I'd mention though there is a newer TWRP. 3.4.0-4 didn't give me any issues.
lewmur said:
Somehow I feel like a noob. I wanted to see what the new stock Android 10 was like, so I installed it via Odin. But now I can't get back to a custom ROM because TWRP fails to flash. The tablet's bootloader is still unlocked and I've enabled Dev mode. Download the latest twrp-3.4.0-3-gts4lvwifi.img.tar and put it in AP. When I click start, I get this error "Can't open the specified file (Line 1892)"
edit: Still don't know what I did wrong the first time, but I started over from scratch, flashed stock 10 again, vbmeta, twrp and it worked. Of course I let it boot and set Dev mode between each flash. Once into TWRP, formated data, wiped and install cDroid and gapps and it is now working.
Click to expand...
Click to collapse
Stock a10 sucked?