[Completed] Elephone P7000 Wireless network update error! - XDA Assist

Hi Guys,
Can someone help me with this?
2 Weeks ago I received my new Elephone P7000. Everything worked fine untill today.
I received a message on my phone that there was an official update for the wireless network …
It automatic doawnloaded this update after clicking on it and I was asked to reboot …
After the installation there was a message “Error!” so I pushed on the home and than the message was “No cammand!”
After pushing the home again I was in recovery mode. I backed up the personal userdatda via this menu and trieded to do a factory reset … I was wiping de personall userdata and the cache … nothing happens anymore … keeps rebooting in the main menu!
These are the errors after root integrity check:
Error:/system/app/Superuser.apk is new it is created on Thu Jan 1 00:00:00 1970
Error:/system/bin/su is new it is created on Thu Jan 1 00:00:00 1970
Error:/system/etc/install_recovery.sh is new it is created on Thu Jan 1 00:00:00 1970
Error:/system/xbin/su is new it is created on Thu Jan 1 00:00:00 1970
Error:/system/xbin/ksu.sud is new it is created on Thu Jan 1 00:00:00 1970
FAILED!
Kind Regards,
Luc Brossé

Hi there,
You'd be best served asking for help from the experts who own your device here:
P7000 Q&A, Help & Troubleshooting
Good luck

Related

[Q] Can't root, none of the methods worked.(4.0.4 ICS Tab)

Hello,
First of all I'd like to share you my device information:
Modell: M-Tech aTab 9.7 IPS
Android: 4.0.4
Kernel: 3.0.8+
SMP PREEMPT Wed Aug 29 00:54:17 CST 2012
Build: rk30_ics_v2.23.00
IMM76D.20120829.005419
That would be all about my Tab.
I recently bought it and I wanted to root it but none of the methods worked for me (Bin4ry's, SuperOneClick, and I can't even reboot inty recovery)
About adb shell.. Permissions are denied for "Reboot recovery" and I can't find any help for my device.
Please help. I'm kind of noob when it's time to do something with a device that is not known for many.
I've been researching and trying out different ways for 2 days now and nothing.
Thanks in advance. Coolby

