how to root after cm10 install - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

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

Related

Newbie help with a failed (?) root

Hey guys, first of all I'm a complete n00b to all of this stuff, so please bear with me and consider using layman type language with me. Some of you may think I shouldn't even be messing with this stuff with my limited knowledge, but I'm determined to get the best out of my Galaxy Nexus and generally learn quickly and follow directions well.
Here's the bullet-point run-down of what happened:
- Bought a Galaxy Nexus that was "yakjuux" and wasn't getting updates.
- Read through a thread on here on how to flash to "yakju". Did so successfully.
- I then wanted to root since my device was already wiped from unlocking bootloader or flashing some partition or something
- Followed this thread (http://forum.xda-developers.com/showthread.php?p=19583168#post19583168)
- Rebooted, saw the "Superuser" app and thought I nailed it.
- Saw an update for Jellybean, it requested a reboot before install
- Upon reboot I got a dreaded android on it's back with a red exclamation, nearly wet myself. Took battery out, put back in, phone booted normally. It didn't update to JB anymore and when I check for updates it doesn't show. I figured it'll come around again.
- Went to "superuser" app to update, it said it "Failed!" upon trying to gain root access. Upon reading around, downloaded SU Update Fixer from the store, failed gaining root access. Read some more, downloaded "Root Checker" app and it said my device was not rooted.
So where do I go from here? I'm tempted to just follow the 'flash to yakju' thread again and go back to a clean ROM and forget rooting, but maybe there's something simple I can do from here.
** One side note, in that rooting thread I mentioned above, I did not understand step #7 (7. Using CWM recovery, install su.zip that you downloaded in step 1) too clearly. I didn't understand how my phone could even get the su.zip file. So after reading some other rooting methods, I copy and pasted the .zip into the "Internal Storage" drive under My Computer > Samsung Phone > Internal Storage. Then using CWM Recovery on my phone just selected to install it from sdcard (since the Gnex doesn't have an sdcard) and it seemed to be a success. But I'm not sure if that was right. I assumed it was since I got the Superuser app.
Another thing that felt kind of wrong is that, when I flashed to yakju, it wiped my phone clean. I expected rooting to do the same thing, but it didn't (I think because my bootloader was already unlocked?). So I'm not sure if that has anything to do with it either.
Please help. And remember to please refer to things in dummy form. I only know things that involve the above, like using the cmd and typing fastboot and flashing files from a directory, etc.
Thank you in advance.
BryMerc said:
Hey guys, first of all I'm a complete n00b to all of this stuff, so please bare with me and consider using layman type language with me. Some of you may think I shouldn't even be messing with this stuff with my limited knowledge, but I'm determined to get the best out of my Galaxy Nexus and generally learn quickly and follow directions well.
Here's the bullet-point run-down of what happened:
- Bought a Galaxy Nexus that was "yakjuux" and wasn't getting updates.
- Read through a thread on here on how to flash to "yakju". Did so successfully.
- I then wanted to root since my device was already wiped from unlocking bootloaderor or replace some partition or something
- Followed this thread (http://forum.xda-developers.com/showthread.php?p=19583168#post19583168)
- Rebooted, saw the "Superuser" app and thought I nailed it.
- Saw an update for Jellybean, it requested a reboot before install
- Upon reboot I got a dreaded android on it's back with a red exclamation, nearly wet myself. Took battery out, put back in, phone booted normally. It didn't update to JB anymore and when I check for updates it doesn't show. I figured it'll come around again.
- Went to "superuser" app to update, it said it "Failed!" upon trying to gain root access. Upon reading downloaded SU Update fixed from the store, failed gaining root access. Read some more, downloaded "Root Checker" app and it said my device was not rooted.
So where do I go from here? I'm tempted to just follow the 'flash to yakju' thread again and go back to a clean ROM and forget rooting, but maybe there's something simple I can do from here.
One side note, in that rooting thread I mentioned above, I did not understand step #7 (7. Using CWM recovery, install su.zip that you downloaded in step 1) too clearly. I didn't understand how my phone could even get the su.zip file. So after reading some other rooting methods, I copy and pasted the .zip into the "Internal Storage" drive under My Computer > Samsung Phone > Internal Storage. Then using CWM Recovery just selected to install it from sdcard (since the Gnex doesn't have an sdcard) and it seemed to be a success. But I'm not sure if that was right. I assume it was if I got the Superuser app.
Please help. And remember to please refer to things in dummy form. I only know things that involve the above, like using the cmd and typing fastboot and flashing .img files from a directory, etc.
Thank you in advance.
Click to expand...
Click to collapse
Re-install superuser the same way you did the first time. The OTA failed because you have a custom recovery installed. If you want to update to Jelly Bean, look into installing one of the JB ROMs in the development forums, or if you must have the OTA you'll have to flash the stock recovery and make sure everything else is stock as well. OTAs do not care if you are rooted or have an unlocked bootloader.
you can also install the OTA manually, heres my method
1) grab the link for yakju IMM76i > 4.1.1 from here: http://forum.xda-developers.com/showthread.php?t=1764536 and place that iin your sdcard. ALSO download this version of Superuser (chainfires one): http://download.chainfire.eu/197/SuperSU/CWM-SuperSU-v0.93.zip and place that in your sdcard too.
2) install clockworkmod recovery again the same way you did before, using fastboot flash recovery recovery.img, press vol down twice in the bootloader and go straight into the recovery.
3) install the OTA zip you downloaded and placed in your sdcard
4) clear cache and fix permissions (might not be necessary but you can do it just incase)
5) reboot, you should now have stock jellybean. the ClockworkMod recovery would be removed at this point because stock android has a file in system which replaces the stock recovery after every reboot, unless you delete that file.
6) go back into the bootloader, flash recovery as before and again boot straight into the recovery. this time flash the superuser zip you downloaded.
7) reboot. should be all sorted now
JaiaV said:
Re-install superuser the same way you did the first time. The OTA failed because you have a custom recovery installed. If you want to update to Jelly Bean, look into installing one of the JB ROMs in the development forums, or if you must have the OTA you'll have to flash the stock recovery and make sure everything else is stock as well. OTAs do not care if you are rooted or have an unlocked bootloader.
Click to expand...
Click to collapse
Thanks for the fast response.
So basically, I just copy and paste su.zip again into my Internal Storage on my computer. Put my phone into Recovery Mode, plug it in, find and install that su.zip again, and then reboot?
Also, this is something I didn't know: So if you are rooted, you cannot update "normally"? I will always have to flash over the latest ROM?
Thanks.
BryMerc said:
So basically, I just copy and paste su.zip again into my Internal Storage on my computer. Put my phone into Recovery Mode, plug it in, find and install that su.zip again, and then reboot
Click to expand...
Click to collapse
Yes.
BryMerc said:
Also, this is something I didn't know: So if you are rooted, you cannot update "normally"? I will always have to flash over the latest ROM?
Click to expand...
Click to collapse
JaiaV said:
OTAs do not care if you are rooted or have an unlocked bootloader.
Click to expand...
Click to collapse
They only care that the recovery and /system are stock, and even then (as I said) don't care if you're rooted. Rooting doesn't matter. Having a custom recovery does. They are not the same thing. Also, read through ||Nexus|| response.
IINexusII said:
you can also install the OTA manually, heres my method
1) grab the link for yakju IMM76i > 4.1.1 from here: http://forum.xda-developers.com/showthread.php?t=1764536 and place that iin your sdcard. ALSO download this version of Superuser (chainfires one): http://download.chainfire.eu/197/SuperSU/CWM-SuperSU-v0.93.zip and place that in your sdcard too.
2) install clockworkmod recovery again the same way you did before, using fastboot flash recovery recovery.img, but dont reboot this time, press vol down twice in the bootloader and go straight into the recovery.
3) install the OTA zip you downloaded and placed in your sdcard
4) clear cache and fix permissions (might not be necessary but you can do it just incase)
5) reboot, you should now have stock jellybean. the ClockworkMod recovery would be removed at this point because stock android has a file in system which replaces the stock recovery after every reboot, unless you delete that file.
6) go back into the bootloader, flash recovery as before and again boot straight into the recovery. this time flash the superuser zip you downloaded.
7) reboot. should be all sorted now
Click to expand...
Click to collapse
OK, thank you so much. I'm going to do exactly this. When I "fastboot flash" these over again, will they just replace the old ones? Or do I have to uninstall the ones already on my phone or something. I feel like it may get cluttered or something lol, sorry if that's stupid.
BryMerc said:
OK, thank you so much. I'm going to do exactly this. When I "fastboot flash" these over again, will they just replace the old ones? Or do I have to uninstall the ones already on my phone or something. I feel like it may get cluttered or something lol, sorry if that's stupid.
Click to expand...
Click to collapse
no, youre just reflashing the recovery which wont affect anything else. once you reboot it will revert back to the stock recovery anyway, so youll be able to get future OTA updates just fine.
edit: yes itll just be replacing the recovery, nothing else
IINexusII said:
no, youre just reflashing the recovery which wont affect anything else. once you reboot it will revert back to the stock recovery anyway, so youll be able to get future OTA updates just fine.
edit: yes itll just be replacing the recovery, nothing else
Click to expand...
Click to collapse
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
BryMerc said:
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
Click to expand...
Click to collapse
in clockwork mod recovery there should be a "Wipe Cache" option, and for fixing permissions go to "advanced" and "Fix Permissions"
BryMerc said:
Hey, I just installed the Jellybean but how do I do #4? Clear cache and fix permissions?
Click to expand...
Click to collapse
Wait, actually I don't think the JB installed now that I'm staring at the screen properly.
It went Installing update...
assert failed: file .........blah blah
Installation aborted.
Also, the drivers I thought I had for my phone seem to be messing up and in device manager it says "Full" with an exclamation point. I'm not sure why.
Sorry for the late responses as a n00b I'm stuck with 5 minute intervals here.
which country are you from?
IINexusII said:
which country are you from?
Click to expand...
Click to collapse
Canada.
I just tried reinstalling the drivers and everything and for some reason it's not working. I flash Clockwork Recovery, I see the JB.zip, but when I click to install it it says "assert failed" and has the dead Android. Not sure if it's a driver issue, but I redid the Universal Naked one I had before that worked.
BryMerc said:
Canada.
I just tried reinstalling the drivers and everything and for some reason it's not working. I flash Clockwork Recovery, I see the JB.zip, but when I click to install it it says "assert failed" and has the dead Android. Not sure if it's a driver issue, but I redid the Universal Naked one I had before that worked.
Click to expand...
Click to collapse
After selecting "Install zip from sdcard" I see an option "apply /sdcard/update.zip". Is that anything maybe I need to do or something?
check your PM

