Related
First day I got the phone I rooted and installed clockwork mod. I downloaded and installed cm9 but now I can't flash any other roms. Every time I try and flash a new one it boots to log screen then stays on a blank black screen. Any help would be appreciated as i would like to try something else out. Also I followed the flashing instructions of each rom and even tried formatting system with no luck.
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
scott0 said:
just to check, you have to format data as well as cache and dalvik when switching amongst roms. not assuming you didn't, just checking.
---------- Post added at 04:26 PM ---------- Previous post was at 04:16 PM ----------
another thought would be to try to flash via recovery, if you haven't tried that.
Click to expand...
Click to collapse
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
lendmeyoureers said:
Thanks for your reply. I have tried flashing in recovery, and just to make sure I was doing everything ok I wiped cache, wiped davlik cache and formatted the system and it still boots to lg screen, then goes to a blank black screen (but the screen is still on) and stops there. The only rom I can get to flash is CM9.
Click to expand...
Click to collapse
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
drumist said:
What ROMs are you attempting to flash that aren't working? Did you try to re-download them to see if the original download was corrupted?
Click to expand...
Click to collapse
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
scott0 said:
ahh yes, i bricked my phone several months ago this very way, it looks to me like you will have to do machz' unbrick.
Click to expand...
Click to collapse
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
lendmeyoureers said:
But the phone isn't bricked. I can boot and even install CM9 but no other ROM. I have tried the unbrick (post 29) but I get stuck at the lg install tool when I plug my phone in it says failed to download
Click to expand...
Click to collapse
i didn't say your's was bricked, i said i bricked mine doing what you did.
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
i'm not sure what post 29 is, but i've done machz's unbricking 2x succesfully, it's the 1st post in his thread.
either way, i know how frustrating it can be, i hope you get it all sorted out.
lendmeyoureers said:
I have tried the kernelpan1c one and domination HD multiple times through multiple downloads.
Click to expand...
Click to collapse
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
scott0 said:
my point was going towards the topic of the thread, you want to fix your phone to be able to flash other ROMs and i'm figuring you will need to follow the unbricking guide to get your phone to a point to do that, even if it's not bricked, by definition.
Click to expand...
Click to collapse
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
this is good advices. but i never was able to sort out how to use terminal emulator, ugh. i kept trying to run commands from within the phone that were ....hekk can't recall exactly. it was frustrating.
but the best advice i think is the nandroid b/u of the original ROM. although nothing necc. wrong with doing a debrick, only takes <30 minutes, as long as the debricking Gods are all in a good mood at that particular moment.
If you get hono's GB rom, then flash HONO's GB kernel, you should be able to boot into GB no problem
drumist said:
The reason you're having the problem is because the Kernelpan1c ROM does not include a boot image. I'm guessing the Domination HD ROM didn't either, although it seems like the thread for that ROM was deleted so I can't verify that. The ROMs require that you still have the default LG Gingerbread boot image on your device for either of them to work.
Meanwhile CM9 includes a custom boot image, which is necessary since it's ICS.
Do you have a Nandroid backup from when your phone had stock LG Gingerbread installed? If so, what you should do is first restore the Nandroid backup (which will also revert your boot image), then install Kernelpan1c or DominationHD ROM.
If you don't have a nandroid backup, let me know.
---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------
Unbricking is overkill. He can boot into CM9 which would give him root access already, so really all he would need to do is go into terminal emulator and push the correct boot image to his device (unless he already has a Nandroid backup, which is easier and less prone to accidentally bricking the device).
Click to expand...
Click to collapse
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
lendmeyoureers said:
Thanks everyone for the replies. I don't have a backup of the original GB ROM, so I'm assuming the boot img is my issue. Someone mentioned flashing a boot image through CM9. Is there a specific instruction list for this? I can go forward with the unbricking procedure if you guys think its easier.
Click to expand...
Click to collapse
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
drumist said:
Go to the unbricking guide thread and download the boot.img file and place it on your SD card. You don't need any other file.
Next from CM9, open terminal emulator (may have to install it) and type:
Code:
su
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
Be extra careful that you type this exactly! It's a zero, not an 'o', following 'mmcblk', and it must all be lowercase.
Next turn the device off. If it won't turn off, just pull the battery. Don't try to boot back into CM9 because the phone won't boot up properly at this point in time.
Next use volume down + power to get into CWM again. From there, do factory reset/wipe data and install the ROM you want like normal. It should boot up fine now.
(If it doesn't, you can reflash CM9.)
Click to expand...
Click to collapse
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
hah, yeah, that command reminded me of what i was doing wrong, i was mistakenly trying to run shell commands from the emulator.
lendmeyoureers said:
THIS WORKED! Thanks so much! Now if there were only more then 1 ROM whose download links worked...
Click to expand...
Click to collapse
Awesome. Now make a Nandroid backup BEFORE you install another ROM, so you have an easier way to revert to your current boot image. That way you can install CM9 again later if you want without worrying about going through this again if you want to install something else.
So I rooted my KF installed TWRP using KFU. Then accidentally wiped the rom without backing it up, now I have no way to install ICS or the KF OS either would be great. I need some help, I have spent 24 hrs working on this and can't find the answers...!
crossfirexavier said:
So I rooted my KF installed TWRP using KFU. Then accidentally wiped the rom without backing it up, now I have no way to install ICS or the KF OS either would be great. I need some help, I have spent 24 hrs working on this and can't find the answers...!
Click to expand...
Click to collapse
Mount your sd card in twrp transfer http://forum.xda-developers.com/showthread.php?t=1439916 this to your sd card find it and flash it reboot then system you should be good to go
---------- Post added at 10:16 PM ---------- Previous post was at 10:08 PM ----------
and just so you know this is the only time you dont have to wipe to flash and never wipe your sd card unless you know what your doing and always make backups!!
The last thing I remember doing is going to flash a new ROM.
I went into recovery then pushed "factory reset" in CWM.
Ever since then I have not been able to mount /data or /cache so I cannot restore a backup or flash a new ROM. I've tried a lot of different things, NOW I cannot even get a Recovery to start up. (flashed and deleted different versions of different Recoveries (TWRP and CWM).
Was wondering what other solutions there might be.
Right now I am currently using an older booloader with the yellow triangle. Any help is appreciated. Thank you so much!
Well start by putting twrp back on if at all possible go to mount and make sure there are no checks in the boxes of data in system and try to flash another rom or do a restore if you still have issues something far worse has gone wrong post back when and if you can get to that point
---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------
Also read the first post then maybe through this thread and make sure this is not your case http://forum.xda-developers.com/showthread.php?t=1651413
I accidently deleted my back-up and now I'm left with TWRP 2.2 and everytime I try to install a tom it fails halfway through. So I looked and most say ignore and wipe Dalvik cache, so I do. Reboot, then it just boots to TWRP.
Kindle Fire Utility will not detect my Fire either.
I'm at a loss, please help.. :\
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
veeman said:
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
Click to expand...
Click to collapse
Do a factory reset again and then flash.
veeman said:
In twrp go to mount and then mount the drive. Then download a rom from the development section and transfer it to your kindle. Then flash the rom.
---------- Post added at 11:21 PM ---------- Previous post was at 11:21 PM ----------
Do a factory reset again and then flash.
Click to expand...
Click to collapse
I followed your instructions explicitly and they were to no avail, as they relinquished the same results in my latter post.
I've been inactive here over the last month, but from what I've seen the over last couple of days, it seems there's a new version of TWRP (2.2.0? am I seeing this correctly?) that is causing problems. Try an earlier version.
soupmagnet said:
I've been inactive here over the last month, but from what I've seen the over last couple of days, it seems there's a new version of TWRP (2.2.0? am I seeing this correctly?) that is causing problems. Try an earlier version.
Click to expand...
Click to collapse
I had first tried 2.0 then updated to 2.2.
Thanks
Then I would say, since you know you can restore from a backup, try requesting one (minus personal data of course) from someone and see if you can restore from it.
It's very strange some of the things going on lately. I'd hate to think Amazon's hardware has something to do with it, although, I wouldn't put it past them.
soupmagnet said:
Then I would say, since you know you can restore from a backup, try requesting one (minus personal data of course) from someone and see if you can restore from it.
It's very strange some of the things going on lately. I'd hate to think Amazon's hardware has something to do with it, although, I wouldn't put it past them.
Click to expand...
Click to collapse
Any idea where I'd look for a back-up?
The idea has merit, I just googled it and nothing came up.
maybe you'd volunteer to send me a back up?
Thanks
JerzyLW said:
Any idea where I'd look for a back-up?
The idea has merit, I just googled it and nothing came up.
maybe you'd volunteer to send me a back up?
Thanks
Click to expand...
Click to collapse
Lemme see what I can do...
---------- Post added at 12:17 AM ---------- Previous post was at 12:12 AM ----------
Gimme time to flash something create a backup and upload it stick around It won't be posted for long...
Thepooch said:
Lemme see what I can do...
Click to expand...
Click to collapse
It is much appreciated! :highfive:
Check your pm
---------- Post added at 12:52 AM ---------- Previous post was at 12:44 AM ----------
I was thinking more direct upload but since your not here that's kinda difficult lol yea restoring a borrowed backup is probably your best bet once you have a working system replacing twrp would probably be a good idea I have a simple solution for that that really doesn't require much just placing a folder on your SD card and using file browser to run a script... but I really can tell you whether this will remedy your problem if it still exists it could be more than meets the eye..
Maybe your just doing it wrong.
1. Factory reset
2. Wipe cache
3. Wipe dalvik
4. Wipe system
5. Flash rom zip (in zip form)
6. Flash gapps zip (in zip form)
7. Reboot then system if prompted....
If your doing all this and it fails make sure you have zip signature verification and md5 verification unchecked, still failing sounds like a twrp problem..
Also twrp should be throwing you some errors would be nice to know what they are?
Thepooch said:
Check your pm
---------- Post added at 12:52 AM ---------- Previous post was at 12:44 AM ----------
I was thinking more direct upload but since your not here that's kinda difficult lol yea restoring a borrowed backup is probably your best bet once you have a working system replacing twrp would probably be a good idea I have a simple solution for that that really doesn't require much just placing a folder on your SD card and using file browser to run a script... but I really can tell you whether this will remedy your problem if it still exists it could be more than meets the eye..
Click to expand...
Click to collapse
The restore was successful. I am now stuck in a boot loop with TWRP.
And I still cannot get KFU to recognize my Fire either.
JerzyLW said:
The restore was successful. I am now stuck in a boot loop with TWRP.
And I still cannot get KFU to recognize my Fire either.
Click to expand...
Click to collapse
Install a newer version of TWRP (2.1.1 or greater). Reboot to system does not work properly in earlier versions. Otherwise, use "adb shell idme bootmode 4000" to set the bootmode to normal manually. If you are unfamiliar with adb/fastboot, read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
The third post has explanations of adb/fastboot commands and how to use them, but the entire guide will probably be useful to you.
kinfauns said:
Install a newer version of TWRP (2.1.1 or greater). Reboot to system does not work properly in earlier versions. Otherwise, use "adb shell idme bootmode 4000" to set the bootmode to normal manually. If you are unfamiliar with adb/fastboot, read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
The third post has explanations of adb/fastboot commands and how to use them, but the entire guide will probably be useful to you.
Click to expand...
Click to collapse
Thanks I'll take a look.
JerzyLW said:
Thanks I'll take a look.
Click to expand...
Click to collapse
No matter what I do, I cannot get my computer to recognize my Kindle. In device manager it says it is there with a yellow triangle, so I click update it doesn't work, I check my Android SDK downloader and it says I have the drivers downloaded so I manually searched for them in the extras folder in the sdk folder, still no go. I get an error. I am now at ends I have no idea what to do, and it is very aggravating to say the least.
Thanks for your help guys!
Instead of letting it boot by itself manually select normal boot in the boot menu if that doesn't work rewipe restore the backup again this time skip the dalvik and cache wipe after the restore...
My computer can't find my kindle fire and it's mounted on twrp
make sure there are no checks in the boxes of system and data then hit the big button that says mount..... the only things that should have checks in them are sdcard and cache...
Thepooch said:
make sure there are no checks in the boxes of system and data then hit the big button that says mount..... the only things that should have checks in them are sdcard and cache...
Click to expand...
Click to collapse
Yes they are but the computer wont find it. Do you know how to get the computer to find the kindle via adb?
if you cant mount your sdcard there is more at play than meets the eye look at this thread http://forum.xda-developers.com/showthread.php?t=1877567
Hi all, first of all...sorry if I did not provide enough information...I am first time doing this whole flashing thing on my own...
My phone's CID number: HTC_044
Version main: EMPTY <<< is this normal?
Version bootloader: 3.19.0.0000
Using stock ROM i suppose...didn't flash any other third party's ROM before
My phone was rooted for sometime and lately I want to upgrade my phone to Lollipop...I thought I need to unroot first and therefore I found solution online...everything went fine and I was able to upgrade to Lollipop using the official way (update through phone).
However, later on I was trying to root it back...tried to download SU from Google Play and it just can't install properly...I then thought have to re-do everything again (restore back to basic OS version).
Then this second time I do, I wiped the data, cache, and dalvik cache (I did not do this for the first attempt). Then things start to go haywire...my Android files are not going into the internal storage...instead...it is being installed in my external SD card.
I then tried numerous time flasing back to basic OS version (Kit Kat 4.4.2) and update to Lollipop again...still no luck...
Until yesterday I thought everything worked out fine...and I tried installing Facebook...it says cannot install...
Can anyone help me on this? I also not quite sure what went wrong...hope you guys can enlighten me...will try to provide as much information as possible.
jkidz91 said:
However, later on I was trying to root it back...tried to download SU from Google Play and it just can't install properly...I then thought have to re-do everything again (restore back to basic OS version).
Click to expand...
Click to collapse
That is not the proper way to root. Installing SU from the store does not root the phone. It just install the app, not the SU binary.
To root, unlock the bootloader, install TWRP and flash the proper version SuperSU zip in TWRP.
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
jkidz91 said:
Then this second time I do, I wiped the data, cache, and dalvik cache (I did not do this for the first attempt). Then things start to go haywire...my Android files are not going into the internal storage...instead...it is being installed in my external SD card.
I then tried numerous time flasing back to basic OS version (Kit Kat 4.4.2) and update to Lollipop again...still no luck...
Until yesterday I thought everything worked out fine...and I tried installing Facebook...it says cannot install...
Click to expand...
Click to collapse
Its not clear to me what you did, but it might be best to RUU to full stock using the link I provided in the other thread you posted to.
redpoint73 said:
That is not the proper way to root. Installing SU from the store does not root the phone. It just install the app, not the SU binary.
To root, unlock the bootloader, install TWRP and flash the proper version SuperSU zip in TWRP.
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
Its not clear to me what you did, but it might be best to RUU to full stock using the link I provided in the other thread you posted to.
Click to expand...
Click to collapse
Noted bro! You r really helpful!