I flashed a modified boot.img (found here: http://forum.xda-developers.com/amazon-fire/general/alternative-launcher-t3239540), rebooted and found the "Installing the latest software" screen. The orange bar got to the end, I waited a good few minutes, and.... ...nothing.
I force-power-downed the tablet (longpress on power), flashed the original boot.img, and still had the same problem... Kept trying, no help.
Any ideas on what I could do?
Related
Hey guys, my phone got totally stuck on a Samsung logo (neverending loop).
Yesterday I let my bro play an Angry Birds on my phone. After a while I took my phone back and to my surprise it wasn't responding. Mobile was turned on (connected to the charger) but all I could see was a black screen. I tried restarting my phone by removing battery but it didn't help at all. I got stuck at Cyanogen Mod logo everytime. Since I haven't updated my firmware in a while I decided to intstall the newest version of CM (KitKat 4.4.4 from novafusion.pl) using Odin app. After a successful installation my phone still didn't boot up, I was getting stuck on a blue CM logo. After this I wanted to wipe my cache/dalvik cache but I wasn't able to get into recovery mode (getting stuck on a TeamWin screen). Reinstalling TWRP and installing ClockWork recovery didn't have any effect. I wiped my phone using .tar file found on this forums, tried reinstalling my ROM recovery many times, tried installing param file (don't even know what's that) and resetting three button combination using Benzonat0r's mod. None of these things seemed to have any impact. I'm still not able to get into recovery neither boot my phone up - Samsung logo bootloop. What am I supposed to do to unbrick my phone?
On a side note my knowledge about Android phones is tiny so please consider this. Also forgive me my poor grammar, not a native English speaker here.
Guskax said:
Hey guys, my phone got totally stuck on a Samsung logo (neverending loop).
Yesterday I let my bro play an Angry Birds on my phone. After a while I took my phone back and to my surprise it wasn't responding. Mobile was turned on (connected to the charger) but all I could see was a black screen. I tried restarting my phone by removing battery but it didn't help at all. I got stuck at Cyanogen Mod logo everytime. Since I haven't updated my firmware in a while I decided to intstall the newest version of CM (KitKat 4.4.4 from novafusion.pl) using Odin app. After a successful installation my phone still didn't boot up, I was getting stuck on a blue CM logo. After this I wanted to wipe my cache/dalvik cache but I wasn't able to get into recovery mode (getting stuck on a TeamWin screen). Reinstalling TWRP and installing ClockWork recovery didn't have any effect. I wiped my phone using .tar file found on this forums, tried reinstalling my ROM recovery many times, tried installing param file (don't even know what's that) and resetting three button combination using Benzonat0r's mod. None of these things seemed to have any impact. I'm still not able to get into recovery neither boot my phone up - Samsung logo bootloop. What am I supposed to do to unbrick my phone?
On a side note my knowledge about Android phones is tiny so please consider this. Also forgive me my poor grammar, not a native English speaker here.
Click to expand...
Click to collapse
Download This rom "I8190 серв. укр.rar" from here
Unpack .rar and open Odin.
Select the goldenxx.pit to [PIT]
Select CODE_I8190XXAMA2_809600_REV00_user_low_ship.tar.md 5 to [PDA]
Select CSC_QXE_I8190QXEAMA1_20130109.163004_REV00_user_lo w_ship.tar.md5 to [CSC]
Put your phone in download-mode and connect it to computer.
Hit [Start] when device is detected by Odin.
You will end up with a "La'Fleur" branded phone, but no worries!
Just go to download mode again and flash a custom recovery and after that a ROM of your choice.
The three button combo will still work!!
This is not my work, give my friend @tyson a thanks for that!
I tried installing stock recovery and ROM. After completed installation I finally managed to pass Samsung screen. I got to the something like Android installation screen and my phone suddenly shut down. Now it's totally bricked, I can't turn it on nor get into the download mode. Charging progress doesn't show up while phone is plugged in neither. Any help?
moonryder said:
Download This rom "I8190 серв. укр.rar" from
Unpack .rar and open Odin.
Select the goldenxx.pit to [PIT]
Select CODE_I8190XXAMA2_809600_REV00_user_low_ship.tar.md 5 to [PDA]
Select CSC_QXE_I8190QXEAMA1_20130109.163004_REV00_user_lo w_ship.tar.md5 to [CSC]
Put your phone in download-mode and connect it to computer.
Hit [Start] when device is detected by Odin.
You will end up with a "La'Fleur" branded phone, but no worries!
Just go to download mode again and flash a custom recovery and after that a ROM of your choice.
The three button combo will still work!!
This is not my work, give my friend @tyson a thanks for that!
Click to expand...
Click to collapse
Hey dude, I wish I saw your reply earlier. If my phone wasn't bricked now I'd give it a shot.
Hi guys, I'll try to explain my problem:
My Milestone has been running the rom "cm-7.2.4e-umts_sholes" since two years without issues... until a few days ago: aleatory restarts and freezes. Yesterday, I turned it on and was stuck on "M" logo. Several restarts later, it shows the "2ndBoot - Kernel Restart in progress" logo and nothing else.
I tried to reflash the rom and encountered some issues:
Bootloader 90.73, I flashed the vulnerable recovery "vulnerable_recovery_only_RAMDLD90_78.sbf" and enter in recovery stock. When I tried to run the "OpenRecovery_2ndbootOR_v1_2" the OR doesn't start at all. Black screen, restarts and recovery stock again. Only the "OpenRecovery_v1_46_SHOLS_inkl_ext_mmcfix_parted_update" does the trick and starts the OR with red letters. After all the obligatory wipes, applied update from "cm-7.2.4e-umts_sholes" and then reboot system. And the same "M" stuck or "2ndboot" stuck screen. I tried wipes again, but no results.
So, I tried to go back to an earlier version and installed "SHLA_U2_02.02.0_USASHLSPERARLA017.0R_USASHLSPERARLAT_P037_A015_HWp2a_1FF" with RDSLite. It boots up Android BUT the touchscreen not works at all, even with several reboots. Tried to reflash Cyanogenmod from here, but the same issues above listed appears.
I really going crazy with this... Did I make some mistake at any point? Must I reflash the bootloader 90.73 if I found it? (besides all the webs containing all the .sbf's and bootloaders appears to be offline by now).
Any solution/advice you can give me please?
Thanks in advance and sorry my english, isn't my first language.
Hi everyone.
I've android 6 stock (xt1068), and today i woke up and it doesn't work
I try to install the twrp and then to flash rom, ecc, but after that i install the twrp succesfully, when i go in the recovery i see that there is no twrp but the main stock recovery. This thing basically appens with everything that i install/wipe, infact the bootloader tells me that my action worked, but it didn't.
Another thing is that if i let my phone boot up, after the boot animation it tells me 'Starting Android', then this text go out, and for a second the boot animation appears again, after that all the screen goes black. (The phone is not closed, but it is showing black in the screen, i think you got it)
Thank you
XT1092 flashing (as in on screen flashing) recovery "no command" screen. Bricked?
Apparently I did something stupid. I had 5.1 which didn't OTA on its own to 6.0. So I thought it maybe had something to do with a past root i had and TWRP recovery. As solution I went and flashed a stock 5.1 rom in fastboot, which worked fine. Still no OTA though, and adb sideloading gave a status 7 error. Then I fastbooted the 6.0 stock rom, but that wouldn't boot (phone would hang in the white "unlocked bootloader" warning screen. I re-flashed 5.1 in fastboot.
Probably not a smart move, cause now I'm stuck in a bootloop to recovery mode where it's flashing the "no command" recovery screen for a fraction of a second, then black screen for 4 seconds, repeating over and over. I can trigger some orange log error by pressing VOL*UP like when you go to recovery mode, but it disappears in the bootloop. (it says qe 1/1 though, which suggests its rooted I read somewhere). So I can't do anything with it anymore. I read tons of threads here of which I found 2 with a similar problem:
http://forum.xda-developers.com/moto-x-2014/help/xt1092-flashing-command-boot-attempt-to-t3259287
http://forum.xda-developers.com/moto-x-2014/help/possibly-soft-bricked-moto-x-flashing-t3195103
It's the same problem I have now, and one of them says that "with some luck" he got into fastboot, but doesn't describe how.
Googling "flashing" related to recovery and/or "no command screen" in this context does'nt yield much result unfortunately.
For the love of god, I can't get it into fastboot mode anymore to do something/anything about it. I pressed, hold, tapped POWER and VOL*UP on countless ways, and it does a "deeper" reboot with appearance of the white unlocked bootloader screen, but it just keeps bootlooping.
How can I fix this? Did I brick it by fastboot flashing 6.0 and then fastboot flashing 5.1? Is it hard bricked and useless?
What do I have to flash when I manage to get in fastboot?
OK, I fixed it. Discovered it when the battery was drained. When the phone is OFF, holding POWER+VOL*UP+VOL*DOWN for 5 seconds and then releasing triggers the fastboot. Problem then is that you can't flash anything cause the battery is nerely depleted. So I let it charge in the bootloop for a bit and I found out I can hard reboot and get into fastboot by holding POWER+VOL*UP+VOL*DOWN for about 10 seconds and then releasing it. It probably turns off and then triggers the fastboot/bootloader mode.
Afraid of bricking it with OTA as I've downgraded to 5.1 from a (non-functioning) 6.0 I've manually flashed a 6.0 stock ROM in fastboot using this guide including mfastboot. So no sideloading or anything. Now it properly boots and I've got a stock 6.0.
Hopefully this helps someone in the future.
I had TWRP already and flashed the V8.5 ROM from https://forum.xda-developers.com/r1-hd/development/modified-8-3-stock-rom-t3602672. Appeared to be successful since it gave no errors but now the device has been stuck on the splash screen for over 45 mins now. When I try to boot into recovery, it just displays the android on its back with a red exclamation symbol. Is there a way to fix/revert this?
update: did factory reset, i think it removed my bootloader though. guessing it's not possible get that back?
update2: never mind, managed to get twrp again