I rooted my kindle fire using kfu 9.8. As of this moment when I install roms they do not boot up and they stay at the boot logo. I dont know if it has to do with TWRP or the roms, but I have tried 2 cm10 roms and one AOSP 4.2.2 rom. I will tell you exactly what I did.
1. Rooted with kfu
2. went straight to recovery, flashed the aosp rom + google apps
3. Booted up and it stayed at the boot screen
4. Tried another rom, put it onto the device through usb mounting with twrp
5. Still stuck at boot logo
6. Tried the last rom but still stuck!!
After that I tried to flash back to stock using this
(doesnt let me post a link if requested I will pm)
But twrp gave an error and it did not install, it said somewhere an error doesnt matter and you would boot up fine but I didnt
Between installing all Roms I wiped cache, dalvik, and factory reset.
Thanks in advnce!
EDIT
Used this to try to bring to stock
theunlockr DOT com/2012/10/29/how-to-unroot-the-amazon-kindle-fire
Used these roms (all on xda)
/showthread.php?t=2100963
/showthread.php?t=2041694
cant find the third rom
EDIT
I have no problem using adb or fastboot so feel free to try and fix my problem with those.
Ilia Goro said:
But twrp gave an error and it did not install it said somewhere an error doesnt matter and you would boot up fine but I didn't
Click to expand...
Click to collapse
It would be very helpful to know exactly what error you are receiving.
soupmagnet said:
It would be very helpful to know exactly what error you are receiving.
Click to expand...
Click to collapse
assert failed:getprop ("ro.product.device") == "blaze" l l
E:unknown command {err_string}
getprop ("ro.product.device") == "blaze"
E:unknown command {err_string}
E:Error in sdcard/update.zip
Status 7
Error flashing zip /sdcard/update.zip
Updating partition details
That is exactly what I get while flashing
Im sorry for making the topic and/or wasting your time, before installing the rom I wiped every single thing possible and it succesfully nstalled.
I have no problem if you lock.
Ilia Goro said:
assert failed:getprop ("ro.product.device") == "blaze" l l
E:unknown command {err_string}
getprop ("ro.product.device") == "blaze"
E:unknown command {err_string}
E:Error in sdcard/update.zip
Status 7
Error flashing zip /sdcard/update.zip
Updating partition details
That is exactly what I get while flashing
Im sorry for making the topic and/or wasting your time, before installing the rom I wiped every single thing possible and it succesfully nstalled.
I have no problem if you lock.
Click to expand...
Click to collapse
Any update on this? I'm getting the same issue on mine.
Runaround said:
Any update on this? I'm getting the same issue on mine.
Click to expand...
Click to collapse
I had the same issue using TWRP 2.4.x.x. I was able to return to stock by downgrading to TWRP 2.2.2.1. Good luck.
Sent from my Nexus 7 using xda app-developers app
philipsw said:
I had the same issue using TWRP 2.4.x.x. I was able to return to stock by downgrading to TWRP 2.2.2.1. Good luck.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
By any chance, can you please give me the link to the TWRP 2.2.2.1?
TIA.
votinh said:
By any chance, can you please give me the link to the TWRP 2.2.2.1?
TIA.
Click to expand...
Click to collapse
http://www.teamw.in/project/twrp2/79
Sent from my Nexus 7 using xda app-developers app
philipsw said:
http://www.teamw.in/project/twrp2/79
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks philipsw, I found the 2.2.2.1 flashable zip file too.
2.2.2.1 zip?
votinh said:
Thanks philipsw, I found the 2.2.2.1 flashable zip file too.
Click to expand...
Click to collapse
where did you find the zip file?
TWRP
You need TWRP 2.6.3.1 too install KitKat Roms here is the link for your first gen fires you need the otter.img
TWRP
PLEASE HELP! Kindle Fire 1st Gen. I've looked everywhere for answers
Okay, This is the first time Ive ever posted anything on this site. Normally I just search for answers and people usually have already solved the problem so I just go off what other people post. But now I cannot seem to find any fix I rooted my Kindle Fire 1st Generation. I was running TWRP 2.2.2. and a Hellfire ROM. I went on vacation and left my Kindle at home. When I got back, most of my apps weren't working properly and my keyboard was glitching so I tried to update my ROM. It was unsuccessful. So I thought maybe if I upgraded my TWRP Recovery to the latest version It would fix the problem... I was wrong. Whenever I try to flash any ROM I get an error like this... (E:Error executing updater binary) I have searched for answers for about a month now and nothing seems to work. I dont know what to do and I feel like crying. Can someone please help me? Please?
Feedback
DroidLover93 said:
Okay, This is the first time Ive ever posted anything on this site. Normally I just search for answers and people usually have already solved the problem so I just go off what other people post. But now I cannot seem to find any fix I rooted my Kindle Fire 1st Generation. I was running TWRP 2.2.2. and a Hellfire ROM. I went on vacation and left my Kindle at home. When I got back, most of my apps weren't working properly and my keyboard was glitching so I tried to update my ROM. It was unsuccessful. So I thought maybe if I upgraded my TWRP Recovery to the latest version It would fix the problem... I was wrong. Whenever I try to flash any ROM I get an error like this... (E:Error executing updater binary) I have searched for answers for about a month now and nothing seems to work. I dont know what to do and I feel like crying. Can someone please help me? Please?
Click to expand...
Click to collapse
Just need a little more info... What TWRP version are you running?? What android version are you trying to flash??
lj50036 said:
Just need a little more info... What TWRP version are you running?? What android version are you trying to flash??
Click to expand...
Click to collapse
I'm currently running TWRP v2.6.0.0
And I'm trying to flash ANY android version.
So far I have tried flashing the latest HellFire, Kit Kat, and Jellybean Stock Roms, All have been unsuccessful.
All I want is to be able to use my kindle without wanting to smash it to pieces, lol. I'm tired of getting booted off the internet every 2 minutes and my apps to force closing on me.
DroidLover93 said:
I'm currently running TWRP v2.6.0.0
And I'm trying to flash ANY android version.
So far I have tried flashing the latest HellFire, Kit Kat, and Jellybean Stock Roms, All have been unsuccessful.
All I want is to be able to use my kindle without wanting to smash it to pieces, lol. I'm tired of getting booted off the internet every 2 minutes and my apps to force closing on me.
Click to expand...
Click to collapse
And you are using the firefirefire utility??
lj50036 said:
And you are using the firefirefire utility??
Click to expand...
Click to collapse
Yes, I believe so.
TWRP
DroidLover93 said:
Yes, I believe so.
Click to expand...
Click to collapse
We need to get you on the latest version of twrp....http://techerrata.com/browse/twrp2/blaze
Go here and get version 2.6.3.1 make sure your get the otter.img as the blaze is for the 2nd gen fire....
Let me know if you need any help with this.. Let me know when you have it installed....Thx lj
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows....
@lj50036
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows...
Thank you! I will do this now and I will let you know when I have it installed. Do I just flash it through recovery or?...
Also, I do not have fastboot and adb drivers on my PC. Where do I go to get them? Running Windows 7
Feedback
DroidLover93 said:
@lj50036
Do you have fastboot and adb drivers for your PC?? Do you have fastboot.exe and adb.exe... I assume your running windows...
Thank you! I will do this now and I will let you know when I have it installed. Do I just flash it through recovery or?...
Also, I do not have fastboot and adb drivers on my PC. Where do I go to get them? Running Windows 7
Click to expand...
Click to collapse
Check this forum for your fastboot adb driver needs...http://forum.xda-developers.com/showthread.php?t=2588979
Hold on a sec I will make you a flashable recovery zip for easy of installation...
TWRP 2.6.3.1
Here is a flashable zip twrp recovery v 2.6.3.1... Just flash it than do a reboot before trying to enter recovery... Let me know if that fastboot/adb stuff is working for you we will still need adb drivers and adb installed on your PC...Thx lj
View attachment 2578399
lj50036 said:
Here is a flashable zip twrp recovery v 2.6.3.1... Just flash it than do a reboot before trying to enter recovery... Let me know if that fastboot/adb stuff is working for you we will still need adb drivers and adb installed on your PC...Thx lj
View attachment 2578399
Click to expand...
Click to collapse
Thanks! Okay so TWRP update was successful. Then I followed the link for ADB and fastboot. I installed them to PC. Now, just to be clear.. Was I supposed to do that with the USB connected to my device? or was that just for my PC? I just dont want to mess anything up.
Related
I recently installed cm10 on my fathers S3 and everything went smooth until root checker said I did not have root access. I dont see how I missed it, I used the steps from the guide on androidauthority.com as well as the steps from the links the guide provided to install clockworkmod and cm10. My S3 is rooted with cm10 with no issue. but my fathers isnt after the install when i used the same guide. Is there a way to root on cm10 without having to wipe and install the stock rom and then root?
simba33 said:
I recently installed cm10 on my fathers S3 and everything went smooth until root checker said I did not have root access. I dont see how I missed it, I used the steps from the guide on androidauthority.com as well as the steps from the links the guide provided to install clockworkmod and cm10. My S3 is rooted with cm10 with no issue. but my fathers isnt after the install when i used the same guide. Is there a way to root on cm10 without having to wipe and install the stock rom and then root?
Click to expand...
Click to collapse
Just reflash the CM10 zip, its pre-rooted. I don't know why its saying you're not rooted in the first place really. Do you see the "Superuser" app in the app drawer?
prscarp said:
Just reflash the CM10 zip, its pre-rooted. I don't know why its saying you're not rooted in the first place really. Do you see the "Superuser" app in the app drawer?
Click to expand...
Click to collapse
thats the weird part! haha I see super user, it opens and everything but it never pops up when i open apps that require root, and root checker says it isnt rooted. Ive wiped and installed CM10 twice, as well as the superuser.zip file the guide says to install with clockworkmod.
In the superuser app, try updating the su binary. Maybe that will fix it.
prscarp said:
In the superuser app, try updating the su binary. Maybe that will fix it.
Click to expand...
Click to collapse
I dont know why it fails but it doesnt like me getting root access. failed at: "gaining root access.... Fail!" when i clicked update
everything is green and says okay until gaining root access then i get the red fail! I took a screenshot but I dont have enough posts to insert the image
What recovery did you install?
I would redownload the CM10 zip, put it on your sd card, reboot into recovery, make a nandroid if you prefer, wipe system, dalvik, and cache, then flash the newly downloaded CM10 zip and gapps again.
This is definitely a strange problem lol
tonymtl said:
What recovery did you install?
Click to expand...
Click to collapse
the zip file says cm-10-20120925-NIGHTLY-d2att.zip
prscarp said:
I would redownload the CM10 zip, put it on your sd card, reboot into recovery, make a nandroid if you prefer, wipe system, dalvik, and cache, then flash the newly downloaded CM10 zip and gapps again.
This is definitely a strange problem lol
Click to expand...
Click to collapse
dang it didnt want to but oh well I'll give it a shot in a few. and yes very strange i never have the normal problems -__-
simba33 said:
the zip file says cm-10-20120925-NIGHTLY-d2att.zip
Click to expand...
Click to collapse
Thats the CM10 zip. Are you using clockwork mod recovery? or TWRP? I haven't had any issues with TWRP.
simba33 said:
dang it didnt want to but oh well I'll give it a shot in a few. and yes very strange i never have the normal problems -__-
Click to expand...
Click to collapse
As long as you dont wipe data you won't lose anything. The only effect this will have is, hopefully, fix root.
prscarp said:
Thats the CM10 zip. Are you using clockwork mod recovery? or TWRP? I haven't had any issues with TWRP.
As long as you dont wipe data you won't lose anything. The only effect this will have is, hopefully, fix root.
Click to expand...
Click to collapse
I'm using Clockworkmod recovery as advised by the guide.
ok i'll give it a shot in a few minutes
Did you flash any custom recovery ??? That cm10 doesn't install it. Also get a more recent cm10 at get.cm
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
What version of cwm?
prscarp said:
Thats the CM10 zip. Are you using clockwork mod recovery? or TWRP? I haven't had any issues with TWRP.
As long as you dont wipe data you won't lose anything. The only effect this will have is, hopefully, fix root.
Click to expand...
Click to collapse
ok well i get an error:
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
E:Error in /sdcard/cm-10-20121009-NIGHTLY-d2att.zip
(status 7)
installation aborted
I downloaded the 2nd latest which was added to the site yesterday from the other guys site he suggested. I got this same error on my phone and somewhere when googling someone said download notepad++ and erase the top line within the zip file and it installed for me. but i shouldnt have to do that. whats going on? i wiped everything you told me except factory/data
tonymtl said:
Did you flash any custom recovery ??? That cm10 doesn't install it. Also get a more recent cm10 at get.cm
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
What version of cwm?
Click to expand...
Click to collapse
Yes i ave clockworkmod recovery and I downloaded that cm-10 a couple of weeks ago and I have root. its the same zip. but I downloaded the more recent, (2nd most recent on the site you referred) and it wont install as i stated in my previous post
simba33 said:
ok well i get an error:
assert failed: getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att"
E:Error in /sdcard/cm-10-20121009-NIGHTLY-d2att.zip
(status 7)
installation aborted
I downloaded the 2nd latest which was added to the site yesterday from the other guys site he suggested. I got this same error on my phone and somewhere when googling someone said download notepad++ and erase the top line within the zip file and it installed for me. but i shouldnt have to do that. whats going on? i wiped everything you told me except factory/data
Click to expand...
Click to collapse
That has also never happened to me lol. Right before you flash the zip, select the "Toggle script asserts" option then try to flash.
A little explaination: When you go to flash the zip, it checks your current build.prop to make sure you're flashing the right rom to the right device. Since we wiped system before flashing, the build.prop is gone and it is unable to check. TWRP might not check which is why it has never happened to me. I don't know for sure that this is the case but I am just guessing.
You need to update recovery.
prscarp said:
That has also never happened to me lol. Right before you flash the zip, select the "Toggle script asserts" option then try to flash.
A little explaination: When you go to flash the zip, it checks your current build.prop to make sure you're flashing the right rom to the right device. Since we wiped system before flashing, the build.prop is gone and it is unable to check. TWRP might not check which is why it has never happened to me. I don't know for sure that this is the case but I am just guessing.
Click to expand...
Click to collapse
I tried the toggle idea and it didnt work, can you link me to a TWRP download? this is getting annoying lol I appreciate the help so far though
lol well this is annoying.
http://www.teamw.in/project/twrp2/104
Here is the link to TWRP for the AT&T SGS3. Grab the .img file near the bottom and flash it with fastboot. I assume you are familiar with fastboot?
fastboot flash recovery openrecovery-twrp-2.2.2.0-d2att.img
I love this recovery btw, so much easier to use than CWM
prscarp said:
lol well this is annoying.
http://www.teamw.in/project/twrp2/104
Here is the link to TWRP for the AT&T SGS3. Grab the .img file near the bottom and flash it with fastboot. I assume you are familiar with fastboot?
fastboot flash recovery openrecovery-twrp-2.2.2.0-d2att.img
I love this recovery btw, so much easier to use than CWM
Click to expand...
Click to collapse
uhm actually no im not familiar with it. ive heard of it but not sure how it works, i just tried doing my own research on it for about 20 minutes and still not sure how it works. can you point me in the right direction here?
You will need to get the android sdk, run it and install the tools. You should then have a platform-tools folder that includes fastboot.exe. place the recovery img in that directory, open a command prompt to that directory, put your phone in fastboot mode and run the command I wrote above.
Sorry about being brief about it, I'm on my phone right now. I can help more later when I'm at a pc.
prscarp said:
You will need to get the android sdk, run it and install the tools. You should then have a platform-tools folder that includes fastboot.exe. place the recovery img in that directory, open a command prompt to that directory, put your phone in fastboot mode and run the command I wrote above.
Sorry about being brief about it, I'm on my phone right now. I can help more later when I'm at a pc.
Click to expand...
Click to collapse
what is fastboot mode? is that download mode? lol sorry but I havent messed with fastboot at all. Ive rooted a bunch of phones and flashed quite a few but never worked with fastboot
Ok so I am not the greatest when it comes to flashing ROMs but so far I have managed to get by.
I went from MMuzzyROM 4.2.2 to [ROM] [4.3] [JSS15J]. I wiped my data/dalvick/cache, flashed the new ROM and Gaaps and installed SuperuserSU. As of right now SuperuserSU will not install and I get an installation error. And when using Rom Manager I can not reboot into recovery. And there is a bit more, when I try and boot into recovery from the holding the volume and power button down, after choosing recovery the android with the error shows up. From what I understand is that the 4.3 rom I flashed removed the stock recovery, but I am just confused how to get back recovery.
My main question is did I loose root and how can I get the recovery option back.
Thanks, Noel
knoll126 said:
Ok so I am not the greatest when it comes to flashing ROMs but so far I have managed to get by.
I went from MMuzzyROM 4.2.2 to [ROM] [4.3] [JSS15J]. I wiped my data/dalvick/cache, flashed the new ROM and Gaaps and installed SuperuserSU. As of right now SuperuserSU will not install and I get an installation error. And when using Rom Manager I can not reboot into recovery. And there is a bit more, when I try and boot into recovery from the holding the volume and power button down, after choosing recovery the android with the error shows up. From what I understand is that the 4.3 rom I flashed removed the stock recovery, but I am just confused how to get back recovery.
My main question is did I loose root and how can I get the recovery option back.
Thanks, Noel
Click to expand...
Click to collapse
4.3 is buggy with root right now. You can use rom manager to reflash cwmrecovery or you can use goomanager to install twrp
dnewha sees
NyPlaya513 said:
4.3 is buggy with root right now. You can use rom manager to reflash cwmrecovery or you can use goomanager to install twrp
Click to expand...
Click to collapse
I try to reflash but doesn't seem to work.
knoll126 said:
I try to reflash but doesn't seem to work.
Click to expand...
Click to collapse
USE TWRP!
When trying to flash CWR I get an error message. I am pretty sure I am unrooted without an option for recovery and stuck on 4.3?
beekay201 said:
USE TWRP!
Click to expand...
Click to collapse
Ok I guess I am just too confused. Downloading TWRP gives me an image file which I don't understand how to install, because I thought I need recovery to do it? When in fastboot I can select recovery but I get the error android.
knoll126 said:
When trying to flash CWR I get an error message. I am pretty sure I am unrooted without an option for recovery and stuck on 4.3?
Click to expand...
Click to collapse
what error message?
what's the fastboot command you're using to flash recovery.
about loosing your recovery after flashing/boot/reboot OS for the first time, it's probably the same that 4.2 had
/system/recovery-from-boot.p
/system/install-recovery.sh
beekay201 said:
what error message?
what's the fastboot command you're using to flash recovery.
about loosing your recovery after flashing/boot/reboot OS for the first time, it's probably the same that 4.2 had
/system/recovery-from-boot.p
/system/install-recovery.sh
Click to expand...
Click to collapse
The error message is when using the clockwork mod app to install the recovery, once downloaded it states an error has occurred. Then when trying TWRP I am following these steps I get "fastboot is not a recognizable command..." I am pretty lost as you can tell and am thankful for the help.
knoll126 said:
The error message is when using the clockwork mod app to install the recovery, once downloaded it states an error has occurred. Then when trying TWRP I am following these steps I get "fastboot is not a recognizable command..." I am pretty lost as you can tell and am thankful for the help.
Click to expand...
Click to collapse
*facepalm*
WHY you people don't read the frakkin stickies?!?!?
http://forum.xda-developers.com/showthread.php?t=1812959
beekay201 said:
*facepalm*
WHY you people don't read the frakkin stickies?!?!?
http://forum.xda-developers.com/showthread.php?t=1812959
Click to expand...
Click to collapse
Mainly because I thought if I had rooted my device and done all this once, I should remember how to do it again. But through ignorance I thought I could and be able to remember the steps and what not. I'll read through it and figure it out, it was just a moment of panic of losing the option of recovery that I have had for a long time and not being able to use it means (or I think it means) I am just stuck of 4.3 for a bit and hopefully the ROM isn't too bad.
when i tried to install d update.zip the teminal is showing this:
Installing ‘/sdcard/update.zip
Checking for MD5 file …
Skipping MD5 check: no MD5 file found (True, there isn’t one in the ZIP file)
assert failed: getprop(“ro.product.device”) == “blaze” ||
E:unknown command [err_string]
getprop(“ro.product.device”) == “blaze”
E:unknown command [err_string]
E:Error executing updater binary in zip ‘/sdcard/update.zip’
Error flashing zip ‘/sdcard/update.zip’
Updating partition details…
i am getting above errors.i Dont know why this kindle is making me irritated .Please anyone help me with this.,.
You are using new a version of TWRP, right?, like 2.6? I suggest to use TWRP 2.2
Sent from my Amazon Kindle Fire using xda app-developers app
404-Not Found said:
You are using new a version of TWRP, right?, like 2.6? I suggest to use TWRP 2.2
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Sorry for the late reply . it took some time for me for this (as i am a beginner) . I have install 2.2 and installed update.zip file
terminal lines:
verifying update.zip
verifying portions.,.
and i selected reboot
on reboot there is kindle fire logo(white and orange) and led light(orange) .,.,and thats all its not going any further
Did you factory reset first?
soupmagnet said:
Did you factory reset first?
Click to expand...
Click to collapse
yea soupmagnet i did it . i have swiped dalvik,cache and did a factory reset
kvnkarthik said:
yea soupmagnet i did it . i have swiped dalvik,cache and did a factory reset
Click to expand...
Click to collapse
You you get the same results with every ROM or just this one?
kvnkarthik said:
Sorry for the late reply . it took some time for me for this (as i am a beginner) . I have install 2.2 and installed update.zip file
terminal lines:
verifying update.zip
verifying portions.,.
and i selected reboot
on reboot there is kindle fire logo(white and orange) and led light(orange) .,.,and thats all its not going any further
Click to expand...
Click to collapse
That error happened to me before, but it was only when I used 2.6 Now I use 2.2
Sent from my Amazon Kindle Fire using xda app-developers app
soupmagnet said:
You you get the same results with every ROM or just this one?
Click to expand...
Click to collapse
i tried to install http://forum.xda-developers.com/showthread.php?t=2041694 rom onto kindle but i was stuck at the first itself.i had problem with rooting .i chked status of the device and unrooted it by using adb commands.i have installed twrp to revert kindle to stock and i am getting this. shall i try installing another ROM
kvnkarthik said:
i tried to install http://forum.xda-developers.com/showthread.php?t=2041694 rom onto kindle but i was stuck at the first itself.i had problem with rooting .i chked status of the device and unrooted it by using adb commands.i have installed twrp to revert kindle to stock and i am getting this. shall i try installing another ROM
Click to expand...
Click to collapse
By all means, yes, try a different ROM.
soupmagnet said:
By all means, yes, try a different ROM.
Click to expand...
Click to collapse
its showing an error when i try to enter recovery or fastboot mode .KFU is showing that adb status is online and device status as unknown. please tell me how could i got to TWRP mode.since adb is active i have tried to run in shell then it showed me an error -"exec '/system/bin/sh' failed:no such file or dicrectory(2)\"
kvnkarthik said:
its showing an error when i try to enter recovery or fastboot mode .KFU is showing that adb status is online and device status as unknown. please tell me how could i got to TWRP mode.since adb is active i have tried to run in shell then it showed me an error -"exec '/system/bin/sh' failed:no such file or dicrectory(2)\"
Click to expand...
Click to collapse
Hmm...as I suspected, that is the exact error you would receive if you tried to flash a ROM without first performing a factory reset (perhaps you were mistaken in thinking you did so?).
Your shell is unavailable, which means you cannot use it to change the bootmode to access recovery. However, if you have FireFireFire installed, you can use it to access custom recovery with the power button. If you don't have FireFireFire installed, then shame on you :wags finger: because you'll need a factory cable to get into fastboot so you can access recovery from there.
soupmagnet said:
Hmm...as I suspected, that is the exact error you would receive if you tried to flash a ROM without first performing a factory reset (perhaps you were mistaken in thinking you did so?).
Your shell is unavailable, which means you cannot use it to change the bootmode to access recovery. However, if you have FireFireFire installed, you can use it to access custom recovery with the power button. If you don't have FireFireFire installed, then shame on you :wags finger: because you'll need a factory cable to get into fastboot so you can access recovery from there.
Click to expand...
Click to collapse
:silly: :silly: i don't have a factory cable but i have usb cable and i have adb online .what can i do to get out from here
kvnkarthik said:
:silly: :silly: i don't have a factory cable but i have usb cable and i have adb online .what can i do to get out from here
Click to expand...
Click to collapse
Get a factory cable. That's all you can do...that is, without opening the device and shorting a certain pin to drop the device into usbboot so you can install a new bootloader and custom recovery, which would also put the device into fastboot mode afterwards...but I would suggest you steer clear from that option until you have no other choice.
soupmagnet said:
Get a factory cable. That's all you can do...that is, without opening the device and shorting a certain pin to drop the device into usbboot so you can install a new bootloader and custom recovery, which would also put the device into fastboot mode afterwards...but I would suggest you steer clear from that option until you have no other choice.
Click to expand...
Click to collapse
I have the same problem as the OP and I'm at my wits end with this. Curiously, everything works if I flash other rom like cm 10.1 but the update zip.
Any help would be greatly appreciated.
[email protected] said:
I have the same problem as the OP and I'm at my wits end with this. Curiously, everything works if I flash other rom like cm 10.1 but the update zip.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
did u get the same error ?? are u in TWRP ??
[email protected] said:
I have the same problem as the OP and I'm at my wits end with this. Curiously, everything works if I flash other rom like cm 10.1 but the update zip.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Did you read the thread that you posted this question in? How exactly are you having the same problem as the OP if you are able to flash any ROMs at all? Did you factory reset before flashing the update.zip? What error messages are you receiving? Do you have FireFireFire installed? What version of TWRP are you using? Do you have a factory cable?
Information like this is the key toward getting the help you need.
kvnkarthik said:
did u get the same error ?? are u in TWRP ??
Click to expand...
Click to collapse
Yes the very same error on your first post, TWRP v2.6.0
---------- Post added at 11:19 PM ---------- Previous post was at 11:02 PM ----------
soupmagnet said:
Did you read the thread that you posted this question in? How exactly are you having the same problem as the OP if you are able to flash any ROMs at all? Did you factory reset before flashing the update.zip? What error messages are you receiving? Do you have FireFireFire installed? What version of TWRP are you using? Do you have a factory cable?
Information like this is the key toward getting the help you need.
Click to expand...
Click to collapse
FFF is installed, TWRP v2.6 and I'm using the cable that came with my Galaxy S3. It's the same error that I am getting as the OP when flashing the update zip. And like what Ive said it works fine if I flash other ROM(in my case cm 10.1 and AOSP 4.2) that's why it baffles me.
[email protected] said:
Yes the very same error on your first post, TWRP v2.6.0
---------- Post added at 11:19 PM ---------- Previous post was at 11:02 PM ----------
FFF is installed, TWRP v2.6 and I'm using the cable that came with my Galaxy S3. It's the same error that I am getting as the OP when flashing the update zip. And like what Ive said it works fine if I flash other ROM(in my case cm 10.1 and AOSP 4.2) that's why it baffles me.
Click to expand...
Click to collapse
As mentioned previously, that error is from not performing a factory reset when flashing a ROM. As a result, you need a factory cable to enable fastboot, and in effect, access custom recovery so a factory reset can be performed.
Ok I Fixed it, COTR did it for me. @kvnkarthik if you could find a way to replace twrp with cotr that would solve your problem in flashing update.zip. Also I used the stock rom downloaded through kfu which is already in zip file, no need to rename it. Once you're in cotr, do a pre-flash wipe then install it and you're good to go. And no, I'm not using a factory cable just the one that I used on my phone.
Good luck. Hope it helps.
I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
Updating partition details...
Formatting Cache using make_ext4fs...
Done.
Wiping data without wiping /data/media ...
Done.
Updating partition details...
Installing '/sdcard/modsnstuff/ShinyROM_maguro_a
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
Installing Shiny ROM build 062114
for maguro
set_metadata_recursive: some changes failed
E: Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/modsnstuff/ShinyROM_
Updating partition details...
Click to expand...
Click to collapse
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?
inasm said:
I just bricked my galaxy nexus by trying to install Shiny ROM. I've got a (europe) maguro galaxy nexus which ran PA before, but I wanted to update as it became extremely slow at times.
Using TWRP v2.5.0.0 I did a factory reset(data, cache and dalvik wipe). I then tried to install ShinyROM, but it gave the following error:
I also put a new PA version on the phone, which gave a similar error.
I tried using the android toolkit to get into adb recovery and flash a new rom somehow. I did not succeed to install the drivers successfully, which is probably because I am not able to boot into android. I do not see how I can use the toolkit now, and since I barely know what it does and I would not know how to install the drivers.
What can I do to correctly install the new ROM, or at least get it to boot in any version of android?
Click to expand...
Click to collapse
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick
DR3W5K1 said:
Search for using fastboot to return to stock Google image(stock ROM). Then install custom recovery again and flash a ROM.
This phone is nearly impossible to brick
Click to expand...
Click to collapse
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.
inasm said:
Thanks a lot for the reply, trying it now. Apologies if I misused the word brick btw.
Click to expand...
Click to collapse
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.
DR3W5K1 said:
No need to apologize just didn't want you to think that you were stuck.
Also it will be very beneficial to study up on adb along with fastboot.
If you learn these two things you will be able to get out of just about any sticky situation you run into.
PS The most difficult part is getting the drivers installed.
Click to expand...
Click to collapse
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.
inasm said:
Would you happen to have a link to a post of some sort? I tried downloading the drivers, then installing them using device manager which didn't work, since windows said they were up to date already. All other guides I found to install the right drivers were with a working android version. Even the soft brick guides assume you have installed the drivers already.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!
DR3W5K1 said:
http://forum.xda-developers.com/showthread.php?t=1583801. Use this for driver issues.
http://forum.xda-developers.com/galaxy-nexus/general/how-to-return-to-stock-galaxy-nexus-t1626895 use this to return to stock.
With these guides you can fix it!
Click to expand...
Click to collapse
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!
inasm said:
The driver still seems to refuse to work. It keeps saying the latest driver is installed. I am using Windows 7 in stead of 8, which is why the guide might not apply 100% to me.
When I use the Android ToolKit and I try to flash the google ROM, it does detect a device in ADB MODE, and it gets the serial number, but it gets stuck on "Waiting for adb Mode". Does this mean the drivers are already correctly installed?
EDIT:
I remembered that I downloaded an old version of PA a long time ago using goo manager, which was still on my phone. ADB drivers are also installed now it seems, now I just have to install the 4.4 version correctly.
Thanks a lot for your help!
Click to expand...
Click to collapse
Your welcome but you should have been using fastboot instead of adb. For future reference they are two different things
Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code
z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.
z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112
Sorry for another nubby question but how do I get flash_all.bat?
z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?
_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah
z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.