Database Develop

Please Help- FRF91 unable to root with Superboot! Bricked?

I'm having serious issues with my N1 since receiving it back from HTC for a repair. I had rooted the phone before it was repaired for a crack in the glass, but the repair center had re-locked the bootloader. I followed steps the way I had done before to root my phone and succeeded in re-unlocking bootloader but when I did superboot (using mac terminal) did not come to screen where root permissions were offered... booted phone, no wifi signal, did not recognize sd, very glitchy, unstable and maybe worst of all unable to mount to computer. So I don't know if anyone with this small amount of information would have any clue as to what I can do. Oh yes and when I had gotten my phone back from repair center I had done update to FRF91.. so I know I'm an idiot for trying to use superboot when there isn't one for the FRF91. There you go gentlemen. If someone is willing to help I can provide any other information required.

As long as you can get to your recovery screen, you're not bricked. Most important, are you running a custom recovery like Amon_RA's?
Edit: If you have a stock recovery and want the superuser/unsecured boot use the updates from here
-If you have a custom recover just flash a ROM that includes superuser/unsecured boot
*Always do a Nandroid

I didn't have it before I unlocked my bootloader, and I can't seem to install it considering that every post says you put it on the sd.. and as I said I cant even mount my phone So apparently I'm on stock..

Micro SD adapter?
That does make things interesting, the only thing i can think of is getting a Micro-sd adapter and putting the update on the sd, then place the sd back in your phone and flash.

Thread moved to Q&A.

Can't you adb push the file while in the recovery menu?

I can't flash if I can't mount my sd card right? So that would make the ROM with superuser useless.. Can you think of a way I can get Amon_Ra recovery through bootloader?

I can't flash if I can't mount my sd card right? So that would make the ROM with superuser useless.. Can you think of a way I can get Amon_Ra recovery through bootloader?

I've heard about this but I'm a total n00b, don't know how to..

I was referring to the adb push.. any help with this would be GREATLY appreciated!

ADB method
If you still have the adb ability try fastboot flashing...just follow the steps here

Emul8tor I really appreciate the continuing advice- home from work now.. I can't seem to get adb if i have done everything correctly working on terminal mac os.. have android sdk and i should be running it under sdk/tools dir correct? i type in adb or adb devices and I get adb: command not found..suggestions?

Have you used the adb method before, kinda sounds like you haven't set the PATH for your environment. I don't have any clue about the set-up for Mac, but theres a tutorial here

okay going to read through this again especially part on creating the PATH.. back soon

really don't know what to think I have no idea how to create a .bash profile and I'm not so sure this is why adb isn't working. Thoughts?

and I didn't use the adb method before.. only fastboot

found this by googling, adding tools to your path lets you run Android Debug Bridge (adb) and the other command line tools without needing to supply the full path to the tools directory when typing commands in Terminal

Dude this guy's having the same problem as me, I guarantee you he used the wrong version superboot with FRF91 http://androidforums.com/all-things-root-nexus/127689-please-help.html
I'll bet he can't mount sd card either

Alright I ran adb command but it isn't registering the phone after list of devices attatched. But it did issue a string of commands after so I assume it is working... Now i guess I can say that I am truly scared because my adb doesn't even recognize the device.

Just a hunch...is debugging enabled on your device?

adb error device not found

I tried everything, downloaded new adb , new cable, I tried win 8 and win 7 but nothing usb drivers and adb drivers are installed correctly , in device manager I see my usb driver (not yellow one)
When ever I put adb devices I can see my device and if I put adb shell it works but if I try adb push it says error device not found
I used to have sony xperia s, every thing used to work normally on it like fastboot and adb commands
Please help me it is so weird

Locked bootloader?

GROGG88 said:
Locked bootloader?
Click to expand...
Click to collapse
yes

i rooted my phone by flashing older kernel and rooting then upgrade to the newer kernel , nothing happened while i was flashing all went right , no errors , but the problem at adb is still there , can't push any file , also flash tool sends a file to a rooted phone called : ftkit the first time u connect your phone with root , it didn't push the file to the phone ,
very weird problem

