Database Info

N00b in need of help. Lock Bootloader?!

Hi,
I've posted a thread or two on here but I cant get any proper help or instructions to help me out
Basically, my phone has its boot loader unlocked (lock symbol shows up) and I have tried all methods to lock it but nothing works.
I cant boot the phone into recovery, and drivers arent very coperative either
I need help! ... I'm planning on selling my phone ,so need to restore it asap.
The problem started when I first bought the phone, it wouldnt update or reboot, so I tried a one click root, it unlocked the bootloader and everything looked fine. UNTIL, an OTA update came along, I applied it, but when my phone came to restart it was stuck on the google logo. I cant even update anymore
Pleease could someone help this n00b out? Really appreciated
Thanks!

Read. No seriously, these forums are chockful of help threads and guides on how to root your phone, install a custom recovery, fix your phone when it's stuck.
Since you want to go back to stock, I'll give you a hint...
1) Unlock bootloader using fastboot (DONE!)
2) Flash custom recovery using fastboot
3) Wipe data/factory reset in custom recovery
4) Install Gingerbread 2.3.6 in custom recovery
5) Lock bootloader using fastboot
Edit: If you're having trouble getting your phone to be recognized in fastboot mode, use the PDANet drivers for Windows. Usually that does it.

Thanks for the reply.
Trust me, I've read around this forum a lot! I've tried the drivers with PDA net but still nothing works. The drivers (adb I think) aren't recognised so can't get anywhere.
I get easily lost with the guides. I don't think they're newbie friendly. I .e. where am I supposed to type 'fastboot oem lock'?
Btw I have no custom rom installed ( I don't think) and when I downloaded the root checker from the market, my phone is recognised as not being rooted (even though I can't apply updates :/ )
I think main thing is that my phone isn't recognised in fastboot mode....

soulja786 said:
Thanks for the reply.
Trust me, I've read around this forum a lot! I've tried the drivers with PDA net but still nothing works. The drivers (adb I think) aren't recognised so can't get anywhere.
I get easily lost with the guides. I don't think they're newbie friendly. I .e. where am I supposed to type 'fastboot oem lock'?
Btw I have no custom rom installed ( I don't think) and when I downloaded the root checker from the market, my phone is recognised as not being rooted (even though I can't apply updates :/ )
I think main thing is that my phone isn't recognised in fastboot mode....
Click to expand...
Click to collapse
Learn about fastboot here
http://wiki.cyanogenmod.com/wiki/Fastboot
For the drivers, you can watch the video here
http://www.youtube.com/watch?feature=player_embedded&v=4AHucGBZHMQ
The guides are as noob friendly as they can be.

Thanks a lot for your help! I owe u polobunny , I can now lock the bootloader BUT, Ive rooted my device with 'twrp' and want to flash a ICS ROM. Which ROM would you reccomend and to install it do I add the rom to SD card and install from twrp interface? Or is it more complicated than that ?
Thankss

soulja786 said:
Thanks a lot for your help! I owe u polobunny , I can now lock the bootloader BUT, Ive rooted my device with 'twrp' and want to flash a ICS ROM. Which ROM would you reccomend and to install it do I add the rom to SD card and install from twrp interface? Or is it more complicated than that ?
Thankss
Click to expand...
Click to collapse
Installing the Rom should be the same regardless of recovery. Yes put the rom on the SD card and flash away.

Thanks but do I need to wipe data/restore or can I just flash?

soulja786 said:
Thanks but do I need to wipe data/restore or can I just flash?
Click to expand...
Click to collapse
Oh boy, you do need to read my friend.
In recovery (twerp, twink, Clockwork, whatever) back up your current set up. Then... I suggest you wipe data/factory reset, then wipe dalvik and cache yes. I do it 3 times on Clockwork just to be sure. The cleaner you get it the less problems you will incur. I always wipe fresh unless instructed specifically to do otherwise.
Flash your Rom, gapps, kernel and enjoy.

[Q] Stuck during cyanogenmod install

Dear XDA community,
I installed Clockwork recovery and the USB drivers. The device is unlocked and when in fastboot mode it is correctly identified by my PC as falcon XT1302 with an USB connection. When in recovery mode, the device appears as "Android" in the devices menu in Windows 7 and there is a yellow "!" next to it. Unfortunately after formatting system and deleting the cache as per instructions the device won't boot up. I'm stuck at the bootloader unlock warning screen. I can access fastboot mode and recovery mode but that's it.
I want to place the cyanogenmod zip inside the internal SD card of the Moto G but adb doesn't work. I get the device not found error when inputting a command. adb devices returns a blank. I don't know which drivers to install or what to do. I've tried various fixes on forums but none work. Maybe USB debugging is the problem although I distinctly remember switching it on. In any case, I can't boot so I can't change the settings.
All I want is a way to place the cyano .zip in the phone /sdcard so that I can install it. I'm all out of ideas. USB mounting doesn't seem to work. Neither does sideloader (or maybe I messed it up?) I am at wit's end.
I didn't have anything important on my phone so I did not make a backup. In hindsight, this was a stupid mistake. I've certainly learned a lot during the install attempt.
If possible please give step by step instructions. I am not a very technical person. Any help would be greatly appreciated. pls halp
kind regards

