Database Users

Unrevoked problems

Sorry to be a hassle, but I just can't figure this out!!
I've rooted my phone with the "new clarified method" thread, gotten to the clockwork mod and everything, but once I've done that I just cannot get the Unrevoked 2 to work. I've tried it on Windows 7, xp, and osx, and nothing seems to work! The main issue I'm getting is that it'll do the whole process, and then I think it says "reboot to recovery" and then I just get that old phone with a red triangle error. What could I possibly be doing wrong??? It can't be driver issues, because doesn't OSX do that automatically?

I had a similar issue on windows 7 and a simple pc reboot seemed to work for me.

Nope, still no luck. Am I supposed to put these Reflash files on the phone somewhere? I just feel like I'm missing some big step or something. Why is there no good tutorial on this process yet?

Oh my god I think I'm going to go insane! Please someone, point me in the right direction! I have done this hundreds of times now, I'm gonna die. All I can get is "Done!" and then my phone is showing me a big dumb red exclamation point triangle thingy. What am I doing wrong??????

Was I supposed to do something once I first reached the clockwork on my initial root? Cuz all I did was reboot to OS. I don't know if anybody can tell, but I'm kinda desperate. hah

Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?

larry996 said:
Did you make sure that the phone is recongized in the device manager once plugged in? Need to help us out tell me what you have done so far? Did you install the SDK USB Drivers?
when at the command prompt, did you type adb devices? Does your device show up as connected?
Click to expand...
Click to collapse
I was having the same problem also until I ran reflash.exe and the command prompt both as admin. I also reran Android SDK installing all of the updates. After plugging in the phone, the SDK picked up two more updates, one of which was USB drivers. Once I did that, things seemed to have worked.

