Cannot install new roms - Kindle Fire Q&A, Help & Troubleshooting

I've been trying to install different roms since I was having problems with my last one.
Using TWRP v.2.2.2.1, but when I try to install a new one and I've tried Chameleon, AOKP and JellyBean I am always stuck on the logo.
Only solution to make the device works is to restore to the original stock rom.
Any help?
Thanks

Try wiping everything and then install and maybe use cotr instead
Sent from my YP-G1 using Tapatalk 4 Beta

goldflame09 said:
Try wiping everything and then install and maybe use cotr instead
Sent from my YP-G1 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks, I'll try it.

Related

why do i keep getting an error 7 when flashing a different rom?

I am running AOKP JB and using CWM. Flashing updated roms of AOKP is fine but when i try to flash a different rom, (I've tried CM9 and 10, KyanRom, and paranoid android) i keep getting the same error.
i factory reset and wipe cache and dalvik but still no go.
any ideas of what i might be doing wrong or how to fix this?
Use Odin flash stock rom then boot into recovery wipe data and reboot done
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
tonyph33r said:
Use Odin flash stock rom then boot into recovery wipe data and reboot done
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
do i have to do this every time i want to flash a different rom? or will doing this one time fix this issue?
What recovery are you running?
Sent from my Nexus 7 using xda premium
defnow said:
What recovery are you running?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
CWM recovery v5.5.0.4
metalhawj said:
CWM recovery v5.5.0.4
Click to expand...
Click to collapse
That's an older version. You need the newest one, which is 5.8.4.7. Download the img file from the website and flash through android emulator.
Downloads: http://www.clockworkmod.com/rommanager
How to install through Android Emulator on the device: http://forum.xda-developers.com/showthread.php?t=1739426
scroll down to the "Third, alternate if unfamiliar with adb commands" option and follow directions.
Beware that once you install this version of CWM, your previous nandroid backups will not work, as they will get md5 mismatch. If you want to go back to the older version of CWM, simply use the method you used when you first flashed CWM (via Odin). I experienced the same thing, so I had to do some research before I flashed CM10. Hope that helped!
Sent from my Galaxy Nexus using Tapatalk 2
amgpower63 said:
That's an older version. You need the newest one, which is 5.8.4.7. Download the img file from the website and flash through android emulator.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Or update through ROM manager...
Sent from my Nexus 7 using xda premium
defnow said:
Or update through ROM manager...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
That works too. But for some reason, my device wasn't listed in the app so I had to go through the other process ):

[Q] TWRP 2.3.1.1 issues

Noob problem
Every time I try to flahs a new rom i get errors.
in wipe and install its getting (E:Unable to mount '/efs')
Now i switched from CWM recovery to TWRP for the reason that their latest update gave me to much trouble and ive been flashing roms on my sgs2 since gingerbread..
I'm not trying to cause problems just trying to get a fix on the situation.
I can always restore back to my last backup but im a flashaholic and sucks that im stuck on the same rom for so long
please help and its ok if i get flamed as long as i get a solution
From the top of my head, I would suggest to downgrade
the TWRP to ver. 2.2.2.0
Try that and see how it goes.
Good luck!
premiatul said:
From the top of my head, I would suggest to downgrade
the TWRP to ver. 2.2.2.0
Try that and see how it goes.
Good luck!
Click to expand...
Click to collapse
+1
Sent from my SGH-T989 using xda app-developers app
premiatul said:
From the top of my head, I would suggest to downgrade
the TWRP to ver. 2.2.2.0
Try that and see how it goes.
Good luck!
Click to expand...
Click to collapse
Flashed and backed up on 2.3.1.1. Absolutely no issues. AOKP JB 10-23 and the king kang kernel.
Sent from my SGH-T989 using xda premium
I also updated to 2.3.1.1 and flashed aokp newest build + gaaps with no issues. Its a great recovery for the t989.
Sent from my Galaxy Nexus using xda premium
Hmm weird I just tried aokp jb and nothing I keep.getting the same error and then just bootloops
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
So figured out I can flash any ics ROM with no issues. I still get the same error but the ROM flashes with no issues.as soon as I try a jb ROM it doesn't work just bootloops after the flash.. Any reason why? Love twrp wish there's a solution
Sent from my SGH-T989 using xda app-developers app
I guess no one has an answer.I'm believing to think it's my phone and not the recovery tool
Sent from my SGH-T989 using xda app-developers app
Have you tried a different download? Try using a different browser to dl and flash again. Or you could try using an older version of TWRP if the newer one isn't working well on your phone.
Sent from my beastly Galaxy S 2.

[Q] Bootloops!

Hi people! I'm new to flashing Tmo's S2, and I am getting bootloops everytime and with every rom out there, my phone is rooted and latest rom manager plus recovery installed, running ics, any suggestion on how to solve it? had tried like 3 different JB roms! Thanks
What recovery are you using?
Sent from my SAMSUNG-SGH-T989 using xda premium
android88 said:
What recovery are you using?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I'm using latest CWM, always update recovery via rom manager.
fernkomoyo said:
I'm using latest CWM, always update recovery via rom manager.
Click to expand...
Click to collapse
Try using TWRP 2.3.3.0 as your recovery system instead, it's more up to date and is reliable. Just flash it through Odin, afterwards, you should be able to install and boot the ROMs perfectly.
fernkomoyo said:
I'm using latest CWM, always update recovery via rom manager.
Click to expand...
Click to collapse
If you don't mind switching to TWRP as the guy above said, then I would switch. If you like CWM, then make sure you aren't using the super wipe scripts on CWM versions other than 5.0.X
Sent from my SAMSUNG-SGH-T989 using xda premium
Did you manage to solve it? i'm having the same issue with every rom i flash

[Q] flashing a rom without bricking?

I cant flash a rom and have it work. I have tried several ROMS like aokp, jedi, smooth, jellybeans, etc and they almost always brick. Jedi worked but google services crashed back to back to back to the point where i couldnt even use the phone. does anyone know of a 4.3 rom that works on att sgh-i317?? i basically went down the list on galaxynote2root.com and tried them all but no success.
I have root, have TWRP installed and flash the rom and it bricks. i factory reset first, then install and nothing.
any ideas?
All of the roms on this forum work.. What are your exact steps?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Kreateablaze said:
All of the roms on this forum work.. What are your exact steps?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Have they been tried on sgh-i317?
I did these exact steps:
Rooted phone and installed TWRP recovery
put AOKP Rom on SD card and booted into recovery mode
Wiped/Factory reset through recovery
rebooted into recovery
installed AOKP ROM
booted and bricked- hangs at "X" aokp bootup screen
Have you installed gapps after flashing an aosp rom? I am running carbon rom right now... Earlier today I was on aokp. I have used them all and I have a I317. An att note 2
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Kreateablaze said:
Have you installed gapps after flashing an aosp rom? I am running carbon rom right now... Earlier today I was on aokp. I have used them all and I have a I317. An att note 2
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
does not having the gapps installed prevent the phone from booting? ive booted a rom before without gapps and it booted.
was there something wrong with my steps? did you use the aokp milestone or nightlies? where did you get the carbon rom? its all good?
I used the latest aokp nightly. And right now I'm running the newest carbon nightly. I got it from the op of the carbon thread.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Kreateablaze said:
I used the latest aokp nightly. And right now I'm running the newest carbon nightly. I got it from the op of the carbon thread.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
What were your steps? what recovery were you using? im just so confused why my phone bricks every time
I'm using the latest version of twrp recovery. Try updating it?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Download your rom and gapps again using a PC...
Then place the files to your SD using a card adapter if no USB connection is possible...
Then fully wipe the device again from within the latest version of TWRP recovery and flash the new downloads ...
You may have a bad flash ...and you are not bricked...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
gregsarg said:
Download your rom and gapps again using a PC...
Then place the files to your SD using a card adapter if no USB connection is possible...
Then fully wipe the device again from within the latest version of TWRP recovery and flash the new downloads ...
You may have a bad flash ...and you are not bricked...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did those exact steps and it did not work. i tried flashing pac man rom the last time and it got stuck in a boot loop too. I think there are some files that are corrupt or some temp files somewhere that are preventing a successful flash. my binary flash count was 9. and that was just on this run, ive tried flashing several times before. each time the only way to recover it is hooking the phone up to a pc and using kies to flash back to stock firmware. this sucks.
What version of twrp are you using? I have never had this issue you are having and I have flashed every rom on this forum for our device.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
igotta67bug said:
I did those exact steps and it did not work. i tried flashing pac man rom the last time and it got stuck in a boot loop too. I think there are some files that are corrupt or some temp files somewhere that are preventing a successful flash. my binary flash count was 9. and that was just on this run, ive tried flashing several times before. each time the only way to recover it is hooking the phone up to a pc and using kies to flash back to stock firmware. this sucks.
Click to expand...
Click to collapse
9 counts ??
Uh....yeh...not right ...
Have you messed with device partitions in ODIN ??
If so...something is definitely wrong ...
At this point ...you may want to consider a full return to stock and allow the PIT to properly restore your partitions..
Just follow the return to stock guide (sticky )...in the general section ..
Once restored to stock with a corrected flash counter you can begin again using CF auto root as your root method..
It sounds as if you have root issues and possible partition damage...
One other step you can try first is to boot into download mode and re-root using CF...
That may help....but certainly won't hurt anything...then attempt a clean flash again..
If it fails ...then the return to stock and rooting again seems prudent ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Ok ill try that. When I do the sticky method is that different than using kies to flash to stock? Kies is supposed to wipe everything and reload stock firmware. I agree the partitions are corrupt somewhere
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
igotta67bug said:
Ok ill try that. When I do the sticky method is that different than using kies to flash to stock? Kies is supposed to wipe everything and reload stock firmware. I agree the partitions are corrupt somewhere
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Are u wiping data and system as well in recovery. If you're running TW and u switch to AOSP without wiping everything.....the results most likely wouldn't b pretty
Sent from my SAMSUNG-SGH-I317 using Xparent Skyblue Tapatalk 2
I'm doing a factory reset--> "swipe to wipe". Do I need to do something else?
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Kies is not the method I use in returning to stock...as I don't trust it..
Odin is my first choice ...
Using Odin to flash a factory rom will wipe everything as well ...and is far more reliable ...IMHO...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
gregsarg said:
9 counts ??
Uh....yeh...not right ...
Have you messed with device partitions in ODIN ??
If so...something is definitely wrong ...
At this point ...you may want to consider a full return to stock and allow the PIT to properly restore your partitions..
Just follow the return to stock guide (sticky )...in the general section ..
Once restored to stock with a corrected flash counter you can begin again using CF auto root as your root method..
It sounds as if you have root issues and possible partition damage...
One other step you can try first is to boot into download mode and re-root using CF...
That may help....but certainly won't hurt anything...then attempt a clean flash again..
If it fails ...then the return to stock and rooting again seems prudent ...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK, so i followed these steps perfectly and it did not work. GOt Stuck in a boot loop again. something is corrupt. i used the latest version of clockwork mod and tried to install the latest AOKP nightlies. :crying:
Alright ...
Do you mean that you returned to stock ??
And have rooted again ...??
If yes ..we can dig deeper ...and if not ...proceed with full unroot...g
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
I used the sticky on turning your phone back to stock which used odin. I followed that list perfectly which said to flash stock using odin, root using cf then using triangle away, then super user to fully unroot. Then I installed clockword mod recovery, booted to recovery mode, cleared all cache and davlik and factory reset again, then installed the aokp and it got stuck in a boot loop
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Here's what I do with twrp when flashing a rom.
Go to wipe menu and then advanced wipe and select dalvik, cache, data, system and internal(optional). I do it three times to make sure. then flash your rom with gapps (if aosp)

Something strange with my gnex...

Sorry for my english, I`m quite bad... I was wondering if someone could help me with my gnex, Some months ago i bought one, it was rooted and with the bootloader unlocked. Í´ve changed the ROM so many times and then i decided to go back to stock. The problem that I have is that my phone is only working with 4.0.4, I´ve tried everything... odin, the tollkit, re-locking the bootloader and trying to update by OTA, nothing works. When I try to update it to 4.1 or another version it keeps on bootloop. I´ve tried changin the baseband, kernel, recovery, tried all official ROMS whit toolkit... Only 4.0.4, cm9 it works but when i try to uptade it goes on bootloop again...
I don´t know what to do. I`m sorry if I`m posting in the wrong section...
When you was flashing ROM's did you do a factory reset?
skhjpz said:
When you was flashing ROM's did you do a factory reset?
Click to expand...
Click to collapse
Yes, of course. Toolkit os flashing the userdata.img and erasing all. Then in recovery I try the factory reset but it keeps con bootloop...
How do you try to update? What ROM do you want to flash? Which recovery do you use? Using which method do you try to update?
Sent from my Galaxy Nexus using xda app-developers app
mrgnex said:
How do you try to update? What ROM do you want to flash? Which recovery do you use? Using which method do you try to update?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I've tried with all methods. OTA over official 4.0.4, toolkit, odin. Nothing.
I want to update it, I don't like ICS. I've tried all types of versions, only ICS ROMs are working. I've tried with diferent recoverys also. Nothing...
I'm desperate
Sent from my Galaxy Nexus using xda app-developers app
Did you try fastboot? That erases everything and has the highest chance of succes.
Sent from my Galaxy Nexus using xda app-developers app
mrgnex said:
Did you try fastboot? That erases everything and has the highest chance of succes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Tried too, not working. The toolkit uses Fastboot and ADB. Nothing...
Sent from my Galaxy Nexus using xda app-developers app
Dont use toolkits. Just use fastboot manually.
Sent from my Galaxy Nexus using xda app-developers app
mrgnex said:
Dont use toolkits. Just use fastboot manually.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Not working... i've tried every possible method. Nothing...
Sent from my Galaxy Nexus using xda app-developers app
My maguro/gnex happen like this as well.
What i do, copy any custom rom(4.4 latest) into sd/data when in ics rom.
Then i flash cwm recovery using adb in fastboot
Then i boot into cwm then flash that custom rom zip file.
And it works.
Or you can find stock jdq39/4.3 in zip and flash that.
Sent from my Galaxy Nexus using xda app-developers app
vocyber said:
My maguro/gnex happen like this as well.
What i do, copy any custom rom(4.4 latest) into sd/data when in ics rom.
Then i flash cwm recovery using adb in fastboot
Then i boot into cwm then flash that custom rom zip file.
And it works.
Or you can find stock jdq39/4.3 in zip and flash that.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Not working . I did it too, only ICS ROMs...
Sent from my Galaxy Nexus using xda app-developers app
and what custom rom that you just try?
still stuck in bootloop?
did u fullwipe/factory reset before flash the rom in cwm/twrp?
vocyber said:
and what custom rom that you just try?
still stuck in bootloop?
did u fullwipe/factory reset before flash the rom in cwm/twrp?
Click to expand...
Click to collapse
I tried CM11 and other 2 based in Kit Kat.
The others were based in 4.1 and 4.2/4.3
Yes, of course. I always make a clean install.
Sent from my Galaxy Nexus using xda app-developers app
mind you try the paranoid rom? its aosp and i never stuck in bootloop in this rom.
vocyber said:
mind you try the paranoid rom? its aosp and i never stuck in bootloop in this rom.
Click to expand...
Click to collapse
I will give a try... but it won't work. Like the others.
It's something really strange, it never happened to me until now...
Sent from my Galaxy Nexus using xda app-developers app
Is not working... I've tried with two diferent versions and nothing... help please...
Sent from my Galaxy Nexus using xda app-developers app
Did you try installing the stock factory 4.3 ROM from Google?
Search the forum and you will find the link, download and use fastboot it even the toolkit and install that. That will erase everything and should have nothing to do with your recovery or root.
But you will end up with stock 4.3 ROM
Sent from my Galaxy Nexus using Tapatalk
niamul said:
Did you try installing the stock factory 4.3 ROM from Google?
Search the forum and you will find the link, download and use fastboot it even the toolkit and install that. That will erase everything and should have nothing to do with your recovery or root.
But you will end up with stock 4.3 ROM
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yes yes, the 4.3 ROM factory rom, I've tried with 4.2.2 too and the 4.1, only 4.0.4 is working properly...
Sent from my Galaxy Nexus using xda app-developers app
Tried changing to twrp? Have you upgraded your recovery to the newest version?
Maybe you're on a 3 year old recovery
Sent from my Galaxy Nexus using Tapatalk
niamul said:
Tried changing to twrp? Have you upgraded your recovery to the newest version?
Maybe you're on a 3 year old recovery
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm always on the newer recoverys, I've tried with CWM and TWRP. Nothing
Sent from my Galaxy Nexus using xda app-developers app

Categories

Resources