so i load bootloader and it says its now ready to go, i push start to reset, but it doesnt it just loads up as normal, like it doesnt go through the 'set up menus' or any of that just turns on as if it would any other normal day onto my homescreen... then i click enter to root (on mac terminal) and it says error: device offline??
i was using my mac and nexus10root app and running 4.3 stock (never rooted before)
any advice or reasons behind this, because im stumped. i was following a step by step tutorial on youtube... thanks in advance guys.
W3bby said:
so i load bootloader and it says its now ready to go, i push start to reset, but it doesnt it just loads up as normal, like it doesnt go through the 'set up menus' or any of that just turns on as if it would any other normal day onto my homescreen... then i click enter to root (on mac terminal) and it says error: device offline??
i was using my mac and nexus10root app and running 4.3 stock (never rooted before)
any advice or reasons behind this, because im stumped. i was following a step by step tutorial on youtube... thanks in advance guys.
Click to expand...
Click to collapse
Did you unlock bootloader?
Sent from my Nexus 4 using Tapatalk 4
Targaeryan said:
Did you unlock bootloader?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
forgive me if im being an idiot, but is that when it turns blue the writing at the bottom? the programme says its been done... unless im missing something,
Deleted: was answered at the same time.
Sent from my Galaxy Nexus using XDA Premium HD app
W3bby said:
forgive me if im being an idiot, but is that when it turns blue the writing at the bottom? the programme says its been done... unless im missing something,
Click to expand...
Click to collapse
When you go into bootloader does it show unlocked state? Or when you boot normally does it show a padlock icon unlocked or locked?
Sent from my Nexus 4 using Tapatalk 4
Targaeryan said:
When you go into bootloader does it show unlocked state? Or when you boot normally does it show a padlock icon unlocked or locked?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
on the bootloader screen...
Lock State: unlocked
Reboot Flag Mode: none
then it says when i push enter on mac, on the rooting programme.
fast boot status: OKAYoem unlocked already
Ok. So you're bootloader is unlocked.. Maybe you can try using wugs toolkit to root it.
Sent from my Nexus 4 using Tapatalk 4
yeh when it restarts, i have the open padlock at the bottom but as i say it just loads up as normal, doesnt start like a factory reset would with me punching in details and signing up etc
then when i try to enter the root it comes up with this in terminal
Pushing CWM-SuperSU-v0.98.zip...
* daemon not running. starting it now *
* daemon started successfully *
error: device offline
error: device offline
does wugtoolkit work with macs?
really appreciate your help, i rooted my s3 in minutes this is taking me much longer!!
Yeah I think it does (I don't use mac).. I had an s3 too and yeah it was easy.. But seems wugs website is down so you won't be able to get it. The toolkit does it easily.. Maybe chainfire's rooting method may work too.. Let me see if I can find it..
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 02:41 AM ---------- Previous post was at 02:39 AM ----------
http://forum.xda-developers.com/showthread.php?t=2025268
[N10] CF-Auto-Root
Sent from my Nexus 4 using Tapatalk 4
Never use toolkits! Flash a custom recovery via fastboot and flash supersu 1.51 via the custom recovery
Sent from my Galaxy Nexus using XDA Premium HD app
ok thanks for the tip, what ones would you recommend? any tutorial video in particular i can follow?
thanks
W3bby said:
ok thanks for the tip, what ones would you recommend? any tutorial video in particular i can follow?
thanks
Click to expand...
Click to collapse
I recommend CWM touch. But it's personal prefrence. Here's a video guide:
https://www.youtube.com/watch?v=EoeliMYXnhk&feature=youtube_gdata_player
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
I recommend CWM touch. But it's personal prefrence. Here's a video guide:
https://www.youtube.com/watch?v=EoeliMYXnhk&feature=youtube_gdata_player
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
many thanks ill check it out.
Remember, Mac and Linux require fastboot to be used as sudo or su!
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Related
Where can I download the latest bootloader and how do I install it?
You can not install a boot loader. It's not possible because the boot loader is already on the phone. You mean custom recovery. Here's the link.
http://forum.xda-developers.com/showthread.php?t=1779092
Sent from my Nexus 7 using xda app-developers app
scream4cheese said:
You can not install a boot loader. It's not possible because the boot loader is already on the phone. You mean custom recovery. Here's the link.
http://forum.xda-developers.com/showthread.php?t=1779092
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Actually you are wrong. You should check that out
http://forum.xda-developers.com/showthread.php?t=1928915
Sent from my Galaxy Nexus
Pirateghost said:
Actually you are wrong. You should check that out
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Not only he's wrong, I'm talking about a tablet. I think I've figured it out.
I can't figure it out, when I enter the command in the CMD, it tells me "waiting for device."
Finally got it to work.
Hi,
After rooting my nexus 4 device is not working.After rebooting it ,it is only showing the colorful X sign and gets stuck there.It seems somehow i lost the OS.I tried verious methods to push the os in the device but it throws the error "device not founf".
Please help.
Thanks,
Amit
amitsinghcs said:
Hi,
After rooting my nexus 4 device is not working.After rebooting it ,it is only showing the colorful X sign and gets stuck there.It seems somehow i lost the OS.I tried verious methods to push the os in the device but it throws the error "device not founf".
Please help.
Thanks,
Amit
Click to expand...
Click to collapse
What method did you use to root it? What OS version did you have when you tried?
Use wugfresh toolkit, then go to bootloader then do an unroot, (soft-brick) after the method is done, follow steps on wugfresh and reroot, you can also install twrp, not sure if cwm is there or not.
Sent from my Nexus 7 using xda app-developers app
naierakram said:
Use wugfresh toolkit, then go to bootloader then do an unroot, (soft-brick) after the method is done, follow steps on wugfresh and reroot, you can also install twrp, not sure if cwm is there or not.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention i was using 4.3 android version.will wugfresh toolkit help?
amitsinghcs said:
Sorry forgot to mention i was using 4.3 android version.will wugfresh toolkit help?
Click to expand...
Click to collapse
What method did you use?
Try the manual method.. Toolkits are never recommended by pros here..
Sent from my Nexus 4 using xda app-developers app
Hey guys,
Just ordered a Nexus 4 online and waiting for it to be delivered. But had to ask a quick question, that is, how easy is it to brick the Nexus 4? And if so, can it be unbricked easily via software?
I am currently using a Motorola Defy + and it its almost unbrickable and can be recovered from any type of brick. So just curious
super noob bros said:
Hey guys,
Just ordered a Nexus 4 online and waiting for it to be delivered. But had to ask a quick question, that is, how easy is it to brick the Nexus 4? And if so, can it be unbricked easily via software?
I am currently using a Motorola Defy + and it its almost unbrickable and can be recovered from any type of brick. So just curious
Click to expand...
Click to collapse
Flash the wrong kernel is a really easy way to brick your nexus 4,and the only i know
Yep worst you can do is flash a kernel or ROM meant for a different device, but even that can usually be recovered by using download mode.
Sent using xda-developers app
Federico_96 said:
Flash the wrong kernel is a really easy way to brick your nexus 4,and the only i know
Click to expand...
Click to collapse
Chromium_ said:
Yep worst you can do is flash a kernel or ROM meant for a different device, but even that can usually be recovered by using download mode.
Sent using xda-developers app
Click to expand...
Click to collapse
You can easily recover if you have a nandroid backup though I think.
Fastboot erase bootloader will brick you pretty quickly
Sent from my Nexus 4 using xda app-developers app
In short, you really have to try to brick it. Even then, it takes some work to break it to the point that you can't fix it with fastboot. You won't hard brick it on accident. I don't consider a soft brick a brick of any sort when you can fix it in 15mins with fastboot.
Pretty much the only way to brick is flashing the wrong bootloader or flashing something that isn't a bootloader to the bootloader partition.
In a way yes. Although it isnt like samsungs download mode, it is kind of unbrickable if you do brick it you just go into the bootloader use a toolkit download the stock rom and it will do the rest for you
Thanks people. Much appreciated
There is a topic somewhere in these forums with a guide that uses a program called lgtool or lgetool (can't remember which)
Which even lets you recover from a bricked bootloader. Though it is a lengthy and technical process.
So at this moment it is physically impossible to brick your phone. Unless it is bricked from actual damage to the hardware
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
There is a topic somewhere in these forums with a guide that uses a program called lgtool or lgetool (can't remember which)
Which even lets you recover from a bricked bootloader. Though it is a lengthy and technical process.
So at this moment it is physically impossible to brick your phone. Unless it is bricked from actual damage to the hardware
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes there's a great guide by Gigadroid somewhere in the general section. Basically as long as you can get into download mode the phone can be recovered.
Sent from my Nexus 4 using xda-developers app
Yeah I don't understand why people view flashing a wrong kernel as bricked. If you can get into the bootloader in my opinion it's not bricked!
Bricked is when it's just that, the phone can only be used as a paperweight and doesn't turn on in any sort of fashion. So doing "fastboot erase bootloader" is what I call a brick, which you'd have to be really drunk or just a total moron to do. And flashing wrong bootloader, or being so lucky as to have a power outage in the spilt second it takes to flash a bootloader is one of those I view as brick.
Sent from my Nexus 4 using XDA Premium 4 mobile app
M3drvr said:
Yeah I don't understand why people view flashing a wrong kernel as bricked. If you can get into the bootloader in my opinion it's not bricked!
Bricked is when it's just that, the phone can only be used as a paperweight and doesn't turn on in any sort of fashion. So doing "fastboot erase bootloader" is what I call a brick, which you'd have to be really drunk or just a total moron to do. And flashing wrong bootloader, or being so lucky as to have a power outage in the spilt second it takes to flash a bootloader is one of those I view as brick.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Maybe because if you flash an incorrect kernel you can't boot into the boot loader? Just a thought.
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
Maybe because if you flash an incorrect kernel you can't boot into the boot loader? Just a thought.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
When does that happen? I've never had that happen. I just purposely flashed a wrong kernel and i can still get to bootloader and recovery...
M3drvr said:
When does that happen? I've never had that happen. I just purposely flashed a wrong kernel and i can still get to bootloader and recovery...
Click to expand...
Click to collapse
I saw a thread where someone flashed nexus 7 kernel on the nexus 4 and he had to buy a new device,but maybe Gigadroid wrote the guide after that thread
Federico_96 said:
I saw a thread where someone flashed nexus 7 kernel on the nexus 4 and he had to buy a new device,but maybe Gigadroid wrote the guide after that thread
Click to expand...
Click to collapse
I remember accidentally doing that on my galaxy Nexus. But twrp actually caught it and wouldn't allow me to install it. Kept errroring out.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Harry GT-S5830 said:
Fastboot erase bootloader will brick you pretty quickly
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This isn't a true fastboot command
But yes, this is a very hard device to brick, most everything is recoverable. But I'm sure there are plenty who find a way to do this, usually the ones who dive in head first and have bad luck.
Just be sure you read and understand before you try and beg for help
Sent from my Nexus 7 using Tapatalk 2
Get in fastboot mode..
Erase bootloader
Reboot
Profit??
Sent from my Nexus 4 using xda app-developers app
demkantor said:
This isn't a true fastboot command
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Have you actually tried the command.
On the nexus 7 this was a valid fastboot command and there was a few instances of people bricking by erasing the bootloader then rebooting before flashing another one
It probably would be a good idea for Google to have removed the ability to erase the bootloader as there really is no need to erase it
Sent from my Nexus 4 using xda app-developers app
WOW after i sold my s4 and got nexus 4 im even loving nexus moreeeDDD i wish nexus 5 is awesome as this DD
Can I use the Nexus toolkit to unlock n root, latest firmware not listed. Is it still supported?
mockneygeeza said:
Can I use the Nexus toolkit to unlock n root, latest firmware not listed. Is it still supported?
Click to expand...
Click to collapse
I'd recommend learning to do it manually rather than a toolkit, that way this will never be an issue again. It's very easy to do. See here: http://forum.xda-developers.com/showthread.php?t=2382051. The entire instruction set is in the very first post.
Sent from my Nexus 7 using Tapatalk 4
oldblue910 said:
I'd recommend learning to do it manually rather than a toolkit, that way this will never be an issue again. It's very easy to do. See here: http://forum.xda-developers.com/showthread.php?t=2382051. The entire instruction set is in the very first post.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
That is not manually rooting. It uses auto root (and has superfluous steps), which is silly for a nexus device.
This is how you root "manually":
http://forum.xda-developers.com/showthread.php?t=2536420
Sent from my Nexus 6 using Tapatalk 4
xdhall said:
That is not manually rooting. It uses auto root (and has superfluous steps), which is silly for a nexus device.
This is how you root "manually":
http://forum.xda-developers.com/showthread.php?t=2536420
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
DOH! I used the wrong link. I should have checked. Thanks for saving me!
Sent from my Nexus 7 using Tapatalk 4
thanks alot guys, just didnt wanna brick it on the day i got it :crying:
mockneygeeza said:
thanks alot guys, just didnt wanna brick it on the day i got it :crying:
Click to expand...
Click to collapse
Np.
Just holler if you have any questions.
Sent from my Nexus 6 using Tapatalk 4
mockneygeeza said:
thanks alot guys, just didnt wanna brick it on the day i got it :crying:
Click to expand...
Click to collapse
We're here to help, man. Try it manually and let us know if you run into any problems. It's basically impossible to hard brick a Nexus device. Almost anything can be recovered from.
Sent from my Nexus 7 using Tapatalk 4
I have used the wugfresh toolkit to root on latest firmware (KRT16S) and it works fine. Just select the "any build" option. Don't know about unlocking though, as my device was unlocked from 4.3
However, I do remember that I was able to unlock my 7 using the wugfresh toolkit BEFORE there was even an option for "nexus 7 2013" so it will probably work ?
Or you could do it the way everybody else here is saying, instead of the newb way ? (but I prefer the newb way)
dragonboydbboy said:
I have used the wugfresh toolkit to root on latest firmware (KRT16S) and it works fine. Just select the "any build" option. Don't know about unlocking though, as my device was unlocked from 4.3
However, I do remember that I was able to unlock my 7 using the wugfresh toolkit BEFORE there was even an option for "nexus 7 2013" so it will probably work ?
Or you could do it the way everybody else here is saying, instead of the newb way ? (but I prefer the newb way)
Click to expand...
Click to collapse
Toolkit was updated and supports latest kitkat, I prefer the easy way. Not that I wouldn't of tried the other method. I've rooted plenty... Just wanted the easy option. Took a while to sort out.. As I had just factory restored my laptop. Anyways that's for all ur help guys, all sorted here!
Wugfresh is what I used. Works flawlessly. Very fast an simple ?
Sent from my Nexus 7 using xda app-developers app
mockneygeeza said:
Toolkit was updated and supports latest kitkat, I prefer the easy way. Not that I wouldn't of tried the other method. I've rooted plenty... Just wanted the easy option. Took a while to sort out.. As I had just factory restored my laptop. Anyways that's for all ur help guys, all sorted here!
Click to expand...
Click to collapse
I really don't understand how a toolkit can be "the easy way" on a nexus device. Run two fastboot commands and press one button and you've done it manually. You never have to worry about someone else's code working or compatibility for future updates. And it's the same for any nexus device.
Sent from my Nexus 6 using Tapatalk 4
Well it's all good, I'm happy...the toolkit was coded by a legend.. Who I've donated too in the past.
Sent from my GT-I9505 using Xparent BlueTapatalk 2
Hi @ all
Does anybody knows a method to downgrade from the new bootloader aka KK 4.4.2 to JB 4.3?
The phone is rooted and a custom recovery is already installed.
I already tried this methods:
For the first only flash a custom 4.3 rom. Surprise no success After restore tried with an official fw by Odin without pitfile (anybody tried this?)
Surprise surprise no success.
Then I tried to unlock the bootloader cause I read that this one is locked. So I used adb with the following cmd lines:
Adb reboot - bootloader phone boots in dl mode
Then I typed fastboot OEM unlock and fastboot shows in cmd waiting for device. The phone driver are already installed in sdk, from official samsung USB driver and the Google adb USB driver. Phone where detected in adb but not in fastboot. U can check this if you type fastboot devices...
So this is what I tried. Does anybody have other solutions that we can try?
Does anyone know how to detect the device in fastboot?
Sry for bad English
Sent from my SM-N9005 using XDA Premium 4 mobile app
Mguttsche said:
Hi @ all
Does anybody knows a method to downgrade from the new bootloader aka KK 4.4.2 to JB 4.3?
The phone is rooted and a custom recovery is already installed.
I already tried this methods:
For the first only flash a custom 4.3 rom. Surprise no success After restore tried with an official fw by Odin without pitfile (anybody tried this?)
Surprise surprise no success.
Then I tried to unlock the bootloader cause I read that this one is locked. So I used adb with the following cmd lines:
Adb reboot - bootloader phone boots in dl mode
Then I typed fastboot OEM unlock and fastboot shows in cmd waiting for device. The phone driver are already installed in sdk, from official samsung USB driver and the Google adb USB driver. Phone where detected in adb but not in fastboot. U can check this if you type fastboot devices...
So this is what I tried. Does anybody have other solutions that we can try?
Does anyone know how to detect the device in fastboot?
Sry for bad English
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
wrong place
and no no downgrading
NO, for the 100th time.
Don't you people read? *sigh*.
I already read every post and everywhere the only answer no but nowhere I can read something about let us try this or that. Sorry for annoying you but if you don't want to try to get a solution for that you better not post.....
Sent from my SM-N9005 using XDA Premium 4 mobile app
It's already been stated hundreds of times that it is impossible to downgrade from 4.4 to 4.3 because the latest bootloader sticks the device to 4.4.
neo2006pf said:
It's already been stated hundreds of times that it is impossible to downgrade from 4.4 to 4.3 because the latest bootloader sticks the device to 4.4.
Click to expand...
Click to collapse
Exactly the same says everybody in the galaxy s2 Foren when 4.0 came out and they want to downgrade to any firmware befor this. It took a while but there was a solution found. So I asked here if anybody tried anything to test if we really stuck on 4.4.2.
Maybe there is a simple way to unlock bootloader and use the files from nexus 4. They got a solution for the downgrade procedure. They unlocked the bootloader and flashed by fastboot a file named flashall.bat. so they where able to flash fw befor 4.4.2. So you see it is possible to do it!!
Sent from my SM-N9005 using XDA Premium 4 mobile app
ok, do it then
Sent from my SM-N9005 using xda app-developers app
Oh man does anyone read the first post. I need a bit help with the fastboot driver. It does not detect the phone. That's why I asked for help not to become stupid reposts that it is not possible. I think no one of you tried to get a solution!
And when there came someone who asked for help nobody reads the op and get stuck on the first sentence. DONT POST ANYTHING IF YOU ARE NOT ABLE TO HELP. I KNOW THAT AT THE MOMENT THERE IS NO SOLUTION BUT LET US TRY TO FIND ONE!!!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Mguttsche said:
Oh man does anyone read the first post. I need a bit help with the fastboot driver. It does not detect the phone. That's why I asked for help not to become stupid reposts that it is not possible. I think no one of you tried to get a solution!
And when there came someone who asked for help nobody reads the op and get stuck on the first sentence. DONT POST ANYTHING IF YOU ARE NOT ABLE TO HELP. I KNOW THAT AT THE MOMENT THERE IS NO SOLUTION BUT LET US TRY TO FIND ONE!!!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did you enable USB debugging in settings? Might help a bit.
Sent from my SM-N9005 using Tapatalk
Yes sir already did that
Sent from my SM-N9005 using XDA Premium 4 mobile app
If your phone is rooted you can enable fastboot. There is a script in the dev section on how to enable fastboot. As for downgrading and playing with bootloaders. You will need to be very very careful, samsung bootloaders don't play nice and you can hard brick very easily.
Couldn't find it. Could you share a link?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Mguttsche said:
Couldn't find it. Could you share a link?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here you go
Can someone send me some links about the s2 stuff? Sounds interesting.