Use attn1's method. The clarified method didnt work for me properly.
I assume you never flashed a rooted rom after reaching clockwork mod. If not the phone is not yet rooted. You have to get back to clockwork recovery and flash a rooted rom (either attn1's liberated one or his stock rooted rom). Both found in his liberated thread. Then set up all the drivers for unrevoked and run it. It should work then.

When my phone is just sitting in bootloader, it is not recognized by adb devices.

You have to go through the whole loop process again booting your phone into recovery and connecting the usb cable.

gdeadfan said:
When my phone is just sitting in bootloader, it is not recognized by adb devices.
Click to expand...
Click to collapse
Thats not good, try reformatting your sd card on your pc with an external reader not with your phone and try again. I'm almost certain it needs to be recognized by adb devices when in bootloader.

Just managed to install the Liberated beta ROM, but now unrevoked can't even get past superuser privelages. it's not popping up anymore

Nevermind, it gets past superuser now, but now it just says "waiting for reboot" and completely reboots the phone to the point at which i can use it regularly

Have you installed the hboot drivers?
Re-ran unrevoked?
Edit: Does it reach "done!"?

Yes, yes, and yes. And my phone just keeps getting to the red triangle. doesn't make any sense to me! And at this point, I'm positive I have no drivers getting in the way like Sync etc., and I'm sure HBoot is installed correctly.

Go to the android market and download titanium backup. It requires root so if it installs we know that you are at least rooted.

Try this, because I had the same problem. Go into device manager with Revoked2 says waiting for reboot. Look under devices above my computer or below cant remember and right click uninstall and remove the android device. reboot your computer then see if it installs are does it automatically, if not don't do anything just plug the phone in and get to hboot/ red triangle screen, then try revoked2 again. This finally got loop to read my device then when I got to clockwork I loaded "liberated rom"
Screw revoked2, just get to clockwork recovery and have liberated rom on your SD card ready to go. Then after install I ran revoked2 for clockwork mod.
Good Luck

Please avoid creating new threads for existing topics. Before creating a new post or thread, you should read all available information in the many Aria rooting threads.
Thank you for your understanding and cooperation as we work to organize the Aria forums.

[Q] Atrix Special "Brick" Problem with touchpad - reset

So, guys...here's a real challenge for all of you.
I taught my friend how to enable multitouch on Atrix 4G and I did mine correctly, but he tried editing the touchpad.cfg file using the Atrix, removed the READ permissions of file and restarted the phone. Obviously, the phone can't read the touchpad.cfg anymore and touchpad is not working at all.
Gladly (yeah, this is sarcasm), the Android won't let he do a factory reset because the Froyo version needs an extra step of TOUCHING the screen to complete the recovery command.
I tried accessing it via ADB too, but it requires you to TOUCH the screen and choose your USB connection type.
So, touch is out of question. Is there any way to access this cell phone and make the files readable again (or replace the files, whatever makes it working). The phone has USB Debugging enabled, if it helps.
p.s: sorry if it's been posted before, but I search the forum A LOT and could only find two similar posts that were unanswered. (Please, let's not make this one be the third. We don't need that.)

Have you tried fastboot? try turning off the phone and holding power + volume down until you see the word Fastboot then press volume up. You should be able to do whatever from adb now. Try that or an official update.
this should be in Q&A btw
Sent from my MB860 using XDA App

Hey, Tayshun, thanks for the reply
I tried using Fastboot, but the device still can't be found by ADB shell. If you can point me some direction of what I may be doing wrong it would be great.
And I don't really understand when you say "that or an official update". How was I suppose to update the phone without touching it at all? Via Recovery Menu too? What is the option?
Thanks in advance

chapter81 said:
Hey, Tayshun, thanks for the reply
I tried using Fastboot, but the device still can't be found by ADB shell. If you can point me some direction of what I may be doing wrong it would be great.
And I don't really understand when you say "that or an official update". How was I suppose to update the phone without touching it at all? Via Recovery Menu too? What is the option?
Thanks in advance
Click to expand...
Click to collapse
if you can't access ADB to push a file, and you can't get recovery to work to reflash a fruitcake, then you're only choice is to sbf flash a 2.3.4 gingerbread sbf. either that, or the pudding sbf if you wish to stay unlocked.
it will give you a fresh, stock state of the phone. if he is on Gingerbread though, you can ONLY flash those two sbf's, any others will hard brick your phone.
EDIT: I just thought of something, it's a long run but you might be able to fix permissions in Recovery mode, i don't know whether it'll work or not though.

Alcapone263 said:
if you can't access ADB to push a file, and you can't get recovery to work to reflash a fruitcake, then you're only choice is to sbf flash a 2.3.4 gingerbread sbf. either that, or the pudding sbf if you wish to stay unlocked.
it will give you a fresh, stock state of the phone. if he is on Gingerbread though, you can ONLY flash those two sbf's, any others will hard brick your phone.
Click to expand...
Click to collapse
Well, he's running Froyo 2.2, so I guess this option is not available for us to try. Even though because I'm not really sure I can go throught all these steps.
Alcapone263 said:
EDIT: I just thought of something, it's a long run but you might be able to fix permissions in Recovery mode, i don't know whether it'll work or not though.
Click to expand...
Click to collapse
Can you please explain me this idea of yours in more details? I think that all I need is to be able to communicate with the device without using touch. I read somewhere that using Fastboot, I could do anything via ABD, but even putting the phone on this mode, I still get "device not found" on ADB console. Maybe I'm missing some extra step. But again, if you could please explain me about this permission thing in Recovery Mode, it would be great, Alcapone. Thanks!!!

Flash a pudding 2.2 sbf

[q] rooting nexus 4 kitkat 4.4.2? Help!!

hey guys im new to the whole rooting and the whole android world .. anyways im on the latest version of kitkat (4.4.2) on my nexus 4 and i dont know how to root it. can anyone help me please?
also i dont know if its normal but my nexus 4 still looks like 4.3 JB .. any suggestions as to what can be the issue?
all help is greatly appreciated. thanks

The ui looks basically the same except for more white than blue.
Follow the guides on how to root.
Won't lay it all out for you since there a million guides and so on.
But you will need to unlock the bootloader. That will wipe all your data off your device. Everything will be gone.
After that you just need to boot up and put the su. Zip on the device. Reboot into the bootloader again flash a custom recovery. Or just boot it. Then flash the zip you put on the phone with the custom recovery.
That's it. Done. Now stock rooted.
If this don't make sense to you. It probably won't. Read the quides in general.

albundy2010 said:
The ui looks basically the same except for more white than blue.
Follow the guides on how to root.
Won't lay it all out for you since there a million guides and so on.
But you will need to unlock the bootloader. That will wipe all your data off your device. Everything will be gone.
After that you just need to boot up and put the su. Zip on the device. Reboot into the bootloader again flash a custom recovery. Or just boot it. Then flash the zip you put on the phone with the custom recovery.
That's it. Done. Now stock rooted.
If this don't make sense to you. It probably won't. Read the quides in general.
Click to expand...
Click to collapse
it doesnt work everytime i try and use ADB it keeps saying error=device offline so i cant even root it. and when i say its exactly like 4.3 JB its literally the same. it still has the widgets menu in the drawer and everyhing, but on my friends its different. its starting t frustrate me ..

zareefpeeroo said:
it doesnt work everytime i try and use ADB it keeps saying error=device offline so i cant even root it. and when i say its exactly like 4.3 JB its literally the same. it still has the widgets menu in the drawer and everyhing, but on my friends its different. its starting t frustrate me ..
Click to expand...
Click to collapse
Did you install Android SDK in your PC? It needs to be installed and set up first, and making sure ADB debugging box is checked in Developer Options in your phone. In addition, when you plug your phone into your PC the first time, look in your phone and select Yes when a dialog pop up asking for authorization to remember your phone.

zareefpeeroo said:
it doesnt work everytime i try and use ADB it keeps saying error=device offline so i cant even root it. and when i say its exactly like 4.3 JB its literally the same. it still has the widgets menu in the drawer and everyhing, but on my friends its different. its starting t frustrate me ..
Click to expand...
Click to collapse
Adb offline is a different issue. But it's irrelevant. Adb is not needed.
We need to use fastboot. Not adb. You're doing nothing but wasting your time with adb.
You would get adb up and running for what exactly? To issue the command adb reboot bootloader or adb reboot recovery..... Forget adb...

Why are you trying to root? You shouldn't undertake such tasks if you're not 100% educated on the subject.
Sent from my Nexus 4 using xda app-developers app

TWRP Stuck

I cant seem to get out of TWRP. I use adb and i used "adb boot recovery" and i cant seem to get out. The issue i think i have is that the adb keeps pushing the command to the phone. Now before you say "Just unplug the phone and reboot it"... I did that. Now it seems that the code is stuck with the phone . Iv tried to put it into TWRP my self without adw and tryed to reboot it but that didnt work. No other tread helped me. If you could tell me how to how to fix this or link me to a thread somewhere else. Its a Verizon phone.
Thanks -
Subby
if it helps: I was trying to root :good:

Shubbyshak said:
I cant seem to get out of TWRP. I use adb and i used "adb boot recovery" and i cant seem to get out. The issue i think i have is that the adb keeps pushing the command to the phone. Now before you say "Just unplug the phone and reboot it"... I did that. Now it seems that the code is stuck with the phone . Iv tried to put it into TWRP my self without adw and tryed to reboot it but that didnt work. No other tread helped me. If you could tell me how to how to fix this or link me to a thread somewhere else. Its a Verizon phone.
Thanks -
Subby
if it helps: I was trying to root :good:
Click to expand...
Click to collapse
I got the phone to RAM dump boot i have no idea how i got it there. But its something else. THE PHONE IS NOT BRICKED.

So you're stuck in recovery??? If so, just flash one of the Verizon based roms that should get you going.

indoz said:
So you're stuck in recovery??? If so, just flash one of the Verizon based roms that should get you going.
Click to expand...
Click to collapse
Thanks but i got out of it. I think it was because i tried to root is so the microsd got corrupted because the rooting process screwed up
Thanks -
Shubb

Shubbyshak said:
I cant seem to get out of TWRP. I use adb and i used "adb boot recovery" and i cant seem to get out. The issue i think i have is that the adb keeps pushing the command to the phone. Now before you say "Just unplug the phone and reboot it"... I did that. Now it seems that the code is stuck with the phone . Iv tried to put it into TWRP my self without adw and tryed to reboot it but that didnt work. No other tread helped me. If you could tell me how to how to fix this or link me to a thread somewhere else. Its a Verizon phone.
Thanks -
Subby
if it helps: I was trying to root :good:
Click to expand...
Click to collapse
This happened to me. I just had to use the hardware buttons to boot into recovery then reboot from there and that got me out of the loop. Not sure why that happens.

Flash mobile with volume down broke

Hello all,
After 5 hours searching and almost done, it seems like the phone won against me...
I have a friend who has his device under Android5, latest version, and need at least Android 6 to update his bank app, which required this update to work normally.
The worst part here, is that the device has the down volume button not working anymore (at all)
I wa a little rusty because I moved two years ago to iOS, but I have some memories with my old samsung and Nexus 6 flashing.
So here's what I've tried so far, I can forgot to mention some stuff because it's been a long work lol
So I have a 1GB SD Card and my indows 10 computer.
- I started to download and install all ADB and fastboot drivers.
- I've activated Debugged mod and OEM Unlock. I couldn't find if the bootloader is allowed for unlock or not, because the command didn't work. So I supposed that yes, it is. The device is the J3 SM-J320FN bought in France, new.
ADB work perfectly, but I didnt manage to get the device recognsied with the Fastboot mode. "ADB Devices" list the phone, but fastboot devices command does not show anything, it goes back to another line.
My friend didn't mentionned that he has installed a recovery. I don't know how, but the recovery is very basic. Here's a photo of the recovery screen. It appear when i press Vol+, home and power button, but I can't move anywehre because of the low volume button not working. Vol-, home and power doesn't work for the Download mode.
I finally managed to enter in download mode by using the command ADB REBOOT DOWNLOAD. With that, I honestly don't remember how I did it, but I think I've flashed a file which allow me to root the device from ODIN. With this, I've got confirmation of Root Checker app that the device is now rooted.
I've passed many hours to make some tests here and there, but nothing gave me a real result. Then I found two apps : ROM Manager and Flashfire.
ROM Manager : The app says that it doesn't find Superuser in System/bin/su. So it's like the device is not rooted. Nothing seems to work on the app too.
Flashfire : It seems like this app can do the job, but I can't finalize the process. So I've changed the year of the phone to 2013 to get the app running, I've tried a wipe, and here... Yahoooo ! A big Loading screen with many line codes, and then... nothing. My computer make the sound to say that it recognised the device, and a full blackscreen for 10mn. Exactly same process if I try to flash a ROM, or whatever action (even doing a backup).
I suppose it's because the app wasnt granted the root permissions. Not sure, because even if the phone seems to have the root status, I never get any pop up to ask if I allow to get the permission or not. I've tried to dwnload the APK for SuperSU app or something, and nothing seems to work.
So now, It looks like i'm close, but I also think that there is nothing more to do.
The device is powering on, with all its data, and seems rooted, but I can't do anything. It seems like the recovery is the only option to go trough the install.
So you guys, do you have any ideas of what can I do ?
I'd like to install LineageOS, but any ROM with Android 6.0 min. will be fine for me.
Also, pardon my english. I'm french lol
Thank you for your help..!

Alerion13 said:
Hello all,
After 5 hours searching and almost done, it seems like the phone won against me...
I have a friend who has his device under Android5, latest version, and need at least Android 6 to update his bank app, which required this update to work normally.
The worst part here, is that the device has the down volume button not working anymore (at all)
I wa a little rusty because I moved two years ago to iOS, but I have some memories with my old samsung and Nexus 6 flashing.
So here's what I've tried so far, I can forgot to mention some stuff because it's been a long work lol
So I have a 1GB SD Card and my indows 10 computer.
- I started to download and install all ADB and fastboot drivers.
- I've activated Debugged mod and OEM Unlock. I couldn't find if the bootloader is allowed for unlock or not, because the command didn't work. So I supposed that yes, it is. The device is the J3 SM-J320FN bought in France, new.
ADB work perfectly, but I didnt manage to get the device recognsied with the Fastboot mode. "ADB Devices" list the phone, but fastboot devices command does not show anything, it goes back to another line.
My friend didn't mentionned that he has installed a recovery. I don't know how, but the recovery is very basic. Here's a photo of the recovery screen. It appear when i press Vol+, home and power button, but I can't move anywehre because of the low volume button not working. Vol-, home and power doesn't work for the Download mode.
I finally managed to enter in download mode by using the command ADB REBOOT DOWNLOAD. With that, I honestly don't remember how I did it, but I think I've flashed a file which allow me to root the device from ODIN. With this, I've got confirmation of Root Checker app that the device is now rooted.
I've passed many hours to make some tests here and there, but nothing gave me a real result. Then I found two apps : ROM Manager and Flashfire.
ROM Manager : The app says that it doesn't find Superuser in System/bin/su. So it's like the device is not rooted. Nothing seems to work on the app too.
Flashfire : It seems like this app can do the job, but I can't finalize the process. So I've changed the year of the phone to 2013 to get the app running, I've tried a wipe, and here... Yahoooo ! A big Loading screen with many line codes, and then... nothing. My computer make the sound to say that it recognised the device, and a full blackscreen for 10mn. Exactly same process if I try to flash a ROM, or whatever action (even doing a backup).
I suppose it's because the app wasnt granted the root permissions. Not sure, because even if the phone seems to have the root status, I never get any pop up to ask if I allow to get the permission or not. I've tried to dwnload the APK for SuperSU app or something, and nothing seems to work.
So now, It looks like i'm close, but I also think that there is nothing more to do.
The device is powering on, with all its data, and seems rooted, but I can't do anything. It seems like the recovery is the only option to go trough the install.
So you guys, do you have any ideas of what can I do ?
I'd like to install LineageOS, but any ROM with Android 6.0 min. will be fine for me.
Also, pardon my english. I'm french lol
Thank you for your help..!
Click to expand...
Click to collapse
So why not just install Marshmallow with Odin?
After that install TWRP the same way?

Is it possible ?
I though that only installing custom rom will allow the phone to go beyond 5.1. Because the phone can’t find any update on OTA.
So if I download the correct file, flashing it should work ?
Thanks for the answer

Alerion13 said:
Is it possible ?
I though that only installing custom rom will allow the phone to go beyond 5.1. Because the phone can’t find any update on OTA.
So if I download the correct file, flashing it should work ?
Thanks for the answer
Click to expand...
Click to collapse
I assumed the J320 had received the MM update. However it seems not.
In that case custom is the only way. For that you will need to install twrp with Odin.

Exactly what I though yesterday. I will call him to see what can I do.
So the latest versions of TWRP are compatible with the touch screen, and then the volume down button isn’t required to process ? After the recovery installed, I will be able to find the zip of the custom rom and install it right ?
Thank you again

Alerion13 said:
Exactly what I though yesterday. I will call him to see what can I do.
So the latest versions of TWRP are compatible with the touch screen, and then the volume down button isn’t required to process ? After the recovery installed, I will be able to find the zip of the custom rom and install it right ?
Thank you again
Click to expand...
Click to collapse
Twrp is touch driven so no need for hard keys.
The only issue is that you need to reboot immediately into recovery mode after flashing twrp.
As down isn't working you will need to leave auto reboot enabled and catch it at the right moment to boot to recovery as it reboots.

Excellent. I will try that and will let you know. Thank you