I began rooting my G-Slate with the newly released rooting method to unlock the bootloader. I was able to root fine, and then I went on to flash the custom kernel. Well, I misunderstood and thought that the root unlocked the bootloader, and now after flashing the kernel, my tablet is stuck in fastboot mode telling me the kernel image is invalid. I am sure this happened because I didn't unlock the bootloader. I have been trying to find a way to unbrick it. I was thinking of four possibilities -
1. I could flash the original kernel (which I do not know if that will work...). I am still looking for the original kernel for 3.1 so if anyone could point me in the right direction, that would be great!
2. I could get a recovery image from somebody (..?) and flash that with fastboot
3. If I could somehow push a zip file to my gslate with fastboot, or if I could burn a zip to an img and flash it that would be amazing, then I could flash the unlock zip.
4. I could buy another, and return it saying that it was messed up, but keep the good one and give them my brick (I'm joking of course)
I would like to refrain from option 4, so PLEASE if anyone knows a solution, let me know ASAP. I am grateful for any help, even if you tell me that I'm screwed.
Related
So I have a ns4g that I attempted to root but got hung up and am now stuck with a unlocked bootloader but no super user. So as I see it I have 3 options (if you see others PLEASE TELL ME)
1. somehow get my bootloader locked again and go back to stock (unroot)
2. keep unlocked bootloader and eventually accept ics ota (will this be ok or will having an unlocked bootloader much things up with the ota?)
3. figure out a way to finish the root process I'm sort of in the middle of (aka get super user)
If it matters I am running 2.3.7 and using a macbook running 10.7.2
What would you guys suggest?
jmelick07 said:
So I have a ns4g that I attempted to root but got hung up and am now stuck with a unlocked bootloader but no super user. So as I see it I have 3 options (if you see others PLEASE TELL ME)
1. somehow get my bootloader locked again and go back to stock (unroot)
2. keep unlocked bootloader and eventually accept ics ota (will this be ok or will having an unlocked bootloader much things up with the ota?)
3. figure out a way to finish the root process I'm sort of in the middle of (aka get super user)
If it matters I am running 2.3.7 and using a macbook running 10.7.2
What would you guys suggest?
Click to expand...
Click to collapse
flash a custom recovery(cwm or twrp) via fastboot, then flash a custom rom(and gapps). thats all you need. all the custom roms out there have root. you dont have to flash superuser.
How do I flash cwm? I think when I did this before I had the wrong version as it didn't allow for me to mount after I unlocked the bootloader
Use http://forum.xda-developers.com/showthread.php?t=1250583 to root! It will recognize that your bootloader is already unlocked and skips to flashing CMW and giving you root! There's a youtube video showing it in action if you get stuck by qbking!
Will this work with osx?
jmelick07 said:
How do I flash cwm? I think when I did this before I had the wrong version as it didn't allow for me to mount after I unlocked the bootloader
Click to expand...
Click to collapse
heres the latest version of cwm recovery for the nexus s(not ns4G) http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-crespo.img
heres where all the cwm recoveries can be found, including the ns4g http://clockworkmod.com/rommanager
Ok, now how do I get that img on my phone?
The cwm for ns4g that I just downloaded that is
I'm fairly content just waiting for the google ics ota... when that comes will it mess my phone up because of my unlocked bootloader?
or even better can someone write me instructions to lock my bootloader?
I found this forum http://forum.xda-developers.com/showthread.php?t=875630
But obviously there are steps before this to have the terminal put these commands towards the phone.
jmelick07 said:
Ok, now how do I get that img on my phone?
The cwm for ns4g that I just downloaded that is
Click to expand...
Click to collapse
look at part 3 http://forum.xda-developers.com/showthread.php?t=1007782
only you dont need superuser, any custom rom has root.
Ok, I think I just want to relock my phone and wait for the ota...
I've tried just going into terminal and typing "fastboot oem lock" and it says that the command is not found... what did I do wrong?
You don't need to lock bootoader to get ota.
I've read before that accepting an ota with an unlocked bootloader will brick your phone... Can anyone else confirm that it's ok to accept the eventual ota with an unlocked bootloader?
So as some of you may know, the vivid was recently unlocked. Being comfortable with root and custom roms from my nexus one, I unlocked the bootloader and rooted it...
I then wanted to install a ROM that many were reporting to work well with the ATT vivid... however I did something wrong.
I first went here- http://forum.xda-developers.com/showthread.php?t=1365853 which says you need to install the kernel here- http://forum.xda-developers.com/showthread.php?t=1359656
However I guess I have no recovery? If I click on recovery in bootloader it just shows a phone with some arrows... and if I open ADB on my computer it just scrolls through stuff quickly then closes. Am I screwed? I can get to my bootloader at least... any help would be much appreciated.
If I could somehow flash the stock kernel back I'm sure it would work, as the stock kernel source is available at htcdev However I can't figure out how to get adb to let me actually enter commands while in the bootloader.
Solved it!
I pushed the recovery using fastboot on the computer and was able to flash the ROM. Yay!
Ok so how does your rom work for you? is it better than stock? Oh and of course what rom was it?
Gary
Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.
Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.
Ok so I gained root access on my Droid razr maxx and tried to use the motopocalyse exploit tool to unlock the bootloader but misunderstood that it would work to unlock the bootloader on my build. The flash failed now I am having to use the button combo to boot the phone. Here are the details of the phone system version:9.18.94.XT926, razr maxx hd, Android:4.1.2 build :9.8.1Q94. Is it possible to unlock bootloader and can someone help me, I do have rsd lite installed, any help would be greatly appreciated thanks.
you can NOT unlock.
any successful flash will fix the error. you could grab your current version from here and re-flash it.
Okay, will I need to mod the file any I read somewhere that I would need to edit it and take the lines containing getvar out,but other say its not needed. I am assuming a wipe would also be essential for the flash. .Also, can anyone recommend any safestrap compatible roms for this phone. I am doing this for a friend that would love something similar to my Alliance rom that I am currently running on my Note 2, I am more comfortable using odin and the download mode on my samsung. .
youraffliction said:
Okay, will I need to mod the file any I read somewhere that I would need to edit it and take the lines containing getvar out,but other say its not needed. I am assuming a wipe would also be essential for the flash. .Also, can anyone recommend any safestrap compatible roms for this phone. I am doing this for a friend that would love something similar to my Alliance rom that I am currently running on my Note 2, I am more comfortable using odin and the download mode on my samsung. .
Click to expand...
Click to collapse
I would edit it so it doesn't flash those. odin is Samsung's version of fastboot, you'll be fine, just grab RSD and you'll be up and running in no time
Successful flash.
palmbeach05 said:
I would edit it so it doesn't flash those. odin is Samsung's version of fastboot, you'll be fine, just grab RSD and you'll be up and running in no time
Click to expand...
Click to collapse
Okay, First I would like to thank you both, I have restored the phone back to working order, restored root and safestrap. Now I am in the process of finding a rom that would work, with the priority being stability and customization, any advice?The only thing I would recommend to people in the same predicament is to download the firmware into its own separate folder because it would not work in my main download folder, not sure why, something to do with the boot image.
I was trying to upgrade my opo and I found my bootloader was locked but to unlock it I needed a recovery installed and somehow it had dissapeared. Please help asap
tom_clegg said:
I was trying to upgrade my opo and I found my bootloader was locked but to unlock it I needed a recovery installed and somehow it had dissapeared. Please help asap
Click to expand...
Click to collapse
None of that makes sense. You don't need a recovery to unlock your bootloader. Your bootloader can't disappear either. Look, you're going to have to provide a lot more information if you expect anybody to be able to help you. We need details, lots of them. We need to know exactly what you did to the device, we need to know exactly what the device can and can't do now. You need to explain everything with as much information as possible, because honestly, with the information you've given so far nobody can help at all.
Heisenberg said:
None of that makes sense. You don't need a recovery to unlock your bootloader. Your bootloader can't disappear either. Look, you're going to have to provide a lot more information if you expect anybody to be able to help you. We need details, lots of them. We need to know exactly what you did to the device, we need to know exactly what the device can and can't do now. You need to explain everything with as much information as possible, because honestly, with the information you've given so far nobody can help at all.
Click to expand...
Click to collapse
Ok well..
I was recently trying to flash the new oxygen OS onto my oneplus, but when i was trying to flash a custon recovery to do so like TWRP, it said bootloader needed to be unlocked, I did what was needed but my phone wouldnt boot into the stock recovery (or recovery of any form) and just stayed at the boot screen. This made me unable to unlock my bootloader so i am basically stuck on the current version of Android and cannot upgrade or flash.
tom_clegg said:
Ok well..
I was recently trying to flash the new oxygen OS onto my oneplus, but when i was trying to flash a custon recovery to do so like TWRP, it said bootloader needed to be unlocked, I did what was needed but my phone wouldnt boot into the stock recovery (or recovery of any form) and just stayed at the boot screen. This made me unable to unlock my bootloader so i am basically stuck on the current version of Android and cannot upgrade or flash.
Click to expand...
Click to collapse
That still doesn't make sense. Where did you read that you need to boot into recovery in order to unlock your bootloader? That isn't true. You use fastboot to unlock your bootloader, not recovery. Have a look at my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471