TWRP Recovery & Possible ROM Issues

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.

[Q] error installing update.zip

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.

[Q] F180S Cyanogen installation

Hello again everyone!
welp, somehow I managed to recover my phone using TWRP.
But I still want to install Cyanogenmod on my phone, which is an F180S LG OG
Some people say that you need to flash to E975 first before installing any custom ROMs, because I tried installing Cyanogen mod for e975 via TWRP its telling me my device is not supported (Your device is not E975, its 1... somewhere along those lines is the error), and on MIUI for F180, its giving me this error
assert failed: getprop("ro.product.device") == "getprop("ro.build.product")=="e975"
Click to expand...
Click to collapse
Anyhow, I saw this on youtube
http://www.youtube.com/watch?v=cUQZCST1jrg
yes its very straightforward, but I still cannot understand how he did this... did he install CWM first? If so, how do you install it?
I saw the FAQ guide here on xda but its not that detailed, it says install freegee, but freegee only installed TWRP. (its the only option when I downloaded freegee)
An also the part where he is flashing Gapps, there is a command prompt open... what did he do? WHy did he open the cmd and what are the commands on that cmd?
Ive downloaded all the files on the youtube page just to make sure, even the CWM zip file.
Thanks for answering ^_^
lancelotconquista said:
Hello again everyone!
welp, somehow I managed to recover my phone using TWRP.
But I still want to install Cyanogenmod on my phone, which is an F180S LG OG
Some people say that you need to flash to E975 first before installing any custom ROMs, because I tried installing Cyanogen mod for e975 via TWRP its telling me my device is not supported (Your device is not E975, its 1... somewhere along those lines is the error), and on MIUI for F180, its giving me this error
Anyhow, I saw this on youtube
http://www.youtube.com/watch?v=cUQZCST1jrg
yes its very straightforward, but I still cannot understand how he did this... did he install CWM first? If so, how do you install it?
I saw the FAQ guide here on xda but its not that detailed, it says install freegee, but freegee only installed TWRP. (its the only option when I downloaded freegee)
An also the part where he is flashing Gapps, there is a command prompt open... what did he do? WHy did he open the cmd and what are the commands on that cmd?
Ive downloaded all the files on the youtube page just to make sure, even the CWM zip file.
Thanks for answering ^_^
Click to expand...
Click to collapse
extract this file from the ZIP:
Code:
META-INF\com\google\android\updater-script
Open in notepad++ or other text editors
Delete the first line that says "assert(getprop..." (until ; )
Save the file
Add the file back to the ZIP file
Flash it via recovery
arasyi said:
extract this file from the ZIP:
Code:
META-INF\com\google\android\updater-script
Open in notepad++ or other text editors
Delete the first line that says "assert(getprop..." (until ; )
Save the file
Add the file back to the ZIP file
Flash it via recovery
Click to expand...
Click to collapse
Thanks again! Yes its working on installation, but when the Cyanogenmod symbol with animation is already appearing... its just stuck there.... nothing happens even if i restart... does it really take some time?
lancelotconquista said:
Thanks again! Yes its working on installation, but when the Cyanogenmod symbol with animation is already appearing... its just stuck there.... nothing happens even if i restart... does it really take some time?
Click to expand...
Click to collapse
It usually take 5-15 minutes on first boot since android need to initialize dalvik cache.
If it takes more than that, try clearing cache and wipe data/factory reset
arasyi said:
It usually take 5-15 minutes on first boot since android need to initialize dalvik cache.
If it takes more than that, try clearing cache and wipe data/factory reset
Click to expand...
Click to collapse
WORKING! OMG thank you so much for healping a total noob like me T_T
lancelotconquista said:
WORKING! OMG thank you so much for healping a total noob like me T_T
Click to expand...
Click to collapse
Good for you. Once you get the hang of flashing ROMs, there will be no problems at all. I usually flash 3 ROMs in my LGOG in a week to test the stability of them.
MitoTakatori said:
Good for you. Once you get the hang of flashing ROMs, there will be no problems at all. I usually flash 3 ROMs in my LGOG in a week to test the stability of them.
Click to expand...
Click to collapse
I have an LG F180S can someone from here please assist me in installing CM11?

