Hi there, I'm new here and I need your help.
My ViewPad7 haven't an original <3e> recovery because i get it from another and it run cooked rom.
Now i want to back to the stock rom following here: http://forum.xda-developers.com/showthread.php?t=1601117 but it need an original <3e> recovery.
Could you kindly help me to get it, if you have a backup of original <3e> recovery from your ViewPad7, please send it for me.
Or you can backup your stock recovery follow this guide: http://forum.xda-developers.com/showthread.php?t=1015005 then help me.
Thank you so much. Sorry for my English.
Anyone, please help?
For Vpad7 - do you have the "older" non-ITE or "newer" ITE (multi-touch) screen - original/stock recovery image file or whatever?
If you aren't sure - post your Vpad7's production date, which is on the printed label on the back as that should help ...
I don't know about the 'non-ITE' or ITE screen of my device. Its production date is: 28-4 2011
Please help me!
Thanks Letitride
Based on device's production date, it's "most" likely an ITE device (there is nothing certain or definitive about it ...)
Okay, calvary to the rescue for fellow XDA's.
AS - please check your PM too (you got mail ...)
Letitride said:
Based on device's production date, it's "most" likely an ITE device (there is nothing certain or definitive about it ...)
Okay, calvary to the rescue for fellow XDA's.
AS - please check your PM too (you got mail ...)
Click to expand...
Click to collapse
I'm having the same problem here. Letitride can u help me out also?
Lanfear28 said:
I'm having the same problem here. Letitride can u help me out also?
Click to expand...
Click to collapse
Have you read the following thread & try it to see if you can restore your device ?
http://forum.xda-developers.com/showthread.php?t=1601117
If not or it failed, please be a little more specific about your issues and error messages/description of bootup problem, etc. ?
sadonsu assailants
I have the cwm recovery and cant get back the original <3e> recovery to flash the original Viewsonic firmware(v3_420)
@Letitride
Works like a charm
Lanfear28 said:
I have the cwm recovery and cant get back the original <3e> recovery to flash the original Viewsonic firmware(v3_420) @Letitride ... Works like a charm
Click to expand...
Click to collapse
Restored & working w the "alternative" *.img as referenced in PM then, excellent & enjoy the Vpad7 - only wished it's a bit faster, overclocking or whatever. But, it is what it is and loved the 7" factor, much easier to slip into a pouch, pocket, jacket, etc. to take along.
Is there anybody with original Viewsonic firmware(v3_420) and with working internet thru mobile data?
i got the viewpad7 back to original with stock recovery that i extracted it from stock rom, thanks
Hello, sorry for bumping this thread but it is relevant to what I need.
EDIT: Moving to thread for visibility.
I recently rooted my Viewsonic Viewpad 7 and put on a custom ROM. I noticed that wifi was not working so I tried some fixes, which none of them worked. One of those fixes involved formatting the sd card. After formatting, I realized I made a huge mistake as my backups are now all gone.
So I have the clockwork recovery installed (v5.0.2.6) and I think it is causing problems. I tried using Software Update Tool L3 (SUT L3) in order to restore the firmware back to normal using the .nbo from the Viewsonic site but I think I need the original <3e> recovery. Whenever I try to recover using the tool, it reboots the device into Recovery mode and after a few minutes I get the error:
Error Code: 0xc60e
Error: Download fail,
Error = SE_ERR_SUT_DETECT_DEVICE_FAIL (0xC60E).
I believe this is because it is expecting the original 3e recovery and doesn't recognize the clockwork recovery. I tried to find a copy of the original recovery.img but I can't find it online anywhere. This thread is the closest I've gotten. Please let me know if there is anything I can do to fix this. Or if anyone has a copy of the original 3e recovery, it may help me out.
Thanks!
FTM Mode Info:
SWVer=3.240
MODEL:FM6-0001
HWVer:107
clandor said:
... rooted my Viewsonic Viewpad 7 and put on a custom ROM ... So I have the clockwork recovery installed (v5.0.2.6) and I think it is causing problems. I tried using Software Update Tool L3 (SUT L3) in order to restore the firmware back to normal using the .nbo from the Viewsonic site but I think I need the original <3e> recovery. Whenever I try to recover using the tool, it reboots the device into Recovery mode and after a few minutes I get the error:
Error Code: 0xc60e
Error: Download fail,
Error = SE_ERR_SUT_DETECT_DEVICE_FAIL (0xC60E).
I believe this is because it is expecting the original 3e recovery and doesn't recognize the clockwork recovery. I tried to find a copy of the original recovery.img but I can't find it online anywhere. This thread is the closest I've gotten. Please let me know if there is anything I can do to fix this. Or if anyone has a copy of the original 3e recovery, it may help me out.
FTM Mode Info:
SWVer=3.240
MODEL:FM6-0001
HWVer:107
Click to expand...
Click to collapse
Are you using the "correct" factory *.nbo file with SUTL3 (which ver.) as it looked like your model is likely an ITE (newer) model ?
Can you boot the device into CWM Recovery mode now? Does it start up with the VS Android boot animation?
I will have to look for my backups as I've them on a backup server somewhere and/or in cloud storage ... will look & see what I have?
Haven't flash/done any factory restoration work on the Vpad7 in over a year+ now but, as I recall, flashing the *.nbo file via the PC with the factory update utility will wipe the device clean and restore it to factory fresh, locked mode so it should NOT matter what recovery you have on the device now.
Please describe in greater details the steps you took in trying to restore ... it's still a joy to go back to the Vpad7 but hard to let go of the new Nexus 7 quad-core "toy" these days for me ...
Thank you for your help.
I am pretty sure it is an ITE model. It's HWVer is 107, and I used this thread to help figure that out.
I downloaded firmware (.nbo) v3_420 and v3_62 from here. (Under Downloads > Drivers)
Here are the steps I took in order to try and restore.
I started off by enabling USB debugging and plugging in the tablet.
I opened up SUTL3 v1.7.9 and selected one of the firmwares (both yield same result). The update option I set to Erase user data. Once I hit next, it says Updating the Phone software, please wait.
The device restarts into recovery mode. The recovery menu title says CWM-based Recovery v5.0.2.6 which is a custom one I changed. I do not know how to get it back to the original as I have lost the backup.
After about a minute or so, I get
Error code: 0x4000
Error: Download fail,
Error = DEVICE_NOT_CONFIGURE (0x4000).
At this point when I retry using SUT L3 without leaving the recovery mode, I will only get the error from the previous post.
I'm not sure what my options are but my goal is to get back to the original ROM or get wifi working again on the current ROM. The current ROM I am using is CleanView Ice v1.3. I tried both the ITE version and non-ITE version and there seems to be no difference.
The only thing I seem to be able to do is Install ZIP from sdcard which lets me switch between custom ROMs but it doesnt fix the wifi problem or let me go back to original.
---
Edit: I tried doing the same thing a few more times with my antivirus disabled and it's still the same.
Also, I'm not sure if this will help at all but I tried to use the Synchronization tool that shows up on the PC when plugging in the device. It gave me the error "Can't access data on handheld! Please check the connection between desktop and handheld and at least enter Contacts once if you just clear your data!" These may be related as I have accessed Contacts and even added one in to test and this error comes up every time.
Maybe some kind of driver problem?
clandor said:
I am pretty sure it is an ITE model. It's HWVer is 107, and I used this thread to help figure that out.
I downloaded firmware (.nbo) v3_420 and v3_62 from here. (Under Downloads > Drivers) ... Maybe some kind of driver problem?
Click to expand...
Click to collapse
Okay, let's see - yours is ITE (UK-based) and running the same firmware as mine (USA) and v3_62 will work too, mine is on v3_420.
You still have working CWM 5.x on your device and can boot into it (small pin hole on the button to reset, etc.)
Okay, a # of points - the SUTL3 is run from the PC together with the *.nb0 file - running Windows XP or Vista, go the Command Prompt - Vpad7 drivers are already installed, give it a try - does it work as that will restore it to factory state - it should not need the Stock Recovery to flash it (I could be mistaken as it's been a while) Unpack the Zip file so that the utility will read the *.nb0 file directly.
First suggestio, however, is that if you have working CWM - my recommendation would be to flash from custom recovery, EUv1.7-ITE firmware in Zip file format - as linked here in Dropbox account of mine, OP/developer's link is no longer accessible or available. https://dl.dropbox.com/u/64025118/EUViewpad7v1.7b-ITE.zip
Download & transfer to mSD card, reboot into CWM, wipe dalvik cache, cache & system/full reset - then, flash the zip file and it should be done in about 10 minutes, be patient and go thru the Setup - if all goes well, your ITE device is back to life again. This is my preferred ROM and WiFi works well, if necessary - do a Master Reset again from the running Rom if necessary, reboot once & then setup your WiFi again.
Turn-off Antivirus & Firewall on the PC while flashing ... let me know whether you can get into the EU Rom as it will save you the extra work of going stock and rooting, etc. if your original challenge was just trying to get a good WiFi signal.
The previous times that I tried to install the .nbo files with SUT L3, I extracted them from the zip.
Also, I got firmwares on the UK site but I am Canadian. Most likely mine is also USA-based as many of our electronics are. I just could not find the files on the USA site.
I am running Windows 7 so some drivers installed automatically. I did use Setup.exe to install some other drivers but I have noticed no difference between the two times. Running setup.exe doesn't install anything anymore.
--
Here are the steps I took after your post:
I first transferred EUViewpad7v1.7b-ITE.zip to the microSD card and after rebooted into CWM-based Recovery. I wiped Dalvik cache, cache and "data/factory reset". I then flashed the .zip file and restarted the device after it finished loading.
I noticed the new intro logo so it seems switching the new ROM was a success.
I went into wireless and network settings and I turned on Wifi in the Wifi settings. The device scans for networks for about 30 seconds, then stops and displays "Unable to scan networks" and turns off.
I know for sure there are networks in the area and the wifi was working before I swapped to another ROM.
This is where I am currently stuck.
Again, thank you for your help.
clandor said:
... Most likely mine is also USA-based as many of our electronics are. I just could not find the files on the USA site. I am running Windows 7 so some drivers installed automatically. I did use Setup.exe to install some other drivers but I have noticed no difference between the two times. Running setup.exe doesn't install anything anymore.
--
Here are the steps I took after your post:
I first transferred EUViewpad7v1.7b-ITE.zip to the microSD card and after rebooted into CWM-based Recovery. I wiped Dalvik cache, cache and "data/factory reset". I then flashed the .zip file and restarted the device after it finished loading. I noticed the new intro logo so it seems switching the new ROM was a success.
I went into wireless and network settings and I turned on Wifi in the Wifi settings. The device scans for networks for about 30 seconds, then stops and displays "Unable to scan networks" and turns off. I know for sure there are networks in the area and the wifi was working before I swapped to another ROM. This is where I am currently stuck ...
Click to expand...
Click to collapse
Great, that's major progress - first, let's check & verify a few things and do it step-by-step:
Go to Settings - About phone - check that the following is same or similiar (they should be identical or almost)
Android 2.2.2
Baseband PR3.7_125
Kernel version Apps_2.6.32.9
Build number 4027_3_420
Check under Mobile network settings -
Data enabled (it should NOT matter, only if you are using a Sim card for voice and/or data in Canada)
Under WiFi settings -
WiFi - enabled, cycled it OFF and ON again, does it see various open and/or secured networks nearby
If NOT, press the soft "Menu" key on the lower right (in landscape mode) - it should open up & show "Scan" & "Advanced"
Can you do a manual "Scan" - make sure you have a known working WiFi, either secured or open (McDonalds/Starbuck or public library, etc.)
Next - open "Advanced"
Wi-Fi sleep policy (mine is set to "Never when plugged in" - try to temporary set it to "Never" for this purposes
MAC address - the unique ID for your device should be shown
Tap the WiFi network that you wanted to connect to - check its setting/status for Security, Signal strength, Link speed & IP address
If it previously connected but no longer worked, press "Forget" to delete it, and when it attempt to reconnect (if it is a secured one) - re-enter the password to see if you can connect.
For your restoration purposes, you might want to use WEP or WPA instead of WPA2, or even temporary changed your router to an "Open" WiFi so that any devices including the Vpad7 nearby can connect insecurely, assuming that your router is assigning DHCP automatically and giving out its IP address.
If NONE of these steps are working still, go back into WiFi settings and manually delete any and ALL saved stored networks (named) on the device, leaving just "Add Wi-Fi Network" as the only option.
Next, run a TB backup of your Apps if necessary and boot back into CWM, and do a Backup first to your mSD card (and cover it to a PC if necessary, as you can always restore it back instead of going thru flashing & Set-up) and you will have working boot.img (kernel) saved along with system, etc.
Exit and boot back to ADB (Android) Go to Settings - Privacy setting, and hit "Factory data reset" - next go first into CWM again, wipe dalvik cache & cache again, then continue with regular Setup including WiFi - your device should be able to pickup a nearby & strong WiFi signal.
If all these are still not working, you will likely need to get to a PC or laptop, earlier users had reported having issues with Win7 OS running, I would recommend borrowing/using one with Vista or XP-SP3 running, make sure the USB device drivers are automatically installed first and that it recognize the device. Then, reconnect and run SULT3 and flash the factory *.nb0 file - as I also suspect that there might be other hidden USB device drivers on your existing Win7 system that's casuing the *.nb0 installation to fail.
Keep me posted on your progress and any error messages or crashes (FC) encountered.
(Apparently, some of the custom Roms ended up "corrupting" the WiFi settings and codes, leaving residual settings that casued it to stop connecting to WiFi's - if you look & check some of the posting under "Development" (for some of the Rom's) - you will see some discussions about it. The EUv1.7 custom Rom (non-ITE was initially done and ITE later on) is among the better ones with few WiFi issues to speak of, 15+ months later, still relatively bug-free and updated all the Apps and add-ons of my own from Google Market (Play Store) automatically, with working Flash Player patched, and Angry Birds happily running along - the CPU is slow but with App2SD helping, not too bad for a device running Android 2.2.2 (Froyo)
I checked the settings in the About section and they are identical to the ones you posted.
I left Data enabled however I haven't inserted a SIM card throughout this whole process. I have no data plan anyways with the current SIM card I am going to put in.
Under the advanced settings in Wifi, I changed the sleep policy to Never and the MAC address says "Unavailable". So far there is still no result. I will try connecting in an area where I know there are open networks later today as I live in a public house where I have no access to the router's settings.
Also just a note about cycling Wifi ON and OFF, it automatically turns off after the message "Unable to scan for networks" shows up and no networks actually show up in the Wifi Networks section throughout the whole process. It stays empty even though there are networks around.
There are currently no stored wifi networks either so Add Wi-fi Network is the only option. I recieved this device from someone recently and I completely formatted the mSD card to start fresh so losing any sort of data is no problem to me.
---
I used the backup option in CWM to create another backup and after that I backed up the mSD card through USB to keep the working boot.img and other stuff onto the PC.
Under privacy settings I selected Factory Reset and let the device do its thing. I noticed the intro looked like normal however the Android's "theme" is still like the EUv1.7. I went into CWM and did a dalvik cache wipe along with a cache wipe and reset the device.
I tried the wifi again at this point and still no change.
I also tried SUT L3 with the .nbo and I yeild the same errors as before (0x4000 first time when using from Android screen, 0xC60E after the first time when using SUTL3 without leaving recovery mode).
--
I will test open wifi later today and I will edit the result. I'll also take a look at the discussion on wifi not working around the development forum. Thank you.
---
Edit:
I tested it out on some wifi networks without any protection and still none showed up.
I also noticed that if you right-click the Setup.exe icon in the taskbar after plugging in the Viewpad 7 it gives you the option to uninstall everything that the setup installed. I tried uninstalling and running SUT L3 but there was no difference. Also no difference after reinstalling, just so you know.
clandor said:
I started off by enabling USB debugging and plugging in the tablet.
I opened up SUTL3 v1.7.9 and selected one of the firmwares (both yield same result). The update option I set to Erase user data. Once I hit
Maybe some kind of driver problem?
Click to expand...
Click to collapse
I re-read some of the posts about flashing & restoring factory ROM, and it mentioned turning OFF USB debugging mode (from within the device's Settings - submenu) before -
If you want are ready to give up on this donated/given to you device, you might want to try this as a last resort - then, run SUTL3 with the *.nb0 file to restore it to factory stock condition - and hopefully, get the WiFi working.
From your last description of the error MSG - MAC address unavailable, the settings are definitely corrupted / damaged. Some of the Vpad7 owners had to RMA back to Viewsonic for repairs, obviously it is beyond the warranty and not worth the expense now with this "aging" Froyo OS.
The solution, as you probably read it by now, was to wipe clean & go back to stock, root it again and then try a different custom ROM ...
* * * * * * * * P.S. Please check your PM/in-box for a special message [/B] * * * * * * * *
KWBR V4.2 custom Rom, still available for download, will work with ITE hardware - http://forum.xda-developers.com/showthread.php?t=1386469
Since your CWM is still working, give it a try by flashing and perhaps it can get your WiFi working.
I ended up fixing the problem.
I downloaded PdaNet (PdaNetA350x64.exe) and installed it. I used it to get some drivers for the Viewpad 7 when plugging it in. After that, I replaced the custom recovery menu with an original recovery menu file. Once the recovery was back to normal, I tried running SUT L3 and using the v3_420 .nbo file. It worked fine that time and my device's software was back to default.
--
Afterward, I rooted it and put on a custom recovery menu again. This time I used EUViewpad7 v1.7b ITE version and it did not break my wifi. My original cell phone broke and this device will serve as a pretty good replacement for a little while.
Thanks again for your help, Letitride.
Hey guys,
since 2-3 weeks i'm using the 6.0.1 official version which i got via OTA update (everything original on my phone, no root, no flashing any software) for my international S6 Edge.
First i noted havy battery drain and uninstalled a few apps. A weather widge forced the heacy battery drain and my phone worked fine.
Since 4 Days i have problems with random reboots. It started with some reboots a day and now it keeps rebooting after i unlocked sim card and want to use my phone. I managed to put my phone in flight mode and i were able to make a backup of my userdata via samsung smartswitch. I initialized the phone via the software and it flashed the newest version. After it finished it booted up and in the language selection screen it keeps rebooting.
I read about corrupted files due update from version 5.x to 6.0.1 and thought to wipe the phone and flash newest software via smartswitch would fix the problem but my phone is not usable anymore.
Maybe you have any advice for me?
Thanks for your further help!
greets
Bastian
Hi borth87
As it won't get worst, I suggest to flash a clean Stock version.
From SamMobile find the latest firmware for your device model.
After, for the download, I suggest you to use:
[TOOL] SamFirm - Samsung firmware downloader & checker
Just provide Model+Region and it will find you the newer firmware available. Please, before download, check the boxes: CRC32 & Decrypt
Flash the above using the lastest Odin v3.11.1
- Open Odin
- Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
- Connect phone and wait until you get a blue sign in Odin
- Add the firmware file downloaed to AP / PDA
- Make sure re-partition is NOT ticked
- Click the start button, sit back and wait few minutes
Let us know your path.
Nice regards.
.
borth87 said:
Hey guys,
since 2-3 weeks i'm using the 6.0.1 official version which i got via OTA update (everything original on my phone, no root, no flashing any software) for my international S6 Edge.
First i noted havy battery drain and uninstalled a few apps. A weather widge forced the heacy battery drain and my phone worked fine.
Since 4 Days i have problems with random reboots. It started with some reboots a day and now it keeps rebooting after i unlocked sim card and want to use my phone. I managed to put my phone in flight mode and i were able to make a backup of my userdata via samsung smartswitch. I initialized the phone via the software and it flashed the newest version. After it finished it booted up and in the language selection screen it keeps rebooting.
I read about corrupted files due update from version 5.x to 6.0.1 and thought to wipe the phone and flash newest software via smartswitch would fix the problem but my phone is not usable anymore.
Maybe you have any advice for me?
Thanks for your further help!
greets
Bastian
Click to expand...
Click to collapse
Thanks for the reply.
Will the flashing via odin touch the knox warranty?
greets,
Bastian
Hi B
No. Just flashing Sammobile firmwares via ODIN will NOT trip knox.
Have fun.
borth87 said:
Thanks for the reply.
Will the flashing via odin touch the knox warranty?
greets,
Bastian
Click to expand...
Click to collapse
Hey,
unfortunately the problems are still the same....
Thanks for your help.
greets
Hi borth87
Sad to know ...
Had you tried downgrade ?
Nice regards.
.
borth87 said:
Hey,
unfortunately the problems are still the same....
Thanks for your help.
greets
Click to expand...
Click to collapse
down grade to Lollipop? Is that possible?
edit: found a video where someone is just flashing 5.1.1. over 6.0.1, i will try this also
greets
Did the downgrade to 5.1.1 i and problems are still the same... I think i will send it to repair
I got back my phone from repair. They switched Mainboard and some minor parts.
Everything is working fine now. As it was warranty i dont have to pay for the change.
greetz
Hi.
I has the same problem. I tried to flash all of firmwares (always STOCK), but it's failed with ODIN all times. Samsung Smart Switch PC software say system repair succesfull (with emergency update repair), but the problem keep joke with me.
Phone don't repond without charger. With PC connection, i don't allow to run restore mode, only ODIN mode. With Wall charger adapter, i allow to run restore mode, odin mode, safe system mode, normal system, but i wiped cache, i do factory reset, i rebooted in bootloader and rebooted system as normal. When i run system in normal mode, language selection show up, and when i press next, phone reboot. When i run system in safe mode, i can select my language, and i can connect to my WiFi, but after i press NEXT at wifi list, phone reboot.
So in safe mode i able to do more one step, but system keep rebooting. Charging screen show battery at 89-90% all times, system start updating battery status from 1% to 100% (1 percent/ 1.5 sec).
Some times red-green-blue-purple rows show at Samsung logo and i got bootloop. Like when i put off my battery from my old phone.
I'm using Samsung Galaxy S9 Plus (SM-G965F) (Android Pie 9.0) and I rooted my phone by using Magisk, after that I cannot setup PIN or pattern. After I setup PIN/pattern and I go to add biometrics screen, when I confirm my PIN/pattern, there's a popup tell me that "PIN/pattern is incorrect."
How I root my phone ?
1. Flash stock Android Pie firmware via Odin
2. Flash TWRP recovery
3. Boot into TWRP
4. Wipe data
5. Flash RMM-State_Bypass_Mesa_v2.zip
6. Flash no-verity-opt-encrypt-samsung-1.0.zip
7. Flash kernel ElementalX-S9-2.01.zip
8. Flash root file Magisk-v18.0.zip
9. Reboot
Did I do something wrong ?
OMG! Finally I've found someone reporting the same issue! My situation is a bit different, but the result is the same as yours. I have a Samsung Galaxy S9 (SM-G960F), and here are a few things worth noting:
I flashed the latest Pie-based firmware for the LUX-region from updato.com through ODIN
I flashed twrp-3.3.0-0-starlte.img.tar through ODIN
I tried flashing both no-verity-opt-encrypt-samsung-1.0.zip and no-verity-opt-encrypt-6.0.zip, and I flashed RMM-State_Bypass_Mesa_v2.zip
I did not flash a custom kernel
Finally, I flashed Magisk v19.2.zip
Everything seemed to work just fine (during my limited time on Pie), but I encountered the same weird behaviour as you when trying to set up my fingerprint. If I dared to reboot my phone after that, it got stuck in some weird loop where the SIM unlock screen will show for a split second, and then turn off again for a moment. That pattern was repeated continuously, and sometimes it rebooted itself. I could basically not get back into my phone.
Please, PLEASE, tell me you've figured this out!? Or if not you, then somebody else. For now, I've restored the backup I made through TWRP prior to flashing Android Pie, so I'm back to a rooted version of Android Oreo. I'll probably stay there unless I have a solution for this problem, cause I just can't see myself using my phone without root access.
The joys of being a power user...
Same problem
I'm using a Samsung S9 (SM-G9600) and my rooting process was quite the same as yours. Phone works just fine, but I can't seem to set any kind of lock screen (including fingerprints, which forbids me from using fingerprint unlock on other apps too).
It's Samsung security stuff, you'd have to remove it to be able to use security again.
As to what exactly you need to remove, I'm not really sure.
Anyone got any updates? I got the same problem. I tried removing the *.key files in twrp to reset the Pin. It does work and it resets the pin asking for a new one but when i set it to 0000 and try to register a fingerprint it says the pin is incorrect.
Hi, cant make a phonecall with any dailer. no crash reports, its just shuts down. It started after i updated the Elixirrom to 13.2. Then flashed the stock 13.0.2 rom and tried Pixel OS rom, same problem.
Sigge2099 said:
Hi, cant make a phonecall with any dailer. no crash reports, its just shuts down. It started after i updated the Elixirrom to 13.2. Then flashed the stock 13.0.2 rom and tried Pixel OS rom, same problem.
Click to expand...
Click to collapse
So i had a similar issue, calls goes direct to ended, wont register ims settings, reset apn, reflash etc, threw the fone away the past year. But today got it working. Oh yeah and the camera app freezes too when in video mode. Not sure how it started but, this has made me lose jobs, appointments, all sorts of BS, and Xiaomi doesnt even offer support even though it's in the 2yr warranty range.
Spent 3 whole days on this crap, cause my replacement phone broke on me... I went through bricking this thing, to losing mac/imei and 300gigs of downloads. Ive gone back and forth, the only thing that gets it working again with all network 4g/lte /volte etc is
"miui_TOCOGlobal_V11.0.1.0.QFNMIXM_eb09b80c56_10.0.zip" you can update, but dont go over Android 10, it just dies again
Some reason mi flash gets a sparse error when trying to flash a tgz aswell as it won't actually flash anything it just goes green "Success" i think it loads up fastboot and thats about it.
So you going to need platform tools/adb/fastboot with an unlocked bootloader
twrp Alex's mod
kick it into fastboot
fastboot flash recovery twrp.img
fastboot boot twrp.img
if it stalls then youre going to have to use vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then
fastboot reboot recovery
in twrpm, you just gonna have to format data, wipe davo's dudes cat
reboot back to recovery
, you gonna hafta adb push it there ie; adb push "paste or drag n drop zip file" i just dump it in root with this /
so should look somth liek this
adb push E:\Download\miui_TOCOGlobal_V11.0.1.0.QFNMIXM_eb09b80c56_10.0.zip /
then flash it
I'm not sured what the root cause of the call ending is, i tried removing the phone services app and replacing it etc no dice. Might be kernel related..
Sigge2099 said:
Hi, cant make a phonecall with any dailer. no crash reports, its just shuts down. It started after i updated the Elixirrom to 13.2. Then flashed the stock 13.0.2 rom and tried Pixel OS rom, same problem.
Click to expand...
Click to collapse
Same thing here.
The problem seems to be from non working VoLTE in these ROM
There's no toggle to switch VoLTE off, so I switched from 4G to 3G network and now calls are working back.
Waiting for next updates to solve the problem