Related
okay i really need some help.
ive tried all the steps to recover my phone.
i get to the g1 screen when i power it up.
i can still get in to recovery menu.
ive tried to do a wipe.
please i need help.
ive also tried reinstalling rc29 with the original spl
but my radio is still 2_22_19_26I
PLEASE I NEED HELP!
or if there is a way that i can make it look like i never touched it then im still able to return it
so anything would help. links also
if you put the DREAIMG.nbh on your phone via bootloader it will reset the radio and spl to stock and everything else will be stock so that you can return the phone as though you never did anything to it
sweet. i guess i cant fix my phone. good thing i only got it 3 days ago.
whats a good thing to tell them when returning my phone?
G-Fetus6 said:
sweet. i guess i cant fix my phone. good thing i only got it 3 days ago.
whats a good thing to tell them when returning my phone?
Click to expand...
Click to collapse
if your phone is not messed up then there is no reason to return it. if you keep it at stock rc29 then it will update to 1.5 firmware within 72 hours supposedly or if you still want root follow these steps in this thread. this is the probably the most reliable way to root your phone, and since it is not as automated as some of the other threads, you might learn some things about your phone in the process http://forum.xda-developers.com/showthread.php?t=442480
david1171 said:
if your phone is not messed up then there is no reason to return it. if you keep it at stock rc29 then it will update to 1.5 firmware within 72 hours supposedly or if you still want root follow these steps in this thread. this is the probably the most reliable way to root your phone, and since it is not as automated as some of the other threads, you might learn some things about your phone in the process http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
well the thing is im stuck at the G1 boot screen.
and cant get it to do anything after that.
so i might as well save me time and just return it tomorrow
G-Fetus6 said:
well the thing is im stuck at the G1 boot screen.
and cant get it to do anything after that.
so i might as well save me time and just return it tomorrow
Click to expand...
Click to collapse
do you have a modified recovery image on the phone or were you able to get that far. if not just take it by where you got it and tell them you got an ota update then wouldn't boot up past the g1 screen
david1171 said:
do you have a modified recovery image on the phone or were you able to get that far. if not just take it by where you got it and tell them you got an ota update then wouldn't boot up past the g1 screen
Click to expand...
Click to collapse
i got that it back to looking stock. so that is better if they try to do a hard reset for me.
yeah ill just tell them that an ota did it. cuz the phone is only 3 days old so im sure theyll say "oh yeah it must of been cupcake"
thanks
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
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
raynefr said:
ok, so i was trying to root my sprint htc one, and everything was going, ok. i unlocked the bootloader simple enough. then i wanted to back up the data, before i tried putting roms on it. well twrp kept saying i only had about 34 mb of space which made no sense since i had formatted it, and only brought back things like contacts and texts. when i checked my phone it said that i had 24gbs. so i couldnt find an answer to this anywhere so while looking through twrp i saw the wipe function. not having seen anything about it, i said, maybe if i reformat it again, itl clear up. so i hit wipe all. well after it was done it only said i had 1.2 gbs, so still confused i went to load my normal os, well i cant. because wiping everything meant the system data the os is on. i spend hours trying to find a fix, as im only able to go between the bootloader and twrp, and i see a sideload option, and after following the steps, i attempt to sideload. everything is going well. Viper looks like its about to install, until at the last second it says install fail. but now i cant even access the recovery menu. literally stuck in the boot loader option. all my contacts and pictures and stuff are backed up, so i have no problem formatting my phone to scratch if it means fixing this, but can anyone point me in the right direction???? i cant find anything on this, ive been searching through this site, and some people with similar issues solve it by sheer luck, but i have no rom back up(since i was trying to do that when i got into this problem) please please help!!!
**edit** i was able to get into twrp by using the recovery steps, though im just back to square 1. is there a guarenteed reliable sideloader that can work?
Click to expand...
Click to collapse
Do you still have the memory issue? If so, try running a RUU, and see if that fixes your problem.
If not, just use adb sideload to sideload a ROM. Then wipe everything except internal storage and install the ROM normally.
EDIT: Looks like @BD619 ninja'd me XD
BTW sideload very rarely works when you wipe your sdcard.
BD619 said:
Look HERE
Try the latest RUU first if it does not work follow the guide from the beginning it will get you fixed up.
Click to expand...
Click to collapse
hey thanks for the reply. i followed the guide and after some effort, everything seemed good, but when i was trying to load 5.03 sense 6 rom, i got to the htc start up, then it defaulted back to the bootloader..i went with the deodex version of the download, should i try the odex? or a different version all together?
and now it doesnt want to boot into recovery mode either! going to try redoing the steps, but i just cant figure out what the problem is
**edit* i cant fix twrp. the title loads, but thats it. endless loop
ok i got it to seemingly work. restoring content now. sat in fron of my pc for 15 hours...not even sure where imat or if i got any closer to rooting..smh..thank you everyone who helped. if anyone comes across this
to get out of the endless cycle of recover/loading screen.. delete your twrp, or whatevs your using. even if you have the latest, just redownload it. worked for me. i guess there is a huge difference between the odex and the deodex.i had figured deodex was a more refined version, but maybe it had more complicated software. in any case, if you are at a point where you dont have a base os, and you make it this far, go with odex, it worked for me. htc is big on back up, so i was more worried about having to scrap my phone then i was regaining data, especially with most of my stuff backed up to google drive. hopefully you guys are careful.
now...about this backup issue i had in the first place. how can i fix the storage issue? i have a 32 gb phone minus partition leaves me with over 24gb..why is it going based off the separate phonememory slot? why cant i change it?
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
Using this guy's guide for the Nexus 5 I had no issues, bought a N6 today and was giddy to flash on Cataclysm for N6 and figured might as well use same person's guide for next phone up.
http://www.androidrootz.com/2014/12/how-to-root-nexus-6-windowsmaclinuxubun.html
Was able to unlock bootloader, then installed TWRP but now am getting the 'corrupt phone' message, however unlike others like I have read on XDA, am unable to boot up by just letting it sit. Screen turns off and that's that. Before beginning entire process I enabled "enable/allow oem unlocking". I'm assuming that when the phone factory resets after the bootloader unlock I need to go back in and recheck 'allow oem unlock' in dev options, but I didn't as I assume/ed that it wasn't necessary and the guide doesn't tell you to.
Tried relocking the bootloader to maybe get phone to open up, but terminal tells me that I need to have 'allow oem unlock' checked. Nice Catch-22 http://puu.sh/moOUf/d0f8fa9050.png
Tried formatting data from within TWRP and factory resetting/wiping everything but it tells me that it is unable to mount '/data'
Have since tried WugsToolkit and flashing to stock with 'softbricked' option enabled the shamu-mmb29k-fact....tgz image that I downloaded and imported myself into Wugs (was taking 10 minutes to dl 1%). That seemed to work and told me it was a success, however when I then went back to re-enable the bootloader via wugs it fails and reboots with the lock sign still open and boots again onto 'corruption' screen that then flashes off and turns phone off, left it for 30 minutes at one point and didn't boot so don't think I'm lucky enough to be able to sit if through like others who had that issue
Where to go from here? Really hoping I didn't brick this phone less that 3 hours after getting it. I can still boot and see the Google screen and can get onto the bootloader and used to be able to get into recovery (since wugs have been getting the android with red triangle)
Been rooting/rom'ing since day one that I've had androids. Had a Samsung Apollo with CM on it, same for the Nexus S, then the Galaxy Nexus, then the N5 and looks like my chain of no issues ended tonight
Anything you can do for guys would be greatly appreciated. No clue where to go from here....
So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.
DO NOT RELOCK THE BOOTLOADER!!!!! I cannot emphasize how critical it is that you do not relock the bootloader, given the position you are in. If you somehow manage to relock the bootloader and "enable OEM unlock" is toggled off and Android will not boot (even after attempting a factory reset), then you are 100% bricked with no way to fix your phone. Personally, I leave my bootloader unlocked 100% of the time so that I can fix anything that may go wrong with my phone. Additionally, I (as well as many other users on here) will always advise against using Wug's or any other toolkit in order to do stuff to your phone. While they do provide a nice GUI as well as an easy way to install the necessary drivers, using the regular platform-tools command line method isn't all that hard to figure out, and it allows you to know exactly what you have done to your phone. With Wug's and the like, you never really know what commands that they are running and exactly at what point in the process a flash may fail. Right now, I would advise you to read up on using the platform-tools method to flash stock images. After you have all of the necessary drivers, platform-tools, etc. working properly on your computer, I would strongly advise that you download MMB29S (the latest official update) from the Google Developer page and flash it using the platform-tools method, NOT with Wug's. And whatever you do, I repeat, DO NOT LOCK YOUR BOOTLOADER!
---------- Post added at 07:03 AM ---------- Previous post was at 06:51 AM ----------
triguyrn said:
So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.
Click to expand...
Click to collapse
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.
matthew2926 said:
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.
Click to expand...
Click to collapse
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
No problem! It's too bad to hear about your device but at least you got a new one on the way. There is really no harm to at least trying the flash-all script. It will either work and save you time or fail halfway through and force you to flash everything manually.
triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
Flash-all script is still broken, flash the img files individualy in fastboot.
gee2012 said:
Flash-all script is still broken, flash the img files individualy in fastboot.
Click to expand...
Click to collapse
You guys are life savers, thank you so much
Got it to work after I was getting ready to phone it in and bring it to a repair shop and eat whatever the charge might've been