elias234 said:
i rooted my phone by flashing older kernel and rooting then upgrade to the newer kernel , nothing happened while i was flashing all went right , no errors , but the problem at adb is still there , can't push any file , also flash tool sends a file to a rooted phone called : ftkit the first time u connect your phone with root , it didn't push the file to the phone ,
very weird problem
Click to expand...
Click to collapse
Have you granted superuser access to adb?

GROGG88 said:
Have you granted superuser access to adb?
Click to expand...
Click to collapse
yes i granted superuser access to adb
i want to ask a question .
when i need to push files to my phone i directly enter the commend " adb push "
ot first i need to enter adb shell ?

Push is not used within shell. Shell is basically used to start a terminal emulator. Push/pull is used within cmd or terminal to treat your device as a remote location.
Sent from my C6603 using XDA Premium 4 mobile app

[Q] Remove Screen Lock

Hey everyone,
One of my co-workers was messing with my phone and added a screen lock, trying to be funny. The stupid part is he forgot what he made the PIN. Anyhow, I am 8 of 10 attempts before my phone alleges to nuke itself. I am using an unlocked Moto X, running TWRP. It seems like I should be able to log into TWRP and fix it. So, I supposed this is a two part question:
Is there a way to login via TWRP and disable the screen lock? Is there an APK in the system that I can rename then reboot?
Would it even wipe my phone. My gut feeling is that the Android OS couldn't invoke the reset due to TWRP. My guess is that it would simply reboot into recovery. Thoughts?
Thanks!