Dont worry too much if you can acces Fast Boot just download STOCK Firmware for your version I can't post links cuz im beginer searc under help "Restore STOCK Firmware" and flash it. :fingers-crossed:
Reply here i will tell you how if you not fixed it alredy

Thanks but that's not really what I want to do. I want to flash cyanogenmod on it.
regards

hechadnebiphyh said:
Thanks but that's not really what I want to do. I want to flash cyanogenmod on it.
regards
Click to expand...
Click to collapse
As above said flash stock boot up copy cm11 and gapps reboot boot loader flash cwm or twrp reboot recovery wipe data,cache,dalvik flash ROM gapps reboot all done
Sent from my Nexus 7 using Tapatalk

Thanks to the users who replied. I've managed to solve the problem. :laugh:

Would have been faster though to get your device recognized while in recovery. You can install the driver manually and it should work. Just search for seperate driver files and ignore the Windows message that it is probably 'not compatible etc.'.
Then your device is connected properly and you can get ADB sideload to work from your recovery.

[Q] TWRP not installing right on GS3

Hey Guys!
I have rooted 3 other GS3's using the method listed here:
http://theunlockr.com/2013/04/02/how-to-root-the-verizon-samsung-galaxy-s-iii-running-android-4-1-2/
All other roots worked great! I was able to flash TWRP (I realize that the specific tutorial above calls for CWM instead of TWRP) and then install a CyanogenMod ROM. However, this time it did not go well.
I forgot to enable USB debugging before flashing VRALEC the first time, and when I went to run TWRP (2.7.0 for d2vzw) I realized that it did not mount the file system I thought that this was unusual and then realized that I need to enable USB debugging. I completely unrooted the phone and installed stock recovery and rom (VRBMF1, Android 4.1.2) once this was done I figured that I would go back to a personally tried and true version of TWRP (2.5.0 for d2vzw). At this point I was careful to ensure that I enabled USB debugging before proceeding with the root process.
With TWRP 2.5.0 I was prompted with a password. This befuddled me and upon some reading on the forums I came across a solution that worked for others but NOT ME. (Essentially you clear the cache and to a factory reset 3x in TWRP recovery and it will stop prompting you for the password and mount your file system correctly). For me I was unable to mount the cache for dalvic-cache to wipe it and factory reset does nothing.
I have rooted and unrooted my phone approx seven times trying different versions of TWRP, CWM, and even trying to use a seperately downloaded VRALEC file just in case if mine had an error.
I also came across this thread (below) and it did look somewhat promising however it is for android 4.2.1 and I don't want to mess up my phone any more than it already was. I am getting similar (not exactly the same) errors in my TWRP. I also made sure to use the same bootloader that I used on other 4.1.2 android systems in addition to using the d2vzw version of TWRP (It is for this reason that I am not sure that flumpster's comment applies to me). I figured that I would include this information just in case it was helpful:
http://forum.xda-developers.com/showthread.php?t=2228447
Any Ideas? I am really looking forward to trying Liquid Smooth 3.0!

Just a quick addition: I was able to use Casual's root method however I am still running into the password prompt in recovery and 3 wipes is not getting rid of that password prompt..
Thanks in advance for any help!

Stuck on CWM when trying to install CM10.2.1

