Related
I decided to go ahead with the TW firmware upgrade. Everything seemed to be going fine until I tried to install it and it told me there was an error and I needed to hook it up to Kies first. I had already been using Kies with it on my Macbook for a couple weeks now so I went ahead and plugged it in. Kies recognized it as usual and all the information came up.
So I went on and tried to install again and it said it needed to reboot.
It reboots and comes to the Samsung Galaxy Tab 10.1 screen like normal (right before it starts the galaxy animation). Next thing I know it comes to a screen that looks like the attached images! I immediately unplugged it from Kies and shut it down. Every time I start it back up it does the same thing. I honestly have NO idea what to do. I can't even return it as it's past the 14 day period and I (stupidly) didn't buy Staples' bogus $160 insurance.
I was not rooted before. This was a stock tab that I bought at staples. It had the firmware 4.24 when I bought it, I think.
Please, any help is appreciated. I tried doing firmware recovery in Kies but the pop up comes up in Korean and I have no idea what it says...
Edit: More info. I'm not the only one with this problem. Two other people have posted on AndroidPolice about this. http://www.androidpolice.com/2011/08/04/samsung-galaxy-tab-10-1-wifi-touchwiz-ux-update-is-now-live/
The software is definitely running underneath all that mess but it's literally impossible to see what is going or to touch anything.
I guess this thread is about the same issue
http://forum.xda-developers.com/showthread.php?t=1203610
Thanks, I'm checking the thread out now. I probably should have searched more than just Google before posting but I freaked out when it happened.
No need to freak out . we have xda and dev to solve all our problems
i have exactly the same problem as you... what should i do now?
I get the same screen but after rebooting! pfft it's making me really sad :\
I'm sorry but I tried reading this http://forum.xda-developers.com/showthread.php?t=1171089 and couldnt understanding what should I do!
What CWM + my device is not rooted, all I could understand is that the thread contains instructions on how to root your device..
I just want my normal screen back!
Please tell me what to do in simple english :\
And now I did a wipe and the stripes are gone, but the screen is black instead :\ still not working. Please help me!
Are you sure you didnt sit on it?
Amal Kadi said:
I'm sorry but I tried reading this http://forum.xda-developers.com/showthread.php?t=1171089 and couldnt understanding what should I do!
What CWM + my device is not rooted, all I could understand is that the thread contains instructions on how to root your device..
I just want my normal screen back!
Please tell me what to do in simple english :\
Click to expand...
Click to collapse
haha i had the same problem go look at my threat that was posted above. in thier someone posted instructions on what to do the link you posted contains the download to the things needed heres a basic rundown of what you need to do
install clockwork recovery mod "CWM" to replace your bootloader.
download and install stock 3.1 and you should have your tab back to normal.
my help thread has the instructions to instal CWM
tonyurquiza said:
haha i had the same problem go look at my threat that was posted above. in thier someone posted instructions on what to do the link you posted contains the download to the things needed heres a basic rundown of what you need to do
install clockwork recovery mod "CWM" to replace your bootloader.
download and install stock 3.1 and you should have your tab back to normal.
my help thread has the instructions to instal CWM
Click to expand...
Click to collapse
So I need to follow all the steps for rooting except the last one which is the actual rooting? Great thanx! Do I need to use Kies? My current computer is Mac but I guess I need to download those things to a Windows machine to make it work, right?
Thank you very much
I had the same problem. I upgraded the update on my non-rooted tablet and got the funked up video mess. Per instructions from Samsung support, I hard booted to the recovery menu (power+vol down, then power up, down on download screen) and did the factory wipe. After that I ended up with the black screen. I could tell things were working in the back but couldnt see a thing. I figured I would throw it on the Kies and it saw that there was a factory upgrade so I let the Kies run through it and it works fine now.
Dont know if this will help w/other but it worked for me.
Ok, please I hope you can help. New to rooting, I rooted my s5, and was working fine for days, then I got the error and yellow triangle "system software not authorized by Verizon" I downloaded one md5 firmware I found and flashed it using odin, after was done had the same error though. I was on version 4.4.2. (don't know if that matters) I cannot find any other "stock" firmware online to try that are md5 that I can use with odin. I can find all these custom roms in zip format but don't know how to flash to odin when they are in the zip format and not tar or md5. Right now im just bricked and cant do anything and trying to learn how to fix all this.
Links to all files you need to download and full instructions on how to Odin back to stock can be found here ==>
http://forum.xda-developers.com/showthread.php?t=2784880
To properly root your device follow these instructions here ==>
http://forum.xda-developers.com/showthread.php?t=2784860
You can not just flash a ROM to your phone like with older phones, due to the locked bootloader. You have to install Safestrap and install the ROM there. You will find all you need to do that along with a link to a Youtube video explaining it all here ==>
http://forum.xda-developers.com/showthread.php?t=2793891
ok, I did just like the guide says and applied the tar file. it goes through the whole process but when it reboots it still says "secure fail:modem" in the left hand corner and "system software not authorized by Verizon wireless has been found on your phone please turn off and got to nearest wireless store for help". Im lost....
do I have to download and flash all those files? the nk2,n12, ne9, ncg??? what is the difference? hope someone can help...been working on this for hours and there doesn't seem to be a lot of information on my issue
tr889 said:
do I have to download and flash all those files? the nk2,n12, ne9, ncg??? what is the difference? hope someone can help...been working on this for hours and there doesn't seem to be a lot of information on my issue
Click to expand...
Click to collapse
Stick with my instructions to reset and the instructions to root. I have all the files and instructions you need for root linked in the how to root section in the OP.
I did it word for word, and after boot it still comes up to the system software not authorized by Verizon screen. Don't know how to proceed?
any help would be greatly appreciated because at this point im out 450 dollars.
Took it too Verizon and they said there is nothing they can do but give 178 dollar gift card...anyone here have any other ideas? Followed the rooting guide here, updates were turned off, don't know what went wrong
tr889 said:
Took it too Verizon and they said there is nothing they can do but give 178 dollar gift card...anyone here have any other ideas? Followed the rooting guide here, updates were turned off, don't know what went wrong
Click to expand...
Click to collapse
Did you re-partition using the pit file when trying to go back to stock? This doesn't make any sense. To the best of my knowledge, even tripping knox won't result in this ...
Yeah I did. Don't know what to do...I seem to be the only one that has had this issue. My question is, what did I do to wrong to make this happen? How do I prevent it when I get a new phone? It seemed to happen after tethering using x tether on xposed? Is there an issue with xtether ?
No there's no issue there. I run it and have Odined back to stock a couple of times and re-installed it.
Work backwards. Un-install all xposed modules. Un-install SuperSU, towel root and everything else you have added. Do a factory data reset and then try to Odin back to stock maybe? Take it all the way back to NGC
You don't use any kernel tars, just the full factory image tar
Hi, I'm new to ROM flashing etc. and seem to have gotten myself in trouble.
I bought a used Moto X Pure (XT1575 model) with, I guess, the Motorola unlocked bootloader and TWRP already installed. I accidentally approved an OTA update this afternoon and ended up in a boot-loop.
In trying to fix it I used the "restore-to-stock tool" for windows found here:
http://forum.xda-developers.com/mot...ndows-tool-moto-x-style-pure-edition-t3199905
This was semi-successful; the OS loaded and I was able to begin migrating my old apps, but
(1) the wi-fi doesn't work at all! I can't turn it on in settings -- the slider will slide on but then slide back off by itself
(2) the recovery image seems screwed up; I can't get into recovery mode, and get an error there instead.
I am at a loss as to what to do but see my last resort in using fastboot to upgrade to the 6.0 stock image as described here:
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
I'm too tired to try tonight, so I thought I'd ask for advice before I go to bed. What are my options here, especially if the upgrade to 6.0 creates new problems? Can I get error meessages for the wireless so I at least know what's going on? Can I reflash the wireless firmware -- might it have been messed up if one or another upgrade was interrupted somehow?
Also -- hope I'm in the right forum -- please point me in the right direction if I'm not!
Many thanks for the help!
Did you read that thread? Quite a bit of wifi talk in there.
lafester said:
Did you read that thread? Quite a bit of wifi talk in there.
Click to expand...
Click to collapse
Oh man, I had NOT read far enough in that thread. The solution was simply to reflash the modem,
Code:
fastboot flash modem NON-HLOS.bin
Just did it and the wifi issue seems to be fixed!
How should I approach the crashed recovery partition? When I got the phone, TWRP was installed as well as SuperSU. I tried the restore-to-stock tool mostly because of the problem with OTA updates being so frustrating; but I wouldn't object to reinstalling TWRP and SuperSU, if I knew how to get and install new images within a few days of the OTA update arriving (I have been deferring the last OTA update since the day I got the phone, a month ago -- I was bound to make a typing error eventually, and it happened yesterday). Anyway, if you can point me in the right direction for learning that stuff I'd be grateful.
So psyched to have wifi working! THank you!
There's a twrp thread in og dev
Requesting guidance before I brick my phone.
I currently have bootloader unlocked, twrp installed, and my nexus 6p rooted. I'm running 7.1.2. I've also changed a line in the (build.prop) provisions in order to tether free (since I am on at&t)
Basically, I'm wanting to install pure nexus. I have the custom rom file and the vendor image file.
Before I install from, I'm wondering if I need to unroot first? Also curious if how "shamu" will affect things since I'm on Angler.
Thanks!
Okay you need to stop everything you're doing and read this topic until you know what is what.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page577
First of all, you obviously wouldn't flash a Shamu package on Angler. That's a great way to brick your phone, permanently.
Read every single step in that guide above, even if you don't think it's pertinent to what you're trying to do. Read it a second, third, fourth, fifth time until you know the steps by heart. Until you know what's next.
Also, download the correct Angler zip file and DO NOT FLASH A SHAMU ZIP ON YOUR PHONE.
help
RoyJ said:
Okay you need to stop everything you're doing and read this topic until you know what is what.
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page577
First of all, you obviously wouldn't flash a Shamu package on Angler. That's a great way to brick your phone, permanently.
Read every single step in that guide above, even if you don't think it's pertinent to what you're trying to do. Read it a second, third, fourth, fifth time until you know the steps by heart. Until you know what's next.
Also, download the correct Angler zip file and DO NOT FLASH A SHAMU ZIP ON YOUR PHONE.
Click to expand...
Click to collapse
Any help on flashing back to stock using TWRP? I unlocked the bootloader and rooted my device (never made a backup till after but still proved to be of no help as it wont work when trying to restore) lesson learned for sure. but i cant boot the device up however i still have access to twrp recovery how can i go back to stock so i can start from scratch?? :crying:
Filly2 said:
Any help on flashing back to stock using TWRP? I unlocked the bootloader and rooted my device (never made a backup till after but still proved to be of no help as it wont work when trying to restore) lesson learned for sure. but i cant boot the device up however i still have access to twrp recovery how can i go back to stock so i can start from scratch?? :crying:
Click to expand...
Click to collapse
You can follow the original advice I posted above. Read that thread I linked. It's ALL covered there. No sense in me writing everything up here when all you need to do is click the link I posted and follow the return to stock sections. There's even one for maintaining your data. Read the thread. It covers literally everything.
..
RoyJ said:
You can follow the original advice I posted above. Read that thread I linked. It's ALL covered there. No sense in me writing everything up here when all you need to do is click the link I posted and follow the return to stock sections. There's even one for maintaining your data. Read the thread. It covers literally everything.
Click to expand...
Click to collapse
Sorry I don't mean to bug man but I'm so lost. I'm trying to find what you are referring me to but I'm not finding the info I need I haven't been on here too often so this is like a pain in my rear so far. Plus I'm a very hands on kinda learner so I need some like handicapped help lol If you don't mind I don't want to pester anyone...
I was able to load pure Nexus. I didn't realize there was a pure nexus rom with Angler on it.
My main question was if I had to reverse the root. But I'm good to good now.
Rom loaded, vendor image loaded, and Google Apps loaded.
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