S2 not booting past CM logo

Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/firmware/cm-11-20140619-NIGHTLY-hercules.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Spud37 said:
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Click to expand...
Click to collapse
"Set metadata recursive" probably means you are using a recovery that is too old.
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
jrc2 said:
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
Click to expand...
Click to collapse
Well there is another issue with my phone that I have actually worked around for awhile now. The MircoUSB on the phone is broken. I bought an extra battery and swap it, I also just use the SD card to copy anything to the phone. Is there a way for me to flash the phone with the new TWRP from the sd card. Why would the older TWRP not install CM 10.2.0 ROM? Do I have to go older perhaps? Thanks though. Knowing is half the battle
EDIT: Going to try and install 10.1.0 and see if it will let me boot. I figure once I can get it to boot, it will be easier to update the Recovery on the phone.
EDIT 2: No problems or errors occured when I installed CM 10.1.0.zip. However it still got stuck in a boot loop. I did however find a file called superwipe for the T mobile S2. I am wondering if that could help
EDIT 3: Okay so the superwipe worked and i am now running 10.1.0, Is it possible to install a Recovery from the phone without using odin?
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
jrc2 said:
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Spud37 said:
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Click to expand...
Click to collapse
It is a lot more risky if your usb port doesn't work, since you can't flash back to stock in Odin if something goes wrong. I would recommend that you get someone to fix that USB port before you make too many changes.
DISCLAIMER: I am not responsible for anything that happens to your phone. These changes could brick your phone if something goes wrong. Proceed at your own risk!
Okay, now for the tutorial. These instructions are assuming that you are already rooted. Download this file and make sure you check the md5sum. Rename it to TWRP.img and move it to /storage/sdcard. This will make the next steps easier. If you move the file somewhere else, make a note of the location of the file. If you have not already, install the terminal emulator app form the Play Store. Open it and type the following lines in it.
Code:
su
[CLICK ENTER]
Code:
dd if=/storage/sdcard/TWRP.img of=/dev/block/mmcblk0p22
(Change the path to wherever you moved the file to) [CLICK ENTER]
Reboot into recovery and wipe cache and dalvik. Reboot. If recovery says that system recovery will override it on reboot, click fix. This should update your recovery.
Have a good afternoon,
jrc2

Categories

Resources