[Тестирование]LeNs FLARE Testing Thread
Thread Closed.
User was a secondary account of a banned "developer".
All I have to say is you freaking rock man. Thank you for ALL you are doing for us! I will test for you anytime I get a chance.
Sent from my EVO using Xparent Blue Tapatalk 2
I'll test anything you want tested, but it's gonna take time. I am waiting for a warranty replacement from Sprint.
Had to go to sense ftm. The wife could have my baby at any moment. But ill be ready again sometime next week
Sent from my EVO using Xparent Red Tapatalk 2
epic4gt said:
Had to go to sense ftm. The wife could have my baby at any moment. But ill be ready again sometime next week
Sent from my EVO using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Great.Good lUCK ;D
Lens_flare said:
http://d-h.st/Wuy
has anyone tested this?
And also Rate this thread 5 stars
Click to expand...
Click to collapse
Downloading right now man
Ill let you know in about 20 minutes
edit: loopin. warnings/errors/fatal and full logcat for you lens :good:
pm'd you my gtalk. hit me up when you get on
edit: re set up my pastebin for you. heres the links.
dont just say its loopin. logcat or gtfo. pm me if you dont know how.
Warnings, etc...: http://pastebin.com/sD71JEyM
Full Log: http://pastebin.com/f8e2Ve2Z
Tested AOKP, stuck on initializing swag
Dab Life
Lens_flare said:
http://d-h.st/Wuy
has anyone tested this?
And also Rate this thread 5 stars
Click to expand...
Click to collapse
Following up here, regarding the AKOP-build from this morning, to keep the threads clean:
Also got stuck at the "initializing swagger" screen. When I flashed back to PA, I noticed an issue with "sd card" [the internal storage, not my external card]. Factory resets were throwing errors [failing] and there was no way to mount the storage. I ultimately reformatted and that cleared the issue. Before the formatting, I could not use my Alarm application [G-Alarm] nor could I view the Gallery. After the format, everything worked.
I'm S-ON, hboot 1.19. Komodo rls21.
Flash the akop build, booted all the way up had no data and acore error repeatedly
ThreeFaces said:
Following up here, regarding the AKOP-build from this morning, to keep the threads clean:
Also got stuck at the "initializing swagger" screen. When I flashed back to PA, I noticed an issue with "sd card" [the internal storage, not my external card]. Factory resets were throwing errors [failing] and there was no way to mount the storage. I ultimately reformatted and that cleared the issue. Before the formatting, I could not use my Alarm application [G-Alarm] nor could I view the Gallery. After the format, everything worked.
I'm S-ON, hboot 1.19. Komodo rls21.
Click to expand...
Click to collapse
Thats because you dirty flashed back to pa..
Cj719 said:
Flash the akop build, booted all the way up had no data and acore error repeatedly
Click to expand...
Click to collapse
You completely wiped everything and flashed?
My guess is you also dirty flashed aokp over whatver you were running.
I tried the aokp build this morning and got stuck at boot ani. I wiped both caches, system, and factory reset 3 times before flashing. Just in case I missed something I did it all again with the same issue.
Sent from my EVO using Xparent Blue Tapatalk 2
I never dirty flash, always factory reset...I typically don't format the system partition. Should I change my process? I don't mind taking a few extra steps to ensure a clean install.
Thanks dude.
Sent from my EVO using xda app-developers app
ThreeFaces said:
I never dirty flash, always factory reset...I typically don't format the system partition. Should I change my process? I don't mind taking a few extra steps to ensure a clean install.
Thanks dude.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Definitely always format system...
Sent from my EVO using Tapatalk 2
ThreeFaces said:
I never dirty flash, always factory reset...I typically don't format the system partition. Should I change my process? I don't mind taking a few extra steps to ensure a clean install.
Thanks dude.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You should always format system when changing ROMs. The system partition is where the ROM is flashed to so not wiping that is bound to cause problems. I wipe everything except sdcards 3 times just to make sure.
Sent from my EVO using Xparent Blue Tapatalk 2
Youdug I did dirty flash over 2.99Pa but I also did a clean install still had no data
Sent from my EVO using xda app-developers app
Cj719 said:
Youdug I did dirty flash over 2.99Pa but I also did a clean install still had no data
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Clean install meaning you wiped system, data, cache, and dalvik?
Youre the only one it booted for if you did.
Yeah full wipe and booted just no data... 1st boot after apps load it rebooted on its on and no issues just no data
Sent from my EVO using xda app-developers app
Related
Hello,
First and foremost, I'm loving this rom. I'm a noob and getting my hands dirty figuring all this out.
Now with that said:
When I try to connect to my wifi network it keeps saying authentication error occurred. I have tried everything and the only thing that fixes it is restoring my backup to my stock rom.
Please help!!!!
Sent from my SAMSUNG-SGH-I717 using xda premium
Smerleau said:
Hello,
First and foremost, I'm loving this rom. I'm a noob and getting my hands dirty figuring all this out.
Now with that said:
When I try to connect to my wifi network it keeps saying authentication error occurred. I have tried everything and the only thing that fixes it is restoring my backup to my stock rom.
Please help!!!!
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I will say 90% of the people in here will say it is not the rom. just because theres seems to work. and i tend to agree. what have you tried to fix it? besides going back (to Stock). i have not had any issues with WiFi on Serephim yet, so i can not say what a fix would be. maybe wipe your cache's. when i had that issue on GB i had to reinstall the kernel and boom it worked. but seeing as though we do not have one yet for ICS. i would say wipe and worst case reinstall the from after a very Thurough Wiping Process.
the2rrell said:
I will say 90% of the people in here will say it is not the rom. just because theres seems to work. and i tend to agree. what have you tried to fix it? besides going back (to Stock). i have not had any issues with WiFi on Serephim yet, so i can not say what a fix would be. maybe wipe your cache's. when i had that issue on GB i had to reinstall the kernel and boom it worked. but seeing as though we do not have one yet for ICS. i would say wipe and worst case reinstall the from after a very Thurough Wiping Process.
Click to expand...
Click to collapse
I have wiped cache a few times and I just downloaded another rom and got the same issue.. The only time it works is on stock GB
Sent from my SAMSUNG-SGH-I717 using xda premium
Smerleau said:
I have wiped cache a few times and I just downloaded another rom and got the same issue.. The only time it works is on stock GB
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Then if your into flashing right now, just try either the superwipe.
Or this is how i wipe.
I factory default/format usb from inside the rom.
I wipe factory/data from cwm
i wipe cache partition from cwm
i wipe delvik from cwm
then i flash "Rom" and reboot.
this leaves nothing from previous roms and or Gingerbreak roms.
try that and see if it works. if not then i am out of ideas until a kernel source is released.
Ok i will try that and see if it works...
Thank you!!!
Sent from my SAMSUNG-SGH-I717 using xda premium
the2rrell said:
Then if your into flashing right now, just try either the superwipe.
Or this is how i wipe.
I factory default/format usb from inside the rom.
I wipe factory/data from cwm
i wipe cache partition from cwm
i wipe delvik from cwm
then i flash "Rom" and reboot.
this leaves nothing from previous roms and or Gingerbreak roms.
try that and see if it works. if not then i am out of ideas until a kernel source is released.
Click to expand...
Click to collapse
I fixed it.... USER ERROR.. I Don't want to admit this but I was entering the wrong password and my old Rom had the password saved so I never had to enter it...
Sent from my SAMSUNG-SGH-I717 using xda premium
Good morning guys. I'm having trouble with my Samsung galaxy SGH-I777. Every time I open an app that uses he camera (ie camera, barcode scanner, flashlight, camera) he flash goes off then it just reboots he phone. I've already done a factory restore. I even went into recovery mode and wipe cache and did a restore from there. I've also just downloaded the new ICS update and it still didn't fix the problem. Please help
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
when you say factory restore does that mean you completely wiped the phone and flashed back to stock rom. If not, that's what I would do to determine if we're looking at a hardware or software issue.
No I didn't flash it back to stock. How would I even do that?
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
pichienyfl said:
No I didn't flash it back to stock. How would I even do that?
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Read the stickies
(⊙＿⊙)
OK I flashed a new rom but it didn't work. Flashed back to ics still doesn't work
Sent from my SGH-I777 using xda app-developers app
I would flash back to stock. If it still does it, bring it in to at&t service center and show them. They can give you a replacement. Or you can call them. Just make sure your on non rooted stock firmware.
a full wipe and reflash is required before posting any problems. because99 % of the time it's user error. Did you fully wipe system, cache, data, and run the kernel cleaning scriptbefore posting this issue?
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Yes. I did a full wipe and restore. Installed a new rom and still nothing can I maybe install a new camera apk?
Sent from my SGH-I777 using xda app-developers app
pichienyfl said:
Yes. I did a full wipe and restore. Installed a new rom and still nothing can I maybe install a new camera apk?
Sent from my SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
IF this is happening across roms, and assuming correct firmware, with a clean install (factory reset, no misc apps installed) then I'd say you have a hardware problem. If you've flashed incorrect firmware then a reset won't help you until you flash back to the correct firmware. Of course all of this moot if its physical damage caused by dropping the phone or maybe water damage. If you're completely stock and haven't subjected the phone to any physical abuse, then return the phone for a new one.
Phalanx7621 said:
a full wipe and reflash is required before posting any problems. because99 % of the time it's user error. Did you fully wipe system, cache, data, and run the kernel cleaning scriptbefore posting this issue?
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
thanks! went back to full stock and problem went away
pcamlin said:
thanks! went back to full stock and problem went away
Click to expand...
Click to collapse
Awesome! Glad yer back in business
Sent from my SGH-I777 using Tapatalk 2
CallMeAria said:
IF this is happening across roms, and assuming correct firmware, with a clean install (factory reset, no misc apps installed) then I'd say you have a hardware problem.
. . .
Click to expand...
Click to collapse
This.
Run fix permissions in recovery (last resort).
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
adma84 said:
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
There is only one superwipe for our phone. There is nothing to compare it to, and no need as it works fine. The link you posted has nothing to do with our device.
http://forum.xda-developers.com/showthread.php?p=27166189
Ta da!
I've never understood super wipes. I just do it manually.
No need for a superwipe. Just Factory Reset and wipe System and you're ready to flash. That's never once given me a problem.
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
theoner1 said:
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
You shouldn't have to wipe boot.
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Exactly I never even heard of a Superwipe until the 3d came out. Never had to flash one since I had my g1 and i'm not going g to start now
Sent from my EVO using xda premium
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
theoner1 said:
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
SoraX64 said:
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
Click to expand...
Click to collapse
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
theoner1 said:
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
SoraX64 said:
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
Click to expand...
Click to collapse
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
theoner1 said:
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm, interesting because I have gone back and forth between CM10 and MeanRom. I have never had an issue. I love the speed and fluidity of CM10 but the Sense camera is just to good at this point.
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
firmbiz94 said:
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
Click to expand...
Click to collapse
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
I think a lot of people got used to using these from the og evo. CWM was thought to have trouble wiping so most would wipe two or three times to make sure it didn't miss anything. I haven't heard of that being an issue for a long, long time though.
One thing that it may help with though is if the ROM doesn't format the system partition. I've spent hours trying to track down bugs only to realize leftover system files were wreaking havoc with the new ROM.
theoner1 said:
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm that's interesting, i remember i flashed tranquility rom and was working great! then tested cmx and at the same time tranquility was updated and that error was still present on the new tranquility rom, but i thought it was the rom so i flashed another sense rom but, this time i used superwipe after manually wiping all and no error anymore, since then i didnt use tranquility thinking it was the new update. now i always use superwipe.
time to go back to tranquility :fingers-crossed::fingers-crossed:
Im currently running Viper4g on my evolte but ive been checking out CM10 and i want to try it out. What would be the usual steps to take when flashing a new rom?
I would do a full NAND backup with whatever recovery you have in case you want to revert back. Then do a full wipe (system, data, cache, dalvik) and flash the new ROM.
Read the guide in my sig lol, explains just about anything you could think of and has a list of basic trouble shooting scenarios that some users are likely to encounter
Come on guys you tell me what a great write up I have and never recommend it?
Edit: I feel like I'm trying to sell myself and I am not a wh***
*runs away in tears*
Of course it's great
However, you said yourself: it's a great reference guide, but not a step-by-step for anything.
The OP asked for steps to take when changing ROMs
Yes but the title of his thread says tips for someone new....ahaaaa.. *cue classic black and white cinema fiend music*
I so wrote it to avoid all these brick and corrupt card threads
Touche...
*bows in defeat*
Make sure you check out om4's AWESOME guide, "DON'T PANIC", here: http://forum.xda-developers.com/showthread.php?t=1869377
*runs off to bed*
bilbo524 said:
Touche...
*bows in defeat*
Make sure you check out om4's AWESOME guide, "DON'T PANIC", here: http://forum.xda-developers.com/showthread.php?t=1869377
*runs off to bed*
Click to expand...
Click to collapse
Suck up
Sent from the depths of hell
Quiet let me have my moment lol
Absolutely not lol
Sent from the depths of hell
Dude, check out the last 2 scenarios, went to the head and the gf added them. I laughed so hard
Well it looks like i did something wrong cause my phone is stuck in a constant boot loop. I followed the instructions on http://forum.xda-developers.com/showthread.php?t=1794867
for
How to flash a boot image if S-ON Dev Unlocked 1.15 HBOOT:
I was trying to install CM10 btw. I did a backup using twrp tried restoring but that didnt work. What can i do now to fix it?
Maybe the cmx was a bad download or bad flash. If you fasboot flashed the aosp boot IMG you might have problems trying to restore a sense backup. I would download cmx again redo all the steps.
I'm not sure if you have to flash a sense boot IMG when restoring a backup , I would try it tho to be safe.
Hey man. The instructions work, so start over and make sure you follow every step including wiping.
Sent from my EVO using xda app-developers app
Did you do a full factory reset and wipe system, data, cache, and dalvik before flashing the ROM?
Sent from my LTEvo powered by CM10 using XDA Premium
bilbo524 said:
Did you do a full factory reset and wipe system, data, cache, and dalvik before flashing the ROM?
Sent from my LTEvo powered by CM10 using XDA Premium
Click to expand...
Click to collapse
No i didnt. Right now i just want to get my phone working again since i have work in an hour. What should i do to get it working again?
Start the process over just make sure you wipe fully before flashing anything. Cache, dalvik, factory reset and system.
Sent from my EVO using xda app-developers app
To restore your existing backup, you will need to reflash your old viper4g kernel (boot.IMG) first with fastboot.
Sent from my LTEvo powered by CM10 using XDA Premium
bilbo524 said:
To restore your existing backup, you will need to reflash your old viper4g kernel (boot.IMG) first with fastboot.
Sent from my LTEvo powered by CM10 using XDA Premium
Click to expand...
Click to collapse
So just follow the steps from the link i posted using the boot.img from the viper4g download?
Yes, follow the same steps you used to flash the CM10 kernel to reflash the viper4g kernel. Your exisiting viper4g backup should then boot OK.
Sent from my LTEVO powered by CM10 using XDA Premium
bilbo524 said:
Yes, follow the same steps you used to flash the CM10 kernel to reflash the viper4g kernel. Your exisiting viper4g backup should then boot OK.
Sent from my LTEVO powered by CM10 using XDA Premium
Click to expand...
Click to collapse
ok im trying to restore again, hopefully it works. i have work in 45 minutes and being without my phone would suck.
It worked! Thanks for the help guys. Im gonna leave CM10 alone until the weekend when im off.
Relevant;
S-OFF, TWRP, CM10 based ROM (RootBox)
Everything is working except for my phone. I get 1x data, but the phone number won't show up, I can't dial out without getting a "your account doesn't have this feature" recording.
The MEID comes up correct, but I can't do ##786# or any PRL updates.
I didn't see anything in the FAQ's, but I'm assuming this is because it's not based off of a stock sprint rom. How can I do the PRL/Provisioning?
Flash a sense rom and update Profile and PRL then flash back to RootBox
bigdaddy619 said:
Flash a sense rom and update Profile and PRL then flash back to RootBox
Click to expand...
Click to collapse
Roger. I'll give it a shot. Thank you.
bigdaddy619 said:
Flash a sense rom and update Profile and PRL then flash back to RootBox
Click to expand...
Click to collapse
In addition, if that doesn't work for you, try to make a phone call once you've flashed a Sense ROM. Sprint may have to re-provision your service, at which point you'd be good to go.
Sent from my EVO using xda premium
FinZ28 said:
In addition, if that doesn't work for you, try to make a phone call once you've flashed a Sense ROM. Sprint may have to re-provision your service, at which point you'd be good to go.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yep. One thing I neglected to mention is that I updated the radio firmware after I went S-off before I loaded the new rom. I was still using Freshmod previously and everything was working great. Since Fresh isn't in development anymore I figured it was time for some upgrades.
Now I can't load a stock rom on to it. Every time I try to install a rom through twrp it reboots about 10-15 seconds into the load, when I get back into TWRP /sdcard is corrupt and has to be reformatted before it's recognized again.
Already did a factory reset/wipe in TWRP 2.6.0.0.... Is this an issue where TWRP has to be downgraded?
defekticon said:
Now I can't load a stock rom on to it. Every time I try to install a rom through twrp it reboots about 10-15 seconds into the load, when I get back into TWRP /sdcard is corrupt and has to be reformatted before it's recognized again.
Already did a factory reset/wipe in TWRP 2.6.0.0.... Is this an issue where TWRP has to be downgraded?
Click to expand...
Click to collapse
Shouldn't be. Boot to recovery and mount your internal storage to your computer. You should get the option to format it. The file system type is FAT32. Should be good to go afterwards. The issue seems to be related to swapping back and forth between Sense and AOSP, but I personally have never had the problem.
Sent from my EVO using xda premium
FinZ28 said:
Shouldn't be. Boot to recovery and mount your internal storage to your computer. You should get the option to format it. The file system type is FAT32. Should be good to go afterwards. The issue seems to be related to swapping back and forth between Sense and AOSP, but I personally have never had the problem.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I had to do an advanced wipe in TWRP and wipe everything, format the internal SD, found a small (350 meg) sense rom (UR/EVO), that loaded this time. I was able to go in and activate the phone and do an activation and PRL update.
Going to try and reload Rootbox now... Wish me luck.
defekticon said:
I had to do an advanced wipe in TWRP and wipe everything, format the internal SD, found a small (350 meg) sense rom (UR/EVO), that loaded this time. I was able to go in and activate the phone and do an activation and PRL update.
Going to try and reload Rootbox now... Wish me luck.
Click to expand...
Click to collapse
Good luck. You should be fine now
Sent from my EVO using xda premium
FinZ28 said:
Good luck. You should be fine now
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Just a follow up - it worked. I can now use my phone in Rootbox!
Thanks!