I wanted to root my phone, which I already rooted before but then I made a factory reset and afterwards I got a root detecting app and it said my phone was rooted. But it didn't seem to exactly 100% work. I had downloaded superuser and I wasn't getting any prompts for superuser access when I tried to use apps that require root.
So I followed the steps in this thread to root:
http://forum.xda-developers.com/showthread.php?t=2784127
nstall TowelRoot from here: http://towelroot.com/
Then install AutoRec from here for TWRP recovery: http://forum.xda-developers.com/showthread.php?t=2715496
Then if your staying stock I highly recommend you download and install SuperSU in recovery so that it's properly rooted. http://download.chainfire.eu/282/SuperSU/
Click to expand...
Click to collapse
Things /seemed/ to go smoothly, but after installing SuperSU from TWRP I tapped on reboot, then system (which I thought meant booting into the android OS, normally) but after the LG logo it went to a black screen with the LED flashing green and blue, and nothing happens... even if I leave it for like 10 mins nothing will happen. I tried lots of button combinations, long pressing the power button restarted the device and did the same issue, pressing volume up, down, and power turned the device off (thank god that exists) but there's nothing else I can do.
TL;DR; phone won't boot into android, after the LG logo during boot the LED flashes green and blue and nothing happens.
Does anyone have any idea what I can do now? Please help me I just want my phone to work again
EDIT: Wrong section, ugh. Sorry. I have the D802 not AT&T version. Mods, remove this thread.
u cant get it to download/recovery mod?
what happends when u plug usb cable ?
Related
Unfortunately, I've bricked my Acer Tablet after trying to flash this ROM http://forum.xda-developers.com/showthread.php?t=1994294
The installscript finished the flash successfully, but after reboot, the bootloader only shows the message "Boot image verified failed" No booting and no CWM Recovery is available no more. I've tried several times to get into the fastboot mode with pressing the Power Button and Volume Button with the two knobs, but nothing helps. Neither switching the screenlock switch on and off. I figured out by trying, how to get into APX mode, but I don't know, if and how that could help me, solving my problem :/
Before I've tried to flash the ROM, I had CM10 with the Stock Bootloader in Unlocked Mode and CWM 6.0.2.3 Touch installed, but the Aroma Installer seems to have destroyed the CWM and locked my Bootloader again. Is there any way to unbrick the tablet now? Any help would be appreciated
V4lk0 said:
Unfortunately, I've bricked my Acer Tablet after trying to flash this ROM http://forum.xda-developers.com/showthread.php?t=1994294
The installscript finished the flash successfully, but after reboot, the bootloader only shows the message "Boot image verified failed" No booting and no CWM Recovery is available no more. I've tried several times to get into the fastboot mode with pressing the Power Button and Volume Button with the two knobs, but nothing helps. Neither switching the screenlock switch on and off. I figured out by trying, how to get into APX mode, but I don't know, if and how that could help me, solving my problem :/
Before I've tried to flash the ROM, I had CM10 with the Stock Bootloader in Unlocked Mode and CWM 6.0.2.3 Touch installed, but the Aroma Installer seems to have destroyed the CWM and locked my Bootloader again. Is there any way to unbrick the tablet now? Any help would be appreciated
Click to expand...
Click to collapse
Just let the battery run dry. Then let it boot up normally without pressing any buttons when the battery runs out by connecting it to your charger. Hope it works!
Thanks for the reply. I tried that, but nothing happens, just the indicator LED on the power button turns on orange. The tablet does not boot on itself, if I connect the charger. I have to press the power button, but this results again in "Boot image verified failed"
Edit: Update. I figured out how to get into fastboot. I read something on google, with switching the screenlock switch on and off. That doesnt worked for me: The thing was, to hold the power button AND the volume button with the two knobs, then the tablet starts, to release the power button and THEN, while still HOLDING the volume button pressed, to switch on and off the screenlock button. Then the bootloader starts into fastboot mode, going into androidsdk and typed in cmd "fastboot oem unlock" solved the problem. The ROM starts and everything is fine
Why you don't write into the mentioned thread? There seems to come the issues from then ask there, sorry can't understand why opening new thread instead asking there.
Also the first time heard sucha thing, I also change the rooms from cm10 to Jacobus, back to stock, on cool one and to cm and back, to test everything and try something out.
Never had issues buy this ways
Gesendet von meinem GT-N7000 mit Tapatalk 2
I don't have the right to post in the proper thread, so I opened up a new one.
In order to install a JB based ROM, you need the JB compatible CWM. The version of CWM you used is apparently for ICS, so I am a little surprised it worked to install CM10. Where did this 6.0.2.3 come from? Use 6.0.1.5 from pawitp. I've used it and swapped/flashed ROMs at least ten times. Never encountered that issue (or any issue). As a matter of fact, I would just run Vorbeth's EasyRoot as it does all the grunt work for you. I've used it twice and it worked flawlessly.
It is just too late... bad luck for me today, I fullbricked the tablet, after performing a restore with CWM 6.0.1.4. Not bootloader, nothing. Just APX Mode.
V4lk0 said:
It is just too late... bad luck for me today, I fullbricked the tablet, after performing a restore with CWM 6.0.1.4. Not bootloader, nothing. Just APX Mode.
Click to expand...
Click to collapse
Hi I had the same issue after flashing from CM10.1 to CoolOne. However I fixed it by unlocking the bootloader => reinstalling recovery => flashing CM 10.1 back.
Did you have any luck recovering from APX?
Gullinbursti said:
Did you have any luck recovering from APX?
Click to expand...
Click to collapse
No, unfortunately not. I gave my tablet 2 weeks ago to the acer repair service and got it back today. The support said, that they have changed the mainboard and flashed the latest android on the tablet, but they did that on guarantee, so I didn't had to pay something ^^ Now it is running Android 4.1.1 Stock ROM from Acer.
Exact same problem
I am having the exact same problem. I am able to boot into recovery mode but then I get the android laying down with with the red triangle, question mark. My bootloader is unlocked but aftrer the update my screen is stucked on the ICONIA TAB startup screen.
Hi Everyone,
I apologize in advance if this is the wrong place to post such question.
I have a Samsung Galaxy Ace (GT-S5830) and I still have Android version 2.2.1 installed on it.
I would like to install Cyanogen Mod 7, but I'm having a few problems.
This is the first smartphone I've attempted to modify.
The phone is at the moment unlocked(it was locked to Vodafone Portugal, but I've unlocked it before attempting to modify anything).
I followed the instructions on the Cyanogen MOD wiki page.
But now I'm having a bit of an issue at the moment!!
I was only able to complete the 1st part of the instructions, installing ClockworkModRecovery kernel, but when I try to do the instalation of CM7 itself, I'm unable to!!
If I press Home+Power and release once the Samsung screen logo appear, the screen gets stuck on the phones Samsung logo, doesn't do anything, doesn't go to recovery mode, I waited about 30 minutes and then had to press Power and then it reboots.
If I press Home+Power+Volume Up I get to the 'RAMDUMP ARM9 Mode' screen, doesn't do anything else, pressed Power for a very long time, doesn't power off, had to remove the battery.
If I press Home+Power+Volume Down goes to Download mode, but doesn't do anything either!!! Power off does't work, had to remove the battery aswell!!
This means I'm unable to get to the second part and install CM7!!!
Good news is that if I just press Power to turn the phone On, and let it load, it still works, I can still enter the PIN number, etc, so the phone is still working properly!!!!
I've double checked the applications that I have installed and 'CWM Manager' is showing as installed, but needs SuperUser access to function.
I haven't rooted the phone, and now anything that requires to try to boot in recovery mode is out of the question, because of course I can't get to recovery mode.
I've also tried to root the phone using SuperOneClick
No go!!
Also tried Instant Root:
No go!!
Also tried using Odin Multi Downloader v4.38, but doesn't do anything, it says couldn't find device.
All applications were copied to the phone's sdcard and running from there.
Does anyone know if I can use 'adb' from the Android SDK to root the phone? And how I can do that?
Can someone please provide some more information regarding this?
I have no idea what else to try!!
Thank you very much,
Ricardo,
Rooted with iroot,
Downloaded the V8 ROM, SuperSu, Kernel for N801X, WiFi Fix for N801X and Remove phone stuff for N801x
- Installed rashr from Google play store and granted root when asked.
- from rashr installed the latest twrp recovery image.
Here is where I fouled up. I held down the power and volume down keys until
I got a warning about installing non official stuff. The I held down the volume up key
(which I think was the wrong thing to do) Now I am sitting with an Android logo and a
warning "Downloading do not turn off target!!" What's happening? How do I fix this? Can I fix this?
HELP.
p.s. It says ODIN Mode at the upper left.
mangurian said:
Rooted with iroot,
Downloaded the V8 ROM, SuperSu, Kernel for N801X, WiFi Fix for N801X and Remove phone stuff for N801x
- Installed rashr from Google play store and granted root when asked.
- from rashr installed the latest twrp recovery image.
Here is where I fouled up. I held down the power and volume down keys until
I got a warning about installing non official stuff. The I held down the volume up key
(which I think was the wrong thing to do) Now I am sitting with an Android logo and a
warning "Downloading do not turn off target!!" What's happening? How do I fix this? Can I fix this?
HELP.
p.s. It says ODIN Mode at the upper left.
Click to expand...
Click to collapse
nothing wrong you can reboot if you don't wanna root. BTW this is the download modus which is needed for rooting via odin
mangurian said:
Rooted with iroot,
Downloaded the V8 ROM, SuperSu, Kernel for N801X, WiFi Fix for N801X and Remove phone stuff for N801x
- Installed rashr from Google play store and granted root when asked.
- from rashr installed the latest twrp recovery image.
Here is where I fouled up. I held down the power and volume down keys until
I got a warning about installing non official stuff. The I held down the volume up key
(which I think was the wrong thing to do) Now I am sitting with an Android logo and a
warning "Downloading do not turn off target!!" What's happening? How do I fix this? Can I fix this?
HELP.
p.s. It says ODIN Mode at the upper left.
Click to expand...
Click to collapse
keep the device on , let the battery drain out.. try turning on it again , it worked for me
I'm a noob at the Android customization stuff, so bear with me.
I have an old Samsung Galaxy S3 phone, and I was planning on flashing a custom ROM. I rooted it successfully with KingoRoot, then installed ROM Manager from the Play Store. I flashed ClockworkMod from the ROM Manager, then accidentally pressed "reboot into recovery". The phone rebooted into a screen with the phone saying that the custom recovery can be harmful and all, because I forgot to unlock the bootloader. So I pressed Volume Down and Power at the same time to restart into the phone. Then I install EZ-Unlock to unlock my bootloader. I think it was successful, but when I turned off the phone, I couldn't turn it on again. No boot screen or anything. I tried putting in the charger with the battery in, but nothing. Then I removed the battery and put the charger back inside, then an orange notification light appeared for 1-2 min, then disappeared. I don't exactly know what happened.
I tried the debrick process for the Samsung Galaxy S3 (https://forum.xda-developers.com/showthread.php?t=2581166), but nothing happened. I really don't know what to do and would appreciate any help. Thank you in advance.
totalnotjunk said:
I'm a noob at the Android customization stuff, so bear with me.
I have an old Samsung Galaxy S3 phone, and I was planning on flashing a custom ROM. I rooted it successfully with KingoRoot, then installed ROM Manager from the Play Store. I flashed ClockworkMod from the ROM Manager, then accidentally pressed "reboot into recovery". The phone rebooted into a screen with the phone saying that the custom recovery can be harmful and all, because I forgot to unlock the bootloader. So I pressed Volume Down and Power at the same time to restart into the phone. Then I install EZ-Unlock to unlock my bootloader. I think it was successful, but when I turned off the phone, I couldn't turn it on again. No boot screen or anything. I tried putting in the charger with the battery in, but nothing. Then I removed the battery and put the charger back inside, then an orange notification light appeared for 1-2 min, then disappeared. I don't exactly know what happened.
I tried the debrick process for the Samsung Galaxy S3 (https://forum.xda-developers.com/showthread.php?t=2581166), but nothing happened. I really don't know what to do and would appreciate any help. Thank you in advance.
Click to expand...
Click to collapse
That's the only guide you could use that might work, you need to use a correct SD card, one that matches the internal memory of the phone.
There's no other way to fix it, EZ unlock is for an old version. All it does now is brick phones.
BadUsername said:
That's the only guide you could use that might work, you need to use a correct SD card, one that matches the internal memory of the phone.
There's no other way to fix it, EZ unlock is for an old version. All it does now is brick phones.
Click to expand...
Click to collapse
Oh, thanks, I didn't know that. Turns out I was using the wrong version of the debrick file, so I used the correct one and it worked. But once it rebooted, it softbricked, so I'm working on fixing that right now. Thanks for the quick reply. I'll be sure never to use EZ-Unlock again.
totalnotjunk said:
I'm a noob at the Android customization stuff, so bear with me.
I have an old Samsung Galaxy S3 phone, and I was planning on flashing a custom ROM. I rooted it successfully with KingoRoot, then installed ROM Manager from the Play Store. I flashed ClockworkMod from the ROM Manager, then accidentally pressed "reboot into recovery". The phone rebooted into a screen with the phone saying that the custom recovery can be harmful and all, because I forgot to unlock the bootloader. So I pressed Volume Down and Power at the same time to restart into the phone. Then I install EZ-Unlock to unlock my bootloader. I think it was successful, but when I turned off the phone, I couldn't turn it on again. No boot screen or anything. I tried putting in the charger with the battery in, but nothing. Then I removed the battery and put the charger back inside, then an orange notification light appeared for 1-2 min, then disappeared. I don't exactly know what happened.
I tried the debrick process for the Samsung Galaxy S3 (https://forum.xda-developers.com/showthread.php?t=2581166), but nothing happened. I really don't know what to do and would appreciate any help. Thank you in advance.
Click to expand...
Click to collapse
IT WAS JUST A SINGLE APP WHICH HARD BRICK YOUR DEVICE..
NOW THE ONLY OPTION IS TO MAKE YOUR DEVICE ALIVE IS JTAG. (JTAG IS THE ONLY OPTION FOR HARD BRICK DEVICE)
I AM SURE ABOUT ALL THIS BECAUSE EXACTLY THE SAME HAPPENED WITH ME A YEAR AGO WHEN I TRY TO UNLOCK MY BOOTLOADER WITH THIS EZ-Unlock APP AND MY MOBILE GOT DEAD AND IT COST ME 1500PKR WITH JTAG .
Hello.
So recently, I wanted to uninstall Magisk to experiment further with my phone. I had no experience with SuperSU or custom ROMs and wanted to try it out. I went to uninstall Magisk, but instead restoring the full stock firmware, I uninstalled Magisk root. To fix this, I thought I would need to re-flash Magisk and have it wipe its partition or whatever it's called of the device so that SuperSU can root it. So I went to recovery mode by pressing power button + volume up + home button (I have TWRP recovery installed and it was working since the previous week), however, it just went on a boot loop for 5-10 minutes. I tried taking off the battery, but TWRP would not load after. So I tried to turn the device on. It went on a bootloop. I went to the mode where you download a custom OS (volume down + power button + home button) to "cancel" the process and restart the device. It worked, and my device restarted properly.
Now here is when I become a big idiot. I went on the TWRP app (I don't remember if I made it a system app or not) and found that all of its root options were still there. I go on other apps that rely on root; Greenify, Servicely, etc, and they functioned without telling me that my root was gone. So I downloaded the latest version of TWRP and "flashed" it through the TWRP app. I then rebooted my phone. It went on a bootloop.
I tried the methods I mentioned above, but the phone wouldn't start. Since I was away for 5 days without a computer, I kept trying. I tried to remove the battery for intervals of 5 minutes, 10 minutes, half an hour to put it back and then to turn it on. I repeated booting to recovery, regularly booting and the custom OS "cancel" thing I did after removing the battery for extended periods of time. Nothing worked.
Now I'm back home and trying to fix my phone with a laptop. Bad news is, I got a new laptop, and I haven't connected my phone with it at all, so the laptop doesn't recognize the phone. I tried my old laptop, but it wouldn't recognize my phone either. I installed ADB and Fastboot but it wouldn't recognize the device. I also tried Odin, but it didn't detect the device either. My bootloader is unlocked; I'm pretty sure I left OEM unlocking on before this happened (and USB debugging too). Please help me. I
I know I sound like a complete idiot (and tech noob) but I just want to fix this.
MCMarsBoyee said:
Hello. So recently, I wanted to uninstall Magisk to experiment further with my phone. I had no experience with SuperSU or custom ROMs and wanted to try it out...
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within one of the following Q&A type threads that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3207909
https://forum.xda-developers.com/showthread.php?t=3298654
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.