I just got a used E980. idk what he's done to it. but appeared vanella. I tried rooting, from the proper thread with the right files. suposedly right for the e980. so I tried to just reboot recovery, but all i get is an android with a red triangle and an ! inside it of.
the error i get when trying to root is -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it's a custom Rom it's already rooted (obviously). Check the build version in your settings.
cougar214 said:
If it's a custom Rom it's already rooted (obviously). Check the build version in your settings.
Click to expand...
Click to collapse
yeah i can't get into TWRP, or the other one. it keeps giving me dude with red !. version is jz054k.
I did a full wipe and install of an origonal build of the software, was able to root it sucesfully now. but still can't get into the bootloader menu. tried cammand line to tell it to boot into it, tried rom manager. no dice. just keep getting little dude. i remember seeing a thread about him, i don't know what he means :\
The bootloader on these phones are locked. You are able to install the custom recovery only because Freegee can bypass the bootloader.
cougar214 said:
The bootloader on these phones are locked. You are able to install the custom recovery only because Freegee can bypass the bootloader.
Click to expand...
Click to collapse
yeah i got around it and managed to do it. didnt much like the rom, know any clean roms that are more stock like? i really didnt mind stock. but i want 4.4 or better than stock.
Honestly, your best option is to wait for the kitkat update to hit in a month or so. You get what you're looking for in one stock update. Hassle free. That's what I'm doing. The more I learn about this phone, the more I am hesitant to flash anything to it. Mostly because there are so many variants for this phone. Everything can't be compatible so why risk it.
eviling said:
yeah i got around it and managed to do it. didnt much like the rom, know any clean roms that are more stock like? i really didnt mind stock. but i want 4.4 or better than stock.
Click to expand...
Click to collapse
This http://forum.xda-developers.com/showthread.php?t=2703029
Read the whole thing then you'll be ready to go
Its the kitkat Korean update, I'm using it on my e980 , pretty sweet
yeah i agree, i havn't found many rom's i like. ive found roms always fail after awhile. so idk. they always bloat up and start to fail than they need the update to be stable blah blah than your reinstalling all apps and backing **** up. idk, was just looking at what phones offer these days for modding but nothing seems to of changed. this phone inparticular is a rather unstable device none stock, seems to be allota issues and a good reason to have bootloader locked.
Un locking the bootloader only allows for custom kernels on any given device. In some cases you will get greater stability. But for the most part you will still have glitches, performance decreases, etc. because you are STILL flashing custom Roms. And in allot of cases your phone will go completely nuts because custom kernels have their glitches too. So in short, sometimes, Custom Rom=glitches. custom kernel=glitches. That all adds up to a totally unstable Rom. Keep in mind all devices are not the same. What runs great on his might crash your phone completely. Just my 2 cents....lol
Related
Hi Guys!
I'm sorry if this question has been asked a gazillion times, but I want to know what I'm getting into first as I am new to rooting.
I have a Sony Xperia Ion (LT28i) with Jelly Bean on it (4.1.2). I was simply wondering if the process outlined in this thread would work:
[Tutorial][ION] Flashing Firmware and Rooting
http://forum.xda-developers.com/showthread.php?t=1812168
Once again, sorry for a repeat but I'm not exactly sure about what my firmware is etc.
Thanks!
WGuitar said:
Hi Guys!
I'm sorry if this question has been asked a gazillion times, but I want to know what I'm getting into first as I am new to rooting.
I have a Sony Xperia Ion (LT28i) with Jelly Bean on it (4.1.2). I was simply wondering if the process outlined in this thread would work:
[Tutorial][ION] Flashing Firmware and Rooting
http://forum.xda-developers.com/showthread.php?t=1812168
Once again, sorry for a repeat but I'm not exactly sure about what my firmware is etc.
Thanks!
Click to expand...
Click to collapse
yes that will work..go to settings>about phone> and you will find all the info abt ur software versions...u are basically looking for build number here..
Build Number is:
6.2.B.0.211
Therefore since it appears to be the most recent firmware, I can simply skip to the rooting portion of the guide correct?
Thanks, I've been hoping to get my phone rooted to get rid of all the bloatware.
You guys are awesome!
I have attempted to root the device to no avail. Does the firmware have to be flashed over? Or can I use the firmware currently on it. If it has to be flashed over, my phone does not appear to have drivers in the flash tool. Can I flash without installing a driver?
WGuitar said:
I have attempted to root the device to no avail. Does the firmware have to be flashed over? Or can I use the firmware currently on it. If it has to be flashed over, my phone does not appear to have drivers in the flash tool. Can I flash without installing a driver?
Click to expand...
Click to collapse
u have an unlocked bootloader or locked???
I believe it is locked as I have not done anything to the phone besides upgrading to JB from ICS. I used the Sony PC Companion to do so as well.
Edit: Bootloader is locked and apparently cannot be unlocked. (According to System info)
WGuitar said:
I believe it is locked as I have not done anything to the phone besides upgrading to JB from ICS. I used the Sony PC Companion to do so as well.
Edit: Bootloader is locked and apparently cannot be unlocked. (According to System info)
Click to expand...
Click to collapse
It doesnt matter...can you tell me the steps that you did briefly and where you faced the problem?
Sent from my Micromax A110 using xda app-developers app
It tells me to use the display system check but it just gets stuck hanging at a white screen on my phone and the program does not continue from there. If you could tell me the version of the root program and which option to use, I might be able to do it, but I've tried a few different versions of it with different options. Not exactly sure what I can do.
Edit: Do I have to flash my firmware before trying to root? It doesn't say anywhere that I have to, however could that be what's not allowing me to root?
WGuitar said:
It tells me to use the display system check but it just gets stuck hanging at a white screen on my phone and the program does not continue from there. If you could tell me the version of the root program and which option to use, I might be able to do it, but I've tried a few different versions of it with different options. Not exactly sure what I can do.
Edit: Do I have to flash my firmware before trying to root? It doesn't say anywhere that I have to, however could that be what's not allowing me to root?
Click to expand...
Click to collapse
This method doesnt work with your .211 fw. Try this http://forum.xda-developers.com/showthread.php?t=1886460&highlight=root+211+ion
I've tried that thread's root method. All I keep getting is a screen that it pauses at basically indefinitely, and none of the other root options work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey everyone. Im relatively new to this forum and rooting. I have some background knowledge in programming and other related aspects, unfortunately nothing related to Android. As well as some Linux OS experience. Now as far as i know ROM's could be compared to OS builds. Android 4.1.2, 4.3, 4.4, etc. Rooting makes you a super user/sudo like Linux. I think i have that pretty much correct. Now for the things i know little about.
-KNOX so far it seems its mostly used for enterprises and to see if we have installed a custom ROM. I've seen a lot of different information about Knox. What exactly else does it do/change? As of 4.3 i see we could no longer roll back or we will brick our device. What should i be wary of? I could care less about tripping the knox counter.
-Stock OTA is another thing i was curious about. This simply means an update was installed post factory by user, correct? My girlfriend has an S3 and i cant remember if 4.3 was stock or 4.1.2. I just wanted to clear up if my OTA updated S3 was covered under this.
-i saw one root method which kept the stock recovery but installed the superuser. What is the benefit for having a stock recovery? Would i be able to use a custom one with Knox in place? I was thinking of using a 4.4 cyanogenmod rom.
Sorry if this seems a bit noobish, but my schedule is tight and i spent maybe 6 hours trying to find exact information. Kind of hidden lol.
I appreciate any answers!
Sent from my SPH-L710 using xda app-developers app
All your questions are probably answered here-http://forum.xda-developers.com/showthread.php?t=2541343- read the whole thing and let us know if you have anymore questions
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And to answer some if them.
There is no advantage to stock recovery, you can't do anything with it.
Yes you can do anything the same with Knox but installing a custom recovery triggers the warranty bit in Knox. If you bring in your phone to be repaired or something, if they put the phone in Download Mode they could tell whether you installed a custom recovery because Warranty Bit would say 1 instead of zero. There's also no way to reset the flash counter with Knox.
And the biggest thing, if you have Knox do not try to downgrade the firmware. Aka don't try to Odin anything other than 4.3+. It will brick your device.
Other than those things it won't effect you at all.
And yes an OTA is Over The Air update. When the device scans for firmware updates and it find one it automatically downloads it and persistently bugs you about it until your firmware is the most current version. Done by the user or sometimes the techs at phone stores like to do it without asking you.
So to clarify (at work, ill read your link, appeciate it) Knox wont affect anything BUT the counter and downgrading? So i could root the old way with odin and cwm for 4.1.2 without problems?
Stock recovery is just worse in general or similar? Lastly "stock" ota is what i meant lol. I guess that means a non-custom ROM from your carrier?
I personally dont care for my warranty, i have a few months left in my contract and could upgrade now to a new phone if i wanted.
Thanks. I hate to sound like i did no research, i appreciate the link.
Sent from my SPH-L710 using xda app-developers app
I have seen a few of these threads, but nothing solid enough to grant a solution.
As you see below, I am getting constant signal drops, and it happens even where there is flawless reception.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So far I've read these suggestions:
-- Flash new Kernel
-- Flash stock rooted ROM then flash back
Any thoughts?
I am currently on Task's Latest (6-28) ROM, but have been experiencing this on previous ones (4.4.3 + 4.4.2).
leeroyjenks said:
I have seen a few of these threads, but nothing solid enough to grant a solution.
As you see below, I am getting constant signal drops, and it happens even where there is flawless reception.
So far I've read these suggestions:
-- Flash new Kernel
-- Flash stock rooted ROM then flash back
Any thoughts?
I am currently on Task's Latest (6-28) ROM, but have been experiencing this on previous ones (4.4.3 + 4.4.2).
Click to expand...
Click to collapse
Task's latest is 7-9 I believe.
That being said, Is your phone unlocked?
Also, does your baseband match your bootloaders?
BWolf56 said:
Task's latest is 7-9 I believe.
That being said, Is your phone unlocked?
Also, does your baseband match your bootloaders?
Click to expand...
Click to collapse
Oops, guess I didn't check Task for the past few days.
Phone is unlocked.
Baseband and Bootloader are both I747UCDLK3
leeroyjenks said:
Oops, guess I didn't check Task for the past few days.
Phone is unlocked.
Baseband and Bootloader are both I747UCDLK3
Click to expand...
Click to collapse
Did this start happening after unlocking? It sounds like your nv file might be damaged.
If so, you might need this http://forum.xda-developers.com/showpost.php?p=43842387
BWolf56 said:
Did this start happening after unlocking? It sounds like your nv file might be damaged.
If so, you might need this http://forum.xda-developers.com/showpost.php?p=43842387
Click to expand...
Click to collapse
No. This started happening maybe about a month or two ago. I unlocked it over a year ago. I have a feeling it was when i switched to a 4.4 rom. Unfortunately i didn't notice right away so i can't pinpoint the cause
Sent from awesomeness
leeroyjenks said:
No. This started happening maybe about a month or two ago. I unlocked it over a year ago. I have a feeling it was when i switched to a 4.4 rom. Unfortunately i didn't notice right away so i can't pinpoint the cause
Sent from awesomeness
Click to expand...
Click to collapse
You can try flashing another modem. If that doesn't work, might wanna try flashing back to stock, test it and work your way back up if all is well.
BWolf56 said:
You can try flashing another modem. If that doesn't work, might wanna try flashing back to stock, test it and work your way back up if all is well.
Click to expand...
Click to collapse
:good: Let's try that. Will get back with the results once I end up doing it in the next day or so.
BWolf56 said:
You can try flashing another modem. If that doesn't work, might wanna try flashing back to stock, test it and work your way back up if all is well.
Click to expand...
Click to collapse
Flashing the modem again did nothing to fix.
One question before I flash the stock ROM, will I need to do anything besides flashing? I'm not sure how it goes, since it is an older version (4.0.3 I believe?).
I know I need to do it in Odin, but nothing else besides that. Flashing an AOSP ROM after that won't be a problem?
Sorry for the questions, just wanna make sure before trying this out.
As the title says, I installed the ASUS Official Unlock tool (and didn't really read it, as you should) and it attempted a boot unlock without SU. The funny thing is, it did exactly what it said it would do and rebooted into the Bootloader. The Bootloader said (and still does) it was a success and that the phone will reboot in 5 seconds. Which is fine, except it's doing that every single time I enter the Bootloader. I can't get it to stop doing that so I can actually do the root and re-do the unlock. The phone still functions perfectly fine otherwise.. any advice? (Yes, I can get it into recovery mode) Hopefully that didn't ban me from OTA.
EDIT: It also turned my boot screen white, and I also tried to use the sideloader, but I already have the latest ASUS firmware so that didn't help. However, in my loader I noticed some weird stuff showing about a MOD_SDUPDATE.ZIP not being found.. I don't know what's that about. It was doing that before I tried to use the sideloader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dunno what exactly happened, but you can do " Using Stock.zip from ASUS site:" from here, that should fix basically everything: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
P.S.: your data won't be lost, however your app ache will be cleared, meaning you'll be logged out everywhere. So if you have some game and no account, that game state will be lost.
So I tried that, first with the ROM that's installed on the phone the .97 version. Then with the original version. It appears to actually install the .97 version, but that does absolutely nothing for the phone and if I try an older version it just tells me it can't flash an older version. Should flashing the same version over-top have taken care of the problem? Doesn't look like it did anything. The boot loader is probably unlocked, but I can't keep it in ADB mode long enough to do anything useful and you can't sideload a recovery to my knowledge.
EDIT: I named the file wrong in my tiredness. I did it again and loaded in recovery...
EDIT2: That did not work.
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
ultramag69 said:
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
Click to expand...
Click to collapse
I don't actually know what you mean by that? With the ASUS unlocking tool causing it to reboot in the bootloader improperly or the booting of the file from Recovery?
The phone isn't actually "broken" but now... I can't do anything to it without the use of ADB.. Which blows.
EDIT: Also, can you point me to these threads?
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
m3t4lw01f said:
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
Click to expand...
Click to collapse
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
bewaffled1 said:
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
Click to expand...
Click to collapse
Yep. We're hoping @ASUS_Khang gets a solution from HQ next week to get us back on track!
Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brickedmum said:
Hello, my 17 year old got the new one plus 5t yesterday,
He rooted the phone but then realised he couldn’t use certain apps with it rooted, so he uninstalled magisk
He rebooted the phone but it only went into custom recovery and wouldn’t load an OS
Because that didn’t work, he tried flashing an OTA update.
Now his phone is stuck on an upside down screen and a fuzzy section on it.
I know ZERO about android phones.
Should I wait for the support to open at one plus? Or is there something I can do to fix this?
Click to expand...
Click to collapse
tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
nguyenlucky said:
tell him to download this (full firmware)
https://otafsg.h2os.com/patch/amazo...xygen_43_OTA_011_all_1804241056_afd261322.zip
Boot to recovery, copy zip to internal storage, swipe to wipe and flash the zip.
p/s if it cannot boot to custom rec then use this guide
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
Click to expand...
Click to collapse
brickedmum said:
Thanks so much for your reply,
In the end I spoke to one plus and they couldn’t fix it, they said I could exchange it free of charge, so he got a brand new phone yesterday! Thank god. I’m never letting him root it again tho, he only had it 24hours!!!
Click to expand...
Click to collapse
You should let him experiment again, this time with some more reading here on the forum before though. He can learn a great deal about how different systems are built and the working parts of them.
And mostly since it's really fun, these days its really hard, close to impossible to mess up the phone bad.
Yes - He should be allowed to root it again - He needs practice
fkofilee said:
Yes - He should be allowed to root it again - He needs practice
Click to expand...
Click to collapse
I'm also in that opinion. He should be allowed to root again.
I may have an idea why this happened: Instead of an Oneplus 5T Firmware, he may have flashed a Oneplus 5 Firmware..
you mentioned an upside down turned Screen... well, the normal oneplus 5 had their Display assembled upside down and oneplus thought it would Fixing it by turn the Display Output by 180° by Software configuration. Your son should be Aware of that Oneplus 5 and 5T are different devices.
First step is using fastboot adb tool to flash some custom recovery first such as twrp,then download the latest oxygen system from oneplus official website(should be about 1.6gb) flash it inside and reboot. U will get a official system with official recovery set everything up. Then flash the custom recovery again and flash custom kernals such as bluespark or franco. goto the google pay or other root blocked app to set up everything.
Now you can flash the magisk to get root and activate magisk hide immediately right after u reboot. Remenber to tick the apps you need to hide the root for.
Wish u success:good: