echo /data/local/tmp/odm_reserved > /sys/firmware/fuse/odm_reserved
Now that we know that we blow a bunch of fuses not intentionally the question is what other effects except a seemingly working unlock does this cause.
will everything else work ok or do we must expect some troubles?
Also a mod may want to go over all threads and cleanup a bit pointing to the proper solution to blowing only the fuses we want blow.
Nobody really knows I don't think, but my phone hasn't had any obvious side effects from this. Agreed a mod should cleanup though, at very least LG could tell its a hacked unlock not official if anybody goes to service centre.
Sent from my rooted P880
On the positive side of things, with this in your fuse you can argue you did not agree to any lost of warranty or so, as you would have to if you would use the official unlock.
DavidXanatos said:
On the positive side of things, with this in your fuse you can argue you did not agree to any lost of warranty or so, as you would have to if you would use the official unlock.
Click to expand...
Click to collapse
Very clever
Sent from my rooted P880
but if you write the locked code back into the fuse you should get your BL locked again. Or Am I wrong ?
Sent from my LG-P880 using xda app-developers app
tobixdev said:
but if you write the locked code back into the fuse you should get your BL locked again. Or Am I wrong ?
Click to expand...
Click to collapse
No you can only change 0 -> 1
you can not overwrite a 1 with a 0 again.
meaning you can fill your fuses with 0xffff...ffff and some more f's thats all, you can not reset it to 0x00...000
DavidXanatos said:
No you can only change 0 -> 1
you can not overwrite a 1 with a 0 again.
meaning you can fill your fuses with 0xffff...ffff and some more f's thats all, you can not reset it to 0x00...000
Click to expand...
Click to collapse
Ok tanks
I thought this was some kind of security error, my mistake
Well I derped and mine is now
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Which if i'm not mistaken, is irreversible and everything has been blown.
Bootloader status reads as locked but kholk's kernel and CWM boots fine. I reflashed recovery a couple of times and it still booted fine. It thinks kholk's kernel was signed by LG
Can't use fastboot to flash, it says security error.
I'll see what other problems there are.
Sent from my LG-P880 using Tapatalk 2
exFAT said:
Well I derped and mine is now
0xffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
Which if i'm not mistaken, is irreversible and everything has been blown.
Bootloader status reads as locked but kholk's kernel and CWM boots fine. I reflashed recovery a couple of times and it still booted fine. It thinks kholk's kernel was signed by LG
Can't use fastboot to flash, it says security error.
I'll see what other problems there are.
Sent from my LG-P880 using Tapatalk 2
Click to expand...
Click to collapse
ok,
does it really think that kholk's kernel was signed by LG or does the boot code just think the phone is unlocked, but the rest of fast boot thinks different, what luckily does not mater that much.
can you flash OEM images using fastboot?
I mean for recovery purposes that would be fine enough, you recover some OEM ROM and than go again to CWM and CM
PS:
When I think about it,
I guess the most proper way to unlock a version that is not officially unlock-able.
Is to remove the sim before flashing x20a the first time, and than writing 40...c8 to the fuses.
My unit a 232-10 directly after flashing offcial v20a had all fues 0 (and some users (1) reported that they could unlock their 232-10 officially) after a few hours o for the 80....00 meaning most likely my carier (drei.at may he be dammed for all eternity) send some command to my phone to permanently deny official unlock.
It would be interesting to see the printout of a unlockable phone befoure and after unlock.
As we know the not eur-open versions that ware unlockable ware so after a few hours, so after the carier granted that and blow some different fuse.
my bet would be 40..00 but thats only a guess.
No our hacked devices are in a confused state, some fuses say unlock forbidden and some other fuses say unlocked.
Luckily the bootloader checks only the later fuses, fastboot is however smarter unfortunately.
So to get an non unlock-able version unlocked cleanly we need to catch the moment no fuses are blown and blow only 40....8c
well and may be never go back to a stock may that may just for fun bow 80...00 making us c0...c8
David X.
hi guys i found this on open europe rom
maybe it useful
D/UnlockService( 625): first sleep end
D/UnlockService( 625): additional while start
D/UnlockService( 625): strOpNumeric : 51008
D/UnlockService( 625): additional while end
D/SecurityManager( 625): Request Data: AT%WALLPAPER=2
D/SecurityManager( 625): JUYA= AT%WALLPAPER=2
D/SecurityManager( 625): getPhoneService
D/SecurityManager( 625): getPhoneService(): tryCount[1]
D/PhoneInterfaceManager( 608): SEND_ATCOMMAND -request.argument [AT%WALLPAPER=2]
D/PhoneInterfaceManager( 608): EVENT_ATCOMMAND_RESPONSE - result [255,255,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]
D/SecurityManager( 625): AT WALLPAPER Result:255,255,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
D/SecurityManager( 625): getPhoneService
D/PhoneInterfaceManager( 608): SEND_ATCOMMAND -request.argument [AT%NTCODE]
D/PhoneInterfaceManager( 608): EVENT_ATCOMMAND_RESPONSE - result ["0","FFF,FFF,FFFFFFFF,FFFFFFFF,FF"]
D/SecurityManager( 625): AT NTCODE Result:"0","FFF,FFF,FFFFFFFF,FFFFFFFF,FF"
D/SecurityManager( 625): network.flag: 0
D/SecurityManager( 625): network.attemptsLeft: 0
D/SecurityManager( 625): network.retry_count_max: 0
D/SecurityManager( 625): NTCode1: "FFFNTCode2:FFF
D/SimLockChecker( 625): setMCC : 0
D/SimLockChecker( 625): setMMC : 0
D/SimLockChecker( 625): setSimState : 0
D/UnlockService( 625): sim state:0 mcc:4095 mnc:255
D/UnlockService( 625): readSysfs_string() : 0x00000000000000000000000000000000000000000000000000000040000000c0
D/UnlockService( 625): setUnlockAvailBit strRead : 00000000000000000000000000000000000000000000000000000040000000c0
D/UnlockService( 625): setUnlockAvailBit reversed : 40000000
D/UnlockService( 625): setUnlockAvailBit nProcessingNumber : 40000000
D/UnlockService( 625): setUnlockAvailBit nResetMaskingBits : c0000000
D/UnlockService( 625): setUnlockAvailBit nNotAvailMaskingBits : 80000000
D/UnlockService( 625): setUnlockAvailBit nAvailMaskingBits : 40000000
Click to expand...
Click to collapse
Related
I decided to tinker in the Wizard's bootloader mode. I found that the "d2s" command that people have used on other devices' bootloader mode does not work on the Wizard. However, the "r2sd" command does allow you to write a specific portion of the ROM to a memory card... provided you can provide the right password to enable the feature. Right now, I'm getting this error message:
Code:
Cmd>r2sd all
***** user area size = 0x1E980000 Bytes
R2SDBackup() - Download type = 6
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512
You didn't get the proper security level to download a specific image
Cmd>
According to other people performing ROM dumps and accessing bootloader commands, you need to type "password [password]" and you'll be able to get the "proper security level." The only problem is, what do I put in for [password]? I've tried WIZARD and PRODIGY and TYPHOON, since those were the passwords of the previous devices, but none work so far. Apparently, if I get the right password, I'll be greeted with a different prompt.
By the way, if we get the right password, this is what the "r2sd" command can supposedly grab.
Code:
Cmd>r2sd
Usage:
r2sd (ipl/spl/splash/os/gsm/ffs/all/gsmdata/diag/extrom/htclogo)
Backup DOC image to SD card .
Cmd>
Hey, I see the words "splash" and "htclogo" in there! So, anyone got any bright ideas?
BeyondtheTech said:
Code:
Cmd>r2sd
Usage:
r2sd (ipl/spl/splash/os/gsm/ffs/all/gsmdata/diag/extrom/htclogo)
Backup DOC image to SD card .
Cmd>
Click to expand...
Click to collapse
Did you try "r2sd os" or "r2sd gsm"?
what is the result from these commands?
Is the Wizard bootloader locked? If so, is there anyway to unlock it?
if you have it unlocked at imei-check.com (even with no simlock)
You will get a new bootloader installed.
and from there you can dump without a password..
Cmd>r2sd all
***** user area size = 0x1E3E0000 Bytes
R2SDBackup() - Download type = 5
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512
Start address = 0x80000000 , Length = 0x800
Start address = 0x80000800 , Length = 0xC0000
Start address = 0x800C0800 , Length = 0x40000
Start address = 0x80100800 , Length = 0x280000
Start address = 0x4E3D4C0 , Length = 0x3900000
Start address = 0x743D4C0 , Length = 0xA00000
SD user size = 0x1E3E0000, Image total size = 0x4680800
1 Start=0x80000000, Length=0x800, Checksum=0xEC197E45
+WriteDataToSDCard() - pusSourceAddr = 0x8C100000 , ulSourceLength=0x800
WriteDataToSDCard() ulTargetSDAddr=0x200 pusSourceAddr=0x8C100000 dwTotalBlock=0x4
-WriteDataToSDCard() - pusSourceAddr = 0x8C100000 , ulSourceLength=0x800
2 Start=0x80000800, Length=0xC0000, Checksum=0xB73A3E59
+WriteDataToSDCard() - pusSourceAddr = 0x8C100000 , ulSourceLength=0xC0000
WriteDataToSDCard() ulTargetSDAddr=0xA00 pusSourceAddr=0x8C100000 dwTotalBlock=0x600
-WriteDataToSDCard() - pusSourceAddr = 0x8C180000 , ulSourceLength=0xC0000
3 Start=0x800C0800, Length=0x40000, Checksum=0xDE71BB6B
+WriteDataToSDCard() - pusSourceAddr = 0x8C100000 , ulSourceLength=0x40000
WriteDataToSDCard() ulTargetSDAddr=0xC0A00 pusSourceAddr=0x8C100000 dwTotalBlock=0x200
-WriteDataToSDCard() - pusSourceAddr = 0x8C100000 , ulSourceLength=0x40000
4 Start=0x80100800, Length=0x280000, Checksum=0xCCF373AE
+WriteDataToSDCard() - pusSourceAddr = 0x8C100000 , ulSourceLength=0x280000
WriteDataToSDCard() ulTargetSDAddr=0x100A00 pusSourceAddr=0x8C100000 dwTotalBlock=0x1400
-WriteDataToSDCard() - pusSourceAddr = 0x8C380000 , ulSourceLength=0x280000
5 Start=0x4E3D4C0, Length=0x3900000, Checksum=0x7754CD01
+WriteDataToSDCard() - pusSourceAddr = 0x8C100000 , ulSourceLength=0x3900000
WriteDataToSDCard() ulTargetSDAddr=0x380A00 pusSourceAddr=0x8C100000 dwTotalBlock=0x1C800
-WriteDataToSDCard() - pusSourceAddr = 0x8FA00000 , ulSourceLength=0x3900000
6 Start=0x743D4C0, Length=0xA00000, Checksum=0x91C3A10A
+WriteDataToSDCard() - pusSourceAddr = 0x8C100000 , ulSourceLength=0xA00000
WriteDataToSDCard() ulTargetSDAddr=0x3C80A00 pusSourceAddr=0x8C100000 dwTotalBlock=0x5000
-WriteDataToSDCard() - pusSourceAddr = 0x8CB00000 , ulSourceLength=0xA00000
Double Check 0 Start=0x80000000, Length=0x800, Checksum=0xEC197E45
Double Check 1 Start=0x80000800, Length=0xC0000, Checksum=0xB73A3E59
Double Check 2 Start=0x800C0800, Length=0x40000, Checksum=0xDE71BB6B
Double Check 3 Start=0x80100800, Length=0x280000, Checksum=0xCCF373AE
Double Check 4 Start=0x4E3D4C0, Length=0x3900000, Checksum=0x7754CD01
Double Check 5 Start=0x743D4C0, Length=0xA00000, Checksum=0x91C3A10A
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512
+WriteHTCSignature,download type = 5
Common Info Checksum=0xC8AFBD04
-WriteHTCSignature...
Click to expand...
Click to collapse
grtx , arnold
but the http://www.imei-check.co.uk/m3000unlock.php doesn't provide service for dopod 838.
mhh i think it's for all htw wizard based phones.
But not sure.
did you mail them already???
Money money
Hi,
28 € for what we used to do for free ??????
Not interested !
Re: Money money
eurorpeen said:
Hi,
28 € for what we used to do for free ??????
Not interested !
Click to expand...
Click to collapse
We??? ......If you want to unlock it now there are two options: Paying 28 Euro at i-mei check or paying 120 Euro at T-Mobile.
There is no free unlocking tool yet.
that's your own choice .
I'm convinced that between now and 1-2 months the tools are freely availeble.
Only i'm still in switching numbers , and would like to use my old orange card for the time being.
so it's worth the e28 to me.
(and got a passfree bootloader)
But i didn't say you have to do it...
grtx , arnold
Not for me
Hi,
By "we", I was saying "the users of the previous models"
And no, if I can, I will not pay 28 € to unlock a phone that will be obsolete before 6 months.
Do you see its successor (for 03/2006) ? A beauty with UMTS and everything else, even an Intel 416 MHz processor.
So for the moment, my S110 will continue to work flawlessly
Hi all,
I want to flash the Qtek rom onto my vario as it's giving me nothing but grief, could someone please tell me how do i backup my t-mobile rom so that i can restore it at a later date?
I see talk of this r2sd command, but how do i send that to the phone? how do i then restore this backup from the SD? is there an app i can run which will save the backup to a file so i can save it on my pc for restoration later?
Thanks in advance
P.S : I have unlocked the phone using the software at imei-check.co.uk
@belial
http://forum.xda-developers.com/viewtopic.php?t=32866
Thank you arnoldl, i'll go try flash with the qtek one now, can't do any harm anyway as in it's current state it's next to no use
After runing the phone unlock programe for my phone, my phone now wont work at all???. If I remove the Sim card all the PDA functions work normaly. However if I insert the Sim it imieadiately asks me for the unlock code. I looked in the Unlock Log which I was able to access via active sync and none of the codes listed in there seem to work. Can anybody please help me.
Thankyou
I am on AIM under the name, Robsmobil
More info
After I ran the software initialy this is what I got. I was able to figure out a way to run version 1.6 for a seccond time with the card still in place. However at the very bottom you will see the results from that.
PLEASE HELP ANYONE !!!
First attempt using V1.5 of the software.
xdadev_all_unlock started
device=PH20B
key found
ril ioctl 0xc2: 00000000
simlock answer: %SIMLOCK= 05
0
current lock status: 05
security answer:
000
security answer2:
at%LISTNETWORKCODE answer: %NetworkCode: 23433F%NetworkCode: 00101F0
at%LISTNETSUBCODE answer: 0
at%LISTSPCODE answer: %SPCode: 000
at%LISTCORPORATECODE answer: 0
xdadev_all_unlock started
at%LISTSIMCODE answer: 0
at%LISTIMSIRANGECODE answer: 0
device=PH20B
key found
ril ioctl 0xc2: 00000000
at%CLEARNETWORKCODE answer:
simlock answer:
invalid sim lock answer
error getting current lock status
at%CLEARNETSUBCODE answer:
at%CLEARSPCODE answer:
at%CLEARCORPORATECODE answer:
at%CLEARSIMCODE answer:
at%CLEARIMSIRANGECODE answer:
setting lock 01
htclock answer:
removing lock 01
htclock answer:
setting lock 04
htclock answer: 0
%SIMLOCK= 05
0
0
0
0
0
0
0
0
removing lock 04
htclock answer:
xdadev_all_unlock failed
ril ioctl 0xc2: 00000000
ril ioctl 0xc6: 00000000
simlock answer: 0
%SIMLOCK= 01
0
xdadev_all_unlock done
ril ioctl 0xc2: 00000000
ril ioctl 0xc6: 00000000
xdadev_all_unlock started
device=PH20B
key found
ril ioctl 0xc2: 00000000
simlock answer:
invalid sim lock answer
error getting current lock status
xdadev_all_unlock failed
ril ioctl 0xc2: 00000000
ril ioctl 0xc6: 00000000
Seccond attempt using V1.6 of the software.
xdadev_all_unlock started
device=PH20B
key found
ril ioctl 0xc2: 00000000
simlock answer:
invalid sim lock answer
error getting current lock status
xdadev_all_unlock failed
ril ioctl 0xc2: 00000000
ril ioctl 0xc6: 00000000
I got it working !!!!!!
All I did was to remove the SIM card run the software agan then waited about 1 minuet. I then put the Sim Card back in and hey presto it works perfectly.........
Hello. First of all thanks for this great forum.
Second, i got a QTEK 9090 (not the best but welll...) and I was trying to unlock the SIM. I went to:
http://forum.xda-developers.com/showthread.php?t=240784 and download the two versions of the unlocker:
xdadev_all_unlock-v1.5.exe
xdadev_all_unlock-v1.6_138.exe
I did this, just like it says in the thread:
copy it to your phone, and run it.
some diagnostic output will be in the file \xdadev_all_unlock.log
After a few minutes it says Phone successfully unlocked and then I restart the QTek. I have done this with both, the sim inside and without the sim.
The log is the following:
dadev_all_unlock started
device=PH20B
key found
ril ioctl 0xc2: 00000000
simlock answer: %SIMLOCK= 00
0
current lock status: 00
security answer:
000
security answer2:
at%LISTNETWORKCODE answer: 0
at%LISTNETSUBCODE answer: 0
at%LISTSPCODE answer: 0
at%LISTCORPORATECODE answer: 0
at%LISTSIMCODE answer: 0
at%LISTIMSIRANGECODE answer: 0
at%CLEARNETWORKCODE answer:
at%CLEARNETSUBCODE answer:
at%CLEARSPCODE answer:
at%CLEARCORPORATECODE answer:
at%CLEARSIMCODE answer:
at%CLEARIMSIRANGECODE answer:
simlock answer:
invalid sim lock answer
xdadev_all_unlock done
ril ioctl 0xc2: 00000000
ril ioctl 0xc6: 00000000
After I restart it SOMETIMES it says its looking for the network and others it just says out of service. When it tries to look for the network it just stays there... I mean its like an infinitive loop. It never finds out a network.
The info about the QTEK is:
PH20B 0 B ESN N TELCE301 1.40.03 0 3 1.40.178 1.12.00 12.00
So I thought that maybe the ROm version or radio may affect and looked up for xda2unlock but it says its only for 1.05.12 soo I'd better to ask here.
I know that maybe all of you have just got this working, so I'd like to ask for help.
Thanks if you can help me. Any info that you guys need, just ask it and I will try to get it.
Thanks a lot.
Oh and my last question is that as I see this Pocket uses 802.11b as wireless protocol, is there any way(a hack or something) to use it with a 802.11g wireless router?
Thanks.
Any ideas...?
Hi to everyone.
I was updating my tab to the latest version of the ROM of sbdags.
Everything was fine until i reboot the tab to use it for the first time: loop in the boot animation and never come out from it.
I came from the previous version of the rom, the Cromi-x 6.1 with 10.26.1.18 bootloader.
The process i use to update was this:
1) wipe of data/factory reset, wipe with format /boot, wipe with format /system
2) Install the CWM recovery 6.0.5.0 and update the bootloader to 11.4.1.17 by flashing they with the file that you can find in the rom page.
3) repeat point 1
4) install the rom by flashing it from an SD. Complete the Aroma installer and answer to every option that it ask to me.
5) reboot the system and stuck in the bootanimation
I use the WW format cause i'm italian and i check the md5
What's wrong? I can go to recovery everytime i need and i have a backup just in case i need it.
Sdbags, i really want to offer you a beer for your work. I think i will do it in every case, but yes, kitkat on my tab would be great :victory:
Sorry for bad english. For every question, i'm here. Thanks a lot.
M.
aMachi said:
Hi to everyone.
I was updating my tab to the latest version of the ROM of sbdags.
Everything was fine until i reboot the tab to use it for the first time: loop in the boot animation and never come out from it.
I came from the previous version of the rom, the Cromi-x 6.1 with 10.26.1.18 bootloader.
The process i use to update was this:
1) wipe of data/factory reset, wipe with format /boot, wipe with format /system
2) Install the CWM recovery 6.0.5.0 and update the bootloader to 11.4.1.17 by flashing they with the file that you can find in the rom page.
3) repeat point 1
4) install the rom by flashing it from an SD. Complete the Aroma installer and answer to every option that it ask to me.
5) reboot the system and stuck in the bootanimation
I use the WW format cause i'm italian and i check the md5
What's wrong? I can go to recovery everytime i need and i have a backup just in case i need it.
Sdbags, i really want to offer you a beer for your work. I think i will do it in every case, but yes, kitkat on my tab would be great :victory:
Sorry for bad english. For every question, i'm here. Thanks a lot.
M.
Click to expand...
Click to collapse
Don't do step 3. Try it again please.
Try the default options first.
sbdags said:
Don't do step 3. Try it again please.
Try the default options first.
Click to expand...
Click to collapse
If default option are those who are pre-selected on the aroma installer i've already try it.
Also i try to do it without point 3. Nothing
Here a log of the installation of the rom
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : CROMi-Xenogenesis KitKat
ROM Version : 7.0.2 DEODEX
ROM Author : sbdags
Device : Asus Transformer TF701T
Start at : Mon Aug 25 20:30:02 2014
Thank you for installing CROMi-Xenogenesis KitKat 4.4.2!
Sit back and relax...
-----------------------------------------------------
This will take a few minutes!
Preparing File System...
about to run program [/sbin/umount] with 3 args
umount: can't umount /system: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/umount] with 3 args
Formatting System....
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
Tuning System....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Tuning Data - Journaling Enabled.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Wiping Cache.....
Installing Core System.....
Installing Options...
Region Specific Files
- TF701 WW Build
Kernel Preparation
- sbdag's 11.4.1.17 Stock Modded Kernel
package_extract_file: no extras/kernel/sbmodded/701sb3.img in package
DPI Preparation
- 320 DPI
Resolution Preparation
- 2560x1600 res
Boot Animation
- Google Android-L
Launcher
- Asus Stock Launcher
Asus Apps 1
- Asus Email
- Asus Desk Clock & Widget
- Asus Weather & Time Widget
- Asus Splendid
- Asus Calculator
- Asus MyDictionary
- Asus Studio
Asus Apps 2
Google Apps 1
- Google Calendar
- Google Now and Voice Search
- Google Music
- News and Weather Genie
- YouTube
- Maps
- Hangouts
Google Apps 2
- Google Chrome
- Google Drive Docs
Misc Apps
- ES File Explorer
- AdAway installed
- Keyboard Manager
- Terminal Emulator
- Polaris Office
Installing CROMi-X System Tweaks.....
about to run program [/tmp/cromix-build-prop.sh] with 1 args
Tweaks and Scripts
- Browser2RAM enabled
- Ad Blocker enabled
- Zip Align Script installed
- Keyboard Dock Remapping installed
Building symlinks.....
Setting permissions.....
Installing BusyBox.....
about to run program [/system/xbin/busybox] with 4 args
Setting ROOT.....
DRM Options
- Google Video & Hulu+ DRM
Installing build.prop
about to run program [/sbin/sh] with 2 args
about to run program [/sbin/sh] with 2 args
Finalising ROM
about to run program [/sbin/umount] with 3 args
---------------------------------------
All Done!
Don't forget to follow @sbdags on Twitter
If you like it please donate to [email protected] on paypal
Enjoy CROMi-X!
script succeeded: result was [Enjoy CROMi-X!]
Installer Sucessfull (Status 0)
I don't know if this can be helpful, but if i restore the backup of the previous version of the rom everything work fine. I'm reading the discussion of the guy with the partition problem and i was wondering if maybe the problem was the same, but i don't think it.
Another time, sorry for bad english and thanks for all your work sdbags.
M.
That log is fine - everything is installed.
Read out the bootloader version from the bootloader screen to double check please.
Also you are rebooting after installing the bootloader and cwm package aren't you?
aMachi said:
If default option are those who are pre-selected on the aroma installer i've already try it.
Also i try to do it without point 3. Nothing
Here a log of the installation of the rom
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : CROMi-Xenogenesis KitKat
ROM Version : 7.0.2 DEODEX
ROM Author : sbdags
Device : Asus Transformer TF701T
Start at : Mon Aug 25 20:30:02 2014
Thank you for installing CROMi-Xenogenesis KitKat 4.4.2!
Sit back and relax...
-----------------------------------------------------
This will take a few minutes!
Preparing File System...
about to run program [/sbin/umount] with 3 args
umount: can't umount /system: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/umount] with 3 args
Formatting System....
Creating filesystem with parameters:
Size: 2147483648
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 8192
Label:
Blocks: 524288
Block groups: 16
Reserved block group size: 127
Created filesystem with 11/131072 inodes and 17193/524288 blocks
Tuning System....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Tuning Data - Journaling Enabled.....
about to run program [/tmp/tune2fs.ext4] with 6 args
tune2fs 1.41.12 (17-May-2010)
Wiping Cache.....
Installing Core System.....
Installing Options...
Region Specific Files
- TF701 WW Build
Kernel Preparation
- sbdag's 11.4.1.17 Stock Modded Kernel
package_extract_file: no extras/kernel/sbmodded/701sb3.img in package
DPI Preparation
- 320 DPI
Resolution Preparation
- 2560x1600 res
Boot Animation
- Google Android-L
Launcher
- Asus Stock Launcher
Asus Apps 1
- Asus Email
- Asus Desk Clock & Widget
- Asus Weather & Time Widget
- Asus Splendid
- Asus Calculator
- Asus MyDictionary
- Asus Studio
Asus Apps 2
Google Apps 1
- Google Calendar
- Google Now and Voice Search
- Google Music
- News and Weather Genie
- YouTube
- Maps
- Hangouts
Google Apps 2
- Google Chrome
- Google Drive Docs
Misc Apps
- ES File Explorer
- AdAway installed
- Keyboard Manager
- Terminal Emulator
- Polaris Office
Installing CROMi-X System Tweaks.....
about to run program [/tmp/cromix-build-prop.sh] with 1 args
Tweaks and Scripts
- Browser2RAM enabled
- Ad Blocker enabled
- Zip Align Script installed
- Keyboard Dock Remapping installed
Building symlinks.....
Setting permissions.....
Installing BusyBox.....
about to run program [/system/xbin/busybox] with 4 args
Setting ROOT.....
DRM Options
- Google Video & Hulu+ DRM
Installing build.prop
about to run program [/sbin/sh] with 2 args
about to run program [/sbin/sh] with 2 args
Finalising ROM
about to run program [/sbin/umount] with 3 args
---------------------------------------
All Done!
Don't forget to follow @sbdags on Twitter
If you like it please donate to [email protected] on paypal
Enjoy CROMi-X!
script succeeded: result was [Enjoy CROMi-X!]
Installer Sucessfull (Status 0)
I don't know if this can be helpful, but if i restore the backup of the previous version of the rom everything work fine. I'm reading the discussion of the guy with the partition problem and i was wondering if maybe the problem was the same, but i don't think it.
Another time, sorry for bad english and thanks for all your work sdbags.
M.
Click to expand...
Click to collapse
sbdags said:
That log is fine - everything is installed.
Read out the bootloader version from the bootloader screen to double check please.
Also you are rebooting after installing the bootloader and cwm package aren't you?
Click to expand...
Click to collapse
When i install cwm and bootloader package i reboot from cwm but i stuck in boot animation. The same that happen when i try to reboot after install the rom.
In bootloader screen i read
Android macallan-user BL released by WW_epad-11.4.1.17-20140711
aMachi said:
When i install cwm and bootloader package i reboot from cwm but i stuck in boot animation. The same that happen when i try to reboot after install the rom.
In bootloader screen i read
Android macallan-user BL released by WW_epad-11.4.1.17-20140711
Click to expand...
Click to collapse
Right and then you boot back to CWM, do a full wipe (you may need to wipe your internal sdcard so back it up first) and then flash the rom. After that it should boot fine.
If not please search xda for how to get a logcat and post one of it bootlooping please.
sbdags said:
Right and then you boot back to CWM, do a full wipe (you may need to wipe your internal sdcard so back it up first) and then flash the rom. After that it should boot fine.
If not please search xda for how to get a logcat and post one of it bootlooping please.
Click to expand...
Click to collapse
I try the first thing that you say but nothing, still loop in bootanimation.
I'll do a logcat through adb in the afternoon. Now i had some problem cause i can't mount usb storage through cwm for some reason. Late i'll find drivers or what's missing.
Maybe can help: when i reboot frequently cwm ask me if i want to fix root. It's normal?
Thanks you for your help.
aMachi said:
I try the first thing that you say but nothing, still loop in bootanimation.
I'll do a logcat through adb in the afternoon. Now i had some problem cause i can't mount usb storage through cwm for some reason. Late i'll find drivers or what's missing.
Maybe can help: when i reboot frequently cwm ask me if i want to fix root. It's normal?
Thanks you for your help.
Click to expand...
Click to collapse
That message is normal. Just a bug in CWM.
We need to find why you are bootlooping.
sbdags said:
That message is normal. Just a bug in CWM.
We need to find why you are bootlooping.
Click to expand...
Click to collapse
Ok, logcat is here.
Hope it can help.
aMachi said:
Ok, logcat is here.
Hope it can help.
Click to expand...
Click to collapse
OK You got some serious problems there. It would appear that your internal sdcard doesn't mount:
Code:
D/Vold ( 359): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.sdcard=/mnt/media_rw/sdcard"
D/Vold ( 359): Volume usbdrive state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.usbdrive=/mnt/media_rw/usbdrive"
I/Vold ( 359): opening the sysfs of TF701
E/Vold ( 359): lookupVolume usbdisk1 failed!
E/Vold ( 359): lookupVolume usbdisk2 failed!
E/Vold ( 359): lookupVolume sdreader failed!
D/Vold ( 359): checkUsbdisk sucess.
D/DirectVolume( 359): i:0 minor:48
D/Vold ( 359): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 359): i:1 minor:49
D/Vold ( 359): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
@lj50036, @_that any suggestions for this one?
@aMachi - what is the SKU of your device? And you can restore a nandroid back to 4.3 and it works fine?
sbdags said:
OK You got some serious problems there. It would appear that your internal sdcard doesn't mount:
Code:
D/Vold ( 359): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.sdcard=/mnt/media_rw/sdcard"
D/Vold ( 359): Volume usbdrive state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 359): *********** Success!! "ro.epad.mount_point.usbdrive=/mnt/media_rw/usbdrive"
I/Vold ( 359): opening the sysfs of TF701
E/Vold ( 359): lookupVolume usbdisk1 failed!
E/Vold ( 359): lookupVolume usbdisk2 failed!
E/Vold ( 359): lookupVolume sdreader failed!
D/Vold ( 359): checkUsbdisk sucess.
D/DirectVolume( 359): i:0 minor:48
D/Vold ( 359): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
D/DirectVolume( 359): i:1 minor:49
D/Vold ( 359): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
@lj50036, @_that any suggestions for this one?
@aMachi - what is the SKU of your device? And you can restore a nandroid back to 4.3 and it works fine?
Click to expand...
Click to collapse
i've some problem to find the SKU code. I search on the box of the tablet but there are too many codes and i don't know what's the right. Can you give me an exemple of it?
Yes, i can restore to 4.3. In this right moment i'm writing with the tab with cromix 6. Everything seems to work fine.
In case like this you really know how much important is to do a backup..
aMachi said:
i've some problem to find the SKU code. I search on the box of the tablet but there are too many codes and i don't know what's the right. Can you give me an exemple of it?
Yes, i can restore to 4.3. In this right moment i'm writing with the tab with cromix 6. Everything seems to work fine.
In case like this you really know how much important is to do a backup..
Click to expand...
Click to collapse
SKU is just your country code - so if you have changed it it could be causing issues with the clean install.
US, WW, TW, CN, JP are the only 5 I know of.
So if you changed the bootloader from US to WW I heard another user reporting some issues.
But in your case I am at a loss as to how you can boot 4.3 but not 4.4.2 as you are apparently on a 4.4.2 compatible bootloader and recovery .......
sbdags said:
SKU is just your country code - so if you have changed it it could be causing issues with the clean install.
US, WW, TW, CN, JP are the only 5 I know of.
So if you changed the bootloader from US to WW I heard another user reporting some issues.
But in your case I am at a loss as to how you can boot 4.3 but not 4.4.2 as you are apparently on a 4.4.2 compatible bootloader and recovery .......
Click to expand...
Click to collapse
Ah, right, i understand. I am WW, and i use it in every installation that i've done on my eee pad, from the rooting process and the unlocking of bootloader to the change of the rom.
Now that i am on the previous version of your rom those are infos of kernel, firmware, ecc.
Android Version 4.3
Kernel Version 3.4.57-g47dbe4d [email protected]#1
Tue Dec 17 23.26.15 CST 2013
Build Number TF701T_CROMi-Xenogenesis-6.1-WW_DEODEX-ORIGINAL-10.26.1.18 020115_201310210002
In ROM Manager i can see that my Recovery still is the 6.0.5.0 version.
In bootloader i can see that it is "WW_epad-11.4.1.17-20140711"
Hope that this might be helpful and hope that i don't write anything of unsafe.
M.
aMachi said:
Ah, right, i understand. I am WW, and i use it in every installation that i've done on my eee pad, from the rooting process and the unlocking of bootloader to the change of the rom.
Now that i am on the previous version of your rom those are infos of kernel, firmware, ecc.
Android Version 4.3
Kernel Version 3.4.57-g47dbe4d [email protected]#1
Tue Dec 17 23.26.15 CST 2013
Build Number TF701T_CROMi-Xenogenesis-6.1-WW_DEODEX-ORIGINAL-10.26.1.18 020115_201310210002
In ROM Manager i can see that my Recovery still is the 6.0.5.0 version.
In bootloader i can see that it is "WW_epad-11.4.1.17-20140711"
Hope that this might be helpful and hope that i don't write anything of unsafe.
M.
Click to expand...
Click to collapse
NO that is expected but hat is not expected is why you can't boot 4.4.2. Let's wait for _that and lj50036 to cast their expert eyes over your issues.
sbdags said:
@lj50036, @_that any suggestions for this one?
Click to expand...
Click to collapse
This seems to be the core of the problem:
Code:
E/dalvikvm(13002): JNI posting fatal error: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting...
Check that the framework is correctly installed and the BOOTCLASSPATH is set correctly:
Code:
adb shell echo $BOOTCLASSPATH > bootclasspath.txt
adb shell ls -l /system/framework > framework.txt
_that said:
This seems to be the core of the problem:
Code:
E/dalvikvm(13002): JNI posting fatal error: Native registration unable to find class 'com/android/internal/os/RuntimeInit'; aborting...
Check that the framework is correctly installed and the BOOTCLASSPATH is set correctly:
Code:
adb shell echo $BOOTCLASSPATH > bootclasspath.txt
adb shell ls -l /system/framework > framework.txt
Click to expand...
Click to collapse
Ok, so maybe now i need some help.
I run adb in my pc then i type adb shell to run the remote shell interactively.
Then what i need to type?
Anyway if i type "ls -l /system/framework > framework.txt" the response is "No such file or directory"
Sorry for my n00b questions. Really hope to learn something here, and give a chance to reward everyone for the help.
aMachi said:
Ok, so maybe now i need some help.
I run adb in my pc then i type adb shell to run the remote shell interactively.
Then what i need to type?
Anyway if i type "ls -l /system/framework > framework.txt" the response is "No such file or directory"
Sorry for my n00b questions. Really hope to learn something here, and give a chance to reward everyone for the help.
Click to expand...
Click to collapse
The commands were supposed to be typed as is on your computer. However I think I missed to quote the "echo $BOOTCLASSPATH" - I want the bootclasspath of your device, not of your PC.
Anyway, if you type "adb shell" first and then "ls -l /system/framework" and you get back "No such file or directory" that's strange...
_that said:
The commands were supposed to be typed as is on your computer. However I think I missed to quote the "echo $BOOTCLASSPATH" - I want the bootclasspath of your device, not of your PC.
Anyway, if you type "adb shell" first and then "ls -l /system/framework" and you get back "No such file or directory" that's strange...
Click to expand...
Click to collapse
Ok so tomorrow i'll give you the result of this test. I hope that i learn how to right use this command.
Any other thing that i can do?
aMachi said:
Ok so tomorrow i'll give you the result of this test. I hope that i learn how to right use this command.
Any other thing that i can do?
Click to expand...
Click to collapse
Post screenshots of your cmd window so that they can see the actual input/output
berndblb said:
Post screenshots of your cmd window so that they can see the actual input/output
Click to expand...
Click to collapse
No need for a graphical screenshot - you can copy the text from the console window.
I have been running the unofficial CM 12.1 release from April on my Tab S2 T-810 since that date.
The tablet has been fine - outside the limitations by that release - this morning, however, I found that I had lost WiFi access and have not been able to restore it. I have not downloaded any program updates, nor updated the system, and this seems to have happened overnight. The tablet had not turned off and showed 71% battery this morning. Rebooting the tablet has no effect. I am loath to reinstall CM since I will lose some of the information related to my setup.
Can this be a software bug? Is there another way of turning WiFi on besides through the CM settings such as using the command line in a terminal window? Any attempt to turn WiFi on in settings only results in "turning WiFi on..." displayed with no further activity. My tablet is rooted. By the way, Bluetooth seems to work.
@T_I
Hmm, how do I interpret your reply?
hga89 said:
Hmm, how do I interpret your reply?
Click to expand...
Click to collapse
Well this would have been a better question to ask in the CM thread.
Try CM13?
Lightn1ng said:
Well this would have been a better question to ask in the CM thread.
Try CM13?
Click to expand...
Click to collapse
I eventually first installed MM 6.0 and then CM 13.0 but WiFi cannot be turned on, then reverting to MM 6.0 to see if WiFi worked there but no luck.
Looks like a hardware problem but has anyone else encountered WiFi suddenly dying completely?
The warranty period is one year and I had had the tablet for almost exactly six months when this happened. Since I have both rooted the tablet and installed another ROM, initially CM 12, it seems it will not be covered?
Does anyone have experience getting warranty repairs on a rooted tablet?
hga89 said:
I eventually first installed MM 6.0 and then CM 13.0 but WiFi cannot be turned on, then reverting to MM 6.0 to see if WiFi worked there but no luck.
Looks like a hardware problem but has anyone else encountered WiFi suddenly dying completely?
The warranty period is one year and I had had the tablet for almost exactly six months when this happened. Since I have both rooted the tablet and installed another ROM, initially CM 12, it seems it will not be covered?
Does anyone have experience getting warranty repairs on a rooted tablet?
Click to expand...
Click to collapse
You might want to check with the dev of the cm13 ROM for the T810. He recently had a warrantee repair on his S2 with knox tripped. You can PM him here.
lewmur said:
You might want to check with the dev of the cm13 ROM for the T810. He recently had a warrantee repair on his S2 with knox tripped. You can PM him here.
Click to expand...
Click to collapse
Thank you, just did that. Samsung quoted me 9-11 days turnaround time for the repair of the WiFi...
I have the same problem, WIFI cannot be turned on
xyandxl said:
I have the same problem, WIFI cannot be turned on
Click to expand...
Click to collapse
Interesting. I have the T810, how about you? Are you on CM?
I spent almost one hour with a Samsung technician yesterday doing the following: force-stopping the two WiFi applications; booting into the recovery partition and wiping the cache; booting into safe mode and finally rebooting my own router on the technician's request. The latter, of course, had no bearing on the problem. The technician had not heard of this problem before.
None of the above worked and just to make sure this was not a CM problem I had - prior to contacting Samsung support - reinstalled stock 6.0 on the unit but it behaved no different.
A command-line tool to run on the unit to find the exact error code would be very helpful.
hga89 said:
Interesting. I have the T810, how about you? Are you on CM?
I spent almost one hour with a Samsung technician yesterday doing the following: force-stopping the two WiFi applications; booting into the recovery partition and wiping the cache; booting into safe mode and finally rebooting my own router on the technician's request. The latter, of course, had no bearing on the problem. The technician had not heard of this problem before.
None of the above worked and just to make sure this was not a CM problem I had - prior to contacting Samsung support - reinstalled stock 6.0 on the unit but it behaved no different.
A command-line tool to run on the unit to find the exact error code would be very helpful.
Click to expand...
Click to collapse
In response to another post I made, Ashyx suggested downloading syslog to check the logs. I will do so. Would be interesting if you could do the same.
Here are the mentions I could find of wifi in the logs using syslog. wifi could be found in last_kmsg.log, logcat.log and eventl.log. I am not used to reading android logs but in last_kmsg.log between lines 399 and 416 a Broadcom Dongle Host Driver is being initialized.
Ideas anyone? I should add that the below is when booting CM 13.
last_kmsg.log:397: [ 2.682373] ## wifi_probe
last_kmsg.log:398: [ 2.682586] wifi_set_power = 1
last_kmsg.log:399: [ 3.202178] wifi_set_carddetect = 1
last_kmsg.log:416: [ 3.378906] wifi_set_power = 0
logcat.log:2080: 08-10 12:57:53.610 I/acvpnagent(16328): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
logcat.log:4854: 08-10 13:00:08.532 I/acvpnagent(17178): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
event.log:360: 08-10 12:53:44.899 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848024710]
event.log:752: 08-10 12:55:47.258 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848147075]
event.log:1379: 08-10 12:58:13.172 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848293002]
Found 9 matches for "wifi".
hga89 said:
Here are the mentions I could find of wifi in the logs using syslog. wifi could be found in last_kmsg.log, logcat.log and eventl.log. I am not used to reading android logs but in last_kmsg.log between lines 399 and 416 a Broadcom Dongle Host Driver is being initialized.
Ideas anyone? I should add that the below is when booting CM 13.
last_kmsg.log:397: [ 2.682373] ## wifi_probe
last_kmsg.log:398: [ 2.682586] wifi_set_power = 1
last_kmsg.log:399: [ 3.202178] wifi_set_carddetect = 1
last_kmsg.log:416: [ 3.378906] wifi_set_power = 0
logcat.log:2080: 08-10 12:57:53.610 I/acvpnagent(16328): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
logcat.log:4854: 08-10 13:00:08.532 I/acvpnagent(17178): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
event.log:360: 08-10 12:53:44.899 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848024710]
event.log:752: 08-10 12:55:47.258 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848147075]
event.log:1379: 08-10 12:58:13.172 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848293002]
Found 9 matches for "wifi".
Click to expand...
Click to collapse
Did a further analysis of the various logs. I cannot find any messages tagged error or warning but it seems the Broadcom Dongle Host Driver is able to retrieve a MAC address for the WiFi card immediately followed by:
last_kmsg.log:416: [ 3.378906] wifi_set_power = 0
Any suggestions?
Please don't paste logs in posts.
Use Pastebin.com or upload the logs to Tinyupload.com.
If you upload them I can take a look.
Also you should be running complete stock.
Is your IMEI intact?
ashyx said:
Please don't paste logs in posts.
Use Pastebin.com or upload the logs to Tinyupload.com.
If you upload them I can take a look.
Also you should be running complete stock.
Is your IMEI intact?
Click to expand...
Click to collapse
Than you ashyx. I have now downloaded the zipped logs to http://s000.tinyupload.com/index.php?file_id=38641397716294966079. This is with CM 13 since I need root access to access the logs.
I cannot find an IMEI listing - or any in the About tablet and Status section where it is on my phone. Note that this is a Wifi-only tablet, T-810. On my phone I do have several fields with IMEI, IMEISV, and (cellular) network info, not so on the tablet, only the IP address (unavailable) and MAC address (all zeroes).
Note that I lost Wifi overnight without having installed any system update or any new software at all, it was just not connecting one morning...
hga89 said:
Than you ashyx. I have now downloaded the zipped logs to http://s000.tinyupload.com/index.php?file_id=38641397716294966079. This is with CM 13 since I need root access to access the logs.
I cannot find an IMEI listing - or any in the About tablet and Status section where it is on my phone. Note that this is a Wifi-only tablet, T-810. On my phone I do have several fields with IMEI, IMEISV, and (cellular) network info, not so on the tablet, only the IP address (unavailable) and MAC address (all zeroes).
Note that I lost Wifi overnight without having installed any system update or any new software at all, it was just not connecting one morning...
Click to expand...
Click to collapse
You should really go back to full stock firmware and then pull the logs.
No point trying to track down an issue that is caused by a custom OS.
ashyx said:
You should really go back to full stock firmware and then pull the logs.
No point trying to track down an issue that is caused by a custom OS.
Click to expand...
Click to collapse
OK, will do that and get the logs after rooting.
Before doing so today, I am, however, restoring the latest of the two nandroid backups I have to see if I can get the service back.
hga89 said:
OK, will do that and get the logs after rooting.
Before doing so today, I am, however, restoring the latest of the two nandroid backups I have to see if I can get the service back.
Click to expand...
Click to collapse
Just restored the latest of the two nandroid backups, which included restoring EFS and RADIO partitions. This backup was done /after/ I encountered the Wifi-issue. Restore went fine but no Wifi, I also see that I now have an IMEI field in Phone Settings/Status but that the field is blank.
I believe I have another nandroid from a long time ago when everything was working fine and I will figure out how to get that to the tablet and try a restore.
hga89 said:
Just restored the latest of the two nandroid backups, which included restoring EFS and RADIO partitions. This backup was done /after/ I encountered the Wifi-issue. Restore went fine but no Wifi, I also see that I now have an IMEI field in Phone Settings/Status but that the field is blank.
I believe I have another nandroid from a long time ago when everything was working fine and I will figure out how to get that to the tablet and try a restore.
Click to expand...
Click to collapse
The 2 are tied together. No IMEI usually means an EFS issue and therefore wifi and radio issues.
You really need that backup of the EFS.
ashyx said:
The 2 are tied together. No IMEI usually means an EFS issue and therefore wifi and radio issues.
You really need that backup of the EFS.
Click to expand...
Click to collapse
Just restored a nandroid backup I had made immediately after buying the tablet (Android 5) but restoring it, including the EFS and RADIO partitions did not restore Wifi-connectivity. I also tried "factory reset" from the OS but that also did not help.
I have now uploaded a syslog archive to http://s000.tinyupload.com/index.php?file_id=25506746479682944901.
Ashyx, thank you for looking at them.
Yesterday I used Odin to restore the nandroid backup I made before I rooted and installing a ROM. However, the Wifi problem persists, it cannot be turned on. Not sure the settings in Odin were correct: I used AP to restore and left the Auto-reboot and F. Reset Time checked which was the default. Was this correct?
I am using Odin 3.10.7 since I have to do this from a netbook running Vista Home and have no other Windows computer available. Does this make a difference?
Thank you.