Hello
I have a problem with my RN3 SE (yes I'm sure it's SE, model "2015161" and 152mm). It all started when I uploaded the Mi-mipip rom to my phone. Initially, I uploaded Kenzo (I was convinced that I have this model) but there were symptoms that were typically associated with inappropriate rom. Initially, I did not have IMEI (no range, wi-fi etc) and constantly popping "camera error" - "can not be connected to the camera", when I was able to recover the imei, Wi-Fi returned, but unfortunately there was still a problem with the lack of range and the camera did not work . Reading many threads, it occurred to me that I uploaded a bad rom. I decided to install the appropriate rom Kate (edl mode by miflash) unfortunately when the phone turned on, only the MI logos and the loading (leaping) dots of the android were displayed (I waited over 2-3 hours and to no avail). Out of curiosity, I uploaded rom from kezno in the same way and the phone immediately woke up to life but still without range and the camera was not working. I solved the problem with the range by replacing the modem with Kate, but I still have a problem with the camera. Trying to repair the mistake I tried to upload rom miuipolska under Kate via TWRP, however, the installation stopped at 99% and did not move for over an hour so that the phone could come alive and I had to flash it again with the Kenzo room with the switched range modem. Do you have any ideas how I could deal with it?
Related
Original post below:
I had problems with MiFlash (it did not see my Phone). The solution was to remove the stock Android ADB driver from android_winusb.inf from a previous attempt .
I have uninstalled the drivers, then started MiFlash, reconnected the phone in fastboot mode -> it installed the drivers, MiFlash did see the phone, installed the latest stable ROM from MIUI.
Unfortunately Google Play does not work (not even Store!).
-------------------
Hi!
I have bought my Xiaomi phone through amazon and found out it had adwares installed. I have just found this article on receiving these kind of xiaomi devices: Techworm Xiaomi Adware Preinstalled (linking is disabled as I am a new user).
So I went and downloaded the unofficial ROM from xiaomi.eu, put update.zip on my SD Card and started updating from the Updater app (selected the zip file). Now it won't boot, it stops and flickers, sometimes my lock screen comes for a sec then it goes back to the MI logo.
The phone otherwise seems original, I've checked the IMEI on imei.info and it pointed to this phone, and also used CPU Z to verify the hardware. I tried though the IMEI service on Xiaomi!s site , but I can't go through the Chinese captcha to verify it .
The good news is that I can reach the phone through fastboot AND MiFlash (can reboot it with that).
How may I proceed?
I don't have a strong emotional connection to MIUI, so even a stock android would be fine. Or the official ROM, I don't care at this point, just let it work!
Thanks for reading/helping!
I already opened an RMA for the phone but they have no stock so I figured I'll take another shot at it.
The short version is that my gf messed up and updated the system while transferring her data from her old phone with the tapNgo thing.
I've done multiple facory resets, downloaded the rom from ZTE support, put it on SD, flashed it from recovery and deleted cache and nothing helps.
I don't have the exact error log anymore since I don't have the phone with me now but it reads something along the lines of
loading /proc/devices/audio/sound------ cannot find file/directory.
I looked it up and after a lot of Googling it seems like the symlink to the actual driver folder is missing and I have no idea why.
Does anyone know if i can fix this with an ADB shell?
Alternatively, I tried to follow some of the many guides out there to put the phone in EDL mode and relfash it with XiamiFlash utility but after trying 3-4 downloads and 900 versions of misflash all I ever get is "reading hello packet... unable to communicate to com4"
Haaaalp please?
*edit* this is pretty much exactly the same as what I'm getting: https://forum.xda-developers.com/android/help/sound-card-detected-t3379736
The problem with the phone is it makes no sounds?
gpz1100 said:
The problem with the phone is it makes no sounds?
Click to expand...
Click to collapse
the sound drivers for the OS is missing completely, no sound no microphone.
The syslog looks like this(this is from another phone its its the exact same problem):
AudioDaemon: Opening sound card state : /proc/asound/card---/state
AudioDaemon: Open /proc/asound/card---/state failed : No such file or directory
AudioDaemon: Sleeping for 100 ms
Strange issue indeed. Which model do you have? Which specific firmware file are you flashing to it?
I would think flashing the full unmodified factory firmware using the stock recovery will wipe the phone completely, including the /data partition.
Everything worked before? Help me understand the order of events. What is tapngo?
While in the midst of transferring information to or from the phone, a software update appeared and she accepted/installed it?
Its the A2017U model.
I had tried the 1.1.0 B15 firmware from SD card as well as the 1.0.0 B29 older firmware.
Right now its on B17 Nougat 7.1.1, the phone runs and works perfectly just has no audio hardware.
I wasn't there for the exact procedure but basically she powered it on, it asked for sim, she inserted that, tapped the "transfer my data" and then held the two phones together to get the NFC process started. That starts the bluetooth transfer process and it takes a really long time where it transfers all data and apps from the old phone.
At this point the phone still made sounds when adjusting the volume etc.
Somewhere in that process the "update available" notification came up and she pressed the option to install it.
After I got home I tried to figure out what is wrong, first i thought the phone wasn't registered on the cellphone network but then after a bit i figured out the audio is the issue, then i did a factory reset both from the phone UI and tried again from recovery mode, both times chose the "erase all data" option but neither time did it help at all.
I don't really know enough about phones but i think its the bootloader/something very early on thats messed up. Either that or the audio chip really just did fry.
My hope was to get the full factory image for everything that you need to install with the EDL mode thing but I can't find any good reliable guides for that.
It's the first thread in the development section.. Stickied even.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Get this package - B15-NEW_FULL (Nougat)
I really don't understand zte's numbering scheme. Newer versions get lower numbers. Makes no sense. That's the full firmware except for the fastboot which passes commands. At this point it's a non issue given the issue you're having.
So I don't need to load TWRP on it, I can still keep it just stock with unlocked bootloader?
I tried that miflash thing before, i had it connected un usb download mode but nothing worked for me, I'll try doing this guide when i get home step by step again.
Their firmware numbers is based on numbers and letters 1.0a-z and then 1.1a-z so 1.0z1 is less that 1.1a1
Ok I have an update
Did miflash, nothing changed.
Ulocked bootloader and miflashed the bootloader from the sticky thread.
The phone made the startup sound and audio worked for a few seconds after android started up and then stopped again
*edit*
ok so after it showed signs of life i re-locked the bootloader, and did the OTA updates to 7.1.1 and the audio seems to be working for good now!!
Conclusion seems to be the bootloader was the key to get it working again. Hope this helps others if it comes to it.
Hey all......I created a thread awhile back when I borked my phone trying out a new treble rom that was supposed to be so easy even a nOOb could flash it, and it ended up messing up my phone to the point where the only way for me to get it back was to follow the thread to disassemble the phone and short the chip out.
Then, the screen was not responsive on ANY rom I flash except for MM and it worked with any up to B29. I tried a few times to upgrade all in vain but I was always able to flash MM B29 and have it work again.
Flash forward to last night and my itchy trigger upgrade finger did it again and I attempted to flash the Oreo from ZTE. It flashed fine but, again, no responsive screen. I thought well, maybe I could try Nougat again and I flash many different versions and in different ways (used miFlash, EDL tool, MiFavor recovery, twrp) and all resulted in the screen not being responsive. Sigh, so I flashed MM B29 but now it will not detect any sim or even allow wifi to be turned on.
I have tried multiple times to reflash MM B29 using all the different ways above and even went back and forth between roms. I tried the original way most of us first unlocked the bootloader and flashed through all those stepped zip packages from B20 to B29 and still nothing. I finally used twrp to erase/format all data and made certain the partitions were formatted as ext4 and tried again, still no sim.
I realize that my imei is not showing and even tried a program to flash? that to the phone.
NOW, what needs to be said is during ALL of this flashing the phone signal/sim DID show......yes.......the sim DID WORK......when I flashed anything other than MM B29. LOL. Of course, the issue is none of those roms allow the screen to work.
Please, if anyone can help I would appreciate it very much. I'm thinking by flashing the Oreo from ZTE it may have changed something that the MM B29 rom is not changing to allow the phone to read the imei/sims.
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps ?
Syberclone said:
I'm not sure but I think the DFU multitool posted by @raystef66 can fix the IMEI issue.
You have installed the correct modem for you device? EG: if you've flashed a U modem on a G device the sim and WiFi won't work.
If this is correct check APN and network setting in the phones software.
I hope this helps
Click to expand...
Click to collapse
I appreciate the suggestions. Unfortunately, the DFU tool doesn't seem to work for me as it remains listed as Disconnected even after choosing the correct port.
I have always flashed the MM B29 EDL rom (A2017U_B29_MARSHMALLOW_FULL_EDL) that contains the correct modem. As I said, it always worked before.
As far as checking APN/network settings, well, there are none to check because the sim is not detected so all of those choices are greyed out. The signal bars fr both sims are blank in the notification area and of course wifi does not turn on.
I just finished another round of trying different roms to flash including LOS 15. LOS came up to the welcome screen (just like all the others) AND the AT&T logo with LTE full signal bars showing. Again, the screen does not respond to touch so it's all useless. I am at a loss as to why flashing MM B29 is no longer working for me.
Stop using guides mentioned in Axon7 thread,or stop listening to other users.Only thing i see here are bricks.
Probably you have hardware fault
The Axon 7 has been the worst phone for being bricked.
I've flashed ROMs on HTC's, Motorola and Google phones all without problems.
There are way too many packages and bootstacks etc, etc that cause problems and confusion.
So I wouldn't say don't follow threads or users advice.
My advice is research, research and research some more.
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
djprez said:
Thanks for the suggestions.
Something to get clear.....
I can successfully flash the roms and get to the Welcome screen to begin setup.
MARSHMALLOW:
-screen does respond to touch
-sims are NOT detected
-no AT&T logo
-no phone signal
ANY OTHER VERSION (Nougat, Oreo):
-screen does NOT respond to touch
-sims are recognized
-AT&T logo appears
-phone signal strength meter shows full bars
So, it's not a hardware fault. The phone was working perfectly fine when I had Marshmallow flashed. It's only this last time I flashed the Oreo from ZTE's website and when that did not work I tried a few other roms and then went back to the Marshmallow B29 EDL that I had been using all along.
Isn't there a way to COMPLETELY wipe this phone and start from scratch? As in, when your Windows is so full of crap and running slow you can format the hard drive and reinstall Windows from scratch. I have tried TWRP and format data (have to type yes to format) etc........is there a way to format w=everything that might affect the sim from being detected in Marshmallow? Better yet, the screen from being responsive in other ROMS after marshmallow?
Click to expand...
Click to collapse
Did you installed a vendor partition?
Predatorhaze said:
Did you installed a vendor partition?
Click to expand...
Click to collapse
I am not certain. If the Oreo update that I downloaded directly off the ZTE site has one, then yes. If that is the cause, how would I modify it?
@djprez: To my knowledge, ZTE's official B12/B20 do not have a vendor partition. ZTE will almost certainly never add Treble support for the A7, if they are going to do so then now is an ideal time, since the A7 is an end-of-life device and no longer being manufactured.
Hi friends. Yesterday my main phone (a OnePlus One) as decided to pass away
The lower part of touchscreen it's begin unresponsive and the phone it's pratically unusable.
My brother today gave me his old "Galaxy Note 4". he uses it at home with wifi whitout sim and it's usage to play some little games (his main phone it's a Note 10+) etc etc.
To replace my actual OPO i thinks it's a good temporary phone this Note 4........he asked me if maybe I could update it especially because the phone has the actually last official samsung image based on android 6.0.1.
we gave a view to several guides today but I got a lot of confusion...... who can show me how to behave ?
The phone it's completely stock.... it's never rooted or somethings similar mod..... has always and only installed the official updates that samsung distributed.
Every suggestion it's been accepted....... thanks in advance.
For absurd I have read that it is a N910F from the battery compartment and from the system info...... how i can check correctly the exact model of phone for prevent brick or somethings similar issue ?
*EDIT*
If from "phone" i tap *#1234# it's appear:
AP : N910FXXU1DRI2
CP : N910FXXS1DQA1
CSC : N910FFITV1DRJ1
It's be usefull this value ?
DjDiabolik said:
Hi friends. Yesterday my main phone (a OnePlus One) as decided to pass away
The lower part of touchscreen it's begin unresponsive and the phone it's pratically unusable.
My brother today gave me his old "Galaxy Note 4". he uses it at home with wifi whitout sim and it's usage to play some little games (his main phone it's a Note 10+) etc etc.
To replace my actual OPO i thinks it's a good temporary phone this Note 4........he asked me if maybe I could update it especially because the phone has the actually last official samsung image based on android 6.0.1.
we gave a view to several guides today but I got a lot of confusion...... who can show me how to behave ?
The phone it's completely stock.... it's never rooted or somethings similar mod..... has always and only installed the official updates that samsung distributed.
Every suggestion it's been accepted....... thanks in advance.
For absurd I have read that it is a N910F from the battery compartment and from the system info...... how i can check correctly the exact model of phone for prevent brick or somethings similar issue ?
*EDIT*
If from "phone" i tap *#1234# it's appear:
AP : N910FXXU1DRI2
CP : N910FXXS1DQA1
CSC : N910FFITV1DRJ1
It's be usefull this value ?
Click to expand...
Click to collapse
Sorry to hear about your OPO.
Yes, you can use the Galaxy Note 4 but of course depends on what you wan to use it for and what kind of phone user are you?
The SM-N910F shows it is a European model, so probably won't work in the us. However it does have a Qualcomm porcessor so should be able to run any ROM you decide to install as long as you get the Snapdragon version (NOT Exynos)!!!
Honestly, if you are just a casual user, you can certainly just leave it as stock and just keep everything as it is. I should caution you that messing with operating systems, or rooting, or firmware could result in your phone not working right anymore. And since this is your only working phone now, you need to consider the pro's and con's.
However, if you have a laptop or desktop computer, you CAN download some software called ODIN and it is fairly easy to flash new A)Firmware - how your phone handles radio signals B)ROM- how your phones operating systems work and C)Recovery - on board software that helps your load ROM's onto your phone.
After some time it's pass i have right now successfully installed TWRP on my phone using odin.
After that it's almost easy to flash roms or zip file for made obtain root accees or all other things.
Whit my old OPO these were things I had been doing for years.....
I just had to find the right directions to start all...........
I am in the same situation as you.
I have an old Note 4 SM-N910F. The phone is on latest stock firmware, but is hell of a slugish. Everything is sooo slow. SO i decided to flash some custom ROM.
I just want a phone that runs smoothly and everything works (fingerprint, camera, wifi, BT). No need for dozens of customization etc. I don´t care about the OS version.
Tried so far:
Dirty unicorn (android 6) - no wifi, camera FC
Resurrection Remix (ANdroid 9) - camera FC
Now I am on a crDroid 4.7.2 (android 8) - camera FC, reboot ends with "device unable to boot normally)
I do always a clean flash. Maybe my phone is broken.
DallasCZ said:
I am in the same situation as you.
I have an old Note 4 SM-N910F. The phone is on latest stock firmware, but is hell of a slugish. Everything is sooo slow. SO i decided to flash some custom ROM.
I just want a phone that runs smoothly and everything works (fingerprint, camera, wifi, BT). No need for dozens of customization etc. I don´t care about the OS version.
Tried so far:
Dirty unicorn (android 6) - no wifi, camera FC
Resurrection Remix (ANdroid 9) - camera FC
Now I am on a crDroid 4.7.2 (android 8) - camera FC, reboot ends with "device unable to boot normally)
I do always a clean flash. Maybe my phone is broken.
Click to expand...
Click to collapse
Try crDroid 6. No problems with my camera....
@Unidave199 i have installed lineage os 17.1.
I obtain no sim signal sometimes at reboot of my phone.
I hope it's not a HARDWARE fault.........
DjDiabolik said:
@Unidave199 i have installed lineage os 17.1.
I obtain no sim signal sometimes at reboot of my phone.
I hope it's not a HARDWARE fault.........
Click to expand...
Click to collapse
No, its more like a a software thing... It happens to me occasinally as well.. I just reboot until it connects.
Hi
any other suggestions for stable ROMs ?
Lineageos 18 is great (freat work from Ripee) but has a 5 min GPS lock and bugs with Bluetooth which is an issue for me for work.
Hello everyone,
I've flashed my phones for quite a few years, messed things up from time to time, but always found solutions. This time however, i don't really know where to start.
I kept my Zenfone Max Pro M1 in its original state for the time of warranty and only unlocked and flashed it a few months ago. I first got into problems with the storage (couldn't install apps) and in my attempt to fix it i kinda bricked my phone... i don't remember all the steps i took, but what ended up working was Qualcomm Flash Image Loader (QFIL) with an Image i found online.
After that i flashed Spark OS and later Superior OS (both clean flashes), but with both i'm having problems with the internet connection. I only get EDGE which is really slow (WiFi, phone calls and everything else works fine). Tried out all possibly APNs and swapped SIM-cards with a friend to rule that out.
I'm suspecting some file needed for UMTS and up (specifically for european networks?) has been overwritten, but i haven't been able to find anything (great job by Microsoft renaming their browser also to Edge, doesn't make the search easier).
I recall having similar problems back then and flashing a certain radio.img fixed it, but i don't find anything about that either. Maybe something else baseband related? Do you think Asus could help me out? What to ask for?
Grateful for any input
Update: realized my serialnumber is displayed as C4ATAS000000 which is not that uncommon and might be the culprit. haven't found a working solution yet, but working on it