Related
Okay so - recently my I9000m went into a boot loop (during normal use - though I did have voodoo installed) and I can not access recovery mode. I could however access download mode.
I attempted to install stock firmware from samfirmware - no luck.
I attempted to install stock firmware from the forums - no luck.
I attempted to install EZBase - no luck.
I even attempted to use Virniks 'stock everything' tutorial - no luck.
After all these attempt and various other attempts involving 3 button fixes I was still having boot-loops.
So I got desperate - and I installed the Odin One Click for captivate - I know...bad idea but like I said.. I was desperate.
Now my i9000m (bell canada) starts up with the AT&T Logo and then boot loops!
The worst part is I can't even access download mode anymore! I understand that this is probably due to the fact that the buttons are remapped - keeping that in mind I tried as many key combos as I could but still get nothing but the AT&T Logo looping over and over.
So to the point.. does anyone have a surefire way to get to captivate download mode on a I9000M?
I've read about the JIG solution but I'll use that as a last resort as I would have to order the pieces (I'm not much of a solderer).
So are there any non-JIG solutions to get back to download mode/restore my phone?
All input is appreciated and I'd like to thank everyone that has tried to help me these last couple of days!
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I'm thinking of doing the same (bringing it to bell) though I'm not sure they'll honor the warranty with it booting up with the AT&T logo, hah :<
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Viper717 said:
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Click to expand...
Click to collapse
Called samsung last night - they said I have to bring it to bell first.
Worst case scenario I'll pay sammy to fix it =/
Update: Just got off the phone with Bell, described my problem, said that I messed with the software real hard and they said that as long as I didn't remove any warranty stickers I'll still be able to get it fixed by samsung foh freeee.
Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
But in the case he would rather use warranty service of his provider, he will need to:
a) try reboot with adb, and fastest as he can, try to issue "reboot download" command with it
OR
b) make JIG, and reboot to download mode, and reflash stock ROM
Asking Samsung Korea for new phone with IMEI sent to them do not require any of above...
EDIT: I have missed your last reply. Good to know, that Bell will fix it for you. But I do not think that they will be able to fix it. They will more likely give you new phone.
Virnik0 said:
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
Click to expand...
Click to collapse
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Sozage said:
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Click to expand...
Click to collapse
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Virnik0 said:
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Click to expand...
Click to collapse
They said they would send it to Samsung and give me a loaner until mine is back.
Not sure if they'll still honor it when I show up in person...but I'm hoping for the best.
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Sozage said:
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Click to expand...
Click to collapse
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Virnik0 said:
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
Btw, it does not matter how many times you'll reflash, this sd bus failure is pretty common in some first series of GT-9000 and GT-9000M
Sent from my GT-I9000 using XDA Premium App
chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
$5 jig could have saved you $150
But at least you're having your phone repaired...
Kops said:
$5 jig could have saved you $150
But at least you're having your phone repaired...
Click to expand...
Click to collapse
Not repaired! New phone! Maybe even one without a faulty SD card!
Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
Right, it should be enought to use common sense, and think a little before any further action. I have tried almost anything, starting with dualboot to xubuntu linux, or editing apk's, modding and themming apps (not always successful), erasing all data partitions, created new ones, installed (or at least tried) to install gentoo linux with simple routing capability, and so on. And I'm still here.
Truth is, that some first lines of SGS were affected with faulty sd bus. But there is no need for paying warranty service, and no need to be few days without my phone. If common sense is used, then User would not:
1) install captivate firmware
2) flash anything before cwm is working
if both above fails, he'll reboot to the download mode, flashed canadian or any other fw containing Sbl.bin, alias recovery.
After that, he would flash standard stock firmware which is used by his operator. As a last thing, he would wipe sdcard from recovery.
Phone will look, behave and WILL BE same as he'd bought it.
So they will look on it, and will see standard, untouched phone, which is unknowingly rebooting itself.
Voila! They'll have no other chance then give you brand new phone right on the spot.
So for the next time, keep your mouth shut at least, when you deal with operator ;-)
Sent from my GT-I9000 using XDA Premium App
t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
I wish people would read the entire thread before posting more bs like this.
Trying to put the captivate software on my phone via Odin One Click was the 10th or so thing I tried to do to restore my phone. Nothing would work - recovery mode did not work on my phone nor was I able to restore it.
Flashing the captivate software was an attempt to get recovery working (a desperate attempt) and had nothing to do with my comment about tweaking.
diaf.
I know there is nothing you can do but out is bs that you' voided' warranty. they make you pay $150 for THEIR hardware failure.
hello everyone, i just got an unlock streak to use with t-mobile. im the second owner but the other guy said he just received it as a replacement from dell. this are the specs
baseband:GAUSB1A140514-US
build number:2.2
my problem:the phone is unlock so when i put my sim and boot i get the led flash 3 times and then goes on a boot loop. and it will keep doing it unless i take out my sim. i manage to get it to somewhat work by booting w/o sim, then put phone on airplane mode then off. place sim and boot. then i take it off plane mode and quickly turn of data. then wait for it to recognize tmobile towers, then turn on data and it works for a few mins then goes on a boot loop again. has anyone had this issue?
my second problem is i try to flash several GB base roms and it flashes but i get a lot of FC and cant run the rom. I currently have (miui 2.3.2 ENG DS5 ) and it runs fine w/o my sim. as soon as i put my sim its back to the boot loop.
btw i am not a noob to android, but am a noob to the dell streak. any help,tips,comments is appreciated thanks.
JDM-Bb said:
hello everyone, i just got an unlock streak to use with t-mobile. im the second owner but the other guy said he just received it as a replacement from dell. this are the specs
baseband:GAUSB1A140514-US
build number:2.2
my problem:the phone is unlock so when i put my sim and boot i get the led flash 3 times and then goes on a boot loop. and it will keep doing it unless i take out my sim. i manage to get it to somewhat work by booting w/o sim, then put phone on airplane mode then off. place sim and boot. then i take it off plane mode and quickly turn of data. then wait for it to recognize tmobile towers, then turn on data and it works for a few mins then goes on a boot loop again. has anyone had this issue?
my second problem is i try to flash several GB base roms and it flashes but i get a lot of FC and cant run the rom. I currently have (miui 2.3.2 ENG DS5 ) and it runs fine w/o my sim. as soon as i put my sim its back to the boot loop.
btw i am not a noob to android, but am a noob to the dell streak. any help,tips,comments is appreciated thanks.
Click to expand...
Click to collapse
You need to flash gingerbread baseband files which are amss.mbn and dsp1.mbn through fastboot.
If you are not new to Android I'm assuming you have fastboot and adb drivers setup on your computer and/or the androidsdk installed to the C: drive and paths set to make command line flashing easy... if not then now would be the time to get all that done, if not then you will be back every other day asking for help and getting flamed..
on a side note, had you bothered to read QUITE A BIT MORE the answers I just gave you are provided in the stickies, not even much need to search really, so please don't be one of those newbies that starts a new thread or posts each time your Streak hiccups, ALL the info you need has already been gone over more times that I care to remember
Your baseband indicates the Streak at one point was running 405, the beta Gingerbread build. It's no wonder you're having problems given you're attempting to run Froyo with a beta Gingerbread baseband.
Where this Streak is used, it's best to flash a stock ROM first to ensure the Streak works properly. 407 would be perfect for this as it's the stock Gingerbread build but you could also use one of the stock Froyo ROMs as well. After flashing the stock ROM and making sure everything is working, then go to your chosen ROM, using the information in the stickies.
Strephon Alkhalikoi said:
Your baseband indicates the Streak at one point was running 405, the beta Gingerbread build. It's no wonder you're having problems given you're attempting to run Froyo with a beta Gingerbread baseband.
Where this Streak is used, it's best to flash a stock ROM first to ensure the Streak works properly. 407 would be perfect for this as it's the stock Gingerbread build but you could also use one of the stock Froyo ROMs as well. After flashing the stock ROM and making sure everything is working, then go to your chosen ROM, using the information in the stickies.
Click to expand...
Click to collapse
thanks for the reply, so then what you are saying is that the phone was on GB at one point? man, i knew this guy tryed to flash a dif rom before he sold it. He told me he just got it replace by Dell and decided he didn't want it. i fixed my second problem but im still having the issue with the phone rebooting when data is turned on and then freezes at boot screen.
cdzo72 said:
You need to flash gingerbread baseband files which are amss.mbn and dsp1.mbn through fastboot.
If you are not new to Android I'm assuming you have fastboot and adb drivers setup on your computer and/or the androidsdk installed to the C: drive and paths set to make command line flashing easy... if not then now would be the time to get all that done, if not then you will be back every other day asking for help and getting flamed..
on a side note, had you bothered to read QUITE A BIT MORE the answers I just gave you are provided in the stickies, not even much need to search really, so please don't be one of those newbies that starts a new thread or posts each time your Streak hiccups, ALL the info you need has already been gone over more times that I care to remember
Click to expand...
Click to collapse
thanks for the reply
correct i do have drivers and adb in my PC and this is not my first time using adb commands. and yes i did bother reading many threads and using the search tool and found lots of great info but nothing pin pointing to the same problem im having with the phone not liking it when i turn my data on.
Btw i figure out why non of the GB roms were working, when i was doing the factory reset i was only doing it through streakmod recovery. but when i FR on the previous menu it worked.
i also made the diagnostic test through fastboot menu to test the sim and every thing else and everything is fine
Sorry for the late reply. I believe your data issues will resolve themselves by installing 407. From there you can install one of the custom ROMs.
hmm ok ill try that
Evening all,
I have a DHD that is stuck in HBOOT/FASTBOOT, or at least that and the stock recovery program is all I can get to.
I tried an AAHK, and it basically tried to do a downgrade and has left the phone with no data, still at s-on, and I can't find an operator RUU(three uk) to flash it back to a useable state.
Is there a three RUU available?
I'm running around in circles as I can't make a gold card, due to not having another DHD available to retrieve the MMC2. All I need is a goldcard and then I can flash a WWE, but I cant find anywhere to make one without the phone or a similar one.
I dont think it turned the microsd properly into a gc, before it tried to downgrade. Is their anyway I can test to see if the memory card has been successfully goldcarded?
Any help would be greatly appreciated.
Thanks
James
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Teichopsia said:
This might help
http://forum.xda-developers.com/showthread.php?p=29203392
Sent from a dream.
Click to expand...
Click to collapse
Mine has a lot of those symptoms to be honest. If I vol down/power to get to Hboot, it sits there with no keys being able to be pressed, just highlighted blue FASTBOOT and not even checking for files on memory card
If I just turn it on, it sits at the three splash screen, which i assume is the equivalent of the HTC one for branded phones.
I have now turned it on and left it on as per those linked threads, in the hopes the sd is a proper gold card and it is just slow. Fingers crossed.
Thanks for the pointer
James
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Teichopsia said:
There are many threads for your problem, do a search, check what it might be. I believe in the second page of that link has another link, check it out. Find out what is wrong before trying anything. If you have any questions, let us know what are the symptoms, what you have done and so on.
Sent from a dream.
Click to expand...
Click to collapse
Well what I did, was follow the AAHK instructions, cleaned up my environment etc, went through the install. When it asked to do the downgrade, I said yes, then it asked about wiping and was I sure, so I said yes. It then rebooted the phone and it is now as it is. I pulled the battery and tried vol-down/power, which brings up HBOOT, but it doesnt let me do anything, vol keys and power do not work and it doesnt start looking for image files.
From that thread, it was mentioned it just could be going very slow, and people have just left it overnight. This is what I have done now, and will see if it has accessed the files on the memory card and downgraded properly in the morning.
Thanks
James
Have you tried looking for the RUU here?
Last I remember when aahk downgrades, you will be asked to reboot to basic recovery twice
Panic over, thankfully! Not my phone, you see!
It was so easy to root my S2 and the X10 before that, and the iP3G before that(and custom winmo, and nokia etc etc), I said give it to me, i'll sort you out with some ICS rom action.
Then it all went wrong as explained in my previous posts.
2 days later, i finally found the H3G RUU I needed to get an system on it. Silly branded phones. Took 4 hours to download as it was on a throttled download service(my 100MB leased line usually eats 300MB in seconds, but not this time)
So long story short, into FASTBOOT USB, ran the RUU and it completed and put froyo on the phone, and as a happy coincidence it was at a level that didn't need a downgrade, so AAHK ran through like a trooper, busybox installed and hey presto, ENG S-OFF. IceColdSandwich installed through cwm and one happy mate, who then proceeded to ring his wife and tell her to rent a film, as he would be tinkering with the phone all night lol
It was getting to the point I was going to have to give him my S2, and as I've just taken possession of a Sony SmartWatch, I didn't want to do that!!
Thank for everyone's help and pointers, not sure what went wrong the first time(probably a memory card/incompatibility/goldcard problem), but all sorted now.
James
Hello,
I am not a phone expert by any means. I am probably in the 'knows just enough to be dangerous category,' but I am quite willing to learn. Here is my situation as I understand it. Please advise whether my premise is flawed.
Phone: rooted Verizon Note 3 KitKat NC4 off contract / pre-paid , no warranty
Ultimate Goal: to wipe my phone and have a clean slate. Bonus if I could be able to backup images of my phone for the future. Heheeeee.
Sitrep: phone is in need of a wipe/do-over to resolve some minor annoyances, but factory reset doesn't work. It says "System software not authorized by Verizon detected...please shove it," or something. That is curious, because, since I am trying to get rid of allllllllll the software, it should just let me do it if it doesn't like some of the software. I probably don't understand this fully. (Or else they just want me to go to Verizon so they can sell me a new/worse/more despotic phone.)
I only get that message if i try to reset it, not every time i turn it on, so it doesnt bother me, but i do want to reset it, because it is full of cobwebs and battery issues. From reading this forum, I think the reason it won't reset is that about a year ago, I installed clockwork and did *something* to the recovery, but it freaked out, because my boot loader wasn't (and still isn't) unlocked, so I uninstalled clockwork. I don't remember why I installed it. It was too long ago. I think i thought i could back up my rom or something. Anyway, it has worked fine ever since, I just can't wipe it and it tells me about unauthorized software. I found instructions on here about 'flashing back to stock kitkat with Odin,' which I gather will fix my recovery, and as long as I don't do that clockwork recovery thing again, I can reset it whenever I want to, on KitKat. (I am not interested in "upgrading.") I was all set to do that, when, last night, to my joy, I saw the Verizon note 3 boot loader unlock has arrived. That (I think) means that I can (eventually) unlock the boot loader and go back to jelly bean. Yay! Or cyanogen!! Yayay!
Question: shall I first reflash KitKat in Odin, so that the recovery is operational, THEN unlock it? Or can I unlock it first, even if the recovery is messed up, skip fixing KitKat, and go back to jelly bean (or maybe cyanogen)? I am afraid that there is a right order and a wrong order, and I'm sure to pick the wrong one.
Maybe these 2 things have nothing to do with each other. I have no idea. I just feel like I might be at a crossroad.
Thank you very much for helping a lady in somewhat unfamiliar territory.
Auralay
Auralay said:
Hello,
I am not a phone expert by any means. I am probably in the 'knows just enough to be dangerous category,' but I am quite willing to learn. Here is my situation as I understand it. Please advise whether my premise is flawed.
Phone: rooted Verizon Note 3 KitKat NC4 off contract / pre-paid , no warranty
Ultimate Goal: to wipe my phone and have a clean slate. Bonus if I could be able to backup images of my phone for the future. Heheeeee.
Sitrep: phone is in need of a wipe/do-over to resolve some minor annoyances, but factory reset doesn't work. It says "System software not authorized by Verizon detected...please shove it," or something. That is curious, because, since I am trying to get rid of allllllllll the software, it should just let me do it if it doesn't like some of the software. I probably don't understand this fully. (Or else they just want me to go to Verizon so they can sell me a new/worse/more despotic phone.)
I only get that message if i try to reset it, not every time i turn it on, so it doesnt bother me, but i do want to reset it, because it is full of cobwebs and battery issues. From reading this forum, I think the reason it won't reset is that about a year ago, I installed clockwork and did *something* to the recovery, but it freaked out, because my boot loader wasn't (and still isn't) unlocked, so I uninstalled clockwork. I don't remember why I installed it. It was too long ago. I think i thought i could back up my rom or something. Anyway, it has worked fine ever since, I just can't wipe it and it tells me about unauthorized software. I found instructions on here about 'flashing back to stock kitkat with Odin,' which I gather will fix my recovery, and as long as I don't do that clockwork recovery thing again, I can reset it whenever I want to, on KitKat. (I am not interested in "upgrading.") I was all set to do that, when, last night, to my joy, I saw the Verizon note 3 boot loader unlock has arrived. That (I think) means that I can (eventually) unlock the boot loader and go back to jelly bean. Yay! Or cyanogen!! Yayay!
Question: shall I first reflash KitKat in Odin, so that the recovery is operational, THEN unlock it? Or can I unlock it first, even if the recovery is messed up, skip fixing KitKat, and go back to jelly bean (or maybe cyanogen)? I am afraid that there is a right order and a wrong order, and I'm sure to pick the wrong one.
Maybe these 2 things have nothing to do with each other. I have no idea. I just feel like I might be at a crossroad.
Thank you very much for helping a lady in somewhat unfamiliar territory.
Auralay
Click to expand...
Click to collapse
It is because you are rooted... A factory reset just wipes user data and applications... It does not totally reload Android.
You can reflash the phone via Odin and a firmware download of the proper version (or higher) for the Verizon Note 3. Firmware is available on www.sammobile.com you have to be a member in order to download but membership is free.
If you want to stick with KitKat... You can unlock the bootloader now and then can load either CWM or TWRP and from them can flash any ROM available here.
Even unlocked i don't think you can move back to Jelly bean
Sent from my SM-N900V using Tapatalk
donc113 said:
It is because you are rooted... A factory reset just wipes user data and applications... It does not totally reload Android.
You can reflash the phone via Odin and a firmware download of the proper version (or higher) for the Verizon Note 3. Firmware is available on ] you have to be a member in order to download but membership is free.
If you want to stick with KitKat... You can unlock the bootloader now and then can load either CWM or TWRP and from them can flash any ROM available here.
Even unlocked i don't think you can move back to Jelly bean
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Thank you so much for taking the time to consider my question. As sad as I am to think about not ever going back to Jelly Bean, which I assume is a tyrannical Verizon/Samsung thing, I am very glad for your input. I could have sworn I have reset this phone since rooting it, but I could just as easily be mistaken. I think I will do Odin first, and see everything is A-OK before leaping out into the unknown of unlocking. Hopefully after I do Odin, I can do resets the old easy way, but it's ok if i can't. Anyway, thanks a bunch for helping me get smarter every day. <3
Auralay
Auralay
Have you already flashed with Odin?
Hold your horses if not, I have an idea which is worth trying.
(It involves unlocking and reinstalling stock without losing root in the process.)
I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
I do not remember exactly, but think that USB debugging is off.
It's a phone with bootloop issue, so cannot get into recovery menu also.
Apologize is if it was already discussed.
jorgen.bumajnikov said:
I'm trying to unlock phone’s bootloader using
Code:
fastboot flashing unlock
, but getting error message:
Code:
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.021s
Checked fastboot devices command and it found my device connected.
I do not remember exactly, but think that USB debugging is off.
It's a phone with bootloop issue, so cannot get into recovery menu also.
Apologize is if it was already discussed.
Click to expand...
Click to collapse
Try this https://www.xda-developers.com/nexus-6p-bootloop-fix/
Sent from my Nexus 6P using Tapatalk
Minh Dao said:
Try this https://www.xda-developers.com/nexus-6p-bootloop-fix/
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Thanks, I saw this post and was trying to follow steps described there, but 9 steps is about unlocking bootloader and I cannot pass it...
Both OEM unlocking and USB debugging need to be enabled in Settings/Developer options before the bootloader can be unlocked.
redduc900 said:
Both OEM unlocking and USB debugging need to be enabled in Settings/Developer options before the bootloader can be unlocked.
Click to expand...
Click to collapse
in post I mention that it's phone with bootloop issue
And I told you why you can't unlock the bootloader.
redduc900 said:
And I told you why you can't unlock the bootloader.
Click to expand...
Click to collapse
so that's it - no way to make it work again at all? (
I tried this but I couldn't make it work.
rootmygalaxy.net/unlock-bootloader-on-huawei-devices/
which leads to
emui.huawei.com/en/plugin/unlock/detail
but no matter how hard I try, I keep getting:
"Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID."
Try enabling OEM unlocking in developer options
Unfortunately can't when it's stuck bootlooping.
bcurran3 said:
Unfortunately can't when it's stuck bootlooping.
Click to expand...
Click to collapse
Follow the thread below, same one as before. You need to stick with this until it works.
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Follow the thread below, same one as before. You need to stick with this until it works.
https://forum.xda-developers.com/showthread.php?t=3640279
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thanks. Yeah, I tried the freezer trick. In fact I put it in there and forgot about it for a week! HA! Didn't work. I'll need to try the hairdryer trick.
I'm REALLY hoping Google responds to the boot.img signature files request....that would make life so much simpler. I'm probably going to shelve this project for the 4th or 5th time and wait a few weeks. (I've been dealing with this since Feb or March.)
I did put in another call to Huawei today. The next available representative was nice but told me that Huawei global unlocks the bootloader for people in China but not the US. I had him open a case to get the bootloader unlock code and pass it up the chain. I doubt it will result in anything...but at least the request is officially in.
OP did you fix the boot looping issue? I am in the exact same spot - my phone is stuck in boot loop and my OEM is locked too
draxz said:
OP did you fix the boot looping issue? I am in the exact same spot - my phone is stuck in boot loop and my OEM is locked too
Click to expand...
Click to collapse
I just fixed my phone and thought I would post my method:
For the people with boot loader locked (You CANNOT do anything with it being locked) I just revived my phone:
You need to heat the phone by using a blow drier for about 5-10 mins while in boot loop - in my case I don't have a blow drier so I turned the stove to medium heat and kept the phone about 10 centimeters above the heat. After 10 mins the phone miraculously booted up and went to "Setup as new phone" (I had wiped the device earlier) after setting it up, I immediately went into the setting to unlock OEM and after 15 mins the phone went into the boot loop again. I followed the instructions on this page https://www.xda-developers.com/nexus-6p-bootloop-fix/, a huge thank you to XCnathan32 and voila the phone works. Thank you XCnathan32 and other, please thank him by clicking the thank you button on his page or by making a donation as a gift.
I wish I was having luck.
Over the past two weeks we've had multiple 100+ degree days in Los Angeles. I threw my 6p on the charger in my OUTSIDE office. The phone got hot as hell. I tried for days to get it to boot up with no joy. I did get the NO COMMAND screen a couple times. One time I actually got to it fast enough to interact and hit the right keys to go and wipe it again. (I wiped it months ago too.) One time I accidently hit install update from SD card (always makes me laugh as there is no SD card) and I think it said it was installing the update from the SD card (again I laughed) but my guess is that's just the default graphic to display from the menu choice even if it doesn't do anything.
Anyways, for 3-4 days in 103-111 degree heat I tried for multiple multiple hours. The phone would never boot to the setup screen for me to go and turn off the OEM unlocking. I thought maybe the cores were still going full bore since it was sitting on the charger and I tried pulling it off a few times...but the battery was never charged enough to do anything.
I'm still at a loss.
Any new developments or suggestions?
unlocked oem problem. help!
I tried everything. Heating. Draining. Freezing. Nothing works for me. I just need to unlock it so I can fix the bootloop issue. I badly need some help here guys. Thank you.
aphrodirish said:
I tried everything. Heating. Draining. Freezing. Nothing works for me. I just need to unlock it so I can fix the bootloop issue. I badly need some help here guys. Thank you.
Click to expand...
Click to collapse
If you bought your Nexus 6P via Google Store you can get a New Google Pixle XL even after the 1 Year device Guarantee
maybe your lucky enough
reddit.com/r/Nexus6P/comments/6y1tm2/official_6p_battery_shutdownbootloop_rma_thread
bcurran3 said:
I'm still at a loss. Any new developments or suggestions?
Click to expand...
Click to collapse
Get a good blow dryer or heat gun? A typical blow dryer will only reach ~140F on a good day. A decent heatgun will start around ~500F and go over 1000F. You're supposed to start with the device bootlooping and apply heat until the phone boots. My guess is you are not hot enough and/or not getting the heat to the right area on the back of the phone. Bear in mind this will just give you enough time to get into Dev Settings and toggle OEM Unlock so you can unlock your bootloader and flash a custom kernel like EX.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Update:
Based on "Google is replacing defective Nexus 6P units with Pixel XLs, but only in North America"
https://www.phonearena.com/news/Goo...h-Pixel-XLs-but-only-in-North-America_id98059
Just got off the phone with Google (10 hours ago) and confirmed they are replacing my dead/looping Nexus 6P out of warranty and swapping with a Pixel XL. It took me SIX MONTHS to get this resolved. I'm not happy about the time frame, but I guess I'm pseudo-satisfied with the end result.
For those who attempt a replacement, the KEY WORDS that seemed to make the customer service rep take notice was that mine started bootlooping after installing the 7.1.2 beta sometime in March. This is where her ears perked up and she started two "escalations" to get approval for "extend warranty" and replace my phone. Hope this helps you out.
The irony of this is, I'm going to give the Pixel XL to my wife, continue using my LG V20 for the moment, and try to determine if I want to spend the bucks on a Pixel 2 XL or a LG V30 later this year.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Try this
Try finding the OEM unlock code for your specific mobile from Huawei customer service site