[Q] Stuck in HTC startup screen while booting - HTC EVO 3D

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?

Related

1.5, used Flash image gui, can't restore back up, cant load roms, white htc screen.

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.

Flash the boot.img FOR RUNNING my shipped phone

My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
1) I cannot boot my phone, the best i can is going to the bootloader
2)USB debugging can't function since i can't boot my phone
My phone:
HTC EVO 3D GSM
Hboot 1.49.0012
LOCKED
S-ON
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Nokiawithandroid said:
My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Click to expand...
Click to collapse
Are you CDMA sounds like your on hboot 1.5? I dunno are you gsm or CDMA?
I know CDMA users make sure you have a copy of your recovery in your adb folder...
Make sure debug is turned on
Then when your in hboot
and plugged into computer using adb...
Type
fastboot boot recovery.img
This way you can flash whatever you want rom wise without taking the boot.img out of it... Also wipe before you go flashing...... This won't brick you... Only way to brick which is hard to do is you would have to flash the wrong radios or be in the middle of a flash or radio flash and pull the battery or your battery dies.... A brick is a useless phone that won't turn back on....
No such thing as a soft brick either lol.. Those are called bootloops or aka stuck on splash screen.... As long as your phone boots to Hboot your safe...
reaper24 said:
Are you CDMA sounds like your on hboot 1.5? I dunno are you gsm or CDMA?
I know CDMA users make sure you have a copy of your recovery in your adb folder...
Make sure debug is turned on
Then when your in hboot
and plugged into computer using adb...
Type
fastboot boot recovery.img
This way you can flash whatever you want rom wise without taking the boot.img out of it... Also wipe before you go flashing...... This won't brick you... Only way to brick which is hard to do is you would have to flash the wrong radios or be in the middle of a flash or radio flash and pull the battery or your battery dies.... A brick is a useless phone that won't turn back on....
No such thing as a soft brick either lol.. Those are called bootloops or aka stuck on splash screen.... As long as your phone boots to Hboot your safe...
Click to expand...
Click to collapse
Sorry, update the status apologize for the mistakes
Any expertise?
Helpppppppppppppppp pleaseeeeeeeee!!!!!!!!!!!!!!!!!!!!! (((
Nokiawithandroid said:
My problem:
http://forum.xda-developers.com/showthread.php?p=22444589
1) I cannot boot my phone, the best i can is going to the bootloader
2)USB debugging can't function since i can't boot my phone
My phone:
HTC EVO 3D GSM
Hboot 1.49.0012
LOCKED
S-ON
Thread I have read:
http://forum.xda-developers.com/showthread.php?p=22444589
http://forum.xda-developers.com/showthread.php?t=1372097
http://forum.xda-developers.com/showthread.php?t=1467293
In conclusion, I understand the following:
boot my phone to fastboot
(turn off first.make sure completely off, then press volume down and power button)
connect my phone to pc, open cmd.exe
Sth I dk how to use:
(fastboot flash boot [location of boot.img]\boot.img
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands)
However, I would like to do a fastboot flash boot to solve the problem of stuck in HTC startup screen.
Difficulties: 1) .img file 2) command 3) would it "brick"? 4) KEEP SHIPPED
Targets: 1) Do not erase (mmssms.db) 2)mmssms.db backup and recovery 3) Functions my phone
Click to expand...
Click to collapse
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
joeykrim said:
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
Click to expand...
Click to collapse
I am having something close to that issue. i have Hboot 1.49.0008 it is Unlocked but with s-On
now i can boot farther then the htc white. mine goes to the htc + quietly brilliant screen. then hits a boot loop.
what are my options and how do i do it?
thanks
joeykrim said:
Seems to be conflicting information provided in the OP. Not sure the best route. Here is the information that seems to conflict, perhaps I misread?
1)If you're S-ON and LOCKED, I don't think you'll have access to use fastboot or any other HTC officially supported method of flashing the kernel. Normally, if you had previously unlocked the device to load a custom kernel and re-locked, it will show RELOCKED instead of LOCKED. Unless, you went the revolutionary route and then reflashed back to stock removing their S-OFF?
2) The kernel/boot partition will not touch the /data partition where (mmssms.db) is stored.
3) The device is pretty difficult to "brick". The common users you'll find claiming they have a brick, is generally due to their ignorance in not following proper directions to restore their device. Some find it easier to claim they "bricked" their device rather than do the proper research to resolve their issues.
4) The HTC splash screen freezing is generally either a bad/incompatible kernel or a bad/incompatible kernel/ROM combination. To fix either of this situations, the device will need to be UNLOCKED and/or S-OFF to allow write access to at least the kernel partition and, if needed, the system partition.
Hope that helps clarify some more!
Click to expand...
Click to collapse
ok...then what can I do to fetch the data out or save my phone?
Nokiawithandroid said:
ok...then what can I do to fetch the data out or save my phone?
Click to expand...
Click to collapse
based on what has been said in the thread, you can flash a new system.img and that should give you access to the phone even if it starts FC like hell, all you need to do from there is to connect via adb backup the SMS database and continue with wiping everything and installing a new ROM (after you unlock of course)
just in case: once you get the system.img you need, apply it by typing
Code:
fastboot flash system [x:\path to file\]system.img
That should help you out.
megabiteg said:
based on what has been said in the thread, you can flash a new system.img and that should give you access to the phone even if it starts FC like hell, all you need to do from there is to connect via adb backup the SMS database and continue with wiping everything and installing a new ROM (after you unlock of course)
just in case: once you get the system.img you need, apply it by typing
Code:
fastboot flash system [x:\path to file\]system.img
That should help you out.
Click to expand...
Click to collapse
How can i flash the system.img? My phone isn't rooted or unlocked. It's totally original. Also, no way to get the debug or adb. The only connection I've got is the "fastboot usb" at the htc original bootloader.
Hopeless, right?
Nokiawithandroid said:
How can i flash the system.img? My phone isn't rooted or unlocked. It's totally original. Also, no way to get the debug or adb. The only connection I've got is the "fastboot usb" at the htc original bootloader.
Hopeless, right?
Click to expand...
Click to collapse
You posted this same question in a separate thread: http://forum.xda-developers.com/showthread.php?t=1525176
In an effort to keep the threads organized, I answered in that thread as follows:
Background on system.img: The system partition is generally only distributed in the system.img format for stock system images. Most aftermarket ROMs perfer to distribute their system content in the form of an update .zip file.
Background on bootloader: The system.img can't be flashed until you unlock the device. This is a standard security feature on any device with a "locked" bootloader, as yours shows from the information you posted.
One option: Once the bootloader is unlocked, the command should be as simple as: fastboot flash system c:\system.img
Hope that helps. Good luck!
Click to expand...
Click to collapse
Not sure how many times this can be repeated or how many different ways the same thing can be repeated. Without unlocking the device, HTC will not allow you to selectively modify any of the partitions from the bootloader or fastboot.
With these three conditions:
1) Without unlocking the device
2) Having the device freeze on the HTC splash screen
3) Never having previously loaded a custom recovery
The only option HTC provides is to run the RUU which will return the device to 100% stock erasing all information currently on the device.
If you're able to unlock the device (condition #1), you would be able to either flash a custom recovery (condition #3), or a stock/new system.img which would allow you access to the device where you can retrieving the stored SMS and MMS.
Using the stock RUU should resolve condition #2, if it didn't, there could be a more serious hardware issue with the device.
I might have missed some aspect. I'm sure somebody will post up if I did.
Hope that helps make more sense!

