Hello everyone so this week I decided to root, flash custom recovery and of course flash a custom ROM in this case KK-FIRE-NEXUS-ROM. Anyway the phone booted it self into recovery and after I rebooted back to the OS and seeing the amazon boot animation it went black; it did not let me turn it on, not sign of power, I plugged the power cord with no signs of it charging then I constantly pressed key combination to boot into fastboot or recovery and it happened! It booted into fastboot and let my go into custom recovery. To make this story short and hopefully this helps others to not make mistakes; I tried to restore a back up of the stock ROM but it did not work. I tried to flash the stock ROM .bin format but it also did not work. I did all of this using my linux machine then I found this options in the recovery to select different ROMS within the recovery so you can boot into them well somehow it was changed to ROM(1) so I selected STOCK, rebooted and that was it. I got my phone working without having to flash anything! or messing up anything!
I hope this helps somebody or stops them from flashing something that will kill their phones!
Related
I had installed 'blackhawks next kernel' for dual-booting.
I had CM11 on partition 1 and Stock Samsung on Partition 2.
I decided I want to simply revert to a single partition with the stock Samsung.
I booted into partition 1.
I used Phils to install 'GT3_MH2_STOCK_Kernel_SM-t310_Tab3.zip'
When the machine rebooted, it jumped into the Cyanogen Mod boot sequence, and just loops.
If I try to turn the machine off to boot into recovery, the Tab doesn't shut down - it just reboots.
Trying to 'time' getting into recovery hasn't netted me much luck with about 20 tries of nailing the 10-second 'hold power button then nail volume up.'
Any suggestions?
Well, I got further.
I found that if I plugged the USB cable into the device into my computer, then pressed and held the power, when it would 'auto-reboot' to the battery icon screen.
Once at the battery icon screen, I unplugged the USB cable and the tablet completely turned off.
From there, I was able to get back to Philz.
So, I guess my new question is: How do I correctly install any kernel other than blackhawks, which would allow me to flash back to a stock ROM?
curiousmike said:
I had installed 'blackhawks next kernel' for dual-booting.
I had CM11 on partition 1 and Stock Samsung on Partition 2.
I decided I want to simply revert to a single partition with the stock Samsung.
I booted into partition 1.
I used Phils to install 'GT3_MH2_STOCK_Kernel_SM-t310_Tab3.zip'
When the machine rebooted, it jumped into the Cyanogen Mod boot sequence, and just loops.
If I try to turn the machine off to boot into recovery, the Tab doesn't shut down - it just reboots.
Trying to 'time' getting into recovery hasn't netted me much luck with about 20 tries of nailing the 10-second 'hold power button then nail volume up.'
Any suggestions?
Click to expand...
Click to collapse
Do a clean install of stock ROM by going into download mode. Power + Volume down + Home button.
curiousmike said:
Well, I got further.
I found that if I plugged the USB cable into the device into my computer, then pressed and held the power, when it would 'auto-reboot' to the battery icon screen.
Once at the battery icon screen, I unplugged the USB cable and the tablet completely turned off.
From there, I was able to get back to Philz.
So, I guess my new question is: How do I correctly install any kernel other than blackhawks, which would allow me to flash back to a stock ROM?
Click to expand...
Click to collapse
The kernel you installed will only work with stock roms. You still had CM installed as primary rom and attempted to use a stock kernel with it. That's why it wouldn't boot.
You have a couple options now for reverting to stock.
1. Odin - Download and flash a full stock firmware; then boot into recovery and do a factory reset. There are many guides for doing this with Odin. Firmware is available at sammobile.com.
2. Recovery - Download a stock-based rom and flash it in recovery. Make sure you do a full wipe in recovery before flashing. The rom will have a kernel also, so there is no need to flash another one.
I cannot use the hardware buttons any longer to even get into fastboot mode. I tried to insert a new TWRP theme, named it ui.zip, place it in the theme folder, then rebooted the phone and now it will not even go into recovery, fastboot mode, nor turn on. Anybody have any suggestions on how to get through to the recovery. I guess I locked up the recovery, and can no longer boot my phone to even be able to delete that ui.zip file from the theme folder under TWRP.
OK, now I managed to get it into fastboot mode. But that is it.
Can I extract a file from the phone in fastboot mode?
Thanks,
chevy383surfing
Well, I finally figured it out. I'll add an explanation on this whole deal after I get off work. Just in case anybody else runs into the same problem, maybe my little routine will help someone else.
chevy383surfing said:
I cannot use the hardware buttons any longer to even get into fastboot mode. I tried to insert a new TWRP theme, named it ui.zip, place it in the theme folder, then rebooted the phone and now it will not even go into recovery, fastboot mode, nor turn on. Anybody have any suggestions on how to get through to the recovery. I guess I locked up the recovery, and can no longer boot my phone to even be able to delete that ui.zip file from the theme folder under TWRP.
OK, now I managed to get it into fastboot mode. But that is it.
Can I extract a file from the phone in fastboot mode?
Thanks,
chevy383surfing
Well, I finally figured it out. I'll add an explanation on this whole deal after I get off work. Just in case anybody else runs into the same problem, maybe my little routine will help someone else.
Click to expand...
Click to collapse
Next time you loop, vol up and power for 10 seconds with phone Unplugged, then vol down and power to go to boot loader
If for some reason it doesn't restart put the phone close to a bright light
Similar problem
Hi. I am on a Kindle Fire HD 7 and just got cynogeanmod 12. I was going through settings when device got laggy. And somehow the device thought I wanted factory reset so thats what it did. My Kindle Rebooted and now I get a screen that says "teamwin" and every 2 secs. the screen flashes. None of the tips using buttons worked. It can only turn on and off. I need assistance in finding a way to get this back to stock(from there I can re-root and do the process again to get back cynogeanmod).
Thanks,
aputtapa000
aputtapa000 said:
Hi. I am on a Kindle Fire HD 7 and just got cynogeanmod 12. I was going through settings when device got laggy. And somehow the device thought I wanted factory reset so thats what it did. My Kindle Rebooted and now I get a screen that says "teamwin" and every 2 secs. the screen flashes. None of the tips using buttons worked. It can only turn on and off. I need assistance in finding a way to get this back to stock(from there I can re-root and do the process again to get back cynogeanmod).
Thanks,
aputtapa000
Click to expand...
Click to collapse
First, this is the M8 forum, not the Kindle forum. However, I actually can help you with that.
Most stock recoveries seem to have a problem with doing factory resets. Flash the stock recovery for your device, let it perform the factory reset, boot back into the OS (to make sure it worked), then reflash your custom recovery.
jshamlet said:
First, this is the M8 forum, not the Kindle forum. However, I actually can help you with that.
Most stock recoveries seem to have a problem with doing factory resets. Flash the stock recovery for your device, let it perform the factory reset, boot back into the OS (to make sure it worked), then reflash your custom recovery.
Click to expand...
Click to collapse
Tank you for this quick reply :good: . I will try to get back into my stock recovery but if it is on my device, how will I access this on my computer and force flash it on my tablet. I only need help making the tablet responsive/workable. Once this is done I should be able to figure out the rest.
Thanks
I'm not entirely sure if this is where I should post this, but I am having a problem with my Fire Phone and I really hope you guys can help.
So, story time. I was thinking that I wanted to install a new ROM on my phone just to try some new things. I decided on the SlimKat android 4.4.x ROM and I installed it with GAPPS using SafeStrap 4.01. However, the new ROM was not working correctly so I thought I installed it wrong. So, I read up a little bit more on this and it said that I had to do a factory restore beforehand so I did it with high hopes that it would work. However, it sill did not work. What happens is that I power it on, it asks whether I want to go into SafeStrap or not, it continues if I say no, and they it starts with SlimKat. After about 20 seconds, it stops the starting animation and starts its boot loop.
Since I factory restore it, I had no back ups or and ROMs that I could install on my device. I try to plug it into my computer but it is unrecognizable even if it is the recovery. I also tried going into download mode, doing it multiple ways, but with not luck. It still goes into the boot loop. I factory reset it multiple times but still with no luck. Within SafeStrap, I tried to wipe it, but it is unable to wipe the Dalvik Cache or Data. If there is any way that I can move the stock ROM onto my phone, it would solve all my problems. If any of you have any ideas, please let me know.
I having same problem. Unable to go to recovery mode in normal way, but I could managed to go to recovery by attaching it to computer with usb cable and keeping pressing power + Vol up key for few seconds.
Then I tried Factory restore, Adb Sideload original file downloaded from amazon, but the problem still not solved.
My phone is keep flashing amazon logo in loop.
If any one have idea please help.
I just upgraded my rooted and bootloader unlocked Robin to Nougat last night by installing the official upgrade files from the Razer Community forum. I've tried installing TWRP several times through fastboot, and each time I can get the phone into recovery, but the phone will never boot into the system. It hangs on the black "Nextbit by Robin" screen, and never goes past it. If I turn off the phone by holding down the power and volume down buttons, and then turn it back on, it still won't get past that screen. I can always get into TWRP, though, but no matter what I do, the phone won't boot. I've been using TWRP 3.1.0. Is there a different version that's required for Nougat?
Saaber said:
I just upgraded my rooted and bootloader unlocked Robin to Nougat last night by installing the official upgrade files from the Razer Community forum. I've tried installing TWRP several times through fastboot, and each time I can get the phone into recovery, but the phone will never boot into the system. It hangs on the black "Nextbit by Robin" screen, and never goes past it. If I turn off the phone by holding down the power and volume down buttons, and then turn it back on, it still won't get past that screen. I can always get into TWRP, though, but no matter what I do, the phone won't boot. I've been using TWRP 3.1.0. Is there a different version that's required for Nougat?
Click to expand...
Click to collapse
My guess is you messed up the boot.img, or worse you corrupted some partition. If it's the boot.img, go get the latest factory image, unzip it, and move the file 'boot.Img' onto where your adb and fastboot files are located. Then go into fastboot on your Robin, and run this command on your PC:
Fastboot flash boot boot.img
If you corrupted something, you basically need to go into fastboot and use the flash-all.bat in the already unzipped Robin_nougat_88 folder to bring your phone back bone stock.
Hope that helped
Had this issue with my phone at first, but eventually just fixed it anyway by flashing the decrypted boot.img.
I ended up fixing it the same way you did. No matter how many times I took it back to stock by flashing the files in the Robin_nougat_88 folder and then flashing TWRP, no matter which version of TWRP I used, it would never boot. I finally flashed TWRP, then booted back into recovery, wiped the phone, loaded and flashed the decrypted boot image and SuperSU, and then the phone booted fine. I should have just done that in the first place since it was always my intention to unencrpyt it and rooted it again, anyway.
My telephone keeps booting to fastboot after trying to update TWRP.
I am trying to restore the original ROM (apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea) and I can get the rom installed through fastboot but the phone enters a boot loop cycle. It starts up, vibrates shortly then reboots.
If i press volume up it goes into the original recovery menu. I have tried clearing everything and even entering safe mode but the phone will not boot.
Am i screwed?
Thanks in advance.
I installed the Pixel Experience recovery and side-loaded the zip and at least have a working OS.
I must be doing something wrong with the stock mi10t
Now i sided the miui zip and its working agian. I think i have misunderstood the procedure. I thought you only need to install the rom with flashboot and that was it.