Database Info

[Q] Nexus s 4g locked up

Okay, first of all I know, I'm a total noob. I have followed these forums a long time and have successfully rooted a few phones. One of which was my nexus s 4g. I was trying to unroot the phone so I could get ics. This is when I ran into problems and right now I just want to be able to get my phone working again. Right now I am stuck on the Miui boot up screen and no matter how long I wait it stays on that screen. If I do a battery pull and hold down power and vol up I can get into the bootloader screen with the information as follows: fastboot mode, product name-Herring, HW Version Rev 34, Bootloader version-D720SPAKE1, Baseband version-D720SPAKE1, Carrier info, SPR, serial number-37308B81276A00EC, Lock State-locked. Then the different options I can choose are reboot bootloader, reboot, recovery, power off. If I choose reboot, it takes me back to the mius screen and stays there. If I choose recovery, I get the triangle with the exclamation point. I then hold power and up volume again and I get a screen that says Android system recovery <3e> with reboot system now, apply update from sd card wipe data/factory reset and wipe cache partition. I have tried all of these as well with no luck. When I go to apply update from sd card I get matrix-cfs_v15.5 zip, root.zip, update.zip and then what looks like apps such as Alarms/, Android/,MIUI?, etc. If I try to select any of the first ones such as matrix-cfs_v15.5 zip, I get Install /sdcard... , finding update package..., opening update package..., verifying update package..., E.signature verification failed, Installation aborted. Then it gives me the system recovery options again. Any help would be appreciated.

Did you try ADB fastboot method?

Not sure how to try that

I tried doing the adb, followed all directions and installed and when I go to the command prompt and type in anything, such as, adb reboot bootloader I get, adb is not recognized as an internal or external command, operable program or batch file.

ok I got that working now but when I type adb devices and press enter I get a message saying List of devices attached and then it doesn't show anything and I get the command prompt again saying:c:\android\android-sdk\platform-tools>

also since the phone is stuck in either the miui screen or bootloader I can't get into it to put it in usb debugging mode. I am trying on my own to get this going and am stuck any and all help would be very much appreciated.

TerryUK98 said:
Lock State-locked.
Click to expand...
Click to collapse
I think that means you have a locked bootloader.
And from what you're telling, I believe you have stock recovery.
Also, when you're in fastboot mode, I don't think adb commands apply. Use fastboot commands instead (i.e. fastboot devices).
Search for guides showing you how to install and use fastboot.

I did fastboot as well and the problem I think I am having is it's not recognizing my phone because usb debugging wasn't turned on before it locked up. How would I get it to recognize my phone or download an img to my phone if it is not being recognized. Sorry if this is a stupid question.

You don't need usb debugging in fastboot mode.
You either:
1. Don't have drivers installed.
2. Don't have fastboot installed correctly.
You really need to read a guide or two, through and thoroughly.
Bc it sounds like you have no clues.

Yeah dude. Take a step back and go over what you have installed and where you installed it.Yes, fastboot commands start with fastboot instead of adb. And you're on stock recovery.

Thanks for the answer that I don't need usb debugging in fastboot mode, I wasn't sure of that. I have downloaded and installed my drivers multiple times and when I use the device manager to update drivers it says I have the latest drivers installed already. Whenever I do fastboot commands I will type in fastboot devices and shouldn't my device serial number come up? It just gives me the line c:\android\android-sdk\platform-tools>
And is waiting on me to type a command in. And yes I have been looking at guides all night. I appreciate any help you guys might have and remember we were all noobs at one time.

The zip in this tutorial should help.
It has adb, fastboot, and the drivers needed.
And unlock the bootloader because it is locked.

Finally got it, I had everything downloaded that I needed already, but looking at different forums, etc, it seemed like everyone named it something different. So I just used the one link you gave me and did it exactly the same way and it worked. Thanks so much! and again thanks for your patience.

[Q]Stuck in bootloop with deleted OS, abd not working.