Hello,
I got this HTC One X from AT&T (->evita) and tried to get CM 10.2.1 running on that.
The steps I made:
Boot into bootloader, go to fastboot, then get the identifier, get unlock token via htcdev and unlocked it with fastboot.
I then flashed CWM 6.0.4.6 for evita via "fastboot flash recovery *filename*". Now I booted into CWM (recovery) and wiped everything instead of first trying to copy the cm.zip onto the sdcard. (I also didnt do this when the stock ROM was still running...)
Now I can access the phone via fastboot in the bootloader but I can not use adb or the USB mount when in CWM. Whenever I plug the phone into my computer (or laptop, doesn't matter. Also tried switching between USB 2 and 3 ports!) Windows keeps making the "unplugged" sound every second.
Reinstalling the latest HTC drivers did not change anything.
Anyone here knows a way how I can stop that or get the zip file on the memory? I also tried flashing the boot.img on boot and tested if I can copy the file then through CWM but that did not work.
Hoping,
NyphoX

Not sure if it'll work but try using TWRP recovery instead:
http://goo.im/devs/OpenRecovery/evita
Sent from my Evita

Installed the most recent version.
I get into the recovry and when I plug it into a computer Windows will keep making the "unplugged"-noise.
I can see the sdcard-directory perfectly when I hit install in both, TWRP and CWM but when I want to mount it via USB it will not change anything and I cannot access it on my PC.
adb doesn't list any device either.
Also, TWRP and CWM keep telling me that my phone is not rooted, when I try to power off or restart. Is that normal?
My other HTC One X (non AT&T) just works fine with cwm 5.*.*.*

It's normal for the recovery to inform you that you're not rooted, it'll suggest that you install superuser but there's no point doing that in your case because you have no working OS installed. Did you at any point perform a factory reset from the bootloader? If so, you've corrupted the internal storage (known bug on modified Evitas) and will need to wipe it with TWRP.
Sent from my Evita

Saw that in your Q&A.
I wiped the internal_sd and tested it after but it still did not work. I also tried a factory reset through TWRP but that did not help either.
Both recovery programs keep telling me "E:Unable to mount '/cache'.
Still not working. Q_Q

Update: I got like the oldest laptop I ever owned and installed the most recent HTC drivers there and tried to mount it. It told me in device manager that the "evita" is not recognized. When I let Windows search automatically it installed the drivers and I am now able to access the memory.
I can only assume what the problem was but it seems like the HTC One X (endeavoru) driver and the evita don't like each other...
TL;DR trying to install now. Will edit.
//EDIT: Windows still screws when I plug the phone to the other computer/laptop, so I just have to use the old machine now. Still thanks for your help, timmaaa!
//EDIT: It does work when I booted CM and enable the USB storage at the other two machines.

[Completed] Help with reinstalling bootloader

Hi.
I am relatively experienced user who has rooted and installed custom roms on samsung galaxy and HTC desire phones before.
I have now attempted to root my alcatel onetouch pixi 4 (4034X) using instructions from this thread :- https://forum.xda-developers.com/android/general/alcatel-one-touch-pixi-4-t3376597
I got as far as flashing twrp recovery and now the phone is stuck in constant reboot. I downloaded alcatels mobile upgrade tool in hopes of reflashing the stock rom but it seems to be looking for a later rom than the one I have installed and keeps telling me I have the lastest and so wont flash.
So can I recover from this at all or have I just bricked my phone? Is there a way to FORCE the mobile upgrade tool to reflash the current rom rather than looking for an upgrade?
It seems that everything except the bootloader is intact so is there another tool I can use to restore the bootloader?
Any help would be greatly appreciated.

Looks like I managed to unbrick using a combination of SP Flash tool and an SPFT rom for the 4034X I found on the internet. will now try reflashing a different recovery tool.

O.K. so I think what is happening is an issue when unlocking the bootloader and not when flashing recovery.
This is what I did:-
1. Enabled developer mode.
2. Turned on usb debugging and unlocked bootloader oem
3. Rebooted phone, plugged in cable and accepted connection authorisation.
4. From windows typed adb reboot bootloader. Went into to fastboot.
5. Typed fastboot oem unlock, Pressed volume up on phone.
At this point I was put back in fastboot but none of the buttons worked and the phone looked like it had frozen. Was It wiping data at this point? There was no indication that it was doing anything.
I removed the battery and reinserted but when I restarted I got the same boot loop problem. Had to restore stock firmware AGAIN.
Am I doing something wrong?

Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?

nyarlathotep_uk said:
Update: I managed to install caliv touch recovery without unlocking the bootloader by using the same sp flash tool I used to restore the stock rom. However, I cant install root. The recovery will only let me sideload and I could only find the chainfire SU binaries for sideload (SuperSU 2.78-SR1 and superSU 2.46). Both of these seem to flash ok using adb sideload with ctr recovery but the phone hangs at the boot logo. I also had superuser-r197 (ph's sueruser) but that wouldn't sideload.
So I now have a custom recovery but still can't root
Has anyone succesfully rooted the 4034X (UK)? If so, how?
Click to expand...
Click to collapse
Hi & welcome to xda-assist,
you can try to force the installation of supersu systemless by this step, chances are good that this will make it boot properly.
boot into twrp >go to the terminal > and type:
echo SYSTEMLESS=false>>/data/.supersu
Don't know if the recovery you use has this terminal option but it's very likely.
You can do additional a Google search on "force SuperSU systemless" to get more information / background information..
Good luck
Sent from my OnePlus 2 using XDA Labs

Thanks for your reply Sam.
I only read that after I had found a copy of a CM13 Rom that worked with The 4034X. I basically flashed superSU first then did a wipe, then installed the custom rom and google apps nano before downloading the supersu apk from google play and reinstalling. Now I have a rooted phone with a custom rom and am somewhat happier. The reason I wanted to root was to remove the bloatware that was taking up 1.5 GB of my already measly 2GB internal memory and this new ROM only takes up .5 GB.
I still have some pain. For example many of the Rom Toolbox Pro functions don't work and I think its because the system image seems protected and refuses to mount rw no matter what I do. Even issuing a remount command using the device name from cat /proc/mounts tells me the block device is read only. I also seem to be unable to verify if I have busybox or install it due to the same reason.
It also took me some time to work out that the boot animations weren't stored in /data/local or /system/media but to /data/system/theme.
This used to be so much easier in the days of ice cream sandwich and lollipop. Ah well!

Update:- Managed to flash busybox 1.26 using a flashable zip via adb sideload in Caliv Recovery (Caliv can't see my adopted storage for some reason).
I'm happy now! Would still like to have a rw system so I can remove some system apps I don't use but its no biggie.