Related
Hey guys, I have an Excalibur that gets stuck on the TMobile splash screen when you try to turn the device on.
I've tried doing a hard reset, but I still end up with the same problem. I can get the phone into the bootloader mode (green, blue red) but everything I've searched around (read the wiki, tried google, youtube, etc.) says that I need to be connected to ActiveSync in order to flash a rom onto it.
Is there any way to flash this thing while in bootloader mode or am I screwed?
Thanks!!
Stickys, official roms & hard-reset bootloader.
Thanks for the quick response, Stylez!
I've read the "hard reset and bootloader" post, which is how I learned to put the device in bootloader mode (thanks to you!)
I've also downloaded the necessary ROM file and loader from the other sticky you mentioned. (I did read and search on my own before asking)
But when I try to run the ROMUpdateUtility.exe it tells me to connect the device to activesync which I can't really do because it's in Bootloader mode and WindowsMobile Device Center says it's not connected.
Try this.
Did you SDA and Surreal unlocked your cell prior to flashing?
If not, do so. You can find both files in the Wiki or in one of the stickies I am sure.
SDA Unlock it from desktop, reboot, Surreal, drag it in the device, install it, once installed... go to the ROM you chose and run the AUTO file, not RUU... you should follow the instructions of when to click on and the center button on the device, now, (this might occur) I know it does make the sound of restarting and when you load the ROM say v1.7a Ricky and Styles RoseROM, it won't go over 3% saying it can't find the device... just click on the RUU this time, and I bet you that this time it will find the device and load it. Try it and let me know.
When I run the SDA Unlock, the button remains greyed out because it doesn't recognize the device is connected to the computer. Is it supposed to even though it's on the bootloader screen?
The white bootloader screen is only needed when you flash a new ROM into it. You need to connect the device NOT in bootloader but just as is when turned on normally so that the ActiveSync will recognize it.
Same thing for Surreal, you just drag it in the phone and install it as you would install any .cab.
Inimical said:
Hey guys, I have an Excalibur that gets stuck on the TMobile splash screen when you try to turn the device on.
Is there any way to flash this thing while in bootloader mode or am I screwed?
Click to expand...
Click to collapse
Thanks, but unfortunately I can't get this thing to boot past the T-Mobile splash screen. Is there no way to flash it without Activesync?
Also, I'm in the Red/Green/Blue bootloader (hold the camera button and attach USB cable) not the White one.
So, you are running the T-Mobile flash, yet you can't go past the initial screen? Did you just get it like this or did you flash it before... ???
Did you try to run USPL CID BYPASS? It might get it into white bootloader mode, just assuming. If not, then do as I suggested, when it says it doesn't find the device, re-run the RUU. As posted above.
I got the phone like this from a friend. So, who knows what could be wrong with it.
The bootloader screen says it's running 1.22.0000 and as far as I know, it's the default TMobile rom.
It won't get passed the T-Mobile initial screen. It will just turn back off after a few minutes. I can get it into the Bootloader mode as mentioned before, so I assumed I'd be able to flash it to fix whatever is preventing it from booting fully.
It seems, however, that something more severe may be wrong with the phone if the computer can't register that it's connected which prevents me from running any kind of CID BYPASS programs or SDA Unlock utilities.
Any other suggestions?
I am gonna think about it, but hopefully the more expert in here will help you sooner. I personally think your buddy messed up while flashing or something. Because if he did not, then he can just send it back and get another one from T-Mo. Plus, not being there to see makes things a bit more complicated this once.
Are you even connected to ActiveSync when in bootloader mode? I don't mean you, I mean in general.
And btw, did you try to do what I suggested you?
Connect the phone, get it in bootloader, try to flash the T-Mo ROM and clickon AUTO.bat, an image is on the guide with pics sticky thread in here... that should open and ms-dos thing, even if it opens the loader and doesn't go over 3%, this time... click on the RUU icon.. it worked for me last night and for the T-Mo ROM you shouldn't need any sda or surreal stuff. Try it...
You can get the T-Mo ROM from their web-site or here too.
I know you can go on youtube and look up upgrade to kavana, there is a guy who has it for download. Thing is T-Mo asks you for a cell number to verify you are the owner of the phone so you might have to insert your friend's number.
Capitan Totti said:
Are you even connected to ActiveSync when in bootloader mode? I don't mean you, I mean in general.
Click to expand...
Click to collapse
No, while in bootloader and connected via USB, ActiveSync (WindowsMobile Device Center in Vista) says that there is no device connected.
Capitan Totti said:
And btw, did you try to do what I suggested you?
Connect the phone, get it in bootloader, try to flash the T-Mo ROM and clickon AUTO.bat
Click to expand...
Click to collapse
I tried this step, however, when the DOS box opens, it tells me it cannot find the phone and asks to try again. I do this repeatedly and get nothing. I also tried clicking NO on the retry, but nothing.
Capitan Totti said:
You can get the T-Mo ROM from their web-site or here too.
I know you can go on youtube and look up upgrade to kavana, there is a guy who has it for download. Thing is T-Mo asks you for a cell number to verify you are the owner of the phone so you might have to insert your friend's number.
Click to expand...
Click to collapse
Tried that too, I actually have T-Mobile so I put in my own number. I ended up with the same error message about not finding a phone. Is it supposed to find the phone when connected in Bootloader mode?
Thanks for your help, btw
Thanks for explaining that. I think you might have yourself a bit of a problem.
I'll ponder on it and let you know. Can't you return it in exchange for another Dash?
What ROM are you trying to flash? I would recommend that you go to T-Mobile.com/wmupgrade and download the current Officially Dash ROM and recover the device that way. If you do not have a T-Mobile phone number, I can get you one that you may use to access the download page.
Once you reflash the official rom I recommend you do the CID unlock and flash a 6.1
stellarvelocity said:
What ROM are you trying to flash? I would recommend that you go to T-Mobile.com/wmupgrade and download the current Officially Dash ROM and recover the device that way. If you do not have a T-Mobile phone number, I can get you one that you may use to access the download page.
Once you reflash the official rom I recommend you do the CID unlock and flash a 6.1
Click to expand...
Click to collapse
I recommend reading the thread before posting. All you proposed I already mentioned and he answered. Look above...
I tried many times and many versions of flashtool but my phone just won't flash any firmware. Unknown source and debugging mode were selected, but I always get Erro Flashing Aborted and it is really starting to annoy me.
Anyone could help????
let me help u out. u should check and do the following steps:
1. Turn on debugging mode + unknown resource in application setting
2. Make sure, drivers for xperia arc fastboot are installed correctly (no yellow hardware warning in "device manager" windows when you use flash mode
3. install sonyerricson software update and update services from sony website (this will correct ur xperia arc driver)
4. Try to update ur firmware from "update services", it will guide u through flash mode. in my case, that will not let me updated bcoz i already unlocked bootloader. The reason i did update via update services is just want it install correct usbdrivers for my arc
5. Go back to flashtool, now i'm pretty sure u can run flashing as smoothly as silk
How do I install those Fastboot drivers?
ratatouille said:
How do I install those Fastboot drivers?
Click to expand...
Click to collapse
So, i can assume that u haven't unlocked ur bootloaders
Here, following those steps thoroughly to get it done:
This one tell u how to install fastboot driver:
http://dvpda.com/299/how-to-unlock-bootloaders-on-your-xperia-arc-for-neo-play-pro.html
Click to expand...
Click to collapse
this one tell u how to get ur phone rooted:
http://www.addictivetips.com/mobile/how-to-root-sony-ericsson-xperia-arc-and-xperia-neo/
Click to expand...
Click to collapse
babygau said:
So, i can assume that u haven't unlocked ur bootloaders
Here, following those steps thoroughly to get it done:
This one tell u how to install fastboot driver:
this one tell u how to get ur phone rooted:
Click to expand...
Click to collapse
Problem is that my bootloader can't be unlocked... No blue light while holding menu button+connecting cable.
I even tried this http://forum.xda-developers.com/showthread.php?t=1115542 but it failed on Installing User Data.sin (at only one milimeter from succes). I am going crazy over it.... Had to use SEUS seven times so far to have the phone work again.
did u buy sim-locked phone?
babygau said:
did u buy sim-locked phone?
Click to expand...
Click to collapse
Yes but it is now unlocked
I think that's bcoz ur using locked phone, so hope this will solve ur problem
punkmonkey1984 said:
So as you may already be aware phones like mine, (orange uk) have the fastboot locked down, and so we cant unlock the bootloader.
I for one believe it can be accessed but needs a little bit of time and research on getting it done.
This thread is aimed for brain-storming for ideas and collecting them for us to try out,
You can de-brand your phone by flashing the software from this thread
http://forum.xda-developers.com/showthread.php?t=1033193
thanks to scott4 for the first upload mirror on page 3
Any ideas on getting the bootloader up and going on locked devices please put them in here
UPDATES
We now have root access thanks to Chainfire's gingerbreak apk which is here
http://forum.xda-developers.com/showthread.php?t=1044765
If your getting "could not extract assets" from gingerbreak
try doing
if that Fails try replacing it with rm -r /data/local/tmp
Update 2
Blagus has kindly opened up this thread here
http://forum.xda-developers.com/showthread.php?t=1063394
We need people with a SIM-FREE phone with a LOCKED bootloader to help us all out, so if thats YOU !!!
Help us poor sods with branded handsets please.
Click to expand...
Click to collapse
ok i have a htc incredible and i have been trying to root it all day but i cant seem to get it to work, i cant get s-off and i cant figure out how to downgrade it and i would really appreciate it if someone would help me
acdc720 said:
ok i have a htc incredible and i have been trying to root it all day but i cant seem to get it to work, i cant get s-off and i cant figure out how to downgrade it and i would really appreciate it if someone would help me
Click to expand...
Click to collapse
Have you seen this guide? http://forum.xda-developers.com/showthread.php?t=1506258 Or this one. http://forum.xda-developers.com/showthread.php?t=1600904
yes i sure have.
yes i have tryed those. my problem is it keeps saying that my unlock code cannot be loaded, and for some reason adb will not reconize my phone
acdc720 said:
yes i have tryed those. my problem is it keeps saying that my unlock code cannot be loaded, and for some reason adb will not reconize my phone
Click to expand...
Click to collapse
Did you install the adb drivers on your pc? If adb isnt working, how did you get the info to give htc for the unlock code?
yea
like i said it works up the the point that i have to put in the fastboot flash unlocktoken Unlock_code.bin command
acdc720 said:
like i said it works up the the point that i have to put in the fastboot flash unlocktoken Unlock_code.bin command
Click to expand...
Click to collapse
That is strange, do other fastboot commands still work? If you type fastboot devices, does it show your serial?
When flashing the unlock code does it give any certain error, or just
hang?
Is usb debugging enabled?
hey
ok what is happaning is adb shows my phone when it is normally running but when it is in bootloader or fastboot it doesent get reconized
acdc720 said:
ok what is happaning is adb shows my phone when it is normally running but when it is in bootloader or fastboot it doesent get reconized
Click to expand...
Click to collapse
Ok you may need to install the driver for that too. On your computer go to device manager with the phone in hboot/fastboot. See if the driver is installed. Its the same driver as the last driver you installed for regular adb, but you have to install it for both one in each mode. Hope you get what im saying.
yea
what driver should i be using?
acdc720 said:
what driver should i be using?
Click to expand...
Click to collapse
The same one you used for the regular adb. If you dont have it still you can use these http://dinc.does-it.net/ADB/ADB_Drivers.zip
yea
that still didint work i have been installing and uninstalling stuff since 6:00 am and i just cant seem to get my phone to get reconized in bootloader
acdc720 said:
that still didint work i have been installing and uninstalling stuff since 6:00 am and i just cant seem to get my phone to get reconized in bootloader
Click to expand...
Click to collapse
Not sure, it has to be a driver issue on the pc. Try uninstalling all the drivers, and restarting from scratch. Install the driver with the phone on and booted, then install same driver while in hboot/fastboot. Mabey take a break and come back to it, if you stare at it too long you start becoming a zombie and make mistakes.
yea
that still didint work, i have the drivers all of the updats and i just cant get it to reconize it
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. I have been trying to unlock this phone for 2 days now!
Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well my code is 16 numbers long. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same.
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Tread3r said:
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. For purposes of convenience and time (I have been trying to unlock this phone for 2 days now!) I will post my IMEI code here ( 3529000059203526 ) and the unlock code given to me by sony through email (61CAA387DC11C4CF).
I hope this doesnt break any rules or anything.
I am doing this to see if anyone here can help me. Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well as you can see my code is 16 numbers long, so in effect I only entered up to number "5". I would like to know if anyone is willing to test my IMEI and see if they get the same code. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key, this is why I am posting. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same (as above).
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Click to expand...
Click to collapse
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Thanks for the advice, I will edit it ASAP.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Hey he removed the imei number from his original message but that's pointless unless u remove it from your quote
Sent from my Xperia S using xda app-developers app
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Chriszo said:
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Click to expand...
Click to collapse
Glad to hear im not alone . No I still haven't found a way to unlock it. Sorry for asking but what does "PN" mean? Just so we are clear.
Ok thanks for your answer. No problem, but its just a mistake. Correctly it should be "PM" for personal message. I thought you would write on this way so I cant read any reasults
UPDATE:
I have tried other processes that all have the same steps, be it they were simplified programs with GUI's. I have come to the conclusion that my fastboot driver was installed incorrectly, because the first time I installed it on my phone I was able to see the S1 bootloader icon on device manager and I was able to click on it fast enough to enable it to install the driver. And correct me if im wrong but when we press UP on the volume rocker on our XS's and connect it to the USB we should see a blue right light? Well that is what happens when I do it so I assume I installed it correctly then.
Now after these first few failed attempts at unlocking I got frustrated and just factory reset my phone, completely ( I made back ups of course). This time however I used a program which is suppose to install all the drivers and simplify the whole unlocking process, I dont remember what program exactly, i'll check my files and get back to you guys on that.
Again it failed, showing the FAILED ("oem" error message) so I checked the steps from Doomlords guide and re checked my device manager. This time when I connect my phone it doesnt show the S1 bootloader icon on Dev manager, instead it shows "android phone ADB Interface". BUT I still get the blue LED when I connect my phone via USB, so does that mean I have fastboot on my phone again? ( I assume I do because the program I used says it did install it correctly and it even showed the "install anyway" window)
I am almost loosing all hope to unlock my XS , maybe I got a lemon phone or did something wrong again. I am willing to do another factory reset and restart the whole process again. This time I will follow every single step on the official website and see what happens.
But before I do that I want to ask, does anyone know of any news or whereabouts for an unofficial unlock bootloader process? I know its a long shot because we already have an official way but as from recent experience it doesnt work 100% of the time.
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Chriszo said:
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Click to expand...
Click to collapse
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Tread3r said:
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Click to expand...
Click to collapse
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
It was AOKP, the advanced project for this device.
I think your right, but in how far is the bootloader linked to the needed kernel? And why cant the bootloader be unlocked several times...?
Of course the kernel is a main part of the rom, but without an unlocked bootloader even the kernel would not be accepted by the bootloader. Thats the problem with other firmwares/ roms why you have to unlock it
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
razormc said:
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
Click to expand...
Click to collapse
I am using Windows 7 and I have used flashtool. I believe the drivers are correct because,as you said, the blue LED does show and stay while I fastboot my phone. Same goes for the green LED when I go to flashboot.
Chriszo said:
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
Click to expand...
Click to collapse
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Tread3r said:
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Click to expand...
Click to collapse
First, unlock your bl. Then root. I done that on my old Arc S and it works great.
Sent from my LT26i using xda developers-app
@ Tread3r:
Yes the drivers are installed correctly, because the phone starts into fastboot and flashboot with each the right light.
Thats the great problem with our devices. I did it nearly the same way and Ive got a similar problem, as the first answers describe in this post. Actual the original stock rom is installed on my Sony and all works correctly, but its just a short-term workaround
The bootloader unlockind process still end in an error message and that is my problem.
@ Vatih:
Nice try, but this is our problem... :/
---------- Post added at 11:41 AM ---------- Previous post was at 10:57 AM ----------
I cant believe it myself, but the alternative way works, althought I cant read anythink in the tool because of the language...
I've got the superuser app and root permissions and all works.
This link helped me: http://forum.xda-developers.com/showthread.php?p=39498268
It's the tool for the "new" firmware, .55, the latest from sony.
Hope, its also succesfully with your devices
I solved our problem. My bootloader is now open
I did it with the unlock, flashtool tool of this forum that helps you to open the bootloader and flash kernels and roms.
http://forum.xda-developers.com/showthread.php?t=2087337
Seems like just the code was wrong.
It worked with the first try
But be careful, although its just the bootloader, all data will be deleted. My phone is empty again :/ Of course I've got some backups...
Ok, I bought a galaxy nexus SCH i515 off ebay. The phone was listed as verizon, all the information behind the battery came up as sch i515. However when I powered it on. The phone said activate samsung account. The phone matches verizon info on the back. I contacted verizon and they said most likely the phone was rooted and that the phone could not be switched back even after a hard reset (which i did). I have wifi so used that to get on play store and downloaded rootchecker.... it says phone is not rooted.. (did original owner just unroot phone) am I screwed or is there anything I can do to get verizon able to activate it?
1) wrong section
2) follow this: http://forum.xda-developers.com/showthread.php?t=1626895
after step 2, check in the phone status menu for the model number.
So i'm a noob and after running through all this I can still (and verizon saying that the imei number wasn't in their database) make this work with verizon... i dont want to get this into a boot loop or fry this thing.. sorry for bugging out... I just want to know if this will officially work... again my phone was verizon and was switched to a sprint phone (upon powering up it asked for sprint activation.)
loopers said:
So i'm a noob and after running through all this I can still (and verizon saying that the imei number wasn't in their database) make this work with verizon... i dont want to get this into a boot loop or fry this thing.. sorry for bugging out... I just want to know if this will officially work... again my phone was verizon and was switched to a sprint phone (upon powering up it asked for sprint activation.)
Click to expand...
Click to collapse
I appreciate your quick informative answer but if i've already called verizon and they have informed me that the imei is not in their data base.... if i do all these steps and flash back to complete stock the imei still will not be in there data base correct? I mean I'm still stuck on this.... if I need to start asking somewhere else please let me know. Thanks
Just flash the factory images from Google. And make sure the ESN is good you can check it just Google search
Sent from my Nexus 4 @1.72 GHz on Stock 4.2.2
where is the factory images from google? Sorry i've been back and forth with seller and verizon and DO NOT want to screw this up
I see nothing specific from google search that says from a google site to flash these files to phone with steps
loopers said:
I see nothing specific from google search that says from a google site to flash these files to phone with steps
Click to expand...
Click to collapse
sorry found files
well found everythhing i need and loaded into the bootloader.. can't get it unlocked because it won't recognize fastboot devices..... it recognizes nothing. tried multiple ports.usb ports that is.... comes up with error code 214dfddsf i can't remember.... googled error.. no one really knows a fix.. if anyone knows of a toolkit for 4.1.1 or similar for samsung galaxy nexus let me know.... i've been trying to get my wifes phone activated for 6 1/2 hours and i'm done with it less you guys have a clear cut alternative.. i don't expect anyone to jump up and say here ya go but if ya do i'd greatly appreciate it.... i've googled the error to death.. no clear cut fix.... and i'm not trying to load up a rom.. i neeed to get the phone completely factory reset so i can get it activated from verizon..
oh yeah... i found all the device drivers etc.. and they are working 100%.... also turned on debugging mode..... know nothing else to do to get it to recognize commands in command prompt... i'm typing the commands from the folder the files are in..... nothing with that error i'm not getting any further anyway....
loopers said:
oh yeah... i found all the device drivers etc.. and they are working 100%.... also turned on debugging mode..... know nothing else to do to get it to recognize commands in command prompt... i'm typing the commands from the folder the files are in..... nothing with that error i'm not getting any further anyway....
Click to expand...
Click to collapse
fastboot and adb are 2 completely different modes, and the commands are not interchangeable. usb debugging has nothing to do with fastboot whatsoever
Pirateghost said:
fastboot and adb are 2 completely different modes, and the commands are not interchangeable. usb debugging has nothing to do with fastboot whatsoever
Click to expand...
Click to collapse
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
loopers said:
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
Click to expand...
Click to collapse
Try wugs nexus root toolkit. More friendly for new users. Just Google the name and it'll come up.
Sent from my Galaxy Nexus using xda premium
loopers said:
i was just following the link on that page the guy posted..... followed download.. hooked up... device installed drivers on comp... and couldn't get it to do anything while on bootloader.. it would not recognize and would show an error on the phone.... wasn't doing anything with adb
Click to expand...
Click to collapse
Just to make sure. You are in the bootloader on the phone and you are typing in the Fastboot devices and then OEM unlock command in Windows cmd? Try a different set of drivers. Uninstall the ones you have now and click the link below. Install those and do the "fastboot devices" command again. The naked divers seem to give people the least amount of problems.
Drivers: http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Carbon | AK SKL
as is strewn throughout these forums....ADB and FASTBOOT use different drivers. just because you have adb working doesnt mean that fastboot is setup properly
Sandman-007 said:
Just to make sure. You are in the bootloader on the phone and you are typing in the Fastboot devices and then OEM unlock command in Windows cmd? Try a different set of drivers. Uninstall the ones you have now and click the link below. Install those and do the "fastboot devices" command again. The naked divers seem to give people the least amount of problems.
Drivers: http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Carbon | AK SKL
Click to expand...
Click to collapse
those are the drivers i have installed i think someone completely fudged this phone
those are all google nexus don't say anything about samsung version :\
fudge it i'm gonna try that root tool kit.. i just gotta get this thing running on verizon for my wife.... don't want root.... just root and unroot like the toolkit says if it works magic... i hope
loopers said:
fudge it i'm gonna try that root tool kit.. i just gotta get this thing running on verizon for my wife.... don't want root.... just root and unroot like the toolkit says if it works magic... i hope
Click to expand...
Click to collapse
No need to root, just install drivers, unlock bootloader and flash stock image, then lock the bootloader up..
Got it fixed. Tool kit worked. Txx
Sent from my SCH-I535 using Tapatalk HD