[ROM's] [Stock ODEX] and [Firmwares] [SM-N900T, N9005, N900W8] Updated on 10-27-2014

1st = I am not a Programmer, not a Developer, nor a Modder... I just love my ANDROID DEVICE's... these roms will not get updated, they are STOCK ODEX Rom's not ALTERED except for renaming the KNOX files by adding the extension .ori so they would not run, I did not delete any files from these ROM's.
2nd = How to install the rom, JUST go to RECOVERY, ( I use TWRP RECOVERY ), Always make a backup 1st.. These Roms don't wipe ur Data, so if you don't wipe Data you might have some issues, - that being said - wipe SYSTEM, DATA, CACHE, DALVIK CACHE 2 times, DO NOT DELETE SDCARD and EXTERNAL SDCARD, then just flash the rom,...
3rd = Don't hold me responsible, if your phone blows up, or for whatever other damages u do to ur phone, flash at your own risk...
**************************************************
I made these Rom's for my personal use, and thought I would share for others that want STOCK ODEX Rom's, these Rom's are not rooted.
If you want the ROM rooted, goto Chainfire and download the newest SU available, after flashing the ROM, flash SU, reboot the phone, goto the Playstore and then install BusyBox, from Steriscon.
**************************************************
before posting theses Rom's I test them out, so they have no issues or problems...
Anyone can use these ROM's as a base for there own, all I ask is - if you share any of these ROM's, give proper credit to me, mdiaz33685...
Please Don't forget to hit the THANK'S Button...
**************************************************
SPECIAL THANKS TO.... in no special order...
Samsung
T-Mobile
XDA for teaching and hosting threads... and all the inspiring chefs...
dsixda's Android Kitchen = without this couldn't cook any roms...
Chainfire's SuperSU
jovy23 = thanks for his tutorials, kernals and MORE... :good:
**************************************************
LIST of FIRMWARES and Roms AVAILABLE at The Site and DOWNLOAD LINK...
DOWNLOAD Link for Stock ODEX Rom's and Firmware's - Link to androidfilehost site
**************************************************
for example these files are in RAR format... N900TUVUDNF1-files-modem.bin-boot.img-recovery.img.rar - ( which includes modem.bin + NON-HLOS.bin + boot.img + recovery.img )
**************************************************
**************************************************
Instructions
•Extract (unzip) the firmware file
•Download Odin v3.09
•Extract Odin zip-file
•Open Odin v3.09
•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 to AP / PDA
•Make sure re-partition is NOT ticked
•Click the start button, sit back and wait a few minutes
**************************************************
N900TUVUBMI7_N900TTMBBMI7_TMB = 4.3 = Build date: Fri, 13 Sep 2013 14:52:13 +0000 = USA (T-Mobile)
N900TUVUCNB4_N900TTMBCNB4_TMB = 4.4.2 = Build date: Wed, 12 Feb 2014 12:37:28 +0000 = USA (T-Mobile)
N900TUVUDNE6_N900TTMBDNE6_TMB = 4.4.2 = Build date: May, 19 Mon 2014 00:00:00 +0000 = USA (T-Mobile)
N900TUVUDNF1_N900TTMBDNF1_TMB = 4.4.2 = Build date: Tue, 17 Jun 2014 10:18:03 +0000 = USA (T-Mobile)
N900TUVUDNF4_N900TTMBDNF4_TMB = 4.4.2 = Build date: Sat, 19 Jul 2014 02:55:32 +0000 = USA (T-Mobile)
N900TUVUDNF9_N900TTMBDNF9_TMB = 4.4.2 = Build date: Fri, 22 Aug 2014 10:12:58 +0000 = USA (T-Mobile)
**********
N9005XXUEND3_N9005OLBENC3-XME = 4.4.2 = Build date: Mon, 14 Apr 2014 08:38:48 +0000 = Malaysia
N9005XXUEND5_N9005NEEEND1_NEE = 4.4.2 = Build date: Thu, 17 Apr 2014 09:36:47 +0000 = Nordic countries
N9005XXUEND6_N9005OLBEND1_SMA = 4.4.2 = Build date: Thu, 24 Apr 2014 00:00:00 +0000 = Philippines (Smart)
N9005ZHUENE3-20140515145650-TGY = 4.4.2 = Build date: Mon, 12 May 2014 00:00:00 +0000 = Hong Kong
N9005DXUENE3_N9005OLCENE4_SIN = 4.4.2 = Build date: Tues, 13 May 2014 00:00:00 +0000 = Singapore - (singtel)
N9005ZTUENE2_N9005ZZTENE2_BRI = 4.4.2 = Build date: Mon, 19 Mon 2014 00:00:00 +0000 = Taiwan
N9005DXUENE4_N9005OLCENE5_SIN = 4.4.2 = Build date: Tues, 20 May 2014 00:00:00 +0000 = Singapore
N9005XXUENE2_N9005MEOENE1_MEO = 4.4.2 = Build date: Fri, 23 May 2014 06:39:11 +0000 = Portugal
N9005ZHUENE6_N9005ZZHENE6_TGY = 4.4.2 = Build date: Tues, 27 May 2014 00:00:00 +0000 = Hong Kong
N9005XXUENE3_N9005MGFENE2_MGF = 4.4.2 = Build date: Wed, 28 May 2014 08:59:36 +0000 = Russia (MegaFon)
N9005ZHUENF1_N9005ZZHENF1_TGY = 4.4.2 = Build date: Thu, 05 Jun 2014 12:29:04 +0000 = Hong Kong
N9005DXUENF3_N9005OLCENF2_SIN = 4.4.2 = Build date Wed, 25 Jun 2014 124211 +0000 = Singapore (SingTel)
N9005XXUFNF4_N9005OXAFNF4_BTU = 4.4.2 = Build date: Wed, 25 Jun 2014 12:15:26 +0000 = United Kingdom
N9005XXUFNF4_N9005OLBFNG1_SMA = 4.4.2 = Build date: Wed, 25 Jun 2014 12:15:26 +0000 = Philippines (Smart)
N9005XXUFNG2_N9005OXXFNG2_SEE = 4.4.2 = Build date: Tue, 08 Jul 2014 15:16:09 +0000 = South East Europe
N9005DXUFNG2_N9005OLCFNG1-XSP = 4.4.2 = Build date: Thu, 24 Jul 2014 10:35:58 +0000 = Singapore
N9005VJUFNG3_N9005UUBFNG2_CHO = 4.4.2 = Build date: Fri, 25 Jul 2014 12:00:32 +0000 = Chile
N9005XXUGNG1_N9005OXAGNG1_BTU = 4.4.2 = Build date Thu, 28 July 2014 000000 +0000 = United Kingdom
N9005XXUGNG1_N9005OJVGNH1_XSI = 4.4.2 = Build date: Mon, 28 Jul 2014 12:56:29 +0000 = United Arab Emirates
N9005DXUGNH1_N9005OLCGNH1_XSP = 4.4.2 = Build date: Tue, 12 Aug 2014 02:28:16 +0000 = Singapore
N9005ZHUENH4_N9005ZZHENH4_TGY = 4.4.2 = Build date: Tue, 19 Aug 2014 15:46:34 +0000 = Hong Kong
N9005XXUGNI4_N9005AUTGNJ1_AUT = 4.4.2 = Build date: Mon, 29 Sep 2014 06:43:19 +0000 = Switzerland
N9005XXUGNI4_N9005TMZGNI1_TMZ = 4.4.2 = Build date: Mon, 29 Sep 2014 06:43:19 +0000 = Czech Republic (T-Mobile)
**********
N900W8VLUCNB7_N900W8OYACNB7_BMC = 4.4.2 = Build date: Thu, 27 Feb 2014 08:12:49 +0000 = Canada (Bell Mobile)
N900W8UBUCNC1_N900W8UUBCNE1_TTT = 4.4.2 = Build date: Wed, 05 Mar 2014 06:14:01 +0000 = Trinidad and Tobago
N900W8VLUCNI1_N900W8OYACNI1_VTR = 4.4.2 = Build date: Mon, 01 Sep 2014 10:22:24 +0000 = Canada (Videotron)
N900W8UBUCNJ1_N900W8UUBCNJ2_TPA = 4.4.2 = Build date: Fri, 03 Oct 2014 20:16:03 +0000 = Panama
**********
N9000QXXUENG4_N9000QTURENG3_TUR = 4.4.2 = Build date: Thu, 21 July 2014 00:00:00 +0000 = Turkey (La Fleur)
**************************************************
**************************************************
Xposed - ROM modding without modifying APKs=http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
Wanam Xposed | Customize your Stock Samsung Roms=http://forum.xda-developers.com/xposed/modules/app-wanam-xposed-customize-stock-t2383484
**************************************************
What I do 1st is make a copy of the rom, then
remove most of the files you don't want, or that you can get from the Play Store from the rom itself (rom name.zip), \system\apps and \system\priv-app
then restore the newest updated files from your \data\apps folder with Titanium Backup free or (PRO) or MyBackup Root free or (Pro) versions.
**************************************************
reserved
reserved
@mdiaz33685 So those are flashable zips of stock ROMs? Seems awesome, I was looking for something like this.
I am a little confused though, when I go into the download folder there are multiple files. I want to select say N9005DXUENE3 which should be the latest for my device (N9005) but there are two files, one named hlte only 700 mbs in size and the other with some Samsung code name being 1.3 gigs in size. What is the difference between the two releases?
Can be N9005DXUENE3 multi csc?
Thanks
Delete
Sent from my SM-N9005 using Tapatalk
---------- Post added at 02:40 PM ---------- Previous post was at 02:37 PM ----------
Favourite thread!
Sent from my SM-N9005 using Tapatalk
testmonkey1 said:
@mdiaz33685 So those are flashable zips of stock ROMs? Seems awesome, I was looking for something like this.
I am a little confused though, when I go into the download folder there are multiple files. I want to select say N9005DXUENE3 which should be the latest for my device (N9005) but there are two files, one named hlte only 700 mbs in size and the other with some Samsung code name being 1.3 gigs in size. What is the difference between the two releases?
Click to expand...
Click to collapse
I'm having the same confusion. But I'm downloading the 1.3gb version. Will flash and feedback later
testmonkey1 said:
@mdiaz33685 So those are flashable zips of stock ROMs? Seems awesome, I was looking for something like this.
I am a little confused though, when I go into the download folder there are multiple files. I want to select say N9005DXUENE3 which should be the latest for my device (N9005) but there are two files, one named hlte only 700 mbs in size and the other with some Samsung code name being 1.3 gigs in size. What is the difference between the two releases?
Click to expand...
Click to collapse
N9005DXUENE3_N9005OLCENE4_N9005DXUENE2_HOME-4.4.2.zip - this is the firmware version...
pcboyy said:
I'm having the same confusion. But I'm downloading the 1.3gb version. Will flash and feedback later
Click to expand...
Click to collapse
looks like they were having issues when I was uploading, and the file didn't upload correctly...
I will upload the Stock Odex rom when I get back, going out right now...
sorry, they were doing server updating...
edit.. uploading the STOCK ODEX ROM = should be done in a few.. N9005DXUENE3-hlte_Stock_Odex_NotRooted-NoKnox.zip
N9005DXUENE3_N9005OLCENE4_N9005DXUENE2_HOME-4.4.2.zip - this is the firmware version...
Instructions
•Extract (unzip) the firmware file
•Download Odin v3.09
•Extract Odin zip-file
•Open Odin v3.09
•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 to AP / PDA
•Make sure re-partition is NOT ticked
•Click the start button, sit back and wait a few minutes
testmonkey1 said:
@mdiaz33685 So those are flashable zips of stock ROMs? Seems awesome, I was looking for something like this.
I am a little confused though, when I go into the download folder there are multiple files. I want to select say N9005DXUENE3 which should be the latest for my device (N9005) but there are two files, one named hlte only 700 mbs in size and the other with some Samsung code name being 1.3 gigs in size. What is the difference between the two releases?
Click to expand...
Click to collapse
yes, these are flashable through recovery, I use twrp 2700... the STOCK Odex Roms, if you want root, just go download your SU, link on the OP page for chainfire.. and then through the play store download busybox..
I always download the newest and keep it on my phone, and install everything manually..
I test everything, without root 1st, then I flash SU - http://forum.xda-developers.com/showthread.php?t=1538053 and install busybox...
Will it flash modem as well?
Rosli59564 said:
Will it flash modem as well?
Click to expand...
Click to collapse
No it won't flash the modem and it won't erase data. But always make a backup first.
Sent from my SM-N900T using XDA Premium 4 mobile app
can i flash t mobile firmware on n9005
brightssingh said:
can i flash t mobile firmware on n9005
Click to expand...
Click to collapse
Which phone do u have... I have the N900T and I flashed the new firmware for N900TUVUDNE6 on top of the rom N9005ZHUENE3, I kept my data, but always make a backup, I only flash the N900T firmware on my phone, but I have used every rom I have posted on my phone.. sometimes it might not keep data... I flashed the firmware so many times, at one point it did wipe the internal SD, but I don't know if it was the firmware or me just wiping the phone trying to flash the modem... I had a very hard time with the modem...
I only recommend flashing firmware for your correct phone model..
Can u share modem ne3.tar ? My modem still in nc2 and I want update it
dl the stock rom and flash it and you will have MODEM: N9005DXUENE2
I have problems with this file N9005DXUENE3-hlte_Stock_Odex_NotRooted-NoKnox.zip
I can't unzip with 7zip and modify it. can you add md5, mine is B79620EEB7D24DBF5F3F3E1E34991119
and the size is 1,26 Go. I dl 2 timzes with same results
rayman95 said:
dl the stock rom and flash it and you will have MODEM: N9005DXUENE2
I have problems with this file N9005DXUENE3-hlte_Stock_Odex_NotRooted-NoKnox.zip
I can't unzip with 7zip and modify it. can you add md5, mine is B79620EEB7D24DBF5F3F3E1E34991119
and the size is 1,26 Go. I dl 2 timzes with same results
Click to expand...
Click to collapse
md5-b79620eeb7d24dbf5f3f3e1e34991119 http://www.androidfilehost.com/?fid=23501681358537470
try another browser, or a different server ... - there are 58 downloads, no one mentioned anything wrong with it,,
im going to download it and see it it works, if not I will upload it again, I let u know ok... give me a bit..
edit: just downloaded the file, looks corrupted, im loading now... I checked and a lot files look kinda short, I had to reupload over 10 files, don't know whats going on when there updating and changing there servers.
md5-3443ac6ae4f79ecce2c43b1ae901b07b
size: 1.2GB
in my kitchen file size is.. 1.29 GB
thank's. Dl again and let you know
---------- Post added at 11:08 AM ---------- Previous post was at 10:35 AM ----------
got the zip with same Md5 : 3443ac........ the size is 1,24 Go but I can't unzip or modify with 7zip and winrar
got message file corrupted in winrar
rayman95 said:
thank's. Dl again and let you know
---------- Post added at 11:08 AM ---------- Previous post was at 10:35 AM ----------
got the zip with same Md5 : 3443ac........ the size is 1,24 Go but I can't unzip or modify with 7zip and winrar
got message file corrupted in winrar
Click to expand...
Click to collapse
+1. Size is 1,26 GBs for me though (on Windows)
Downloaded the zip last night, today when trying to open it through Windows explorer it said corrupted zip. 7zip actually opened the archive but when trying to extract it it gives some weird error.
PS: I think OP is reuploading the file as we speak. Hope it works this time.
@mdiaz33685
What is the difference between N9005DXUENE3-hlte_Stock_Odex_NotRooted-NoKnox.zip and the other archive. One is completely stock and the other has Knox removed? E.g. the removed KNOX is the only difference?
Also do you think of adding minor tweaks like disabled call ringer, and enabled hidden CSC features.
edit: redownloaded the new file. 1,24 GBs in size. Still corrupted. Downloading the other N9005 to check it now.
it seems this file has problem too http://www.androidfilehost.com/?fid=23501681358538194

[Q] Invisiable backups

I seem to have dug myself into a hole. I tried to test KitKat on my Galaxy Mega (GT-I9205). I found two roms that said they supported the Mega, so I made a backup of my current rom and flashed the first rom I found, played around with it and decided to go back to Jelly Bean, backup restored, no problems, all normal.
Then I tried the second rom (cm11 unofficial). Installed, no problems, played around with it and decided it wasn't for me and tried to revert to the JB rom backup. No chance. The recovery environment (which used to be cwm but somehow is now twrp v2.7.0.5 - don't ask me how? ) cannot even see any of the backups I have (and I have plenty, some of which were made by cwm and some by twrp - although probably not the same twrp version, not sure on that).
What I have tried.
Renaming the backups, moving the backups to different folders, using twrp to do a backup of the new rom to see where it saved it and then moving the backups to that folder, but it simply refuses to see them. So I can't go back. I even tried flashing a cwm recovery zip from within twrp - ok, I realise that is not likely to work, and sure enough it didn't..
My next thought was that I will have to continue using the cm rom that I have installed, but it has a problem too. When gapps is not installed every single application runs normally, but as soon as I install gapps both Titanium Backup (6.1.5.6) and Rom Manager (5.5.3.7) crash. I have tried this three times (two different gapps versions) and including cache and dalvik wipes before flashing gapps, absolutely no change.
So in short I have a perfect backup that can't be seen, I have a cm11 rom without gapps that works perfectly normally and I have a cm rom with gapps where two of my most important applications constantly crash.
I would really like to go back to JB - but if anyone can tell me how to fix titanium and rom manager on the present install, that would be fine, I would stick with cm11.
Another complication is that I don't use windows (linux only) so Odin is not an answer for me.
Help!
Edit: Here is another thought. I can easily do without Rom Manager, since Twrp took over my recovery it does nothing anyway, but is there a replacement out there for Titanium Backup? Even something half as capable I would be able to cope with until TB maybe issues an update that works with gapps on cm11.
Edit2: It seems there is such a tool. Jrummy Ultimate Backup seems to have the same functions as Titanium and it runs perfectly so far whereas Titanium still crashes all the time. This might be the answer to continuing to use Cm11.
Well here is a clue. When I look at the backups in the Ultimate backup interface, it actually identifies them by type and it appears that the backups I thought were twrp backup (I even included the letters 'twrp' in the backup name) are in fact cwm backups not twrp. This may be why twrp can't see them!!
Don't think I will ever be able to go back to these now unless I force another recovery onto the phone (cwm of course) - without Odin that is none too easy.
However, the good news is that at the moment (early days still) the CM11 rom with Ultimate Backup on it is running very smoothly so maybe I don't have to go back at all, we will see.
I finally solved this after 4 days puzzling over it. I will tell you how even though I received absolutely no help from anyone on the forum.
All my backups (which used to work) look like this:
Code:
/h/c/b/c/2014-08-10-lite> ls -l
total 2235668
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 boot.img
-rw-r--r-- 1 manjaro 1000 0 Feb 1 2013 cache.ext4.tar
-rw-r--r-- 1 manjaro 1000 19456 Feb 1 2013 cache.ext4.tar.a
-rw-r--r-- 1 manjaro 1000 0 Feb 1 2013 data.ext4.tar
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 data.ext4.tar.a
-rw-r--r-- 1 manjaro 1000 41370112 Feb 1 2013 data.ext4.tar.b
-rw-rw-r-- 1 manjaro 1000 492 Aug 15 15:39 nandroid.md5
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 recovery.img
-rw-r--r-- 1 manjaro 1000 0 Feb 1 2013 system.ext4.tar
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 system.ext4.tar.a
-rw-r--r-- 1 manjaro 1000 226939392 Feb 1 2013 system.ext4.tar.b
You can see from the fourth column that I have three zero byte files in there - don't ask me how, it is just how the backups were written, I didn't interfere with the process and all five backups were the same and they had been used to restore the image before without problem.
What I did was to change it to this:
Code:
/h/c/b/c/2014-08-10-lite-COPY> ls -l
total 2235672
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 boot.img
-rw-r--r-- 1 manjaro 1000 19456 Feb 1 2013 cache.ext4.tar
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 data.ext4.tar
-rw-r--r-- 1 manjaro 1000 41370112 Feb 1 2013 data.ext4.tar.a
-rw-rw-r-- 1 manjaro 1000 339 Aug 16 11:45 nandroid.md5
-rw-r--r-- 1 manjaro 1000 10485760 Feb 1 2013 recovery.img
-rw-r--r-- 1 manjaro 1000 1000000000 Feb 1 2013 system.ext4.tar
-rw-r--r-- 1 manjaro 1000 226939392 Feb 1 2013 system.ext4.tar.a
Removed the zero byte files, renamed the other files appropriately and then regenerated the nandroid.md5 file with the correct values, cd to the backups folder and run:
Code:
md5sum *>nandroid.md5
(on Linux that is)
The amended backup restored at the first attempt.
This process was much complicated by the fact that these backups were done in CWM and my running ROM had TWRP. Thanks to the writers of Heimdall for solving that problem for me - nothing windows or android possessed was capable of doing so.
Having succeeded in restoring the backup I then flashed TWRP onto the Jelly Bean rom so it is now a simple rom flash to switch from one the other.

