Hi,
So I just ported miui stock based rom (marshmallow .305 build miui v8) but well it doesn't boot up and unless I get my hands on adb I can't do anything
Things were easy back in my days I would've just enable adb in build.prop or kernel and everything worked at boot but right now I just get Device Offline which well I have no idea about.
So far what I know is that adb activates only when lockscreen has been shown and your PC authorized to use it ... But since I can't access adb now is there anyway I can access adb from the start of booting process?
Any advice would be so much appreciated
Thanks in advance
PS: I just remembered a thing that I could get RSA from my computer's adb data folder and put it in my phone's /data/misc/adb/adb_key? or such thing
EDIT: My question is how to get adb from start of booting procedure ... And I can't because the rom have not yet boot up and before it reach lockscreen I can't seem to get adb working!
Have you tried to use fastboot mode to access the device?
what do you mean "i doesn't boot up" ?
is your device bricked? how did you install minui ?
please explain!
if its bricked then
hold volume up + power key for 15 seconds, the device will JERK 3 times..... on second jerk IMMEDIATELY release ALL buttons, the device will shut down!
now connect cable in fastboot or flashmode to FLASH proper rom in order for device to bootup
he wants to debug kernel to fix problems and boot-up phone, i guess..
you can try before phone boot-up..
give this command and you will see <waiting for device> connect usb and boot-up
adb -d logcat>c:\kernel_logcat.txt
or you can use kgdb..
fastboot mode doesn't let me access to logs :| I want to get some log to understand what is the problem of not booting ...
Thanks ...
I've edited my post to clarify my question is not about how to get my device back to life :| it was a matter of how to use adb to get log before rom boot correctly ...
Actually I want to debug the rom (as the kernel is stock base and probably have no problem) but your guess is somewhat right ... however my problem is that the rom doesn't boot up so I need to use adb and get log before rom boots up :|
Related
hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!
I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk
Did you try a fastboot command like fastboot devices?
Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.
Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz
Hi guys,
i have a tricky problem.
I bought a used nexus S, without any hope to recover it.
This is the state at the moment (after installed SDK and drivers).
I think the device is in his standard state (all locked up, never rooted, stock rom)
It boot up and ask for a password to encrypt device (works : volume and emergency call).
If i connect usb, he tries to mount USB storage but he dosen't success.
I connect to pc and pc see an Android ADB device in the devices list.
BUT if i lauch 'adb devices' i dont see anything.
I start it in bootloader mode (Vol Up + Power) ... it starts.
BUT Vol Up and Vol down didn't work. I can only press power and return again in bootloader. (volume work if i normally boot)
In bootloader state i tried 'fastboot devices' and i didn't see any device.
So the state is :
Bootloader i think "broken" (volumes dosen't work and fastboot dosen't see device)
Debug usb disabled (adb don't see my device)
Device encrypted
Any idea ?
I think is a nice problem to let your brain works on :laugh::laugh:
Thanks in advice.
Daniele
Hey guys, there is anybody out there ?
I dont think that no one could try to solve this problem.
Thanks
Do you have the drivers installed onto your PC? You will need to get the adb drivers and fastboot drivers. Download Samsung Kies and that will take care of your ADB drivers. Click here: http://www.mediafire.com/download/5a7gou9droidi53/drivers.rar for your fastboot drivers. Hope this helps.
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
sirhaplo said:
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
Click to expand...
Click to collapse
I'd suggest just booting Linux and doing whatever you need to do in there.
The kernel already supports communicating with the Nexus S, no need to mess with drivers like on Windows.
I was trying things on my Lenovo A7-10F and ended up rebooting in fastboot mode. Pressing power doesn't do anything (even for a whole minute..); with other buttons : nothing either. Non removable battery of course, and adb won't detect the device (tried to install different drivers).. What can i do? It's heating quite a lot..
In order to replicate how it is when the battery is taken out just allow it to drain completely. That might help with the reset of it. Hope you get more help here!
Yes that's the last thing I'd like to do though since it's heating a lot and it can last for +10 hours..
did it work by just letting the battery out?
Download, extract and install this Lenovo driver to your PC
Code:
lenovo-forums.ru/index.php?app=core&module=attach§ion=attach&attach_id=39195
Download and install Minimal ADB and Fastboot (search it on xda or google).
Run it.
Connect your device to PC using USB cable.
On the command prompt type: fastboot devices
It will verify your device. If fastboot is configured properly, your device code will appear.
Then you just have to type: fastboot reboot
and your device will reboot to system
Hope it works. Good luck
Hi guys,
I am looking for some advice.
I have a G6 L11.
I cant boot the phone after trying to install a standard rom.
I cant get access to recovery (installed the TWRP) ,
I can only get it into fastboot and resque mode, the bootleader is unlocked and the phase " phone unlocked " is shown is red.
I tried using the cmd with adb and fastboot commands ,
Also tried using the G6 knife toolbox but when I can get anything to work, i get the idea the device isnt recognized.
I could use the G6 knife toolbox before so the drivers are in place, I can however reboot out of fastboot using the G6 Knife toolbox but then the phone start booting and shuts down in the middle of the boot process,
The only way I can get it into fastboot is when I disconnects the battery , if the device failed to start up by shutting off inside the boot process, then one cannot get in into fastboot unless I disconnect the battery and connect it again on the hardware inside the phone,
So each time I want toenter fastboot, i normally have to disconect and connect the battery,
Please help,
Hi Guys,
Is there anyone who can help?
Is it a hardware or a software issue?
What do I do? Throw away the phone?
Standard ROM, what ROM?
Hi, I need your help here. I'm trying to fix my friends phone for her. What she told me is that it got stuck at the second boot screen after an update. She also said that it happened before and her father got it working. So my first thought was to clean flash stock firmware but I can't get ADB working. I've installed usb drivers and minimal ADB and fastboot but it doesn't recognize the phone in "adb devices" (I have no idea if USB debugging was on in dev options but I'm assuming it wasn't). I have no idea what to do now as I'm not that familiar with Xiaomi firmware.
Thanks in advance.
Edit: Xiaomiflash sees the device but not as COM.. but 72e728fb (?) and trying to flash it in this state ends with error:Flash xbl error