Related
Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"
Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.
My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.
Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App
Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.
Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.
Sorry for the long read, this is half rant and half question.
Alright, I got a captivate a long time ago (about a year and 3 months ago), loved it, rooted it and installed cyanogenmod as soon as I got home, changed roms and kernals constantly, did whatever I wanted to do.
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
-Pirate said:
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
Click to expand...
Click to collapse
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
-Pirate said:
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Click to expand...
Click to collapse
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
-Pirate said:
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
Click to expand...
Click to collapse
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
U def don't need a jig. If it's booting it's not bricked. Try removing battery, start Odin, hold down power and down, plug in and put battery in. This should bring u to download mode.
prbassplayer said:
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
Click to expand...
Click to collapse
I did start to see a few people with the problem, however many people do not follow up with what fixes their problem, and I did what a few people had said to do.
prbassplayer said:
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
Click to expand...
Click to collapse
I should of mentioned that I did flash a few times, 3 total I think, it was getting stuck at boot.
prbassplayer said:
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
Click to expand...
Click to collapse
I understand that **** happens but honestly my old captivate could always get into recover mode and download mode no matter what, it's extremely frustrating that something changed with the newer models. One of my questions was what caused the brick? I did nothing wrong from what I see and it was running perfectly until I tried to restart/boot into recovery.
Oh and mbc663, thanks but download mode doesn't work at all, nor does recovery obviously.
I can't say exactly what you are doing. Best advice I can do Re download your .zips Flash back to stock GB and try again.
-Pirate said:
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
Click to expand...
Click to collapse
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Sounds like you got one of the refurbs that is missing the SBL. Have you looked at this thread? http://forum.xda-developers.com/showthread.php?t=1129821
I've not had this problem myself but it sounds like that might help. If I remember reading correctly, once this is flashed it should stick as long as you don't flash any other bootloaders on top of it.
Its not missing the sbl. The sbl it has doesn't respond to key combos. Derpa sherpa moment for samsung I guess?
Rofl yeah...if it was missing the sbl it would be fuggin bricked!
studacris said:
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Click to expand...
Click to collapse
I know, thanks. I'm such a creature of habit, I started doing it like this a bit over a year ago, and has worked flawlessly for me(just jinxed myself!) so I never saw a reason to "fix what aint broke".
I'll take a look at Cezar's thanks!
Yeah, missing SBL was a poor choice of words. My bad.
kangi26 said:
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Click to expand...
Click to collapse
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
kangi26 said:
3buttonFix to my SD, then reboot into recovery
Click to expand...
Click to collapse
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
-Pirate said:
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
Click to expand...
Click to collapse
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
kangi26 said:
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
Click to expand...
Click to collapse
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
-Pirate said:
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
Click to expand...
Click to collapse
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
kangi26 said:
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
Click to expand...
Click to collapse
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: deleted
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
-Pirate said:
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: imgurDOTcom/26sXGl.jpg
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
Click to expand...
Click to collapse
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
kangi26 said:
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
Click to expand...
Click to collapse
Maybe because it's a refurb? and whoops didn't think about that.
-Pirate said:
Maybe because it's a refurb? and whoops didn't think about that.
Click to expand...
Click to collapse
I'm not sure why, mine is a referb, and I have a sticker with mine on it. Ooh well, it is what it is
Sent from a autonomous device
Hi. I have been trying to find an solution to my problem for 3 days. I have looked all over here and the rest of the internet. I believe what I need is an update zip file that will pass the standard e3 recovery.
I have downloaded several zips already(a couple from here), that say they are the stock samsung firmwares, but everytime I put it on an sd, then try to apply the update with it, in the e3 recovey I get E: signature verification failed.
I got to this point by trying to apply the OTA update. ( ok, you can all throw rotten food at me now). I thought I was safe as I didn't have any custom firmware on there. I had, however gained root access. The update went fine and seemed to work, then it finished and tried to reboot, only to get stuck on the samsung logo for over an hour before I decided it had gone wrong and panicked.
The usual ways of fixing I know about are odin, heimdall, adb. None of these are working. I think it's my computer being too old. Odin doesn't detect, Heimdall sees there is a device there but has problems connecting to it. adb will only see it in the e3 recovery mode and not in odin mode and even then because it doesn't seem to be root anymore it can't really do much.
I am open to suggestions on how to get something to work. My thoughts are that I just need a gingerbread rom that has some samsung siigning on that I can put on an sd and use that in E3 to flash from there. I can then work from there if that works. Feel free to laugh and point and tell me that's not gonna work, but if you know a way that will work I would be very grateful.
Thank you for listening and I hope someone can help.
Open kies, do the connection troubleshooting to reinstall device drivers.
Then follow path of flashing stock with PC Odin with pit file. See dr Ketans thread in sticky section of development for path.
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Open kies, do the connection troubleshooting to reinstall device drivers.
Then follow path of flashing stock with PC Odin with pit file. See dr Ketans thread in sticky section of development for path.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
thanks for getting back so soon. I have had kies up on the screen actually. It's been trying to connect for about 3 hours now lol.
I did the troubleshoot thing earlier where it reinstalled drivers. Restarted pc but same. Won't actually connect in either odin mode or recovery.I'm pretty sure it's a pc issue, at least partly anyway, but don't have anything else to try it on.
Is the signed zip idea a definite no go?
Not sure about zip,
Close Kies, open pc odin,
Gp into download mode, connect phone, confirm downloadmode with volume up and try tp flash
Let me know how that goes
Sent from my GT-N7000 using Tapatalk 2
No Odin pc refuses to recognise there is anything attached. I'mgiving up for the night now anyway. thank you for looking in. I'll try again in the morning. I might have to buy a new pc before I can get this thing to work.
Connect the usb to back port, sometimes helps with connection. Use stock usb cable.
please hit thanks if i helped
thanks but I've tried all the basics, but if it would help I'd stick a wire up my nose, so it's all helpful. It could be something simple I just forgot.
PC specs? Is it a Mac maybe? Reboot phone and PC and use another cable. Download latest kies and update it restart PC and then connect the phone.
Sent from my GT-N7000 using Tapatalk 2
Umm, did you wipe after the flash?
1. A data wipe will, in all probability, solve the bootloop after the upgrade from GB to ICS.
2. A data wipe on an ICS kernel CAN result in a hardbrick, as I'm sure you must have noticed, on the forums.
I'd say wipe it. The bricks are not all that common. Just this once. I faced a similar situation, and I KNEW the thing would boot after a wipe, so I just crossed my fingers and did it. All went well.
By they way, what do you mean by e3 recovery? I've been assuming stock.
Sent from my GT-N7000 using xda premium
the PC is a 7-8 year old laptop. Our desktop died a few months ago and we've not really had the spare cash to replace it yet. The desktop was even older and was a real pain. The technical gremlins have really infested my house.
I don't really want to wipe the data, as I could just send off to samsung repair as a last resort. I really want my pictures and data back. Got some of my 2 and half month old daughter on there that I haven't got backed up anywhere else. (yes I'm looking dumber with every post). My next thing to try I guess is see if I can borrow my sister in laws PC for a few hours or something. That is if if cannot find a rom that the recovery will accept to put on my sd.
yes -the e3 recovery s the stock one.
Feel for ya.... if you can enter stock recovery then the connection problem most likely lies either with the cable and port or drivers being out of date
Sent from my GT-N7000 using xda premium
almost positive it's my knackered computer that won't let me do anything. Still can't believe that a rom doesn't exist with samsung signing, somewhere in the world. What is the point of having a standard recovery at all if you can't use it to recover stuff?
I need to be borrow or steal the use of someones computer now I think. I'll keep an eye on this thread incase someone knows of a signed zip file, and I will report of any news incase someone else has the same problems and wants to fix it without sending to Samsung so they can keep their data.
kyllerbuzcut said:
I don't really want to wipe the data, as I could just send off to samsung repair as a last resort. I really want my pictures and data back. Got some of my 2 and half month old daughter on there that I haven't got backed up anywhere else.
Click to expand...
Click to collapse
I understand the reluctance.
Although, the pictures would survive the wipe, as they would be in /sdcard/DCIM/Camera. A wipe wouldn't affect anything in /sdcard, although, you'd lose your contacts if they aren't backed up. Your best bet would be to borrow someone's computer for a while.
thanks for all the advice.
Finally found a zip that the e3 recovery thinks is signed.
It was the 2.3.6 gingerbread, uk cpw one.
It seems to pass the signing check and then it looks like it's doing domething for a few minutes, then nothing seems to happen afterwards. just stays in recovery. If I do it a few times in a row it will sometimes think for longer, then reboot itself like it has all worked, but then get stuck at the samsung logo again.
Can I ask, what exactly is getting wiped then? Just the main android folders and not the sdcard folder? Is that for definite?
Yes. Just the android partition should get wiped, internal SD should remain intact.
Try taking out the battery for five minutes or so before powering on again. Sometimes after flashing the rom needs a breather to "settle".
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
Just an update on my situation. I finally managed to get use of another computer and got it to work properly, so managed to flash the stock ICS rom through odin.
Thanks a lot Samsung for forcing me to put the yellow triangle on my device. At least there are people willing to help with fixing mobile phones' software, even if the manufacturers themselves don't care about you losing all your data. I managed to get everything back. Nothing was lost. If only they allowed you to flash the stock rom from their stock recovery. It's ridiculous that it doesn't.
Anyway there is the triangle away app for that I suppose and now I might try some new roms out to see which I prefer.
Yeah you would have to make a flashable zip. Not sure how to do that.
Good you are back
Sent from my GT-N7000 using Tapatalk 2
Hey All,
Finally got my nexus 6 and I'm pumped to have a developer phone again. Haven't done anything since I got rid of my galaxy nexus a year or so ago, so I'm a bit rusty. Sorry if this has been posted before, I searched but couldn't find anything related to this. Long story short, I had my phone unlocked and rooted and have TWRP installed fine. I just went in and cleared the cache, dalvik cache, and fixed permissions... and now I'm stuck in a bootloop. After researching I'm pretty sure it was the fixed permissions that messed it up, I didn't know that it didn't work on lollipop at the time. I've come to the conclusion I need to reflash the stock images and start from scratch. The only problem is I'm currently stuck at work for another 4 hours and can't use adb at all on this computer. So I'm wondering if anyone knew of another way to fix from just the phone. Thanks in advanced guys!
rev89 said:
Hey All,
Finally got my nexus 6 and I'm pumped to have a developer phone again. Haven't done anything since I got rid of my galaxy nexus a year or so ago, so I'm a bit rusty. Sorry if this has been posted before, I searched but couldn't find anything related to this. Long story short, I had my phone unlocked and rooted and have TWRP installed fine. I just went in and cleared the cache, dalvik cache, and fixed permissions... and now I'm stuck in a bootloop. After researching I'm pretty sure it was the fixed permissions that messed it up, I didn't know that it didn't work on lollipop at the time. I've come to the conclusion I need to reflash the stock images and start from scratch. The only problem is I'm currently stuck at work for another 4 hours and can't use adb at all on this computer. So I'm wondering if anyone knew of another way to fix from just the phone. Thanks in advanced guys!
Click to expand...
Click to collapse
you can try flashing any rom, since you have twrp installed, or you can try wiping data(factory reset).
simms22 said:
you can try flashing any rom, since you have twrp installed, or you can try wiping data(factory reset).
Click to expand...
Click to collapse
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
rev89 said:
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
Click to expand...
Click to collapse
you can try, i dont think itll help. all you got to do is download any rom/gapps/supersu to your phone then flash it. i use rastapop.
simms22 said:
you can try, i dont think itll help. all you got to do is download any rom/gapps/supersu to your phone then flash it. i use rastapop.
Click to expand...
Click to collapse
I know, but I can't boot my phone to download it. Hence, why I'm going to have to flash the stock images when I get home. How is rastapop? I need to find something since the big names aren't out yet. I'll try it out later once everything is fixed. I'm mad I ran into this boot loop because custom rom was next on my list of things to do haha
rev89 said:
I know, but I can't boot my phone to download it. Hence, why I'm going to have to flash the stock images when I get home. How is rastapop? I need to find something since the big names aren't out yet. I'll try it out later once everything is fixed. I'm mad I ran into this boot loop because custom rom was next on my list of things to do haha
Click to expand...
Click to collapse
you didnt happen to make a backup in recovery, did you? if you did, just restore it.
simms22 said:
you didnt happen to make a backup in recovery, did you? if you did, just restore it.
Click to expand...
Click to collapse
Nope, would have made life a lot easier if I did. I was just kicking myself in the ass for that earlier.
Edit: nvm, forgot you don't have adb access
Sent from my Nexus 6 using XDA Free mobile app
Thanks for the help guys. I'm just gonna start from scratch when I get home... god I hate not having a phone.
Yah I realized fixing permissions messes it up. And also if u wipe internal storage the phone looses the system ui and the back home menu buttons as well
well thats good to know. Will it still do that if I'm not encrypted?
rev89 said:
Unfortunately, I do not have any ROMs saved on my phone yet. I just got it last night with only maybe an hour or two of playing time. I also tried factory reset through TWRP and am still experiencing the bootloop. Would formatting data help? I feel like it would, but like I said, I'm rusty.
Click to expand...
Click to collapse
Probably too late to do, but USB-OTG cable and a jump drive. I have downloaded stuff on work PC, copied to jump drive and flashed it on phone with TWRP from the jump drive.
I can personally confirm the permission fix in TWRP recovery breaks the stock L5.0.0 and 5.0.1 and I assume probably most ROMs? There seems to be several threads about this.
githyanki said:
Probably too late to do, but USB-OTG cable and a jump drive. I have downloaded stuff on work PC, copied to jump drive and flashed it on phone with TWRP from the jump drive.
Click to expand...
Click to collapse
you can flash from a jump drive? I didn't know that
Hey guys!*
First time posting on this site but I'm hoping you guys can help!
I have a Note 3 N900AUCUEOC2 5.0 Lollipop version.
My ultimate goal is to root my Note 3. Since in the past I have rooted my old phones and love it. But with the Note 3, specially the N900a 5.0 lollipop version, it seems hardest to get accurate root instructions for.*
After days of searching over many forums, I came to the conclusion that I need to flash my version (using Odin) Lollipop 5.0 OC2 back to Kitkat 4.4 NC2 and then from there I can use Towel Root to root my device and then upgrade to 5.0 again. So I thought..?
First of all, I backed up all my contacts and apps and everything using Easy Back Up. To my ext SD card an then I removed my ext SD card for safe keeping. Then I downloaded the required (working) Odin N900AUCUCNC2 files. Which was 4 separate files. I then put my phone into Odin Mode and connected to PC and ran Odin with the files selected. Everything went smooth, passed and my phone rebooted.. of course I was expecting a full factory reset with the new version. But when I check the version it says I'm still on 5.0??? And I even tried to fire up Towel Root and it won't even let me go to the site anymore and gives me a 404 error messege. All other sites seem to work tho.
Also to confuse things more, I turned off my phone and put my SD card back in to retrieve my back up and everything else on it. But... there's nothing there! It's complete wiped clean! Which doesn't make sense since I didn't have it inside my phone during the flashing progress.*
So now I basically flashed my phone for nothing and lost all my data in the process.*
I thought I was more computer savy than this but I guess this one stumped me and I could really use your guys help.*
Where did I go wrong and how can I fix it?
Monstrous22 said:
Hey guys!*
First time posting on this site but I'm hoping you guys can help!
I have a Note 3 N900AUCUEOC2 5.0 Lollipop version.
My ultimate goal is to root my Note 3. Since in the past I have rooted my old phones and love it. But with the Note 3, specially the N900a 5.0 lollipop version, it seems hardest to get accurate root instructions for.*
After days of searching over many forums, I came to the conclusion that I need to flash my version (using Odin) Lollipop 5.0 OC2 back to Kitkat 4.4 NC2 and then from there I can use Towel Root to root my device and then upgrade to 5.0 again. So I thought..?
First of all, I backed up all my contacts and apps and everything using Easy Back Up. To my ext SD card an then I removed my ext SD card for safe keeping. Then I downloaded the required (working) Odin N900AUCUCNC2 files. Which was 4 separate files. I then put my phone into Odin Mode and connected to PC and ran Odin with the files selected. Everything went smooth, passed and my phone rebooted.. of course I was expecting a full factory reset with the new version. But when I check the version it says I'm still on 5.0??? And I even tried to fire up Towel Root and it won't even let me go to the site anymore and gives me a 404 error messege. All other sites seem to work tho.
Also to confuse things more, I turned off my phone and put my SD card back in to retrieve my back up and everything else on it. But... there's nothing there! It's complete wiped clean! Which doesn't make sense since I didn't have it inside my phone during the flashing progress.*
So now I basically flashed my phone for nothing and lost all my data in the process.*
I thought I was more computer savy than this but I guess this one stumped me and I could really use your guys help.*
Where did I go wrong and how can I fix it?
Click to expand...
Click to collapse
sounds like you did everything typically right, but i dont have this device to verify the steps. best to post your question in the note 3 q&a forums for quicker and possibly more accurate answers.
just my opinion, but im betting your sd wasnt wiped, just something wrong with your phone and cant read it, i could be wrong. you could use an adapter and put it in your pc to verify if its clean or not.
bweN diorD said:
sounds like you did everything typically right, but i dont have this device to verify the steps. best to post your question in the note 3 q&a forums for quicker and possibly more accurate answers.
just my opinion, but im betting your sd wasnt wiped, just something wrong with your phone and cant read it, i could be wrong. you could use an adapter and put it in your pc to verify if its clean or not.
Click to expand...
Click to collapse
Ohh okay. Yeah I wasn't sure where exactly to post, so I'll post it in Q/A.
And I didn't think to check my sd card on my computer. I'll try that.
Monstrous22 said:
Ohh okay. Yeah I wasn't sure where exactly to post, so I'll post it in Q/A.
And I didn't think to check my sd card on my computer. I'll try that.
Click to expand...
Click to collapse
its ok to post here, but if your device has its own forums, you will generally get more detailed help there faster