Related
When trying to switch to a different rom, even after factory reseting and clearing all the cache. Parts of the old ROM consist such as the notification tray colors on the pull down. I dont understand because ive cleared it all
You might have to wipe and start again. I had that problem yesterday.
Sent from my ADR6400L using XDA App
David522d said:
When trying to switch to a different rom, even after factory reseting and clearing all the cache. Parts of the old ROM consist such as the notification tray colors on the pull down. I dont understand because ive cleared it all
Click to expand...
Click to collapse
If all you are clearing is the cache, and not wiping data/cache/davlik, that is your problem right there...
Ive cleared them all 3 times now and still getting the same problem.
David522d said:
Ive cleared them all 3 times now and still getting the same problem.
Click to expand...
Click to collapse
You've gotta be doing something wrong then. Never had this problem before.
What could I be doing wrong. This is getting frustrating
Sent from my ADR6400L using XDA App
You may have to do a full factory reset
FishyChips said:
You may have to do a full factory reset
Click to expand...
Click to collapse
HOW?
Can someone please help
I just tried factory reseting from the phone menu itself no luck. I feel like this ROM is glued to my phone regardless how many times i try to kill it.
WHATS THE DEALLLLLLLLLLLLLLL
David522d said:
I just tried factory reseting from the phone menu itself no luck. I feel like this ROM is glued to my phone regardless how many times i try to kill it.
WHATS THE DEALLLLLLLLLLLLLLL
Click to expand...
Click to collapse
When all else fails, follow unroot steps to return to stock and restart the process. Something you're doing doesn't seem to be adding up.
nerozehl said:
When all else fails, follow unroot steps to return to stock and restart the process. Something you're doing doesn't seem to be adding up.
Click to expand...
Click to collapse
I feel losing root wont gain anything more then re rooting.
Its 1 thing the notification colors in the pull down.
What ROM are you trying to flash, and what recovery are you using? The most reliable is arguably the Clockworkmod version...
Sent from my HTC Desire using XDA App
techtechnique said:
What ROM are you trying to flash, and what recovery are you using? The most reliable is arguably the Clockworkmod version...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
I'm running BAMF 1.5 remix, I want to flash BAMF Stripped. Ive been using recovery to flash my roms. I dont know how to use clockwork
David522d said:
I'm running BAMF 1.5 remix, I want to flash BAMF Stripped. Ive been using recovery to flash my roms. I dont know how to use clockwork
Click to expand...
Click to collapse
Returning to stock is a good way to resolve this issue.
So guess what, you can change the color inside the rom settings
Oh thanks for the help
Are you using ROM manager to flash roms or doing it manually? if your not you should try rom manager it has an option that lets you wipe all data before flashing the new rom. i use it and ive never had any problems
David522d said:
I'm running BAMF 1.5 remix, I want to flash BAMF Stripped. Ive been using recovery to flash my roms. I dont know how to use clockwork
Click to expand...
Click to collapse
If you search this forum or Google 'unrevoked', you'll easily find a complete guide and walkthrough on how to root your phone, which'll (as part of the process) load clockworkmod boot recovery.
The next time you reboot, hold the volume down key, which takes you into your boot screen, and use the vol up and down keys to select 'recovery', and press the power button.
From there, wiping your cache partitions and doing a full factory wipe is very straightforward.
That's the easiest way to fully flatten your phone before installing a new ROM.
Edit - the process might differ a bit for your model phone, but the principle will be the same...
Sent from my HTC Desire using XDA App
After flashing nocturnal Rom and installing apps i experienced a slight overheating and i turned off my phone. I turned it back on and I was unable to access the Rom, recovery, or boot loader. I flashed stock with LGPNST and i re-rooted and unlocked the bootloader. I had the same problem upon rebooting. SO...I can flash through LGPNST stock and root but every time i try the boot loader unlock and reboot my phone has the original problems . I've tried the process a few times with the same results.please help.
Dr0!dFreek said:
After flashing nocturnal Rom and installing apps i experienced a slight overheating and i turned off my phone. I turned it back on and I was unable to access the Rom, recovery, or boot loader. I flashed stock with LGPNST and i re-rooted and unlocked the bootloader. I had the same problem upon rebooting. SO...I can flash through LGPNST stock and root but every time i try the boot loader unlock and reboot my phone has the original problems . I've tried the process a few times with the same results.please help.
Click to expand...
Click to collapse
Nevermind that i got it working
Dr0!dFreek said:
Nevermind that i got it working
Click to expand...
Click to collapse
It may be helpful to someone else, if you were to explain how you fixed it.
Yes, it would indeed be quite helpful if you could elaborate... because this just happened to me and I'm stumped...
I followed the same exact procedure I've used other times without error...
Except that now, after LGNPST, then root, then freegee... go to restart the phone and it hangs... won't boot up. What gives?
I repeated the process and did a factory reset after LGNPST back to stock, since I noticed (oddly enough) that all my apps were still there after LGNPST (full, to 100%)...
Still no luck...
EDIT-- Can't for the life of me figure this effing thing out. LGNPSTed I don't know how many times... with factory reset, without... I've tried fully relocking and unrooting the device... both through the FreeGee app *and* manually through adb... no error mssgs, double-checked... everything followed to the letter. There's only one constant each time: Once I've re-unlocked the bootloader (either with the app or through adb)... the phone is basically softbricked... once I turn the power off, it is A) not possible to boot into the stock rom, B) not possible to access fastboot menu, and C) not possible to boot into recovery. The only thing it *is* possible to do is get into download mode... and from there I'd just have to LGNPST again, but what's the point, because once I've done that and tried to unlock again, I already know what's coming. Never been this frustrated with a phone before, any help would be greatly appreciated.
EDIT 2-- No luck. LGNPSTed to stock once more, and factory reset, because yet again, all my apps were still intact... idk. Anyways, decided to do some hunting around with adb, and "adb reboot recovery" produced an error screen... the android lying on his back with case open... am I to assume this means there is a problem with my recovery partition that could be causing my difficulties... or would one expect to see this screen when trying to access recovery on the stock phone?
adfurgerson said:
It may be helpful to someone else, if you were to explain how you fixed it.
Click to expand...
Click to collapse
Honestly I don't know how it was resolved. I lgpnsted and rooted and unlocked the bootloader like 5 times.I got into recovery a few times but then got the same problem two more times. The last time I got into recovery I managed to flash a custom kernel and everything was fine from then on. I just don't understand how this problem is caused or even how it is truly fixed.
Sent from my LG-E970 using xda premium
dht2005 said:
Yes, it would indeed be quite helpful if you could elaborate... because this just happened to me and I'm stumped...
I followed the same exact procedure I've used other times without error...
Except that now, after LGNPST, then root, then freegee... go to restart the phone and it hangs... won't boot up. What gives?
I repeated the process and did a factory reset after LGNPST back to stock, since I noticed (oddly enough) that all my apps were still there after LGNPST (full, to 100%)...
Still no luck...
EDIT-- Can't for the life of me figure this effing thing out. LGNPSTed I don't know how many times... with factory reset, without... I've tried fully relocking and unrooting the device... both through the FreeGee app *and* manually through adb... no error mssgs, double-checked... everything followed to the letter. There's only one constant each time: Once I've re-unlocked the bootloader (either with the app or through adb)... the phone is basically softbricked... once I turn the power off, it is A) not possible to boot into the stock rom, B) not possible to access fastboot menu, and C) not possible to boot into recovery. The only thing it *is* possible to do is get into download mode... and from there I'd just have to LGNPST again, but what's the point, because once I've done that and tried to unlock again, I already know what's coming. Never been this frustrated with a phone before, any help would be greatly appreciated.
EDIT 2-- No luck. LGNPSTed to stock once more, and factory reset, because yet again, all my apps were still intact... idk. Anyways, decided to do some hunting around with adb, and "adb reboot recovery" produced an error screen... the android lying on his back with case open... am I to assume this means there is a problem with my recovery partition that could be causing my difficulties... or would one expect to see this screen when trying to access recovery on the stock phone?
Click to expand...
Click to collapse
I had access to stock and I could root it. One thing that bothers me is that when I flash with lgpnst my data isn't erased and I feel like there may be a problem there of whether lgpnst is even taking our phones back to stock completely
Sent from my LG-E970 using xda premium
Dr0!dFreek said:
I had access to stock and I could root it. One thing that bothers me is that when I flash with lgpnst my data isn't erased and I feel like there may be a problem there of whether lgpnst is even taking our phones back to stock completely
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
Yes, I know, I've had that same thought. I think I've done what you did... LGNPSTing and unlocking etc... but even as I try like hell, I haven't been able to get back into recovery even once.
dht2005 said:
Yes, I know, I've had that same thought. I think I've done what you did... LGNPSTing and unlocking etc... but even as I try like hell, I haven't been able to get back into recovery even once.
Click to expand...
Click to collapse
Sorry I wish I could help but I don't know that much.
Sent from my LG-E970 using xda premium
Dr0!dFreek said:
Sorry I wish I could help but I don't know that much.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
It's okay, I posted in XsMagical's thread, I'm hoping he can shed some light.
But actually, I'm just glad that I'm not the only one this has happened to...because if this error is reproducible, it can probably be fixed... so that's good. Thanks for your replies!
dht2005 said:
Yes, I know, I've had that same thought. I think I've done what you did... LGNPSTing and unlocking etc... but even as I try like hell, I haven't been able to get back into recovery even once.
Click to expand...
Click to collapse
There have been a small number of phones that will not unlock with standard freegee. They can be unlocked but it is riskier, you would need to talk to Shelnutt in irc.
http://webchat.freenode.net/?channels=lg-optimus-g
adfurgerson said:
There have been a small number of phones that will not unlock with standard freegee. They can be unlocked but it is riskier, you would need to talk to Shelnutt in irc.
http://webchat.freenode.net/?channels=lg-optimus-g
Click to expand...
Click to collapse
Our phones successfully unlocked with freegee originally but some error caused us to lose access to the bootloader and corrupt whatever ROM we were on and then cause errors where we could use free gee but run into problems. In my situation the problem was resolved somehow and free gee worked fine afterwards
Sent from my LG-E970 using xda premium
I'll try and post how I fixed it, but it is recovery related. I'm also working on another way to reset our phones without using LGNPST, but I've been really busy. I'm close though and I believe it will be easier and faster.
Sent from my LG-E970 using Tapatalk 2
I'm still at work but I read most of the post and will try to see if there is a work around
Stroked from my Dirty Nocturnal'd Optimus G
droidiac13 said:
I'll try and post how I fixed it, but it is recovery related. I'm also working on another way to reset our phones without using LGNPST, but I've been really busy. I'm close though and I believe it will be easier and faster.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
XsMagical said:
I'm still at work but I read most of the post and will try to see if there is a work around
Stroked from my Dirty Nocturnal'd Optimus G
Click to expand...
Click to collapse
Thank you guys! I'm willing to try anything at this point. I appreciate it. And droidiac... this phone could really use a quick, easy, and reliable way to completely reset back to 100% stock, so that sounds exciting!
dht2005 said:
Thank you guys! I'm willing to try anything at this point. I appreciate it. And droidiac... this phone could really use a quick, easy, and reliable way to completely reset back to 100% stock, so that sounds exciting!
Click to expand...
Click to collapse
I just picked up a new laptop today so it's going to be a while unless it goes well.
Sent from my LG-E970 using Tapatalk 2
Just for the sake of documentation, I made a little log of my most recent attempt at getting back into the fastboot menu... obviously it's convoluted, but hey... sometimes experimentation gets results. This time, however, it did not... still no luck.
LGNPST back to stock
factory reset from settings->backups
run root exploit
restore original backups from first time freegeeing via adb using carrett's method
reboot
full unroot from SU app
factory reset
LGNPST to stock
re-run root exploit
reboot
re-unlock with freegee script (adb)
disconnect cable
reboot
(right here is the failure. after running "power off and reboot" from the power button menu, phone shuts off. it tries to start up, then i get a quick flash of the LG logo, straight to a backlit black screen that hangs indefinitely. only thing possible from here is to enter download mode.)
Back to the drawing board...
Same here
dht2005 said:
Just for the sake of documentation, I made a little log of my most recent attempt at getting back into the fastboot menu... obviously it's convoluted, but hey... sometimes experimentation gets results. This time, however, it did not... still no luck.
LGNPST back to stock
factory reset from settings->backups
run root exploit
restore original backups from first time freegeeing via adb using carrett's method
reboot
full unroot from SU app
factory reset
LGNPST to stock
re-run root exploit
reboot
re-unlock with freegee script (adb)
disconnect cable
reboot
(right here is the failure. after running "power off and reboot" from the power button menu, phone shuts off. it tries to start up, then i get a quick flash of the LG logo, straight to a backlit black screen that hangs indefinitely. only thing possible from here is to enter download mode.)
Back to the drawing board...
Click to expand...
Click to collapse
Just for documentation and in case I can help solving this, I am having the same problem, I explain my case with more detail on the FreeGree Thread, but pretty much I am on the same ship as you, I have tried after LGNPST, with and without factory reset, with the Google Play application and with the desktop application, but same result, black screen after restart.
I have a brand new phone, picked it less than a week ago, could LG have changed something? bootloader/recovery partition sizes? something?
I am still within the 14 days period and as much as I like the phone, if I can't bootloader unlock, means I will be stuck on stock ROM, and that is something I don't want... might as well go and change it for a different phone, or sell it and get a nexus 4...
I get same.thing. black screen after freegee. Its two days old. So now what!?
Sent from my LG-E970 using xda premium
Its a known issue. IRC guys can help. Something about the misc.IMG file getting corrupted
Sent from my Nexus 7 using xda app-developers app
nygfan760 said:
Its a known issue. IRC guys can help. Something about the misc.IMG file getting corrupted
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
How does this happen from a random stock ROM. I think I was using nocturnals ROM and how was the problem resolved through multiple flashes?
Sent from my LG-E970 using xda premium
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Try reflashing a kernel. Might try stock first, then maybe Elkay's or dsb's writeable.
In case you're doing it a different way, try flashing it this way: flash the boot.img using the Flash Image GUI app. Then flash the corresponding modules for that specific boot.img kernel (can't mix and match) in Recovery.
If that doesn't help the situation, you may need to flash a different radio.
HTH!
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
have you tried a completly different rom?
.torrented said:
have you tried a completly different rom?
Click to expand...
Click to collapse
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
saabguy93 said:
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
Click to expand...
Click to collapse
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Perhaps you accidentally flashed your radio partition? Reflash your radio and you'll probably be good to go. Either that or like someone else said try a different sim card.
Bigandrewgold said:
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I put the SIM in my Nexus and I dont have any problems at all.
saabguy93 said:
I put the SIM in my Nexus and I dont have any problems at all.
Click to expand...
Click to collapse
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Run the RUU again but this time try and just booting into android from the RUU and trying to use your phone
saabguy93 said:
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Click to expand...
Click to collapse
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah so it was a rom issue then
Sent from my HTC6435LVW using XDA Premium HD app
Not a Rom issue, I've had the problem on viper and hatka, both before and after soff and new radio. New kernel, old kernel.
I'm getting ready to try stock 1.15 before I ruu.. will report back.
Edit: Fresh off RUU, with the old radios flashed before the RUU. Still no change. Tried turning phone off, remove sim card, phone on, try to use cell connection (obvious failure), phone off, insert sim card and boot. Still no good. About to try above method using CWM and Digital Dream, as soon as it downloads.
Edit 2: Still no such luck. After digging through system logs, there's quite a few errors pertaining to the radio, IccCard, and RIL. One that particularly caught my eye was an error that there stated Ril_get_icc_status returned an error, and it should never return an error. Unfortunately, I didn't get a capture on the time I saw that, the radio reset which Su to reset which caused catlog to reset. Still have quite a few errors pertaining to SIM problems as well. I am way over my head after this point. I can interpret java, and linux.. but not so much understand when they're mixed together in Android.
http://www.pastebin.ca/2317800 This is logcat capture I got of the radio log. Unknown technology doesn't sound good to me....
http://db.tt/nbYfqEkb A full system log as soon as I could save after the force close. Couple things here and there.
I suppose if I can't get it fixed in a day or two.. off Verizon for a replacement. What's the purpose of a phone if I can't make phone calls on it?
Sent from my HTC6435LVW using xda premium
Unless an error loops continually, its okay.
Have you tried to manually select a different network? I'm not quite sure how to do it on a sense rom, but I do know that when I was messing around within my CM10 build and changed to the wrong network type, I lost 4G data in sense. I reflashed CM10, selected a different network and then flashed back and it was working.
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
CharliesTheMan said:
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
Click to expand...
Click to collapse
Any luck figuring this out? I have the same issue and have tried radios, kernels, ROMs, RUU, and am still getting the same error message.
jc332986 said:
I was having "com.android.phone" issues. I relocked then ran the RUU. It didn't fix the error. I unlocked, tried to go Into recovery and there was no recovery. I flashed cwm recovery, flashed busy box/superuser, and rebooted. I flashed cubed kernel. The fix for the phone was to fix permissions with system write capabilities. I'm not sure why the RUU didn't put the phone all the way back to stock.
Click to expand...
Click to collapse
spjoneser said:
I had this problem with my first DNA, warrantied it out after trying all the same things, flashing different roms, RUUing. After replacement I came across a thread somewhere and found that someone had fixed the same problem by simply fixing permissions before doing anything else, sounds like once you flash something else you're screwed.
Anyone try that first?
Click to expand...
Click to collapse
Anyone have an idea about the permissions described here?
same issue
dragonstalker said:
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Click to expand...
Click to collapse
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
jimmydee62 said:
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
Click to expand...
Click to collapse
I'm in the same boat with you my friend :crying:...Can someone please help us. PLEASE!!!
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
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..