I dont understand alot. Read the thread about IMEI, but still cant get IMEI. Can someone please make guide for newbie?
Why do you need IMEI? If it is for Swype, there are countless workarounds. If not, then, well, I'll post a guide. But I need which app, and the ROM.
Hey everyone. I was just hoping that I saw this thread here or I was going to make it. I have been through Dizzy's thread with jealousy and have tried a few different things but could never get it to work.
A step by step guide would be awesome and greatly appreciated.
I want it for HBO Go and a few games that need it to run. Thanks again if this is possible.
Alot of app in the market need IMEI to use. Like Zenonia, Tap Tap and others
The best (and also the original) guide is by DizzyDen and you can find that here: http://forum.xda-developers.com/showthread.php?t=1103766
Read through it carefully so you know what to expect.
Ok, but if some1 got time and can make a guide step by step it will be good. Not everybody know English so good, so thx.
DISCLAIMER: This is a quickie guide that's written down from memory, so please be very careful if you choose to follow these directions. Nothing I say here is better than what's already listed in Dizzy's very informative post, it's just a shortened version.
Dizzy's thread is here: http://forum.xda-developers.com/showthread.php?t=1103766
AGAIN, please be careful. What follows, while it worked wonderfully for me and others, may break your Nook. You've been duly warned.
If you find these steps useful to you at all, please go to Dizzy's thread and thank Dizzy for the program.
-Cheers
=======================================================
1. Install the Java JDK on your machine (assuming windows) by going here:
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
I use the Windows x86 one and that worked for me. YMMV.
2. Once Java is installed properly, download DizzyDen's IMEI zip file. I will not link it here, refer to the his/her original post to get the most up to date file.
3. Unzip the file into a directory somewhere convenient.
4. Go to your Nook and make sure you have the adbWireless app (download it from the market if you need to).
5. Run the adbWireless app and press the big green button. It will turn red and then show you an ip address. Make a note of this.
6. Launch Dizzy's IMEI program (!IMEIme.exe). At the dialog box "Do you want to use In-Place update features?" Answer YES.
7. The program will attempt ADB via USB and fail. Press OK.
8. At the next dialog box, enter the IPORT info from the adbWireless screen into this box.
9. Let it do it's thing. There may be other dialog boxes, I don't have my Nook with me right now to check, but they should be pretty obvious. When it's all done, the Nook should reboot and Dizzy's program will clean up after itself.
10. Now try out some of the IMEI required apps and see if they work.
Apps that worked for me once I did this:
XDA Free
Zenonia 3
Caligo Chasers
Mega Jump
fuul4nook said:
DISCLAIMER: This is a quickie guide that's written down from memory, so please be very careful if you choose to follow these directions. Nothing I say here is better than what's already listed in Dizzy's very informative post, it's just a shortened version.
Dizzy's thread is here: http://forum.xda-developers.com/showthread.php?t=1103766
AGAIN, please be careful. What follows, while it worked wonderfully for me and others, may break your Nook. You've been duly warned.
If you find these steps useful to you at all, please go to Dizzy's thread and thank Dizzy for the program.
-Cheers
=======================================================
1. Install the Java JDK on your machine (assuming windows) by going here:
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
I use the Windows x86 one and that worked for me. YMMV.
2. Once Java is installed properly, download DizzyDen's IMEI zip file. I will not link it here, refer to the his/her original post to get the most up to date file.
3. Unzip the file into a directory somewhere convenient.
4. Go to your Nook and make sure you have the adbWireless app (download it from the market if you need to).
5. Run the adbWireless app and press the big green button. It will turn red and then show you an ip address. Make a note of this.
6. Launch Dizzy's IMEI program (!IMEIme.exe). At the dialog box "Do you want to use In-Place update features?" Answer YES.
7. The program will attempt ADB via USB and fail. Press OK.
8. At the next dialog box, enter the IPORT info from the adbWireless screen into this box.
9. Let it do it's thing. There may be other dialog boxes, I don't have my Nook with me right now to check, but they should be pretty obvious. When it's all done, the Nook should reboot and Dizzy's program will clean up after itself.
10. Now try out some of the IMEI required apps and see if they work.
Apps that worked for me once I did this:
XDA Free
Zenonia 3
Caligo Chasers
Mega Jump
Click to expand...
Click to collapse
Very good write up... a couple of things...
7... if you edit the ini file after first run... set Use_ADB_USB = 0 you won't have to deal with that question... it will disable the usb function in my program.
8: you only have to enter the port number in that box if you change the default port in your adbwifi app... you can also set a default ip address : port in the ini file and it will have it pre-loaded in the ip input box.
Ok here is my ini settings [Settings]
Use_In_Place = 1
Use_Previous_Patch = 0
Use_Serial_Number = 0
Use_MAC_Address = 0
Use_Manual_Input = 1
Encrypt_IMEI = 0
Use_ADB = 1
Use_ADB(usb) = 0
Use_ADB(WiFi) = 1
Clean_Up = 1
WiFi_IP_Address = 192.168.2.100
IMEI = 4938567924
I try to write the Ip. It say Adb wifi failed. Then i try IPort. Failed agian. My Ip is 192.168.2.100. Try with 2 adb wifi app.
devil4eto said:
Ok here is my ini settings [Settings]
Use_In_Place = 1
Use_Previous_Patch = 0
Use_Serial_Number = 0
Use_MAC_Address = 0
Use_Manual_Input = 1
Encrypt_IMEI = 0
Use_ADB = 1
Use_ADB(usb) = 0
Use_ADB(WiFi) = 1
Clean_Up = 1
WiFi_IP_Address = 192.168.2.100
IMEI = 4938567924
I try to write the Ip. It say Adb wifi failed. Then i try IPort. Failed agian. My Ip is 192.168.2.100. Try with 2 adb wifi app.
Click to expand...
Click to collapse
what is your computer ip address? if it is not also in the 192.168.2.0 network... you have IP isolation on for wifi and the computer will not talk to the nook.
Ok it seem my PC IP is class A 78..... i use my neighbor wifi. Can i fix the problem somehow? Can i do it with USB adb? I try but get error... Sorry my English is not very good.
Hi Folks,
Another "no wifi" s4 here. This is a work colleagues phone that was totally stock. After upgrading to 4.4.2, wifi won't turn on. I've tried pretty much everything I've found on this site with regards to fixing it. The last thing that I hadn't looked at was the /persist folder (MMCBLK0P17). The one on this phone is empty and from what I've read, it should be populated. Could someone with a rooted i9505 post a list of the contents or better still, upload a copy of their /persist folder please?
TIA!
Mark
mjh74 said:
Hi Folks,
Another "no wifi" s4 here. This is a work colleagues phone that was totally stock. After upgrading to 4.4.2, wifi won't turn on. I've tried pretty much everything I've found on this site with regards to fixing it. The last thing that I hadn't looked at was the /persist folder (MMCBLK0P17). The one on this phone is empty and from what I've read, it should be populated. Could someone with a rooted i9505 post a list of the contents or better still, upload a copy of their /persist folder please?
TIA!
Mark
Click to expand...
Click to collapse
So what is everything found on this site with regards to fix it?
/persist folder is also empty on my phone.
mjh74 said:
Hi Folks,
Another "no wifi" s4 here. This is a work colleagues phone that was totally stock. After upgrading to 4.4.2, wifi won't turn on. I've tried pretty much everything I've found on this site with regards to fixing it. The last thing that I hadn't looked at was the /persist folder (MMCBLK0P17). The one on this phone is empty and from what I've read, it should be populated. Could someone with a rooted i9505 post a list of the contents or better still, upload a copy of their /persist folder please?
TIA!
Mark
Click to expand...
Click to collapse
Dial *#1234# and paste here what appears.
AP: I9505XXUGNG8
CP: I9505XXUGNG8
CSC: I9505BTUGNG2
So far I've tried the following:
Flashing the wifi-fix
Re-partitioning before flashing a stock rom
Rooting, Phillz recovery, clear dalvik, factory reset and format for new rom option before flashing various different 4.4.2 UK stock roms.
Editing build.prop and changing "ro.securestorage.support=true" to false.
Removing the back, removing and replacing the antenna wire.
Flashing a CM11 nightly.
Deleting wpa_supplicant.conf
Dmesg shows some interesting stuff.
"<4>[ 1277.591125] ## wifi_remove
<4>[ 1277.591125] wifi_set_power = 0
<4>[ 1277.591156] ####btlock released, cookie: WiFi
<6>[ 1277.591156] ------------------------------------------------
<6>[ 1277.591156] ------------------------------------------------
<6>[ 1277.591156] brcm_wlan_power Enter: power off
<6>[ 1277.591186] barcode_emul_ice4: ice_gpiox_set : num = 3 , val = 0
<7>[ 1277.592590] usb 1-1: usb wakeup-resume
<7>[ 1277.592651] usb 1-1: finish resume
<7>[ 1277.599456] hub 1-0:1.0: resume on port 1, status 0
<7>[ 1277.599487] hub 1-0:1.0: port 1, status 0503, change 0004, 480 Mb/s
<6>[ 1277.727569] [email protected] 42
<6>[ 1277.732635] set_freq_limit: 0x1 -1, min 384000, max 1350000
<4>[ 1277.822662] wifi_set_carddetect = 0
<4>[ 1277.822692] brcm_wifi_status:298 status 0
<6>[ 1277.822692] mmc1: Slot status change detected (1 -> 0)
<4>[ 1277.823638]
<4>[ 1277.823638] failed to power up wifi chip, max retry reached, exits **"
As I'm typing this, the phone has a stock rom and isn't rooted. I've just rooted again with CF-ROOT and Odin, rebooted the phone and wifi enabled instantly, something I've not seen before! It was the first boot and SuperSU wanted to update and reboot. After the reboot, wifi will no longer come on again.
I See you have the same error as I'm having:
Code:
<6>[ 1277.822692] mmc1: Slot status change detected (1 -> 0)
Can you check dmesg for mmc1 CRC errors and post output here?
ajax505 said:
I See you have the same error as I'm having:
Code:
<6>[ 1277.822692] mmc1: Slot status change detected (1 -> 0)
Can you check dmesg for mmc1 CRC errors and post output here?
Click to expand...
Click to collapse
Here you go.
mjh74 said:
Here you go.
Click to expand...
Click to collapse
So after pretty much giving up and weeks of flashing and faffing around. I managed to get wifi enabled. I've no idea how but I went from stock rom XXUGNG2, rooted with CF-AUTO-ROOT, Phillz recovery installed and a Cyanogen nightly and no wifi. Flashed XXUGNG2 back to the phone and wifi sprung into life! I then flashed XXUGNG8 and wifi still worked! I then performed a factory reset from Backup & Reset and wifi hasn't worked again since!?!?
So I'm not so convinced now that it's a hardware issue as I first thought.....
Lucky you I tried every possible solution. The interesting thing is that if I flash stock I can see Wifi mac, toggle button is "alive" but wifi won't turn on. If I flash cyanogen, wifi mac is not available and the wifi button is gray saying "turning wifi on" like forever.
ajax505 said:
Lucky you I tried every possible solution. The interesting thing is that if I flash stock I can see Wifi mac, toggle button is "alive" but wifi won't turn on. If I flash cyanogen, wifi mac is not available and the wifi button is gray saying "turning wifi on" like forever.
Click to expand...
Click to collapse
Like you, I'm back at exactly the same place. Cyanogen won't even let me turn wifi on now, the button is grayed out and says "turning wifi on". Stock roms show a pale green wifi signal icon until it turns gray again and fails. Arghhh how did I get it working briefly?!
mjh74 said:
So after pretty much giving up and weeks of flashing and faffing around. I managed to get wifi enabled. I've no idea how but I went from stock rom XXUGNG2, rooted with CF-AUTO-ROOT, Phillz recovery installed and a Cyanogen nightly and no wifi. Flashed XXUGNG2 back to the phone and wifi sprung into life! I then flashed XXUGNG8 and wifi still worked! I then performed a factory reset from Backup & Reset and wifi hasn't worked again since!?!?
So I'm not so convinced now that it's a hardware issue as I first thought.....
Click to expand...
Click to collapse
mjh74 said:
Like you, I'm back at exactly the same place. Cyanogen won't even let me turn wifi on now, the button is grayed out and says "turning wifi on". Stock roms show a pale green wifi signal icon until it turns gray again and fails. Arghhh how did I get it working briefly?!
Click to expand...
Click to collapse
When people learn that means "nightly" with CM?
Looking through the June security bulletin and found this https://www.exploit-db.com/exploits/39921/. I downloaded it from the source, and it cam with a compiled PoC. I ran it and it seemed to work, but I don't know exactly what it is doing. Here is a log of what the code gives me after being run:
127|[email protected]:/data/local/tmp $ ./sdcard_poc
[*] sdcard off-by-one poc
[*] getting everything ready...
- creating 16 small entries
- creating large entries
- adjusting pad_1 entry
rename_pad_1(1, 2)
rename_pad_1(2, 1)
- resizing overflow entries
rename_overflows(255)
[*] triggering!
rename_pad_2(1, 2)
rename_pad_2(2, 3)
rename_pad_2(3, 4)
rename_pad_2(4, 5)
rename_pad_2(5, 6)
rename_pad_2(6, 7)
rename_pad_2(7, 8)
rename_pad_2(8, 9)
rename_pad_2(9, 10)
rename_pad_2(10, 11)
rename_pad_2(11, 12)
rename_pad_2(12, 13)
rename_pad_2(13, 14)
rename_pad_2(14, 15)
rename_pad_2(15, 16)
rename_pad_2(16, 17)
rename_pad_2(17, 18)
rename_pad_2(18, 19)
rename_pad_2(19, 20)
rename_pad_2(20, 21)
rename_pad_2(21, 22)
rename_pad_2(22, 23)
rename_pad_2(23, 24)
rename_pad_2(24, 25)
rename_pad_2(25, 26)
rename_pad_2(26, 27)
rename_pad_2(27, 28)
rename_pad_2(28, 29)
rename_pad_2(29, 30)
rename_pad_2(30, 31)
rename_pad_2(31, 32)
rename_pad_2(32, 33)
rename_pad_2(33, 34)
rename_pad_2(34, 35)
rename_pad_2(35, 36)
rename_pad_2(36, 37)
rename_pad_2(37, 38)
rename_pad_2(38, 39)
rename_pad_2(39, 40)
rename_pad_2(40, 41)
rename_pad_2(41, 42)
rename_pad_2(42, 43)
rename_pad_2(43, 44)
rename_pad_2(44, 45)
rename_pad_2(45, 46)
rename_pad_2(46, 47)
rename_pad_2(47, 48)
rename_pad_2(48, 49)
rename_pad_2(49, 50)
rename_pad_2(50, 51)
rename_pad_2(51, 52)
rename_pad_2(52, 53)
rename_pad_2(53, 54)
rename_pad_2(54, 55)
rename_pad_2(55, 56)
rename_pad_2(56, 57)
rename_pad_2(57, 58)
rename_pad_2(58, 59)
rename_pad_2(59, 60)
rename_pad_2(60, 61)
rename_pad_2(61, 62)
rename_pad_2(62, 63)
rename_pad_2(63, 64)
rename_pad_2(64, 65)
rename_pad_2(65, 66)
rename_pad_2(66, 67)
rename_pad_2(67, 68)
rename_pad_2(68, 69)
rename_pad_2(69, 70)
rename_pad_2(70, 71)
rename_pad_2(71, 72)
rename_pad_2(72, 73)
rename_pad_2(73, 74)
rename_pad_2(74, 75)
rename_pad_2(75, 76)
rename_pad_2(76, 77)
rename_pad_2(77, 78)
rename_pad_2(78, 79)
rename_pad_2(79, 80)
rename_pad_2(80, 81)
rename_pad_2(81, 82)
rename_pad_2(82, 83)
rename_pad_2(83, 84)
rename_pad_2(84, 85)
rename_pad_2(85, 86)
rename_pad_2(86, 87)
rename_pad_2(87, 88)
rename_pad_2(88, 89)
rename_pad_2(89, 90)
rename_pad_2(90, 91)
rename_pad_2(91, 92)
rename_pad_2(92, 93)
rename_pad_2(93, 94)
rename_pad_2(94, 95)
rename_pad_2(95, 96)
rename_pad_2(96, 97)
rename_pad_2(97, 98)
rename_pad_2(98, 99)
rename_pad_2(99, 100)
rename_pad_2(100, 101)
rename_pad_2(101, 102)
rename_pad_2(102, 103)
rename_pad_2(103, 104)
rename_pad_2(104, 105)
rename_pad_2(105, 106)
rename_pad_2(106, 107)
rename_pad_2(107, 108)
rename_pad_2(108, 109)
rename_pad_2(109, 110)
rename_pad_2(110, 111)
rename_pad_2(111, 112)
rename_pad_2(112, 113)
rename_pad_2(113, 114)
rename_pad_2(114, 115)
rename_pad_2(115, 116)
rename_pad_2(116, 117)
rename_pad_2(117, 118)
rename_pad_2(118, 119)
rename_pad_2(119, 120)
rename_pad_2(120, 121)
rename_pad_2(121, 122)
rename_pad_2(122, 123)
rename_pad_2(123, 124)
rename_pad_2(124, 125)
rename_pad_2(125, 126)
rename_pad_2(126, 127)
rename_pad_2(127, 128)
rename_pad_2(128, 129)
rename_pad_2(129, 130)
rename_pad_2(130, 131)
rename_pad_2(131, 132)
rename_pad_2(132, 133)
rename_pad_2(133, 134)
rename_pad_2(134, 135)
rename_pad_2(135, 136)
rename_pad_2(136, 137)
rename_pad_2(137, 138)
rename_pad_2(138, 139)
rename_pad_2(139, 140)
rename_pad_2(140, 141)
rename_pad_2(141, 142)
rename_pad_2(142, 143)
rename_pad_2(143, 144)
rename_pad_2(144, 145)
rename_pad_2(145, 146)
rename_pad_2(146, 147)
rename_pad_2(147, 148)
rename_pad_2(148, 149)
rename_pad_2(149, 150)
rename_pad_2(150, 151)
rename_pad_2(151, 152)
rename_pad_2(152, 153)
rename_pad_2(153, 154)
rename_pad_2(154, 155)
rename_pad_2(155, 156)
rename_pad_2(156, 157)
rename_pad_2(157, 158)
rename_pad_2(158, 159)
rename_pad_2(159, 160)
rename_pad_2(160, 161)
rename_pad_2(161, 162)
rename_pad_2(162, 163)
rename_pad_2(163, 164)
rename_pad_2(164, 165)
rename_pad_2(165, 166)
rename_pad_2(166, 167)
rename_pad_2(167, 168)
rename_pad_2(168, 169)
rename_pad_2(169, 170)
rename_pad_2(170, 171)
rename_pad_2(171, 172)
rename_pad_2(172, 173)
rename_pad_2(173, 174)
rename_pad_2(174, 175)
rename_pad_2(175, 176)
rename_pad_2(176, 177)
rename_pad_2(177, 178)
rename_pad_2(178, 179)
rename_pad_2(179, 180)
rename_pad_2(180, 181)
rename_pad_2(181, 182)
rename_pad_2(182, 183)
rename_pad_2(183, 184)
rename_pad_2(184, 185)
rename_pad_2(185, 186)
rename_pad_2(186, 187)
rename_pad_2(187, 188)
rename_pad_2(188, 189)
rename_pad_2(189, 190)
rename_pad_2(190, 191)
rename_pad_2(191, 192)
rename_pad_2(192, 193)
rename_pad_2(193, 194)
rename_pad_2(194, 195)
rename_pad_2(195, 196)
rename_pad_2(196, 197)
rename_pad_2(197, 198)
rename_pad_2(198, 199)
rename_pad_2(199, 200)
rename_pad_2(200, 201)
rename_pad_2(201, 202)
rename_pad_2(202, 203)
rename_pad_2(203, 204)
rename_pad_2(204, 205)
rename_pad_2(205, 206)
rename_pad_2(206, 207)
rename_pad_2(207, 208)
rename_pad_2(208, 209)
rename_pad_2(209, 210)
rename_pad_2(210, 211)
rename_pad_2(211, 212)
rename_pad_2(212, 213)
rename_pad_2(213, 214)
rename_pad_2(214, 215)
rename_pad_2(215, 216)
rename_pad_2(216, 217)
rename_pad_2(217, 218)
rename_pad_2(218, 219)
rename_pad_2(219, 220)
rename_pad_2(220, 221)
rename_pad_2(221, 222)
rename_pad_2(222, 223)
rename_pad_2(223, 224)
rename_pad_2(224, 225)
rename_pad_2(225, 226)
rename_pad_2(226, 227)
rename_pad_2(227, 228)
rename_pad_2(228, 229)
rename_pad_2(229, 230)
rename_pad_2(230, 231)
rename_pad_2(231, 232)
rename_pad_2(232, 233)
rename_pad_2(233, 234)
rename_pad_2(234, 235)
rename_pad_2(235, 236)
rename_pad_2(236, 237)
rename_pad_2(237, 238)
rename_pad_2(238, 239)
rename_pad_2(239, 240)
rename_pad_2(240, 241)
rename_pad_2(241, 242)
rename_pad_2(242, 243)
rename_pad_2(243, 244)
rename_pad_2(244, 245)
rename_pad_2(245, 246)
rename_pad_2(246, 247)
rename_pad_2(247, 248)
rename_pad_2(248, 249)
rename_pad_2(249, 250)
rename_pad_2(250, 251)
rename_pad_2(251, 252)
rename_pad_2(252, 253)
rename_pad_2(253, 254)
255|[email protected]:/data/local/tmp $
I am not sure what steps to take next, can anyone offer any help? This seems to be pretty promising as it actual works for once.
I tried that and I think it only gains System Privelleges. But honestly I really haven't seen any change. I even checked with id. Still was 2000 as usual.
NavSad said:
I tried that and I think it only gains System Privelleges. But honestly I really haven't seen any change. I even checked with id. Still was 2000 as usual.
Click to expand...
Click to collapse
So is this useless? I'm just kind of confused on what this does exactly...
It did some weird stuff to my phone, and I ended up having to factory reset. It seemed to have completely wiped the quick settings feature, and everything was back to the factory settings except for the apps that I had downloaded before
Honestly Annoying said:
So is this useless? I'm just kind of confused on what this does exactly...
Click to expand...
Click to collapse
I think someone would need to put some code into it that could inject system permission. Otherwise it's just a buffer overflow.
NavSad said:
I think someone would need to put some code into it that could inject system permission. Otherwise it's just a buffer overflow.
Click to expand...
Click to collapse
Yeah that makes sense...
In the meantime, check this out: https://www.exploit-db.com/exploits/39340/
Honestly Annoying said:
Yeah that makes sense...
In the meantime, check this out: https://www.exploit-db.com/exploits/39340/
Click to expand...
Click to collapse
I think this exploit could be patched because it was published in Janurary. But here's another exploit: http://www.cvedetails.com/cve/CVE-2016-3135/. Just need someone to port it over.
NavSad said:
I think this exploit could be patched because it was published in Janurary. But here's another exploit: http://www.cvedetails.com/cve/CVE-2016-3135/. Just need someone to port it over.
Click to expand...
Click to collapse
The thing about this exploit is that it was never assigned an official CVE, so it could have gone unnoticed.
And I'll check that one out. I've ported them over before. Is there a download link for it?
NavSad said:
I think this exploit could be patched because it was published in Janurary. But here's another exploit: http://www.cvedetails.com/cve/CVE-2016-3135/. Just need someone to port it over.
Click to expand...
Click to collapse
Also, this is an OLD root exploit that used a buffer overflow http://security.stackexchange.com/questions/68442/escalating-from-apache-shell-to-root/68482#68482
Honestly Annoying said:
The thing about this exploit is that it was never assigned an official CVE, so it could have gone unnoticed.
And I'll check that one out. I've ported them over before. Is there a download link for it?
Click to expand...
Click to collapse
Yes there is. https://bugs.chromium.org/p/project-zero/issues/detail?id=758&redir=1
NavSad said:
Yes there is. https://bugs.chromium.org/p/project-zero/issues/detail?id=758&redir=1
Click to expand...
Click to collapse
Yeah I just saw that... I'm trying right now but there's only a .c file. I'll see what I can do
I really appreciate you guys trying to get root, I wish I could do the same but I have no idea what to do.
NavSad said:
I think this exploit could be patched because it was published in Janurary. But here's another exploit: http://www.cvedetails.com/cve/CVE-2016-3135/. Just need someone to port it over.
Click to expand...
Click to collapse
I believe that I have ported the CVE over.
I have two different files, one of them gives an "unshare: Invalid argument" error. In the other file, I just deleted the lines that had "unshare" in them and recompiled it. This one seems to run the right way, but I don't exactly know what to do with it. Why did you say this CVE would work? And what can I do to see if it is working for me?
Honestly Annoying said:
I believe that I have ported the CVE over.
I have two different files, one of them gives an "unshare: Invalid argument" error. In the other file, I just deleted the lines that had "unshare" in them and recompiled it. This one seems to run the right way, but I don't exactly know what to do with it. Why did you say this CVE would work? And what can I do to see if it is working for me?
Click to expand...
Click to collapse
I said I thought it might work because Android and Linux share the same kernel, so problems can be ported over. Try adding some code that can inject root after the exploit is finished, maybe that could work.
Would adding something that would run "chmod 777 /data" work? If it is something like that it should be no problem
NavSad said:
I said I thought it might work because Android and Linux share the same kernel, so problems can be ported over. Try adding some code that can inject root after the exploit is finished, maybe that could work.
Click to expand...
Click to collapse
Would adding something that would run "chmod 777 /data" work? If it is something like that it should be no problem
Honestly Annoying said:
Would adding something that would run "chmod 777 /data" work? If it is something like that it should be no problem
Click to expand...
Click to collapse
Yeah put the file in data/local/tmp and do chmod 777.
NavSad said:
Yeah put the file in data/local/tmp and do chmod 777.
Click to expand...
Click to collapse
No I mean adding to the code. How can I get this to open a root shell?
Honestly Annoying said:
Would adding something that would run "chmod 777 /data" work? If it is something like that it should be no problem
Click to expand...
Click to collapse
I think he wanted to use the exploit to change the root folder's permissions to read write execute and then inject a su binary via file manager, and wanted to know if that would work... :/
MadnessChi1d said:
I think he wanted to use the exploit to change the root folder's permissions to read write execute and then inject a su binary via file manager, and wanted to know if that would work... :/
Click to expand...
Click to collapse
? I want to add code to the .c file to execute an exploit
Hi guys;
I found a way to enable the double tap to wake up in LineageOS and RR for the mi mix.
Here it comes:
1: Donwload the Root Explorer and the QuickEdit;
2: With Root Explorer, go to sys/bus/i2c/12-0038/wakeup-mode;
3: Open that with Quick Edit and change the value "0" to "1";
4: Save it;
5: Have fun.
This is my first post here, take easy guys. I searched here for a solution for this problem, but didn't find anything about this two roms.
Thanks if it works!
PS: The only problem is that when you reboot the system, the system automatically returns to "0", so you will have to do the whole process again every time you restart the device. Does anyone know the solution to leave this fixed by default?
I'll add that to init process in ramdisk and enable it in source again. In build 0412 it is disabled, but it seems to work anyway Thx for finding it out.
pappschlumpf said:
I'll add that to init process in ramdisk and enable it in source again. In build 0412 it is disabled, but it seems to work anyway Thx for finding it out.
Click to expand...
Click to collapse
No problem! This is a tweak that I cant live without! And, congratulations for the amazing job. The ROM is perfect to me, Im using as my daily driver. The only 2 problens that I found, is this one and the low volume in Calls. Thanks to provide this ROM, I really appreciated.
Great! Is working fine...
Hello ,
works fine , but after reboot it is back to"0"
mfg , hjf
hjfisch said:
Hello ,
works fine , but after reboot it is back to"0"
mfg , hjf
Click to expand...
Click to collapse
As I said
Couldn't i just change the value and save the file as read only? I'm kind of afraid to try it out but wouldn't that work?
Blackphantom said:
Couldn't i just change the value and save the file as read only? I'm kind of afraid to try it out but wouldn't that work?
Click to expand...
Click to collapse
Will work. Just change the value to 1, save and exit. But, every time that you reboot the device, u will need make the process again.
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Blackphantom said:
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Click to expand...
Click to collapse
Dont know. Could you try and post the result?
Blackphantom said:
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Click to expand...
Click to collapse
NO, as /sys is just a mountpoint for a virtual Filesystem (type sysfs)
So basically, everything under /sys/ is virtual, so no real Files, so no persistance after a reboot. At least not by interacting with sysfs.
This is the Linux way of making runtime live adaptations of certain hardware or software features.
Let me give you an example.
On a regular Dektop-Linux, if you do:
>> echo "1" > /sys/block/sda/device/delete
on the command line, you tell the kernel to flush the caches of the sda disk and spin it down. (so you could safely hotswap)
and if you do not replace your disk, but now want to get that disk spinning again, you put:
>> echo "0 0 0" > /sys/bus/scsi/devices/host1/scsi_host/host1/scan
into console.
So some of the Files there are read only (in like nothing happens when you change the content) , and others can be tampered with, but every change is gone after reboot.
except when you can manage to let some startup-skript make those changes, or you can edit the kernel-source default initialisation variables.
rootgremlin said:
NO, as /sys is just a mountpoint for a virtual Filesystem (type sysfs)
So basically, everything under /sys/ is virtual, so no real Files, so no persistance after a reboot. At least not by interacting with sysfs.
This is the Linux way of making runtime live adaptations of certain hardware or software features.
Let me give you an example.
On a regular Dektop-Linux, if you do:
>> echo "1" > /sys/block/sda/device/delete
on the command line, you tell the kernel to flush the caches of the sda disk and spin it down. (so you could safely hotswap)
and if you do not replace your disk, but now want to get that disk spinning again, you put:
>> echo "0 0 0" > /sys/bus/scsi/devices/host1/scsi_host/host1/scan
into console.
So some of the Files there are read only (in like nothing happens when you change the content) , and others can be tampered with, but every change is gone after reboot.
except when you can manage to let some startup-skript make those changes, or you can edit the kernel-source default initialisation variables.
Click to expand...
Click to collapse
Yeah that makes sense. I tried it and realized that it was set back to zero every time i restarted so i figured it would be something like that. Luckily DT2W works now in the build so we don't have to do that anymore.
Thanks for the explanation though. Really appreciated.
Hey there
i followed your steps but i cant seem to find the 12-0038 folder after i2c. Any thoughts?
If you're using Lineage just install the DragonXiaKernel. Double Tap To Wake is working fine.
Tiago A said:
Hi guys;
I found a way to enable the double tap to wake up in LineageOS and RR for the mi mix.
Here it comes:
1: Donwload the Root Explorer and the QuickEdit;
2: With Root Explorer, go to sys/bus/i2c/12-0038/wakeup-mode;
3: Open that with Quick Edit and change the value "0" to "1";
4: Save it;
5: Have fun.
This is my first post here, take easy guys. I searched here for a solution for this problem, but didn't find anything about this two roms.
Thanks if it works!
PS: The only problem is that when you reboot the system, the system automatically returns to "0", so you will have to do the whole process again every time you restart the device. Does anyone know the solution to leave this fixed by default?
Click to expand...
Click to collapse
I installed "lineage-14.1-20170415-UNOFFICIAL-X3". I only get path till sys/bus/i2c/
There is no 12-0038/ folder. Can you help me out on this? I need it badly.
same here, no 12-0038
running smooth with 14.1-20170725-NIGHTLY-hammerhead though
Same for me on 14.1 LG g4 can't t find the file
Ls .../i2c/devices/
0-0006
0-a004
0-a006
1-0051
10-0048
11-003b
...
There iz no 12-0038 in both /i2c/ and /i2c/devices/
:crying:
Vipxpert said:
Ls .../i2c/devices/
0-0006
0-a004
0-a006
1-0051
10-0048
11-003b
...
There iz no 12-0038 in both /i2c/ and /i2c/devices/
:crying:
Click to expand...
Click to collapse
DT2W is working in RR (Oreo) just fine and I assume it's the same for Lineage 15.1 (Oreo). Which ROM are you using?
gavin19 said:
DT2W is working in RR (Oreo) just fine and I assume it's the same for Lineage 15.1 (Oreo). Which ROM are you using?
Click to expand...
Click to collapse
RR oreo as u said !