Related
Hello, I have a Kindle Fire HD 7" running the downgraded 7.2.3 from KFFA. Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo.
My screen doesn't do the "White haze" that others have mentioned.
Still boots into recovery allowing for wipes + installs.
I have reverted back to 100% stock then made my way back to stock + TWRP three times now, and have looked rather extensively through any threads even somewhat relative to my own problem.
I've been using the Factory fastboot cable to get into fastboot if that makes any difference.
I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before.
ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)
Have tried my cable from my Note 2, Captivate, Epic 4G Touch, and stock KFHD 7" cable as well as the factory fastboot cable.
Kinda stuck, have gone round like this for about 4 hours + now and I must say, the KFHD 7" has been the biggest pain out of any of my Androids by far xD Great tab though.
Any help would be much appreciated. I could always just run stock, but, I'd really like to have CM 4.3 or 4.4 based on my device.
Thanks!
If I left out anything, please, let me know and I will respond ASAP.
veladem said:
Any help would be much appreciated. I could always just run stock, but, I'd really like to have CM 4.3 or 4.4 based on my device.
Thanks!
Click to expand...
Click to collapse
You need to enter TWRP and sideload a ROM. Use this tutorial here http://forum.xda-developers.com/showthread.php?t=2459498
LinearEquation said:
You need to enter TWRP and sideload a ROM. Use this tutorial here http://forum.xda-developers.com/showthread.php?t=2459498
Click to expand...
Click to collapse
Not to be an arse but I don't know how that is going to help 0.o?
My recovery works just fine . . .
veladem said:
Not to be an arse but I don't know how that is going to help 0.o?
My recovery works just fine . . .
Click to expand...
Click to collapse
You have no OS and that's why it won't boot past TWRP. Go into TWRP and adb sideload a ROM onto TWRP and flash it and boot into system. You should probably read a bit before just posting. The link answered your question.
LinearEquation said:
You have no OS and that's why it won't boot past TWRP. Go into TWRP and adb sideload a ROM onto TWRP and flash it and boot into system. You should probably read a bit before just posting. The link answered your question.
Click to expand...
Click to collapse
If I restore my stock rooted OS via TWRP it boots up just fine . . .
The problem I have is after flashing any ROM's I can't get past the blue logo.
But I'll try what you are saying just for kicks.
veladem said:
If I restore my stock rooted OS via TWRP it boots up just fine . . .
The problem I have is after flashing any ROM's I can't get past the blue logo.
But I'll try what you are saying just for kicks.
Click to expand...
Click to collapse
You need to check the zip and make sure it did not get corrupted during the download. Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror. Make sure it is the ROM for your year and model Kindle Fire HD. You also need to update your TWRP to 2.6.3.1 right away, http://forum.xda-developers.com/showthread.php?t=2128848 Before you flash, factory "swipe" then flash ROM then wipe Dalvik/CACHE then boot into OS. Just drag and drop ROM onto internal SD card before booting into TWRP.
LinearEquation said:
You never said you could access an OS. You simply said you could not get past TWRP. You need to check the zip and make sure it did not get corrupted during the download. Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror. Make sure it is the ROM for your year and model Kindle Fire HD. You also need to update your TWRP to 2.6.3.1 right away, http://forum.xda-developers.com/showthread.php?t=2128848 Before you flash, factory "swipe" then flash ROM then wipe Dalvik/CACHE then boot into OS.
Click to expand...
Click to collapse
Oh boy lol, let me just correct everywhere you went wrong, cause I've tried to be nice, but I can't let you get away with not even reading the OP.
"You never said you could access an OS." ---> "I could always just run stock"
"You simply said you could not get past TWRP" ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo." (PS: Being stuck at the "Blue logo" is much different then not being able to boot and being booted into TWRP.)
"You need to check the zip and make sure it did not get corrupted during the download." ---> "I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before."
"Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror." ---> That was where I downloaded from the second+ time I downloaded the ROM.
"Make sure it is the ROM for your year and model Kindle Fire HD." ---> "ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)"
"You also need to update your TWRP to 2.6.3.1 right away," ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP"
So, I just copied and pasted all that from you post, and my OP.
So, let me quote you again from another post you made in my thread.
"You should probably read a bit before just posting." READ THE OP BEFORE TRYING TO HELP MIGHT BE A GOOD IDEA!!! x'D
Thanks for attempting to help though, much appreciated.
veladem said:
Oh boy lol, let me just correct everywhere you went wrong, cause I've tried to be nice, but I can't let you get away with not even reading the OP.
"You never said you could access an OS." ---> "I could always just run stock"
"You simply said you could not get past TWRP" ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP but for whatever reason I can't seem to install a ROM that will boot past the "Blue" Logo." (PS: Being stuck at the "Blue logo" is much different then not being able to boot and being booted into TWRP.)
"You need to check the zip and make sure it did not get corrupted during the download." ---> "I have downloaded the GAPPs and ROM twice, and I have a very stable connection that hasn't given me issues before."
"Goo.img is updating their servers and downloads can be corrupted. Try downloading from the crackflasher mirror." ---> That was where I downloaded from the second+ time I downloaded the ROM.
"Make sure it is the ROM for your year and model Kindle Fire HD." ---> "ROM is the same as from Hash's thread for TWRP + 2nd Bootloader. (cm-10.2-20131115-UNOFFICIAL-tate)"
"You also need to update your TWRP to 2.6.3.1 right away," ---> "Then I used Hash's TWRP 2.6.3.1 + 2nd Bootloader thread to get Stock with TWRP"
So, I just copied and pasted all that from you post, and my OP.
So, let me quote you again from another post you made in my thread.
"You should probably read a bit before just posting." READ THE OP BEFORE TRYING TO HELP MIGHT BE A GOOD IDEA!!! x'D
Thanks for attempting to help though, much appreciated.
Click to expand...
Click to collapse
You are screwing up some where. Your doing something wrong. N00bs coming in here and don't read and try and complain about the information posted. Every question you have has been answered a dozen times. Try Google or TMFSE. Quit being lazy.
LinearEquation said:
You are screwing up some where. Your doing something wrong. N00bs coming in here and don't read and try and complain about the information posted. Every question you have has been answered a dozen times. Try Google or TMFSE. Quit being lazy.
Click to expand...
Click to collapse
Well, now you're just flat out being an ass. I've been rooting my phone ever since my G1, definitely not a noob, and I wouldn't have asked for help if I didn't need it and if I hadn't already searched a ton.
I've been here longer then you, just an FYI. Also, your grammar is horrid.
I really wish trolls like you weren't allowed on XDA but man, can't control you guys.
PS: Don't get mad and call me a noob just cause you can't read x'D
EDIT: Linear has been added to my ignore list so if he does reply I don't have an urge to argue with him some more.
Biggest problem here Linear is that you really, really need to learn how to read an OP before posting help.
Thanks!
veladem said:
Well, now you're just flat out being an ass. I've been rooting my phone ever since my G1, definitely not a noob, and I wouldn't have asked for help if I didn't need it and if I hadn't already searched a ton.
I've been here longer then you, just an FYI. Also, your grammar is horrid.
I really wish trolls like you weren't allowed on XDA but man, can't control you guys.
PS: Don't get mad and call me a noob just cause you can't read x'D
EDIT: Linear has been added to my ignore list so if he does reply I don't have an urge to argue with him some more.
Biggest problem here Linear is that you really, really need to learn how to read an OP before posting help.
Thanks!
Click to expand...
Click to collapse
Like I said, do some searching first and you'll get there if you implement some reading skills. For being here so long, you still act like a n00b.
As to the troll comment. I have received 169 thanks in a few short months and you have 17 yet you have been on here here almost 3 years. Way to give back to the community, take a bow.
LinearEquation said:
Like I said, do some searching first and you'll get there if you implement some reading skills. For being here so long, you still act like a n00b.
As to the troll comment. I have received 169 thanks in a few short months and you have 17 yet you have been on here here almost 3 years. Way to give back to the community, take a bow.
Click to expand...
Click to collapse
I give back to the community by offering free Android and iPhone modding in my area, and free support via text and email.
Plus I make sure to tell them to check out the Dev's thread or website and to consider donating to the people who make the magic happen.
The only service I make people pay for is electronic repairs which is a flat rate of $20 + customer buys the parts.
So I think I give back to the community at least a little seeing as I have at the least 20+ people a month asking for help cause some idiot installed a unstable ROM on their phone and 4G vanished or other problems.
By the way, since we are laying our d*cks on the table, might I add that boasting about how many "Likes" you have or "Thanks" isn't something to be proud of, you earned them yes, but don't shove that in other peoples faces, that's just childish.
Thanks again for trying to help.
OK before this turns into a flame war, lemme ask something. Did you factory reset and wipe the system partition before flashing the cm ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK before this turns into a flame war, lemme ask something. Did you factory reset and wipe the system partition before flashing the cm ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I did try that yes.
Thank you for helping btw.
It's water under the bridge for me. Would be funny if that were the case though because asking him if he swiped was one of my initial responses to him.
Sent from Nexus 7 flo running SinLess ROM 4.2.2 using xda app-developers app
OK I'm going to reiterate some of what linear said, but in a different way, did you checknthe md5sum of the ROM before you flashed it to make sure it matched up with the one given?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
OK I'm going to reiterate some of what linear said, but in a different way, did you checknthe md5sum of the ROM before you flashed it to make sure it matched up with the one given?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yes sir I did.
OK now for the stupid question, I saw you said it runs a 7.x.x os, just wanted to verify that you are sure of this. I know that kinda a noob question but I have to ask to double check things. Also have you tried flashing cm 11?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Reiterate
You have a 2012 kfhd
You can get into twrp
Nothing will flash
Odd
We have another person that can't get a restore to take. I've always wondered if it was a formatting issue for him...
But if you were to hand me this kindle I would restore from the restore tool not kffa then I would follow hash codes install 2nd boot loader + twrp thread .
If you've tried that I'm at a loss
Forgive me I read the entire thread but I got lost somewhere in post 3
Sent from my XT907 using xda app-developers app
Sucess! Kinda :/
stunts513 said:
OK now for the stupid question, I saw you said it runs a 7.x.x os, just wanted to verify that you are sure of this. I know that kinda a noob question but I have to ask to double check things. Also have you tried flashing cm 11?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I did verify that it is on stock, rooted, de-self updater-ed, 7.2.3. It was on 7.3 something originally.
Hellfire flashed over just fine, CM 10.1 (I think) Flashed it, booted KindleFire (Orange) then (Blue) then Boot logo Booted pretty fast too.
mrkhigh said:
Reiterate
You have a 2012 kfhd
You can get into twrp
Nothing will flash
Odd
We have another person that can't get a restore to take. I've always wondered if it was a formatting issue for him...
But if you were to hand me this kindle I would restore from the restore tool not kffa then I would follow hash codes install 2nd boot loader + twrp thread .
If you've tried that I'm at a loss
Forgive me I read the entire thread but I got lost somewhere in post 3
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yes, 2012 KFHD 7" (Tate)
Yes, TWRP works fine.
No, I got Hellfire to flash, but so far nothing else will flash 0.o :/
Also, I did all my restores from KFFA, BUT, I did do a original backup via ADB and did a restore via Fastboot thinking it might have been KFFA but no go still.
And yes, the thread kinda goes to poop cause I was already kinda upset cause this has been the most frastrating Android to work with, and then the pressure got compounded just cause I decided to ask for help :/
If any of this info helps, please let me know, I believe Hellfire is CM 10.1 . . . I believe, that's off the top of my head though.
Thanks!
To be honest I've only installed kinology... Wife won't let me get rid of the kindle os. I didn't really needed kinology but I wanted to update and did not want to reset it up again. He basically ran a neater version of what I was doing.
Is there an error when you flash the ROM and what ROM are you flashing
Sent from my XT907 using xda app-developers app
Ello,
This is my first post!
I've just bought a Asus TF701t and I want to install CROMi-X. I've already done a Nandbackup using CWM booted from fastboot so I still have the stock recovery. However I hear that this tablet allows for a much lower level of backup using APX. Before I do any further changes to this tablet I would like to backup the boot loader.
Is this possible? All the tutorials are for older Transformers.
I'm currently on 10.26.1.18 bootloader with Stock rom.
Thanks...
Read the FAQ
IcePee said:
Ello,
This is my first post!
I've just bought a Asus TF701t and I want to install CROMi-X. I've already done a Nandbackup using CWM booted from fastboot so I still have the stock recovery. However I hear that this tablet allows for a much lower level of backup using APX. Before I do any further changes to this tablet I would like to backup the boot loader.
Is this possible? All the tutorials are for older Transformers.
I'm currently on 10.26.1.18 bootloader with Stock rom.
Thanks...
Click to expand...
Click to collapse
Ooops, I just read: http://forum.xda-developers.com/showthread.php?t=2554744. Doh! Newbie mistake.
This leads to my next question Does anyone know if we will be getting this feature?
IcePee said:
Ooops, I just read: http://forum.xda-developers.com/showthread.php?t=2554744. Doh! Newbie mistake.
This leads to my next question Does anyone know if we will be getting this feature?
Click to expand...
Click to collapse
It took a very long time to get nvflash working on Android 4.2.1 on the TF201, TF300 and TF700. As we have fewer devs working on the TF701 I would say you have zero chance of seeing anything insode the next 6 months.
As long as you follow the guides it is hard to brick. If unsure ask first And NEVER wipe from the BOOTLOADER. EVER.
OK, going for it
sbdags said:
It took a very long time to get nvflash working on Android 4.2.1 on the TF201, TF300 and TF700. As we have fewer devs working on the TF701 I would say you have zero chance of seeing anything insode the next 6 months.
As long as you follow the guides it is hard to brick. If unsure ask first And NEVER wipe from the BOOTLOADER. EVER.
Click to expand...
Click to collapse
Thanks for getting back to me this quickly.
OK, I'm going for it! I've already done a wipe data/factory reset and wipe cache partition. Let's see where we get to...
Result!
Just to let you know I've successfully installed the CROMi-X firmware. It went very smoothly once I could get it going. I kept having problems installing from the keyboard dock's SDCard reader. It kept failing the initial checksum process. I switched to a higher capacity MicroSD in the internal reader and it went on without a hitch.
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
meeniemuffin said:
.... But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot.
Click to expand...
Click to collapse
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
meeniemuffin said:
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
Click to expand...
Click to collapse
-enable "OEM unlocking" in developer options
-unlock bootloader
-flash TWRP using fastboot
-flash a custom kernel
-flash SuperSU 2.52
-KEEP BOOTLOADER UNLOCKED
-KEEP "OEM unlocking" ENABLED
---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------
NLBeev said:
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
There's nothing mentioned there.
Droidphilev said:
There's nothing mentioned there.
Click to expand...
Click to collapse
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
NLBeev said:
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
Click to expand...
Click to collapse
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Droidphilev said:
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Click to expand...
Click to collapse
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Aha! i saw you posting this before but never knew that it was a joke
I didn't even need to read all this stuff. First thing I did was get into developer mode and almost instinctual that I turned on OEM unlocking before setting about unlocking the bootloader.
Sent from my Nexus 6 using Tapatalk
Yeah I bought my N6 recently and had a bad first time experience too. I ended up using a toolkit to root and all that, didn't need a custom rom so I kept it stock with TWRP and I'm very happy. Since then, I rooted some of the old devices I had laying around (you can check my signature), so I should be more prepared next time I need to update. My problem is I didn't really understand the commands, what did what and what exactly was required for root. Now that I have had plenty to practice with I'm pretty comfortable with commands and recoveries. Practice makes perfect I guess
NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
shadowcore said:
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
Click to expand...
Click to collapse
I hope not. Google's software and design will be the weak point. Google could not give us some simple options like a dark interface, reboot options and dpi settings.
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
If bootload is locked, unlock it - This will erase everything backup your device
1. Get modified boot.img for your version, flash it
2. Flash twrp
3. Flash SuperSu 2.52
meeniemuffin said:
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Droidphilev said:
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Click to expand...
Click to collapse
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
meeniemuffin said:
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
Click to expand...
Click to collapse
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Droidphilev said:
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Click to expand...
Click to collapse
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
meeniemuffin said:
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
Click to expand...
Click to collapse
enjoy!
but DO NOT forget to keep "OEM unlocking" enabled!
(it will save you when you ever get locked out from your google acoount because you became aflashoholic)
Hi I just flashed cm 12 on my device but the cm screen doesn't boot up it just keeps on showing the logo I've been waiting for an hour. Please anyone know how to fix it?
Its_Ima said:
Hi I just flashed cm 12 on my device but the cm screen doesn't boot up it just keeps on showing the logo I've been waiting for an hour. Please anyone know how to fix it?
Click to expand...
Click to collapse
Sorry - this is a known issue with no resolution. Best (only) option is to seek a courtesy exchange from Amazon if still within warranty.
Davey126 said:
Sorry - this is a known issue with no resolution. Best (only) option is to seek a courtesy exchange from Amazon if still within warranty.
Click to expand...
Click to collapse
so there's no way to fix it? Even with adb commands?
Its_Ima said:
so there's no way to fix it? Even with adb commands?
Click to expand...
Click to collapse
Unfortunately, no. There is a known but not fully understood interaction between CM and FlashFire which occasionally results in a CM boot loop. Also destroys access to the stock recovery partition which would be the normal fall back following a failed flash. ADB is not active and thus can not be used. Fastboot environment is crippled on Amazon devices with a locked bootloader. Factory/fastboot cables are ineffective. Sorry for the bad news ...
If you cannot get to Amazon recovery, it is bricked. If you can get to it, you can go back to stock and try it again.
From what I know, the problem with CM12 and flashfire is the location of the wipe, people do not place it on top of the order as specified on instructions before flashing.
If wrong, someone let me know...
shabuboy said:
If you cannot get to Amazon recovery, it is bricked. If you can get to it, you can go back to stock and try it again.
From what I know, the problem with CM12 and flashfire is the location of the wipe, people do not place it on top of the order as specified on instructions before flashing.
If wrong, someone let me know...
Click to expand...
Click to collapse
Mispositioning of the Wipe action is certainly a problem but not the smoking gun as more than a handful of users are adamant they followed 'best practices' yet still ended up with a brick. These claims are supported by screenshots that show a reasonable FlashFire configuration just before execution. Also doesn't explain the bricks that occur when no wipe action is included.
I FIXED IT!!
All I did way follow this videohttps://m.youtube.com/watch?v=RQLoH-ahjy4 and it worked.
Its_Ima said:
I FIXED IT!!
All I did way follow this videohttps://m.youtube.com/watch?v=RQLoH-ahjy4 and it worked.
Click to expand...
Click to collapse
Aah - so the stock recovery could still be accessed! This is unusual with CM flash failures; I just assumed it was fully borked (note to self: never assume). So yea, recovery is both possible and fairly easy thanks to Root Junky's excellent video.
Question: what version of FlashFire did you use? This could be a major breakthrough if newer builds do not destroy access to stock recovery when a CM flash goes bad.
Davey126 said:
Aah - so the stock recovery could still be accessed! This is unusual with CM flash failures; I just assumed it was fully borked (note to self: never assume). So yea, recovery is both possible and fairly easy thanks to Root Junky's excellent video.
Question: what version of FlashFire did you use? This could be a major breakthrough if newer builds do not destroy access to stock recovery when a CM flash goes bad.
Click to expand...
Click to collapse
I used flashed fire 0.27
Its_Ima said:
I used flashed fire 0.27
Click to expand...
Click to collapse
I was just wondering is there anyway to flash cm 12 successfully?
If you have 5.0.1 yes, with TWRP.
5.1.1 only flashfire and it is a gamble.
Both methods discuss at the CM12 ROM:
http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
Its_Ima said:
I used flashed fire 0.27
Click to expand...
Click to collapse
Its_Ima said:
I was just wondering is there anyway to flash cm 12 successfully?
Click to expand...
Click to collapse
shabuboy said:
If you have 5.0.1 yes, with TWRP.
5.1.1 only flashfire and it is a gamble.
Both methods discuss at the CM12 ROM:
http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
Click to expand...
Click to collapse
Agreed. The Fire Gods were looking over you on the last attempt as your device was recoverable. I see you recently posted a question about flashing Resurection-Remix. I have no direct experience with this rom so can't speak to reliability with FlashFire. I suggest looking at Nexus or SlimLP both of which have a modest track record of sucessful installs via FlashFire. Nexus holds a slight advantage IMO as GAaps and SuperSU are built-in so only one item to flash. There's a nice video (by Root Junky) in the OP. That said, SlimLP, Remix and others are fine alternatives. Nice to have choices.
For now stay away from CM. While the ROM is excellent unpredictable behavior with FlashFire is a spoiler.
Davey126 said:
Agreed. The Fire Gods were looking over you on the last attempt as your device was recoverable. I see you recently posted a question about flashing Resurection-Remix. I have no direct experience with this rom so can't speak to reliability with FlashFire. I suggest looking at Nexus or SlimLP both of which have a modest track record of sucessful installs via FlashFire. Nexus holds a slight advantage IMO as GAaps and SuperSU are built-in so only one item to flash. There's a nice video (by Root Junky) in the OP. That said, SlimLP, Remix and others are fine alternatives. Nice to have choices.
For now stay away from CM. While the ROM is excellent unpredictable behavior with FlashFire is a spoiler.
Click to expand...
Click to collapse
I was able to flash resurrection remix successfully. It's a really nice rom btw.
So long story short, I was messing with my Fire after it sitting for a few months, trying to put Xposed Modules on it, I ended up flashing a bad custom recovery. Now, I am stuck with a bootloop and no recovery whatsoever. If I hold Vol Down + Power, all I get is the fire logo, but nothing with it. It will sit for hours. Only thing I can get into is fastboot, but I'm not sure where to go from there. Any help would be great! It should still be rooted, since I haven't modified any of that. I was running Slim LP rom from December. So I'm on old FW. Thanks for any help ya'll can provide.
camistotle said:
So long story short, I was messing with my Fire after it sitting for a few months, trying to put Xposed Modules on it, I ended up flashing a bad custom recovery. Now, I am stuck with a bootloop and no recovery whatsoever. If I hold Vol Down + Power, all I get is the fire logo, but nothing with it. It will sit for hours. Only thing I can get into is fastboot, but I'm not sure where to go from there. Any help would be great! It should still be rooted, since I haven't modified any of that. I was running Slim LP rom from December. So I'm on old FW. Thanks for any help ya'll can provide.
Click to expand...
Click to collapse
At preaent there is no reasonable recovery from this condition unless your bootloader is 5.0.1 (which permits booting twrp).
Davey126 said:
At preaent there is no reasonable recovery from this condition unless your bootloader is 5.0.1 (which permits booting twrp).
Click to expand...
Click to collapse
I may be possible that I am.. I can't remember. Got the link to it? I'll give it a shot. Not like I can do much more harm. Thanks.
camistotle said:
I may be possible that I am.. I can't remember. Got the link to it? I'll give it a shot. Not like I can do much more harm. Thanks.
Click to expand...
Click to collapse
This thread should prove helpful (obtaining and booting twrp image):
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548/page1