N4 converted OG fails to flash any roms - AT&T LG Optimus G

I converted my LGOG today, and everything went smoothly. I have CMW touch as my recovery (but i've tried TWRP too) and when I try to flash a rom (Pacman in this case) it aborts the install and tells me "error 7, something about assest failed getprop." The only thing I haven't done is do the fix for 8gb -> 16gb.
Any ideas?
Edit: I finally got 10.1 to install, looks like my Pacman download might have been corrupt. However, its stuck on the spinning cyanogenmod screen for the past 20 minutes.

xsaqzw said:
I converted my LGOG today, and everything went smoothly. I have CMW touch as my recovery (but i've tried TWRP too) and when I try to flash a rom (Pacman in this case) it aborts the install and tells me "error 7, something about assest failed getprop." The only thing I haven't done is do the fix for 8gb -> 16gb.
Any ideas?
Edit: I finally got 10.1 to install, looks like my Pacman download might have been corrupt. However, its stuck on the spinning cyanogenmod screen for the past 20 minutes.
Click to expand...
Click to collapse
Did you use a N4 recovery? Because you need one to flash n4 specific roms like Pacman. Also there was a step late in the conversion that involved wiping that you might want to look into again.

Optimus G recovery for our custom CM10.1 roms
N4 recovery for N4 roms

C2fifield said:
Did you use a N4 recovery? Because you need one to flash n4 specific roms like Pacman. Also there was a step late in the conversion that involved wiping that you might want to look into again.
Click to expand...
Click to collapse
I used the Optimus recovery at first, but later used the N4 recoveries. The N4 recoveries ran fine. I was able to install the ROMS, however each one hung at the boot screen (CyanogenMod screen and the pacman boot screen.)
After failing with that I went back to stock. Now my phone is hung on the "at&t rethink possible" screen. LGNPST got to 85% but I heard that was normal and to exit out and continue.
Now what?
tdnick said:
Optimus G recovery for our custom CM10.1 roms
N4 recovery for N4 roms
Click to expand...
Click to collapse
Yes, I used the N4 recovery.

Hey, man I just had this exact same problem under different circumstances so maybe I can help. When LGNPST finishes and reaches 85% wait for the pop up that says the device disconnected. Once it does that turn the device off. Now hold volume down and power and it should ask if you want to reset your device. Press power to reset it and it should boot up (it might feel like its taking a while after all this time your spending waiting and getting nothing, I know that feeling!). There you go! All fixed up! Someone helped me with that last night in a thread and I was sure I'd tried that but I was wrong and it worked! If it doesn't then it's possible you need to charge your phone and then do it. Let me know if that does or doesn't work, bud. Good luck!
Sent from my LG-E970 using xda app-developers app

Related

[Q] LG Optimus V problem flashing to stock

So my Optimus V was running slow so I decided to reset it to factory defaults but I didn't know if your phone is rooted then you shouldn't do it from within android so I did. Then I couldn't get it to do anything but boot up into ClockworkMod Recovery. I tried loading up old backups but every time it just boots back up into Clockwork. So then I went here:
prepaidandroid. org/index.php?title=How_to_restore_your_Optimus_V_to_almost_original_condition
and I followed the "flashing stock ROM" section but when I rebooted it still went into clockwork. Really I just want my phone to work again. Anyone know what the problem could be?
bump bump bump
JDCRulezd00d said:
So my Optimus V was running slow so I decided to reset it to factory defaults but I didn't know if your phone is rooted then you shouldn't do it from within android so I did. Then I couldn't get it to do anything but boot up into ClockworkMod Recovery. I tried loading up old backups but every time it just boots back up into Clockwork. So then I went here:
prepaidandroid. org/index.php?title=How_to_restore_your_Optimus_V_to_almost_original_condition
and I followed the "flashing stock ROM" section but when I rebooted it still went into clockwork. Really I just want my phone to work again. Anyone know what the problem could be?
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/showthread.php?t=1090687
samrox144 said:
try this
http://forum.xda-developers.com/showthread.php?t=1090687
Click to expand...
Click to collapse
Thanks man. That seems to be the right thread.
Can't really figure out how to use ADB though, hah. Every tut on it seems to tell you to do completely different things and I don't know enough about it to figure out how to use it in this case.

[Q] trouble flashing roms

gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Did you try to wipe data/factory reset/ wip cachd and wipe dalvik?
all of it. follow directions for each rom exactly. i always end up in the same spot
burnitdown said:
all of it. follow directions for each rom exactly. i always end up in the same spot
Click to expand...
Click to collapse
How much you wait? After I flashed the Galaxy Task 14 room earlier this day it took several minutes to load.
Certain ROMS require an older version of CWM, such as CM9. If that is the latest version you have installed it may not work. Maybe try using ODIN to flash the recommended version (you can easily find that in the CM9 Nightly threads or simply by searching around)?
bar_rodoy
Click to expand...
Click to collapse
i let it sit long enough.
this_is_nick6
Click to expand...
Click to collapse
i'm using the most up to date cwm. right now i'm trying to flash aokp m4
burnitdown said:
gtab wifi, stock tw3.2., cwm 5.8.3.1
i've tried flashing several roms using cwm and through rom manager. every time i get stuck on the the samsung screen after reboot, which takes about 30 seconds after initiating flash. i've never had a problem installing anything on my phones or my nook color. it's been nothing but a paper weight for the last year and it's going to the landfill if i can't figure it out soon.
Click to expand...
Click to collapse
Can you link us to the CWM 5.8.3.1 recovery your using???
As far as I know this is the latest version of CWM http://droidbasement.com/db-blog/?p=2655 as of 6/30 and it's only 5.5.0.4.
As far as Googling is telling me...
1. It may be a touch recovery?
2. I couldn't find a many search returns that mentioned it being for Tab10.1s
3. The search returns I did find that mentioned Galaxy Tabs were in languages I don't read.
Just curious don't ya know...
Sent From My Galaxy10.1 Class Starship....
Questions go in the Q&A section
my recovery is listed on the cwm site under rom manager. it's not touch
now i'm curious as to what version everyone else is using
okay. so i flashed 5.5.0.4 through odin then flashed aokp m4 plus gapps. all seemed to go well until boot time. i've been sitting at the samsung screen for a full 20 minutes now. i suppose my next course of action would be to revert to stock via odin and start the process over? i'd really like to use this thing but absolutely can't stand tw
you may have gotten a corrupt partition somewhere. I'd odin back to stock and start fresh. fwiw, I wouldn't trust ROM Manager for the latest recovery, it doesn't always have the correct file for your device. For example, for may particular phone Rom Manager had never worked properly and soft-bricks the phone every time.
Always check here on XDA for the proper recovery files for this device first.
that's all i needed to hear. now, can anyone point me in the direction of the file i need? my searches all point to S0ckM0nk3y's link which results in a 404 error
disregard my last post. i flashed sam's ics via odin. i'll play with it and try to like it. thank you sir
huh. still can't flash a custom rom...
Well, I don't know what I did but i was able to get MapleSyrup's CM10 preview to run. I'm happy for now
Are you doing a factory reset and wiping the cache in CWM before you flash? I always do that and then use titanium backup to restore my apps.
Also, what version of recovery are you using? I'm on CWM 5.5.0.4 which I've used to flash a couple of different roms, including the latest stock ICS from Toldo I think.
you can get it here and use ODIN to flash. Just make sure you download the correct version for your device:
http://droidbasement.com/db-blog/?p=2668
i had the same problem. i flash stock ics rom for my 7510. at first it looks fine until i try to reboot my tab. it starts to hang at the bootscreen. i try to reflash the rom via recovery but fail. try to install nandroid backup and also fail. the last resort is to do clean flash from odin. this thing happened 5 times in 3 days. one time after i install all the apps and try to restart my tab then it happened again, stuck at bootcscreen.

[Q] Why are these roms not working?!? x.x

There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
rejectedjs said:
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
Click to expand...
Click to collapse
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
It's probably your recoverys fault. On my last DNA I had nothing but failures. Once it took at least 30 times to get a Rom installed. Never solved the issue on that phone. I just soffed my new DNA yesterday, installed the newest cwm touch and flashed 4 different roms with no problem. Try re-flashing cwm touch.
pio_masaki said:
Did you do a full wipe? System, factory reset, dalvik?
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Yes, still the same thing, I'm not saying I didn't do that the first time though, that's like the basics of installing a rom.
str8upx said:
It's probably your recoverys fault. On my last DNA I had nothing but failures. Once it took at least 30 times to get a Rom installed. Never solved the issue on that phone. I just soffed my new DNA yesterday, installed the newest cwm touch and flashed 4 different roms with no problem. Try re-flashing cwm touch.
Click to expand...
Click to collapse
Do you think its TWRP's fault? After I found out there was no way to mount USB storage in TWRP I wanted to switch to CWM, but sadly I don't know how.
rejectedjs said:
Yes, still the same thing, I'm not saying I didn't do that the first time though, that's like the basics of installing a rom.
Do you think its TWRP's fault? After I found out there was no way to mount USB storage in TWRP I wanted to switch to CWM, but sadly I don't know how.
Click to expand...
Click to collapse
You could use the goomanager from the play store or use fastbook flash recovery cwm.img
Edit: for the touch version of cwm fastboot is required.
str8upx said:
You could use the goomanager from the play store or use fastbook flash recovery cwm.img
Edit: for the touch version of cwm fastboot is required.
Click to expand...
Click to collapse
I would rather use goomanager, because it seems easier, but the only thing it seems to be able to download is the twrp image. How would I set it to cwm?
I have canvas 2 running on suvi6 Jupiter rom i have some prob with this when i reboot some icon on home screen will disappear, i found that those apps which r installed on ext sd card its icon will disappear from home screen, but apps working in apps list, only icon from home screen disappeared.
Other problem is that while incoming a call i cannot see full picture of caller becoz half screen is black and half picture can be seen.
Please help me
Sent from my Micromax A110 using xda app-developers app
rejectedjs said:
I would rather use goomanager, because it seems easier, but the only thing it seems to be able to download is the twrp image. How would I set it to cwm?
Click to expand...
Click to collapse
Sorry I was mistaken, goomanager installs twrp not cwm.
Fastboot is easy to use, I'm at work so I can't to a step by step til I get home later. You should be able figure it out but if not I will help when I get home.
str8upx said:
Sorry I was mistaken, goomanager installs twrp not cwm.
Fastboot is easy to use, I'm at work so I can't to a step by step til I get home later. You should be able figure it out but if not I will help when I get home.
Click to expand...
Click to collapse
I don't know if you knew this already but I s-offed using moonshine, is that a problem? I installed cwm and tried installing hatka again and it did the same thing, restart like every three seconds into android. I don't know what to do anymore.
kundan.lohar said:
I have canvas 2 running on suvi6 Jupiter rom i have some prob with this when i reboot some icon on home screen will disappear, i found that those apps which r installed on ext sd card its icon will disappear from home screen, but apps working in apps list, only icon from home screen disappeared.
Other problem is that while incoming a call i cannot see full picture of caller becoz half screen is black and half picture can be seen.
Please help me
Sent from my Micromax A110 using xda app-developers app
Click to expand...
Click to collapse
Pretty sure you're in the wrong forum.
From my S-Off BadSeed DNA
rejectedjs said:
There were two main roms I wanted to try after I finally S-OFF'd my phone yesterday. Hatka Supreme 1.1.0 and Carbon. Neither of these worked and I'm glad that I backed up my S-OFF rooted stock rom. Hatka Supreme, the guy states its best to use Beast Mode kernal with the rom, which I flashed after I installed the room, and it just randomly reboots at the splash screen/a few seconds after getting into Android, so I restored my stock and everything worked fine. Next, I tried Carbon, and it just sat there at the carbon flash screen for like 20 minutes, so again, I had to restore to stock. Is there something I'm doing wrong? Is there a difference between Original Android Development and Android Development? Should I be looking at the original or what? I'm really lost, I'm going to try another rom, hopefully someone replies to this before it finishes downloading. Thanks for the help.
EDIT: I'd rather just sit and wait to see if someone replies before I waste time downloading another rom...any help would be appreciated.
Click to expand...
Click to collapse
I'm no expert, but when u flashed hatka, did u reboot into the system before flashing beast mode kernel? Flashing a kernel in the same recovery session is a no no. Also, beast mode is not compatible with carbon, fyi.
Sent from my HTC6435LVW using Tapatalk 4 Beta
kelvinnotcalvin said:
I'm no expert, but when u flashed hatka, did u reboot into the system before flashing beast mode kernel? Flashing a kernel in the same recovery session is a no no. Also, beast mode is not compatible with carbon, fyi.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did that the first time, and thats when I started experiencing it, so I figured that was the problem. So I restored to stock, and then just tried flashing the rom and booting, still same thing, rebooting every 5 seconds. Sometimes I'm able to get into settings, scroll up and down a few times, and then it reboots.
EDIT: If I remember correctly, I didn't even flash beast mode kernel after I flashed carbon.
rejectedjs said:
EDIT: If I remember correctly, I didn't even flash beast mode kernel after I flashed carbon.
Click to expand...
Click to collapse
If you had you never would have seen the carbon boot animation I don't think, just a white scrambled screen.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
If you had you never would have seen the carbon boot animation I don't think, just a white scrambled screen.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
What exactly is the problem I'm experiencing here? x.x Of all roms I REALLY wanted to try Hatka, why me...
rejectedjs said:
What exactly is the problem I'm experiencing here? x.x Of all roms I REALLY wanted to try Hatka, why me...
Click to expand...
Click to collapse
I've had the same sort of thing happen to me when we first started working with CM. I had to lock up and run the RUU then unlock again, started flashing normally again after that.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I've had the same sort of thing happen to me when we first started working with CM. I had to lock up and run the RUU then unlock again, started flashing normally again after that.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
You mean you want me to go back to pure stock and soff all over again?
rejectedjs said:
You mean you want me to go back to pure stock and soff all over again?
Click to expand...
Click to collapse
I don't want you to do anything, in was just saying what I did to correct it when it happened to me.
And no, I didn't day s-on, I said relocked, the RUU won't run on an unlocked device. Locked and son are different.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
I don't want you to do anything, in was just saying what I did to correct it when it happened to me.
And no, I didn't day s-on, I said relocked, the RUU won't run on an unlocked device. Locked and son are different.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
I've never had so many problems just trying to flash a Rom before, this is crazy...I'm seriously at a loss about what to do other than stay on rooted stock
bump?..I really want some help..
Did you figure it out? I'd do what pio said. He's kind of amazing. He's a very smart man who most likely knows what he's doing
Sent from my HTC6435LVW using xda app-developers app

[q] please help - possible brick

Hello everyone, Forgive me if I seem a bit flustered, but I am. I was adding a few fonts with an app from the play store. It would restart after each fine, and there was no issue. On the final one, it restarted, but then got hung up for 10 minutes on the ATT logo. I have restarted it with the power button numerous times now, and it has done nothing different. I have only rooted the phone, I have no custom recovery or anything. I booted into the LG stock recovery, canceled the reset, and it still hung up at the ATT logo.
What might have happened, and how can I fix this? I would rather not hard reset, but if I have to, I have to. Please respond with anything at all that might help me. I'm using my old GSII right now, and the newer sim doesn't fit quite right in it. I can make calls and stuff, but i want to get back on the OG as fast as possible. PLEASE respond with anything helpful. Thanks.
I am running stock Jellybean (The initial jellybean we got, I think it was 4.1.1), rooted. No custom roms, no custom recovery.
UPDATE: I did a factory reset (by holding power and volume down). It is still doing the same thing. It gets to the ATT logo and plays the music "Dee dee dee dee 'click'", then stops. Nothing more happens. At all. I've let it sit for a while and nothing is happening. So now the question is, how can I save it with that in mind?
chrisphoenix7 said:
UPDATE: I did a factory reset (by holding power and volume down). It is still doing the same thing. It gets to the ATT logo and plays the music "Dee dee dee dee 'click'", then stops. Nothing more happens. At all. I've let it sit for a while and nothing is happening. So now the question is, how can I save it with that in mind?
Click to expand...
Click to collapse
Sound like you need to use LGNPST or use a teenybin then flash a custom ROM. Factory reseting ( I think) only clears out the /data partition which is where all user and app data is saved. If something in the /system partition is not allowing it to boot, that is why the factory reset didn't work. To fix you have to restore the /system partition back to stock.
To do so, flash a full bin. Which will reset the phone to complete stock (no root, no unlocked bootloader).
Or you can flash a teenybin. Which is smaller and safer. Flashing a teenybin unlocks the bootloader and puts a custom recovery. From there you can just flash a new ROM.
Joecascio2000 said:
Sound like you need to use LGNPST or use a teenybin then flash a custom ROM. Factory reseting ( I think) only clears out the /data partition which is where all user and app data is saved. If something in the /system partition is not allowing it to boot, that is why the factory reset didn't work. To fix you have to restore the /system partition back to stock.
To do so, flash a full bin. Which will reset the phone to complete stock (no root, no unlocked bootloader).
Or you can flash a teenybin. Which is smaller and safer. Flashing a teenybin unlocks the bootloader and puts a custom recovery. From there you can just flash a new ROM.
Click to expand...
Click to collapse
Thanks. Do you know if there's an accurate guide on how to do the teenybin? It's been ages since I've done anything more than root, and I'm not sure what to search for.
chrisphoenix7 said:
Thanks. Do you know if there's an accurate guide on how to do the teenybin? It's been ages since I've done anything more than root, and I'm not sure what to search for.
Click to expand...
Click to collapse
The directions to use the Teenybin are in the OP found here: http://forum.xda-developers.com/showthread.php?t=2230994
The hardest part is getting LGNPST working properly. But that's easy now thanks to the auto install.
Did u fix your phone?
Going to assume teeney bin worked for op. It did for me when I had issues
Sent from my LG-E970
Apologies all, yes I got it working... Mostly. WiFi quit working completely (refused to connect), phone calls took forever to go through, and other odd issues. I'm running it off an old backup of ICS on my external SD. The issues were too much for me to handle, and I was scared to do anything more, so I've got a Moto x. I'm going to try to correctly fix the OG now, so hopefully by documenting the process I can help someone else.
Sent from my XT1058 using xda app-developers app
chrisphoenix7 said:
Apologies all, yes I got it working... Mostly. WiFi quit working completely (refused to connect), phone calls took forever to go through, and other odd issues. I'm running it off an old backup of ICS on my external SD. The issues were too much for me to handle, and I was scared to do anything more, so I've got a Moto x. I'm going to try to correctly fix the OG now, so hopefully by documenting the process I can help someone else.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
i was scared to use teenybin like you but 4.4 lured me into trying. Give teenybin a try its not that bad. you just need to install it, download the teenybin, launch the program, boot your phone into download mode and run the program with the dll and bin files selected.
optimusv45 said:
i was scared to use teenybin like you but 4.4 lured me into trying. Give teenybin a try its not that bad. you just need to install it, download the teenybin, launch the program, boot your phone into download mode and run the program with the dll and bin files selected.
Click to expand...
Click to collapse
I used the Teenybin. It worked enough so I could install my backup. The OS got wiped completely, so I think the kernel just couldn't handle all the stuff it had to anymore.
Sent from my XT1058 using xda app-developers app
I used LGNPST to make full recovery and i dont have any problems with this software.. if want help just ask me.. i will guide you..

[Q] So I decided to wipe everything and startover, and BOOTLOOPED at the Samsung Logo

Here's the fact
1. I was running the 12-31-13 CM11 Nightly with KToonz 12-21 Kernel.
2. I had some problem with the screen not turning on after I accept a call. It's been going on for a few months now, despite doing full wipes in between, so I decided I was gonna just do another wipe and hope that it would somehow solves itself.
3. While I was in TWRP 2.5.2.X , I did factory reset
4. I also wipe /system
5. I flashed CM11 1-1-14 / 12-30 GApps / KTkernel / BootAnimation / SuperSU 1.86
6. During the last portion, I get some running message that it failed to mount E:/ something something & Partition and such
7. Thinking it was a fluke, I pressed reboot and... bootlooped at the Samsung logo screen
8. I Power + Vol UP back into Recovery and flashed the 12-31 CM11 nightly, plus GApps etc,
9. Got the same strings of messages telling that it failed to mount partition and E:/ and /data/ and something lost and found/
10. I rebooted and... Bootlooped at the Samsung logo.
11. I tried to get back into recovery and has been unable to.The little blue "Recovery Booting" seems to appear for a very short time before the phone rebooted again. Seems like it's not there anymore.
Part of me thinks that perhaps the phone's internal memory failed. So far the only thing I can do with it is charge the phone.
Anyone with any knowledge of this, please help.
you gotta go to back odin to get a recovery back on your phone. Also the screen not turning on has been an AOSP issue for awhile, it's not just you and reflashing won't do anything to fix it.
Sent from my CIA sanctioned device
joshm.1219 said:
you gotta go to back odin to get a recovery back on your phone. Also the screen not turning on has been an AOSP issue for awhile, it's not just you and reflashing won't do anything to fix it.
Sent from my CIA sanctioned device
Click to expand...
Click to collapse
What would I do with another recovery? Is the one I have on it now doesn't work anymore?
asianrage said:
What would I do with another recovery? Is the one I have on it now doesn't work anymore?
Click to expand...
Click to collapse
well if you can't boot into it, it's not working right?
asianrage said:
What would I do with another recovery? Is the one I have on it now doesn't work anymore?
Click to expand...
Click to collapse
Just a note keep in mind TWRP is not recommended for CM11. Also I am lucky I have MDK device and a version of the no data wipe stock install, whenever things go wonky (like bootloop on Samsung Logo) I Odin back to stock. make sure the phone works, then restart from scratch and re-root, re-install recovery and reflash CM. I am not super technical so sometimes it can take about 1-2 hours from screwing up the phone to going back to having a working CM11 GS4.
All Hail invisiblek
http://forum.xda-developers.com/showthread.php?t=2559335
stein5830 said:
Just a note keep in mind TWRP is not recommended for CM11. Also I am lucky I have MDK device and a version of the no data wipe stock install, whenever things go wonky (like bootloop on Samsung Logo) I Odin back to stock. make sure the phone works, then restart from scratch and re-root, re-install recovery and reflash CM. I am not super technical so sometimes it can take about 1-2 hours from screwing up the phone to going back to having a working CM11 GS4.
All Hail invisiblek
http://forum.xda-developers.com/showthread.php?t=2559335
Click to expand...
Click to collapse
Thanks for the reply. I've already started the process to flash back to stock MDK. I've been using TWRP for a while and have always been annoyed at how long it'll take to go past the logo screen (if I didn't give up and pulled the battery). Wish me luck.

Categories

Resources