Ace 2 (I8160) not on the Wifi

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

Help!!! My Rezound got bricked!! :'(

Ok... This is my 4th android phone.. And I love this phone... And only had it for a week.... and just now got it bricked.... here's what happen... Today I tried to flash a sense 4.1 rom, but im so new at this, and I'm half way done, and I went in a rush because I was nervous, and I accidentally press "install and keep data" and that was my mistake. I factory reset it b4 so I tried to flash it... So I thought it wouldn't be a problem. So I waited till the phone finish flashing. And when I rebooted the phone.... Nothing happened, just stuck on the white screen.... vibrating and etc... And I tried to restore all my data in clockworkmod recovery like I never even tried flashed it.. and it kept saying "won't mount sd card" and I tried to clear my cache/dalvik-cache, and like it still wont fix the issue. I even tried to restore wat I backup b4 I tried to flash it... and It was gone!!! Even my windows 8 laptop won't even detect my resound nor my sd card(unless its on a different android). But How can I fix my Rezound?!? plzzzz How can I fix this soft bricked issue? pllzzzzzzz help!!!
Im assuming you already have adb installed
Download this file
http://www.mediafire.com/download/oa2sjlvrecx0wdn/recovery-ra-vigor-3.16-gnm.img.zip
Extract the recovery img
Put it in the adb folder
Load into fastboot
Open up the terminal
Put "cd" then hit space
Drag and drop the adb folder into the terminal window then hit enter
Now use this command to flash that recovery "fastboot flash recovery recovery.img" (without the quotation marks)
Now go into recovery Find "format data system cache ect."
Go to format all to ext3 once that is done hit return
Flash your prefered rom from the flash menu and all that
Once you are done return to the main menu and go to "developer menu"
Then reboot to bootloader
Now go into your rom that you downloaded on your pc and find the rom now open it and get the boot.img
Copy the boot.img file to your adb folder
Open up terminal again and this time use the command "fastboot flash boot boot.img" in terminal its going to say sending then writing usually takes a couple of seconds
now just go to the reboot option and your rom should work
Now remember that since you are s on you need to get the boot.img file from EVERY rom you install and flash it thru the terminal in order to get your rom working
xkjonathanxk said:
Im assuming you already have adb installed
Download this file
http://www.mediafire.com/download/oa2sjlvrecx0wdn/recovery-ra-vigor-3.16-gnm.img.zip
Extract the recovery img
Put it in the adb folder
Load into fastboot
Open up the terminal
Put "cd" then hit space
Drag and drop the adb folder into the terminal window then hit enter
Now use this command to flash that recovery "fastboot flash recovery recovery.img" (without the quotation marks)
Now go into recovery Find "format data system cache ect."
Go to format all to ext3 once that is done hit return
Flash your prefered rom from the flash menu and all that
Once you are done return to the main menu and go to "developer menu"
Then reboot to bootloader
Now go into your rom that you downloaded on your pc and find the rom now open it and get the boot.img
Copy the boot.img file to your adb folder
Open up terminal again and this time use the command "fastboot flash boot boot.img" in terminal its going to say sending then writing usually takes a couple of seconds
now just go to the reboot option and your rom should work
Now remember that since you are s on you need to get the boot.img file from EVERY rom you install and flash it thru the terminal in order to get your rom working
Click to expand...
Click to collapse
If you are S-ON, you are likely not bricked, it's almost impossible to completely brick when you are S-ON.
Why do people keep telling occasional flashers that are S-ON to do this?!?!? It is the hard way, also don't use Amon Ra, is it outdated and known to cause issues with current ROMs, use TWRP or CWM recovery!!! Also, verify your ROM is specifically for the HTC Rezound, check the Developer threads here and make sure it is stable and widely used unless you really know what you are doing.
Although xkjonathanxk is on the right track, he is making more complicated than it needs to be...
- Download the first link in the first post of this thread and place it on the root of your SD card: [Tool] - 3/24 - CleanWIPE 1.0 - Wipe 5 or 10x before ROM install! - 1heffer Edition! (CleanWIPE formats all the necessary partitions for you, and prepares the phone for a new ROM)
- Download TWRP or CWM Rececovery (one of the first two links in post 1) and extract the recovery*.img and place it in the adb folder that contains fastboot.
- Download a tested and verified ROM of choice and place it on the root of your SD card
- Now, reboot into fastboot, remove battery and hold down Power and Vol Dn, once the menu comes up select Fastboot and press power, connect phone to PC
- In ADB enter the command "fastboot devices", if it shows a device continue, if not report back please
- Now enter the command "fastboot boot recovery.img" and TWRP (or CWM) should open on the device in a few seconds (replace recovery.img with whatever the name of the xxxx.img file is from TWRP or CWM archive)
- Install the CleanWIPE zip from above
- Install ROM zip image
- Reboot and enjoy the goodness
Remember to give the ROM some time to settle down on the first boot, and that the first boot can take a long time, like a painfully wrong "WTF did I do to ruin my device!" long time, but give it a solid 10 minutes before doing anything else.
@acejavelin
acejavelin said:
If you are S-ON, you are likely not bricked, it's almost impossible to completely brick when you are S-ON.
Why do people keep telling occasional flashers that are S-ON to do this?!?!? It is the hard way, also don't use Amon Ra, is it outdated and known to cause issues with current ROMs, use TWRP or CWM recovery!!! Also, verify your ROM is specifically for the HTC Rezound, check the Developer threads here and make sure it is stable and widely used unless you really know what you are doing.
Although xkjonathanxk is on the right track, he is making more complicated than it needs to be...
- Download the first link in the first post of this thread and place it on the root of your SD card: [Tool] - 3/24 - CleanWIPE 1.0 - Wipe 5 or 10x before ROM install! - 1heffer Edition! (CleanWIPE formats all the necessary partitions for you, and prepares the phone for a new ROM)
- Download TWRP or CWM Rececovery (one of the first two links in post 1) and extract the recovery*.img and place it in the adb folder that contains fastboot.
- Download a tested and verified ROM of choice and place it on the root of your SD card
- Now, reboot into fastboot, remove battery and hold down Power and Vol Dn, once the menu comes up select Fastboot and press power, connect phone to PC
- In ADB enter the command "fastboot devices", if it shows a device continue, if not report back please
- Now enter the command "fastboot boot recovery.img" and TWRP (or CWM) should open on the device in a few seconds (replace recovery.img with whatever the name of the xxxx.img file is from TWRP or CWM archive)
- Install the CleanWIPE zip from above
- Install ROM zip image
- Reboot and enjoy the goodness
Remember to give the ROM some time to settle down on the first boot, and that the first boot can take a long time, like a painfully wrong "WTF did I do to ruin my device!" long time, but give it a solid 10 minutes before doing anything else.
Click to expand...
Click to collapse
I really appreciate your help and everything. So i thank you. But Like i said im running windows 8, it wont detect my rezound or my sd card, the only time the pc is able to detect the sd card is when im able to mount my sd card to CWM. But it really wont detect it.... help me again
Multidex24 said:
I really appreciate your help and everything. So i thank you. But Like i said im running windows 8, it wont detect my rezound or my sd card, the only time the pc is able to detect the sd card is when im able to mount my sd card to CWM. But it really wont detect it.... help me again
Click to expand...
Click to collapse
Ubuntu Live CD... Windows not required.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Dont know how to work ubuntu.. help again
acejavelin said:
Ubuntu Live CD... Windows not required.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Click to expand...
Click to collapse
lol its the good thing i know how to make a dual os between win8 and ubuntu, but heres another problem, i dont even know how to work ubuntu...
i think my pc can detect the rezound. But idek how to work ubuntu, plzzzz help!!
Multidex24 said:
lol its the good thing i know how to make a dual os between win8 and ubuntu, but heres another problem, i dont even know how to work ubuntu...
i think my pc can detect the rezound. But idek how to work ubuntu, plzzzz help!!
Click to expand...
Click to collapse
For the things you need to do, its not much different than Windows. Download and install adb, copy images to same places, and the commands are pretty much the same. If you can dualboot you obviously have some knowledge of such things.
If this is all do difficult, just grab a thumb drive, put mini-adb, recovery.img, and your ROM on it and go to a buddies computer with Win7 for 20 minutes and get it done that way.
I know this seems like a huge, potentially fatal problem, but it is minor...
Another thought I had... Download TWRP, go into CWM recovery and copy the TWRP file and ROM to the sd card, and FLASH TWRP recovery ZIP with CWM recovery, reboot into recovery and you will then be on TWRP and you can use TWRP's HTC Dumlock to flash the ROM and the boot.img without a PC at all... In theory, it should work.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app

