I loaded the Slimkat ROM using flash fire. Everything seemed ok until the final step where the os loads. It is stuck at the Slimkat spinning. I tired going to recovery but it does not work. I can get to FAST BOOT mode but other then displaying the product version nor reboot nothing else works I get and unknown command. If i try to flash through fast boot it says the system is locked.
Given I can get into Fastboot i am hoping there is something that can be done to fix. Any ideas?
Related
Well I was getting the itch to flash a new ROM as I was running CM11. Thought it was a good idea to download one through GooManager.
Anyways, I flashed the ROM and GApps for 4.4 and now all it does it boot to the orange Kindle logo then a white line a few pixels thick appears down the left side.
I can't get it to boot into recovery holding any of the buttons but it will turn off and "on" with the power button. Any ideas?
Wischmaster said:
Well I was getting the itch to flash a new ROM as I was running CM11. Thought it was a good idea to download one through GooManager.
Anyways, I flashed the ROM and GApps for 4.4 and now all it does it boot to the orange Kindle logo then a white line a few pixels thick appears down the left side.
I can't get it to boot into recovery holding any of the buttons but it will turn off and "on" with the power button. Any ideas?
Click to expand...
Click to collapse
Sounds like you will have to restore from fastboot mode, hopefully your pc will still detect it as a jem device for a very breif moment when it turns on on the orange logo. If it can you can just run
Code:
fastboot -i 0x1949 getvar product
and then plug the device in while its off and reflash with kindle fire first aid. Might be a pain to get the drivers to install for fastboot though because it doesnt show up for very long. If you don't have drivers installed and cant get them to isntall in time before it disconnects a Ubuntu live cd/usb is a good way to go, it doesnt have to install drivers because they are built into the kernel so it works instantly.
Okay, I was able to get it into Fastboot mode. However I'm at a loss of how to flash a recovery and/or ROM through Fastboot.
Wischmaster said:
Okay, I was able to get it into Fastboot mode. However I'm at a loss of how to flash a recovery and/or ROM through Fastboot.
Click to expand...
Click to collapse
You mist flash stock files first. Your device has to be functioning before recovery and ROM and that good stuff
Sent from my Kindle Fire HD running AOKP
Thanks guys! I eventually figured it out.
The whole going back to stock was stopping the process, got it up and running again.
Whew!
My friend's phone somehow got into a reboot cycle. It loads up, launcher starts, notifications start working. Then there is a nullpointer and a core service that is failing to start then it reboots.
So as a solution I thought try wiping data/cache. When booting the bootloader it was already unlocked - not sure if we did that a while ago or what. So going into recovery, trying the data wipe, it says success and then when I start the phone it is the same, no data is gone, apps are there, reboot problem continues.
So next step, try flashing the os. I downloaded the most recent yakju build, jwr66y. My bootloader version is PRIMELA03 and the build comes with MD04, so I try:
fastboot flash bootloader <bootloader_img>
And it reports success, everything looks fine. So I reboot the bootloader and it says BOOTLOADER VERSION - PRIMELA03.
Try fastboot oem lock, says locked. Reboot, UNLOCKED. Tried flashing the bootloader and the main img with and without restarting but always get the error:
Device version-bootloader is 'PRIMELA03'.
Update requires 'PRIMEMD04'.
when trying to flash the stock rom.
I also can't boot the stock image via 'fastboot boot'. It looks successful up until it says booting and goes to the Google screen with the padlock at the bottom and just hangs.
If I try using adb sideload to push the stock update, it says verifying, then aborts.
I also tried flashing the recovery with a cwm recovery but the same problem - it says writing, OKAY, no error message, everything looks fine, then boot recovery and it's the stock recovery.
What it looks like to me is that the bootloader and possibly the entire system is failing to write to the system flash but for some reason thinks it's succeeding. How is this possible? Is the flash dead? Am I missing something basic? I haven't rooted a phone in a couple years so it's quite possible I'm just missing a step.
Thanks in advance for any advice.
I just tried flashing an older stock (imm76i), starting by flashing the radio, but again the radio flash looks successful but the kernel won't flash because it complains about an out of date baseband and sure enough, the old one is still the one it's reporting, not the one just flashed.
tried fastboot erase system and fastboot erase recovery. Both report success but recovery boots as normal and system boots as normal (still in a reboot cycle).
I should also mention, that after the system boots, there is enough time to uninstall an app. It says successfully uninstalled, but after a reboot, the app is still there (this was the first attempt to stop the reboot cycle as a custom keyboard app was suspected). But again, the changes to flash seem to not be sticking.
Hi,
Have you resolved the problem? I'm in the same situation and I don't know what to do to stop the continuous reboot. I've already tried to flash a stock 4.3 factory image, erase the user data or only unlock the bootloader but nothing works. I'm running Android 4.3 stock without root and my bootloader is locked.
thank you in advance.
So today for the first time tried to mess around with my phone, but i failed miserably. I rooted my phone with Kingo ROOT, and then followed the instructions on the wiki page, but at step 4 things got messed up, my phone got stuck at the SONY logo with the blue light turned on and it wouldnt do anything, so i removed the battery, now it boots up at the cyanogen recovery but i cant do anything from there , everytime i close the device when i boot it , it boots to this menu. I have tried everything to get it back to normal but nothing seems to work. I will tell exactly what i did in order to reach in this state. I downloade the nicki nightly cm, and moved the boot.img to my platform-tools folder in which i run on command prompt the following commands :
fastboot flash boot boot.img
fastboot reboot
After that my phone gets stuck and i can only access Cyanogen Recovery, does anyone have any idea what to do?? :crying: :crying:
Have you tried flashing the rom using cyanogen recovery?
Htc One M8... was running marshmallow sense rom with elementalx kernel.
- S-off
- running Bell marshmallow firmware
- Twrp recovery latest one.
Randomly the phone rebooted while I was using it last night and after that got stuck in a bootloop.
Now it seems to boot up but it goes to a screen where it says "please enter password to decrypt phone" ... I don't have a password so then it tells me to factory wipe the phone.
I can get into Hboot fine... the issue I am having is for some reason along with the rom, the recovery has crashed too... I have tried reflashing a new twrp or even the stock recovery but the recovery just will not boot. Regardless of me flashing the stock recovery... when I try to boot into it, it shows that I am booting into twrp (which makes me assume that the recovery isnt really being flashed)
I tried the RUU method but when I do rebootRUU from fastboot it just boots my phone and its stuck back in the bootloop and doesnt go to Black HTC screen :S.
Kind of stuck... I dont have a windows device otherwise I would try the exe method and lost on how to recover the device. Feels like maybe the flash memory crashed... but its so random
If anyone can help, would be greatly appreciated.
Thanks
so just tried to run a gpe ruu as well... it did the first step of flashing the bootloader and just rebooted to the normal htc bootloader :S
seems like whatever I do nothing is being flashed to any partition... i found the adb command that fixes encryption for aosp roms... but I cannot run adb because I cant boot into recovery :S
Hi. I've got a jem, which was previously running CM11, which I finally got around to trying to update. In the process, I ended up with AICP installed. It won't fully boot; it hangs at the logo, but is responsive using adb (shell, logcat, etc).
Since their release notes mention a new recovery requirement, I tried to upgrade my recovery and it failed. Now, I can boot the AICP rom (which hangs at the logo), but all efforts to get into either the recovery or fastboot fail, and aicp still isn't booting completely (i let it sit overnight, and the logo was still spinning in the morning.
I'm hoping that since adb works, the tablet isn't a brick.
Can anyone suggest a path out?
thanks
bricklayer16 said:
Hi. I've got a jem, which was previously running CM11, which I finally got around to trying to update. In the process, I ended up with AICP installed. It won't fully boot; it hangs at the logo, but is responsive using adb (shell, logcat, etc).
Since their release notes mention a new recovery requirement, I tried to upgrade my recovery and it failed. Now, I can boot the AICP rom (which hangs at the logo), but all efforts to get into either the recovery or fastboot fail, and aicp still isn't booting completely (i let it sit overnight, and the logo was still spinning in the morning.
I'm hoping that since adb works, the tablet isn't a brick.
Can anyone suggest a path out?
thanks
Click to expand...
Click to collapse
To self-reply, for some reason, adb reboot bootloader wouldn't work, but adb reboot recovery got me into fastboot. I've managed to get things repaired.