This thread for question and answer. Reserved.
Hey I need your help. I have edited /fstab.qcom file(backup fastab.qcom.bak). I can start TWRP but I don't where the "root" partition is?
/-
|- /system is patirtion
|- /data is patirtion
But where is / itself
I tried restoring boot partition from dd IMG that I had, but it didn't help. Help me please. It's urgent. My phone was only phone. This is my only phone.
Someone tell me where are / or root are stored
ro.build.id=LMY47V
ro.build.version.security_patch=2017-07-01
ro.product.name=Alcatel_4060A
def.tctfw.brandMode.name=Alcatel IDEAL
def.tctfw.build.number=M7UUAU1
ro.product.pcsuite=Alcatel IDEAL
Does this version support VoLTE Video call?
Has anyone realise sudden changes in brightness to 100% while using ?
Well I happens with my phone. Sometime at night when I set brightness to minimum and using my phone the brightness increases. To set to minimum I change the valve by sliding then back to minimum.
Are you guys are suffering from this problem or its just me.
Does this phone support usb otg?
Why my contact app is showing nickname, how can I disable this, I tried installing google contact, but no success, looks like problem of OS not contact app.
kdm6389 said:
Has anyone realise sudden changes in brightness to 100% while using ?
Well I happens with my phone. Sometime at night when I set brightness to minimum and using my phone the brightness increases. To set to minimum I change the valve by sliding then back to minimum.
Are you guys are suffering from this problem or its just me.
Click to expand...
Click to collapse
Fixed by M7UUAU1 ROM
@Chupi383 I want to draw your lillte attantion for once to post number #3, #5, #6. These are not serious issue. just i want to know if u have suffered these problem, maybe you have fix to share with us.
The root partition on Android is always in the initrd in the boot partition.
I see no option for video call of any sort on any firmware for this phone. It is designed for US use, and video call isn't a standard feature here.
No, USB OTG is not supported. The software stack for it is present, so some USB OTG detector apps will tell you it's supported, but the hardware for it is not there. I plugged in a few devices with USB OTG adapters that work on my Galaxy S7 Edge and nothing happens -- no power to the device, nothing detected on the phone. Even using a tee adapter that lets me power both the device and phone USB port, the phone doesn't enumerate or detect the device.
I have been using Google's contacts app successfully and it works well. I haven't tried assigning a "nickname" to a contact. It just shows their first and last name as I've entered them.
Brightness does randomly change to 100% on some firmware versions. Best I can tell, it only happens with USB debugging enabled, or possibly only after connecting to the phone on adb. Disable USB debugging and reboot after you're done hacking and it shouldn't do that anymore.
Alcatel 4060a I rooted device using kingoroot or king root with purify already with it, I obtained root ,used phone. I removed system apps n bloatware. Ok then I wanted to give my phone away airgo I took back root access, n went n removed all my Google account s then went into phone settings, and reset it. Well erased n Reeset. As soon as I hit the reset button. It went to black then Alcatel powered by Android screen. Now is stuck can't get it to boot to anything. My computer recognizes but when I run adb command window says no connected devices. Help me please like step by step instructions please
ashluvsgary420 said:
Alcatel 4060a I rooted device using kingoroot or king root with purify already with it, I obtained root ,used phone. I removed system apps n bloatware. Ok then I wanted to give my phone away airgo I took back root access, n went n removed all my Google account s then went into phone settings, and reset it. Well erased n Reeset. As soon as I hit the reset button. It went to black then Alcatel powered by Android screen. Now is stuck can't get it to boot to anything. My computer recognizes but when I run adb command window says no connected devices. Help me please like step by step instructions please
Click to expand...
Click to collapse
adb dont work on reseted phone, to anable you have to go setting > developer mode > USB debugging.
or wait for 30min to start phone since it take little time after reset
or you have bricked your alcatel
try using
Code:
$ [B]fastboot -i 0x1bbb devices[/B]
ashluvsgary420 said:
Alcatel 4060a I rooted device using kingoroot or king root with purify already with it, I obtained root ,used phone. I removed system apps n bloatware. Ok then I wanted to give my phone away airgo I took back root access, n went n removed all my Google account s then went into phone settings, and reset it. Well erased n Reeset. As soon as I hit the reset button. It went to black then Alcatel powered by Android screen. Now is stuck can't get it to boot to anything. My computer recognizes but when I run adb command window says no connected devices. Help me please like step by step instructions please
Click to expand...
Click to collapse
Go to through https://forum.xda-developers.com/android/general/super-guide-alcatel-one-touch-4060a-t3621525 to unbrick
Related
We now know that the new vibrant phones have the hardware key disabled to enter recovery mode. But these phones are not defective. The hardware key has been purposefully disabled as part of a misplaced strategy to secure a phone that has basically no security built into it.
Therefore it is really easy to gain root access to these phones. However the process requires the use of the adb program that is part of the google android sdk. This program likes to run on a 32-bit linux distribution. Since it will not run on a 64 bit system, here is how I managed to gain root access to my phone:
1. Download the sdk from google.
2. Boot into linux on a 32 bit machine. (I used ubuntu live cd on an old Toshiba laptop with an available linux partition to mount on the hd. Your mileage may vary.)
3. If you are not using ubuntu make sure that your c library is compatible.
4. Install the google android sdk on the hd linux partition, e.g. /home/android.
5. Plug your Samsung vibrant into the usb port on the linux machine.
The following steps are specific to ubuntu. The important thing to remember is that the adb program must run its server as root to gain the access we desire.
6. Start the terminal app: Applications > Accessories > Terminal
7. Mount the partition and change to the sdk directory:
sudo mount /dev/sda2 /media
cd /media/*/home/android/tools
7. Start the adb server:
sudo ./adb start-server
8. Make sure your device is recognized:
./adb devices
If you do not see your device connected you have some troubleshooting to do.
9. Reboot your phone into recovery mode:
./adb reboot recovery
Congratulations! You just gained root access to your hardware locked vibrant.
This message has been posted by my old g4 laptop while tethered through t-mobile 3g using wireless tether on my brand new Samsung vibrant.
M_T_M said:
Hmmmm..good enough to stick!
Click to expand...
Click to collapse
Yeah it's good, but you should move this thread to Samsung Vibrant forum.
This works on any android phone.
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
r2d4 said:
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
Click to expand...
Click to collapse
Would this also work for the new T-mobile G2 4G ?
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
r2d4 said:
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
Click to expand...
Click to collapse
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Installing the root update
tjhart85 said:
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Click to expand...
Click to collapse
If you want to keep root after your next reboot, you need to update your filesystem. The first step is to install the programs busybox and su.
Before you boot into recovery mode, make sure you have the update.zip file downloaded onto your phone's internal memory card. Whatever is on this card will be left alone even upon a factory reset. But the phone's internal memory will be wiped. The update.zip file merely installs those two programs to the internal memory and doesn't wipe anything.
1. Download the root update for your phone. Rename the file update.zip and place it on the root directory of your device's internal flash memory.
2. Once you are in recovery mode, use the volume keys to scroll and the power key to select "reinstall packages". (This works on the vibrant. The g2 may be slightly different.)
3. Your phone will reboot and you will find the Superuser app has been installed. This app lets you grant root access to applications that need it.
Now you can download powerful apps from the market to gain even more control over your phone.
I hope this helps.
Does boot with a live CD of 32 bit ubuntu on my AMD64 work?? or do i need to boot on a computer with a 32bit processor as well?
Running the 32 bit distribution cd on your 64 bit system should be fine.
Need help
Hello I need help to unlock my samsung vibrant
can someone tell me where i can fin the link
thank you
r2d4 said:
If you want to keep root after your next reboot, you need to update your filesystem. The first step is to install the programs busybox and su.
Before you boot into recovery mode, make sure you have the update.zip file downloaded onto your phone's internal memory card. Whatever is on this card will be left alone even upon a factory reset. But the phone's internal memory will be wiped. The update.zip file merely installs those two programs to the internal memory and doesn't wipe anything.
1. Download the root update for your phone. Rename the file update.zip and place it on the root directory of your device's internal flash memory.
2. Once you are in recovery mode, use the volume keys to scroll and the power key to select "reinstall packages". (This works on the vibrant. The g2 may be slightly different.)
3. Your phone will reboot and you will find the Superuser app has been installed. This app lets you grant root access to applications that need it.
Now you can download powerful apps from the market to gain even more control over your phone.
I hope this helps.
Click to expand...
Click to collapse
Does boot with a live CD of 32 bit ubuntu on my AMD64 work?? or do i need to boot on a computer with a 32bit processor as well?
unlocking on root system
I was wondering if it was okay to unlock a Samsung Vibrant when it is already rooted?
the JI6 OTA update fixed this issue.
If you upgraded using Kies or ODIN, you may still be HWL, BUT, there is a fix:
If you can not get into download mode, please try this:
** Please note this is for JI6, if you are running froyo do not do this **
untermensch has a fix for those who are HWL'd that seems VERY effective. I always heard some who updated from JFD to JI6 had the HWL fixed automatically, but that was not the case for everyone. It appears those who updated OTA got the fix, but most who did ODIN or Kies did NOT get the HWL issue fixed.
Please see his excellent thread by clicking here. Hope this helps.
If you are using froyo, I imagine you could revert back to JI6 and flash this to fix the HWL.
HWL but scared to update.zip
Hi all. I am running Ji6 and i am still hardware locked. I just want to root my phone so i can delete some stock bloatware.
Can root my phone without having to "fix" HWL. I am wondering, how Kies successfully upgraded my phone to JI6 with HWL? If I upgrade to froyo (once available) will the upgrade access recovery? WIil the upgrade brick my phone?
I know for Froyo there is z4root which seems to be an easy, safe way to root..
So should i plan on waiting for Froyo??
Just fyi... I just had my vibrant warranty replaced through tmobile, when I registered it with samsung the manufacture date showed november. I had no issues getting to recovery using the keypresses.
The whole warranty swap went alot better than I was expecting, phone looks new not refurbed, it came in like 1 or 2 days from when I called, AND they unlocked it for me even though I was at my unlock limit since it was a warranty replacement, just make sure they specify that in the request.
Sent from my Samsung Galaxy S - powered by Team Whiskey™
Thanks for help, T-mobile's Vibrant is hardware locked.
Of course, you don't need either Linux or 32-bit, it worked just fine from a Windows 64-bit machine (and will from any that has a version of ADK for it). Just Shift+right-click in "android-sdk-windows\platform-tools" and select "Open command window here", enter "adb devices" to launch the daemon and make sure your device is connected properly (it needs to be in "USB debugging mode", which you can select in settings), and then enter "adb reboot recovery". Phone should restart, select "Reinstall Packages" using volume keys and power key to enter.
Bought Samsung Vibrant - SGH T959 - Have questions...
Hi all,
I joined the forums recently to learn about rooting my EVO. With the help of a number of people on the forums I was able to easily root my EVO and install a custom ROM. Still haven't flashed any new Kernels yet but I may do that soon.
Anyway, I bought a Samsung Galaxy S (Vibrant) which of course is T-Mobile phone. I got it from my friend for $50 because I know they sell on eBay for anywhere from $250-$350.
However, I recently upgraded the phone for him before I bought it to 2.2 (Froyo). This seems to be bad for me because now I want to Unlock the phone so that it can be used with any carrier, or a carrier aside from T-Mobile but I've read in the forums here that it's hard to Unlock the device if you've upgraded to Froyo via Kies.
Can anyone help me with Unlocking my device and could someone give me a quick rundown of what the key commands are for this phone too? Such as how to access recovery to flash a ROM. Although I am not going to ROOT this device unless it is required in order to unlock the phone.
Thanks in advance for any help!!!
Oh, and I won't get mad if my post needs to be moved to another thread either so please move it to the right place if it needs to be.
Thanks!
PAinguINx said:
Hi all,
I joined the forums recently to learn about rooting my EVO. With the help of a number of people on the forums I was able to easily root my EVO and install a custom ROM. Still haven't flashed any new Kernels yet but I may do that soon.
Anyway, I bought a Samsung Galaxy S (Vibrant) which of course is T-Mobile phone. I got it from my friend for $50 because I know they sell on eBay for anywhere from $250-$350.
However, I recently upgraded the phone for him before I bought it to 2.2 (Froyo). This seems to be bad for me because now I want to Unlock the phone so that it can be used with any carrier, or a carrier aside from T-Mobile but I've read in the forums here that it's hard to Unlock the device if you've upgraded to Froyo via Kies.
Can anyone help me with Unlocking my device and could someone give me a quick rundown of what the key commands are for this phone too? Such as how to access recovery to flash a ROM. Although I am not going to ROOT this device unless it is required in order to unlock the phone.
Thanks in advance for any help!!!
Oh, and I won't get mad if my post needs to be moved to another thread either so please move it to the right place if it needs to be.
Thanks!
Click to expand...
Click to collapse
Well now, I found this http://forum.xda-developers.com/showthread.php?t=761045 but is it cool to do this while running Froyo? And another question, since I bought this phone from a friend can I still have it replaced/fixed (if needed) if the warranty is still active on it?
Thanks!
Back to original ROM by Odin, T959UVJFD.tar and s1_odin_20100512.pit
in dounload mode (down + power)
Hi,
so I have been using this root guide for my HTC G2 http://forum.xda-developers.com/showthread.php?t=2448887 ,and like in the video, when I opened the first screen to imput code, my phone did not show up. Have I forgotten to install something? it just says searching even though my phone is connected to my computer.
any help is appreciated, rooting is turning out hard for me to do, thank you
SuperSho4 said:
Hi,
so I have been using this root guide for my HTC G2 http://forum.xda-developers.com/showthread.php?t=2448887 ,and like in the video, when I opened the first screen to imput code, my phone did not show up. Have I forgotten to install something? it just says searching even though my phone is connected to my computer.
any help is appreciated, rooting is turning out hard for me to do, thank you
Click to expand...
Click to collapse
Hey SuperSho4,
I'm afraid you need to give a little more information what exactly you are doing, i.e. which software you are using etc. Do you see your phone in lsusb?
I'm using Ubuntu and the latest adb, and I have to be root on my computer for adb to work and find my phone.
You also may try another way of rooting, e.g. I used UniversalAndroot-1.6.2-beta5.apk to do that, which you can transfer to your SD-Card and then select for installation with probably any File Browser, (just make sure that you enabled "other software sources").
For me. there's was a quirk in that method: Using the default settings, UniversalAndroot only claimed to successfully get root-access, but left everything unchanged! Only after finding a comment on some website did I try to check both check-boxes (log and temporary install) - this time it worked (it installs yet another app called SuperUser)! (I then ran it again without the temporary setting enabled, which at least did not revoke the SuperUser-Account).
Good luck!
Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.
I installed GLTools for the 5th time, I have never had any issues with it before.
Suddenly this time I installed the version of GLTools on XDA forums(this forum!), the phone turned off afterwards, had to manually turn it back on, now it just sits at the Alcatel Boot logo!
I can access the phone with ADB when its turned off and do adb shell, su, with success. Now how can I remove GLTools and restore the phone to normal useage!?
Please somebody help me here, If i get it working again I will never use any software thats not straight from Google Store again!
Please help!
phenom2955 said:
I installed GLTools for the 5th time, I have never had any issues with it before.
Suddenly this time I installed the version of GLTools on XDA forums(this forum!), the phone turned off afterwards, had to manually turn it back on, now it just sits at the Alcatel Boot logo!
I can access the phone with ADB when its turned off and do adb shell, su, with success. Now how can I remove GLTools and restore the phone to normal useage!?
Please somebody help me here, If i get it working again I will never use any software thats not straight from Google Store again!
Please help!
Click to expand...
Click to collapse
get aroma file manager.
go 2 recovery
mount system
flash aroma recovery file mgr
navigate to root/data/app And delete gltools.
go to data/data/(gltools folder) and delete it.
Then go to root partition and delete all 3 texure plugins.
U r done.
possible issue : maybe u messed with the system partition or plugins of latest gltools isn't compatible.
How do i do that if i cant boot the phone?
Please man I am begging you, need to fix this. Cant have another brick on something stupid.
I dont have a custom recovery since there was not one available for my phone. Alcatel OneTouch Fierce XL. Can't I delete the files with adb commands?
You know what happened. I Attempted to try an older version of GLTools 1.97 ealier to see if it would work better to clear up performance of a game, I got rid of that. Then today I went ahead to reinstall 1.99. I suppose the driver files were still installed and are conflicting?
How can I delete them with ADB commands? I have SU access in ADB, just need to know the proper commands and directories to reach and delete the proper files?
phenom2955 said:
How do i do that if i cant boot the phone?
Please man I am begging you, need to fix this. Cant have another brick on something stupid.
I dont have a custom recovery since there was not one available for my phone. Alcatel OneTouch Fierce XL. Can't I delete the files with adb commands?
Click to expand...
Click to collapse
sure.. u can do it with adb too.
but i don't know the process.
Better u ask t3snake in gltools thread.
Hope he will help u
Great now windows applied an update and now my phone is unauthorized! Please tell me I can roll it back and it will be Authorized again?
****ing great now becuase windows updated itself it is unauthorized and I am ****ed.
phenom2955 said:
****ing great now becuase windows updated itself it is unauthorized and I am ****ed.
Click to expand...
Click to collapse
@T3snake
a issue here..
yea think, as if windows had it all plotted against me.... itnt that wierd?
phenom2955 said:
****ing great now becuase windows updated itself it is unauthorized and I am ****ed.
Click to expand...
Click to collapse
If u didnt know It means ur computer isnt authorized anymore(u have to do it after enabling usb debugging for every system)
U can always flash a system.img using fastboot
yea I had authorized it and told it to remember this computer always before the phone bricked. It was working fine last night, I just didnt know what adb commands to use after adb shell and then "SU", from there I should have been able to delete the GLTools drivers if I had known the commands. Then suddenly windows decided in all its glory to update and restart, now its Unauthorized again. So I guess I am ****ed eh? I was hoping a restore point to a couple hours before windows update or rollback the update would set the PC to the same state when It was still authorized, but no Dice huh?
I dont think my phone has a fastboot, the only button combos that work are Power+VolUp, brings up a stock recovery with only 4 options, Restart Phone, Factory Reset, Wipe Cash, and Power down. Thats it.
God this is such bull****, Next droid device I get I am locking down 100% as much as can get and not using anything on it but a few basic apps from GooglePlay.
Thanks anyways though.
Hi, I am trying to unlock a Galaxy J1 Ace SM-J111F/DS for my colleague. The phone belonged to his younger brother who had passed away in an accident, now that he's gone, we have no information as to now to unlock his phone.
I have tried researching and searching around for methods but to no avail. I was hoping maybe someone here could provide some assistance
A factory reset is out of the question as he needed to access information stored inside the phone
Some device details:
Device is locked by a pattern lock
Unable to unlock via Google account(No one in his family knows his account name/password)
Phone is not Rooted
Phone is FRP Locked
Things I have wanted to try and done so far:
Intended to flash a bypass to unlock the lock screen
Attempted to flash a custom recovery in order to flash the bypass, however FRP is locked and it does not allow a custom recovery to be flashed
Attempted various methods of "security exploits" to unlock, but appears to be patched on current firmware
Tried to search methods of unlocking FRP, however all the methods I've seen so far requires access to developers option, or requires a flash of stock firmware.
Tried accessing device via ADB, however it does not work as USB debugging is not enabled
I'm currently out of options trying to do this by myself, we would really appreciate it if someone could help us out in this
If powered on, and plugged in to PC, is it 'seen' at all?
robneymcplum said:
If powered on, and plugged in to PC, is it 'seen' at all?
Click to expand...
Click to collapse
Yes, it is "seen", but I can't do anything else to it
If it is seen, there is a chance you can get data off it.
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Chilli71 said:
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Click to expand...
Click to collapse
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
XenoJin said:
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
Click to expand...
Click to collapse
Ill jump in this one to. im in a similar situation. I have a lg g vista that no conventional method is working to bypass frp. Device is not encrypted. My prob is. I believe if i can downgrade back to stock kk which the phone was released with it didnt hve frp then so bam im in. But lgflash tool wont downgrade. Always errors. Loads of diffrent settings have been made. Also followed guides to a t.
But in ure case to if it is possible to dlmode and odin back to kk or earlier u should the be able to skil the google login totally. I dont know if ure device came with kk from factory or lolipop. Frp was implemented in loli so kk should be good. Maybe
Two comments:
1) I have a Huawei G8 in front of me. I worked all weekend with it with bootloader/fastboot. I wanted to test the lock screen/adb behavior, But to my surprise ADB does not find it w/ and w/o lockscreen. --> There are different possibilities why the phone does not show up (it worked in the past with this phone/notebook, but quit working). Before you flash make sure that your setup is working (best with an identical mobile). It seems that USB connection can behave different in Bootloader/Recover/Android OS mode.
2) I made a dirty flash (w/o erasing flash) of Lollipop over Marschmallow last weekend. The result was that many directories including SDCard0 where not accessible. Also user data was not accessible. And you have always the chance that you mess something up when flashing and you loose the content.
If the data is really important your friend could pay a data rescue company (if you don't loose your face). I'm pretty sure that programs exist that can be loaded into RAM with bootloader (fastboot boot) that provide an interface to the PC (in the easiest case, adb again).
Chilli