Database Info

[Q] [HELP BRICK] power button broken bootloop

nexus s i9023 with ics offical rom rooted and unlocked but power button suddenly stopped working so i flashed a jb volume wake zip to enable this feature but it gave me a bootloop now i cant even recover because of the power button i managed to get in the fastboot mode by putting the battery and quickly press volume up but in fastboot the device is not even detected by the usb (original) i have sdk and usb drivers but the problem is i put my phone in usb its like ive put a potato nothing happens and the sentences usb control init and usb control init end have disappeared in fastboot mode so i cant send commands to the phone through adb is there a way to make my phone detectable although when my phone is in the bootloop process its detected by the computer normally but no response of course.
THANKS in ADVANCE

osos96 said:
nexus s i9023 with ics offical rom rooted and unlocked but power button suddenly stopped working so i flashed a jb volume wake zip to enable this feature but it gave me a bootloop now i cant even recover because of the power button i managed to get in the fastboot mode by putting the battery and quickly press volume up but in fastboot the device is not even detected by the usb (original) i have sdk and usb drivers but the problem is i put my phone in usb its like ive put a potato nothing happens and the sentences usb control init and usb control init end have disappeared in fastboot mode so i cant send commands to the phone through adb is there a way to make my phone detectable although when my phone is in the bootloop process its detected by the computer normally but no response of course.
THANKS in ADVANCE
Click to expand...
Click to collapse
EDIT/UPDATE 1: i managed to get into recovery mode :victory:
HOW? NOTICE: IM NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KINND YOU DO TO YOUR PHONE USE AT YOUR OWN RISK
1. keep phone plugged in usb
2.download SDK Manager from (http://developer.android.com/sdk/index.html)
3.install it in root path in Windows 7>>>>>C:/Users/[yourusername]/SDK
4.boot your phone NORMALLY in boot loop
5.connect your phone in usb if you neglected step one
6.your computer should detect it
7.open command promote (CMD) (shortcut windows flag+R) type cmd
8.a black screen will appear type in it "cd SDK/sdk/platform-tools" and press enter
9.path now should be C:\users\[your user name] \SDK\sdk\platform-tools>adb shell second line [email protected]:/ #
10.now type this (copy and paste is recommended) "mount -o remount,rw -t yaffs2 /system /system"
11.now simply type reboot recovery and your phone should reboot in recovery img
12.wipe factory settings now you should be good

osos96 said:
EDIT/UPDATE 1: i managed to get into recovery mode :victory:
HOW? NOTICE: IM NOT RESPONSIBLE FOR ANY DAMAGE OF ANY KINND YOU DO TO YOUR PHONE USE AT YOUR OWN RISK
1. keep phone plugged in usb
2.download SDK Manager from (http://developer.android.com/sdk/index.html)
3.install it in root path in Windows 7>>>>>C:/Users/[yourusername]/SDK
4.boot your phone NORMALLY in boot loop
5.connect your phone in usb if you neglected step one
6.your computer should detect it
7.open command promote (CMD) (shortcut windows flag+R) type cmd
8.a black screen will appear type in it "cd SDK/sdk/platform-tools" and press enter
9.path now should be C:\users\[your user name] \SDK\sdk\platform-tools>adb shell second line [email protected]:/ #
10.now type this (copy and paste is recommended) "mount -o remount,rw -t yaffs2 /system /system"
11.now simply type reboot recovery and your phone should reboot in recovery img
12.wipe factory settings now you should be good
Click to expand...
Click to collapse
I will try it now! If this works, then you are superman for me :good:
Edit:
1. should I type "adb shell second line [email protected]:/ #" after the new path is set and press enter?
2. if I do it, i always get the message "the command mount is wrong or can not be found"

!Lür said:
I will try it now! If this works, then you are superman for me :good:
Edit:
1. should I type "adb shell second line [email protected]:/ #" after the new path is set and press enter?
2. if I do it, i always get the message "the command mount is wrong or can not be found"
Click to expand...
Click to collapse
Was much easier for me, don´t know why.
Solution for me:
1. Turn device into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
Requirement is a working Android-SDK.

!Lür said:
Was much easier for me, don´t know why.
Solution for me:
1. Turn device into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
Requirement is a working Android-SDK.
Click to expand...
Click to collapse
yup i just made it a step by step tut for noobs and your welcome

Need help preparing Xoom for official updates

Hey folks,
I´ve ran my MZ601 xoom on EOS builds over the last 1,5 years.
Obviously its unlocked and rooted. Currently its running CWM Recovery 4.0.0.4
Now I want to go back to stock to install the latest official updates to get the updated drivers for the UMTS radio/modem module.
After that I want to unlock and get root again to use any of the lastest custom Roms again.
Switching to a touch based recovery would be nice too.
I surfed around a bit and I´m rather confused which steps I need to perform in order to do this.
I guess I need to remove root and lock the bootloader again before I can install official updates ?
Could someone please toss me in the right direction? Maybe some step-by step list?

You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloader​Then run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot reboot​You'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img​(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
If you are unable to use adb in recovery, then you can enable this through Windows by doing the following:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.

Wow, what a detailed guide
Thank you sir

No problem!
Let me know how it goes, hopefully shouldn't have any problems.

Resetting worked great :good:
Right now I´m in an OTA marathon
all that unlock, root and recovery stuff sounds familiar so I don´t expect any problems.
Thanks so far :good:

alecbond said:
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Click to expand...
Click to collapse
Ok, so this is not working
after I flash touch recovery and do thta reboot thing I can enter touch recovery, thats fine.
Flashing universal root, fine.
THEN,
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
gives me error since in recovery mode there ist no adb connection
Whatever when I choose to reboot the system, recovery warns me that it will get overwritten by boot and ask me to disable this.
Shall I do this?
EDIT: Nevermind, I decided to be a little brave and just confirmed that message.
Now touch clockwork seems to be persistent and I´m a happy Xoomer again

Sorry, I had meant to reply during my lunch break.
Edit: Realised the time on the second of your posts, so wouldn't have been much help on my lunch anyway
Well I believe I just learned something new!
Either that or I'd forgotten it asked.
I assume it disables the action rather than deletes those files.
My method was just so you can use the reverse rename in future to re-enable the overwrite on boot.
In future, not that you'll necessarily ever need this information, you can enable adb in recovery through windows by doing the following
When in recovery and connected to your PC, open Device Manager, find your phone, usually under 'Other Devices'.
Then right click > Update driver > Browse my computer > Let me pick from list > Pick your phone (either one if there's two shown)
Should confirm driver installed then adb should work.
I didn't include the above previously as I couldn't remember having to do it personally.
Glad to hear all is well though!

alecbond said:
You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloader​Then run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot reboot​You'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img​(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.
Click to expand...
Click to collapse
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD

XxLordxX said:
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
Click to expand...
Click to collapse
No problem, I'd be honored!

How to root xolo x900

hello there can any one help me to root xolo x900 i had tried every thing that is available in internet every thing failed is there any way to root it

First make sure you have the following
- Xolo ICS update installed.
- Intel USB driver for Windows
- The Root Installer
-------------------------------------------------
Then,
- Enable USB Debugging mode and then connect your Phone to PC.
- Extract root installer archive and run the runme.bat file.
- In your PC, type 1 in the command prompt for “Make a choice”. your device will ask for Full Restore. You will not loose data. Select Restore my data. Finally, your device will reboot twice and you will be rooted. Note that your screen may flash before the second reboot which is fine.

Managed to Root my xolo x900
I think I've found a way to root my x900. It's currently running the latest version of SuperSU 2.16 and has the stericson busybox installed.
I've tried rooting the x900 with all possible methods and have never been successful. Especially the part where it says 'restore started' then 'restore ended' almost immediately. By no means am I an expert on this and the following was achieved with a lot of trial and error, I've tried to put it down in the simplest way I could.
Warning: Try the following at your own risk.I do not wish to be held responsible for any damage your phone might incur.
These were my steps:
1.I extracted the boot.img(a) from the orange-sandiego ics signed update file found at modaco forum
2. I extracted the boot.img(b) from the official rom downloaded from androidxda.
3. Download and install minimal adb and fastboot installer from XDA forums along with the Intel-usb and adb drivers from androidxda.
4. Download the latest Superuser binary and .apk .zip from the official XDA thread
5. Download the stericson.busybox.apk from the internet.
6. Place the boot images[(a) and (b) renamed to your preference] in the main folder of the minimal adb/fastboot exe, found in C: program files x86...... Also unzip the SU file and place su from the x86 folder and the Superuser.apk into the main adb/fastboot folder along with the busybox.apk.
4. Turn on usb debugging and switch off the phone.
5. Hold vol-up + power keys for about 10seconds to put the phone into bootloader mode. It should say 'droidboot' on the screen.
6. Open a command prompt from the adb/fastboot desktop shortcut you have after you're done installing the adb/fastboot exe.
7. Type in
fastboot devices
Your device will be listed, then type in
fastboot flash boot boot.img(a)
This will flash the boot.img from the orange-ics-update, then type
fastboot reboot
Your phone should now reboot to system but the screen will not be functional and will only show different colors.
8. Now type
adb devices
To confirm your device is visible. Follow this with:
adb shell
su
mount -o rw,remount /system
exit
exit
adb push su /sdcard/su
adb shell
su
cat /sdcard/su > /system/xbin/su
ln -s /system/xbin/su /system/bin/su
chmod 6755 /system/xbin/su
exit
exit
adb install Superuser.apk
adb install stericson.busybox.apk
adb reboot bootloader
9. Now once again after confirming that the device is recognized in fastboot do this:
fastboot flash boot boot.img(b)
fastboot reboot
Your phone will now reboot to system, and it will have root access and busybox installed.
Good Luck.

You user framaroot v 1.9

0967894983 said:
You user framaroot v 1.9
Click to expand...
Click to collapse
I've tried all versions of framaroot before, none worked, neither does towel root, cydia impactor, v-root or shuame root helper.

Wicked! Thanks for that.
Are you able to install a full Linux distro on the device after it is rooted or is the bootloader still locked?

[TWRP RECOVERY] + [ROOT] Teclast Tbook 11 (E5A6) Android 5.1

Hello,
This is my first post on how to root and install TWRP recovery on the Teclast Tbook 11 (E5A6) android 5.1
The TWRP works with touch and I haven't encounterd any problems with it
I have not created the TWRP, it is made by nik2670
We only flash or boot the recovery, then install SuperSU 2.82- 201705271822. Nothing else !
Sorry for the mirrors. (I will remove them if you're the owner)
Be sure to have ADB drivers v1.4.3 installed before you continue.
Download TWRP 2.8.7.0. Recovery Tbook 11 and ADB and Fastboot and put it in a folder on your desktop
Enable USB debugging on your tablet (Settings->Developers->usb-debugging)
Connect your tablet with your PC
Open up a CMD prompt in the folder you have your ADB. Win+R type CMD, hit enter. Copy the path of ADB and put in the CMD prompt
Code:
cd [path]
Mine was cd "C:\Users\Thermaltake\Desktop\ADB FASTBOOT FILES WINDOWS"
In the CMD prompt, type
Code:
adb devices
If you see your device you good to go.
Type
Code:
adb reboot bootloader
your tablet reboots, select android while it reboots
Now we're in fastboot mode, just to be sure we see the device type
Code:
fastboot devices
. If you can't see your device like me you have to manually install drivers.
Do you have the recovery.img in the same folder as ADB? Good. Type
Code:
fastboot boot recovery.img
OR
Code:
fastboot flash recovery recovery.img
to permanently have the TWRP recovery on your device (I recommand boot)
Your tablet is now in recovery mode! You can acces the internal storage. Add SuperSU-v2.82 on your device.
Hit Install->SuperSU-v2.82-201705271822->Swipe to confirm flash->Wipe dalvik cache->Reboot----> DONE !
Image of succesfully root
Thanks for following my guide, if there are any problems I try to update the tutorial or provide more information to you!
Mathero11
Thanks to nik2670 for the recovery, chainfire for supersu and unpersonally xda developers for other flash/root tutorials

How to escape TWRP? Activate ADB w/ broken screen?

So my screen broke on my Note 10+, leaving only the top 15% with display and the bottom 60% with touch. I am trying to activate ADB on it so that I can backup my internal storage.
I booted into TWRP so that I could backup the rest of my system, which I did successfully, but because of the bad touch screen I am unable to hit the ADB side load button. I'd like to reboot into the system because I have ADB enabled there, however I also cannot click the reboot to system button, only reboot to download and shutdown. Since I can't see most of the screen, it is also not possible to access the terminal and work from there.
Anybody know how I can escape TWRP or otherwise activate ADB? Thanks for the help.

Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload

jwoegerbauer said:
Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload
Click to expand...
Click to collapse
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.

AllanRSS said:
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.
Click to expand...
Click to collapse
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot

jwoegerbauer said:
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot
Click to expand...
Click to collapse
I can not use ADB. It is for this very reason I am asking how to enable ADB. But thank you for these valuable ADB commands, I'll be sure to reboot my system once I enable ADB