Sorry for my english, I`m quite bad... I was wondering if someone could help me with my gnex, Some months ago i bought one, it was rooted and with the bootloader unlocked. Í´ve changed the ROM so many times and then i decided to go back to stock. The problem that I have is that my phone is only working with 4.0.4, I´ve tried everything... odin, the tollkit, re-locking the bootloader and trying to update by OTA, nothing works. When I try to update it to 4.1 or another version it keeps on bootloop. I´ve tried changin the baseband, kernel, recovery, tried all official ROMS whit toolkit... Only 4.0.4, cm9 it works but when i try to uptade it goes on bootloop again...
I don´t know what to do. I`m sorry if I`m posting in the wrong section...
When you was flashing ROM's did you do a factory reset?
skhjpz said:
When you was flashing ROM's did you do a factory reset?
Click to expand...
Click to collapse
Yes, of course. Toolkit os flashing the userdata.img and erasing all. Then in recovery I try the factory reset but it keeps con bootloop...
How do you try to update? What ROM do you want to flash? Which recovery do you use? Using which method do you try to update?
Sent from my Galaxy Nexus using xda app-developers app
mrgnex said:
How do you try to update? What ROM do you want to flash? Which recovery do you use? Using which method do you try to update?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I've tried with all methods. OTA over official 4.0.4, toolkit, odin. Nothing.
I want to update it, I don't like ICS. I've tried all types of versions, only ICS ROMs are working. I've tried with diferent recoverys also. Nothing...
I'm desperate
Sent from my Galaxy Nexus using xda app-developers app
Did you try fastboot? That erases everything and has the highest chance of succes.
Sent from my Galaxy Nexus using xda app-developers app
mrgnex said:
Did you try fastboot? That erases everything and has the highest chance of succes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Tried too, not working. The toolkit uses Fastboot and ADB. Nothing...
Sent from my Galaxy Nexus using xda app-developers app
Dont use toolkits. Just use fastboot manually.
Sent from my Galaxy Nexus using xda app-developers app
mrgnex said:
Dont use toolkits. Just use fastboot manually.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Not working... i've tried every possible method. Nothing...
Sent from my Galaxy Nexus using xda app-developers app
My maguro/gnex happen like this as well.
What i do, copy any custom rom(4.4 latest) into sd/data when in ics rom.
Then i flash cwm recovery using adb in fastboot
Then i boot into cwm then flash that custom rom zip file.
And it works.
Or you can find stock jdq39/4.3 in zip and flash that.
Sent from my Galaxy Nexus using xda app-developers app
vocyber said:
My maguro/gnex happen like this as well.
What i do, copy any custom rom(4.4 latest) into sd/data when in ics rom.
Then i flash cwm recovery using adb in fastboot
Then i boot into cwm then flash that custom rom zip file.
And it works.
Or you can find stock jdq39/4.3 in zip and flash that.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Not working . I did it too, only ICS ROMs...
Sent from my Galaxy Nexus using xda app-developers app
and what custom rom that you just try?
still stuck in bootloop?
did u fullwipe/factory reset before flash the rom in cwm/twrp?
vocyber said:
and what custom rom that you just try?
still stuck in bootloop?
did u fullwipe/factory reset before flash the rom in cwm/twrp?
Click to expand...
Click to collapse
I tried CM11 and other 2 based in Kit Kat.
The others were based in 4.1 and 4.2/4.3
Yes, of course. I always make a clean install.
Sent from my Galaxy Nexus using xda app-developers app
mind you try the paranoid rom? its aosp and i never stuck in bootloop in this rom.
vocyber said:
mind you try the paranoid rom? its aosp and i never stuck in bootloop in this rom.
Click to expand...
Click to collapse
I will give a try... but it won't work. Like the others.
It's something really strange, it never happened to me until now...
Sent from my Galaxy Nexus using xda app-developers app
Is not working... I've tried with two diferent versions and nothing... help please...
Sent from my Galaxy Nexus using xda app-developers app
Did you try installing the stock factory 4.3 ROM from Google?
Search the forum and you will find the link, download and use fastboot it even the toolkit and install that. That will erase everything and should have nothing to do with your recovery or root.
But you will end up with stock 4.3 ROM
Sent from my Galaxy Nexus using Tapatalk
niamul said:
Did you try installing the stock factory 4.3 ROM from Google?
Search the forum and you will find the link, download and use fastboot it even the toolkit and install that. That will erase everything and should have nothing to do with your recovery or root.
But you will end up with stock 4.3 ROM
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yes yes, the 4.3 ROM factory rom, I've tried with 4.2.2 too and the 4.1, only 4.0.4 is working properly...
Sent from my Galaxy Nexus using xda app-developers app
Tried changing to twrp? Have you upgraded your recovery to the newest version?
Maybe you're on a 3 year old recovery
Sent from my Galaxy Nexus using Tapatalk
niamul said:
Tried changing to twrp? Have you upgraded your recovery to the newest version?
Maybe you're on a 3 year old recovery
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm always on the newer recoverys, I've tried with CWM and TWRP. Nothing
Sent from my Galaxy Nexus using xda app-developers app
Related
I am running AOKP JB and using CWM. Flashing updated roms of AOKP is fine but when i try to flash a different rom, (I've tried CM9 and 10, KyanRom, and paranoid android) i keep getting the same error.
i factory reset and wipe cache and dalvik but still no go.
any ideas of what i might be doing wrong or how to fix this?
Use Odin flash stock rom then boot into recovery wipe data and reboot done
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
tonyph33r said:
Use Odin flash stock rom then boot into recovery wipe data and reboot done
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
do i have to do this every time i want to flash a different rom? or will doing this one time fix this issue?
What recovery are you running?
Sent from my Nexus 7 using xda premium
defnow said:
What recovery are you running?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
CWM recovery v5.5.0.4
metalhawj said:
CWM recovery v5.5.0.4
Click to expand...
Click to collapse
That's an older version. You need the newest one, which is 5.8.4.7. Download the img file from the website and flash through android emulator.
Downloads: http://www.clockworkmod.com/rommanager
How to install through Android Emulator on the device: http://forum.xda-developers.com/showthread.php?t=1739426
scroll down to the "Third, alternate if unfamiliar with adb commands" option and follow directions.
Beware that once you install this version of CWM, your previous nandroid backups will not work, as they will get md5 mismatch. If you want to go back to the older version of CWM, simply use the method you used when you first flashed CWM (via Odin). I experienced the same thing, so I had to do some research before I flashed CM10. Hope that helped!
Sent from my Galaxy Nexus using Tapatalk 2
amgpower63 said:
That's an older version. You need the newest one, which is 5.8.4.7. Download the img file from the website and flash through android emulator.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Or update through ROM manager...
Sent from my Nexus 7 using xda premium
defnow said:
Or update through ROM manager...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
That works too. But for some reason, my device wasn't listed in the app so I had to go through the other process ):
I have a rooted galaxy nexus and went to install the ota jb update. It gave me the red sign in cwm and said failed whole package sign or something like that.. now it says no update available. Anyone know what I should do to get jb update without wiping?
Sent from my Galaxy Nexus using xda app-developers app
you clearly modified system files. you need to find the files you modified and change them out to ones that are unmodified.
Yeah.. I changed recovery from boot.p to recoveryfromboot.p.bak as that's what a tec said to do after rooting if cwm didn't stick... can I change it back without breaking root?
Sent from my Galaxy Nexus using xda app-developers app
aaronmcc11 said:
Yeah.. I changed recovery from boot.p to recoveryfromboot.p.bak as that's what a tec said to do after rooting if cwm didn't stick... can I change it back without breaking root?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
That's not the reason why. You must have changed your radio or kernel or recovery. The ota update won't install ota with cwm
Sent from my Galaxy Nexus using Tapatalk 2
aaronmcc11 said:
Yeah.. I changed recovery from boot.p to recoveryfromboot.p.bak as that's what a tec said to do after rooting if cwm didn't stick... can I change it back without breaking root?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
you are confusing root with a custom recovery. they are not the same. to get root, you have to have a custom recovery (least on anything 4.0.4 or higher). you do not need root to have a custom recovery.
if you take the OTA, you will lose root anyways and then you will also lose your custom recovery.
So I have to wait for a rom build and flash it to have jb with root??
Sent from my Galaxy Nexus using xda app-developers app
I think there are plenty of JB roms out there from the announcement in June. I could be wrong, but if you're just looking for the new radios, I think they can just be flashed over your current setup.
Sent from my Galaxy Nexus using xda app-developers app
No. You can accept (or flash) the OTA & then root it.
aaronmcc11 said:
So I have to wait for a rom build and flash it to have jb with root??
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
You need to have a read of this thread. And then, maybe have a read of this one if you think it's easier.
efrant said:
You need to have a read of this thread. And then, maybe have a read of this one if you think it's easier.
Click to expand...
Click to collapse
That confused the hell out of me.. and I'm not dumb. Lol. The second one doesn't mention toroplus from what I read.
I think I'll just update and reroot.. my problem is.. do I have to change that system file back to its original? And then do I have to download the update from somewhere BC my phone says up to date now?
Sent from my Galaxy Nexus using xda app-developers app
Sorry I'm confused.. I had an og Droid before this so a bit different.
Sent from my Galaxy Nexus using xda app-developers app
Hy .. On my notification bar said update found and downloaded. Size of update was 768kb.... I pressed install update and phone restarted and booted in cwm recovery and asked to install untrusted package and i said yes. Then told me update failed..... Anyone knows what update was and why didn't installed ? I have stock 4.2 rom with been 6.0.... No root.
Sent from my Galaxy Nexus using xda app-developers app
clockwork
If you are trying to install an OTA stock update with CWM it wont work. You will need the stock recovery in place for the OTA stock update to work properly. At least, that is what was needed in my case. If you want to keep CWM then you can flash a developer's stock zip for your respective nexus.
OK. Thnx but what was that little update ?
Sent from my Galaxy Nexus using xda app-developers app
Since you're on 4.2, it was probably 4.2.1.
And a changelog ? Or what is changed ?
Sent from my Galaxy Nexus using xda app-developers app
It's a fix for the "December issue" (apparently December isn't accessible in the People app in 4.2). Some people have claimed some performance increases, but that might be placebo. I went from 4.1.2 to 4.2.1, so I can't comment on 4.2 vs 4.2.1.
I tried to install the update with stock recovery .. I was in custom rom which is rooted .. the install failled and make the device won't boot the system! Any idea?
Sent from my SGH-T959V using xda app-developers app
Use fastboot to erase the system partition and re-flash a valid system image.
Cilraaz said:
Use fastboot to erase the system partition and re-flash a valid system image.
Click to expand...
Click to collapse
Am I going to lose my data?
Sent from my SGH-T959V using xda app-developers app
Med1a said:
Am I going to lose my data?
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Yes....
Med1a said:
Am I going to lose my data?
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Your sdcard? Only if you erase userdata, which is the same as /data/media
Sent from my i9250
Does using odexed ROM like most ROMs here matter?
I note the OTA packages have codex files in them.
Sent from my Galaxy Nexus
I was under the impression most roms available on the Dev section are deodexed.
Sent from my i9250
Hey Guys, coming from the Samsung galaxy nexus. Receiving my s4 in a few days.
Just a few question to install twrp:
1.Root using motochopper
2. Install goo manager
3. Install TWRP
4. Funfun
Are those the correct steps? Thanks!
Sent from my Galaxy Nexus using xda app-developers app
I think unlock bootloader should be in there somewhere.
Isn't tmobile s4 boot loader already unlocked?
Sent from my Galaxy Nexus using xda app-developers app
Don't worry about the bootloader I just rooted w motochopper and then from there I installed recovery via Goo manager already flashed a couple of things with success everything runs fine
Sent from my SGH-M919 using xda app-developers app
pezlomd said:
Don't worry about the bootloader I just rooted w motochopper and then from there I installed recovery via Goo manager already flashed a couple of things with success everything runs fine
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
So the steps :
1 Motochopper
2. Goo manager
3. Install TWRP
That's correct right? We don't need to worry about boot loader because its unlocked alrdy. Right? Coming from GN so.. Just making sure.
Sent from my Galaxy Nexus using xda app-developers app
TonikJDK said:
I think unlock bootloader should be in there somewhere.
Click to expand...
Click to collapse
nitrogen618 said:
Isn't tmobile s4 boot loader already unlocked?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Bootloaders on T-Mobile's S4 are not locked, confirmed.
pilot_xphile said:
Bootloaders on T-Mobile's S4 are not locked, confirmed.
Click to expand...
Click to collapse
Thanks guys! Sorry for being a noob. So I just need to root then get goo manager to get TWRP right?
Sent from my Galaxy Nexus using xda app-developers app
nitrogen618 said:
Thanks guys! Sorry for being a noob. So I just need to root then get goo manager to get TWRP right? TWRP will be perm right?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Sorry double post. Once I install twrp with goo, twrp will be perm right?
Sent from my Galaxy Nexus using xda app-developers app
nitrogen618 said:
Sorry double post. Once I install twrp with goo, twrp will be perm right?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Sorry for the bootloader comment. I have no idea how I got in the t mobile section. I'm vz.
Yes twrp will be permanent unless you flash it back to stock.
pezlomd said:
Don't worry about the bootloader I just rooted w motochopper and then from there I installed recovery via Goo manager already flashed a couple of things with success everything runs fine
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Did doing it that way change your system status in Odin mode? I Odin'ed TWRP and then rooted. Now I have a system status of Custom instead of Official.
Atmazzz said:
Did doing it that way change your system status in Odin mode? I Odin'ed TWRP and then rooted. Now I have a system status of Custom instead of Official.
Click to expand...
Click to collapse
If u have a custom recovery the status will always say custom. Only flashing back to stock through odin will make it official again.
Sent from my SGH-M919 using xda app-developers app
pezlomd said:
If u have a custom recovery the status will always say custom. Only flashing back to stock through odin will make it official again.
Click to expand...
Click to collapse
I'm used to my Galaxy S2 I guess. It never said custom. Tried Odin k0ane's stock file. Still says custom. I thought I was going to have to return the phone. It started using hotspot data for all data. I was almost to my 500 meg limit. A factory reset fixed it and Tmo gave me an extra 2gb hotspot data for this month only for free.
What's the difference between custom and official?
Sent from my Galaxy Nexus using xda app-developers app
nitrogen618 said:
What's the difference between custom and official?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Stock recovery doesnt let u flash custom roms ; no bakups.
Custom you won ur phone.
Sent from my SGH-M919 using xda premium
nitrogen618 said:
What's the difference between custom and official?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Official is all stock factory system. Custom means you altered the system and your warranty is probably void. That's why people try to flash back to stock if they need to get their phone repaired or replaced.
I see. Coming from the galaxy nexus, so much to learn..
Also, where can I get the samsung USB Drivers to do the motochopper?
nitrogen618 said:
I see. Coming from the galaxy nexus, so much to learn..
Also, where can I get the samsung USB Drivers to do the motochopper?
Click to expand...
Click to collapse
Direct from Samsung, a few people have posted the links on the development boards already so check there.
Sent from my SGH-M919 using xda premium
nitrogen618 said:
I see. Coming from the galaxy nexus, so much to learn..
Also, where can I get the samsung USB Drivers to do the motochopper?
Click to expand...
Click to collapse
Take a look ant the N2 and S3 forums - they have threads on returning to stock and i am sure we will see one here - AS SOON as and only when an official Samsung TMo firmware is available.
If you break or brick your device before then you will have to wait before sending it in to Samsung or TMo.
gaww said:
Take a look ant the N2 and S3 forums - they have threads on returning to stock and i am sure we will see one here - AS SOON as and only when an official Samsung TMo firmware is available.
If you break or brick your device before then you will have to wait before sending it in to Samsung or TMo.
Click to expand...
Click to collapse
I can't believe sammobile hasn't gotten the firmwares posted yet. Isn't this unusual? Doesn't Samsung usually release the firmware almost immediately?
Does anyone know why that when I download something to my internal sd card and then boot into twrp and try to install it the file is missing in the download folder. Am I doing something wrong? i'm coming from cwm and things are a lot different. Any help would be great thanks
Sent from my SGH-I317 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