I tried to change system fonts, I replaced files in /system/fonts using adb and rebooted phone. Now it hangs on boot screen now, I have only fastboot and recovery access. How I can fix my phone?
I tried to run RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe but I get USB-connection error.
I thought about flashing from SDcard, but I don't know how to do it.
Can you help me?
I found solution:
http://forum.xda-developers.com/showpost.php?p=4467471&postcount=13
Related
I successfully rooted my phone using this method:
http://forum.xda-developers.com/showthread.php?t=2130276
Then I tried the following method to modify multi-window on the phone:
http://www.andromods.com/tips-trick/verizon-galaxy-note-2-adding-all-apps-to-multi-window-bar.html
And ran into this problem on this step:
4. Copy and replace “FlashBarService.odex” to “/system/app” folder, as well as “services.odex” to “/system/framework” folder. If you have difficulty to replace services.odex, reboot your device. In case you experiencing bootloop after replacing services.odex, then you need to pull out and reinsert the battery, if the bootloops remains, just flash the root image with ODIN to fix it.
PROBLEM: THE PHONE FROZE. THEN WHEN I REMOVED AND RE-INSTALLED THE BATTERY AND TURNED IT ON, IT LOADS UNTIL THE 4GLTE SCREEN AND REMAINS THERE INDEFINITELY.
- I did what it directs to do with the battery but it didn't work.
- I don't know what it means to "flash the root image with ODIN"
I've tried this to fix it:
http://galaxynote2root.com/galaxy-n...ootunbrick-galaxy-note-2-with-stock-firmware/
and I believe maybe another thing with odin. Odin usually fails, maybe it's just my USB drive. But i have no idea what to do, or what to even look up to learn how to fix it because I don't know what my problem is called.
Can anybody help me by giving me a method to use or steps to follow or some information?
Try this
http://forum.xda-developers.com/showthread.php?t=2040264
It is called a boot loop by the way
God bless the American people.
barrackOBAMA said:
It is called a boot loop by the way
Click to expand...
Click to collapse
Its not a boot loop, that would be when you try to boot a phone (or anything) and it crashes mid boot restarting again only to crash again, his is just freezing and not fully booting.
Milimbar said:
Its not a boot loop, that would be when you try to boot a phone (or anything) and it crashes mid boot restarting again only to crash again, his is just freezing and not fully booting.
Click to expand...
Click to collapse
That's right, you understand. and perhaps I just don't know what it means but, I don't think it "freezes" on the 4GLTE screen, it loads until that screen and then continues to be animate, rings appearing and disappearing, loading indefinitely. I don't know if that's anything different, but just in case that clarifies anything.
and I tried http://forum.xda-developers.com/show....php?t=2040264 but to no avail. it always fails @ or immediately after the RECOVERY step.
Any ideas?
I have a Sero 7 Pro that has sero7pro-bld60220-dopa-v2.0 installed. It has been working fine for months until last night when I picked it up and it was powered off. It was plugged in to my PC usb port like I usually keep it so the battery should have been fully charged and I don't know why it powered itself off. Now it won't boot up. It sticks on the bootanimation screen. I tried to get into Fastboot using the volume/power button but it just hangs on the Fastboot screen and never goes any further. I am able to get into Recovery and have tried various options from just clearing cache and data to restoring the original OS using sideload and Adb on my PC. Nothing allows me to boot beyond the bootanimation. I have also tried to replace the bootanimation.zip file in the /system/media folder but it continues to try to boot with the same animation file. Is this somehow related or am I replacing the file in the wrong folder? Any ideas what might be wrong? How do I retrieve a log file to help diagnose the problem?
I attempted return to totally stock using XE-Sero7Pro-factory-4.2.1-stock_v2. I booted to Recovery and used adb sideload to install. No errors were reported during the wipe, format and install, but nothing actually got changed. Any ideas?
So my friend was trying to get some stupid game to work on my phone that my phone didn't support, so he tried replacing the build.prop for my Pantech Flex with one for the Galaxy s3. Which needless to say bricked it.
I can start up the phone, and I assume it starts up normally and goes to the lock screen. But everything after the pantech logo is black screen.
Here is what I've tried:
1. Pulling my current build.prop and editing it, then pushing it back with ADB. Pulling it works, but when I push it, nothing seems to happen. It says "Success" but when rebooting the device, my phone is still ****ed up. And when I pull the build.prop back again, it's the one for the Galaxy s3 and not the one I just pushed.
I read that the reason this is happening is because ADB doesn't have root permissions. Not sure if thats true though, as I obviously have rooted my phone.
2. Booting the device into recovery. For a while now, trying to boot into recovery leaves me stuck on the Pantech logo. I think this may be due to me flashing a recovery that wasn't for my device a while back. So I can't get into my recovery to factory reset it.
3. Booting into fastboot mode. The Flex is a strange creature, so there is no standard bootloader apparently so when using "adb reboot bootloader" it reboots into fastboot instead of a bootloader. Meaning on the screen is just white text saying "FAST BOOT mode" and adb disconnects, and fastboot devices sees the device now.
Trouble here is, I have the stock recovery for the Flex. But when I use Fastboot boot recovery.img or Fastboot flash recovery recovery.img or fastboot wipe data or anything in fastboot really, I get a "Not support!!" error. Which I assume means my phone is a piece of **** and can't be used with fastboot.
So now I'm at my wits end and don't know what else to do. I am dead broke and need my phone for work.
Is there anyway I can fix the build.prop or factory reset my phone?
Fukesh said:
So my friend was trying to get some stupid game to work on my phone that my phone didn't support, so he tried replacing the build.prop for my Pantech Flex with one for the Galaxy s3. Which needless to say bricked it.
I can start up the phone, and I assume it starts up normally and goes to the lock screen. But everything after the pantech logo is black screen.
Here is what I've tried:
1. Pulling my current build.prop and editing it, then pushing it back with ADB. Pulling it works, but when I push it, nothing seems to happen. It says "Success" but when rebooting the device, my phone is still ****ed up. And when I pull the build.prop back again, it's the one for the Galaxy s3 and not the one I just pushed.
I read that the reason this is happening is because ADB doesn't have root permissions. Not sure if thats true though, as I obviously have rooted my phone.
2. Booting the device into recovery. For a while now, trying to boot into recovery leaves me stuck on the Pantech logo. I think this may be due to me flashing a recovery that wasn't for my device a while back. So I can't get into my recovery to factory reset it.
3. Booting into fastboot mode. The Flex is a strange creature, so there is no standard bootloader apparently so when using "adb reboot bootloader" it reboots into fastboot instead of a bootloader. Meaning on the screen is just white text saying "FAST BOOT mode" and adb disconnects, and fastboot devices sees the device now.
Trouble here is, I have the stock recovery for the Flex. But when I use Fastboot boot recovery.img or Fastboot flash recovery recovery.img or fastboot wipe data or anything in fastboot really, I get a "Not support!!" error. Which I assume means my phone is a piece of **** and can't be used with fastboot.
So now I'm at my wits end and don't know what else to do. I am dead broke and need my phone for work.
Is there anyway I can fix the build.prop or factory reset my phone?
Click to expand...
Click to collapse
Also, maybe there is a way to set up a VNC server of some sort to use the phone from the computer??
I'm using the Wren (smaller ZW2) and got it stuck in a boot loop when flashing SuperSU/kernel. It is looping while in the "circling dots" animation and is not recognized on my PC. Any help would be nice!
Edit: I got into recovery by swiping from the top right corner to the bottom left in the ASUS splash screen. I'll see what I can do from here.
Edit 2: Would anyone be kind enough to provide a stock recovery IMG/TWRP backup for my specific device? I can't get into system anymore. Booting the device up goes straight into recovery and booting to system via recovery does the same.
Edit 3: A stock device would be helpful. Adb shell, su, dd if=/dev/block/platform/msm_sdcc.1/by-name/ of=/sdcard/stockrecovery.IMG extracts the recovery to the SDCARD.
bump
Still desperate!
Fixed?
After install rom ver 1.2.44 my watch stays forever at boot animation.
It is accessible via adb and i can reboot it into fastboot, but the boot not continue completely.
I tried to install other rom versions, even stock, but there isn't way to repair, all always stays at boot animation.
I need your help.
If somebody have any fix i can do, will be appreciated.
Maybe format the system via fastboot or something like this.
Any idea?
Thx.
jmpcarceles said:
After install rom ver 1.2.44 my watch stays forever at boot animation.
It is accessible via adb and i can reboot it into fastboot, but the boot not continue completely.
I tried to install other rom versions, even stock, but there isn't way to repair, all always stays at boot animation.
I need your help.
If somebody have any fix i can do, will be appreciated.
Maybe format the system via fastboot or something like this.
Any idea?
Thx.
Click to expand...
Click to collapse
SOLVED.
I used this installer as my last chance and then all went ok.
https://www.youtube.com/watch?v=z5M3OiAshz4
Thanks to @Alain.