I know this question has been answered hundreds of times but I can't figure this out on my own. I used the stickies above and it still wont work
I went to flash MMuzy Rom and i flashed the ToroPlus instead of Toro and my Clockwork mod deleted my back up.
ADB Wont push to my phone for some reason either, a list of prompts comes up in the CMD promp.
Please please help
Thanks
did you wipe before flashing the rom?
syntax for adb
adb push c:\locationoffile\file.zip \sdcard\
Yes I did and i used that and nothing, I am trying to use the GNEX Tool but it is stuck on Waiting for Device
good god. not another toolkit user.
you need to install the correct drivers.
Zepius said:
good god. not another toolkit user.
you need to install the correct drivers.
Click to expand...
Click to collapse
I don't usually use the tool kit
I made a human mistake and flashed the wrong rom.
Zepius said:
good god. not another toolkit user.
you need to install the correct drivers.
Click to expand...
Click to collapse
didnt you hear?
every time someone uses the toolkit, an angel gets its wings....
using the toolkit will stop world hunger and provide world peace....
using the toolkit absolves anyone of needing ANY knowledge to actually troubleshoot or fix their device....
screenkeyx said:
I don't usually use the tool kit
I made a human mistake and flashed the wrong rom.
Click to expand...
Click to collapse
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
How can I use this when my phone won't actually boot? I am in clockwork mod and my phone wont pop up on my computer
screenkeyx said:
How can I use this when my phone won't actually boot? I am in clockwork mod and my phone wont pop up on my computer
Click to expand...
Click to collapse
did you even read it?
no you couldnt have since you didnt even read the part of using the bootloader (fastboot) to flash everything.
Zepius said:
did you even read it?
no you couldnt have since you didnt even read the part of using the bootloader (fastboot) to flash everything.
Click to expand...
Click to collapse
Sorry I am extremely stressed out of this and have skimmed it a lot due to people walking in and out of my office
Pirateghost said:
didnt you hear?
every time someone uses the toolkit, an angel gets its wings....
using the toolkit will stop world hunger and provide world peace....
using the toolkit absolves anyone of needing ANY knowledge to actually troubleshoot or fix their device....
Click to expand...
Click to collapse
I heard that if you enter "up up down down left right left right b a start select" into the toolkit it gives your phone infinite RAM.
Issue resolved.
I used the Gnex tool and restored with fast boot.
Thanks for the not funny joke
.....
Zepius said:
good god. not another toolkit user.
you need to install the correct drivers.
Click to expand...
Click to collapse
OMG he used a tool kit, he's so inferior. You might as well call him stupid...
cctoro said:
OMG he used a tool kit, he's so inferior. You might as well call him stupid...
Click to expand...
Click to collapse
Lazy or ignorant would be more accurate. Probably a bit of both.
cctoro said:
OMG he used a tool kit, he's so inferior. You might as well call him stupid...
Click to expand...
Click to collapse
and he learns nothing by using it so he cant even troubleshoot basic problems
Zepius said:
and he learns nothing by using it so he cant even troubleshoot basic problems
Click to expand...
Click to collapse
You know I always thought this community was a good spot to ask questions and get help.
Seems like you guys are no different than fanboys on an Iphone forum.
Have fun jerking your phones off in ADB settings and SDK
screenkeyx said:
You know I always thought this community was a good spot to ask questions and get help.
Seems like you guys are no different than fanboys on an Iphone forum.
Have fun jerking your phones off in ADB settings and SDK
Click to expand...
Click to collapse
Actually this is a developers website.
Not a support forum for making your device cool
Sent from my Nexus 7 using Tapatalk HD
screenkeyx said:
You know I always thought this community was a good spot to ask questions and get help.
Seems like you guys are no different than fanboys on an Iphone forum.
Have fun jerking your phones off in ADB settings and SDK
Click to expand...
Click to collapse
you know i always thought people who came to this site were willing to learn and better themselves with knowledge
seems like you (and most users now days) are no different. unwilling to learn and even accept answers given to you.
have fun relying on toolkits to get you out of trouble. you will receive no more help from me.
Related
I could use some help so I don't brick my phone. I have done a search or two on how to root this particular build and it's probably me - I don't think I have found any information to my question. On xda there was info on the superboot method from modaco that it only worked on ICS4.0.1. The GNex toolkit v7 does not have build IMM30d included. I purchased the phone from Google play and received it late last week. Is this build supported by any root method mentioned? Or will anyone link me to a method that supports the build?
My signature will get you running in a jiffy, sir.
Are you familiar with the toolkit at all?
dirtyreturn said:
Are you familiar with the toolkit at all?
Click to expand...
Click to collapse
for the love of all things good and holy... dont use the toolkit or you'll ask silly questions like this: http://forum.xda-developers.com/showthread.php?t=1747639
dirtyreturn said:
Are you familiar with the toolkit at all?
Click to expand...
Click to collapse
Don't use toolkits. It's not that there is anything inherently bad with them, but having a program do everything for you without understanding how it is doing it means that you don't know how to fix anything if something goes wrong. It's better to do things manually and learn how everything works before taking the easy way through it.
Haha, alright. This is in the Q&A section and I'm sure as hell no developer. I'm coming from a mytouch4g. Had to use adb to downgrade from gingerbread to froyo to root it. Even after reading it over a couple times the directions were still intimidating. It looked like an easy option. Appreciate the input though.
I'll reiterate what others said...
You'll want to know that adb and fastboot are set up correctly, anyway.
They're EXTREMELY useful in countless situations.
I promise you that it'll be an easy process.
Jubakuba said:
I'll reiterate what others said...
You'll want to know that adb and fastboot are set up correctly, anyway.
They're EXTREMELY useful in countless situations.
I promise you that it'll be an easy process.
Click to expand...
Click to collapse
Appreciate the link/input you posted. I'll follow it correctly I hope as it doesn't appear to be rocket science.
Zepius said:
for the love of all things good and holy... dont use the toolkit or you'll ask silly questions like this: http://forum.xda-developers.com/showthread.php?t=1747639
Click to expand...
Click to collapse
hey thanks for rating this one star. :good:
dirtyreturn said:
hey thanks for rating this one star. :good:
Click to expand...
Click to collapse
wasnt me that did that. i dont rate threads.
dirtyreturn said:
hey thanks for rating this one star. :good:
Click to expand...
Click to collapse
Might not have been him...
There's someone(s) bum-rushing the forum today and rating everything 1*.
Jubakuba said:
Might not have been him...
There's someone(s) bum-rushing the forum today and rating everything 1*.
Click to expand...
Click to collapse
Zepius said:
wasnt me that did that. i dont rate threads.
Click to expand...
Click to collapse
HA. sorry. if you are still willing to help real quick... the command 'adb reboot bootloader' brought up a bubble installing device driver.. android 1.0.. failed to install driver. I had already had the drivers installed. Idea?
Most likely, if you connect you device to Wi-Fi, it will receive an OTA update -- I think IMM76 (blanking on build number).
dirtyreturn said:
HA. sorry. if you are still willing to help real quick... the command 'adb reboot bootloader' brought up a bubble installing device driver.. android 1.0.. failed to install driver. I had already had the drivers installed. Idea?
Click to expand...
Click to collapse
The driver needs to install TWICE: once when your device is booted normally, and once when booted into the bootloader.
I'm having a problem using juba's rooting method. It won't go into recovery mode. I'm using the same android and build as the fellow poster. Any help? It's just sticking on the google word with the unlock thing at the bottom when I try to reboot into recovery from the bootloader.
Hold down vol+ and vol- and turn the phone on. When the menu comes up, select recovery.
I seem to be stuck on the CyanogenMod Boot Screen. It continually keeps displaying it. How would I fix this? Let me know if you need more details.
Your post is bad and you should feel bad
tom yoyo said:
I seem to be stuck on the CyanogenMod Boot Screen. It continually keeps displaying it. How would I fix this? Let me know if you need more details.
Click to expand...
Click to collapse
Please include more information, I told you to add more, including your model number, etc.
You're the stupidest kid
EdwinForTheWin said:
Please include more information, I told you to add more, including your model number, etc.
You're the stupidest kid
Click to expand...
Click to collapse
Please keep this attitude away, we on the Q&A forums are here to help, if you feel that you can't help him, don't post.
@TS
Did you do a factory reset in a custom recovery?
tom yoyo said:
I seem to be stuck on the CyanogenMod Boot Screen. It continually keeps displaying it. How would I fix this? Let me know if you need more details.
Click to expand...
Click to collapse
Assuming you have a custom recovery, you could try the following:
- boot into recovery
- push a rom (for instance: the CM version you have installed) to your /sdcard/ using adb
- flash it
If you have the toolkit install (found in the dev sec.) its gonna be a breeze to flash another rom or the stock nexus image
irizwan said:
If you have the toolkit install (found in the dev sec.) its gonna be a breeze to flash another rom or the stock nexus image
Click to expand...
Click to collapse
No idea why they stuck the toolkit on the dev section, it's nothing related to dev.........
And stop using the toolkit, at least learn how it works:
http://forum.xda-developers.com/showthread.php?t=1812959
Mach3.2 said:
No idea why they stuck the toolkit on the dev section, it's nothing related to dev.........
And stop using the toolkit, at least learn how it works:
http://forum.xda-developers.com/showthread.php?t=1812959
Click to expand...
Click to collapse
Just because i recommended the toolkit to a new user cause itll be easier for him doesnt mean i dont know how it all works thanks for the link btw very informative
irizwan said:
Just because i recommended the toolkit to a new user cause itll be easier for him doesnt mean i dont know how it all works thanks for the link btw very informative
Click to expand...
Click to collapse
Purpose of me recommending him doing it manually is so that he won't make more threads like this.
Beamed from my Maguro.
EdwinForTheWin said:
Please include more information, I told you to add more, including your model number, etc.
You're the stupidest kid
Click to expand...
Click to collapse
Why would he need the model number to fix this problem? The same methods will fix this whether he is on GSM or CDMA Nexus. Apparently you're the stupid one.
So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
jahames said:
So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
Click to expand...
Click to collapse
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart
StuMcBill said:
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart
Click to expand...
Click to collapse
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
jahames said:
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
Click to expand...
Click to collapse
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?
StuMcBill said:
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?
Click to expand...
Click to collapse
Was working with the 4.4.2 image. Going to give the 4.4 a shot now
Same thing with 4.4...still stuck with the flo bootloader
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
jahames said:
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
Click to expand...
Click to collapse
You flashed a recovery for flo. Flash one for deb.
Edit:
http://techerrata.com/browse/twrp2/deb
Reasonably sure I had a deb recovery, but apparently redownloading and reflashing the CWM image did the trick. Thanks!
if you ever have problems try nexus root toolkit. It works wonders if you ever severely mess up any nexus device.
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
same issue
Richieboy67 said:
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
It is here
http://www.wugfresh.com/
It is a toolkit that makes these things very easy. I have used this many times and have never had any issues with it.
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
LinearEquation said:
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Richieboy67 said:
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Click to expand...
Click to collapse
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
LinearEquation said:
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
Click to expand...
Click to collapse
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Richieboy67 said:
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Click to expand...
Click to collapse
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
LinearEquation said:
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
Click to expand...
Click to collapse
While not disastrous, I kind of know what you mean, I started with Wug's (and it is a great toolkit), but once I flashed my own kernel (I used francos app to autoflash so did not have to use recovery or fastboot), I did not realize that by using Wug's a week later that it would flash over that kernel to run those commands and NOT replace francos (I found I was back on stock), lucky by then I had learned enough to recover and no damage was done, but it does point out that my reliance had caused me more work and a bit of worry in the long run.
Still Wug's NRT is a great toolkit...but it should be used as a tool, not a replacement for knowing what to do without it.
Hi everyone.
I have a samsung galaxy S2, I tried to upgrade the Rom, but made mistake, now it boots up and stuck at "teamwin" logo. Would anyone please help: how to fix this. I appreciated for your help.
Joe
Hmm, if I'm correct and since you don't seem to be such an expert. You may have to use adb or some other android debugger to flash it from the computer. Better get searching on how to do that because I'm not going to explain how.
Using CM12.1 on my SGH-T999
aaaall2006 said:
Hi everyone.
I have a samsung galaxy S2, I tried to upgrade the Rom, but made mistake, now it boots up and stuck at "teamwin" logo. Would anyone please help: how to fix this. I appreciated for your help.
Joe
Click to expand...
Click to collapse
AlienDrew said:
Hmm, if I'm correct and since you don't seem to be such an expert. You may have to use adb or some other android debugger to flash it from the computer. Better get searching on how to do that because I'm not going to explain how.
Using CM12.1 on my SGH-T999
Click to expand...
Click to collapse
wow dude... were you ticked about something when you posted this? he was just asking for help man....
it sounds like your recovery got messed up. download the .img file for your phone, put it on download mode, flash the img in odin, reboot to recovery, reflash your rom. shouldnt be too bad to fix. Old thread i know, but i was just walking down the t-mob S2 memory land and saw this impolite response to a valid question
youdoofus said:
wow dude... were you ticked about something when you posted this?
Click to expand...
Click to collapse
No, I wasn't "ticked". I was just trying to be a bit sarcastic... is that a crime?
AlienDrew said:
No, I wasn't "ticked". I was just trying to be a bit sarcastic... is that a crime?
Click to expand...
Click to collapse
This is a forum dedicated to helping it's fellow members. Be helpful or gtfo
youdoofus said:
This is a forum dedicated to helping it's fellow members. Be helpful or gtfo
Click to expand...
Click to collapse
You can still be helpful even if you are sarcastic, take House on the TV series as an example.
Agreed, but if help isnt included with the sarcasm when someone asks an actual question, then don't bother posting
Sent from my unknown using XDA Free mobile app
Is there a way to root without PC. I googled it but what I found was almost a year old so I wasn't sure if anything has changed.
UnicornHub said:
Is there a way to root without PC. I googled it but what I found was almost a year old so I wasn't sure if anything has changed.
Click to expand...
Click to collapse
Nope. You need a pc to unlock the bootloader so you can then root your device. Sorry man.
Badger50 said:
Nope. You need a pc to unlock the bootloader so you can then root your device. Sorry man.
Click to expand...
Click to collapse
Dang ok. I saw the all in one toolbox's are those stable and do they work well? If not what's the best easiest root method
UnicornHub said:
Dang ok. I saw the all in one toolbox's are those stable and do they work well? If not what's the best easiest root method
Click to expand...
Click to collapse
I've never used a toolkit. I prefer the manual method with my pc and fastboot commands. Here's a great guide to help you on your way :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Yes knowing how to do it manually is the best way typically I've tried a few all in ones and some reason usually have issues also some make it too easy to mess it up if I don't know what you are doing and hey inpatient
Sent from my Pixel 2 XL using Tapatalk
gjkrisa said:
Yes knowing how to do it manually is the best way typically I've tried a few all in ones and some reason usually have issues also some make it too easy to mess it up if I don't know what you are doing and hey inpatient
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I'm pretty sure that even with one click root methods, you'll still need an unlocked bootloader.
Yeah true
xunholyx said:
I'm pretty sure that even with one click root methods, you'll still need an unlocked bootloader.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
Don't rely on the "AIO" Toolkits or the "One Click Root" Toolkits. I do appreciate the developers' effort they put in these toolkits to make people's life easier however many times they are outdated and don't work as they should and are just causing headache. Use Fastboot and ADB and nothing can go wrong! If something does, well... There are so many extremely nice people here who are willing to help you out, answer your questions and bring your phone back to life! Khm... @Badger50 just to mention one! Khm...
True, with oneclick root you must still have an unlocked bootloader otherwise i won't work.