i manged to unlock the bootloader no problem i installed the drivers but it only reads my device when its in fastboot mode and i get this error message when i try to root 'root\boot-insecure-.img': No error why am i getting this?
Guess I'm returning my nexus 7 and get something else since it won't root
Sent from my Nexus 7 using xda app-developers app
OK I feel retarted I know why it won't root its prolly cuz Im running winxp so I have to go buy a win7 computer tomorrow ignore this question I'm just had a dumb moment lol
Sent from my Nexus 7 using xda app-developers app
Or you could download a toolkit which will do all for you no problem.
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Wugfresh? Installed the drivers already but it still says some Error like boot.IMG cannot be found can't remember but when I click root it says that and at the end of it it says no error
Cannot load 'root\boot-insecure-.img': no error
Sent from my Nexus 7 using xda app-developers app
Where can I get the boot.img?
Sent from my Nexus 7 using xda app-developers app
Is there a easier way of doing this? I don't understand how rooting is the most diffcult part
Sent from my Nexus 7 using xda app-developers app
Class_of_punk26 said:
i manged to unlock the bootloader no problem i installed the drivers but it only reads my device when its in fastboot mode and i get this error message when i try to root 'root\boot-insecure-.img': No error why am i getting this?
Click to expand...
Click to collapse
How are you trying to root?
Class_of_punk26 said:
OK I feel retarted I know why it won't root its prolly cuz Im running winxp so I have to go buy a win7 computer tomorrow ignore this question I'm just had a dumb moment lol
Click to expand...
Click to collapse
Or Linux LiveCD.
Try mskip toolkit, I've never had problem with it. It should work correctly. The thing with WugFresh's toolkit is that it downloads mostly the needed components from goo and it has some problems at the moment. So yeah using mskip would be better I think.
Hope it helps.
Envoyé depuis mon Nexus 7 avec Tapatalk 4
Related
Every time I do anything through rom manager I get the superuser has stopped message. How can I fix this? I can't seem to find it online..
Sent from my Galaxy Nexus using xda premium
fk.gregor said:
Every time I do anything through rom manager I get the superuser has stopped message. How can I fix this? I can't seem to find it online..
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Haven't run into this issue specifically, but you can try updating your Superuser binary whether it says it's up to date or not.
It's under the Tools menu in the SU app.
OK there was an update. I see one option failed? Is this important? What is it?
Sent from my Galaxy Nexus using xda premium
fk.gregor said:
OK there was an update. I see one option failed? Is this important? What is it?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Mounting system as read only. Fail is okay.
Hi,
Maybe not a (your) solution but sometimes Superuser really sucks ,like many I have had problems with it so I switched to Super SU,no more issues
Play Store:https://play.google.com/store/apps/...51bGwsMSwxLDEsImV1LmNoYWluZmlyZS5zdXBlcnN1Il0.
XDA:http://forum.xda-developers.com/showthread.php?t=1538053
OK I tried but that still didn't work. It still says its stopped.
Sent from my Galaxy Nexus using xda premium
fk.gregor said:
OK I tried but that still didn't work. It still says its stopped.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Could be a Rom Manager issue, does it do it any other time? I've never used RM personally so can't confirm.
It does it when I try and backup/restore and reboot in recovery. I Aldo tried restoring and it didn't have the md5 sums matched up.
Sent from my Galaxy Nexus using xda premium
Having the same issue
I feel ya buddy, I keep having superuser stop/crash while trying to do anything but flash CWM. Really annoying.
Running ICS 4.04 on GNex (Verizon)
ROM Manager hardly (if ever) works. I'm starting to regret having bought the premium version.
I've read a few places that rom manager and cwm don't 'get along' very well, that's if you're using cwm of course
Sent from my GT-I9100 using XDA
trooperjohn said:
I've read a few places that rom manager and cwm don't 'get along' very well, that's if you're using cwm of course
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
If that is true, it's a damn shame, considering clockworkmod recovery and ROM Manager are both made by the same developer. (Koushik Dutta)
trooperjohn said:
I've read a few places that rom manager and cwm don't 'get along' very well, that's if you're using cwm of course
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
?? Rom manager ONLY works with CWM...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
?? Rom manager ONLY works with CWM...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yeah exactly what I thought I may have misread but thought I'd say anyway correct if I am wrong anybody mind
Sent from my GT-I9100 using XDA
Off Topic: Who keeps rating all threads here with a 1 star?
I have the same problem as OP
I have the same problem, superuser stops when: backup in rom-manager, downloading rom, and booting to recovery.. tried all the things said over..
Anyone?
Geir74 said:
I have the same problem, superuser stops when: backup in rom-manager, downloading rom, and booting to recovery.. tried all the things said over..
Anyone?
Click to expand...
Click to collapse
It isn't exactly a problem...
And non-native app will cause this.
Superuser is granting SU access to allow the phone to reboot.
So as soon as it's granted the process is killed...causing it to throw an error.
It isn't a problem.
Problem solved
Jubakuba said:
It isn't exactly a problem...
And non-native app will cause this.
Superuser is granting SU access to allow the phone to reboot.
So as soon as it's granted the process is killed...causing it to throw an error.
It isn't a problem.
Click to expand...
Click to collapse
The problem was that the reboot returned Andy on his back with a red triangle in his servicehatch, no matter what I did..
Your ultimate guide (awesome guide by the way:good gave me a hint that the problem wasn't with superuser, but with my flashed cwm. I manually reflashed cwm, reflashed superuser. I dumped the su.zip file I had used and replaced it with the file in your guide. A bootloop later, all is good and up and running
Now running CM9 and ADW.
Thx alot for your awesome guide, I will recommend it for everyone looking for the basics, like me.
I followed instructions on this site from another user on how to unlock and root my Verizon Galaxy Nexus. Unlocking was a success... as was Rooting. I continued to try to install Android 4.1 and my phone has been stuck in boot loop on the "Google" screen since 5 this afternoon. So no JellyBean and no phone. hahahaha... great.. help?
Can you get to your recovery
Sent from my Galaxy Nexus using xda app-developers app
yes.
Then just go restore your backup and start over with fresh downloads
Sent from my Galaxy Nexus using xda app-developers app
Restore your backup. Or failing that, you may need to reflash 4.0 in the fastboot screen.
Sent from my Galaxy Nexus using xda app-developers app
I tried that and all I get is "Couldn't open directly" "no files found"
how do I reflash it? do I need to find 4.0 to download?
The easiest thing to do would be just downloaded the one nexus toolkit and use it to flash back to stock and then start over
Sent from my Galaxy Nexus using xda app-developers app
shouldn't that all be in the toro file I downloaded?
Ya if you have a rom on there to flash other than jb use that but if not us this to get back to base
http://forum.xda-developers.com/showthread.php?t=1400871
Sent from my Galaxy Nexus using xda app-developers app
wow. seems like a lot of work. there doesn't seem to be anything saying whether it matters if i'm using a mac or not. I am.
I'm of no help there I know nothing about Macs good luck
Sent from my Galaxy Nexus using xda app-developers app
Erased everything from twrp 2.20 now it doesnt get past the google logo it says i have no OS installed. Im rooted on 4.1.1 how can i install the OS???
Sent from my EVO using xda premium
you formatted the system partition.
i assume you formatted your SD card. so you have 2 choices
1) you download whatever custom rom you want on your pc and use: adb push locationofrom /data/media/
2) you use fastboot to restore to stock.
How can i use fastboot to restore to stock?
Sent from my EVO using xda premium
Adb push to move roms to the phone
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
afgomar said:
How can i use fastboot to restore to stock?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895
adding to that, adb only works in recovery. from fastboot, restart recovery, push a rom, flash it. no need to reflash stock images in this situation, imo.
Sent from my i9250
kyokeun1234 said:
Adb push to move roms to the phone
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
how can i do this? it seems like its not too hard
http://forum.xda-developers.com/showthread.php?t=1529058
forgot to mention i have the sprint galaxy nexus
afgomar said:
forgot to mention i have the sprint galaxy nexus
Click to expand...
Click to collapse
There is the nexus toolkit that has all you need. Its stickied in the sprint section. You can flash a ROM through there.
FrostyF7 said:
There is the nexus toolkit that has all you need. Its stickied in the sprint section. You can flash a ROM through there.
Click to expand...
Click to collapse
good god no
learn to use adb and this wont be a problem
Instead of toolkit, I would Odin back to stock, and start over from there
Sent from my Galaxy Nexus using xda app-developers app
gagb1967 said:
Instead of toolkit, I would Odin back to stock, and start over from there
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
how does odin work? is it easier than adb?
Zepius said:
good god no
learn to use adb and this wont be a problem
Click to expand...
Click to collapse
im downloading adb right now
i cant use adb because the computer wont recognize the phone when plugged in since i can only get into recovery or bootloader
gagb1967 said:
Instead of toolkit, I would Odin back to stock, and start over from there
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
God no, unless fastboot fails.
Beamed from my Grouper
afgomar said:
i cant use adb because the computer wont recognize the phone when plugged in since i can only get into recovery or bootloader
Click to expand...
Click to collapse
adb is not the problem, your pc/windows is. adb is available IN recovery, not in bootloader, stop making that confusion jeez
Sent from my i9250
Problem solved fixed it using odin.
wow you guys are the best
this is why i love xda
thank you everyone for your help
Glad you fixed it. As you see, we all use different methods in the same situation, glad one of them worked for you.
Sent from my Galaxy Nexus using xda app-developers app
With android u don't have to worry about anything if it's software based problem. Every problem can be solved here. We've got the best devs here that make everything is just possible. That's what iphone users can't have. They have to wait for apple for every fixes while we don't.
Sent from my Galaxy Nexus using Tapatalk 2
gagb1967 said:
Instead of toolkit, I would Odin back to stock, and start over from there
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Nice! This helped me out big time. Couldn't get my laptop to recognize my phone. Odin did it though. Thanks.
Can anyone lead me to the correct solution?
Sent from my Galaxy Nexus using xda app-developers app
I think status 7 means a problem with updater script. Maybe a bad download? Have you checked md5sum?
Sent from my Galaxy Nexus
what is the full status 7 error message? you gave us nothing.
Zepius said:
what is the full status 7 error message? you gave us nothing.
Click to expand...
Click to collapse
It mentioned that there was a issue with the sdcard I'm not able to post the picture of the screen at the moment . I have downloaded the 4.2.2 update zip several different times and it still won't work. I also wiped dalvick and cache and re installed the 4.1.1 zip and also the boot loader and radios but still I got the same status 7 error when trying to manually update 4.2.2.
Sent from my Galaxy Nexus using xda app-developers app
E_manificent said:
It mentioned that there was a issue with the sdcard I'm not able to post the picture of the screen at the moment . I have downloaded the 4.2.2 update zip several different times and it still won't work. I also wiped dalvick and cache and re installed the 4.1.1 zip and also the boot loader and radios but still I got the same status 7 error when trying to manually update 4.2.2.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well yes the file errored because of a message. see this: http://forum.xda-developers.com/showthread.php?t=2208028
i need to know what the assert error is to be able to tell you what is wrong.
Zepius said:
well yes the file errored because of a message. see this: http://forum.xda-developers.com/showthread.php?t=2208028
i need to know what the assert error is to be able to tell you what is wrong.
Click to expand...
Click to collapse
Yes that's the error. Sorry for not giving enough info.
Sent from my Galaxy Nexus using xda app-developers app
E_manificent said:
Yes that's the error. Sorry for not giving enough info.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
your error was the same in the screenshot? if so, you modified your build.prop. i gave an answer in there on how to correct it.
So I need to factory reset then root and unlock it ? I'm sorry I'm not very knowledgeable I just know some of the basics .
Sent from my Galaxy Nexus using xda app-developers app
E_manificent said:
So I need to factory reset then root and unlock it ? I'm sorry I'm not very knowledgeable I just know some of the basics .
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
no. you just need to fastboot flash the system.img from the stock image.
after the update, you would lose root anyways and would need to re-root. there is a handy android 101 guide efrant wrote you should look at.
Zepius said:
no. you just need to fastboot flash the system.img from the stock image.
after the update, you would lose root anyways and would need to re-root. there is a handy android 101 guide efrant wrote you should look at.
Click to expand...
Click to collapse
OK thanks for your insight on the issue it's much appreciated!!:beer:
Sent from my Galaxy Nexus using xda app-developers app
I am in 4.2.2 and tried many times to OTA update to 4.3 but it always failed.
Looking in the ROM Manager first screen says that my ROM is not set up to receive OTA.
There are no other options as these are for premium users of the app.
What can I do?
Sent from my Galaxy Nexus using xda app-developers app
Flash it manually via fastboot.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Flash it manually via fastboot.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Well I tried to do so using the nexus root toolkit by Wugfresh but it doesn't seem to work for 4.3 yet.
My other option is to download the file from Google and flash it with the Gal.Nex. toolkit.
As you see I am not very good with commands etc and I am trying to do it the easy way..
Sent from my Galaxy Nexus using xda app-developers app
DomieMic65 said:
Well I tried to do so using the nexus root toolkit by Wugfresh but it doesn't seem to work for 4.3 yet.
My other option is to download the file from Google and flash it with the Gal.Nex. toolkit.
As you see I am not very good with commands etc and I am trying to do it the easy way..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
did he say use a toolkit? no he didnt.
stop being lazy and follow this: http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
did he say use a toolkit? no he didnt.
stop being lazy and follow this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
OK you are right and I am going to do my homework tonight BUT...
Why the h... is it unable to OTA?
It's a completely stock jakju 4.2.2
Sent from my Galaxy Nexus using xda app-developers app
something isnt stock. it could be the radio, kernel, some system file you modified.
When it errors out it should tell you where the problem is.
Zepius said:
something isnt stock. it could be the radio, kernel, some system file you modified.
Click to expand...
Click to collapse
There are some system apps that I have deleted or freezed. It might be it?
In another thread here in xda I read that the device should be in stock recovery in order to accept the OTA update. Now mine is in clockwork mode.
Is this right?
Sent from my Galaxy Nexus using xda app-developers app
DomieMic65 said:
There are some system apps that I have deleted or freezed. It might be it?
In another thread here in xda I read that the device should be in stock recovery in order to accept the OTA update. Now mine is in clockwork mode.
Is this right?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Sigh. CWM doesn't stop otas, modifying /system does that.
If you removed system apps then that's your problem. You will never be able top install the OTA in any way
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
Sigh. CWM doesn't stop otas, modifying /system does that.
If you removed system apps then that's your problem. You will never be able top install the OTA in any way
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
So if I install them back again it will be OK?
Sent from my Galaxy Nexus using xda app-developers app
DomieMic65 said:
So if I install them back again it will be OK?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Yeah probably. But I still suggest using fastboot. It's not that hard.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Yeah probably. But I still suggest using fastboot. It's not that hard.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yes you are right... I will try!
Thnx.
Sent from my Galaxy Nexus using xda app-developers app