Alright, found my own solution. Ill post here in case anyone else has the same issue.
Reboot into TWRP
Select to mount system
Issue the following commands:
adb shell
rm data/system/*.key
Reboot and it should be gone!
Thanks!

can anyone offer me some help

Background
Okay so the glass on my 2013 Moto X broke on September 27th I ordered a new one and while changing it I accidentally broke the digitizer so I disconnected the digitizer and the phone turned on while my digitizer with disconnected then i had no way of turning it off while my digitizer was disconnected the phone started to vibrate every 3 seconds until the battery died... so I was forced to switch over to my Nexus 6 because at the time that was my backup phone because I love the performance of my Moto X.. now a few months later yesterday to be exact my new digitizer arrived and I brought my Moto X back to life powers on and performs just fine
Problem
My wrist twitch to activate camera doesn't work
My dual chop to activate led doesn't work
Whenever I make a phone call or receive a phone call my screen turns off automatically but the phone call works just fine once the phone call has ended my screen does not turn back on I have to reboot the phone to turn on the display again
Phone info
2013 moto x on 5.1.1 stock rom locked bootloader rooted using crashes method with ultra slim root
any help or tip is greatly appreciated

Maybe, but it really depends what's actually wrong. The Moto has a TI MSP430 chip that handles all that 'motion, wave-to-wake, chop-chop' stuff and it's loaded from a /firmware folder or partition (have forgotten at this point). @masterifla figured out which files it was on 4.4.4 & 5.1 that got uploaded to the 430 and wrote a .zip file to change from 4.4.4's "wave to wake" to 5.1 "chop chop" or vice versa. I fixed some little bug in it, and stuck the working .zips up in this post although they may be elsewhere as well: (so :: these zips contain the firmware that actually does the wave-to-wake stuff and can be 'recovery-flashed')
http://forum.xda-developers.com/showpost.php?p=63616790&postcount=17
At least if that works, you'll know that it was the firmware for that chip, and if not, it might actually be the 430 chip(which you can see in the teardown). The post by me and anything by masterifla should be pretty well explained.
Cheers.

but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this

BADDINOROX99 said:
but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this
Click to expand...
Click to collapse
There still might be a way. I keep trying to have people get this to work, but I'm not sure of the outcome yet, so give it try if you like: Here's some steps:
1) Locked bootloader / no root means mostly that you can't write system, but I'm pretty sure you should be able to temporarily boot into a PC-based copy of twrp. Once in twrp (for one time say) you are root, and you have access to anything on your gizmo. In theory, you should be able to mount system read-write and change something in the file system.
2) Get the correct copy of twrp and adb (from dev forum for this box) and put it on a PC with fastboot in the same folder. To make this easy, called twrp "twrp.img" and call "fastboot" or "mfastboot" fastboot.exe (I am for some reason assuming you've got a PC, not a mac or linux, but the ideas are similar.
3) quick explain of the files in the .zip from above ^^ : 8 files prefixed by MSP that are located when on the moto in /system/etc/firmware. Unzip them and stick them in that same folder.
4) Tricky part : (I think) : reboot into the twrp.img on your PC by getting your device into fastboot / bootloader mode: (so .. volume-up&down&power keys all held down for ~10 seconds perhaps, then if you've gotten it right (it's touchy), you'll be in the bootloader where it has a small tiny text list of stuff like "continue, recovery, etc).
5) you're good with the phone if you've made it here: now on the PC from that folder, type in "fastboot boot twrp.img" and good luck. If it works, your phone will be in TWRP with root access. If not, I don't know another option at the moment.
6) Probably the rest is most easily done from the PC command (or shell) window where the files are. Since your device is in the bootloader and awaiting further instruction, you should be able to use adb to talk to recovery now. so carry on:
7) (get the files from your PC (the MSP prefixed ones) onto the device, so first remount system r/w):
Code:
a) "adb remount" // supposedly should remount system toggling the read attribute to write
b) "adb push msp* /system/etc/firmware/" // copies files to device unless I've got syntax wrong, try one at a time if doesn't work.
c) "adb shell ls -al /system/etc/firmware/" // list all files, and post them back here to see if it even worked.
d) "adb remount" // system partition back to normal ro state.
d) "adb reboot" // moment of truth, a reboot.
8) after things settle post-reboot, check out "wave-to-wake" , camera twist, etc. This works on 4.4.4 or 5.1 (if this other stuff above works).
Note: I could be way off on my idea that rebooting into recovery will give you enough functionality to do this, but I'm not sure what other choices you've got without being able to root. I guess another thing I'm wondering about is why you wouldn't be able to root the phone from recovery regardless of how you booted into it. You still can't unlock bootloader, but I'm not clear on what difference it makes at the moment.
Good luck. It's a "hail mary" pass.

thanks I got my stuff working again ? I screwed up in the file install part freaked out and reflashed stock and rerooted so everything is good now once again thanks

Sort of a bootloop after Android 11 update

Hello guys,
I hope someone can help me with this problem...
So the thing is - yesterday I finally got OneUI 3 and Android 11 update (yay?). But ofcourse as soon as the phone rebooted and optimised all the apps and came back to main screen it rebooted after a minute or so...everytime. As soon as I enter my pin and unlock the phone it reboots after a short period.
The same problem happened when I de-bloated the phone a while ago via ADB - but I then enabled back all the apps except facebook and some "safe to debloat apps" which were not even system apps and it has since worked for almost a year. But here we go again....
I even "re enabled/installed" all the apps I could list in ADB ( so basically all the apps on the phone) and then went to wipe cache - but still no go.
I am also wondering if there is a posibility to somehow mount storage just to copy some files to my computer (which are important, and my latest backup is around a month old) and then I'll gladly do a a factory reset - no problem.
Any help would be appreciated, thanks!

If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".

TacoDeMuerte said:
If you're able to use ADB to enable/install apps, then you should be able to use "adb pull path/to/files" to copy the files to your computer. You could reboot into recovery mode and see if your computer pulls up the storage that way too. Also, if you have TWRP, you can use the file system to copy files to an external SD card. So you have a few options to get your files.
You can also create a back-up of specific apps (and their data) using "adb backup -f MyBackUpName.ab com.corp.AppName".
Click to expand...
Click to collapse
Hello, thanks for the reply and helping out.
But all the commands and stuff is kinda useless because the phone reboots sooner than in 30 seconds after getting to the main screen. When I boot to recovery the storage doesn't get mounted.......
And I would've had TWRP but the phone is still under warranty so that's a shame, because on my backup phone I have it (and so did on all the previous ones) and it would be great. But IIRC if I install TWRP now, the phone needs to be wiped.
FFS samsung, what is this....because I now read a couple threads and posts on social media people having exactly same problem, and some didn't do anything with ADB prior to update. shame...