Related
Good day!
Kindle Fire HD 7 7.2.2 was succesfully rooted through Qemu
After that start the Root Explorer and frozen some programs from Amazon
After Root explorer closed - system wrote that the application is not responding and offered either wait or force close.
Waited about 5 minutes and then forcibly closed.
The tablet is rebooted and it now shows a picture Kindle Fire, which is quickly poured color.
Tell me what to do? Can I fix something back?
Thanks in advance!
I believe that at this point, all you can do is put the tablet in Odin (fastboot) mode and flash a image containing the partitions. You'll have to Google to see if anyone has uploaded genetic partitions for the HD. The problem is that no one has come up with a working boot recovery that most other Android devices have that allow you to run a restore. I've seen several postings of developers working on this.
Sent from my SPH-L710 using xda premium
ameswilliam said:
I believe that at this point, all you can do is put the tablet in Odin (fastboot) mode and flash a image containing the partitions. You'll have to Google to see if anyone has uploaded genetic partitions for the HD. The problem is that no one has come up with a working boot recovery that most other Android devices have that allow you to run a restore. I've seen several postings of developers working on this.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I understand that I need a cable factory, similar to Kindle Fire. The manual, which indicates how to make such a cable was told to solder one pin and 4-pin. After that, download the program from the subject http://forum.xda-developers.com/showthread.php?t=1951254 and take a backup to 7.2.2, as of 7.2.1 is not suitable.
I understand you correctly? And if so, where to take a backup of 7.2.2?
Thanks in advance!
backup 7.2.2
baxxik said:
I understand that I need a cable factory, similar to Kindle Fire. The manual, which indicates how to make such a cable was told to solder one pin and 4-pin. After that, download the program from the subject http://forum.xda-developers.com/showthread.php?t=1951254 and take a backup to 7.2.2, as of 7.2.1 is not suitable.
I understand you correctly? And if so, where to take a backup of 7.2.2?
Thanks in advance!
Click to expand...
Click to collapse
i have backup 7.2.2 for you, copy anh past in images folder and launch SR Tool.bat, chose 1..good luck..:laugh:
http://sdrv.ms/TZ4pOG
Huuthaolove said:
i have backup 7.2.2 for you, copy anh past in images folder and launch SR Tool.bat, chose 1..good luck..:laugh:
http://sdrv.ms/TZ4pOG
Click to expand...
Click to collapse
Thank you very much for your help! :good:
Please let us know if you were able to recover your HD with this image. Thanks.
Wat happen to kindle did work
Sent from my SGH-T989 using xda premium
I'm the living testimonial and last survivor for this bricking journey. I had my device rooted on the second day that I got my KFHD, then bricked it and kept in the kindle fire bootloop for days.
I was a bit sceptical to buy a factory cable initially as I would have to wait for weeks over this part on earth. But after reading all the sources available online and I know this factory cable is unavoidable, I ordered, waited and received my factory cable and guess what, this is just like the immediate antidote given to the sleeping beauty, after I plugged in the factory cable and carefully followed the instructions by the seniors here, I unbricked my KFHD in 10 minutes.
My two-cents advice is, if you are adventurous type and plan to go wild with your KFHD, get your factory cable before anything else, then, you can experiment all the wonderful ideas/ modding here.
Good luck and have fun!
Sent from my KFTT using xda premium
Did you manage to restore the image? 7.2.2 Me too have this problem
u cant help u
Brannier said:
Did you manage to restore the image? 7.2.2 Me too have this problem
Click to expand...
Click to collapse
your kindle had update 7.2.3???, if it's true, i think you will need 7.2.3 system.img image, i cant buckup for you, wait me...:fingers-crossed:
Long story short I flashed a 7.2.3 bootloader from hashcodes TWRP thread to my KFHD7 and now it wont turn on at all. I have a factory cable but fastboot and adb can't do anything since the bootloader isn't even loaded yet. I'm sort of nervous to do the USB boot trick because I heard that that trick was designed for an older kindle model. I'm downloading Firekit now but the option I need to fix my kindle requires the USB boot trick so will that trick work on my kindle or not? Also could anyone point me in the right direction to flashing a CORRECT bootloader so this doesent happen a third time? (My kindle's OS is 7.4.3 with OTA disabled)
P.S. The file attached is the bootloader I flashed.
I would not do what you are attempting, the older tricks and utilities are not usually something u mix with the new kindles. When u say factory cable I have to ask do u mean the cable that came with the kindle or a fastboot cable. If its a fastboot cable then when u hook your kindle up to your PC with it it should make the kindle say fastboot on the screen. If it can then u can reflash the 7.2.3 uboot file. That should fix it. If instead your PC picks up an omap440 device then you are in trouble.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I would not do what you are attempting, the older tricks and utilities are not usually something u mix with the new kindles. When u say factory cable I have to ask do u mean the cable that came with the kindle or a fastboot cable. If its a fastboot cable then when u hook your kindle up to your PC with it it should make the kindle say fastboot on the screen. If it can then u can reflash the 7.2.3 uboot file. That should fix it. If instead your PC picks up an omap440 device then you are in trouble.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yes I mean a fastboot cable and I can't flash anything because the kindle wont boot up, the screen wont turn on or anything
Hmm that's bad, year uncould try seeing if the battery would charge. Ur I'm guessing hard brick, I'd wait to see if anyone else has any other suggestions. I'm guessing when u flashed this either u didn't check the md5 signature first or u tried flashing the zip file instead of what's in it. Sorry if the second one sounds a bit condescending I just don't know how well you are with pc's. If its hard bricked you could try sending it to amazon, they might replace it. Lookup some tips on the forum for she ding it in because I hard things about telling them its rooted but not that u have flashed it or something, cause technically u void the warranty when u root it but sometimes they are forgiving. Anyways see if some other people respond before sending it in.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Hmm that's bad, year uncould try seeing if the battery would charge. Ur I'm guessing hard brick, I'd wait to see if anyone else has any other suggestions. I'm guessing when u flashed this either u didn't check the md5 signature first or u tried flashing the zip file instead of what's in it. Sorry if the second one sounds a bit co descending I just don't know how well you are with pc's. If its hard bricked you could try sending it to amazon, they might replace it. Lookup some tips on the forum for she ding it in because I hard things about telling them its rooted but not that u have flashed it or something, cause technically u void the warranty when u root it but sometimes they are forgiving. Anyways see if some other people respond before sending it in.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yeah it's hard bricked, I'll wait a while just in case someone else has some tips or something. Let that be a lesson, ALWAYS check the MD5 to whoever is reading this
LURKMOAR1234 said:
Long story short I flashed a 7.2.3 bootloader from hashcodes TWRP thread to my KFHD7 and now it wont turn on at all. I have a factory cable but fastboot and adb can't do anything since the bootloader isn't even loaded yet. I'm sort of nervous to do the USB boot trick because I heard that that trick was designed for an older kindle model. I'm downloading Firekit now but the option I need to fix my kindle requires the USB boot trick so will that trick work on my kindle or not? Also could anyone point me in the right direction to flashing a CORRECT bootloader so this doesent happen a third time? (My kindle's OS is 7.4.3 with OTA disabled)
P.S. The file attached is the bootloader I flashed.
Click to expand...
Click to collapse
Sorry to tell you but there is nothing you can do. The "usb boot trick" does not work on the new gen models. I have seen numerous people with the same problem and no solution has been found.
I'm a little confused as to why the fastboot cable won't work. It should entirely bypass the need for a boot loader, that's sort of the whole point.
What happens when you plug in your fastboot cable (to both your PC and your kindle) and power on? Do you even get the orange kindle flash animation?
-voided said:
I'm a little confused as to why the fastboot cable won't work. It should entirely bypass the need for a boot loader, that's sort of the whole point.
What happens when you plug in your fastboot cable (to both your PC and your kindle) and power on? Do you even get the orange kindle flash animation?
Click to expand...
Click to collapse
I don't know where you get that idea, but you are radically misguided. The bootloader is never "bypassed" when using a factory cable. The bootloader is fully functional and doing exactly what it is programmed to do, which is, enable fastboot while a factory cable is plugged in.
However in your case, the bootloader isn't even being loaded because the OMAP ROM has completely halted the boot process...which is exactly why the factory cable will not work.
-voided said:
I'm a little confused as to why the fastboot cable won't work. It should entirely bypass the need for a boot loader, that's sort of the whole point.
Click to expand...
Click to collapse
That's what I thought at first too, but then I thought I heard something about the boot loader having fast boot in it, now I am just confusing myself. Fast boot has to be stored somewhere on the kindle, for some reason I always thought of it as a chip that wasn't part of the onboard storage, but then I realized if we get omap440 bricks and fastboot won't kick in it must be part of the partitions, so I am inclined to think its stored in the boot loader. If I am wrong I would love to know where it is stored out of curiosity.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
That's what I thought at first too, but then I thought I heard something about the boot loader having fast boot in it, now I am just confusing myself. Fast boot has to be stored somewhere on the kindle, for some reason I always thought of it as a chip that wasn't part of the onboard storage, but then I realized if we get omap440 bricks and fastboot won't kick in it must be part of the partitions, so I am inclined to think its stored in the boot loader. If I am wrong I would love to know where it is stored out of curiosity.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Wait a sec I just found something: http://forum.xda-developers.com/showthread.php?t=2135611
Could these drivers be used to somehow communicate with the kindle? Maybe prevent the OMAP ROM from stopping the booting process?
If not then I'll just buy a new kindle, since I can't even access the filesystem to delete the su and busybox binaries if I wanted to send it back to amazon.
The drivers are useful, but not to the point we can use them, we need a program that knows how to communicate sending data to the kindle thru omap440 interface. Much like how adb drivers are useless without the adb program.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
The drivers are useful, but not to the point we can use them, we need a program that knows how to communicate sending data to the kindle thru omap440 interface. Much like how adb drivers are useless without the adb program.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Have you tried looking earlier in the thread where it has the usbboot/aboot website?
Sent from my Amazon Kindle Fire HD using xda app-developers app
---------- Post added at 03:12 AM ---------- Previous post was at 03:03 AM ----------
I can't seem to find a compiled one so I'll see if I can do it for ya.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Some of the most talented and experienced developers and hackers in the community have been looking at this problem for some time now. The Kindle Fire is not the only device to have OMAP HS processors with M-Shield turned on, and it definitely isn't the first.
Believe me, if there is a solution to this problem, it will be found, but by those who are waaaaaaay more experienced than any of us.
The best you can do at this point is learn from your experience, be much more careful in the future, and do the appropriate amount of research the next time you decide to modify your device.
soupmagnet said:
Some of the most talented and experienced developers and hackers in the community have been looking at this problem for some time now. The Kindle Fire is not the only device to have OMAP HS processors with M-Shield turned on, and it definitely isn't the first.
Believe me, if there is a solution to this problem, it will be found, but by those who are waaaaaaay more experienced than any of us.
The best you can do at this point is learn from your experience, be much more careful in the future, and do the appropriate amount of research the next time you decide to modify your device.
Click to expand...
Click to collapse
Yeah you're right. Well thanks to everyone for all the information, and I'll be sure to be way more careful when screwing around with low level things such as bootloaders. I'm just gonna sell my bricked kindle on ebay for parts and get a new one from amazon. Thanks again everyone.
LURKMOAR1234 said:
Yeah you're right. Well thanks to everyone for all the information, and I'll be sure to be way more careful when screwing around with low level things such as bootloaders. I'm just gonna sell my bricked kindle on ebay for parts and get a new one from amazon. Thanks again everyone.
Click to expand...
Click to collapse
You're not gonna wait for me to compile usbboot and aboot?
Sent from my Amazon Kindle Fire HD using xda app-developers app
Because I'm too lazy to Google right now, what do those programs do?
Edit: after looking through some threads I'm guessing its a flasher for the omap440 device, that's kinda not tested and just stuck together for testing. So we have no idea if it would work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Because I'm too lazy to Google right now, what do those programs do?
Edit: after looking through some threads I'm guessing its a flasher for the omap440 device, that's kinda not tested and just stuck together for testing. So we have no idea if it would work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
It wouldn't hurt anything. To your knowledge, your device is screwed beyond repair. And if it fixes your kindle, why not try it?
Sent from my Amazon Kindle Fire HD using xda app-developers app
r3pwn said:
It wouldn't hurt anything. To your knowledge, your device is screwed beyond repair. And if it fixes your kindle, why not try it?
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
Don't waste your time. The initial USB loader used to flash images to the eMMC must also be digitally signed. Unless, by some miracle, you happen to have a copy...it won't work. You'd be better off either trying to get a copy of the boot tools used by Amazon in the factory (somewhere in China), or finding an exploit in the OMAP ROM code which, I'm guessing, probably isn't available either.
r3pwn said:
It wouldn't hurt anything. To your knowledge, your device is screwed beyond repair. And if it fixes your kindle, why not try it?
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
Well I still do have my kindle so if you do happen to get usbboot and aboot working I'd gladly have my kindle be the lab rat for it. But the only problem is the signature for the USB loader, just like soupmagnet said.
sorry about how old this thread is, but I flashed a good bootloader to my Kindle (forgot the exact model), but it was for a different Kindle. Is there anything I can do? My computer doesn't pickup ANYTHING when I plug it in.
Hi all,
I got really interested in rooting and such my Kindle Fire. However, when I used the tool on here for installing Google Play and its components, my dog accidentally pulled on the cable, disconnecting the Kindle mid-process of the tool.
Tool was this: http://forum.xda-developers.com/showthread.php?t=2069329
No however upon boot up, my kindle shows NO ads now. Then when I unlock it, it's extremely sluggish, shows no icons in the carousel, but still recognizes all my personal data and can still be accessed via computer.
I've tried loads of different things to fix it, but to no avail. I've gone into Fastboot mode (Though it just remains stuck at the logo) and when I try these two tools, nothing seems to help fix the problem.
Tools: http://forum.xda-developers.com/showthread.php?t=1428428
http://forum.xda-developers.com/showthread.php?t=2096888
Any suggestions guys? Any help will be great. I'd just like to get it back to the way it was.
Ugh I think I vaguely remember what causes this but not well enough to fix it, so what did you do so far, did you reflash the system partition? Because I think this might be in the /data folder in a build.prop but I am unsure, I know the main built.prop you usually see is in the /system folder. This I think has something to do with a qemu property but like I said I hope I am pointing you in decent direction. I will see if I can pull up a similar post and give you a link to a fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ugh I think I vaguely remember what causes this but not well enough to fix it, so what did you do so far, did you reflash the system partition? Because I think this might be in the /data folder in a build.prop but I am unsure, I know the main built.prop you usually see is in the /system folder. This I think has something to do with a qemu property but like I said I hope I am pointing you in decent direction. I will see if I can pull up a similar post and give you a link to a fix.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for the advice, but sadly I'm unfamiliar with loads of the inner workings, since I was using the automatic coders to get the roms in and etc.
All I really did was start the Tool, hit the number on CMD for applying the Google Play stuff (NOTE: I manually rooted the kindle before hand) then the dog thing happened. Now it's as I've said. I don't own the Fastboot cable either, but I DO get to go to Fastboot Mode (Logo Only) through the tool.
Be careful, I don't know if that tool is from this section of the forum, and some tools from the kf1 section can hard brick your kindle, still looking for the thread BTW.
Edit: I can't seem to find the thread... I don't like recomending doing this since it will wipe all your apps and their data, but do a factory reset from the kindles settings if you can get to it, I think it will fix the problem, not positive.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I've been looking into it, I may have used stuff for Gen 1 Kindle's, so yeah, that could have been the problem.
Gonna do the factory reset, only thing I haven't tried. Transferring photos. Lady friend may stab me for losing those.
Thanks again for the advice. I'll get back to you with any change.
Ah thanks to soupemagnet he reminded me of what I am thinking of, you need to delete /data/local.prop
Hope you get this before you lose any data.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks for all the tips, go it to work. Sadly I already did the factory reset, and now it's all back to normal.
Any guides out there to get the Kindle to A Full on tablet? I'd be trusting only the ones you send now. Don't want to use a guide for KF1s.
If you mean flashing a ROM of an actual android os, here's the guide for it: http://forum.xda-developers.com/showthread.php?t=2271909
Just make sure that in fire flash you check the box with the red warning text or your kindle will have a red screen of death that only a fastboot cable will fix, also remember to put a copy of the ROM you want to flash and gapps for that ROM on the kindles sdcard before flashing or you might get stuck in a recovery loop depending on your kindle os version. That tutorial also has some ROMs on it you can use, there might be others in the development section its from you can use as well depending on whenever the last time seokhun updated that tut. That tutorial may be lengthy, but make sure you read all of it, that way you make sure you follow exactly what it says to do and reduce your chances of bricking. Its always better to be safe when messing with a locked devices boot loader than sorry.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
BACKGROUND: So i rooted my kindle using this tutorial http://www.youtube.com/watch?v=hUW6KARo8Y4 and it worked fine... up until i tried to put the new os. This was a very long time ago and you can follow my progress in my old forum http://forum.xda-developers.com/showthread.php?t=2536008&page=4 (which did not fix it.) I decided i need a new start so i made this new forum.
Okay so heres the problem: When i boot up my kindle, it shows the regular kindlefire logo (not fire fire fire) and then a red screen slides by and it boots into fastboot.
*I do have access to a factory fastboot cable*
18lo said:
BACKGROUND: So i rooted my kindle using this tutorial http://www.youtube.com/watch?v=hUW6KARo8Y4 and it worked fine... up until i tried to put the new os. This was a very long time ago and you can follow my progress in my old forum http://forum.xda-developers.com/showthread.php?t=2536008&page=4 (which did not fix it.) I decided i need a new start so i made this new forum.
Okay so heres the problem: When i boot up my kindle, it shows the regular kindlefire logo (not fire fire fire) and then a red screen slides by and it boots into fastboot.
*I do have access to a factory fastboot cable*
Click to expand...
Click to collapse
Its a really simple fix. Just making sure, this is codename tate? Turn off the kindle. Download the restore image tool for the kindle on the development page where you get ROMs. After that's downloaded plug in the fast boot cable to the PC and your kindle. Turn the device on, run the bat file from the image tool, and then you want to do 4, then the one that restores to the original bootloader, don't know what number. Then hit 1. After that you have a brand new kindle. And reboot with a regular cable.
18lo said:
BACKGROUND: So i rooted my kindle using this tutorial http://www.youtube.com/watch?v=hUW6KARo8Y4 and it worked fine... up until i tried to put the new os. This was a very long time ago and you can follow my progress in my old forum http://forum.xda-developers.com/showthread.php?t=2536008&page=4 (which did not fix it.) I decided i need a new start so i made this new forum.
Okay so heres the problem: When i boot up my kindle, it shows the regular kindlefire logo (not fire fire fire) and then a red screen slides by and it boots into fastboot.
*I do have access to a factory fastboot cable*
Click to expand...
Click to collapse
I told you last time you flashed the wrong bootloader. The video is for an 8.9. You seem to not be able to make up your mind which mod you tried first but you have issue that are not repairable.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
I told you last time you flashed the wrong bootloader. The video is for an 8.9. You seem to not be able to make up your mind which mod you tried first but you have issue that are not repairable.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Um, you sure he hard bricked it? He said it's going to a red screen then fastboot, if that was the case and the pc can detect it he should be able to reflash the bootloader. Then again i didnt really read the thread he posted, just kinda glanced through it.
stunts513 said:
Um, you sure he hard bricked it? He said it's going to a red screen then fastboot, if that was the case and the pc can detect it he should be able to reflash the bootloader. Then again i didnt really read the thread he posted, just kinda glanced through it.
Click to expand...
Click to collapse
You might try reading the original thread then.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
You might try reading the original thread then.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok after reading that i'm a bit confused becasue it seems suggestions were being thrown all over the place. I see it says he thought he flashed firefirefire, but as far as i know, flashing that would have resulted in the device not even wanting to power on since its not designed for our device and wouldnt turn on.
I'm willing to play ball and see where this goes just to see whats going on. If you can get fastboot to recognize the device try running "fastboot -i 0x1949 getvar product" and tell me what it hands off, i want to know once and for all that this is a 7" hd model and that will tell me.
LinearEquation said:
I told you last time you flashed the wrong bootloader. The video is for an 8.9. You seem to not be able to make up your mind which mod you tried first but you have issue that are not repairable.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i was able to remove the bootloader
Uh oh... I tried to use KFFirrstAid again and completely restore to 7.2.3 and i believe i have officially hard bricked my kindle. It does not turn on and the computer cannot detect it. Thanks for your help anyway
how did kffa manage to hard brick it???? Well if it is indeed hard bricked i would see about putting it to a good cause and see if @kurohyou wants it. He mapped out emmc pins for the 8.9" and kf2 so we can reflash teh bootloader via soldering a sdcard reader to the kindles motherboard, but he still needs a hard bricked kfhd 7 to map th epins out for this model. Downside is it will probably make the kindle's motherboard completely unusable because he has to unsolder the emmc chip to figure out the pin locations. He might be able to solder the emmc back on thought so you might actually get a working motherboard back if you get lucky. This would benefit the community as awkward as it is to ask.
stunts513 said:
how did kffa manage to hard brick it???? Well if it is indeed hard bricked i would see about putting it to a good cause and see if @kurohyou wants it. He mapped out emmc pins for the 8.9" and kf2 so we can reflash teh bootloader via soldering a sdcard reader to the kindles motherboard, but he still needs a hard bricked kfhd 7 to map th epins out for this model. Downside is it will probably make the kindle's motherboard completely unusable because he has to unsolder the emmc chip to figure out the pin locations. He might be able to solder the emmc back on thought so you might actually get a working motherboard back if you get lucky. This would benefit the community as awkward as it is to ask.
Click to expand...
Click to collapse
ill see what i can do. i certainly have no use for it.
Hey guys, been using the forums for quite some time now, but this is my first time posting so i just registered an account.
I have looked over the forum but can't seem to find an answer to my issue.
I basically rooted my kindle fire HD but when I came to install a new ROM i ran into some issues.. I followed ALL the instructions on what to do but i think i did something wrong.
When it came to installing the new ROM i was told to wipe everything.. So from TWRP I went to wipe > and then i wiped everything.. But i MEAN everything, so there is nothing at all left on the device AT ALL.. Only TWRP and thats it, no data files or anything. SO everytime i start up it boots into TWRP.
I tried flashing the new ROM using TWRP but everytime i do it doesn't do anything, it says error finding /misc but I read that thats a normal error message.
I've tried flashing a few different ROM's and nothing has worked... I think i may have messed up when it came to putting FireFireFire onto the device using Kindle Fire Utility, am i having this problem because I have tried to install a custom ROM without having FireFireFire...? Or is my device bricked?
Sorry if this is a noob question but I'm not really used to flashing ROM's I've rooted many devices but ive never flashed a ROM before, any help would be greatfully appreciated!
What version of the Kindle Fire HD do you have?
Sent from my SCH-I545 using XDA Free mobile app
Im not actually 100%sure to be honest.. i know its old i think its 1st gen
I need a reply please, I might have possibly flashed the wrong ROM for my device but I highly doubt it, to double check how can i check what model and verrsion m device is just by using TWRP?
Does your kindle fire HD have a camera,HDMI port,power button and volume rocker on one edge of the device? Lynker