Related
Hey,
So I received the Nexus 10 this morning, signed into my Google account, downloaded a few app updates, then it said the 4.2.2 update was ready. I let it install and reboot, but ever since touch is not working at all on the device. It boots fine, but it won't unlock as it doesn't register the touch.
I've used the Recovery menu to restore it to factory defaults, which it did, but touch still doesn't work (I can't change language etc). I've downloaded the official 4.2.2 ROM, the SDK, installed the USB drivers, but ADB Devices doesn't find it. I guess this is because I can't enable Debugging Mode.
Can anyone offer some advice? Yes, I could return the tablet to Google, but I head back to the Middle East in a few days and I should imagine the turn around time will be much longer than that.
I'm happy to install any custom kernel, recovery mode etc. to try and restore it. When booted, Windows Explorer will allow me access.
I've Googled as much as I can, but most things rely on being able to enable the ADB link.
Many thanks.
You dont need ADB to install the stock firmware, it uses Fastboot. See here:
http://nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/
EniGmA1987 said:
You dont need ADB to install the stock firmware, it uses Fastboot. See here:
http://nexus10root.com/nexus-10-unroot/how-to-unrootunbrick-nexus-10-factory-firmware/
Click to expand...
Click to collapse
Thank you for your help. Although the above process did re-flash the tablet with the downloaded 4.2.2 firmware, the touch screen is still not accepting any input.
Google only host the 4.2.2 image on their site, but the post here: http://forum.xda-developers.com/showthread.php?t=2003731 has the 4.2 version. I shall download that and try again.
Sinker_UK said:
Thank you for your help. Although the above process did re-flash the tablet with the downloaded 4.2.2 firmware, the touch screen is still not accepting any input.
Google only host the 4.2.2 image on their site, but the post here: http://forum.xda-developers.com/showthread.php?t=2003731 has the 4.2 version. I shall download that and try again.
Click to expand...
Click to collapse
4.2 downloaded and flashed; still no joy.
I guess this will have to go back to Google / Samsung. I don't know what the 4.2.2 update did, but it appears to have completely killed the touch screen!
Sinker_UK said:
Hey,
So I received the Nexus 10 this morning, signed into my Google account, downloaded a few app updates, then it said the 4.2.2 update was ready. I let it install and reboot, but ever since touch is not working at all on the device. It boots fine, but it won't unlock as it doesn't register the touch.
I've used the Recovery menu to restore it to factory defaults, which it did, but touch still doesn't work (I can't change language etc). I've downloaded the official 4.2.2 ROM, the SDK, installed the USB drivers, but ADB Devices doesn't find it. I guess this is because I can't enable Debugging Mode.
Can anyone offer some advice? Yes, I could return the tablet to Google, but I head back to the Middle East in a few days and I should imagine the turn around time will be much longer than that.
I'm happy to install any custom kernel, recovery mode etc. to try and restore it. When booted, Windows Explorer will allow me access.
I've Googled as much as I can, but most things rely on being able to enable the ADB link.
Many thanks.
Click to expand...
Click to collapse
Sorry for not providing any help, however it's a bit strange that flashing a firmware break the screen.
I just received my tab yesterday then flash 4.2.2 OTA without any issues
FredC94 said:
Sorry for not providing any help, however it's a bit strange that flashing a firmware break the screen.
I just received my tab yesterday then flash 4.2.2 OTA without any issues
Click to expand...
Click to collapse
Please don't worry about not providing any help; I appreciate that this one is an oddity. I was just hoping that the OTA had goosed the drivers or some-such, and that re-flashing it would help, but alas no.
Grab the original stock image 4.2.1 and try flashing back to that. Never heard of this before!
brees75 said:
Grab the original stock image 4.2.1 and try flashing back to that. Never heard of this before!
Click to expand...
Click to collapse
Well, as above, I tried the original 4.2 and that didn't work. I haven't seen the 4.2.1 image anywhere, but can't believe that would make a difference when the other two haven't. I've also just tried a touch-based recovery and that also doesn't respond to touches (TWRP). Oh well. :crying:
I'm at a loss of what to do now so will have to send it back. Pity, it was great when it did work!
Thanks for all the help.
I've contacted Google Play. They went through a reset then agreed to replace it. Will return it as faulty for a refund, and purchase another to save time. 32GB this time, seeing as they are now in stock!
Sent from my GT-N7000 using XDA Premium HD app
Phewwwww...scary...The 4.2.2 has been sitting on my task bar forever now but I am still resisting actually installing it. This thread might scare me away even more...Why fix things if they are not broken.
A better topic for your post: "My touch screen happened to stop working after I installed the 4.2.2 OTA" .. but it may not have caused it.
Hardware can break at any time.
I'm holding off on letting 4.2.2 install itself because I read that it breaks Adblock in Firefox. Not sure what 4.2.2 will do for me, but I want Adblock to work!
Edit to add: also just read the thread here about 4.2.2 causing sloooow scrolling problems in Firefox. So if you use Firefox, don't let 4.2.2 install!
I own the Sprint LG LS980. I bought it 2 weeks ago, and Unlocked it following this guide http://forum.xda-developers.com/showthread.php?t=2655133 and then changing the build.prop to:
ro.build.target_operator=spr
ro.carrier=spr
persist.service.crash.enable=1
This has let me use the Sprint LG G2 on AT&T for 2 weeks.
The only caveats I found were:
-LTE doesn't work
-Had to set my apn using Tweakker https://play.google.com/store/apps/details?id=com.tweakker
-Wifi right after boot wouldn't turn on (has happened twice in 2 weeks) Reset to fix.
-Ugly GSM with a circle around it logo instead of H+ or LTE or H (found a link stating to erase the value and leave blank in my ro.build.targer_operator, and it changed the logo to "H" but it started crashing all the time. I changed it back to spr)
On 4.4.2 stock rooted rom
Everything has been working great until all of a sudden my phone will be working until it times out or I use knock on to turn the screen off. The screen turns off, but when I try to turn the screen on, there are horizontal lines all over. The touch screen still works though. I have to hard reset it, and then my screen works fine again until I turn the screen off again. Same issue. Same result when I reboot.
I took a video. http://youtu.be/3Erj3ETbECo
Also, something weird. I flashed a stock based rom (Cloudy) and it shows the same behavior in the video. I then flashed AOKP and it works perfectly. I can turn the screen off and on.
Is there something someone knows how I can get my stock rom working? Should I just try and go back to stock using whatever TOT is? Thanks for your help.
You have to flash Cloudyfa's fix for our phones. For some reason we have to have the stock kernel or we are going to get the lines bug. That also means we will lose recovery though.. It fixed it for me though. How did you unlock your phone exaclty? I tried to change my apn to tmobile on a 4.4 lg rom (cloudyflex) but it kept crashing my systemui
juanacevedo said:
You have to flash Cloudyfa's fix for our phones. For some reason we have to have the stock kernel or we are going to get the lines bug. That also means we will lose recovery though.. It fixed it for me though. How did you unlock your phone exaclty? I tried to change my apn to tmobile on a 4.4 lg rom (cloudyflex) but it kept crashing my systemui
Click to expand...
Click to collapse
You have to follow the original link I posted. http://forum.xda-developers.com/showthread.php?t=2655133 Download the rar file in the OP, and copy the \carrier folder to your phone. Use root explorer on your phone to make a backup of the /carrier folder and then delete it. Copy your new carrier folder to the phone.
Next I had to modify my build prop to the following.
ro.build.target_operator=spr
ro.carrier=spr
persist.service.crash.enable=1
Then I had to set my apn using Tweakker https://play.google.com/store/apps/details?id=com.tweakker.
juanacevedo said:
You have to flash Cloudyfa's fix for our phones. For some reason we have to have the stock kernel or we are going to get the lines bug. That also means we will lose recovery though.. It fixed it for me though. How did you unlock your phone exaclty? I tried to change my apn to tmobile on a 4.4 lg rom (cloudyflex) but it kept crashing my systemui
Click to expand...
Click to collapse
Can you provide a link for Cloudyfa's fix?
From Cloudyfa: http://forum.xda-developers.com/showpost.php?p=51974589&postcount=281
For those having issue with white lines (mostly LS980) and losing Knock On (F320) after using 21o/21p org kernel. This is a temporary solution for you:
1. Use AutoRec to have custom recovery (TWRP).
2. Install the ROM you want.
3. You will now having white lines/Knock On lost issue. Just leave it.
3. Setting up all your app/mod.
4. Install my BootStack package here: http://www.androidfilehost.com/?w=files&flid=13798
5. When you wanna change to another ROM, repeat all above steps.
There's no other way for you now as you must use the org kernel from LG, no patched or moded kernel working. Maybe we can fix this issue with later LG kernel source. Anyway, using the this temporary solution still can help you to change to any custom ROM (which support your variant) you want, not stuck with stock ROM anymore (and wasting time flashing zvc (LS980) or 21o/21p (F320) all the time)
brandonbarlow said:
From Cloudyfa: http://forum.xda-developers.com/showpost.php?p=51974589&postcount=281
For those having issue with white lines (mostly LS980) and losing Knock On (F320) after using 21o/21p org kernel. This is a temporary solution for you:
1. Use AutoRec to have custom recovery (TWRP).
2. Install the ROM you want.
3. You will now having white lines/Knock On lost issue. Just leave it.
3. Setting up all your app/mod.
4. Install my BootStack package here: http://www.androidfilehost.com/?w=files&flid=13798
5. When you wanna change to another ROM, repeat all above steps.
There's no other way for you now as you must use the org kernel from LG, no patched or moded kernel working. Maybe we can fix this issue with later LG kernel source. Anyway, using the this temporary solution still can help you to change to any custom ROM (which support your variant) you want, not stuck with stock ROM anymore (and wasting time flashing zvc (LS980) or 21o/21p (F320) all the time)
Click to expand...
Click to collapse
Yup, that's it!
brandonbarlow said:
You have to follow the original link I posted. http://forum.xda-developers.com/showthread.php?t=2655133 Download the rar file in the OP, and copy the \carrier folder to your phone. Use root explorer on your phone to make a backup of the /carrier folder and then delete it. Copy your new carrier folder to the phone.
Next I had to modify my build prop to the following.
ro.build.target_operator=spr
ro.carrier=spr
persist.service.crash.enable=1
Then I had to set my apn using Tweakker https://play.google.com/store/apps/details?id=com.tweakker.
Click to expand...
Click to collapse
It's not supposed to work for US carriers but I followed your method using the cloudystock 2.0 rom and it's working fine on T-Mobile(US). Strange, so far so good though. Before if i would change my apn to Tmobile, it would make the phone keep crashing SystemUi making it unusable but its good with the method you listed, thanks a lot!
juanacevedo said:
It's not supposed to work for US carriers but I followed your method using the cloudystock 2.0 rom and it's working fine on T-Mobile(US). Strange, so far so good though. Before if i would change my apn to Tmobile, it would make the phone keep crashing SystemUi making it unusable but its good with the method you listed, thanks a lot!
Click to expand...
Click to collapse
Give thanks where thanks is do. I didn't do any modding or any real work. I just read through forums and reposted others work. Be sure to thank the linked forum OP for the real work.
Deleted
I made a new link covering a walkthrough how to use the our phone with tmobile or att http://forum.xda-developers.com/showthread.php?t=2729370
Sent from my LG-LS980 using Tapatalk
brandonbarlow said:
From Cloudyfa: http://forum.xda-developers.com/showpost.php?p=51974589&postcount=281
For those having issue with white lines (mostly LS980) and losing Knock On (F320) after using 21o/21p org kernel. This is a temporary solution for you:
1. Use AutoRec to have custom recovery (TWRP).
2. Install the ROM you want.
3. You will now having white lines/Knock On lost issue. Just leave it.
3. Setting up all your app/mod.
4. Install my BootStack package here: http://www.androidfilehost.com/?w=files&flid=13798
5. When you wanna change to another ROM, repeat all above steps.
There's no other way for you now as you must use the org kernel from LG, no patched or moded kernel working. Maybe we can fix this issue with later LG kernel source. Anyway, using the this temporary solution still can help you to change to any custom ROM (which support your variant) you want, not stuck with stock ROM anymore (and wasting time flashing zvc (LS980) or 21o/21p (F320) all the time)
Click to expand...
Click to collapse
i have f320k ...its knock on has been lost after flashing cloudy2.2 and i also faced white line issue
...i did all to solve this like flashing tot file or upgrade to 4.4 but same ..no knock on is working...i cant fine bootstack package too..
ur help in urgently needed
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Reflash it
TheZadok42 said:
I've upgraded to Android p and a few minutes ago I've rooted my phone
Since then my wifi won't work, what can I do?
Ok the root did not work
Click to expand...
Click to collapse
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Wolfhawke said:
Rooting a Beta Rom is usually a bad thing. My only suggestion is reflash following Essential's steps...
Click to expand...
Click to collapse
Why? Root works fine with it, this has nothing to do with that.
crixley said:
Why? Root works fine with it, this has nothing to do with that.
Click to expand...
Click to collapse
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
jmill75 said:
Root works fine with what? A dev preview OS.
If someone is having issues then it must not be working ok.
Click to expand...
Click to collapse
Yes it works fine and the issue has nothing to do with root. Probably half of us using it are rooted without issue
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
tliebeck said:
Bit of a thread-dig here, but I just got a PH1 and went straight to P (not rooted yet) and saw no WiFi. Wouldn't even turn on.
The phone came with 7.1.1 and I flashed P via fastboot. Tried rebooting and monkeying with it, but never saw any progress, no list of networks, etc.
7.1.1 did see WiFi for the 5 minutes I ran it.
Flashed latest stable 8.1 and it WiFi worked again immediately.
Then flashed 9 a second time and now WiFi works fine.
My best guess is the 7.1.1->9 transition has some kind of issue (doesn't quite make sense to me, given that I think EVERYTHING is being flashed by the 9 update, but this did fix it).
Click to expand...
Click to collapse
Just got my Essential Phone today as well and did the exact same thing, flashed straight from 7.1.1 to P. I thought I was seriously going to have to send the phone back due to a broken Wi-Fi chip or something. You are seriously a lifesaver!
rignfool said:
Kernel or firmware mismatch
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
If I take your post at face value... You have a bad flash and need to try again... Or blame your cable... And go buy a new one...
Otherwise... You have a bad download... Or there is something wrong wrong with your zip or batch/script... Or you're not completely unlocked
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Same here but can't roll back to Oreo
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
1jason said:
See.issue here but I seem.to not be able.to resolve wifi issue or roll back to Oreo. When I try to reflash it just says it expects a newer version of is. Any ideas?
Click to expand...
Click to collapse
Yes flash the july oreo flashall. Bat
Saundersmtt said:
What can be done about this? I am having the same issue, but I have flashed the whole "Back to Stock" set for P beta 2 from the other thread.
Click to expand...
Click to collapse
I had the same problem. went back to stock on July's build (was on January's stock build previously) and reflashed P. Been smooth sailing ever since
jacksummers said:
Listen guys, the issue is bc the ota zip for p doesnt flash both slots and the fastboot images zip doesnt either. If u look at the script (flashall. Bat) with a text editor it specifically shows only flashing one slot. To fix the wifi issue, u need the july oreo images file and that flashall. Bat flashes both slots and will fix the lost wifi and or Bluetooth. Once u do that, it reboots twice and go back to dev options and renable usb debugging. Now u reboot bootloader and flash p. Now it should all work. Also, in doing this, you will have to lose your data.
Click to expand...
Click to collapse
The reason is because one of the OTAs did not have the partition you're looking for... And it created a mismatch somewhere...
You DO NOT need to have the same software on A and B... It just makes troubleshooting easier from our perspective... And... It forces you to reflash and probably fix the problem...
As intended... There should ALWAYS be a mismatch between A and B... At least a monthly security update... If not an Android versioning difference
Edited. We are all just trying to help others. Lets keep it that way.
so, uhmmm like yea...... there is this thread here, called the stock images thread (link for posterity https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 ) this is firmware images, directly from essential. I have added the remaining images that you dont get from essential, so that way you can reflash, and get the same version of software on both sides. there are wipe and no wipe bat files in there, twrp11 (the working twrp we have), and the fix red boot (in case you broke verity), and a stockboot.img (coincidentally the same file as called boot in the zip, but renamed for your twrp/rooting pleasure).
These images work great, many many many people have used them to go back and forth between O and P, OTA, or recover from catastrophe. As usual, beware of dragons, make SURE SURE SURE SURE you have a working adb/fastboot environment (use the version that comes with essentials drivers) (you can always do ADB VERSION or FASTBOOT --VERSION ) to check your version and where its working out of. It is 1 stop shopping. I also know the guy that makes the zips
jacksummers said:
Edited. We are all just trying to help others. Lets keep it that way.
Click to expand...
Click to collapse
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
rignfool said:
Sorry if my post came off as harsh... I'll edit it... But this forum is literally littered with VAST amounts of guessing and misinformation...
Click to expand...
Click to collapse
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
jacksummers said:
No prob, i understand the frustration.i assure you i was not guessing. I only post what i know is for sure. When faced with the exact same issue as OP i was forced to flash both slots to fix it. Yes, they could boot up with slightly different partitions, but the wifi was broken still. I believe the whole phone needed both slots flashed with each corresponding img simultaneously in order to resolve said issue. For whatever reason, i had both a and b screwed up. At the time i was trying to fix the ril and camera issues on the pixel 2 system image after flashing it on my essential. I want to get that working fully to release as a port.
Click to expand...
Click to collapse
Wouldn't it be easier to attempt to port the 2 or 3 features we don't have as a separate systemui.apk or framework-res.apk?
And use Magisk?
Since we don't have that fancy hardware photo rendering thingymabob
So it seems, some custom roms floating around out there can cause the WiFi Mac address to get changed, my understanding it has to do with the persist getting messed up.
There are a few tools floating around on XDA, one is the Persist_Resurrector.
But it's my understanding, if you have not messed with flashing another persist.img, then you are safe, and flashing back at Stock ROM will correct this.
I had one or two custom roms change my wifi mac, not sure which ones now, but I just flashed stock oreo back, and my original mac address is back, so I'm assuming I am all good, and this problem isn't bad, as long as you don't mess with another persist.img, flash stock back and you're golden?
How can I check if my persist partition is ok?
Thanks
Remove
cherryb8844 said:
Remove
Click to expand...
Click to collapse
@cherryb8844
Sorry remove what?
DoR3M3 said:
@cherryb8844
Sorry remove what?
Click to expand...
Click to collapse
I think he post on the wrong thread and ask mod to remove post
For your question I still don't know I'm really happy with stock experience and those persist partition froze me on moving to a custom ROM
But all MiA1 are not the same and yours seems to have survive also they have probably fix this problem on newer custom ROM build
Dead-neM said:
I think he post on the wrong thread and ask mod to remove post
For your question I still don't know I'm really happy with stock experience and those persist partition froze me on moving to a custom ROM
But all MiA1 are not the same and yours seems to have survive also they have probably fix this problem on newer custom ROM build
Click to expand...
Click to collapse
Ok on removed message...
I like the Stock too, I just wish Xiaomi could of put out a ROM, that doesn't have Gapps, and allow the users to pick their own...
I personally don't want anything google on my phone, or as little as can be possibly had...
DoR3M3 said:
Ok on removed message...
I like the Stock too, I just wish Xiaomi could of put out a ROM, that doesn't have Gapps, and allow the users to pick their own...
I personally don't want anything google on my phone, or as little as can be possibly had...
Click to expand...
Click to collapse
That would be bizzare if it happened for a AndroidOne phone not to have 'google anything' on the phone.
DoR3M3 said:
So it seems, some custom roms floating around out there can cause the WiFi Mac address to get changed, my understanding it has to do with the persist getting messed up.
There are a few tools floating around on XDA, one is the Persist_Resurrector.
But it's my understanding, if you have not messed with flashing another persist.img, then you are safe, and flashing back at Stock ROM will correct this.
I had one or two custom roms change my wifi mac, not sure which ones now, but I just flashed stock oreo back, and my original mac address is back, so I'm assuming I am all good, and this problem isn't bad, as long as you don't mess with another persist.img, flash stock back and you're golden?
How can I check if my persist partition is ok?
Thanks
Click to expand...
Click to collapse
As long as you have the original Xiaomi WiFi and BT Mac addresses, your persist partition is untouched.
DoR3M3 said:
Ok on removed message...
I like the Stock too, I just wish Xiaomi could of put out a ROM, that doesn't have Gapps, and allow the users to pick their own...
I personally don't want anything google on my phone, or as little as can be possibly had...
Click to expand...
Click to collapse
Why not just disable the Gapps you don't want.
I have these apps I don't use frozen (updates removed first):
Google play games
Google play books
Google play movies
Google play music
korean input
indic input
pinyin input
and zhuyin input all disabled.
I don't disable them because I object to Google, I freeze them because I don't want them to update, once updated you have two copies on your device, the outdated original stays in system, the new uses your storage (for an app you don't want).
I have also removed the Xiaomi installed user apps I don't use, feedback, mi store etc
joeyhuab said:
As long as you have the original Xiaomi WiFi and BT Mac addresses, your persist partition is untouched.
Click to expand...
Click to collapse
Hey joeyhuab, the persist got messed up, but I had the original WiFi Mac address from my router, LOL...
As far as the BT Mac, well, if the persist is messed up, is it going to change it too?
I figured out how to flash stock rom, using the persist.img with MiFlash tool and got it all working, I guess for now, not sure the BT Mac address was changed or not...
@kudos1uk, yeah titanium is good to freeze apps, I was doing that before in Stock...
DoR3M3 said:
@kudos1uk, yeah titanium is good to freeze apps, I was doing that before in Stock...
Click to expand...
Click to collapse
You don't need titanium, just disable then in the app manager.
kudos1uk said:
You don't need titanium, just disable then in the app manager.
Click to expand...
Click to collapse
Yes of course the app manager, I just mentioned titanium, I just find it easier to scroll through it, either way works...
DoR3M3 said:
Yes of course the app manager, I just mentioned titanium, I just find it easier to scroll through it, either way works...
Click to expand...
Click to collapse
Titanium is great but it needs root and I don't know if you can use it without changing the system partition and stopping OTA, app manager is safer as you can't disable important apps by mistake, Google only allow you to disable non critical apps.
I only mention it as you can keep your phone 100% stock without root and disable most Google apps which can be easily turned back on in the future, of course things like Play Store can't be disabled.
Back to the original topic...
So my persist was messed up, and I restored it, but the only way I could figure this is with the image on xiaomifirmware.
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
Hopefully this wasn't such a bad move, wifi works, and I see a mac address, but I'm not sure if they are the original, also I can make calls, so not sure if the imei is the original, or the network, just updated the phone to a new iemi.
How can I tell, or is there a way, if I have everything back to original?
Thanks
DoR3M3 said:
Back to the original topic...
So my persist was messed up, and I restored it, but the only way I could figure this is with the image on xiaomifirmware.
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
Hopefully this wasn't such a bad move, wifi works, and I see a mac address, but I'm not sure if they are the original, also I can make calls, so not sure if the imei is the original, or the network, just updated the phone to a new iemi.
How can I tell, or is there a way, if I have everything back to original?
Thanks
Click to expand...
Click to collapse
Is that way considered as flashing another phones persist file that not belong to our phone? Its just because we don't know where that persist (that available there) come from. I don't know for sure so CMIIW. Because i restored my persist by persist resurrector to get my original mac back. I don't wanna wreck my device by flashing another persist file that I don't know where it come from. One more time, correct me if I wrong.
upilguebu said:
Is that way considered as flashing another phones persist file that not belong to our phone? Its just because we don't know where that persist (that available there) come from. I don't know for sure so CMIIW. Because i restored my persist by persist resurrector to get my original mac back. I don't wanna wreck my device by flashing another persist file that I don't know where it come from. One more time, correct me if I wrong.
Click to expand...
Click to collapse
I don't think by flashing with this persist.img we call the phone damaged, just that the mac addresses are changed, maybe the imei too, but I made calls and text ok, so if it changed my imei, the carrier picked it up no problem...
For now, I'm trying to get the phone booted into edl mode, and oh what a PAIN in the, you know what! LOL...
Just a few simple cmds and the hours it seems to take to do things, heck, running Linux is simpler then this, I could of installed several Unix/Linux systems, by the time I have figured this out! LOL
Last go, I installed the 15 Seconds ADB installer by Snoop, and adb devices wouldn't show anything, then I tried the minimal adb setup/installer and same problem. Now I'm going to try the android sdk and install and the platform tools and see if it works this way, mind you, all this time, to make sure everything is clean, I have been constantly wiping out my box, reformatting it, and putting back a clonezilla image I have for Win8.... OH BOY, so much bloody work...
The WHOLE goal here is, that supposedly, you place phone in; fastboot oem edl, have the oreo rawprogram0.xml edited, so it has 'persist.img' in it, then flash with MiFlash and this is suppose to flash the original stock persist.img
BUT, I see that a lot of people are saying the only way to get edl is to open phone, and short out a few connectors on the board, which put's it into edl...
http://en.miui.com/thread-1680467-1-1.html
Also I read, you hold both up/dn vol and power and wait for phone to vibrate twice and this makes edl...
So I've been going to all this trouble to try and run; adb reboot-edl because fastboot oem edl always gives me some failed...
Hmm
kudos1uk said:
Titanium is great but it needs root and I don't know if you can use it without changing the system partition and stopping OTA, app manager is safer as you can't disable important apps by mistake, Google only allow you to disable non critical apps.
I only mention it as you can keep your phone 100% stock without root and disable most Google apps which can be easily turned back on in the future, of course things like Play Store can't be disabled.
Click to expand...
Click to collapse
if you want to remove the apps,you can use the bat script,no root needed,put in the adb folder and give the necessary permission,run the bat script..mi launcher is disable by default
View attachment 4526190
upilguebu said:
Is that way considered as flashing another phones persist file that not belong to our phone? Its just because we don't know where that persist (that available there) come from. I don't know for sure so CMIIW. Because i restored my persist by persist resurrector to get my original mac back. I don't wanna wreck my device by flashing another persist file that I don't know where it come from. One more time, correct me if I wrong.
Click to expand...
Click to collapse
roshan2989 said:
if you want to remove the apps,you can use the bat script,no root needed,put in the adb folder and give the necessary permission,run the bat script..mi launcher is disable by default
View attachment 4526190
Click to expand...
Click to collapse
Ahh interesting...
Thanks
P.S. Post all good, issue resolved, no need to reply...
I tried to flash it but it only bootloops for me. Have tried almost everything it seems. Have never had so much trouble flashing a phone.
I have tried Lieage os 15.1 but after i tried to flash N2G48B_4Cores.img from this side https://www.xda-developers.com/nexus-6p-bootloop-fix/ Lineageos bootloops even faster. Even tried the twrp from the side who requires a password I cant find so it it is useless.
I have tried Aquatios but it bootloops.
I have tried to flash stock android but it says something about the zip is wrong.
Someone who knows what I should do or am I stuck? I forgot to make a backup to so I am a bit desperate. Never forget it usually but only because it's not my phone I do forget.
I hope someone knows what I should do.
*EDIT* [SOLVED]
Trie this and got a bit further: https://forum.xda-developers.com/ne...t/rom-lineageos-16-0-nexus-6p-angler-t3849169
Only that the screen flashes soon after after the settings come up and turn itself of after a while.
I have not flashed the radio though. Is that necessary?
*EDIT 2* [NOT SOLVED]
The radio were necessary for wifi.
Now is the problem with signing in to google.
Never can anything go smoothly.
I solved it finally. Will remove the thread as soon as I see how I do. Have not used xda in a while.
orrebo said:
I solved it finally. Will remove the thread as soon as I see how I do. Have not used xda in a while.
Click to expand...
Click to collapse
Good to hear. So what did you do wrong and what did you do to fix it?
Aimless Rambler said:
Good to hear. So what did you do wrong and what did you do to fix it?
Click to expand...
Click to collapse
Yeah. What did I do. Tried until I found a solution that worked. Think I mentioned it (did not). This thread I looked at to solve that problem: https://forum.xda-developers.com/ne...t/rom-lineageos-16-0-nexus-6p-angler-t3849169
I had to flash a bootloader file and after that it worked better.
But I can't sign in to google how I do. Will try a couple of other gapps. Hopefully someone will work.
I have seen this before but don't remember how I solved it back then.
It even bootloops if it don't like the gapps.
New problems every time. A new one again where it crashes in the initial settings.
It stopped suddenly and is now back to checking info and this time it said it can't connect to google servers.
Have never ever worked with such a ****ty phone.
*EDIT*
I give up. It is as good as it gets.
If someone else of her friends wants to try so be my guest.
Over and out for this time.
If it's toast from the infamous bootloop issue can't blame you for setting the phone aside. But if you venture back to it I'd suggest flashing stock Google firmware then doing the 4cores fix if needed.