Related
Galaxy S advance.
Rooted a while ago. Android 4.1.2
Baseband I9070XXLQ4
Today phone says 'no SIM'. I can't call, I can't be called. Only emergency calls.
SIM card works with other phones.
So it's software or hardware.
Help.
hardware.. seems like u got ur baseband.. so modem still working fine..
edit: if it happen after you root try flashing stock rom or kernel..
flash stock via Odin!
Sent from my GT-P1000 using Tapatalk 4
pawelarc said:
flash stock via Odin!
Sent from my GT-P1000 using Tapatalk 4
Click to expand...
Click to collapse
All the times I had this problem I've flashed stock ROM with Odin and I can confirm that it works. Seems that sometimes is a problem of SecPhone.apk
Thanks guys, but can you point in the right direction (with flashing the stock ROM)? Like, where do I find it and stuff...
(I don't know how I managed to root my phone without breaking it in the first place xD)
vici30 said:
Thanks guys, but can you point in the right direction (with flashing the stock ROM)? Like, where do I find it and stuff...
(I don't know how I managed to root my phone without breaking it in the first place xD)
Click to expand...
Click to collapse
I've writed how to reflash stock firmware in this thread, you can follow up to the sixth step, and if you are interested also to root and CoCore kernel go up to tenth step (after this reboot device)
EDIT: You don't need "Re-Partition" option in Odin
No SIM card (but network OK 4 bars)
Hi,
I have a 9070P (NFC) simlocked to Orange France.
I've got the very same "no SIM card" issue after upgrading to JB via Odin (3.07) (tar downloaded from samfirmware).
Network is OK (4 bars), but "no SIM card". The SIM works fine in any other phone I have tested + inserting a SIM from a different operator does not trigger the "enter unlock code" popup at startup.
My IMEI is OK and has always been (*#06#).
Note : from the many posts I've read, it is *not* stored in /efs on this phone but could be stored in CSPSA partition.
Note : I've always flashed the *right* firmwares for I9070P (not I9070).
What I have tried so far :
* restock to GB with this tutorial : http://forum.xda-developers.com/showthread.php?t=2247604
--> No SIM card
* then flashed Orange's stock firmware with Odin from samfirmware
--> No SIM card
* played a bit lot with "secret code" *#197328640# menus. It happened once that I recovered the SIM card + data connexion then it failed again after next boot. So I'm pretty sure the pb *is* software.
It's a pitty I have backed up my "efs", and "CSPSA" partitions (http://forum.xda-developers.com/showthread.php?t=2145464) after the pb occured...
I have rooted the phone, dumped and tried to analyse modem/RIL logs, but did not manage to spot the pb...
I'm used to linux, flashing and so on but not that much of Android intricaces, so if anybody is willing to help me finding the solution I'd pay him/her a bear (or two)
Questions : does anybody know how to check CSPSA partitions ? It's content might have been damaged during flashes. As I have repartitioned when downgrading, partition size should be OK, but as I have read somewhere in xda that that partition content might not be replaced when flashing a tar.md5 that contain a cspsa image (which is the case in the ROM flashed to downgrade) because it contains the IMEI encrypted.
-> is there a way to mount and explore it or to extract the content of a cspsa image from a ROM (I've tried to mount it as ext4: failure)?
Thanks in advance !
What version of Jelly Bean you have flashed the first time?
Hi!
It was this one : Germany (T-Mobile) I9070PXXLPJ grabbed from Samfirmare (I doubled checked it was the one for the "P" version)
Any known pb with those JB upgrades?
flentus said:
Hi!
It was this one : Germany (T-Mobile) I9070PXXLPJ grabbed from Samfirmare (I doubled checked it was the one for the "P" version)
Any known pb with those JB upgrades?
Click to expand...
Click to collapse
I don't know if this version has the simlock, maybe your phone doesn't recognize sim card because you have updated with Odin from a simlocked GB to a non-simlocked JB or with simlock from another carrier
Hm, did you try to do factory reset? People had problems with signal if they do not do it after GB>JB.
Sent from my GT-I9070 using Tapatalk
Tesla-MADAL93 said:
I don't know if this version has the simlock, maybe your phone doesn't recognize sim card because you have updated with Odin from a simlocked GB to a non-simlocked JB or with simlock from another carrier
Click to expand...
Click to collapse
I restocked to original ROM : still no Sim card + if the pb was simlock, it would ask for unlock code whereas it just say "no SIM card".
---------- Post added at 10:10 AM ---------- Previous post was at 09:57 AM ----------
shut_down said:
Hm, did you try to do factory reset? People had problems with signal if they do not do it after GB>JB.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
Yes, I did factory resets, cache wipes, dalvik cache erasure multiple times (like 20) : no dice.
Does anybody know how to activate and analyse modem and RIL logs (and manage debug level) ? I think it would help find the root cause faster than "trial and error" + decrease the risk of bricking.
flentus said:
I restocked to original ROM : still no Sim card + if the pb was simlock, it would ask for unlock code whereas it just say "no SIM card".
Click to expand...
Click to collapse
Right, as you said maybe the problem is really the CSPSA because simlock infos are stored in this partition, seems that there is no way to unpack or to see the files contained in it, if you try to reflash Jelly Bean using repartition?
Tesla-MADAL93 said:
Right, as you said maybe the problem is really the CSPSA because simlock infos are stored in this partition, seems that there is no way to unpack or to see the files contained in it, if you try to reflash Jelly Bean using repartition?
Click to expand...
Click to collapse
- Reflash Jelly Bean with repartion : already done without success + JB ROMs (I've seen until now) do not contain CSPSA partition.
But my problem is not SIM lock, it's "no SIM" at all, as I already said, if it was a Sim lock issue, I would have the "insert unlock code" dialog at logon.
- For reference : I've found the sources for CSPSA Android manager and desktop tools at : download.meego.com/live/home:/imppa/Trunk/src/[/url] (it's from the Meego project)
I think it would enable to read/write from/to CSPSA partition properly (not peeking/poking blindly).
- For now, I'm trying to analyse "adb logcat -b radio", but lots off errors seem to but "normal", I can hardly identify which ones are relevant.
Anybody reading radio logcat fluently ?
Guys, could any of you backup the 3 following partitions of their I9070P and post them somewhere to me so that I can try to restore them on my device to see if it sorts out my problems ?
The full tuto is here : http://forum.xda-developers.com/show....php?t=2145464
Thanks in advance !
Bump !
Nobody willing to help me ?
Tried installing CM10.1: still "no SIM"
search xda to find help contain tee folder
i forget links source
but u can after root
copy orginal tee folder from ,, lib ,, system , tee
i use zsmg2 work and copy tee folder and flash another rom then copy tee and replace them fine my simcard work
zakaria9 said:
search xda to find help contain tee folder
i forget links source
but u can after root
copy orginal tee folder from ,, lib ,, system , tee
i use zsmg2 work and copy tee folder and flash another rom then copy tee and replace them fine my simcard work
Click to expand...
Click to collapse
Hi Zakaria !
thanks for your answer.
This solution works if you have flashed a "I9070" ROM on a "I9070P". But I never did that, I have always flashed "P" ROMs.
I have checked the MD5sum of the files in my "tee" folder, they are (as expected) the same as the ones into the .zip you are recommending me (I've checked the rights too : everything is OK).
Given what I see in the radio logs (logcat -b radio), the problem appears to be under the RIL layer: modem seems OK but it replies that the SIM is "absent" when queried. It could be a hardware problem to, but as it worked well before, I don't think so.
I would really like to overwrite my CSPSA, modemFS and EFS partitions from a working I9070P to see if it would solve the pb (I've made backups of mine in the current "non working" state).
I'm just expecting someone to dump and send them to me...
Have a nice day.
flentus said:
Hi Zakaria !
thanks for your answer.
This solution works if you have flashed a "I9070" ROM on a "I9070P". But I never did that, I have always flashed "P" ROMs.
I have checked the MD5sum of the files in my "tee" folder, they are (as expected) the same as the ones into the .zip you are recommending me (I've checked the rights too : everything is OK).
Given what I see in the radio logs (logcat -b radio), the problem appears to be under the RIL layer: modem seems OK but it replies that the SIM is "absent" when queried. It could be a hardware problem to, but as it worked well before, I don't think so.
I would really like to overwrite my CSPSA, modemFS and EFS partitions from a working I9070P to see if it would solve the pb (I've made backups of mine in the current "non working" state).
I'm just expecting someone to dump and send them to me...
Have a nice day.
Click to expand...
Click to collapse
We do not have much P ROMs, maybe just one. What P ROM you flashed?
shut_down said:
We do not have much P ROMs, maybe just one. What P ROM you flashed?
Click to expand...
Click to collapse
I've always flashed stock ROMs from SamMobile. There are dozens of them.
As explained in a my first post in this thread, I have tried to upgrade to JB (German (T-Mobile) I9070PXXLPJ) : this is when appeared the "no SIM" problem.
Then I went back to GB (tutorial posted in xda ref. given in my 1st post) and then applied stock ROM from my Carrier: stil no SIM. (SIM card is OK in any other phone, and tried at least 3 other SIM cards from my carrier, -my phone is still SIM locked to it: no SIM).
Even if I use a SIM card from another carrier, I don't get the "Enter unlock code" popup.
If I remove any of those SIM while phone is on, I don't get the "SIM removed: reboot" popup.
I have even flashed the latest nightly CM10.1 for the I9070P.
I can past radio logcats if anybody want to have a look at it...
Flentus
I successfully rooted galaxy pop/mini but now its signals are gone also baseband vesion is gone , it do not detect any sim card , i tried to repair it from shop but they also denied , please help friends !
Hi,
I will have your thread moved to your device section. I suggest you add some more information to your post though. Like how you rooted exactly... Did it work also? Is your imei number still showing? (don't post the number here) and anything else you've done to your device.
Good luck!
RohitSole said:
I successfully rooted galaxy pop/mini but now its signals are gone also baseband vesion is gone , it do not detect any sim card , i tried to repair it from shop but they also denied , please help friends !
Click to expand...
Click to collapse
What is your firmware version?
Indian baseband? You flashed anything after rooting?
Where did you get that root zip?
That zip must have contained some third party binaries which caused baseband crash. It is always advised to flash stock rom via odin(pop/mini specific odin).
Sent from my GT-S5570 using XDA Free mobile app
Yes it is indian baseband but now its showing unknown , i'll tell u firmware version shortly , it successfully rooted all was fine but i started it by mistakenly using "LOCK key + Home key + VOLUME down ' and it said downloading and then the problem started ..... the zip file was from here (xda) only !
Dear Darth
Hi Darth , i rooted it by using mobile only via download zip available here , yes it is showing imei , but unable to detect signals from sim card now should i re root it via odin ?
RohitSole said:
Hi Darth , i rooted it by using mobile only via download zip available here , yes it is showing imei , but unable to detect signals from sim card now should i re root it via odin ?
Click to expand...
Click to collapse
Flash back stock gb using odin. Mine is also indian baseband and i never had imei issues after rooting.
Sent from my GT-S5570 using XDA Free mobile app
Not
Bro now having imei no gone and baseband version too , i hav to pay 1500 rupees to get it official , tried to flash via odin but its not detecting it !
Did someone try to change the firmware on any UL00 device to L09 and uptade to B303?
I changed my Location from UL00-C00B120 to UL00-C433B114 without any Problems.
If i try to change to L09-C432B114 the same way (change build.id etc.) an error appears "incompatible with current version"
Changed Build.id to L09-C432B114/B000 and then tried to update to B114/B145 without success.
Tuerkay said:
Did someone try to change the firmware on any UL00 device to L09 and uptade to B303?
I changed my Location from UL00-C00B120 to UL00-C433B114 without any Problems.
If i try to change to L09-C432B114 the same way (change build.id etc.) an error appears "incompatible with current version"
Changed Build.id to L09-C432B114/B000 and then tried to update to B114/B145 without success.
Click to expand...
Click to collapse
I think you would need to change the details in the file OEMINFO.
If you look in the forums I made a post about converting from L09 to UL00
I recently converted back from UL00 to L09
brumgav said:
I think you would need to change the details in the file OEMINFO.
If you look in the forums I made a post about converting from L09 to UL00
I recently converted back from UL00 to L09
Click to expand...
Click to collapse
change oeminfo back to dualcu/cn or leave as hw/meafnaf?
Tuerkay said:
change oeminfo back to dualcu/cn or leave as hw/meafnaf?
Click to expand...
Click to collapse
From memory I think OEMINFO needs to be hw/eu for L09
But I would need to check when I get home in about 2 hours time
You'll then need to install the CRR-L09C432B114 firmware, which will them collect OTA update to B145...then you can install the B303 MM Beta from the other forum post
brumgav said:
From memory I think OEMINFO needs to be hw/eu for L09
But I would need to check when I get home in about 2 hours time
You'll then need to install the CRR-L09C432B114 firmware, which will them collect OTA update to B145...then you can install the B303 MM Beta from the other forum post
Click to expand...
Click to collapse
OK. red your post again and searched the web for more information.
- changed OEMINFO to hw/eu
- changed ro.build.display.id=CRR-L09C432B000
- loaded the full Update.app for CRR-L09C432B114
- fully unrooted device
- flashed stock recovery
- device made some app updates and now there is a message in the notificationbar "Defect report reminders (Beta version) Prohibit any running behaviour!")
- still tried to do an local update.
- Software install failed! Incompatibility with current version
Tuerkay said:
OK. red your post again and searched the web for more information.
- changed OEMINFO to hw/eu
- changed ro.build.display.id=CRR-L09C432B000
- loaded the full Update.app for CRR-L09C432B114
- fully unrooted device
- flashed stock recovery
- device made some app updates and now there is a message in the notificationbar "Defect report reminders (Beta version) Prohibit any running behaviour!")
- still tried to do an local update.
- Software install failed! Incompatibility with current version
Click to expand...
Click to collapse
Have you done a factory reset during any of the above?
brumgav said:
Have you done a factory reset during any of the above?
Click to expand...
Click to collapse
nope not before.
tried to do a factory reset after the update failed but the facotry reset also failed.
Tuerkay said:
nope not before.
tried to do a factory reset after the update failed but the facotry reset also failed.
Click to expand...
Click to collapse
I had to do a factory reset before I could get the update to install?
You may still be on the UL00 version....check your settings to see if you have things like the permissions manager and the mobile data package details (you know the place where you can change your monthly data allowance and cycle date) because if you still have thm then your still on the UL00 firmware.
I had this happen even though my build was showing as L09.
I took the update.app from the CRR-L09C432B144 zip and placed it in the dload/ folder on the root of the device, and then when it tried to update it said not compatiable, and then asked me if I wanted to download the full package, which it did....but a factory reset was needed in the end for me.
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
Also, something else which I think I had to do was to switch off and then hold both power + and - then press the power on...This took me to a firmware update screen (before booting) where it used my wifi to download the latestest firmware....maybe you could try this....im not certain on the volume button combo...it was either just the - and power on, or just the + and power on or like i said both the + and - and power on
brumgav said:
I had to do a factory reset before I could get the update to install?
You may still be on the UL00 version....check your settings to see if you have things like the permissions manager and the mobile data package details (you know the place where you can change your monthly data allowance and cycle date) because if you still have thm then your still on the UL00 firmware.
I had this happen even though my build was showing as L09.
I took the update.app from the CRR-L09C432B144 zip and placed it in the dload/ folder on the root of the device, and then when it tried to update it said not compatiable, and then asked me if I wanted to download the full package, which it did....but a factory reset was needed in the end for me.
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
Also, something else which I think I had to do was to switch off and then hold both power + and - then press the power on...This took me to a firmware update screen (before booting) where it used my wifi to download the latestest firmware....maybe you could try this....im not certain on the volume button combo...it was either just the - and power on, or just the + and power on or like i said both the + and - and power on
Click to expand...
Click to collapse
like i already said. after changeing the oeminfo and edititing the build.prop, the factory reset always fails at 3%. i also can´t use any update.app file. tried using the update.app from the b145.zip but didn´t work either. i also don´t get an message to download the correct update.
what exactly did you write into the build.prop?
i currently have no permission manager and no mobile data manager
Tuerkay said:
like i already said. after changeing the oeminfo and edititing the build.prop, the factory reset always fails at 3%. i also can´t use any update.app file. tried using the update.app from the b145.zip but didn´t work either. i also don´t get an message to download the correct update.
what exactly did you write into the build.prop?
Click to expand...
Click to collapse
I think I wrote CRR-L09C432B114
@Tuerkay Had the same problem. Let me know if you find a fix for it... I'm searching too.
bgx said:
@Tuerkay Had the same problem. Let me know if you find a fix for it... I'm searching too.
Click to expand...
Click to collapse
tried many different things but nothing worked. Now i´m back at C433B114 until someone finds a solution.
I´m missing so many functions but i won´t change back to C00B160 because my main language isn´t supported well enough
Hi,
I am on UL00C00B160. I want to hawe european version. Is it possible to make UL00C432? If I convert to L09 will the phone still be dualsim?
Iverom said:
Hi,
I am on UL00C00B160. I want to hawe european version. Is it possible to make UL00C432? If I convert to L09 will the phone still be dualsim?
Click to expand...
Click to collapse
European version only supports 1 SIM
Loosing the DUAL SIM capability, which is the real benefit of turning a UL00 to a L09?
plantunes said:
Loosing the DUAL SIM capability, which is the real benefit of turning a UL00 to a L09?
Click to expand...
Click to collapse
The languagesupport kinda sucks for german users, if you use the chinese UL00. To have better support, i changed my location from UL00-C00B160 to UL00-C433B112. This way i have got a better language implementation but lost some features which i´m missing now. I´m not using the dual-sim function which is why there are no cons for me.
But since i have the chinese hardware, maybe it would be possible to activate the dual-sim function.
There are two lines in the Buld.prop
persist.sys.dualcards=false
ro.dual.sim.phone=false
changeing these and some other options could help maybe.
Tuerkay said:
The languagesupport kinda sucks for german users, if you use the chinese UL00. To have better support, i changed my location from UL00-C00B160 to UL00-C433B112. This way i have got a better language implementation but lost some features which i´m missing now. I´m not using the dual-sim function which is why there are no cons for me.
But since i have the chinese hardware, maybe it would be possible to activate the dual-sim function.
There are two lines in the Buld.prop
persist.sys.dualcards=false
ro.dual.sim.phone=false
changeing these and some other options could help maybe.
Click to expand...
Click to collapse
Do you have a CL00 converted into a L09?
If you do, you could change that string "ro..dual.sim.phone" into TRUE and see what happens. It would be absolutely great if that was possible!
I had the same problem than you, so i flashed Boot.img, Cust.img, Recovery.img, system.img and userdata.img (just in case), and it worked. the phone doesn't found the OTA to B145, but i'll try to update manually.
Lightofdarkness666 said:
I had the same problem than you, so i flashed Boot.img, Cust.img, Recovery.img, system.img and userdata.img (just in case), and it worked. the phone doesn't found the OTA to B145, but i'll try to update manually.
Click to expand...
Click to collapse
Flashed all files and then tried a clean update. Didn´t work. My Mate S shows the right Build and Vendor but i´m still not able to use the C432 Update.app´s.
Are you able to update manually?
Is your phone originally an L09 or UL00 device? If it´s an UL00 Mate S, could you tell me exactly what you did?
My phone is originally an L09, but i broke it in UL00C00, can't get back to L09, recovery don't boot, flash via fastboot lead to freeze at boot
Yesterday I figured to debrand my VNS-l21. Everything is fine, updated manualy to latest ROM B130. But, CUSTC has changed from C02 (Vodafone EU) to C900 (Global). In P7 thread there someone posted small update.app file (around 18 kb, http://forum.xda-developers.com/ascend-p7/help/p7-l10-defect-report-reminders-t2952124) that after flashing will change the CUSTC back to C432 (EU open market).
Have someone idea where to get this file for VNS-l21?
Ghouless said:
Yesterday I figured to debrand my VNS-l21. Everything is fine, updated manualy to latest ROM B130. But, CUSTC has changed from C02 (Vodafone EU) to C900 (Global). In P7 thread there someone posted small update.app file (around 18 kb) that after flashing will change the CUSTC back to C432 (EU open market).
Have someone idea where to get this file for VNS-l21?
Click to expand...
Click to collapse
Heyho,
u can do this also on the VNS-L21.
Hope i could help u
Regards,
Sebastian
k1ll3r8e said:
Heyho,
u can do this also on the VNS-L21.
Hope i could help u
Regards,
Sebastian
Click to expand...
Click to collapse
Nice work with the toolkit Years before I had unlocked & rooted every of my smartphones but, last two years I need to work with some apps that recognizing rooted device and won't work (bank app etc.). So if there no chance to change the region back to C432 without rooting the device, I will stay on that Global CUSTC (after two days of deep testing, there's no problem with it). Maybe later someone will do that update.app file or will be included in future update ROM.
Thread that I'm talking about http://forum.xda-developers.com/ascend-p7/help/p7-l10-defect-report-reminders-t2952124
Ghouless said:
Nice work with the toolkit Years before I had unlocked & rooted every of my smartphones but, last two years I need to work with some apps that recognizing rooted device and won't work (bank app etc.). So if there no chance to change the region back to C432 without rooting the device, I will stay on that Global CUSTC (after two days of deep testing, there's no problem with it). Maybe later someone will do that update.app file or will be included in future update ROM.
Thread that I'm talking about http://forum.xda-developers.com/ascend-p7/help/p7-l10-defect-report-reminders-t2952124
Click to expand...
Click to collapse
Heyho,
THX for ur warm words and the hint
-
About the build id, the only problem which happened to me while i was on the Asia build is, that u don't get any updates...
About the update.app, i just downloaded the file u linked me, i'll have today a look at it. Maybe we can produce such an file also for our L21/L31.
Regards,
Sebastian
k1ll3r8e said:
Heyho,
THX for ur warm words and the hint
-
About the build id, the only problem which happened to me while i was on the Asia build is, that u don't get any updates...
About the update.app, i just downloaded the file u linked me, i'll have today a look at it. Maybe we can produce such an file also for our L21/L31.
Regards,
Sebastian
Click to expand...
Click to collapse
First, if you can build that update.app for l21/l31, it would be amazing, because that will be BIG help for everyone who want only to debrand our P9 Lite's without lose warranty or brick it.
Second, nice to have there someone, who taking care of this phone :good:
Hello dear developers...Recently I bought a used Huawei p9 lite vns-l21c150b106 single sim...It is cosmote branded and I want to debrand it cause I found out by searching that there are several updates such as b150...When I try to update my phone it says that has the latest updates...I wanted to ask if there is a way to debrand it and return to official Europe stock rom without void my warranty...I found a way in the internet through local update via sd card but I don't find the stock rom Europe(I live in Greece)for my single sim vns-l21...I found only vns-l21c432b160 which is for dual sim...I think that vns-l21c150b160 must be for my single device,i suppose that the difference is c150 and c432...any solution please???
hey guys i hope you can help me with this lil problem.
I was flashing update with just fail messages so i decide to install the same (eva-l19C6005B135) BUT it was the D007 (my phone has D002) and it was ok, after the update the phone restarts but now the wifi isn't working( it does turn on but doesn't show any wifi available).
btw the phone says D002 is installed (weird) (CUSTC605D002)
everything is just working fine, i restore the net config and restarted the phone but still the same, no wifi
what can i do now ? :/ this isn't my phone
Blackko said:
hey guys i hope you can help me with this lil problem.
I was flashing update with just fail messages so i decide to install the same (eva-l19C6005B135) BUT it was the D007 (my phone has D002) and it was ok, after the update the phone restarts but now the wifi isn't working( it does turn on but doesn't show any wifi available).
btw the phone says D002 is installed (weird) (CUSTC605D002)
everything is just working fine, i restore the net config and restarted the phone but still the same, no wifi
what can i do now ? :/ this isn't my phone
Click to expand...
Click to collapse
You mean eva-l19C6005B135 (c605), not eva-l19C6005B135 (c6005)?
Anyway, this is old Android 6 / EMUI 4, why don't you upgrade to Android 7?
If you have valid SIM card and WiFi, no OTA for update coming?
Check under Settings / System Updates.
You can also check from HiSuite if it offers you a newer version to install
Also, switch off, connect to charger, press and keep Vol+, switch on by Pow, and check from eRecovery: Download and install latest firmware and recovery, what it offers to install
You can also try to install by DLOAD, L19 c605 eg b394 - for DLOAD it must be FullOTA, MF-PV (must be PV), package number #109400, as on screenshot from Firmware Finder
zgfg said:
You mean eva-l19C6005B135 (c605), not eva-l19C6005B135 (c6005)?
Anyway, this is old Android 6 / EMUI 4, why don't you upgrade to Android 7?
If you have valid SIM card and WiFi, no OTA for update coming?
Check under Settings / System Updates.
You can also check from HiSuite if it offers you a newer version to install
Also, switch off, connect to charger, press and keep Vol+, switch on by Pow, and check from eRecovery: Download and install latest firmware and recovery, what it offers to install
You can also try to install by DLOAD, L19 c605 eg b394 - for DLOAD it must be FullOTA, MF-PV (must be PV), package number #109400, as on screenshot from Firmware Finder
Click to expand...
Click to collapse
the phone doesn't show any update to nougat, im stock at C605B135, but i do remember that it showed an update a while ago, but not now, weird thing.
well, if i try to install with the dload method the phone says "Incompatibility with current version. Please download the correct update package"
I tried the B380 and 397, i will try the 394 that you suggest.
thanks for the help buddy, i will update the post later with the results
PD: can i download this rom from another site or this is the only one? it always fails at 60-70% and it is really slow, 3mb download, i have 30mb
zgfg said:
You mean eva-l19C6005B135 (c605), not eva-l19C6005B135 (c6005)?
Anyway, this is old Android 6 / EMUI 4, why don't you upgrade to Android 7?
If you have valid SIM card and WiFi, no OTA for update coming?
Check under Settings / System Updates.
You can also check from HiSuite if it offers you a newer version to install
Also, switch off, connect to charger, press and keep Vol+, switch on by Pow, and check from eRecovery: Download and install latest firmware and recovery, what it offers to install
You can also try to install by DLOAD, L19 c605 eg b394 - for DLOAD it must be FullOTA, MF-PV (must be PV), package number #109400, as on screenshot from Firmware Finder
Click to expand...
Click to collapse
the same error... "Incompatibility with current version. Please download the correct update package" with the version that you said, i dont know what to do now
here are the steps that i did:
1-downloaded update.zip (just this file)
1.1 unzip it
2-put it on sd(dload folder)
3-enter download mode and try to install it
do i need to download the other files?
do i need to format my sd again? because it have some other files in it, but with the ota b135 it jus install it fine over and over again
Blackko said:
the same error... "Incompatibility with current version. Please download the correct update package" with the version that you said, i dont know what to do now
Click to expand...
Click to collapse
Sorry, don't know the situation with c605 ROMs.
IMO, you should try to flash FullOTA-MF-PV but the MM buiild, but I cannot find by Firmware Finder any MM PV build for your c605 cust (hence I also don't know how did you flash that D007 at the first place?!)
You could also rebrand to eg c432, there are many more stock firmwares for c432 - but for rebranding you will first need to unlock Bootloader
PS: For DLOAD, you must download and put to the DLOAD folder all update* files you find for the given build, not just the first update.zip file- if you didn't do so, that was maybe the reason for your issues with WiFi
zgfg said:
Sorry, don't know the situation with c605 ROMs.
IMO, you should try to flash FullOTA-MF-PV but the MM buiild, but I cannot find by Firmware Finder any MM PV build for your c605 cust (?!)
You could also rebrand to eg c432, there are many more stock firmwares for c432 - but for rebranding you will first need to unlock Bootloader
PS: For DLOAD, you must download and put to the DLOAD folder all update* files you find for the given build, not just the first update.zip file- if you didn't do so, that was maybe the reason for your issues with WiFi
Click to expand...
Click to collapse
how can i unlock the BL? the only method that i think will work is send an email to huawei as a request for the code :/ or paying 20$ for chimera software and unlock it(i don't know if it will work anyway)
but for now im going to download all the files again for a second try and yes, im sure that's why my wifi if failing, i downloaded a ota (not full ota) with a different D007 (mine is D002) because there is not any MM rom for c605 just that one from firmware finder rewrite (desktop version)
Blackko said:
hey guys i hope you can help me with this lil problem.
I was flashing update with just fail messages so i decide to install the same (eva-l19C6005B135) BUT it was the D007 (my phone has D002) and it was ok, after the update the phone restarts but now the wifi isn't working( it does turn on but doesn't show any wifi available).
btw the phone says D002 is installed (weird) (CUSTC605D002)
everything is just working fine, i restore the net config and restarted the phone but still the same, no wifi
what can i do now ? :/ this isn't my phone
Click to expand...
Click to collapse
Please check older threads under the same P9 Q/A subforum (and/or in the Guides subforum) where you opened your own thread - every week or so somebody asks the same questions about codes for Bootloader (just curious why nobody wants first to invest his own time to search for the answers
Not specific for P9 but same for the other Huawei/Mate models (excluding the newest models released alreadyvwith Pie)
Hint: DC Unlocker or Ministry of solutions, price is not 20 but 4 or 5 Euros
zgfg said:
Please check older threads under the same P9 Q/A subforum where you opened your own thread - every week or so somebody asks the same questions about codes for Bootloader (just curious why nobody wants first to invest some of his own time to search for the answers
And/or in the Guides subforum.
Not only for P9 but same for the other Huawei/Mate models (excluding the newest models eleased alreadyvwith Pie
Hint: DC Unlocker or Ministry of solutions, price is not 20 vut 4 or 5 Euros
Click to expand...
Click to collapse
ok thx budd, where do i have to unzip the other files? like data and public data etc, in the same dload folder?
Blackko said:
ok thx budd, where do i have to unzip the other files? like data and public data etc, in the same dload folder?
Click to expand...
Click to collapse
All three update*.zip files must not be unzipped, just copy them as zip files to DLOAD folder, do not create any subfolders
Do not use L09 file, just update.zip and two others with L19 and public in the name - see screenshot
Dlete DLOAD and create again, to make sure something hidden did not remain
And for Bootloader codes you have:
https://www.dc-unlocker.com/
https://ministryofsolutions.com/paid-services
zgfg said:
All three update*.zip files must not be unzipped, just copy them as zip files to DLOAD folder, do not create any subfolders
Do not use L09 file, just update.zip and two others with L19 and public in the name - see screenshot
Dlete DLOAD and create again, to make sure something hidden did not remain
And for Bootloader codes you have:
https://www.dc-unlocker.com/
https://ministryofsolutions.com/paid-services
Click to expand...
Click to collapse
thx for the help, this is all the info i need, you know alot of this
Blackko said:
thx for the help, this is all the info i need, you know alot of this
Click to expand...
Click to collapse
Were you able to update/DLOAD now?
zgfg said:
Were you able to update/DLOAD now?
Click to expand...
Click to collapse
well, i think i bricked my device :/ i unlocked it via chimera, and installed a rom from another country without rebrand it first, after that it just boot to a recovery screen with the option of factory reset but it trows an error,
y flashed the rom b135 that i flash before and the phone install it and everything was ok but now, it doesn't boot, im stuck at the warning screen "your device has been unlocked and can't be thrusted" and the phone says booting now but nothing happends, i can't even flash the same rom again, im stuck :/
PD:the chimera or hi suit doesn't recognize the phone
Blackko said:
well, i think i bricked my device :/ i unlocked it via chimera, and installed a rom from another country without rebrand it first, after that it just boot to a recovery screen with the option of factory reset but it trows an error,
y flashed the rom b135 that i flash before and the phone install it and everything was ok but now, it doesn't boot, im stuck at the warning screen "your device has been unlocked and can't be thrusted" and the phone says booting now but nothing happends, i can't even flash the same rom again, im stuck :/
PD:the chimera or hi suit doesn't recognize the phone
Click to expand...
Click to collapse
Of course that flashing another cust without rebranding first, bricks the phone.
I just wonder how you know now that, why you didn't take time to read or ask about in advance (and I think, in previous answers I was also writing you about)
Sorry, I'm busy and cannot help you further.
There are guides on XDA, but maybe better pay for DC-Phoenix or Ministry of solutions to unbrick the phone and to install you Nougat like c432 b504
download http://download-c1.huawei.com/downlo...52&siteCode=np
Create a file dload in SD card and move file Update.app in dload .
Use method 3 Buttons To install.