Hi,
I do have a Ace 2 (I8160) but I can't get the mobile on the Wifi and he keeps saying: trying to get the IP-adress
Does somebody know how to solve this problem?
Try to connect to another wifi. If the wifi you're trying is yours, go to the router's settings & remove wireless security, then try again.
For the moment \I'm in another house and again I can't get acces to the Wifi and there is also a Wifi signal that isn't protected and there I have the same problem .......... trying to get the IP-adress
You running stock or custom ROM? Have you flashed anything recently? Did the wifi ever work before?
I do have stock and yesterday I rooted the phone and I "think: it has something to do with that ?!
Is it an option to install the stock back there this is a new phone so I do have another phone for the moment.
Simply having root permissions shouldn't affect your ability to connect to wifi. Have you installed a custom recovery? If yes, try clearing cache & dalvik cache.
No I didn't.
Is it possible to install now or doesn't it make that any sence ..... I don't think so
Pfffff, how can we solve this ??
Some ideas:
Unroot, see if it reverts your problem
Flash a custom recovery, if one is available (I suggest Android Flash Recovery to flash it)
If you have a data connection, install ROM Manager & flash custom recovery that way
post-mortem said:
Some ideas:
Unroot, see if it reverts your problem
Flash a custom recovery, if one is available (I suggest Android Flash Recovery to flash it)
If you have a data connection, install ROM Manager & flash custom recovery that way
Click to expand...
Click to collapse
I'm from Holland and my English is not soooooo good
Do you mean that I can install the original software from this phone with the ROM Manager ( http://www.samfirmware.com/ ) ?
And as far I know it's not possible to unroot this phone ??!!
The ROM Manager app has an option to download & install CWM recovery, if your phone is in their database. sammobile/samfirmware will let you download the stock software for your phone, and you need to plug your phone to a computer to flash it. It will return your phone to stock, and you will lose all data.
I thought it was easyer with the second option:
Flash a custom recovery, if one is available (I suggest Android Flash Recovery to flash it) but I thin it works the same?
If ROM Manager has a custom recovery in their database, then that's easier & less steps, but I avoid ROM Manager because it bricked my phone. If you download a custom recovery .img file which you know is compatible with your exact model #, then Android Flash Recovery is probably safer. Android Flash Recovery requires the use of a computer, and a Windows one, at that. However, you can flash any custom recovery (i.e., AmonRa, TWRM), and not just CWM.
What is the bootloader / fastboot mode ??
Is that the CWM .... but I'm wondering if this is available for my GSM
No, CWM is recovery. When you see that, it means you have done something to force your phone to boot off of the recovery partition, instead of the normal boot procedure. Fastboot is different; it's like an alternative to adb. You can put your phone into fastboot mode (I don't have your device, so I don't know how you would do it), but you can also communicate through fastboot when you're not in fastboot mode.
To test if you're able to communicate with the device properly, connect your phone via USB, then type adb devices to see which devices are visible to your system; same with fastboot devices .
post-mortem said:
No, CWM is recovery. When you see that, it means you have done something to force your phone to boot off of the recovery partition, instead of the normal boot procedure. Fastboot is different; it's like an alternative to adb. You can put your phone into fastboot mode (I don't have your device, so I don't know how you would do it), but you can also communicate through fastboot when you're not in fastboot mode.
To test if you're able to communicate with the device properly, connect your phone via USB, then type adb devices to see which devices are visible to your system; same with fastboot devices .
Click to expand...
Click to collapse
Now I'm lost ...........
I connect my phone to the laptop and it's recognized but where do I have to type this ???
Those commands you type on the laptop, in a cmd window. Remember step 2? You need to be in that folder (which you said was c:\ ).
post-mortem said:
Those commands you type on the laptop, in a cmd window. Remember step 2? You need to be in that folder (which you said was c:\ ).
Click to expand...
Click to collapse
SORRY I don't really know what you are talking about
I know the old ms-dos command prompt ...... do you mean that and where did we talk about it ??
bruce the boss said:
SORRY I don't really know what you are talking about
I know the old ms-dos command prompt ...... do you mean that and where did we talk about it ??
Click to expand...
Click to collapse
LOL, sorry! I got this thread confused with another one! Never mind about the step 2 thing.
Uh, yeah, so those commands are typed into a DOS prompt. You need to be in the same folder as where your adb and fastboot binaries are located (unless you added them to the PATH, of course).
go to samsung service center. claim warranty.
it's easier to fix it
Related
Hey guys.
I am assuming my phone is not "bricked" because I can still get to the clockworkmod interface and mount usb and things like that, but I cant get any roms to load. I followed all the instructions and multiple videos to make sure I did my 1.5 right. Seems to be find as far as root. When I logged in to my old backup i had superuser and all.
I tried to install the WARM rom, but didnt work, so i restored my backup and bought Flash Image GUI which then I loaded the WARM zip and it said it found the Kernel and went to install it. It then asked me to reboot, which I did, and then proceeded to install the rest of the ROM via clockwork install ZIP, after doing that I can no longer even restore my backup.
If i try to load WARM, it just sits at white HTC screen and never changes. If I try to load MIUI, it loads to HTC screen, makes a sound and then goes black forever with backlight on but black and buttons lit.
That is all I can currently do. My backup no longer loads or works.
Is my phone bricked? I dont think so since I can get to clockworkmod, but what can I do to try to get it back up and running?
Thanks,
M374llic4.
Your kernel is most likely the problem. When using the the flash image GUI, dont accept when it asks you to reboot, manually hold down the power button and reboot yourself. Hook up your phone to the computer and boot into fastboot usb and fastboot boot recovery.img then install the warm rom. This will ensure you have access to flash the kernel.
JayDaKissEP said:
Your kernel is most likely the problem. When using the the flash image GUI, dont accept when it asks you to reboot, manually hold down the power button and reboot yourself. Hook up your phone to the computer and boot into fastboot usb and fastboot boot recovery.img then install the warm rom. This will ensure you have access to flash the kernel.
Click to expand...
Click to collapse
Hey man, I am following most of what you said, but when yo said boot in to fastboot usb, I know how to do that, but how do i fastboot recovery.img, where is that?
m374llic4 said:
Hey man, I am following most of what you said, but when yo said boot in to fastboot usb, I know how to do that, but how do i fastboot recovery.img, where is that?
Click to expand...
Click to collapse
A friend kinda having a similiar issue with this.. but I tried this all on his computer and not sure if it's driver issues or not.. but I can't get adb to communicate with this phone.. when I use " adb device's " it doesn't show up.. but If i plug my phone it - it picks it up.. Same issue as the guy above it seems.. but when I go into the boot loader - click fastboot and it picks up the usb.. i still can't get them to talk.. any idea's?
m374llic4 said:
Hey man, I am following most of what you said, but when yo said boot in to fastboot usb, I know how to do that, but how do i fastboot recovery.img, where is that?
Click to expand...
Click to collapse
When you rooted your phone, you should have downloaded a folder called newevo3droot or something like that. There's adb files, fastboot..etc and this is how you would have flashed clockworl recovery. Since you are on hboot 1.5, you need to go into fastboot and connect usb so that it says fastboot-usb, then you need to run the command fastboot boot recovery.img. Recovery.img is the name of the recovery image file in that folder. I think it's something like cwm******.img
I did download that, and had some help from someone in the IRC channel and he got me back up up and running! Turns out you have to use USB fastboot on the phone along with fastboot.exe via cmd prompt on the pc with the CWM.exe to load the kernel, then once you do that, you use the phone cwm load from zip to load the rest of the rom and you are good to go!
JayDaKissEP said:
When you rooted your phone, you should have downloaded a folder called newevo3droot or something like that. There's adb files, fastboot..etc and this is how you would have flashed clockworl recovery. Since you are on hboot 1.5, you need to go into fastboot and connect usb so that it says fastboot-usb, then you need to run the command fastboot boot recovery.img. Recovery.img is the name of the recovery image file in that folder. I think it's something like cwm******.img
Click to expand...
Click to collapse
Yeah, thats what I did with some help from a fellow XDA member via IRC and it worked perfect! I was trying to do it all via the CWM on the phone side only, not via command prompt which was my issue.
Well, I have to ask for help right here because Goole/Yahoo/Wiki DIDN'T help. Although it's a bit long but please read it
Here's my problem:
At the last time that my phone is still being functional, I was playing the game "Contract Killer" and "Facebook", "Internet" were running in the background.
Suddenly, it shut off with showing "power off...(Sth like that). This is obviously a normal situation when the battery is out of power. I took it to charge as usual and went to sleep.
Next day, I waked up and tried to boot up my HTC EVO 3D...
First time: Stuck in the startup screen without playing the HTC opening sound track( The phone used to be in Silent Mode)
Second time: I pulled out the battery and put it back and boot again. Still stuck in the startup screen but this time it play the HTC opening sound track...
I've got a lot data in the internal memory and I've never BACKUP before.....
Is there anyway that can boot up my phone without losing the data???
Oh...my phone has never been rooted.
Anyone know the problem??? (
I dunno, kinda sounds like a Hard Reset/Factory Reset is in order. Did you take the battery out for a while and then try to reboot?
There's no way unless u can take to service provider an have them extract it
Sent from my PG86100 using XDA App
i had that kind of a problem once but i was on a CUSTOM ROM so i'm not sure it will work for you and I'M NOT SAYING this method is THE SAFEST.
so 1st thing i did was.. i panic'd... 2nd, i started googling and when all the signs pointed me to a boot up problem i opened the zipped rom, i extracted the boot.img, connected the phone to the pc in fastboot mode and flashed the boot image. after that it started with no problems, all my data was there. what do anyone else suggest? would it be okay to flash boot.img (stock one) on a stock rom?
I would suggest the following:
If rooted with custom recovery:
1. Pull out the battery
2. Replace the battery, and access recovery and do nandroid backup, you will only need the user data.
3. wipe, wipe, wipe
4. install the ROM you had and let it boot
5. reboot in to recovery and restore you DATA ONLY
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
let me know if anything helps.
PS. There is a great risk that you won't be able to recovery your apps data but lets try and hope for the best.
This sounds like a battery, cable, or AC adapter problem to me. You can get a cheap replacement battery on eBay for a few bucks and see how that works out. Also try different wall pieces, micro USB cables, and power outlets.
If none of that has worked, then you more than likely have a corrupted boot image. You can mount the EMMC (internal flash storage) onto a Linux distribution (like Ubuntu or Fedora) via usb and copy your data to a safe place like a flash drive or HDD. Then do an RUU (there are tutorials on this in the development thread) to restore the phone to stock, then of course pull whatever is needed from the data you saved.
Now if absolutely none of this has worked at all, you have malfunctioning hardware. Your only option at this point is to go to a Sprint store to have your data transferred over to a new replacement phone.
Hope this helped mate.
Sent from a Shooter running Android 4.0.3 via XDA Premium.
megabiteg said:
I would suggest the following:
If rooted with custom recovery:
1. Pull out the battery
2. Replace the battery, and access recovery and do nandroid backup, you will only need the user data.
3. wipe, wipe, wipe
4. install the ROM you had and let it boot
5. reboot in to recovery and restore you DATA ONLY
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
let me know if anything helps.
PS. There is a great risk that you won't be able to recovery your apps data but lets try and hope for the best.
Click to expand...
Click to collapse
First of all, thanks for helping~ I would like to know that will my data lose if install the custom recovery? Seems like a huge risk...
Besides, I am a little confused about using the .img to boot my phone.......
MikeyCriggz said:
This sounds like a battery, cable, or AC adapter problem to me. You can get a cheap replacement battery on eBay for a few bucks and see how that works out. Also try different wall pieces, micro USB cables, and power outlets.
If none of that has worked, then you more than likely have a corrupted boot image. You can mount the EMMC (internal flash storage) onto a Linux distribution (like Ubuntu or Fedora) via usb and copy your data to a safe place like a flash drive or HDD. Then do an RUU (there are tutorials on this in the development thread) to restore the phone to stock, then of course pull whatever is needed from the data you saved.
Hope this helped mate.
Sent from a Shooter running Android 4.0.3 via XDA Premium.
Click to expand...
Click to collapse
I was once using Nokia N900, and it is very easy to flash the rom meanwhile i can keep everything in the emmc remain unchanged! Since ANDROID is based on Linux, I am sure your way will be damn work! Any software or environment would i need to do these stuffs? Thx at all!!
:
All in all, I do care the messages in the phone only. That is what i really want.
Nokiawithandroid said:
All in all, I do care the messages in the phone only. That is what i really want.
Click to expand...
Click to collapse
Well if you can somehow get ADB access to your phone you can try to backup the following file:
/data/data/com.android.providers.telephony/databases/mmssms.db
This is there database that contains all your messages (SMS / MMS).
Flashing the boot.img file is easy, if you have the phone in fastboot (and it indicates the usb connection on the phone too) then you can just flash this way:
fastboot flash boot [location of boot.img]\boot.img
You will not loose any personal data, there that the partition affected by the boot.img is not the same as the one affected by /data. This also apply to the recovery section of the phone, in case you want to load a custom recovery:
fastboot flash recovery [location of recovery.img]\recovery.img
Hope this helps, if you need any more help let us know.
HELLO?
megabiteg said:
Well if you can somehow get ADB access to your phone you can try to backup the following file:
/data/data/com.android.providers.telephony/databases/mmssms.db
This is there database that contains all your messages (SMS / MMS).
Flashing the boot.img file is easy, if you have the phone in fastboot (and it indicates the usb connection on the phone too) then you can just flash this way:
fastboot flash boot [location of boot.img]\boot.img
You will not loose any personal data, there that the partition affected by the boot.img is not the same as the one affected by /data. This also apply to the recovery section of the phone, in case you want to load a custom recovery:
fastboot flash recovery [location of recovery.img]\recovery.img
Hope this helps, if you need any more help let us know.
Click to expand...
Click to collapse
How can i get to access my phone by ADB?
I am totally new for all these...
Nokiawithandroid said:
How can i get to access my phone by ADB?
I am totally new for all these...
Click to expand...
Click to collapse
This can get you acquainted with ADB
http://forum.xda-developers.com/showthread.php?t=1241935
Props to Droidzone for putting it all together.
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
Can i do the above things while i can't get connect USB with my phone - -?
Nokiawithandroid said:
If not rooted:
1. Install custom recovery
2. go to rooted instructions
IF this doesn't work you can get the .img files from the forums of the ROM you had or stock if that was what you had and only install the boot.img and system.img and try to see if you get the phone to boot with your data in there.
Can i do the above things while i can't get connect USB with my phone - -?
Click to expand...
Click to collapse
If you remove the battery off your phone and then you reinsert it back, press PWR+Vol UP to access the bootloader.
While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else.
WOW! I am approaching the target. To be clear, fastboot command stands for using ADB access?
AND:"While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else." means my phone can connect the computer by using "press PWR+Vol UP to access the bootloader"??? The bloody bootoader??
I am sure i'm almost there!!!!! THANKSSWSSSS
Nokiawithandroid said:
WOW! I am approaching the target. To be clear, fastboot command stands for using ADB access?
AND:"While in the Bootloader access fastboot and ensure to have the USB connected. from there, you can run any fastboot command you need, like loading custom recoveries or anything else." means my phone can connect the computer by using "press PWR+Vol UP to access the bootloader"??? The bloody bootoader??
I am sure i'm almost there!!!!! THANKSSWSSSS
Click to expand...
Click to collapse
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk
megabiteg said:
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Oh..damn.....the voyage is lengthy
What equipment/environment do i need?
My target: 1)Back up the Message Database 2) Run this bloody phone.
Difficulties: 1)S-ON 2)command 3) environment 4) Flashing a new (boot?image?)
megabiteg said:
Fastboot is a different command center from it counterpart adb. From fastboot you use only commands related to the flashing img files and more.
Just use fastboot /? From the command prompt to see a quick help of all what fastboot can do for you, but the main thing you'll need from this command is the ability yo flash a new boot, and maybe system image to get your phone back up and running.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Any thread for that?
I was trying to create more space. I saw the apps folder and moved it to somewhere else. Then my phone started crashing, so i turned it off. When i turned it back on i got a bootloop. My phone is rooted and i have an alacatel one touch 983. It keeps showing the o2 logo. I think this is because there is no launcher. Help please
If you have adb set up then pull the app folder from where you put it and push it to system/app. I presume you don't have a custom recovery or nandroid backup.
sinkster said:
If you have adb set up then pull the app folder from where you put it and push it to system/app. I presume you don't have a custom recovery or nandroid backup.
Click to expand...
Click to collapse
I think i put it in custect (or a something like that) but not sure, can i just push a folder called app and then add the launcher?
Bump - Please help. CMD says error: device not found, but i have sdk. Im trying to change the driver but it keeps saying its up to date.
If you're not sure where you put the folder then using adb could be pretty tedious anyway... You'd need the whole file, the bootloop probably won't be caused solely by having no launcher. If you've got a custom recovery then flash the Aroma file manager to find/move the folder, or find a CWM/TWRP flashable home launcher. If not, then your best bet is probably to use One touch support to update your rom, i,e, reflash back to stock.
sinkster said:
If you're not sure where you put the folder then using adb could be pretty tedious anyway... You'd need the whole file, the bootloop probably won't be caused solely by having no launcher. If you've got a custom recovery then flash the Aroma file manager to find/move the folder, or find a CWM/TWRP flashable home launcher. If not, then your best bet is probably to use One touch support to update your rom, i,e, reflash back to stock.
Click to expand...
Click to collapse
Well, i have a system.img that i want to flash with fastboot. i also found an o2 rom for my phone. So if i could get adb or recovery mode to work i could restore it. I have a rough idea of where it is, so i could get it, but adb and fastboot don't recognise my device. I tried hard resetting it by holding the volume up button but im still stuck at the o2 screen. I have tried the alcatel driver but that doesn't work. It doesn't recognise it when i try to put it into recovery mode. If you know the combination for the alcatel 983 please say. Maybe it is because hard resetting it disabled usb debugging, but my pc recognises it fine. (cannot open sd card), but it recognises it and it's name. So i do not know why adb doesn't recognise it.
I'm not familiar with Alcatel phones, but it should be volume down while turning on for fastboot. If you can get into fastboot you should be able to flash a custom recovery.
sinkster said:
I'm not familiar with Alcatel phones, but it should be volume down while turning on for fastboot. If you can get into fastboot you should be able to flash a custom recovery.
Click to expand...
Click to collapse
Holding up while turning on makes it to hard reset and holding down does makes it freeze. So how can i make it work with adb on my pc. Should i try a different pc? There are no other buttons, it is touch screen.
Actually holding down while it says waiting for device works, testing some stuff out now thanks. will show my resuslts
When you switch on/press down, the freeze is the phone in fastboot (apparently), so try that, connect to your pc, open cmd window where you'd normally open adb and try 'fastboot erase cache' and see if you get a response. should return a message saying cache erased, or similar. If so, you're in fastboot and you can use it to flash a custom recovery (obviously one for your phone)
This post seems to be a similar issue/resolution. There's no custom recovery yet for the phone.
sinkster said:
When you switch on/press down, the freeze is the phone in fastboot (apparently), so try that, connect to your pc, open cmd window where you'd normally open adb and try 'fastboot erase cache' and see if you get a response. should return a message saying cache erased, or similar. If so, you're in fastboot and you can use it to flash a custom recovery (obviously one for your phone)
Click to expand...
Click to collapse
ok ill try thanks.
Well i done that, but now it is frozen at the o2 screen. I flashed boot, recovery and system img. Lower buttons work but its stuck at o2 screen. What do i do next?
Can you connect with adb yet?
sinkster said:
Can you connect with adb yet?
Click to expand...
Click to collapse
Nope still no adb, still saying device not found. Is there an adb mode that i can get to?
Adb needs the system to respond, out may be borked due to the move of the system/app folder. What commands did you use in fastboot? Fastboot flash system xxx.img?
sinkster said:
Adb needs the system to respond, out may be borked due to the move of the system/app folder. What commands did you use in fastboot? Fastboot flash system xxx.img?
Click to expand...
Click to collapse
Yes i did fastboot flash system/boot/recovery for each their img's. Well i am trying the alcatel one touch update now. Ill see if that fixes it. Ill report back when its done
ok, good luck.
sinkster said:
ok, good luck.
Click to expand...
Click to collapse
Well, that didn't work. Got any other tips? Im still stuck at o2 screen. Thanks
supernovakid said:
Well, that didn't work. Got any other tips? Im still stuck at o2 screen. Thanks
Click to expand...
Click to collapse
It has worked, thanks a lot for your help! You are a great person thanks!
No probs.
I kinda messed up about a month ago, I was wanting to root my HTC One so I could try some custom ROMS and experience other cool stuff
However, Me, feeling nervous decided to go the Cyanogenmod Installer route (You know this isn't gonna end well). And so I plugged in my device and everything was good and fine until It was unlocking my bootloader, it seemed to do the HTCDev one, I got the option to unlock it or lock it, and as soon as the device restarted the phone disconnected.
Some apps went missing, however I recently had a talk to a friend who said that is normal, and he recommended me to come here to get some help.
I can boot into the bootloader where you can go into fastboot and stuff, I can factory reset through the Android OS once its booted, however when I enter recovery in the bootloader, the screen goes black and a red exclamation mark shows up for about 5-10 minutes and then the device reboots into Android.
The same thing happens when I try to get Over the air updates, I can still get OTA updates, they just don't install.
So what I'm looking for is, can I relock my device and get it back to how it was before I ran Cyanogenmod installer and then maybe I can try root it manually and have more control over the situation.
I hope you guys can help me and I hope I can find a place on this forum
Thanks in advance guys!
First of all, it seems you shouldn't have started to mess with this at all...
now to fix this...
Download the latest recovery of your choice e.a. twrp. @ http://techerrata.com/browse/twrp2/m7 the normal one is the m7 i suppose? else go to the right section...
save it to your /sdcard directly or move it there. than for the eaz just rename it to twrp.img
open an terminal if installed on your device and type
su
than
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 (note command for the m7)
if you however don't have the capability to install an app because of missing gapps... which sounds like it...
install adb/fastboot on your pc with the htc drivers..
download the recovery image with your pc and rename it to twrp.img and put it at your fastboot file
turn off your device
keep holding volume down until a menu shows up
select fastboot from the menu
attach the device to your pc
open cmd and type fastboot devices (to see if you actually installed the right driver... and that it's recognizing it)
if it does
type:
fastboot flash recovery twrp.img
if that all succeeded, you can download gapps for the android version your using or flash something else with the working recovery..
goodluck!
Hawkysoft said:
First of all, it seems you shouldn't have started to mess with this at all...
now to fix this...
Download the latest recovery of your choice e.a. twrp. @ (It prevented me posting links) the normal one is the m7 i suppose? else go to the right section...
save it to your /sdcard directly or move it there. than for the eaz just rename it to twrp.img
open an terminal if installed on your device and type
su
than
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 (note command for the m7)
if you however don't have the capability to install an app because of missing gapps... which sounds like it...
install adb/fastboot on your pc with the htc drivers..
download the recovery image with your pc and rename it to twrp.img and put it at your fastboot file
turn off your device
keep holding volume down until a menu shows up
select fastboot from the menu
attach the device to your pc
open cmd and type fastboot devices (to see if you actually installed the right driver... and that it's recognizing it)
if it does
type:
fastboot flash recovery twrp.img
if that all succeeded, you can download gapps for the android version your using or flash something else with the working recovery..
goodluck!
Click to expand...
Click to collapse
Thank you! Will there be a risk in ruining my device?
And thank you once again! I definitley shouldn't have messed with this, but you gotta start somewhere right?
If I never took the risk of building my own computer then I never could have done it Its how we learn.
Anyways, I'm not sure about the terminal bit, I don't run linux and I don't have a mac? So, how would I have access to the terminal. Unless I somehow got it on my device (I don't know how to do that).
And one more question, once I've done the things you've told me to do I can just put Cyanogenmod on it?
Thanks once again
Oh, and I have got Gapps, if my Gapps you mean Google Apps, yes I have I've got Google play services, Google play, hangouts etc.
Thank you! Will there be a risk in ruining my device?
Click to expand...
Click to collapse
Further than now? i highly doubt it... unless you totally put in a wrong recovery which magically wud fk up the partitions?
And thank you once again! I definitley shouldn't have messed with this, but you gotta start somewhere right?
Click to expand...
Click to collapse
True, but babysteps mate...
Anyways, I'm not sure about the terminal bit, I don't run linux and I don't have a mac? So, how would I have access to the terminal. Unless I somehow got it on my device (I don't know how to do that).
Click to expand...
Click to collapse
Terminal should be on the phone, if not use command prompt in windows... u need to do a little research on the m7 forums which driver you need they probably have an m7 toolkit again if the one is the m7, as far as i knew it is.. than you could put the recovery.img in the folder of fastboot.exe and go there with command prompt and do what i've written before
And one more question, once I've done the things you've told me to do I can just put Cyanogenmod on it?
Click to expand...
Click to collapse
erhm ofcourse you can, however just download the rom instead of an installer...
p.s. you got gapps.. install an emulator oh... better solution... install flashify download the latest twrp and install it with that if u have proper root that is!
Hawkysoft said:
Further than now? i highly doubt it... unless you totally put in a wrong recovery which magically wud fk up the partitions?
True, but babysteps mate...
Terminal should be on the phone, if not use command prompt in windows... u need to do a little research on the m7 forums which driver you need they probably have an m7 toolkit again if the one is the m7, as far as i knew it is.. than you could put the recovery.img in the folder of fastboot.exe and go there with command prompt and do what i've written before
erhm ofcourse you can, however just download the rom instead of an installer...
p.s. you got gapps.. install an emulator oh... better solution... install flashify download the latest twrp and install it with that if u have proper root that is!
Click to expand...
Click to collapse
Thanks I don't have root, I've run rootchecker, and it says I don't have root.
And what if I do Cyanogenmod but I want to go back to HTC Sense (Doubt it though)
Will instlaling the recovery root my device? If not, how will I root it?
Oh and, how do I get fastboot and ADB?
Hi. so today i thought i would try to unlock bootloader and root then install a custom rom. I got everything ready on windows 8.1 . managed to unlock the bootloader and then when to flash twrp. Now the error i made is instead of flashing twrp i booted into it. I then proceeded to make the necessary wipes and then went to mount phone to pc so i could transfer the zip for the new rom and the phone just wouldnt show up on my pc. I tried eveything. So now i can only do 2 thing.s Boot into fastboot or into stock reocvery which offers 2 choices. update with update zip already placed in phone or clear data. When i boot into fastboot and then connect hpone and opem command prompt then type adb usb it starts daemon then says devices. In device manager it shows adb interface fine. So what can i do now as i need this phone to work as dont have a spare. How can i get it to let me use adb usb properly so i can flash twrp and then flash rom. It currently has no os on phone. Is there a way to flash via the phone itself? Also if i let it boot up it auto matically open stock reocvery. Can anyone please help asap thanks.
Heyyo, @dead4ngel
Derp! Just figured it out. Once you're in fastboot you don't use adb devices command, it changes to stuff like fastboot devices
Hence there's an adb.exe and a fastboot.exe
So for example once you're in fastboot on your phone and you plug in your usb cable? To flash TWRP you would do this on your command prompt
fastboot flash recovery twrp.img
by chance have you tried this guide? Worked for me
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151/
You legend!!!!
ThE_MarD said:
Heyyo, @dead4ngel
Derp! Just figured it out. Once you're in fastboot you don't use adb devices command, it changes to stuff like fastboot devices
Hence there's an adb.exe and a fastboot.exe
So for example once you're in fastboot on your phone and you plug in your usb cable? To flash TWRP you would do this on your command prompt
fastboot flash recovery twrp.img
by chance have you tried this guide? Worked for me
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151/
Click to expand...
Click to collapse
Thank you so much. That worked right away. Theen all i had to do is mount in twrp and install mtp device. Now copying rom to internal and i should be good to go. Im so happy was ****ting bricks thinking iv just killed this phone only after 3 months of having it lol.
dead4ngel said:
Thank you so much. That worked right away. Theen all i had to do is mount in twrp and install mtp device. Now copying rom to internal and i should be good to go. Im so happy was ****ting bricks thinking iv just killed this phone only after 3 months of having it lol.
Click to expand...
Click to collapse
Glad to hear you got her sorted out
If you experience fingerprint reader issues when your device is asleep please flash an updated version of the modem firmware. I know it sounds odd but it does affect fingerprint reader performance when the device is asleep.
Chinese 26s 05.09 from here works good
https://yadi.sk/d/woKdrlRrv8yhr/Китай
But others have preferred developer 466D from here
https://yadi.sk/d/woKdrlRrv8yhr/Для разработчиков
Modem firmware is separate from the ROM so you can flash them freely without risk of wiping out your ROM
Try each for a few days and see which one works best for you