Related
Ight so yesterday I got ADB setup and I was able to change my Splash Screen and now I feel special. But no I really want to setup Emulator becuase it looks really cool to use. But I also have a few questions,
1) Do we have to root the Emulator or is it already rooted orr like, whatsup?
2) Is Emulator just like a regular Android phone where we can Flash Recovery Images and ROMs and Themes and stuff?
Below, I have uploaded a few pictures of the Screens I get when I try to use it. BTW, I don't have the thingys (the uhmm like 2.1 n other FirmWares on my SDK setup becase they wouldn't download and when I tried to download it, it wouldn't work.)
I'm on Windows Vista and I'm running VegaMans Legend Port. Also, my phone doesn't get discovered my ADB. When I trype in
Code:
ADB Shell
I get;
Code:
Error: No device found
I'm guessing it's the ROM becuase I was able to be discovered on FastTest and that's how I was able to change my Splash1. Also, I Tether with my phone soo...
Mod please delete.
can you help me fix this problem
after wipe all data, cache and anotherthing wipe (it's name very hard to remember ).
I cant use recovery mode, my phone can open fastboot and bootloader, but can't open recovery mode (it's only show a android logo when i press "recovery")
please help me (
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
justflikwalk said:
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
Click to expand...
Click to collapse
can you show me more, i dont know adb commands, and push new recovery is "recovery clockwork" and "recovery RA". I tried apply them, but it's not work,may be i wrong in some thing, it's the first time i use android phone . throught usb, i have "fastboot usb"
please help me
http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide
but my phone cant connect with PC, atlthough i installed google usb driver.
i might be wrong but cant you just flash a original ruu, than root and reinstall recovery
#1)Go and download yourself a recovery.img file that is compatible with your device and put the image on the root of your SD card (that means on the main directory and not in a folder)
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
#3)Open up your terminal and type in
Code:
su
to gain root access. If you are root the next line should show the
Code:
# symbol
#4)At the next line type in
Code:
flash_image recovery /sdcard/name-of-recovery.img
you will need to replace the code that says name-of-recovery.img with the exact name of the file on your SD card.
#5)Hit enter, wait a few seconds and viola ! you have a recovery again.
Good luck man.
hxq88 said:
but my phone cant connect with PC, atlthough i installed google usb driver.
Click to expand...
Click to collapse
Try the driver from this thread.
It helped me set up my ADB for the N1
http://forum.xda-developers.com/showthread.php?t=613217
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
hxq88 said:
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
Click to expand...
Click to collapse
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
baseballfanz said:
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
Click to expand...
Click to collapse
i typed ADB devices on command prompt, it'show
View attachment 763802
and it's my driver after update from your link
View attachment 763803
what is passimg method, is the way rename room.zip => PASSIMG.zip
You did have debugging turn on correct?
Not sure what else to suggest except the passimg method, worth a shot.
Sent from my Transformer TF101 using Tapatalk
And... if you try to install a stock rom? When starts the HBOOT automatically detect the rom and ask to install. One time you've installed the rom, root & install recovery
I think that work because, It happens to me 1 week ago.
I have Imilika's AOSP ICS ROM V6,
I changed the buid.prop
ro.sf.lcd_density=213
for tablet mode. after I reboot, my GNote is not booting. I cannot go to recovery mode or download mode.
Please help. I don't know what to do
Got it
OK, I was really sad about what happens to my phone, but finally I managed to fix it .
As I told you, my phone was not booting to recovery or download modes (key combinations not worked). finally I try to connect to PC via USB and luckily my PC could detect my phone . So i realized that the problem is the display not coming but phone is halfway booted.
So, I tried to change my build.prop via adb but failed due to cannot grant root permission (becoz display is off).
Finally I issue a adb commad to reboot in recovery mode.
"adb reboot recovery"
yeah, that command directly take me to the CWM recovery. then I flash AOSP v6 again.
Now, my phone is working again.
P.S. I just note this down for others if they get same problem future !
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
If you don't know what ADB is, you probably shouldn't be flashing so regularly. Anyway, ADB stands for "Android Debug Bridge" and it is a protocol for device control, development, and debugging.
Sent from my GT-N7000 using Tapatalk
priyanv said:
I have question.. I don't understand the term adb. What that actually and why need that? I did so many flashing so far and I didn't use this adb yet!
Click to expand...
Click to collapse
adb is a connection type. we can run shell commands (in the phone), file transfer via adb by using our PC. for that we should have to enable usb debug mode in our mobile.
Actually you might used adb, when you root your phone in the first place . If you have CF-Root zip file, just extract it. you will see a folder called "files", in there you can see adb.exe .
If you need test run,
connect phone via USB(make sure you've enabled USB debug), open command prompt, navigate to that "files" directory.
run "adb shell ls" (to run "ls" command in phone)
run "adb push <anyfile in the PC> /system/sdcard/" (copy files from PC to sdcard)
like that
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
priyanv said:
OK now I got it.. But why do we need to push some file like this when we are able to transfer files like mass storage??? Or what else can be done??? Sorry for the basic questions..
Click to expand...
Click to collapse
Its functionality is not only to copy files from pc to mobile and vice versa.You can use it to get logs due to bad flashing,zip align apps,reboot into recovery,DL mode,normal reboot etc...
MY ADB has stopped Working
It happened after Installing the CWM And TWCR
Well What happened it was saying ADB was outdated while installing but it installed CWM and TWCR
Now if i enable ADB in the phone the windows doesnt read that there is a mobile nor anything detected not even charging
When i disable ADB I can see my phone charging and i can transfer files
I don't know what to do and I am very worried ...
Hope If any1 could help...
Tried installing ADB drivers and the Android SDK .. No luck
I think the problem is in the phone as it doesnt allow me to connect to the PC with ADB on
I read this http://forum.xda-developers.com/showthread.php?t=1917741
and found that ro.debuggable=0 in the Deafult.prob While it is enabled ...
And there is a question too how can i backup it so if i eddit it and get a bootloop I want to be able to restore using CWM or TWCR
John98Zakaria said:
MY ADB has stopped Working
It happened after Installing the CWM And TWCR
Well What happened it was saying ADB was outdated while installing but it installed CWM and TWCR
Now if i enable ADB in the phone the windows doesnt read that there is a mobile nor anything detected not even charging
When i disable ADB I can see my phone charging and i can transfer files
I don't know what to do and I am very worried ...
Hope If any1 could help...
Tried installing ADB drivers and the Android SDK .. No luck
I think the problem is in the phone as it doesnt allow me to connect to the PC with ADB on
I read this http://forum.xda-developers.com/showthread.php?t=1917741
and found that ro.debuggable=0 in the Deafult.prob While it is enabled ...
And there is a question too how can i backup it so if i eddit it and get a bootloop I want to be able to restore using CWM or TWCR
Click to expand...
Click to collapse
Can you use adb over other computers?
Also, try ADB over network. Goto Settings > Developer Options and turn "ADB over network" on. If prompted with a warning, press OK. Then you will see an ip address with a port number under ADB over Network setting. Now open cmd (or Terminal in Linux) and cd to the directory where the ADB files are present. Then type
Code:
adb connect <ipaddress>
Of course, replace <ipaddress> with the ip that you see in the Developer Options under ADB over network. It should be something like "192.168.1.2:5555", enter the whole thing. Then see if you are successfully connected by typing
Code:
adb devices
.
If you are using windows go to control panel and look for "hardware" or more specifically "drivers". It is somewhere there, just look around and you will find it. Then enable adb and connect phone. Then Select your device name from the list and right-click and select appt. drivers.
ayushag96 said:
Can you use adb over other computers?
Also, try ADB over network. Goto Settings > Developer Options and turn "ADB over network" on. If prompted with a warning, press OK. Then you will see an ip address with a port number under ADB over Network setting. Now open cmd (or Terminal in Linux) and cd to the directory where the ADB files are present. Then type
Code:
adb connect <ipaddress>
Of course, replace <ipaddress> with the ip that you see in the Developer Options under ADB over network. It should be something like "192.168.1.2:5555", enter the whole thing. Then see if you are successfully connected by typing
Code:
adb devices
.
If you are using windows go to control panel and look for "hardware" or more specifically "drivers". It is somewhere there, just look around and you will find it. Then enable adb and connect phone. Then Select your device name from the list and right-click and select appt. drivers.
Click to expand...
Click to collapse
Thanks for the reply I can't use ADB anywere ..
The phone doesn't even appear in the PC with ADB debuging enabled not even a connected sound or anything ..
I tried Wifi Kontect on the playstore as I didnt find "ADB over Network" But ADB wont connect....
Any Other solutions ... I dont mind if i have ADB over wifi the important thing is to have any ADB connection
www .mediafire .com/convkey/fb15/db3ykaaldgkqsd66g.jpg?size_id=5
www .mediafire .com/convkey/93e0/49f47ps6s9nbeyj6g.jpg
Remove spaces so you can see the images I cant post links yet
Fixed
I have fixed my probem thanks to @sijav !
Installing
http://forum.xda-developers.com/showthread.php?t=1687590
Fixed everything ! even after un-installing the app
This guide will be about deleting a magisk module that caused your phone to bootloop. Definetly works with Xiaomi Redmi Note 10 5G, let me know if it works on Poco M3 Pro as well.
Prerequisites:
- rooted phone with magisk installed
- usb data cable
First you have to boot into safe mode which will disable the loading of all magisk modules:
- Turn off the smartphone completely.
- Turn it on normally and when the MIUI logo appears, press and hold the volume down button until the system boots completely, and you see the lock screen, it should also display "safe mode" in the bottom left corner.
Next enable USB debugging on your phone and connect it to a pc, then run
adb devices
If your devices is recognized and authenticated it will output:
List of devices attached
**************** device
where ************* is your device ID. If it writes 'unauthorized' then accept the prompt for authorization on your phone.
Now open an ADB shell from your pc:
adb shell
su
cd /data/adb/modules
ls
This will list all your installed magisk modules. Remove the problematic one with:
rm -r problematic_module
Done, reboot normally!
------------------------- If su command freezes the command line------------------------------
If somehow this does not work, for example you have not granted shell superuser rights before, then you have the following backup options:
run:
adb wait-for-device shell magisk --remove-modules
This should remove all installed modules, and reboot the phone. If it does not work from safe mode, you can try it during the boot animation. (After MIUI logo comes up adb gets enabled (check with 'adb devices' command, if adb is running))
If so far nothing worked you still have a third option to recover you phone/data:
--------------------- Nothing working ---------------------------
You can flash the stock boot.img from your currently installed stock ROM and it should boot your phone without magisk (but also no root). This will enable you to back up your phone/data, but if you want magisk again, you probably have reflash your ROM from fastboot again. This is because with no root access, and magisk not present in your boot image there is no way to remove the module that is causing the bootloop.
Feel free to comment, share your suggestions, and correct me on anything if I am wrong.
Gorg2331 said:
This guide will be about deleting a magisk module that caused your phone to bootloop. Definetly works with Xiaomi Redmi Note 10 5G, let me know if it works on Poco M3 Pro as well.
Prerequisites:
- usb debugging already enabled and authenticated (preferrably)
- rooted phone with magisk installed
- usb data cable
all you have to do is connect your phone to your PC and when it shows the MIUI logo during normal boot run
adb devices
If your devices is recognized and authenticated it will output:
List of devices attached
**************** device
where ************* is your device ID. If it writes unauthorized then skip to the "Other Method" section below. If you get back nothing try to run it a couple times during boot. I am not sure when adb gets enabled during the boot but should be around the MIUI logo appearing.
next write:
adb wait-for-device shell magisk --remove-modules
This will delete all magisk modules from your phone, and it reboot it automatically. It should boot up just fine, and all your magisk modules will be deleted.
---------------- Other method --------------------------
If you really need access to the phone, but do not have adb enabled:
You can flash the stock boot.img from your currently installed stock ROM and it should boot your phone without magisk (but also no root). This will enable you to back up your phone/data, but if you want magisk again, you probably have reflash your ROM from fastboot again. This is because with no root access, and magisk not present in your boot image there is no way to remove the module that is causing the bootloop.
Feel free to comment, share your suggestions, and correct me on anything if I am wrong.
Click to expand...
Click to collapse
just a thought on the above;
i haven't followed this topic anymore since the built-in functionality where modules are disabled if phone is in safe mode so i just thought to post it as a way to remind people that ( i think) most phones have a safe mode and with that , it might get you out of the bootloop.
I guess the above option is a great way too, but i think the use of safe mode makes it a lot easier.
pjottrr said:
just a thought on the above;
i haven't followed this topic anymore since the built-in functionality where modules are disabled if phone is in safe mode so i just thought to post it as a way to remind people that ( i think) most phones have a safe mode and with that , it might get you out of the bootloop.
I guess the above option is a great way too, but i think the use of safe mode makes it a lot easier.
Click to expand...
Click to collapse
That is a great suggestion, tho you cannot use any root applications since they will not be loaded. (Even if you install them during safe mode) But it should help sidestep the adb not authorized issue possibly! I incorporated safe mode in the post.
I used safemode purely to get rid of the troublesome modules( since you still have root access) . Then reboot the phone normal, and all should be fine/ you should be out of the bootloop
And i know the safemode is a bit off topic compared to what you are writing about, but it might help getting back into the phone
pjottrr said:
I used safemode purely to get rid of the troublesome modules( since you still have root access) . Then reboot the phone normal, and all should be fine/ you should be out of the bootloop
And i know the safemode is a bit off topic compared to what you are writing about, but it might help getting back into the phone
Click to expand...
Click to collapse
Oh you are totally right! You can use safe mode to remove the problematic modules with rm -r. But I think this only works if you have previously granted shell superuser rights. (Since in safe mode you will not get prompts to give SU rights)
I confirm, your guide Is correct. Now i have installed a modules called magisk bootloop saver. Works fine. Do the same thing without digit the adb command.
i'd also suggest in case of BOOTLOOP (cause of bad magisk module)
you can still fastboot
Code:
fastboot flash boot boot.img
the ORIGINAL boot.img of your actual ROM ( so everytime you root keep a copy of the original BOOT.IMG)
in that case you'll be able to reboot your phone ( without root ) and without losing any data !
yes, all these suggestions are good and 100% work! great thread
Booting into Safemode, adb shell and deleting the bad module worked great, thank you!