[Q] Padfone X T00D, "Can't Load Invalid boot image" Solution?

Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
MH928 said:
Hello,
I just purchased this phone knowing that it has this problem and I am trying to fix it but I do not know much about the original firmware or anything except of the following:
SKU: 6233A, MFG: 2014/05/30, HW: R1.6
I need to restore the Firmware and preferably be able to use the Dock Station (reason I bought it).
I also like to use it with T-Mobile and do not know if these phones are locket to ATT or not.
I am not a developer but have good technical knowledge.
Any advice will be appreciated.
Thank you
Mike
Click to expand...
Click to collapse
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
paleszgergo said:
Hopefully you can enter in to fastboot mode.
Try to reflash this ATT_userdebug rom from TWRP recovery, and then restore this backup.
1. Turn on the fastboot mode(vol up + power), plug in the cable to PC, open CMD, Boot in to twrp(fastboot boot recoveryyouchoose.img) and use "adb push filename.zip /sdcard"
2. install .zip then reboot
3. boot up, then boot back to TWRP recovery, make a backup.
4. boot up, copy the downloaded backup, boot back to recovery
5. restore it.
hope it works
Click to expand...
Click to collapse
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
MH928 said:
The second link (to restore) redirects to another Thread but most of the links there do not work, can you send me a direct link to the file?
Click to expand...
Click to collapse
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Justatechie said:
I think he meant these for the second link.
http://forum.xda-developers.com/showpost.php?p=60403709&postcount=34
Edit: you must use twrp to flash these backups after user debug.
Click to expand...
Click to collapse
Yeah, thats what i mean!
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Sirocco.ukr.lviv said:
Please help. the same problem. Invalid boot. TWRP recovery i have already. please help step by step...
(why invalid boot? i flashed new recovery from Quarx to a boot partition )
Click to expand...
Click to collapse
Is your Bootloader unlocked?
Justatechie said:
Is your Bootloader unlocked?
Click to expand...
Click to collapse
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Sirocco.ukr.lviv said:
Locked bootloader. Where i can see for sure?
When VolUp+Power i can see this window
I need adb driver.
TWRP that i have on this phone is old one ported from nexus device and it can't see SD card.
Click to expand...
Click to collapse
To find out, you have to put your phone into fastboot.
To do that power down your phone, then hold volume up and power button at the same time. There, the asus logo will pop up like normal and hang on that screen to show that you are in fastboot mode.
Open up command prompt and verify your device is connected, by typing in fastboot devices.
If it shows up good then all you have to do is type in fastboot oem device-info.
If it says device unlocked: true that means your BL is unlocked.
If its not, you have to download crowlock from the cm12 thread and flash it.
It works better with cwm but since you are stuck its worth a shot to flash it under old twrp.
Then check the BL status again, if its good great.
You could restore your device from some backups posted or if you could find a boot.img from the stock image, you could use the new version of twrp to flash the boot image under image flashing.
This is the adb/fastboot driver I use http://forum.xda-developers.com/showthread.php?t=2588979
Justatechie you are only one who help. i appreciate it. god bless you!
i've done it. unlocked already. i watched bootloop so i wiped everything. what rom to install?
del
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Justatechie said:
Nice to hear that.
Well it depends if you want to install one or you want to keep it stock.
For keeping it stock unfortunately you must restore from backups posted.
If its custom well Cm is a good way, just the dock does not work, but it will work hopefully soon when the developer receives it soon.
Click to expand...
Click to collapse
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Sirocco.ukr.lviv said:
My asus padfone x T00D with full wipes identifies like T00N (padfone s) and reboots on first welcome screen on your rom...
please see video:
https://www.youtube.com/watch?v=aMB9Ctvrk0Q
Click to expand...
Click to collapse
Dont worry about the asus_toon, it will turn back into padfone x when you are finally able to restore to the at&t factory rom
What is very strange,is that you cannot wipe certain things, I guess It may be due to a tampered bootloader. (something must have tripped it up)
My bootloader is unlocked but not tampered.
But the reason why it says ASUS_T00N is because you installed cm or miui and it changed build prop and the partitions. (all of quarx roms are built from the pfs source but work on the pfx too) its not a big deal don't worry.
Have you tried any other recoveries, perhaps the older version of twrp Here
Try booting them through fastboot using the fastboot boot filename.img (of the recovery file that should be located inside a folder containg fastboot/adb files)
See if they can wipe cache data(no media) and system. Remember, booting from fastboot is just temporary
Then try flashing a rom, doesnt matter what it has to be but it should work after its done. Maybe flash without gapps, it could sometimes cause a random problem and besides you can always install it later.
I never had to use fastboot to wipe cache either because well I could do that in recovery, plus its safer

Categories

Resources