Hey all,
I have a big problem with my TF700.
I wanted to root my device after unlocking the bootloader through the app, but by being dumb I managed to delete the OS in TWRP (thought it was factory reset) and now I'm in big trouble.
The only thing the tablet loads now is the TWRP 2.2.1 recovery. (TWRP came with a root-package, I didn't install it myself.)
Since I can't load an OS that is apparently deleted, I'm stuck with using the (latest) SDK to get the stock rom back on the tablet.
The problem is, it doesn't work, at all. The device is recognised by my (Win7) PC and the 'adb devices' command gives me the ID and 'recovery'.
If I try to push the ROM to the Sdcard folder (or any folder, for that matter) It gives me a "protocol error" with no other explanation.
If I try to sideload it it is stuck on "Waiting for device".
I tried the 'shell' command, just to see what that does, but it also gives me an error.
Other commands can also give the the "error: closed" message.
Since both of those commands don't work, I can't get anything on this tablet, since I can't get this version of TWRP to mount an external (micro) SDcard, the option simply isn't there.
Can anyone help me with this, of has my tablet been reduced to an expensive paperweight?

That's the problem with packages - you don't really know what's in it...
What root package did you use?
You have a very outdated recovery installed. I'm guessing here, since you didn't post your bootloader version and that's the first thing we need to know!
Can you still get into the bootloader?
Boot with Power and Volume Down buttons until you see the tiny script and post your bootloader version. Should be something like 10.6.1.....
Do NOT do anything else in recovery at this point!!!! If it is incompatible with your bootloader you could hard brick!
Once we know if you have fastboot access and what your bootloader version is, we can help you to flash the correct recovery in fastboot. With that installed it's a piece of cake to get you up and running.
But be patient! Don't do anything else you're not quite sure of!

*Update Below*
I believe the culprit was the 'Install recovery' method "Scott's Recovery install tool"
I tried a few but most didn't do anything. Every tool I tried comes from the xda forums and checked youtube videos explaining the steps.
If I boot using Volume down + power, nothing extra happens. I just see in the left hand corner "this device is unlocked", since I unlocked the bootloader using the ASUS app.
If I use the command adb reboot bootloader, it goes to TWRP 2.2.1.
Does this imply that I also deleted the bootloader?
Update: I deleted all drivers and software regarding the tablet from my PC and I installed the adb setup package from these forums and reinstalled the (universal?) driver package. This turned out to be a newer version of adb, and I actually managed to push a file to the tablet with no problems. I am reluctant to try anything else at the moment, since this whole ordeal had given me quite the scare (and the desire to learn more about this all)
Can anyone help me revive my tablet?

FooYoungHi said:
*Update Below*
I believe the culprit was the 'Install recovery' method "Scott's Recovery install tool"
I tried a few but most didn't do anything. Every tool I tried comes from the xda forums and checked youtube videos explaining the steps.
If I boot using Volume down + power, nothing extra happens. I just see in the left hand corner "this device is unlocked", since I unlocked the bootloader using the ASUS app.
If I use the command adb reboot bootloader, it goes to TWRP 2.2.1.
Does this imply that I also deleted the bootloader?
Update: I deleted all drivers and software regarding the tablet from my PC and I installed the adb setup package from these forums and reinstalled the (universal?) driver package. This turned out to be a newer version of adb, and I actually managed to push a file to the tablet with no problems. I am reluctant to try anything else at the moment, since this whole ordeal had given me quite the scare (and the desire to learn more about this all)
Can anyone help me revive my tablet?
Click to expand...
Click to collapse
Ok, good - you got adb working. The adb command to boot into the bootloader is
Code:
adb reboot-bootloader
Note the hyphen
Also I wonder if you pushed Power and Volume Down long enough. You should feel the tablet vibrate twice, then see some tiny script and 3 icons appear. That would be the bootloader menu and in it, you are in fastboot mode by default.
The next step would be to check if you have a fastboot connection.
The command for that is
Code:
fastboot devices
Read my guide on flashing a custom recovery and rom very carefully and follow the steps outlined to get TWRP 2.8.0.1 on your tablet.
Ask any questions you may have in that thread.
http://forum.xda-developers.com/showthread.php?t=2688891
Edit: Sorry, forgot that we have to determine your bootloader version first. So use the button combination or the adb command to boot into it and post it. Don't worry. I don't think you did anything to the bootloader - it's not that easy to mess it up...

Unfortunately, the adb code doesn't work, with or without the hyphen. The device will reboot, but will return to TWRP.
I've held down the Volume down+power button for more than a minute witout result. The device will just reboot after a while for as long as I'm holding it. I do see the screen flicker for a second.
I've also noticed, that after I push a file to the tablet, that after a reboot it loses the data I just moved.
After booting TWRP, when I look in the command line of TWRP, it tells me that it can't mount the 'system' , 'data' and 'cache' forders. (tw_mount)
And it specifically mentions (multiple times) that the /data folder failed to mount, giving the message "No such file or directory"
It seems I really managed to F'ed it up good...

My "force-boot-to-bootloader" kernel module might help you unbrick. Read this guide very carefully before you do anything:
http://forum.xda-developers.com/transformer-tf700/help/guide-t2853546

You people are my new heroes!
The last guide did the trick. The stock firmware is installed and I'm currently updating and installing all the apps.
Thank you all só much, you really saved me a ton of frustration.

[HELP] CM13+TWRP - Installation error, bootloop, PC doesn't recognize phone via USB

Moto G XT1032
Hello,
I hope that you understand my English. I am kind of a layman concerning Android, but still wanted to install Cyanogenmod 13. I followed these instructions (can't post them apparently since I am new). Official instructions on the CM website. (Bootloader was already unlocked because I already installed Cyanogenmod 12, went back to Stock ROM and now tried to install CM13). Like alwas there were some minor errors during the first steps, but I handled them alright, I think.
The real problem started when I tried to install the zip-file of CM13 ("Installing CyanogenMod from recovery", step 8). I followed the instructions (wipe etc.), but the installation stopped at "Patching system image unconditionally" and it said something like "missing md5-file" although the file I downloaded on the TWRP website was right next to the recovery .img.
After trying and trying I started to go through the options in TWRP recovery (which was a fault, I know) and wiped some things that probably should not have been wiped. Next error message was: "unable to mount /system". New problem.
Then I thought, I might try the recovery that was right next to the downloadlink of the CM13 firmware. Installed it succesfully and tried again some things, now I have a bootloop and can't shut off the phone. When I shut it off, 1 second later the Google-screen with the open lock appears again". The only help was to manually shut it off with recovery.
I can't even start Android anymore, which means I can't activate USB-debugging, the installation files of CM13 are missing and the main problem: my PC only recognizes the phone in fast boot mode - I can't move files to the phone, it just says in the task bar: "Fastboot falcon S".
As soon as I enter recovery mode, the USB-sign on Windows vanishes.
Tried to move the files to the devices by "adb push cm-13.0-20160703-NIGHTLY-falcon.zip /scard", but it says "* daemon not running. starting it now on port 5037 *
* daemon startet successfully *
adb: error: connect failed: no devices/emulators found"
The device is not recognized by "fastboot devices" in cmd.
I hope that you understood everything. Already tried to get help in German forums, but nobody answered there.
And yeah, I definitely stopped trying to solve it by myself because I might just destroy it more.
Thanks for your help!

seems like we are on the same trolley.
I wanted to have a 100% clean system so I wiped everything.
I reinstall SDK, google drivers, motorola drivers, but no success. In fastboot mode it's written: USB connected, on the computer eject "Fastboot falcon S". I create file adb_usb.ini with id in it, restarted system, killed adb and so on. Tried different USB port, different cables.
Aendroit, if you find a way share.
I'm on W10 if that matters.
Ok. So I managed to go through the problem.
First, I was able to reinstall TWRP with fastboot (fastboot root twrp.....), so fastboot worked for me. Then it seems that on the main screen, where you choose options with volume buttons, fastboot works, but not adb.
I went into recovery and "adb shell" worked, so did "adb devices".
I used push command and so on.

I'm glad you got the solution now. Unfortunately I can't follow the instructions. Could you please take me through it step by step ("fastboot root twrp", I never used a command like this before). Thanks!
Because when I go in recovery and type in "adb shell" or "adb shell" on my computer, it says "no devices/emulators found".
Update: Got it. I can enter TWRP now, but in the installation log it said "Mismatched partition size (recovery)" at the end. If someone knows what that means ...

I meant: fastboot flash recovery twrp-3.0.0.0_2-falcon.img
Mismatched size is just an information, nothing to worry about. Now, when you are in TWRP try to check the device "adb devices", should work.

Thank you, my computer recognizes the device again! I was able to copy the files to my phone. Unfortunately I still can't install a custom rom. I tried Mokee instead of CM13 now and i always get the same messages:
"Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Target: 146758281
Detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and so on.
I don't know what that is supposed to mean ...

Well, I'm not very good oriented in all this stuff, so I don't know why you got those problems, far from being a dev.
I copied ressurection ROM + open gapps nano (thou I always used banks, but this time wanted to save more free space) and installed it via TWRP without any issues.

Thank you for the answer. Mokee works now! I'm not happy that I can't use CM13, but I got Mokee working after a while and I'm glad about it.

Alps x6_v5_x50 phone bricked

I uninstalled magisk root and my phone is not booting and just run into loop on start up. I have a backup on my system but the phone is not reading sdcard as well and I've been trying to send the backup to the phone through adb sideload, all I get is error message. Please help me, I just got the phone.
The phone is China smartphone known as X50 Plus

adb sideload only accepts a properly signed Stock ROM - what always is housed in a ZIP-file.

jwoegerbauer said:
adb sideload only accepts a properly signed Stock ROM - what always is housed in a ZIP-file.
Click to expand...
Click to collapse
Thanks so much, I really appreciate your response. I read your thread, my question is that:
Will my device be connected to the system while I run the command scripts?

Also the fastboot in stock recovery mode is not running!
Can anyone help with this

harbbyhordun said:
Also the fastboot in stock recovery mode is not running!
Can anyone help with this
Click to expand...
Click to collapse
Fastboot deals with device's bootloader, hence to work device must got booted into its bootloader
ADB deals with Android's filesystem, so to work USB debugging must got enabled on device
If you boot device into Recovery then an app gets started what offers you a menu where you can select specific actions from to get applied to the device in hope some common problems get fixed or that device's Stock ROM should get re-installed.

Question ADB Sideload not finishing

Hey,
I installed GrapheneOS but want to return to stock rom.
Flash site doesn't work.
When in bootloader mode my phone is not detected. I know the drivers solution but Device Manager isn't even showing ANY device when in bootloader mode so I can't even change the drivers.
In recovery mode the phone IS detected but when sideloading the OTA file it stops at 47% (1xfer) and aborts the installation.
Flashboot doesn't work either, I get an error when trying to flash the bootloader img.
Flash-all doesn't work either, always fails at writing bootloader.
Android flash tool same problem, when the phone goes to bootloader mode Windows doesn't see the device anymore. No device to be found in device manager...
Anyone any idea. Really stuck now :s

Found the culprit... it was the cable... unbelievable :s

StarrOw said:
Hey,
I installed GrapheneOS but want to return to stock rom.
Flash site doesn't work.
When in bootloader mode my phone is not detected. I know the drivers solution but Device Manager isn't even showing ANY device when in bootloader mode so I can't even change the drivers.
In recovery mode the phone IS detected but when sideloading the OTA file it stops at 47% (1xfer) and aborts the installation.
Flashboot doesn't work either, I get an error when trying to flash the bootloader img.
Flash-all doesn't work either, always fails at writing bootloader.
Android flash tool same problem, when the phone goes to bootloader mode Windows doesn't see the device anymore. No device to be found in device manager...
Anyone any idea. Really stuck now :s
Click to expand...
Click to collapse
Sideload stopping at 47% is actually "normal". FYI.

JohnTheFarm3r said:
Sideload stopping at 47% is actually "normal". FYI.
Click to expand...
Click to collapse
Not when the next part is: installation aborted. It is normal when it is not a Google image.

StarrOw said:
Not when the next part is: installation aborted. It is normal when it is not a Google image.
Click to expand...
Click to collapse
Aborted installation happens quite often due to various reasons, it's very picky. NOT saying that aborted installations are normal, just saying sideload ending at 47% is "normal".

If you see log "xfer 1.0 successfull" after sideloading, everything is okey. If you don't see, i recommend you to use TWRP without "signature verification". Set this option off and try again.