So i have come across a strange problem.
I was using AEX 6.6 on my z2 for almost 15 days now and wanted to switch to AOSIP , so i boot in twrp try flashing and get ERROR 7 (very strange , because i had flashed that before) , so i try to revert back to AEX and still get ERROR 7 (it says failed to flash system img or something like that), ended up QFILing ZUI 2.5.
After booting that up the IMEI was missing and sim card was not detected (thought maybe that was the reason for ERROR7 , but turns out it wasn't) ,so i look around threads and finally fix it .
Now IMEI is back and sim cards working as expected , so i flash TWRP and still end up with ERROR 7 , so QPST again ,this time ZUI 3.5 , repeatedthe same process again and still ERROR 7.
Tried downloading zui again and trying everything again , still ERROR 7 .
Tried old TWRPs and Nougat and still the same thing .
I am not sure what's causing it because ZUI is working totally fine.
Tried experimenting with several roms , v2f and f2v , still the same .
Tried flashing zui 1.9 , all the way to zui 3.5.
Tried unlocking bootloader on all zui versions and trying flashing Roms.
Still the same Error 7 .
Anyone has any idea what the hell is wrong with my device ?
I don't understand how zui works totally fine ,if it is somehow a hardware problem .
BTW i have taken my device apart several times , but i don't think that's the cause .
All help would be really appreciated
Most probably vender to factory or vice versa error. It happens when you flash different treble/non treble custom roms. I see you tried most of the stuff butt I was stuck having exactly same error for a week and through hit and trial i somehow fixed it, happened a while back almost a year ago.
Use all in one tool on pc, go to edl mode format everything. EVERYTHING! don't relock, instead reflash twrp by Kuber it's hosted on android file host than reboot and set up twrp settings and reboot again format cache and data etc (since there is no os) it should have no problems. If there are no errors. You are good to go.
Related
I started with unlocking bootloader using minimal ABD and fastboot. Once done my device went into bootloop.Then I download the stock frimware from sony's software called xperifirm which said that it is 15.5.A.1.5 but was 15.5.A.0.18.And wanted me to update using my laptop. tried doing that to but every time a error 12 came up.then i found someone's thread with .ftf file for 15.5.A.1.5 that to generic_IN. flashed it and then booted into it,got network working.then updated to CM13 and still it says sim card not detected.then flashed the same ftf file checked for software update and this is what i got:
Settings>about phone>bulid number:15.5.A.1.5
Update center>system::15.5.A.1.5 Ready to download 104.4MB
still downloaded it and tried to install.but,while installition when phone goes into recvery mode the screen stared blinking and the installition failed .then flashed cwm recovery and tried again but this is what comes up:
CWM-based Recovery v6.0.4.9
E:invalid command argument
Finding update package. . .
Opening update package. . .
Verifying update package. . .
E:footer is wrong
E:signature verification failed
Install Untrusted Package?
THIS CAN NOT BE UNDONE
- Yes - Install untrusted zip
E:Can't open /cache/recovery/fota/update_package(bad)
Installation aborted.
Rebooting. . .
Note:bold text is recovery log
pls someone help me out I want cm 13 with network working (only one sim working is ok for me but two will be better)
just the same problem
Hi,
I came here looking for a solution to this same problem. I have a C2004, and I have to admit I didn't really know what I was doing, but at this point I'm sure I've followed the right steps at least once. I only followed the official wiki.
I
- unlocked the bootloader
- flashed CM13
- booted, no GApps
- installed GApps (phone unusable due to popups)
- Re-flashed CM13 and GApps before first boot, phone works beautifully but I did all my tests without the SIM, when I rebooted to insert the SIM I noticed the phone was not detecting it. Eventually I found a post detailing what the problem was: CM13 required a previous Android 4.3, but my phone was on an older version.
So I downloaded the radio firmware and the image of the stock Sony OS on 4.3:
- wiped all data
- flashed radio firmware
- restored OS backup with CWM
- booted: SIM card is detected, no idea whether dual sim works because I'm not interested on it, GPS doesn't work
- wiped all data
- flashed CM13 again, still no network.
I repeated the above process several times, always get a working stock OS (except for GPS) but never got CM13 to connect to the mobile network. So, right now I'm stuck on that Sony OS, because it even detects an OS upgrade but can't install it because CWM doesn't know how to handle the upgrade package.
I'd like to know if it is possible to get a copy of the original recovery partition, so that official upgrade can be installed.
Or, better, to get CM13 working, somehow it seems my issue is not common because everything I find on the web points to the same above steps...
After installing CM13 , Did u flash the dual sim patch?
Steps :
First install a custom recovery,
then wipe/format everything
install cm13,dual sim patch and gapps(if u need) in one go because after that your recovery will be replaced by the cyanogenmod recovery and you will have to reinstall another recovery.
I don't know where, but I read that was not needed anymore, and that idea was fixed in my head. Maybe I mixed comments about the dual patch with comments about the radio patch, I can't recall at this point.
Anyway, patching that additional zip fixed the network access for me. Let's just see if its get fixed for the OP as well
Thanks!
You need to flash a patch for enabling dual sim, without it you will get no network ... This is because the official cyanogenmod gives no support for the xperia m dual and so an extra patch has to be flashed before you can really access the sim card's network! hope this helps ! so go on flash the cm13 and then the patch and share the results!!
Hello guys,
I managed again to brick my phone.
I flashed Fulmics as I wanted to swap from those not fully stable nougat roms. Well, I have no idea what caused my problem - Fulmics run without prolbems for a 2 or 3 days including xposed etc.
Then today I changed my ChromePie options and that's when the reboots began. I don't know if this the real cause was though.
So I tried to flash another rom but always got random reboot even in recovery after few minutes/seconds. So I went all the way back to stock rom (4.4.2) with LG Flash tool - which worked after a few tries. Then I installed MM rom via .kdz file and flash tool 2014, which also worked after a few more tries. But then the reboots started again. Can't say if the 4.4.2 rom was without boots because I updated to 6.0 quite quickly.
The strange thing is that after some reboots phone won't boot again and I have to take and leave out the battery for some time to boot the phone again.
Any solutions for my problems?
Best regards
..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.
Gerhard.M said:
..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.
Click to expand...
Click to collapse
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.
Hi, got the same problem with my G3
wi fi and bluetooth didn't work and phone loop rebooted
Here below the steps I followed to solve
1) First attempt (didn't solve): had cloudy rom, got back to stock official but still rebooting, tried fulmics and other rom but problem persisted.
2) second attempt (didn't solve): went back to stock and changed battery (found somewhere in internet), now I have a brand new battery but a phone still loop rebooting
3) third attempt (SOLVED): found that the wi-fi / bluetooth chip (one for both) copuld have unwelded and solved so (it appears I can't post outside link, delete spaces to have the correct link):
youtube .com / watch?v=1zWpzYh2DPI&t=15s"
youtube .com/ watch?v=6_0jzp65eLY&t=256s
Now i'm on fulmics and no more loop reboot
Hope you can solve
[sorry for my english]
frosty234 said:
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.
Click to expand...
Click to collapse
http://stockroms.net/file/LGG3/D855/European/BIN_LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G-0.zip
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/D855/
used flashtool
have to say restoring and/or flashing isn't always that stable. I've experienced it sometimes needs a 2nd try.
Hopefully it isn't a hardware issue in your case.
So I tried all of oyur suggestions but nothing seems to work.
On the contrary I ended up in a status where I can't even flash a new firmware.
In LG Flash Tool 1.8.1 I get the error
"Donwload Fail!!!"
PID: NULL
IMEI: NULL
MODEL:
DLL: D855
BIN: LGD855AT.....
SWV:
SWOV:
Model Information Check Fail!
000000000
Click to expand...
Click to collapse
In LG Flash Tool 2014 (flashing MM with kdz file) phone shuts down in middle of process.
But I can still access Download Mode.
No more ideas?
I really think I finally broke my phone... But the fact that I can still access download mode keeps my hopes up.
So, after 2 months I just tried to reawaken my phone. Still the exact same problem. It just keeps shutting down aber some while, but just when I start flashing something. If it stays connected to computer whitout doing anything it can stay on for like ever.
Can anyone confirm that this could be a hardware defect?
(TL;DR available)
I have a Zenfone 2 (Z00A) and I used to have LineageOS (Android N 7.1) installed, however after some time I noticed the SIM Card wasn't getting detected anymore. At first I tought it was Lineage, so I updated it to the latest experimental, still, nothing. Then I decided to test the SIM in another phone with the same version of Lineage, with my old Zenfone 5, and the SIM still worked. So I reset my Zenfone 2 back to stock ROM, stock Bootloader, stock everything, and the SIM worked. Still thinking it was Lineage, I installed Ressurection Remix, which also requires the MM Bootloader, and the SIM didn't work once again.
*** TL;DR ***
I believe the MM Bootloader is causing the phone to not read the SIM card. It only happens with this provider, since other providers' cards are still recognized. It's very weird. Any help is fairly appreciated.
(This is my first thread and english is not my primary language so sorry for any mistakes.)
1) Which stock ROM does it work with , surely its MM bootloader ?
2) Which TWRP did you have installed.
3) Depending on Which TWRP you do have and what stock ROM (answers from 1&2 above) , you back up stock rom which works , back up in TWRP and simply restore it, a two minute job .
Depending on all answers above...
Try slim7 ROM till linos is fixed . RR is based on linos.
Latest linos does take approx 5 mins to register sim after reboot, don't touch device , leave screen / display setting to half hour and watch it connect without touching the phone.
This question should be answered in thread of ROM development you had trouble with , reading related threads is also wise .
https://forum.xda-developers.com/showpost.php?p=71270877&postcount=25
timbernot said:
1) Which stock ROM does it work with , surely its MM bootloader ?
2) Which TWRP did you have installed.
3) Depending on Which TWRP you do have and what stock ROM (answers from 1&2 above) , you back up stock rom which works , back up in TWRP and simply restore it, a two minute job .
Depending on all answers above...
Try slim7 ROM till linos is fixed . RR is based on linos.
Latest linos does take approx 5 mins to register sim after reboot, don't touch device , leave screen / display setting to half hour and watch it connect without touching the phone.
This question should be answered in thread of ROM development you had trouble with , reading related threads is also wise .
https://forum.xda-developers.com/showpost.php?p=71270877&postcount=25
Click to expand...
Click to collapse
1) I am currently running SuperZen which is based on Android L, works fine.
2) 3.0.2 and I tried with older 2.x.x versions too, no success.
3) Can you specify a little more? A bit confused with what you mean.
I will try LineageOS once again, and shall also try Slim7.
I posted this here since I didn't, and still don't, beleive this has to do with the ROM, but with the Bootloader itself.
I read a lot of threads, including the one you sent me, tried everything without success.
Thank you for now!
kronkraken said:
1) I am currently running SuperZen which is based on Android L, works fine.
2) 3.0.2 and I tried with older 2.x.x versions too, no success.
3) Can you specify a little more? A bit confused with what you mean.
I will try LineageOS once again, and shall also try Slim7.
I posted this here since I didn't, and still don't, beleive this has to do with the ROM, but with the Bootloader itself.
I read a lot of threads, including the one you sent me, tried everything without success.
Thank you for now!
Click to expand...
Click to collapse
Backed up, completely wiped, installed MM Bootloader and flashed Slim7. No SIM. Set Sleep Timer to 30 minutes, rebooted, unlocked screen and left the phone for 10 minutes. No SIM. Did it again but this time didn't even unlock the phone, no SIM. Completely wiped and flashed LineageOS, same process, no SIM. Even went further and tried CM13 (Android M), same process and still no SIM. At this point I am 99.9% sure it is the MM Bootloader that is causing the issue, because as soon as I fallback to the L Bootloader and flash any L ROM, like Stock ASUS or Super ZEN the SIM works fine.
Try stock M , there's been about 6 stock updates in stock M
timbernot said:
Try stock M , there's been about 6 stock updates in stock M
Click to expand...
Click to collapse
Not sure where I can find Stock M, but I found an update on ASUS' Website, Firmware version UL-4.21.40.144 that is Brazil specific, wonder if it has something to do with the SIM not working.
kronkraken said:
Not sure where I can find Stock M, but I found an update on ASUS' Website, Firmware version UL-4.21.40.144 that is Brazil specific, wonder if it has something to do with the SIM not working.
Click to expand...
Click to collapse
are you from Brazil ?
It shouldn't by rights , yes there was probs with Brazilians receiving signal but jrior dev , incorporated those fixes for Brazilians into CM which should be carried through lineageOS.
I don't have anytime right now but will help you update.
Watch you don't brick doing anything daft.
:crying::crying:
timbernot said:
are you from Brazil ?
It shouldn't by rights , yes there was probs with Brazilians receiving signal but jrior dev , incorporated those fixes for Brazilians into CM which should be carried through lineageOS.
I don't have anytime right now but will help you update.
Watch you don't brick doing anything daft.
:crying::crying:
Click to expand...
Click to collapse
Okay, for now I will just restore my backup! Thanks!
kronkraken said:
Okay, for now I will just restore my backup! Thanks!
Click to expand...
Click to collapse
I was able to get the Official MM Bootloader installed, and SIM works fine. Not being able to install any MM-based ROMs tho, they all give Error 7: "This package supports Ifwi Versions: %2; 0094.0183;this device has Ifwi version ."
hi all, please help. My zuk z2 plus keep restarting.
When I start it, it just open up the wallpaper and then restarting again and again.
The memory's just fine, still 25GB.
One weird thing is it shows 1/1/1970 for the date.
Is it some kind of bugs or virus?
What should I do? Anybody knows how to solve it?
Thanks in advance
You should try to restore the device back to its original firmware to make it run on factory default software.
Use QPST/QFIL method to flash your stock ROM. In case of Indian/Global Eng, then i guess the Zui 2.0 or 2.5
Refer to this thread for details https://forum.xda-developers.com/lenovo-zuk-z2/how-to/guide-lock-bootloader-avail-warranty-t3694883
Make sure to charge the device and your laptop battery fully before proceeding to QPST/QFIL flashing. Device or PC must not lose power or reboot while running the flashing process.
(Warning, QPST method will relock your bootloader while restoring factory default)
Once you are on your stock ROM, check if everything working fine or not. In case things are still not working, there is a high chance that you may be having some hardware issue.
Friend If your phone has already been installed zui 2.5 indiana (then installed the customs roms) Do not need to upgrade (install the Chinese 3.5 by qpst). The basebands do not come out of 1.70x only have one that is different that is 1.76 (mine is zuk z2 + (131) in it I put the zui 2.5 indiana and then went to the customs roms and now I went to the roms with kernel 4.4 without installing zui 3.5
Hey guys I recently flashed stock ZUI 3.5 to get to the new baseband. Then I flashed AEX 6.2 and was using a root explorer to chance the U-touch options. After making some changes and rebooting the "fpc1020tp.kl" file, was not there in the folder anymore. I tried clean flashing again but the problem still persisted for some reason, tried multiple roms, still doesn't show up. Please help.
Even after flashing with QFIL and back to AEX the files still cannot be seen.
wantei said:
Hey guys I recently flashed stock ZUI 3.5 to get to the new baseband. Then I flashed AEX 6.2 and was using a root explorer to chance the U-touch options. After making some changes and rebooting the "fpc1020tp.kl" file, was not there in the folder anymore. I tried clean flashing again but the problem still persisted for some reason, tried multiple roms, still doesn't show up. Please help.
Even after flashing with QFIL and back to AEX the files still cannot be seen.
Click to expand...
Click to collapse
Which zui you flash Indian or Chinese.
Haider** said:
Which zui you flash Indian or Chinese.
Click to expand...
Click to collapse
Chinese. I managed to find it in system/vvendor/usr/keylayout.
Now my problem is, my phone only detects 16GB of storage instead of 64GB. I need help.