Help!!
I cannot go from beta 2 to beta 3. Everyone I install beta 3 even wiping all data/partition/dalvik. After first system reboot the phone goes on a loop right after the Samsung logo.
Tried a different rom such as aokp and same thing happened.
Reflashed beta 2 and here we are... I don't have any more ideas..
Anyone??
Sent from my SPH-D700 using XDA
Sent from my SPH-D700 using XDA
Redownload the rom? Sounds like a bad download.
Sent From My Sprint Galaxy Nexus via XDA Premium
I tried 2 different rooms already...
Tomorrow I can try to download on my PC since tonight I did using my phone but I really don't think that's the issue.
Sent from my SPH-D700 using XDA
teco2010 said:
I tried 2 different rooms already...
Tomorrow I can try to download on my PC since tonight I did using my phone but I really don't think that's the issue.
Sent from my SPH-D700 using XDA
Click to expand...
Click to collapse
If that doesn't work.. I would suggest you Odin back to stock and repartition. Reroot and try and flash it with a fresh download. This may solve your issue.
Sent From My Sprint Galaxy Nexus via XDA Premium
I got stuck in a boot loop as well coming from beta 2 to 3... the CM9 boot screen would just keeping running and the phone would vibrate every minute or so.
I believe it was because I didn't uninstall cpu voltage before I flashed.
Wiping data and then installing beta 3 on a fresh slate worked fine for me... Didnt have to odin.
Related
I have not tried to use it on an not rooted version of JB. Just wondering if anyone can chime in and share their experience. I know that since the update the flash counter will go up to 1 everytime you reboot your phone, triangle away says it reset the flash counter but next boot it is increased again. Would that be the reason I cannot use the All share cat dongle? It worked fine on ICS rooted but not on JB. EDIT:
The is a thread in general about three flash counter with Doc Holiday and chainfire trying to figure this out. I think it's best if we post there.
http://forum.xda-developers.com/showthread.php?t=2010157
Sent from my Nexus 7 using Xparent Cyan Tapatalk 2
Anybody?
Sent from my Nexus 7 using Xparent Cyan Tapatalk 2
Had to reset the dongle after updating to JB(stock root) then all worked fine. Before resetting, TV hung at connecting screen even tho phone said connected.
Sent from my SGH-T999 using xda app-developers app
I tried resetting it several times but it still doesn't connect. I tried to but then says all share cast is closing to connection... I tried with stock recovery because I thought that maybe because the flash counter keeps resetting itself, thought CWM was resetting the counter but even with the stock recovery it doesn't work. Samsung really sucks with what they did with this update... there is no way to keep the flash counter at zero....
Sent from my Nexus 7 using Xparent Cyan Tapatalk 2
I updated with wildchild's Odin firmware then flashed his stock de-odexed rom with twrp. Used triangle away one time and reset the dongle and everthing is working as it should.
Sent from my SGH-T999 using xda app-developers app
LoGiK915 said:
I updated with wildchild's Odin firmware then flashed his stock de-odexed rom with twrp. Used triangle away one time and reset the dongle and everthing is working as it should.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I am using wildchild' s xquisit and can't get it to connect. Maybe there is something missing in the Rom...
Sent from my Nexus 7 using Xparent Cyan Tapatalk 2
Samsung galaxy note 2 n7100
I don't think it has anything to do with the rom, this problem came up for me after rooting. does anyone no of any file changes when rooting ? my allshare is not working if i flash it back to stock rom
would like to know the answer also. My non rooted note 10.1 works fine. My rooted Note 2 doesn't
Run Triangle Away. That worked for me!
nilezon said:
Run Triangle Away. That worked for me!
Click to expand...
Click to collapse
Not working for me. What ROM are you on? Custom recovery or stock? Stock kernel or custom?
In the general forum is a thread about the flash counter and doc holiday and chain fire are trying to figure out what the cause is.
Here is the link.. Probably better if this gets discussed in in one central thread...
http://forum.xda-developers.com/showthread.php?t=2010157
Sent from my Nexus 7 using Xparent Cyan Tapatalk 2
There is an update in the play store.
http://www.google.com/url?sa=t&sour...n4HIAw&usg=AFQjCNGqZaX6XbjBoGP7bS8gzXBLHmhHQQ
jcbofkc said:
There is an update in the play store.
http://www.google.com/url?sa=t&sour...n4HIAw&usg=AFQjCNGqZaX6XbjBoGP7bS8gzXBLHmhHQQ
Click to expand...
Click to collapse
I updated but still no go. I am going to try a different ROM today and see if that helps...
Sent from my SGH-T999 using Xparent Cyan Tapatalk 2
Hi all
I can't seem to figure this out
I passed down my gnex to the wife as I got a n4
Now when i had it there were no issues of random reboots
I have cm10 nightly loaded on it with the cm kernel and its getting random reboots
I cannot find out what it is... I have tried different kernels and still the same issue... I have tried diff ROMs. I tried fitsnugly cm10 and same issue,,.
Anyone have any ideas as to what I can do... I've tried everything I can think of
Its random as in it happens sometimes when she is browsing or it will jut be sitting on on the table and then reboot without anyone touching it...
Ugh. Help
Sent from my A510 using Tapatalk HD
I would put the last stable release on there, unless u don't mind working on her phone..
Do u format system in recovery when u install and new ROM?
Or maybe install ur nandroid backup and c if that works
Sent from my Galaxy Nexus using Tapatalk 2
LiquidXed said:
I would put the last stable release on there, unless u don't mind working on her phone..
Do u format system in recovery when u install and new ROM?
Or maybe install ur nandroid backup and c if that works
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yup
I did a full wipe in recovery before giving it to her.
Actually what had happened is I wiped everything including SD card and it wouldn't boot so i restored to stock via Odin and toolkit. Then started from scratch. Installed fitsnugly ROM etc
Sent from my Nexus 4 using Tapatalk HD
Try a different ROM away from cm. Like aokp or paranoid and see if u have the same issues on those.
Sent from my Galaxy Nexus using xda premium
c_86 said:
Yup
I did a full wipe in recovery before giving it to her.
Actually what had happened is I wiped everything including SD card and it wouldn't boot so i restored to stock via Odin and toolkit. Then started from scratch. Installed fitsnugly ROM etc
Sent from my Nexus 4 using Tapatalk HD
Click to expand...
Click to collapse
A full wipe doesn't format system.. U need to go into where u can mount the partitions and format the system partition.. Its worth a shot.. And I'd do a nandroid restore and leave it stock, from my experience my wifey doesn't know how to use any of the extra mods that come with the ROMs anyways, and its just a disaster waiting to happen... But that's just me
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 12:44 AM ---------- Previous post was at 12:40 AM ----------
What kernel u running?
Sent from my Galaxy Nexus using Tapatalk 2
Well wouldn't restoring stock with Odin wipe literally everything? Including partition?
And the current ROM and kernel is stock cm10.1
So whatever the latest nightly is.
Sent from my Nexus 4 using Tapatalk HD
Not sure if it does.. I don't use Odin.. If u do a nandroid restore and see if its still doing random reboots ull know if its a hw problem or ROM/kernel
Sent from my Galaxy Nexus using Tapatalk 2
LiquidXed said:
Not sure if it does.. I don't use Odin.. If u do a nandroid restore and see if its still doing random reboots ull know if its a hw problem or ROM/kernel
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'll give that a try if she gets more reboots.
Sent from my A510 using Tapatalk HD
Someone please help me. I tried to flash the unroot back to stock through twrp as ma5 wasn't working all that well for me and i wanted to start from scratch unrooted and get the sprint ova for the ma7.
So i flashed the file and it said that it was successful. It even went to the special recovery like it was supposed to before rebooting. Now we get to the problem. The phone wont reboot. It just stays on the first black galaxy note 2 screen. Is there anything i can do to fix this? Someone please help me.
U coukd try and flash another rom or use odin to flash a stock rom.
Sent from my SCH-I535 using xda premium
musclehead84 said:
U coukd try and flash another rom or use odin to flash a stock rom.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I tried both of those already. It acts like everything flashes ok but then when it reboots, it stays on the black note 2 screen
You can try flashing twrp through odin and make sure auto reboot is not checked
Then reboot into recovery and flash a rom.
Unless you can reboot into recivery, cause if you can then this is pointless.
Sent from my SPH-L900 using XDA Premium HD app
I had to order a new phone through Sprint. Luckily it was so screed up they couldn't tell whether it was rooted or not. Which is double good because I also had a broken secure element
Sent from my PC36100 using xda app-developers app
So here's what happened - I installed digitalblur but forgot to install the 4.3 bootloader prior to flashing digitalblur. ROM flashed fine and went thru setup of rom and then as I always do after setup I like to reboot the phone. But it wouldn't reboot, all it would do is continue to boot loop at the Samsung Galaxy Note 2 screen. Now I can't get into recovery. Anyone have any ideas of what I can do to fix this issue?
Sent from my Nexus 7 using Tapatalk
If you can get into download mode, you should be able to Odin back to stock.
Sent from my SPH-L900 using xda app-developers app
shuka325 said:
If you can get into download mode, you should be able to Odin back to stock.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Thats exactly what I ended up doing thanks for the help.
So I tried many times installing Wicked in my S4 and Everything going good with the installation now going in to the First boot which is that longest one like I was told But I Waited More The 20 Minutes On the Phone and It just seemed to gotten stuck on the Samsung s4 screen cause it was like throughout the whole time any suggestions ??? I'm Using the latest TWRP recovery and I Was On The NB4 Modem if that help
I'd boot into recovery and do a wipe.
Sent from my SGH-M919 using XDA Premium 4 mobile app
I did and it was the same results
Sent from my SGH-M919 using Tapatalk
I read that you have to wipe the internal sd card ?
Sent from my SGH-M919 using Tapatalk
Wipe cache and Wipedata/factory reset
I Give It Another try then
Sent from my SGH-M919 using Tapatalk
Slayer809 said:
Wipe cache and Wipedata/factory reset
Click to expand...
Click to collapse
I guess I'm Giving up Now Cause I Have Tried everything , I've Done Factory Rest/Wipe and Even Advance wipe And It Still Boot In The Samsung S4 Screen And I Even Downloaded it Again Thinking it Was A Bad down But I got the same results :/ And After That I switched recovery think that would work Cause I Read Around Forums people Mentioning that The Latest TWRP Has Problems Flashing Roms Sooo I the Flashed CWM 6.0.4.4 Which Was the Latest one And Still that didn't Work :/ im I Missing A Step Or Something ?
Sent from my SGH-M919 using Tapatalk
Could try flashing an earlier version like wicked 9. And then try flashing vI0.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
Could try flashing an earlier version like wicked 9. And then try flashing vI0.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Okay Thanks For the help I'll give it a try
Sent from my SGH-M919 using Tapatalk
Still Did Not work :/ waited 15 minutes on the Splash screen but still nothing and i made sure i selected something during the installation like they mentioned .. There Might Something wrong with my phone Can It possibly be the stock kernel ?