Ok, a bit of backstory for context: I had the bootloader unlocked, CWM and lgcmn and ZeroNull's rom installed, few days later, ran the wrong script on my hard disk whilst experimenting, and installed the A10x bootloader over my A200 bootloader, essentially bricking it.
is there someway I can fix it myself? or is Acer needed for this?
dragynbane222 said:
Ok, a bit of backstory for context: I had the bootloader unlocked, CWM and lgcmn and ZeroNull's rom installed, few days later, ran the wrong script on my hard disk whilst experimenting, and installed the A10x bootloader over my A200 bootloader, essentially bricking it.
is there someway I can fix it myself? or is Acer needed for this?
Click to expand...
Click to collapse
Has to go to Acer sorry to say.
Tapatalked from my Galaxy S II.
pio_masaki said:
Has to go to Acer sorry to say.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Alright, thanks for the quick reply.
Related
Hello all. Well after many many years with Sprint they finally got on my last nerve and now I am a new Verizon customer and a very happy new owner of the Galaxy Nexus. Awesome phone! Anyway my question is I have been told the bootloader of this phone is locked. I have never messed with a phone with a locked bootloader. While I was with Sprint I had the Epic 4G Touch so I am familiar with Odin, CWM, flashing roms, etc. What is the preferred method to altering the Nexus to be able to root, CWM, flash roms? Also what is currently considered by most to be the best rom that leaves the phone with all of its functions working? Thank you in advance for any information you folks can offer.
Pete720 said:
Hello all. Well after many many years with Sprint they finally got on my last nerve and now I am a new Verizon customer and a very happy new owner of the Galaxy Nexus. Awesome phone! Anyway my question is I have been told the bootloader of this phone is locked. I have never messed with a phone with a locked bootloader. While I was with Sprint I had the Epic 4G Touch so I am familiar with Odin, CWM, flashing roms, etc. What is the preferred method to altering the Nexus to be able to root, CWM, flash roms? Also what is currently considered by most to be the best rom that leaves the phone with all of its functions working? Thank you in advance for any information you folks can offer.
Click to expand...
Click to collapse
Unlock the boot loader firstly but beware it will wipe your sdcard.
Use fast boot to unlock it, type oem fastboot unlock and go from there.
Flash cwm using fastboot by typing fastboot flash recovery xxxxxxx.img (xxxxx.img is whatever the filename is)
You are probably familiar with cwm so I won't bother explaining that.
All the rooms here have everything working on them. We'll except sense 4.0 and touchwiz ports etc. But that's obvious.
Ps. All phones have locked bootloaders!
Yeah, you might mean unlocked bootloader. You do have to unlock it first, but it doesn't take an exploit to do so. See here for a starting point:
http://forum.xda-developers.com/showthread.php?t=1400871
As for the best rom, impossible to say, so many . It depends on what exactly you're looking for. aokp is probably the most features-popular, but there are many others. I use cm9 with the reloaded mod, personally.
sent from my Zerg Hatchery.
Ok I used the Toolkit 5.5 to unlock, root, CWM etc. Seemed easy and effortless. I have now installed AOKP Rom on my Nexus. What do I need or need to know in order to return my phone to box stock say incase I have to take it to Verizon for any reason?
Pete720 said:
Ok I used the Toolkit 5.5 to unlock, root, CWM etc. Seemed easy and effortless. I have now installed AOKP Rom on my Nexus. What do I need or need to know in order to return my phone to box stock say incase I have to take it to Verizon for any reason?
Click to expand...
Click to collapse
SDK, Fastboot, ADB
anton2009 said:
SDK, Fastboot, ADB
Click to expand...
Click to collapse
Forgive me, I am just an end user that can follow directions well Can you explain what this means? Is there a file I am going to have to download or does Option #8 in the Toolkit do everything?
Pete720 said:
Forgive me, I am just an end user that can follow directions well Can you explain what this means? Is there a file I am going to have to download or does Option #8 in the Toolkit do everything?
Click to expand...
Click to collapse
Options 8 (Extract and Flash Google Factory Stock ROM), 10 (Reflash Stock Recovery [just to be safe]), and 11 (Relock bootloader) will return it all to stock. I know, because I just had to do this to 3 GNex's this past week to send them back to Verizon
Looks like your question was answered, but for me, I used Wugfreshes toolkit to root then to unroot, just click unroot, let it do its thing and then click OEM lock to make it factory.
Okaay said:
Looks like your question was answered, but for me, I used Wugfreshes toolkit to root then to unroot, just click unroot, let it do its thing and then click OEM lock to make it factory.
Click to expand...
Click to collapse
Only if you are stock and rooted.
He is running a custom rom and kernel and has cwm flashed, that method will not revert them to stock.
nodstuff said:
Ps. All phones have locked bootloaders!
Click to expand...
Click to collapse
hmmm...not true, the Samsung Galaxy S II doesn't come with a locked bootloader
nicholaschum said:
hmmm...not true, the Samsung Galaxy S II doesn't come with a locked bootloader
Click to expand...
Click to collapse
My apologies, I totally forgot to update my signature. I do not have the GSII anymore.
Can anyone point me int he direction of the box stock rom file I need to work with Toolkit to restore my phone? I followed the directions and got the image from code.google.com but it wont install. ALways says something is missing.
Toolkit says the file shouls end in .tgz but the file I am downloading from Google does not say that. My phone is 4.0.2 (ICL53F) and that is the file I am downloading from Google's image site.
Pete720 said:
Toolkit says the file shouls end in .tgz but the file I am downloading from Google does not say that. My phone is 4.0.2 (ICL53F) and that is the file I am downloading from Google's image site.
Click to expand...
Click to collapse
I believe that the toolkit will auto download if you just run the option.
Hi,
Been snooping round here for a while but haven't needed to post as i found all the answers until now!
I have just flashed my Galaxy Nexus to yakju using the Nexus Root Toolkit by Wugfresh in order to get 4.1.1 and it all went smoothly. The updtae is there but when i try and install it i just get a red error sign. At first i though it was because i still had an unlocked bootloader so i re-locked it (symbol has gone) but i still get the same error.
I'm a complete rookie at this but could do with some help!!!
Thanks,
KING LUFF said:
Hi,
Been snooping round here for a while but haven't needed to post as i found all the answers until now!
I have just flashed my Galaxy Nexus to yakju using the Nexus Root Toolkit by Wugfresh in order to get 4.1.1 and it all went smoothly. The updtae is there but when i try and install it i just get a red error sign. At first i though it was because i still had an unlocked bootloader so i re-locked it (symbol has gone) but i still get the same error.
I'm a complete rookie at this but could do with some help!!!
Thanks,
Click to expand...
Click to collapse
what error does it have exactly?
Also, I would download the update over WiFi, could be a corrupt OTA maybe.
I would reflash the 4.0.4 image via toolkit, then relock bootloader, then use WiFi to get the OTA
KING LUFF said:
Hi,
Been snooping round here for a while but haven't needed to post as i found all the answers until now!
I have just flashed my Galaxy Nexus to yakju using the Nexus Root Toolkit by Wugfresh in order to get 4.1.1 and it all went smoothly. The updtae is there but when i try and install it i just get a red error sign. At first i though it was because i still had an unlocked bootloader so i re-locked it (symbol has gone) but i still get the same error.
I'm a complete rookie at this but could do with some help!!!
Thanks,
Click to expand...
Click to collapse
Make sure you have the right 4.0.4 radio already on your device... xxla2 i believe.
RiG14LA said:
Make sure you have the right 4.0.4 radio already on your device... xxla2 i believe.
Click to expand...
Click to collapse
great advance there, i reinstalled all of the images and it's done it. I think i may have missed the radio off the list 1st time round :silly:
Thanks to both of you for the help, hopefully everything runs smoothly
:good:
Just remember next time you return to stock that it's important to flash both the stock bootloader and stock radio in order to receive and auto-install the OTA.
Also, bootloader unlock state does not matter. You can have an unlocked bootloader and it does not at all affect your ability to receive and apply an OTA.
KING LUFF said:
great advance there, i reinstalled all of the images and it's done it. I think i may have missed the radio off the list 1st time round :silly:
Thanks to both of you for the help, hopefully everything runs smoothly
:good:
Click to expand...
Click to collapse
you got it.
i got plenty of help in the last few days so i had to return the favor.
enjoy.
I've only recently bought an acer a100 but I've also bricked it...
I made a mistake of unlocking the boot loader while I was using a custom rom...
So, I can't get into recovery or something
For now, my question is this..
I used USBDeview or something like that to find out the uid but it seems that it isn't the right one
There's also a500 listed in the list, but it is only 11digits..
I guess this is because I adjusted the build prop.
So, my question is this for now. When you flash another rom or change its device name, does the UID change?
Sorry for my weird english..
Thank you in advance
jasonjjang08 said:
I've only recently bought an acer a100 but I've also bricked it...
I made a mistake of unlocking the boot loader while I was using a custom rom...
So, I can't get into recovery or something
For now, my question is this..
I used USBDeview or something like that to find out the uid but it seems that it isn't the right one
There's also a500 listed in the list, but it is only 11digits..
I guess this is because I adjusted the build prop.
So, my question is this for now. When you flash another rom or change its device name, does the UID change?
Sorry for my weird english..
Thank you in advance
Click to expand...
Click to collapse
Did you mean you locked the boot loader on a custom rom? I suppose this means you also have a custom recovery which means you're locked out, needs to be sent to Acer. We don't have the key to access the firmware to correct this.
Tapatalked from my Galaxy S II.
thx...but
Is there still a way to find out my UID?
Without using the USB thing I mean
Oh god....
jasonjjang08 said:
Is there still a way to find out my UID?
Without using the USB thing I mean
Oh god....
Click to expand...
Click to collapse
Dunno what a uid is but if you mean cpuid its the serial number. Won't matter though, its locked up.
Tapatalked from my Galaxy S II.
I have a L700 and it's refusing to let me re-lock the bootloader. It shows that it locks, but if I restart fastboot it shows unlocked again. if I restart the phone, it shows that it's unlocked. i've tried to flash a new build using ODIN and Fastboot but it still is acting up. Also, if i flash CWM and restart the phone, TWPR shows up which is currently on the phone. It's like updates aren't actually working!!!
Any ideas?
(It won't let me update my bootloader/radio's or recovery which is why I want to relock it, I think that might solve something)
Thanks,
Why do you need to relock your bootloader?
It's pretty much pointless.
electro` said:
Why do you need to relock your bootloader?
It's pretty much pointless.
Click to expand...
Click to collapse
I believe it will fix my issue. I feel as if I can lock it then unlock it, i'll be able to flash what I need. Since it's pointless, can you explain why my bootloader and radio's won't update?
This is going to be really stupid but did you do the command prompt relock bootloader in fastboot?
This seems kind of unusual.
Did you reflash the bootloader or anything else?
If not, try that.
electro` said:
This is going to be really stupid but did you do the command prompt relock bootloader in fastboot?
This seems kind of unusual.
Did you reflash the bootloader or anything else?
If not, try that.
Click to expand...
Click to collapse
I did relock the bootloader as stated in the OP. It goes back to unlocked with a restart or bootloader restart which shouldn't happen. I know it seems unusual. I've flashed everything (system, recovery, radio, bootloader) to no avail.
This might be a really stupid question but you say you have a L700???
What's that? These are the Google Galaxy Nexus forums.
Sent from my Nexus
bk201doesntexist said:
This might be a really stupid question but you say you have a L700???
What's that? These are the Google Galaxy Nexus forums.
Sent from my Nexus
Click to expand...
Click to collapse
http://www.samsung.com/us/support/owners/product/SPH-L700ZKASPR
Sprint GNex
bk201doesntexist said:
This might be a really stupid question but you say you have a L700???
What's that? These are the Google Galaxy Nexus forums.
Sent from my Nexus
Click to expand...
Click to collapse
Way to be an anus and look like an idiot doing it. I've read other threads with the same issue, I think it's a hardware issue and I'm just out a phone.
Thanks anyway.
Sooppex said:
Way to be an anus and look like an idiot doing it. I've read other threads with the same issue, I think it's a hardware issue and I'm just out a phone.
Thanks anyway.
Click to expand...
Click to collapse
He was trying to help you.
No need to be a **** about it.
You could try the Nexus Root Toolkit by WugFresh. I think that has a bootloader relocking facility in it.
http://goo.im/devs/WugFresh/NexusRootToolkit
Edit: Whoops, sorry, didn't fully read the thread, my bad
Hi,
Sorry for the silly questions. I just want to quickly check some things about the Nexus 7 Flo.
QUESTION 1: I'm constantly scared of bricking my device when rooting it. If I brick it when rooting, will ASUS repair it? If not, is there a tool I can use to unbrick?
QUESTION 2: If I use the All-In-One toolkit, how likely is a soft brick/hard brick? Can I un-everything (unroot + lock + install stock ROM + stock recovery) using the All-In-One toolkit if I need to?
QUESTION 3: If something happens with the hardware (e.g. port broken, screen cracked) and I am everything'ed (root + unlock + ROM installed + custom recovery), will ASUS repair it?
QUESTION 4: Can we get ParanoidAndroid 3+ for Nexus 7 Flo yet?
Thank you, and sorry for the noob questions!
OrangeFlash81 said:
QUESTION 1: I'm constantly scared of bricking my device when rooting it. If I brick it when rooting, will ASUS repair it? If not, is there a tool I can use to unbrick?
Click to expand...
Click to collapse
As far as I know, you don't have to unlock the bootloader to root. If you do, and need a repair, see question 2.
OrangeFlash81 said:
QUESTION 2: If I use the All-In-One toolkit, how likely is a soft brick/hard brick? Can I un-everything (unroot + lock + install stock ROM + stock recovery) using the All-In-One toolkit if I need to?
Click to expand...
Click to collapse
I would say unlikely to soft brick, and very unlikely to hard brick. And yes, you should be able to undo everything with a toolkit / fastboot commands.
OrangeFlash81 said:
QUESTION 3: If something happens with the hardware (e.g. port broken, screen cracked) and I am everything'ed (root + unlock + ROM installed + custom recovery), will ASUS repair it?
Click to expand...
Click to collapse
If the USB port breaks you might have a problem, since you need USB connection to issue fastboot commands, which are used to restore the device to locked, stock state. If the firmware is altered and/or the bootloader is unlocked, the warranty is void.
OrangeFlash81 said:
QUESTION 4: Can we get ParanoidAndroid 3+ for Nexus 7 Flo yet?
Click to expand...
Click to collapse
Patience...
If the firmware is altered and/or the bootloader is unlocked, the warranty is void.
Click to expand...
Click to collapse
@ameinild, will ASUS still repair it for me (but for a fee), or will they refuse to repair it at all? I don't understand warranties
OrangeFlash81 said:
@ameinild, will ASUS still repair it for me (but for a fee), or will they refuse to repair it at all? I don't understand warranties
Click to expand...
Click to collapse
Honestly I have no idea. I'm not too sure about how vendor repairs work either.
But as long as you don't erase or corrupt your bootloader (which would be an amazingly stupid thing to do) or smash your USB port, you should be good.
@ameinild, I have another question: Will ASUS know my device has been previously rooted or unlocked? Is there a triangle or something? Thanks!
Sent from my XT890 using xda app-developers app
OrangeFlash81 said:
@ameinild, I have another question: Will ASUS know my device has been previously rooted or unlocked? Is there a triangle or something? Thanks!
Click to expand...
Click to collapse
I'm pretty sure they can't know that in any way - I don't believe Nexus devices have a counter...
ameinild said:
Honestly I have no idea. I'm not too sure about how vendor repairs work either.
But as long as you don't erase or corrupt your bootloader (which would be an amazingly stupid thing to do) or smash your USB port, you should be good.
Click to expand...
Click to collapse
Not entirely true. Ordered mine from B&H, rooted, etc., and woke the next morning with a hard brick. Even restoring through fastboot did not work. So I wiped system, recovery, and boot, relocked the bootloader, and sent the device back for a refund. Just received the refund today without question. Simply told the customer service dude the device wouldn't boot when I received it. I know, a little dishonest, but I followed all instructions to a T, I believe it was a hardware issue anyway, though I only overclocked to 1800 or so.
dillinjer said:
Not entirely true. Ordered mine from B&H, rooted, etc., and woke the next morning with a hard brick. Even restoring through fastboot did not work. So I wiped system, recovery, and boot, relocked the bootloader, and sent the device back for a refund. Just received the refund today without question. Simply told the customer service dude the device wouldn't boot when I received it. I know, a little dishonest, but I followed all instructions to a T, I believe it was a hardware issue anyway, though I only overclocked to 1800 or so.
Click to expand...
Click to collapse
But you still managed to relock your bootloader, meaning fastboot worked which is the important thing.