Long story short a custom kernel completely screwed up the graphics on my N4 CM11 so I'm trying to flash the original kernel from the ROM which is NOWHERE to be found in the cyanogen site.
Anyone got a link?
MGREX said:
Long story short a custom kernel completely screwed up the graphics on my N4 CM11 so I'm trying to flash the original kernel from the ROM which is NOWHERE to be found in the cyanogen site.
Anyone got a link?
Click to expand...
Click to collapse
Just reflash the rom.
If you don't want to, tell me what version of cm11 your'e running and i'll make a flashable kernel zip :good:
or pull the boot.img out of the rom zip and use the flashify app to flash it. the boot.img is the kernel. but honestly, it sounds like you have absolutely no idea what you are doing. if you have any questions, please ask, im willing to help. can you explain what happened?
Yeah I screwed up, didn't notice it wasn't CAF
22sl22 said:
If you don't want to, tell me what version of cm11 your'e running and i'll make a flashable kernel zip :good:
Click to expand...
Click to collapse
It's 11.0-InstallerXNPQ08Q
Thanks!
So after a reboot to enter recovery my N4 is stuck in the splash screen with the white google logo.
This is getting worse by the minute...
MGREX said:
So after a reboot to enter recovery my N4 is stuck in the splash screen with the white google logo.
This is getting worse by the minute...
Click to expand...
Click to collapse
just fastboot flash a recovery, this shouldnt an issue. did you flash a recovery before, or just boot one? it makes a difference if it sticks around or not.
simms22 said:
just fastboot flash a recovery, this shouldnt an issue. did you flash a recovery before, or just boot one? it makes a difference if it sticks around or not.
Click to expand...
Click to collapse
I'm able to force-access recovery and CWM but that's it, once it boots it gets stuck on the splash screen, and thanks to the lack of a SD port I'm unable to easily load a kernel or ROM, and despite having the android SDK I'm unable to sideload the file through adb on Windows.
Any ideas? besides trying the adb through Linux (I'm doing that now)
Here's the flashable kernel zip taken from Snapshot M7 build :good:
Okay now it gets stuck in the cyanogenmod boot animation
Any ideas? that don't involve wiping everything I mean
simms22 said:
or pull the boot.img out of the rom zip and use the flashify app to flash it
Click to expand...
Click to collapse
Can't do since it no longer boots into android, but I tried to do what you say and sideload the zip but I get a "installation aborted" error on CWM
MGREX said:
Can't do since it no longer boots into android, but I tried to do what you say and sideload the zip but I get a "installation aborted" error on CWM
Click to expand...
Click to collapse
What about TWRP?
Sent from my Nexus 4 using Tapatalk
22sl22 said:
What about TWRP?
Click to expand...
Click to collapse
You mean installing TWRP?
BTW that problem is with the kernel I assembled using a CM11 ROM, your zip actually does boot into cyanogenmod but it gets stuck in the CM boot animation
Okay I'm not sure why or how, but this time it booted alright:laugh::highfive::good:
Thank you guys for the assistance, I'll do a full backup in case it decides to crash again so I can do a total wipe and flash a new ROM from scratch
MGREX said:
Okay I'm not sure why or how, but this time it booted alright:laugh::highfive::good:
Thank you guys for the assistance, I'll do a full backup in case it decides to crash again so I can do a total wipe and flash a new ROM from scratch
Click to expand...
Click to collapse
No problem
Do a titanium backup that backs up all your apps with data. Always have a backup so if things do go wrong you can just wipe and restore apps afterwards :good:
Sent from my Nexus 4 using Tapatalk
Related
Hi there, so i am on 4.2.2 stock with ClockworkMod Recovery v6.0.2.3
I installed the trinity kernel (TS-ALPHA64)
now the n7 is in a boot loop, i can get in to recovery, how can i go back to stock and fix this issue? Would really appreciate any help! THANKS!
Demolition49 said:
Hi there, so i am on 4.2.2 stock with ClockworkMod Recovery v6.0.2.3
I installed the trinity kernel (TS-ALPHA64)
now the n7 is in a boot loop, i can get in to recovery, how can i go back to stock and fix this issue? Would really appreciate any help! THANKS!
Click to expand...
Click to collapse
Reinstall the kernel? Or use the kernel cleaning script, then reflash the kernel then try booting again.
This is why folks make backups.
Replacing a kernel is a significant operation; you should take backups before doing anything significant.
You wouldn't even need to come in here and ask if you had just made a backup.
OK, they might take a bit of time, but they give you freedom too: you can try all sorts of things out; if those experiments don't go well, simply revert to the backup.
To fix your problem, pull the boot image out of the FULL 4.2.2 distro from Google, and flash it to the boot partition.
bftb0 said:
This is why folks make backups.
Replacing a kernel is a significant operation; you should take backups before doing anything significant.
You wouldn't even need to come in here and ask if you had just made a backup.
OK, they might take a bit of time, but they give you freedom too: you can try all sorts of things out; if those experiments don't go well, simply revert to the backup.
To fix your problem, pull the boot image out of the FULL 4.2.2 distro from Google, and flash it to the boot partition.
Click to expand...
Click to collapse
Leonhan said:
Reinstall the kernel? Or use the kernel cleaning script, then reflash the kernel then try booting again.
Click to expand...
Click to collapse
Thanks for all the help and yes i learnt the hard way ... i used the nexus 7 toolkit to reflash to 4.2.2!
Demolition49 said:
Hi there, so i am on 4.2.2 stock with ClockworkMod Recovery v6.0.2.3
I installed the trinity kernel (TS-ALPHA64)
now the n7 is in a boot loop, i can get in to recovery, how can i go back to stock and fix this issue? Would really appreciate any help! THANKS!
Click to expand...
Click to collapse
dude, that kernel is from august 13, 2012. what are you doing flashing it on a 4.2.2 rom? of course itll bootloop. flash the latest trinity 4.2.2 kernel, TS1700-GPUOC-4.2.2-ALPHA1 http://goo.gl/jl1BQ btw, all you had to do is flash another kernel.
AW: HELP! boot loop 4.2.2
bftb0 said:
This is why folks make backups.
Replacing a kernel is a significant operation; you should take backups before doing anything significant.
You wouldn't even need to come in here and ask if you had just made a backup.
OK, they might take a bit of time, but they give you freedom too: you can try all sorts of things out; if those experiments don't go well, simply revert to the backup.
To fix your problem, pull the boot image out of the FULL 4.2.2 distro from Google, and flash it to the boot partition.
Click to expand...
Click to collapse
Agreeing fully, but there is another possibility for playing around with kernels: simply use fastboot to test the kernel before flashing.
fastboot boot <kernel-you-want-to-use> [<ramdisk.img<>]
In case you have only a boot.img you can extract kernel and ramdisk from that.
Sent from my Nexus 7 using xda app-developers app
This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.
Try flashing a different compatible kernel.
ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app
I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!
Glad it's working out for you.
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.
Hey, I seem to have gotten myself into a pickle. Here's what happened: I wanted to do an update to Cyanogenmod 10.2, so I downloaded the ROM and gapps. I wiped dalvik, cache, and system and flashed the ROM. When I tried to flash the gapps Clockwork Mod said it was corrupt. No problem, turned the phone off, pulled micro usb card and put the gapps on that. The only problem is now I can't boot into recovery at all, with the Power+down option and ROM Manager crashes when I try to open it. So the problem is that I can't boot into recovery and I can't reinstall ROM Manager because I don't have gapps. Titanium Backup is also having problems and can't get root access. Does anyone have any ideas on what the problem is or how to fix it? Thanks in advance.
I'd Odin back to stock and start over.
jd1639 said:
I'd Odin back to stock and start over.
Click to expand...
Click to collapse
How do I do that? Will I be able to since I had CyanogenMod 10.1 on before I tried to update?
Also, It would be better if I could just reflash a custom recovery, is there any way to do that?
AwesomeDerek said:
Also, It would be better if I could just reflash a custom recovery, is there any way to do that?
Click to expand...
Click to collapse
See if you can find an odin flashable recovery. There's probably one in the development forum. Flash that.
jd1639 said:
See if you can find an odin flashable recovery. There's probably one in the development forum. Flash that.
Click to expand...
Click to collapse
Do you think this tool would work? http://forum.xda-developers.com/showthread.php?t=2297033&highlight=odin+recovery
AwesomeDerek said:
Do you think this tool would work? http://forum.xda-developers.com/showthread.php?t=2297033&highlight=odin+recovery
Click to expand...
Click to collapse
It's worth a try. If it doesn't work you could go the Odin to stock method.
hungape special
Ding! Got into recovery, now I'm gonna wipe everything. Thanks for your help
AwesomeDerek said:
Ding! Got into recovery, now I'm gonna wipe everything. Thanks for your help
Click to expand...
Click to collapse
Np
Hey XDA,
I'm tempted to install a kernel on my Nexus 4. This is the first time doing a Kernel (already have the nexus 5 rom) but what I was wondering is:
How will I get the stock kernel (3.1.0 if im right?) back on the phone when I want to undo things?
Is it as simple as doing a stock recovery or something else. From what I think recovery is only for the OS and not kernel?
You just dirty flash your current rom. (flash it, then wipe cache and dalvik)
Chromium_ said:
You just dirty flash your current rom. (flash it, then wipe cache and dalvik)
Click to expand...
Click to collapse
its pointless wiping dalvik and cache, as they get wiped when you flash the rom. also, if just flashing a kernel, wiping dalvik and cache have nothing to do with it, so no need to wipe.
Chromium_ said:
You just dirty flash your current rom. (flash it, then wipe cache and dalvik)
Click to expand...
Click to collapse
Same process that I did before installing the Nexus 5 port rom? Trough clockwork etc? If yes then I know what you mean!
Can I install Franko kernel trough clockwork ? or..
ZyreHD said:
Same process that I did before installing the Nexus 5 port rom? Trough clockwork etc? If yes then I know what you mean!
Can I install Franko kernel trough clockwork ? or..
Click to expand...
Click to collapse
Yes. Go into recovery (clockworkmod), and simply flash the rom. Like simms22 said, wiping cache and dalvik isnt necessary, but it wont hurt anyone
Franco packages his kernel as a boot.img (which is installed using fastboot) and as a zip (which is flashable via recovery). Pick the one that you want and install it using the appropriate method.
Chromium_ said:
Yes. Go into recovery (clockworkmod), and simply flash the rom. Like simms22 said, wiping cache and dalvik isnt necessary, but it wont hurt anyone
Franco packages his kernel as a boot.img (which is installed using fastboot) and as a zip (which is flashable via recovery). Pick the one that you want and install it using the appropriate method.
Click to expand...
Click to collapse
Alright and when I want to remove everything and go back to stock via clockwork then it will also remove the custom kernel?
:fingers-crossed:
Mind telling me which link I need? I have this rom installed:
http://forum.xda-developers.com/showthread.php?t=2507021
Only see a 4.2.2 only link at:
http://forum.xda-developers.com/showthread.php?t=2002782
ZyreHD said:
Alright and when I want to remove everything and go back to stock via clockwork then it will also remove the custom kernel?
:fingers-crossed:
Click to expand...
Click to collapse
whenever you flash any rom, it removes the custom kernel, replaces it with the one from the rom(until you flash it again).
simms22 said:
whenever you flash any rom, it removes the custom kernel, replaces it with the one from the rom(until you flash it again).
Click to expand...
Click to collapse
Added some more information. If you mind taking a look.
So just to make sure I understand. When I go into clockwork and whip the phone etc etc it will also whip the custom ROM AND custom Kernel.
So when it boots back into stock android again it also has the original kernel that the nexus 4 was running on?
ZyreHD said:
Added some more information. If you mind taking a look.
So just to make sure I understand. When I go into clockwork and whip the phone etc etc it will also whip the custom ROM AND custom Kernel.
So when it boots back into stock android again it also has the original kernel that the nexus 4 was running on?
Click to expand...
Click to collapse
ytes, if you flash the stock rom again, itll include the stock kernel.
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
ZyreHD said:
Alright and when I want to remove everything and go back to stock via clockwork then it will also remove the custom kernel?
:fingers-crossed:
Mind telling me which link I need? I have this rom installed:
http://forum.xda-developers.com/showthread.php?t=2507021
Only see a 4.2.2 only link at:
http://forum.xda-developers.com/showthread.php?t=2002782
Click to expand...
Click to collapse
from what i understand, most 4.3 kernels will boot on the hybrid 4.4 roms that are out right now, including the port. now ive heard that jwr kernels arent smooth on the 4.4 hybrid roms/ports, but jss kernels run great.
simms22 said:
ytes, if you flash the stock rom again, itll include the stock kernel.
Click to expand...
Click to collapse
Cool then I understand :laugh:
Last thing before I attempt it, do you know which link or file I need?
http://forum.xda-developers.com/showthread.php?t=2002782
Seeing I'm running on the Nexus 5 port for the Nexus 4.
Which is this one: http://forum.xda-developers.com/showthread.php?t=2507021
ZyreHD said:
Cool then I understand :laugh:
Last thing before I attempt it, do you know which link or file I need?
http://forum.xda-developers.com/showthread.php?t=2002782
Seeing I'm running on the Nexus 5 port for the Nexus 4.
Which is this one: http://forum.xda-developers.com/showthread.php?t=2507021
Click to expand...
Click to collapse
flash franciscos jss/jls kernel for the nexus 5 port
simms22 said:
flash franciscos jss/jls kernel for the nexus 5 port
Click to expand...
Click to collapse
Alright I downloaded the lastest JSS file which is a img but when I'm in clockwork and have the file on my phone it doesn't see it?
I went to zip from sdcard.
Or do I need to package the img into a zip file? OR is it something that has to be done trough the cmd? Hope not as clockwork is faster.
ZyreHD said:
Alright I downloaded the lastest JSS file which is a img but when I'm in clockwork and have the file on my phone it doesn't see it?
I went to zip from sdcard.
Or do I need to package the img into a zip file? OR is it something that has to be done trough the cmd? Hope not as clockwork is faster.
Click to expand...
Click to collapse
img files get flashed via fastboot and your desktop.
simms22 said:
img files get flashed via fastboot and your desktop.
Click to expand...
Click to collapse
I got it flashed but now I have a never ending boot animation?
I fastbooted into the bootloader and then flashed it via the cmd. Then I booted with me now sitting here with a never ending animation.
Maybe power it down and then on?
Powering it down and on again isn't working
reflash your rom. the kernel might not be working on the rom then, trinity kernel does http://goo.gl/QtuabY
ZyreHD said:
I got it flashed but now I have a never ending boot animation?
I fastbooted into the bootloader and then flashed it via the cmd. Then I booted with me now sitting here with a never ending animation.
Maybe power it down and then on?
Powering it down and on again isn't working
Click to expand...
Click to collapse
simms22 said:
reflash your rom. the kernel might not be working on the rom then, trinity kernel does http://goo.gl/QtuabY
Click to expand...
Click to collapse
Problem now is that the phone is in USB debugging so my PC won't see the phone. When USB debugging is disabled it does.
Meaning now I can't put the zip on the phone?
How do I get the stock kernel again? Do I need to reinstall the Nexus 5 port or?
ZyreHD said:
Problem now is that the phone is in USB debugging so my PC won't see the phone. When USB debugging is disabled it does.
Meaning now I can't put the zip on the phone?
How do I get the stock kernel again? Do I need to reinstall the Nexus 5 port or?
Click to expand...
Click to collapse
yes, reflash the port, dont wipe anything.
simms22 said:
yes, reflash the port, dont wipe anything.
Click to expand...
Click to collapse
It worked. It booted now! I didnt even know the apps would still be there
ZyreHD said:
It worked. It booted now! I didnt even know the apps would still be there
Click to expand...
Click to collapse
thats why we say to dirty flash. if you flash without wiping anything, your apps and data remain. if you wipe data before flashing, you lose your apps and data.
simms22 said:
thats why we say to dirty flash. if you flash without wiping anything, your apps and data remain. if you wipe data before flashing, you lose your apps and data.
Click to expand...
Click to collapse
I see.
Alright I have had a blast with the kernels and roms but now is my biggest hurtle. How do I remove clockwork and revert back to stock? If you mind explain in detail.
One where you also remove clockwork and one where clockwork just stays on the phone but have stock again.
I can't get it to work :/ get errors etc
So i finally rooted and went into twrp. This is the first rom im installing. Ive done this whole root thing for a little over 4 years now.
I went to do a wipe, system, cache, dav....and its been stuck on "factory reset" for 10 mins now what do i do. did i do something wrong?
formatting cache using make_ext4s function" is what its saying
the phone shut of and i thought it was done for. It did reboot but nothing was wiped. am i doing something wrong here?
normally you just go into the twrp, slide to wipe everything, install rom, gapps, wipe cache and dav and reboot.
xzero425x said:
So i finally rooted and went into twrp. This is the first rom im installing. Ive done this whole root thing for a little over 4 years now.
I went to do a wipe, system, cache, dav....and its been stuck on "factory reset" for 10 mins now what do i do. did i do something wrong?
formatting cache using make_ext4s function" is what its saying
the phone shut of and i thought it was done for. It did reboot but nothing was wiped. am i doing something wrong here?
normally you just go into the twrp, slide to wipe everything, install rom, gapps, wipe cache and dav and reboot.
Click to expand...
Click to collapse
Which twrp are you using? 2.6.3.2 has slow wipes...really slow..... But you should wipe cache,davlik,system, and data then flash ROM and gapps if needed then wipe cache and davlik again then reboot!
RubbleTea said:
Which twrp are you using? 2.6.3.2 has slow wipes...really slow..... But you should wipe cache,davlik,system, and data then flash ROM and gapps if needed then wipe cache and davlik again then reboot!
Click to expand...
Click to collapse
thats the one im using!! is there a newer one around? ill give it another shot.
EDIT: I did them separate, and tried installing a 4.4.2 rom and it keeps failing, hmm
xzero425x said:
thats the one im using!! is there a newer one around? ill give it another shot.
Click to expand...
Click to collapse
Which build do you have? I'll post the link if you want?
RubbleTea said:
Which twrp are you using? 2.6.3.2 has slow wipes...really slow..... But you should wipe cache,davlik,system, and data then flash ROM and gapps if needed then wipe cache and davlik again then reboot!
Click to expand...
Click to collapse
RubbleTea said:
Which build do you have? I'll post the link if you want?
Click to expand...
Click to collapse
tmobile, now i tried to reboot and it just keeps taking me right back to twrp
http://www.teamw.in/project/twrp2/197
Here's the link just click on which build....if you have tmobile ...there's a unofficial 2.6.3.3 I think and 2.6.3.4 or try philz cwm recovery here;
http://forum.xda-developers.com/showthread.php?t=2554053
RubbleTea said:
http://www.teamw.in/project/twrp2/197
Here's the link just click on which build....if you have tmobile ...there's a unofficial 2.6.3.3 I think and 2.6.3.4 or try philz cwm recovery here;
http://forum.xda-developers.com/showthread.php?t=2554053
Click to expand...
Click to collapse
My computer for some reason isnt recognizing the phone, so i cant put any files on it. when i hit reboot, it just goes back to twrp....
should i do a recovery of my backup?
xzero425x said:
My computer for some reason isnt recognizing the phone, so i cant put any files on it. when i hit reboot, it just goes back to twrp....
should i do a recovery of my backup?
Click to expand...
Click to collapse
Did you flash a ROM? After wiping....you could use koush universal drivers and sideload a ROM if your stuck in recovery.....sounds like you Dont have a rom
RubbleTea said:
Did you flash a ROM? After wiping....you could use koush universal drivers and sideload a ROM if your stuck in recovery.....sounds like you Dont have a rom
Click to expand...
Click to collapse
i tried flashing gummy 4.4.2 and it keeps failing, no idea why. maybe the older twrp.
xzero425x said:
i tried flashing gummy 4.4.2 and it keeps failing, no idea why. maybe the older twrp.
Click to expand...
Click to collapse
OK do you have signature check off? Do you have gapps too?
RubbleTea said:
OK do you have signature check off? Do you have gapps too?
Click to expand...
Click to collapse
yes and yes
the error it gets is - error executing updater binary in zip (where my file is)
:good:
xzero425x said:
yes and yes
Click to expand...
Click to collapse
Ah....2.6.3.2 doesn't support 4.4 Roms man try philz recovery
RubbleTea said:
:good:
Ah....2.6.3.2 doesn't support 4.4 Roms man try philz recovery
Click to expand...
Click to collapse
Derp. Alright well. whats my best bet from here? My computer isnt seeing the device atm and i dont have a rom?
Recover my old image and see if that works or something else?
xzero425x said:
Derp. Alright well. whats my best bet from here? My computer isnt seeing the device atm and i dont have a rom?
Recover my old image and see if that works or something else?
Click to expand...
Click to collapse
Crap guessing you don't have a backup......try using koush universal drivers to get your phone recognized...and use adb to sideload a ROM or use adb to push the philz cwm recovery zip to your recovery
---------- Post added at 05:09 PM ---------- Previous post was at 05:05 PM ----------
If you want to sideload a ROM its easy and I'll guide you through or you can push a zip with adb to your recovery
RubbleTea said:
Crap guessing you don't have a backup......try using koush universal drivers to get your phone recognized...and use adb to sideload a ROM or use adb to push the philz cwm recovery zip to your recovery
Click to expand...
Click to collapse
no no! i do have a backup! Thats what i meant from restoring my old image. Ill recover my back up now, then hopefully put the newer twrp on it, then flash the 4.4 rom. hopefully
xzero425x said:
no no! i do have a backup! Thats what i meant from restoring my old image. Ill recover my back up now, then hopefully put the newer twrp on it, then flash the 4.4 rom. hopefully
Click to expand...
Click to collapse
Yah try the backup...the newer twrps for tmo aren't official either so you'll have to find
RubbleTea said:
Yah try the backup...the newer twrps for tmo aren't official either so you'll have to find
Click to expand...
Click to collapse
the backup is restoring now, taking a bit
xzero425x said:
the backup is restoring now, and i cant even find the new twrp in that list, sadly bc i cant figure out the name for the tmobile lgg2. like my old nexus was "toro" but im not sure what this is "called"
Click to expand...
Click to collapse
If you want to flash 4.4. Try the philz cwm recovery link...its a zip so just flash and reboot recovery....there's a unofficial 2.6.3.4 in android development section but no longer supported......I would choose philz over 2.6.3.4 IMO only....and thanks for all the thanks!!!! Just saw them
RubbleTea said:
If you want to flash 4.4. Try the philz cwm recovery link...its a zip so just flash and reboot recovery....there's a unofficial 2.6.3.4 in android development section but no longer supported......I would choose philz over 2.6.3.4 IMO only....and thanks for all the thanks!!!! Just saw them
Click to expand...
Click to collapse
haha thank you! Alright, my phone is alive, im downloaded the philz recovery. going to flash it and try the 4.4..again, haha here we go