MITM interrupt connection

HI!
I got a problem wwhen using MITM(from s7262).it works finely but the target loses its internet connection!
so the target cant access to any webpage and even those connected to the same network lose internet connection! and he get the following messages:
1) connection has interrupted
2)youtube
-Expires: Tue, 27 Apr 1971 19:44:06 EST
Content-Type: text/html; charset=utf-8
Date: Thu, 16 Oct 2014 19:11:42 GMT
3)facebook page are not affected!
4)google
:X-XSS-Protection: 1; mode=block Google-Creative-Id: 33465098134 Google-LineItem-Id: 50136214 X-Content-Type-Options: nosniff
if any1 expereinced this problem plz link me to the solution!
any help is appreciated!thank u in advance

ZONMAI XS9 128 GB Tablet - Storage & Boot Problems

Good day mates
I've bought a used ZONMAI XS9 knowing it's wired behavior "restoring after boot" , and today I have received the tablet.
I thought I could fix the problem rebooting in recovery mode and "flash heal" the device, but I've failed to do so.
Neither the button press method (select recovery mode from boot menu) nor using adb reboot recovery via USB connection succeeded. It seems the tablet tries to go into recovery mode, but can't boot it for unknown reason and falls back to main boot loading.
I can access the device and install applications setup WLAN do all kind of things, but after a normal reboot (or factory reset) ALL changes are lost, and last used state of the previous owner around 12.2021 is restored.
I've noticed a security patch discrepancy. In the "About tablet" tab the system claims security patch level April 2021 as latest patch -but- under System Update tab the last Android security update is registered October 5, 2019 that makes the 2 year difference between the update and patch, kind-a-weird I think.
I've tried an external SD-Card used in internal storage mode too, but after reboot the tablet forgot about the SD card and wants it to format again.
I've searched the internet for a stock ROM to flash but the ZONMAI seems to be Chinese mass market no-name brand, so I could not find one.
I think the eMMC might be the issue here may be damaged or some firmware issues?
Any ideas or clues ?
Greetings from PitcherGood
PS: Sorry if this is the wrong forum, i could not find a ZONMAI forum.
System Specs
Brand: ZONMAI
Model: XS9
RAM: 6GB
eMMc: 128GB
Android Version: 10
Security Patch Level: April 5, 2021
Kernel Version: 3.18.79 (gcc version ... Tue Nov 2 12:09:13 CST 2021)
Build number: C30V3.8_PJX06_EN_20211102
Custom build number.: C30V3.8_PJX06_EN_20211102

Categories

Resources