Related
Hi Everyone,
I thought I'd create a thread for this issue as it seems to be happening at an alarming frequency as of late. Here are some other threads for reference:
http://forum.xda-developers.com/showthread.php?t=1038768&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=1035464&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=1034261&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=1029474&highlight=recovery+mount+open
http://forum.xda-developers.com/showthread.php?t=991206&highlight=recovery+mount+open
http://forum.cyanogenmod.com/topic/...overy++mount++open__fromsearch__1#entry172534
If you're currently experiencing this issue, I'd like to get some information about your device to look for any trends or similarities:
1) Do you have a G2 or a DZ?
2) Which ROM was last running on your device?
3) Do you have the ENG HBOOT installed?
4) Aside from using ROM Manager to flash the recovery image, did you use ROM Manager for anything else (e.g. flashing ROMS)?
To me it seems people are running into this issue alot, and its happing around when the new recovery fix charge came out as well cm7 final came this could be a factor
ilostchild said:
To me it seems people are running into this issue alot, and its happing around when the new recovery fix charge came out as well cm7 final came this could be a factor
Click to expand...
Click to collapse
Which version of cwm are you referring to?
The newest recovery that fixes the off charge issue
maybe related:
http://forum.xda-developers.com/showthread.php?t=1044042
ilostchild said:
To me it seems people are running into this issue alot, and its happing around when the new recovery fix charge came out as well cm7 final came this could be a factor
Click to expand...
Click to collapse
Doubt it. Highly.
1)G2
2)CM 7 RC4
3)No eng hboot
4) I may have used rom manager to download roms a couple times as well as flashing roms
DON_58 said:
1)G2
2)CM 7 RC4
3)No eng hboot
4) I may have used rom manager to download roms a couple times as well as flashing roms
Click to expand...
Click to collapse
which cwm?
Im running 3.0.0.5
We have been looking into this issue on IRC for the past week or so. ANYONE WHO IS HAVING THIS ISSUE NEEDS TO STOP BY THE IRC CHANNEL.
We need to get some more info, right now we only have 2 cases to go on.
irc.freenode.net
#G2ROOT
The internal partitions of the emmc on the incredible are actually visible when connecting to your computer, so a lot of really smart folks formatted these partitions in an attempt to "fix" something that wasn't broken.
this resulted in recovery being unable to mount the partition.
i remember a long time ago helping someone troubleshoot through the process, it involved loading recovery, and using parted to partition and format the different blocks. (this thread here: http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ i'm -Stevo-, although the problem was slightly different the same thing stands, no ability to mount cache.
Now, it's kind of annoying, i've found EVERY person i've ever dealt with that had this issue either disappears a half hour after you begin helping them, or are not advanced enough to use ADB (IT's gonna be required in this case if the above still stands)
There's a couple courses of action that can be taken here, you can manually try and format the partition using parted, or it could be as easy as opening adb shell and
mke2fs -t -ext3 /dev/block/mmcblk0p27
mount /dev/block/mmcblk0p27 /cache
i dunno, no one ever sticks around enough to try anything.
i couldnt even get someone to give me the output of
ls /dev/block
okay so i decided to live dangerously and recreate this error on my device. I made sure the cache partition was nice and corrupted and got greeted with this wonderful message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now this not the same situation that ALL people are in, but in this situation i opened adb shell and typed
mke2fs /dev/block/mmcblk0p27
reboot recovery
everything back to normal.
Now this is ONLY if your cache partition alone is corrupted, not if the actual paritions are just gone. in that case you'd want to check /dev/block and see the partitions listed, if they are all there as they should be (mmcblk0p25 mmcblk0p26 and mmcblk0p27) you can try and do the same.
hope this helps anyone.
Some things to remember though:
/cache/recovery/command is usually only invoked if your device is not properly rooted (check the numerous droid, evo, desire threads on this, they all had to restore an official RUU and root again to fix)
if there's nothing to mount in /dev/block have a feeling this is related to the emmc not initializing, in which case...
amazinglarry311 said:
okay so i decided to live dangerously and recreate this error on my device. I made sure the cache partition was nice and corrupted and got greeted with this wonderful message:
Now this not the same situation that ALL people are in, but in this situation i opened adb shell and typed
mke2fs /dev/block/mmcblk0p27
reboot recovery
everything back to normal.
Now this is ONLY if your cache partition alone is corrupted, not if the actual paritions are just gone. in that case you'd want to check /dev/block and see the partitions listed, if they are all there as they should be (mmcblk0p25 mmcblk0p26 and mmcblk0p27) you can try and do the same.
hope this helps anyone.
Some things to remember though:
/cache/recovery/command is usually only invoked if your device is not properly rooted (check the numerous droid, evo, desire threads on this, they all had to restore an official RUU and root again to fix)
I have a feeling this is related to the emmc not initializing, in which case...
Click to expand...
Click to collapse
You should make your own thread. I think this will help many people. Great job bro.
Sent from my HTC Desire Z/G2 using XDA Premium App
Hi !
We have to be carefull not to mix two issues here that might look similar to the user.
In both cases the recovery will give an error that it can't mount recovery.
One is that some partitions are corrupted and this can be fixed by recreating the partition as described by amazinglarry above or by reflshing the stock rom.
The second issue is that the emmc chip fails to initialize and in this case nothing can read or write the emmc. You can check if you have this case by booting into recovery and using adb to get a shell. In the shell do a "cat /proc/kmsg | grep mmc0" (i will reformat this tomorrow).
If you see messages that indicate that the emmc did not initialize, then you are in this boat.
There is currently no cure for this, but we try to find what causes this.
have fun - Guhl
Sent from my HTC Vision using XDA App
I'm glad that this issue is being worked on -- no one should have their phone suddenly brick.
Anyways, check out these IRC logs for more context: http://irclog.netripper.com/G2ROOT/2011/4/26/ (start from the middle)
The MyTouch 4G is also having the same problem, I'll be around here looking for solutions as well as maintaining a thread on the myTouch general side.
This happened to a friend's phone. I tired everything to get it fixed (I made a thread but I don't have the link) and ended up returning it to gat another one. What I'm curious about is how do you enter the partition commands? Is recovery (it was cwm 3.0.0.5 btw) able to provide adb access? If so, I was never able to get that and yes, I know how to use adb and have the drivers.
Sent from my HTC Vision using XDA App
I had the same problem. I started a few threads about it as well and posted everything I did (search my username so I dont fill up the thread) and I never got it fixed. Ended up just getting a new phone instead because it seemed like no one really knew much about the error and how to fix it.
SAAADD!
mke2fs /dev/block/mmcblk0p27
reboot recovery
I have this problem (for the second time actually...I was able to fix it the first time by flashing a 2.x.x.x CWM in EBL and formating the cache in that but no such luck the second time I got this error)
Anyhow I tried the above command for all (25/26/27) and it did not fix my issue...I also tried
cat /proc/kmsg | grep mmc0
to test if I have that fail to intialize issue. But it says that isn't a valid command in adb.
Any help? Also I read flashing PMG15.IMG in EBL fixes this but when I tried that I get the Failed PU error!! I think Im screwed huh?
Had same issue. one difference is that I flashed the rom on top of it and my phone bricked completely.
No hboot,no adb , nothingg
Sent from my HTC Desire Z using Tapatalk
I am sorry for opening this thread.
After 2 days of waiting, it seems that the 3G forum section is useless in terms of helping the ones in need.
My issue: after i updated via OTA, the tablet, the 3G stopped working, the OTA corrupted the radio partition, and now it seems that my tablet is on first baseband (a backup radio it seems) released with the device which has some issues (wifi signal very crappy)
In fastboot the baseband appears N/A
My request, if someone knows, on which emmc partition is stored the radio i would be very grateful.
Also a dump of that partition would help also.
I cannot flash the radio via fastboot
apia-1231_0.17.0_1205.img
sending 'radio' (16384 KB)...
OKAY [ 2.001s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.018s
Also trying to dump the partition on the usual mount point results this
dd if=/dev/block/platform/sdhci-tegra.3/by-name/RDO of=/sdcard/RDO.img
/dev/block/platform/sdhci-tegra.3/by-name/RDO: cannot open for read: No such file or directory
In theory i should be able to restore by using the dd on the emmc partitions, but i don`t know which one it is.
ls /dev/block/mmcblk*
ls /dev/block/mmcblk*
/dev/block/mmcblk0 TO BIG
/dev/block/mmcblk0boot0 2.048KB (bootloader)
/dev/block/mmcblk0boot1 2.048KB (bootloader backup)
/dev/block/mmcblk0p1 12.288KB (boot or recovery)
/dev/block/mmcblk0p2 8.192 KB
/dev/block/mmcblk0p3 TO BIG
/dev/block/mmcblk0p4 TO BIG
/dev/block/mmcblk0p5 512KB
/dev/block/mmcblk0p6 10.240KB (boot or recovery)
/dev/block/mmcblk0p7 5.120KB
/dev/block/mmcblk0p8 512KB
/dev/block/mmcblk0p9 TO BIG
In my first look this is what i found, if someone can assist me with this, there are multiple users with this issue, so also others at some moment will be grateful if we fix this.
1) On which partition is the radio stored
2) Can someone dump that partition using dd ?
Again, sorry for creating this post, i don`t usually do things like this (old user, know how the things work around here), but i am a little bit desperate.
Managed to fix partially the issue.
In bootloader the Baseband still appears as N/A
What I did.
1) Mounted radio-tilapia-1231_0.18.0_0409.img
2) Copied the radio_update.zip
3) Rebooted the Tablet in RECOVERY
4) Presse Power Key and Volume Key Plus (first power key, while you keep the power pressed, press the volume key for 2 seconds, release)
5) Select "Apply Update From ADB"
6) Issue the command "adb sideload radio_update.zip
7) Wait till the update goes to end,, and select Reboot system now.
Now when you check in Settings/About Tablet/Baseband, you should have the Baseband which you applied via adb
For those in need, here is the radio_update.zip
http://globula.arctablet.com/Nexus7/radio_update.zip
Still the question remains open, HO KNOWS WHAT PARTITION IS THE ONE FROM THE RADIO ?
Hello
I have exactly the same issue reported by globula neagra.
In my case the issue started just after Nexus came back from Asus repair center with the motherboard replaced. .
As the radio cannot be flashed, the ota procedure fails.
Any idea how to recover the radio partition in order to flash the correct radio image file?
Regards.
My N7 2012 has the same symptoms (Baseband N/A in fastboot) after getting it back from Asus a couple of weeks ago. I believe they replaced the motherboard of my N7 if that matters. I was able to adb sideload the radio from 4.3 then fastboot all factory images from the latest update and then relock. Not sure if I should send it back since it will not install otas on its own, and I will have to adb sideload the radio every update. Thanks op for the info on adb radio update.
Sent from my Nexus 7 using xda app-developers app
My Nexus 7 2012 has the same problem. I could not update OTA and also fastboot update fails, because of Baseband N/A. Now I'm on 4.3 but with old Baseband. I didn't update it, because looks like everything is running.
Before my one was two times in service at Asus. One time they replaced the mainboard.
For sure the solution of globula neagra is a good workaround, but it is very strange that, after the motherboard replacement, you cannot update anymore a standard product with a standard OTA procedure.
Maybe something could be revised in the replacement process.....
flaps1970 said:
For sure the solution of globula neagra is a good workaround, but it is very strange that, after the motherboard replacement, you cannot update anymore a standard product with a standard OTA procedure.
Maybe something could be revised in the replacement process.....
Click to expand...
Click to collapse
UP
Can someone dump that partition using dd, as asked by Globula Neagra?
I don`t understand what exactly you talk about .. radio partitions etc. but if that helps I had a problem with the memory of the tablet: have 32g + gsm N7 and in storage tab it appears only 6gb availabale, so I downloaded nakasig-jwr66y-factory-bdbb7bd7.tgz , extracted the archive and in created folder there was
bootloader-tilapia-4.23.img
flash-all.bat
flash-all.sh
flash-base.sh
image-nakasig-jwr66y.zip
radio-tilapia-1231_0.18.0_0409.img
Using windows 8 I executed in CMD flash-all.bat and the script flashes the radio,bootloader,stock rom and many other things that I did not seen before.I can`t provide a link for download but it is in the forum.I`ll be happy if that can help you solve your problem! Just flash without fear
Blown_ouT said:
I don`t understand what exactly you talk about .. radio partitions etc. but if that helps I had a problem with the memory of the tablet: have 32g + gsm N7 and in storage tab it appears only 6gb availabale, so I downloaded nakasig-jwr66y-factory-bdbb7bd7.tgz , extracted the archive and in created folder there was
bootloader-tilapia-4.23.img
flash-all.bat
flash-all.sh
flash-base.sh
image-nakasig-jwr66y.zip
radio-tilapia-1231_0.18.0_0409.img
Using windows 8 I executed in CMD flash-all.bat and the script flashes the radio,bootloader,stock rom and many other things that I did not seen before.I can`t provide a link for download but it is in the forum.I`ll be happy if that can help you solve your problem! Just flash without fear
Click to expand...
Click to collapse
So it will erase all apps and data on N7?
vndnguyen said:
So it will erase all apps and data on N7?
Click to expand...
Click to collapse
Yes in that case executing the flash-all.bat it will wipe all the data and apps but you can try to manualy flash the radio and the bootloader with that latest version...and like I understand your problem you can`t lose much...still you can`t use your device
@Blown_ouT
I did tried several approaches, and actually what you are saying above broke my device and created the issue with the radio.
The bootloader is saying that my radio partition does not exist anymore, therefore you can not flash something that is not existent, and your method does not work.
Tough, the partition is not vanished it must be there but i think is corrupted somehow.
When i broke the device first time i did this:
1) Update the tablet using the OTA
2) Result was a broken radio
3) Tried to re-flash the tablet using the stand alone pack
-when i did this, i did not wanted to unlock the tablet, still the cmd file runned and erased everything from the tablet but not flashed nothing, which is the most stupid thing since i did not unlocked the device and therefore the restrictions were up (which are supposed to be in theory a non access to erase/write but still google allows you to brick your device with the cmd file without unlocking, but does not allow you to fix it till you unlock it, again VERY STUPID)
-i was able to flash all the files one by one except the radio
globula_neagra said:
@Blown_ouT
I did tried several approaches, and actually what you are saying above broke my device and created the issue with the radio.
The bootloader is saying that my radio partition does not exist anymore, therefore you can not flash something that is not existent, and your method does not work.
Tough, the partition is not vanished it must be there but i think is corrupted somehow.
When i broke the device first time i did this:
1) Update the tablet using the OTA
2) Result was a broken radio
3) Tried to re-flash the tablet using the stand alone pack
-when i did this, i did not wanted to unlock the tablet, still the cmd file runned and erased everything from the tablet but not flashed nothing, which is the most stupid thing since i did not unlocked the device and therefore the restrictions were up (which are supposed to be in theory a non access to erase/write but still google allows you to brick your device with the cmd file without unlocking, but does not allow you to fix it till you unlock it, again VERY STUPID)
-i was able to flash all the files one by one except the radio
Click to expand...
Click to collapse
Hello, just an update about this issue,
I started the RMA procedure and ASUS replaced me the motherboard again (already one had been replaced).
Yesterday i received back the Nexus, nothing had changed, the tablet has exactly the same issue.
At this point, i think there are only three possibilities:
1) all the motherboards used in the Repair center are faulty
2) there is something wrong in the ASUS procedure
3) the problem is not related to the motherboard but is somewhere else
I am very frustrated about this situation, 5 months of tablet and three times in repair center without repairing the issue.
flaps1970 said:
Hello, just an update about this issue,
I started the RMA procedure and ASUS replaced me the motherboard again (already one had been replaced).
Yesterday i received back the Nexus, nothing had changed, the tablet has exactly the same issue.
At this point, i think there are only three possibilities:
1) all the motherboards used in the Repair center are faulty
2) there is something wrong in the ASUS procedure
3) the problem is not related to the motherboard but is somewhere else
I am very frustrated about this situation, 5 months of tablet and three times in repair center without repairing the issue.
Click to expand...
Click to collapse
I do think is an issue on a software level.
Google/Asus don`t want to admit that the updates are "braking" the tablets.
Geez, I have the same problem, I also got my Nex7 GSM from the repair with the new motherboard.
They had one job....
globula_neagra said:
My issue: after i updated via OTA, the tablet, the 3G stopped working, the OTA corrupted the radio partition, and now it seems that my tablet is on first baseband (a backup radio it seems) released with the device which has some issues (wifi signal very crappy)
In fastboot the baseband appears N/A
Click to expand...
Click to collapse
When ASUS replaced my device's motherboard they reinstalled the factory 4.2 instead of the 4.4.4 it was on at the time. During the 4.3 OTA upgrade the device hung and now the baseband is N/A in the bootloader menu. Trying to flash factory images or just the radio itself obviously doesn't work.
Other than your excellent sideload work-around, have you found a proper fix for the radio partition itself?
globula_neagra said:
ls /dev/block/mmcblk*
/dev/block/mmcblk0 TO BIG
/dev/block/mmcblk0boot0 2.048KB (bootloader)
/dev/block/mmcblk0boot1 2.048KB (bootloader backup)
/dev/block/mmcblk0p1 12.288KB (boot or recovery)
/dev/block/mmcblk0p2 8.192 KB
/dev/block/mmcblk0p3 TO BIG
/dev/block/mmcblk0p4 TO BIG
/dev/block/mmcblk0p5 512KB
/dev/block/mmcblk0p6 10.240KB (boot or recovery)
/dev/block/mmcblk0p7 5.120KB
/dev/block/mmcblk0p8 512KB
/dev/block/mmcblk0p9 TO BIG
Click to expand...
Click to collapse
Still the question remains open, HO KNOWS WHAT PARTITION IS THE ONE FROM THE RADIO ?
Click to expand...
Click to collapse
By now it's probably common knowledge to you and others with this problem that when the Nexus 7 3G gets into this state, the radio partition doesn't show up in the list anymore. My tablet broke before I could have a look at what correct partition information looks like, and there isn't much about it on the Internet either. However, these seem to agree:
http://forum.xda-developers.com/showpost.php?p=35103211&postcount=16
http://www.0jl.com/blog/?p=2196
http://forum.xda-developers.com/showthread.php?p=45045265#post45045265
E.g.:
Code:
Device "/ dev / block / mmcblk0p1", the name of "SOS", format emmc, capacity 12M, mount --- storage recovery
Device "/ dev / block / mmcblk0p2", the name "LNX", format emmc, capacity 8M, mount --- storage boot
Device "/ dev / block / mmcblk0p3", the name "APP", format ext4, the capacity of 650M, mount "/ system", the storage system
Device "/ dev / block / mmcblk0p4", the name "RDO", format emmc, capacity 16M, mount --- store radio
Device "/ dev / block / mmcblk0p5", the name "CAC", format ext4, the capacity of 443M, mount "/ cache", storage cache
Device "/ dev / block / mmcblk0p6", the name "MSC", format emmc, capacity 512K, mount --- storage misc
Device "/ dev / block / mmcblk0p7", the name "USP", format, capacity 10M, mount --- storage ---
Device "/ dev / block / mmcblk0p8", the name "PER", format, capacity 5M, mount --- storage ---
Device "/ dev / block / mmcblk0p9", the name "MDA", format, capacity 512K, mount --- storage ---
Device "/ dev / block / mmcblk0p10", the name "UDA", format ext4, capacity 28G, mount "/ data", storage userdata
and
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IOW, compared to grouper the tilapia has an extra 16M radio partition inserted at mmcblk0p4.
Tablets in this state had this partition corrupted or deleted. Would it be correct to deduce that the problem can therefore be fixed by correctly recreating the partition table and then reflashing the machine?
I'm only familiar with working with Windows partitions and haven't been able to find instructions for recreating the Nexus 7 3G's partition table specifically. Is the above information sufficient for doing that, and what commands are needed? My tablet's currently on 4.2.2 and comes with both fdisk and parted.
Thanks in advance,
Francois
globula_neagra said:
My issue: after i updated via OTA, the tablet, the 3G stopped working, the OTA corrupted the radio partition
Click to expand...
Click to collapse
This seems to be the common experience with radio partition corruption. It also seems the process that leads to this corruption could involve a corrupt bootloader.
It turns out that both recent factory images as well as at least the 4.3 OTA for the Nexus 7 3G contain a corrupt bootloader, see http://forum.xda-developers.com/nexus-7/general/info-nexus-7-3g-ota-bootloader-corrupt-t3033513. This means whether Android software is being installed manually or automatically, the target machine is potentially exposed to the corrupt bootloader.
Most firmware installs that include a new bootloader and radio software first install the bootloader, then boot into that, then next proceed with installation of the radio software, and then whatever else.
This opens up the possibility that failure to install and activate the new bootloader contributes to corruption of the radio partition when its upgrade is attempted. If I manage to test this once my machine is returned from repairs I hope to update. Any other thoughts or contributions in the meantime will be appreciated. Especially towards fixing the radio partition.
There are some chinese distributors that accidentally clears your NVRAM when flashing their ROM, thus the phone loses IMEI, MAC and other serials.
There are some methods that fixes this by copying files to data/nvram etc, but that's just a temporary fix, and resets after a wipe.
Here is a proper solution. Windows 10 tested.
Do NOT connect your phone yet. Have it turned off completely.
First you need to install the drivers.
Run
Code:
All MTK USB Driverv.9.2.PDanet.Adb 2015\SmartPhoneDriver\Driver_Auto_Installer_SP_MTK\Driver_Auto_Installer\SmartPhoneDriver\x64 or x86\spinstall.exe [B]WITH Administrator privileges[/B]
Maybe there are some other drivers needed, I don't remember all that I've installed. You will find a lot of drivers in my Google Drive (link at the bottom).
Install SP META, and run it. You need to select AP NVRAM Editor and press Connect.
Now connect the phone, it should detect it, and pop up a window.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Press Read From NVRAM. Browse APDB_MT6795_S01_L0.MP6_W15.32 and press OK on the warning.
WIFI MAC:
SELECT RDEB LID/AP_CFG_RDEB_FILE_WIFI_LID/1 and press Read From NVRAM
aucMacAddress will be your WIFI MAC address. You need to write every 2 character like 0xD0, 0xB3, etc.
Google drive link with everything you need: HERE
does this method work for all mt6795 device? I need to change the imei of my letv x600. Thank you
lala206 said:
does this method work for all mt6795 device? I need to change the imei of my letv x600. Thank you
Click to expand...
Click to collapse
Yes, it should work. You might need a different APDB file, but that should be in the ROM package for your phone.
Xmister said:
Yes, it should work. You might need a different APDB file, but that should be in the ROM package for your phone.
Click to expand...
Click to collapse
thank you for your reply but in the rom package of letv x600, I couldnt find any APDB file. Could you take a look at the rom package in the attachment for me. Thank you!
First try it with my APDB, only if it not works find another.
And it should be in ROM packages that can be flashed with sp flash or fastboot.
lala206 said:
thank you for your reply but in the rom package of letv x600, I couldnt find any APDB file. Could you take a look at the rom package in the attachment for me. Thank you!
Click to expand...
Click to collapse
here is the rom package that can be flashed with sp flash tool. Would you mind taking a look at it again. I wonder if using your file might brick my phone or not. Thanks!
lala206 said:
here is the rom package that can be flashed with sp flash tool. Would you mind taking a look at it again. I wonder if using your file might brick my phone or not. Thanks!
Click to expand...
Click to collapse
I can't see it, you may have to get it from somewhere else then.
It can't brick your phone. This only touches your NVRAM, so make a backup of it, and you are good to go.
i tried this, i lost my imei and all the time i do a factory for install new rom i've to place the mpb file inside nvram folder, but don't work. I can modify the array in IMEI[0] and IMEI[1], i can write it to nvram (and it remains inside) but if i reboot the phone, i have no IMEI :/
EDIT: i tried to flash an nvram backup of a friend with the same smartphone too, i have initially his imei that i can canghe with the mpb metod, but if i try this guide with his backup flashed his imei is not saved into the array IMEI[0] or IMEI[1]...
ILGreat said:
i tried this, i lost my imei and all the time i do a factory for install new rom i've to place the mpb file inside nvram folder, but don't work. I can modify the array in IMEI[0] and IMEI[1], i can write it to nvram (and it remains inside) but if i reboot the phone, i have no IMEI :/
EDIT: i tried to flash an nvram backup of a friend with the same smartphone too, i have initially his imei that i can canghe with the mpb metod, but if i try this guide with his backup flashed his imei is not saved into the array IMEI[0] or IMEI[1]...
Click to expand...
Click to collapse
If the written values remains inside nvram, then it's most probably some modem inconsistency. First of all, don't change the nvram folder on data, it can overrule the changes you made in the real nvram.
And try to flash a stable rom with MI Flash after you have changed the values in your nvram.
Note: I hope you wrote the 2 digits backwards, as I said so.
Xmister said:
If the written values remains inside nvram, then it's most probably some modem inconsistency. First of all, don't change the nvram folder on data, it can overrule the changes you made in the real nvram
And try to flash a stable rom with MI Flash after you have changed the values in your nvram.
Note: I hope you wrote the 2 digits backwards, as I said so.
Click to expand...
Click to collapse
I write the 2 digit backwards, i think i will try to change again the nvram with my value and after that i use Mi Flash, but i've just change the nvram folder, 2 second before i read you're replay :crying: .
ILGreat said:
I write the 2 digit backwards, i think i will try to change again the nvram with my value and after that i use Mi Flash, but i've just change the nvram folder, 2 second before i read you're replay :crying: .
Click to expand...
Click to collapse
Do a factory reset, that resets the nvram folder. Or you can just delete the nvram folder from your data.
Xmister said:
Do a factory reset, that resets the nvram folder. Or you can just delete the nvram folder from your data.
Click to expand...
Click to collapse
Man I LOVE YOU!!! I want you here for a kiss, all permanent restored.
First i delete the folder nvram, then factory reset from twrp.
I wasn't sure than all was deleted, so i flash the fastboot ROM with MiFlash, i change the IMEI with your guide and last i re-flash with MiFlash.
After reboot IMEI were OK, but for another check i pick twrp, reboot, factory reset again and flash last developer Miui EU (.29) and all work like a charm, so really really thank you ^^
Inviato dal mio Redmi Note 2 utilizzando Tapatalk
ILGreat said:
Man I LOVE YOU!!! I want you here for a kiss, all permanent restored.
First i delete the folder nvram, then factory reset from twrp.
I wasn't sure than all was deleted, so i flash the fastboot ROM with MiFlash, i change the IMEI with your guide and last i re-flash with MiFlash.
After reboot IMEI were OK, but for another check i pick twrp, reboot, factory reset again and flash last developer Miui EU (.29) and all work like a charm, so really really thank you ^^
Inviato dal mio Redmi Note 2 utilizzando Tapatalk
Click to expand...
Click to collapse
I'm glad that I cold help.
You can donate something if you wish,but it's up to you
s 5830i gingerbread to s5 mode
After watching your video I updated my galaxy ace 5830i from gingerbread to s5 mode. But I can't make call or receive call or SMS. It shows that invalid imi like that. Please help me I am in trouble . [email protected] is my email adress please reply me with solution. Please I don't want to lose my phone please tell me what should I do now
We can't help you here. Find the forum for your device.
Is it possible to set a custom IMEI this way?
ILGreat said:
Man I LOVE YOU!!! I want you here for a kiss, all permanent restored.
First i delete the folder nvram, then factory reset from twrp.
I wasn't sure than all was deleted, so i flash the fastboot ROM with MiFlash, i change the IMEI with your guide and last i re-flash with MiFlash.
After reboot IMEI were OK, but for another check i pick twrp, reboot, factory reset again and flash last developer Miui EU (.29) and all work like a charm, so really really thank you ^^
Inviato dal mio Redmi Note 2 utilizzando Tapatalk
Click to expand...
Click to collapse
Hi,
I have the same problem with the IMEI.
I tried to use the fastboot, but couldn't find a proper guide how to do it (can't connect the PC to the phone when it is in fastboot mode). can you help me here? is there a step-by-step guide for newbies? can I use the phone ROM update utility instead of the MiFlash? (what is the difference between the two?)?
in addition, I did not fully understand the steps you've done to recover the IMEI. when you write "First i delete the folder nvram, then factory reset from twrp", how did you deleted the folder (using a file explorer like ES file explorer?), what is twrp?
Thanks in advance.
OKup.
he bro iam new this but i really need your help
I need your help bro to sett your programs on my pc is there a way I can contact you privately please?
okup said:
Hi,
I have the same problem with the IMEI.
I tried to use the fastboot, but couldn't find a proper guide how to do it (can't connect the PC to the phone when it is in fastboot mode). can you help me here? is there a step-by-step guide for newbies? can I use the phone ROM update utility instead of the MiFlash? (what is the difference between the two?)?
in addition, I did not fully understand the steps you've done to recover the IMEI. when you write "First i delete the folder nvram, then factory reset from twrp", how did you deleted the folder (using a file explorer like ES file explorer?), what is twrp?
Thanks in advance.
OKup.
Click to expand...
Click to collapse
It should be use TWRP to Root your RN2 then delete NVRAM folder using ES File Explorer.
Dear sir, my Xiaomi redmi note 2 won't start wifi or bluetoot since the OTA update, I have try down grade it, put chinese ROM and back again to global ROM, flash it, etc but none of it working, I have read your post about reinstall driver for wifi and bluetooth on NVRAM, but your step not work on my computer, can u help me please?
Here is report from spinstall.exe
C:\Users\Double Click\Desktop\All MTK USB Driverv.9.2.PDanet.Adb 2015\SmartPhoneDriver\Driver_Auto_Installer_SP_MTK\Driver_Auto_Installer\SmartPhoneDriver\x86\Infs\usbvcom.inf--->
there are no matching devices in the device tree
C:\Users\Double Click\Desktop\All MTK USB Driverv.9.2.PDanet.Adb 2015\SmartPhoneDriver\Driver_Auto_Installer_SP_MTK\Driver_Auto_Installer\SmartPhoneDriver\x86\Infs\usbvcom_brom.inf--->
there are no matching devices in the device tree
=====Operation Succeeded=====
File Closed.
and here the error warning from SP meta tool
Search Kernel USB COM port time out!
please help me
Please help
Can anyone give me qcn file for ze550kl Z00L
My imei is lost
It's just a small file
Pleaze help pleaze
https://drive.google.com/file/d/0B_D6S6CoxAwEaW9tUVNuSEJycTg/view?usp=drivesdk
Link to QCN file.
Search for 1111111111111111 - SIM 1 IMEI & 1111111111111112 - SIM 2 IMEI
and replace with yours in correct format.
Just for info my device is ZOOL 3GB/16GB Snapdragon 615 variant.
Sent from my ASUS_Z00LD using Tapatalk
aadi50 said:
https://drive.google.com/file/d/0B_D6S6CoxAwEaW9tUVNuSEJycTg/view?usp=drivesdk
Link to QCN file.
Search for 1111111111111111 - SIM 1 IMEI & 1111111111111112 - SIM 2 IMEI
and replace with yours in correct format.
Just for info my device is ZOOL 3GB/16GB Snapdragon 615 variant.
Click to expand...
Click to collapse
thanks a lot bro
For file
But unfortunately it doesn't worked for me
aadi50 said:
https://drive.google.com/file/d/0B_D6S6CoxAwEaW9tUVNuSEJycTg/view?usp=drivesdk
Link to QCN file.
Search for 1111111111111111 - SIM 1 IMEI & 1111111111111112 - SIM 2 IMEI
and replace with yours in correct format.
Just for info my device is ZOOL 3GB/16GB Snapdragon 615 variant.
Click to expand...
Click to collapse
also
When i try to find ur imei
i.e
111111111111111
In hex format
It says no string found
I am using
Ultra edit
And imei converter
addy692 said:
also
When i try to find ur imei
i.e
111111111111111
In hex format
It says no string found
I am using
Ultra edit
And imei converter
Click to expand...
Click to collapse
I rechecked and its fine. I can search it.
Are you trying to convert "1111..." before searching.
If yes then dont. Directly search for "1111..." in editor.
Its a random nmbr i put just as a placeholder only...
Just convert your imei only before replacing in file.
aadi50 said:
I rechecked and its fine. I can search it.
Are you trying to convert "1111..." before searching.
If yes then dont. Directly search for "1111..." in editor.
Its a random nmbr i put just as a placeholder only...
Just convert your imei only before replacing in file.
Click to expand...
Click to collapse
oh ok
I will try
I was converting 1111
:good:
thnku
HELP!!
Please someone have a QCN for Ze550kl(Z00L 2GB RAM) ??
I've hard bricked my phone with 9008, and 9006.. I managed to make it come back to life, but I'm with the 2 IMEI null, and I can not find on the net any QCN for the model of my cell phone, The QCN above its MSM8939 and I need MSM8916 please somebody help me. :crying::crying:
kensk8 said:
Please someone have a QCN for Ze550kl(Z00L 2GB RAM) ??
I've hard bricked my phone with 9008, and 9006.. I managed to make it come back to life, but I'm with the 2 IMEI null, and I can not find on the net any QCN for the model of my cell phone, The QCN above its MSM8939 and I need MSM8916 please somebody help me. :crying::crying:
Click to expand...
Click to collapse
bro did you manage to get the qcn file?
Leelka said:
bro did you manage to get the qcn file?
Click to expand...
Click to collapse
No, unfortunatelly. I'm with my phone until today with IMEI Null, I've tried hardly to find on net but with no success at all. :/
kensk8 said:
Please someone have a QCN for Ze550kl(Z00L 2GB RAM) ??
I've hard bricked my phone with 9008, and 9006.. I managed to make it come back to life, but I'm with the 2 IMEI null, and I can not find on the net any QCN for the model of my cell phone, The QCN above its MSM8939 and I need MSM8916 please somebody help me. :crying::crying:
Click to expand...
Click to collapse
I fixed the imei of my MSM8916 with the qcn above.
igorfs10 said:
I fixed the imei of my MSM8916 with the qcn above.
Click to expand...
Click to collapse
But which are your Zenfone? same than mine?
Z00L 2GB Ram, 4 core, 16GB emmc ?
if yes, how you do?
is possible tell me all the steps do you follow, cuz I'm with many problems with this device, I cannot install any custom roms in it.. I've tried and always get stuck on boot waiting more than 40 mins to boot up and nothing happens, I'm with the IMEI and S/N lost (IMEI "null") and S/N with a ramdom number like 29880ed3 something like this.. I've tried to install custom roms but nothing happeans, tried 6 CR and all get on stuck bootloop, I get unlocked bootloader as ask in steps, cleaned all "wipe, dalvik, data and system" clean install with lastest twrp and stucks on boot.. anyway if its possible to help me I appreciate.
Thanks for now;
kensk8 said:
No, unfortunatelly. I'm with my phone until today with IMEI Null, I've tried hardly to find on net but with no success at all. :/
Click to expand...
Click to collapse
Surprise, i can help you.
https://drive.google.com/file/d/1-9fo7TBwygrDHipjB3271qVpP_EBszjv/view?usp=sharing
Enjoy . :good:
Leelka said:
Surprise, i can help you.
https://drive.google.com/file/d/1-9fo7TBwygrDHipjB3271qVpP_EBszjv/view?usp=sharing
Enjoy . :good:
Click to expand...
Click to collapse
Man I appreciate a lot for ur help, but unfortunatelly this QCN if I put, it will brick my phone again on bootloop cuz this qcn model is for MSM8939, as well my phone is MSM8916
But I really thank you.
kensk8 said:
But which are your Zenfone? same than mine?
Z00L 2GB Ram, 4 core, 16GB emmc ?
if yes, how you do?
is possible tell me all the steps do you follow, cuz I'm with many problems with this device, I cannot install any custom roms in it.. I've tried and always get stuck on boot waiting more than 40 mins to boot up and nothing happens, I'm with the IMEI and S/N lost (IMEI "null") and S/N with a ramdom number like 29880ed3 something like this.. I've tried to install custom roms but nothing happeans, tried 6 CR and all get on stuck bootloop, I get unlocked bootloader as ask in steps, cleaned all "wipe, dalvik, data and system" clean install with lastest twrp and stucks on boot.. anyway if its possible to help me I appreciate.
Thanks for now;
Click to expand...
Click to collapse
Same model ze550kl, 2gb ram, 1.2 ghz quad core.
You need to use an hex editor and imei converter. Use your imei in imei converter and search in hex editor for bytes 1111111111 and overwrite it with your imei converted. Do the same thing with second imei, but this time you have to search for 1111112. There is a software that can change sn but i cant remember. When i have more time i ll make a better tutorial explaining how to use this qcn if needed.
kensk8 said:
Man I appreciate a lot for ur help, but unfortunatelly this QCN if I put, it will brick my phone again on bootloop cuz this qcn model is for MSM8939, as well my phone is MSM8916
But I really thank you.
Click to expand...
Click to collapse
Well you are saying cuz at the time of inserting the file in qpst to restore, it will show like this is not for this model.? Ignore it. Cuz i got it too and ignored it and restored. Voila it worked.
igorfs10 said:
Same model ze550kl, 2gb ram, 1.2 ghz quad core.
You need to use an hex editor and imei converter. Use your imei in imei converter and search in hex editor for bytes 1111111111 and overwrite it with your imei converted. Do the same thing with second imei, but this time you have to search for 2222222222. There is a software that can change sn but i cant remember. When i have more time i ll make a better tutorial explaining how to use this qcn if needed.
Click to expand...
Click to collapse
Ok then. Thanks
Leelka said:
Well you are saying cuz at the time of inserting the file in qpst to restore, it will show like this is not for this model. Ignore it. Cuz i got it too and ignored it and restored. Voila it worked.
Click to expand...
Click to collapse
Ok man I'll try it then, thank you
kensk8 said:
Ok then. Thanks
Ok man I'll try it then, thank you
Click to expand...
Click to collapse
Download 00000000.qcn from aadi50 post
Download HxD https://mh-nexus.de/en/downloads.php?product=HxD
Download IMEI Converter
1 - Open IMEI Converter
2 - Put your IMEI and click on "Convert IMEI"
3 - Copy the number after "08"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4 - Open HxD and open 00000000.qcn in HxD.
5 - Go to "Search > Find"
6 - In the "Search for" box put "1111111111111111"
7 - Change "Datatype" to "Hex-value" and change "Search direction" to "All" and press the "Ok" Button
8 - HxD will select the 1111111111111111
9 - Now click with right mouse button right before the first number 1 and select "Paste write" to paste the converted IMEI without "08"
10 - Do the same thing for IMEI 2 But Search for "1111111111111112" in HXD and use your second IMEI
11 - Now save the qcn file in HXD and flash it with qpst
Now you have the right IMEI in your cellphone.
Dont forget to do a factory reset.
I hope it works for you.
igorfs10 said:
Download 00000000.qcn from aadi50 post
Download HxD https://mh-nexus.de/en/downloads.php?product=HxD
Download IMEI Converter
1 - Open IMEI Converter
2 - Put your IMEI and click on "Convert IMEI"
3 - Copy the number after "08"
4 - Open HxD and open 00000000.qcn in HxD.
5 - Go to "Search > Find"
6 - In the "Search for" box put "1111111111111111"
7 - Change "Datatype" to "Hex-value" and change "Search direction" to "All" and press the "Ok" Button
8 - HxD will select the 1111111111111111
9 - Now click with right mouse button right before the first number 1 and select "Paste write" to paste the converted IMEI without "08"
10 - Do the same thing for IMEI 2 But Search for "1111111111111112" in HXD and use your second IMEI
11 - Now save the qcn file in HXD and flash it with qpst
Now you have the right IMEI in your cellphone.
Dont forget to do a factory reset.
I hope it works for you.
Click to expand...
Click to collapse
dude really good work u've done, thanks for tutorial and for ur time for made it, I'll try follow this steps I think that now its possible to recover my IMEI
Have u something to recover others things, I mean Serial Numbers in that case, to recover my phone SN, it was with unknow number, like 28779dc2 and lost it SN for Bluetooth and Wifi too, and now I've got a error too in TWRP "Error /factory mount" and same to try it on flash any Custom Rom, I don't know if cuz this missing SN or error on /factory, cuz I do all steps requested on Customs, Unlocked Bootloader, lastest update asus Ze550kl v.2196 stock rom, I've tried clean everything too for a clean install, tried delete 3 folders after flashed a custom rom in /system/etc/firmware "modem folders" as sugest on another post here in forum, nothing work for me :/
tried all variable customs possible like, based on all versions, 8.0, 7.0, 6,0 as dotOS, Rescurrection Remix, LineAge OS, and with old Cyanogen based 13.1, 14.1, and 15.1 Nothing work on my phone.. I'm very sad :crying:
Anyway I really appreciate ur help guys!
PS: Sorry if have some errors in my English (Brazilian).
There is a software called IMEI & SN writer
https://forum.xda-developers.com/cr...repair-corrupted-invalid-imei-signal-t2927078
You can use it to change sn, imei, bt and wifi mac address to fix this.
For the factory i had the same problem after downgrading to an older lp version. To fix it i had to flash an old asus test version using emmc raw flash tool, after i had to flash the qcn again, flash the asus stock rom and unlocked bootloader again to flash custom rom. Its an extreme dangerous process that can kill your phone. I cant remember now all the steps i had used in this, and i dont want to kill my phone to try. I can boot every custom rom but sometimes i have some issues with bt and wifi on most of oreo roms that are not based no luks lineage.
Ps: Br here too.
A thread for everyone from everyone! Noob friendly and a home for every newcomer!
Thread rules:
1. Respect xda rules regarding conduct. (Rule no. 2 here)
2. All questions allowed by xda rules are welcomed.
3. Your questions must show that you want to learn. No one will criticize you because you are trying to learn.
4. Ask politely no matter how desperate you might be.
5. Do not post or request warez. XDA rule 6 here.
6. There are no bad questions, but only bad intentions and bad answers.
7. Don't use this thread as an excuse to ask all kinds of questions everywhere in the forums, especially in development threads. This is why this thread is for.
8. For all who want to help, do that kindly according to the rule 2.3 of xda
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Work In Progress
Android related questions
Q: What is a smartphone?
A: ... just kidding, you are way past that!
Q: What is an android ROM?
A: Android Read-Only Memory. A file containing the Android operating system and its apps. The "stock ROM" comes preinstalled on the phone.
Q: What is a custom ROM?
A: A custom ROM replaces your device's preinstalled Android operating system (or Stock ROM), normally stored in read-only memory, with a new version of the Android operating system.
Q: What is a kernel in android?
A: A kernel is the component that helps the applications communicate with the hardware. It manages the system resources, communicates with external devices when needed, and so on. Android uses a variation of the Linux kernel. The kernel is the bridge between the ROM and hardware.
Q: Rooting-What is it?
A: Rooting is the process of allowing users to attain privileged control (root access) over various Android subsystems. As Android uses the Linux kernel, rooting an Android device gives similar access to administrative (superuser) permissions as on Linux. Rooting gives the ability (or permission) to alter or replace system applications and settings, run specialized applications that require administrator-level permissions, or perform other operations that are otherwise inaccessible to a normal Android user.
Q: What is a recovery in android?
A: In Android, recovery refers to the dedicated, bootable partition that has the recovery console installed. It is accessible with a combination of key presses, or instructions from a command line.
Q: What is Stock Recovery?
A: The Recovery that comes with your Android Device from the manufacturer is called Stock Recovery. Stock recovery can be used to flash updates from an update.zip file, OTA Updates, for factory reset etc.
Q: What is a Custom Recovery?
A: From stock recovery, we cannot flash Custom ROMs, Modules etc. For this, you need to flash custom recoveries like TWRP. Flashing a custom recovery overwrites the system recovery. Custom Recoveries have been coded to allow for backup and restore functions, selective deletion of data so you don't have to wipe everything, and modified to allow update packages that have not been digitally signed by official sources.
Q: What does TWRP stand for?
A: Team Win Recovery Project.
Q: What does OTA stand for?
A: Over The Air Update. An OTA Update is a software update that is distributed via Wi-Fi or broadband network, making use of functions built into the operating system itself.
Note:
Noobs and newcomers: If someone answers you and the answer is helpful to you, press the "thanks" button for that person. It's a polite thing to do in the forums and saves you from creating a post just to say "thanks".
And remember: there are those that are noobs and those that were noobs!
Credit: Google.com for helping me to search, select, format and prepare some of the answers for easy reading.
Thanks for doing this. Been thinking of making one myself but you beat me to it. I'll help you out with answering whenever I can.
joeyhuab said:
Thanks for doing this. Been thinking of making one myself but you beat me to it. I'll help you out with answering whenever I can.
Click to expand...
Click to collapse
Welcome on board!
Now that is a good thread, I do really hope people would ask here now instead of making separate threads.
Xadus said:
Now that is a good thread, I do really hope people would ask here now instead of making separate threads.
Click to expand...
Click to collapse
We can ask the moderators to make this thread a sticky. So it will be always visible.
My device is rooted. I m use substratum in my device.. I m using a theme in substratum for 2 week ago but today I try to install & apply a new one but once I did that my device itself restart & Showing me a message " Android system load failed.. Your Data maybe corrupted , Please do a reset factory " but I want to back my device without loosing my data... What can I do. Please anyone help me..This is error
shafayetsabbir3 said:
My device is rooted. I m use substratum in my device.. I m using a theme in substratum for 2 week ago but today I try to install & apply a new one but once I did that my device itself restart & Showing me a message " Android system load failed.. Your Data maybe corrupted , Please do a reset factory " but I want to back my device without loosing my data... What can I do. Please anyone help me..This is error
Click to expand...
Click to collapse
Substratum creates a folder in your internal sd card with a flashable file that you can rescue your system.
Boot your phone into twrp if you have one and flash that file.
If you don't have a recovery installed, than just boot into a recovery and again flash that file.
Is there any way to resolve this issue of feb patch not getting installed
ragav_lithun said:
Is there any way to resolve this issue of feb patch not getting installed
Click to expand...
Click to collapse
Can you please give some more details? How are you installing the february patch?
Did you root your phone? Can you take a screenshot of the problem and upload it here?
varben said:
Substratum creates a folder in your internal sd card with a flashable file that you can rescue your system.
Boot your phone into twrp if you have one and flash that file.
If you don't have a recovery installed, than just boot into a recovery and again flash that file.
Click to expand...
Click to collapse
I have twrp installed bro.. What to do now?
shafayetsabbir3 said:
I have twrp installed bro.. What to do now?
Click to expand...
Click to collapse
Boot into twrp, find the folder substratum in your internal sd card and flash the rescue zip file. (Or uninstall, can't remember the exact name of the file)
I've bought a dux ducis flip cover. Any advice on how to turn on/off screen when open/close cover?
edgardurao said:
I've bought a dux ducis flip cover. Any advice on how to turn on/off screen when open/close cover?
Click to expand...
Click to collapse
Is it a smart flip cover? Link to the product details?
Hello..
I love xperia sound enhancement instead of viper or atmos.
my question are:
1. have you try installing such as mod on Mia1? is it applicable on oreo?
2. do you have any mod version recommended for mia1?
3. i'd love if it's magisk friendly any suggest?
thanks in advance for the answer..
varben said:
Is it a smart flip cover? Link to the product details?
Click to expand...
Click to collapse
Well I think it is: https://m.pt.aliexpress.com/item/32...32835263750&shortkey=bUvYjAfQ&addresstype=600
Any ideas?
varben said:
Boot into twrp, find the folder substratum in your internal sd card and flash the rescue zip file. (Or uninstall, can't remember the exact name of the file)
Click to expand...
Click to collapse
bro r u sure it will work?
For now I don't have twrp install in my device but I will boot twrp but if I found no rescue file in substratum folder then?
edgardurao said:
Well I think it is: https://m.pt.aliexpress.com/item/32...32835263750&shortkey=bUvYjAfQ&addresstype=600
Any ideas?
Click to expand...
Click to collapse
That doesn't look like a smart cover. So you can't use it to turn screen on/off by opening and closing the cover.
Sorry!
shafayetsabbir3 said:
bro r u sure it will work?
Click to expand...
Click to collapse
Can you try it? It's safe to do it.
varben said:
Can you try it? It's safe to do it.
Click to expand...
Click to collapse
Ok bro... I will try that tomorrow.. If it work then u save my life.. Actually there is lots of important data which I don't wants lose..
many people have faced with proximity sensor issue on devices such as redmi 3s, redmi note 3, note 4, redmi 4x, mi a1 and others ... the problem occurs when incoming calls, but xiaomi does not respond ... can someone look at the logs and fix this? Can someone help?
http://c.mi.com/thread-517279-1-1.html
http://c.mi.com/thread-294939-1-1.html
http://en.miui.com/thread-1341151-1-1.html
there's so many proximity sensor bug reports. Why does no one want to solve this problem? I have two devices (Mi a1, Redmy note 3 pro) with an incorrectly working proximity sensor.