NOTE: I DO NOT HAVE WINDOWS, AT THE MOMENT! THE DEVELOPEMENT HAS STOPPED TEMPORARILY!! I'M SORRY FOR THIS!
Welcome to the original thread, of Beatsleigher's Root Helper!!
This program is completely free, with no Xtra options for donators...
What this program will do:Well this program is designed for beginners, and advanced users.
Beginners, can learn, about flashing. And learn, what to do, to get a custom ROM running...
Advanced users & pros, have a few more options, they can flash their ROMs, even some advanced options, like RadioOptions (If you know, what that is).
If you need to setup ADB drivers, then follow the steps, in the ADB -> Help menu!!
List of features:Several Reboot options,
Backup/Restore
Unlock bootloader (fastboot)
Relock bootloader (fastboot)
Root (ADB+fastboot)
Flash recovery (fastboot)
All-in-one solutions (Some new ones, again ^^)
Using a complete GUI!
Very explicit detailing of what the program is currently doing!
Install drivers - (USB + ADB/fastboot drivers)
List of ROMs/kernels
Help menus
Install apps, as user apps.
Install apps, as system apps.
Push files, to SD.
Flash ROMs.
Flash stock ROM.
Context menus!!
And much, much more!
What's to expect:In-program E-Mail subscription, to get notified about updates.
User experience program…
More updates
Requirements::[/CENTER]
This program requires following, to run:
.net framework +Ver. 3.5 (SP1)
.net framework 3.5 Client Profile
.net framework 4.0 Client Profile
Windows Installer ver. 3.1 & 4.5
It uses just over 30 MB of RAM (Excluding the scripts) on average.
CPU usage is at 5% at the moment
If RAM usage goes over 90%, the program WILL shut down... (Not the computer)
ADB is the ONLY background process, used by BRH (The only 3rd party process)
FAQ:Q:When installing the drivers, why do I need to change my system configuration?
A:You need to configure your machine, to notice the device, but to leave it alone, instead of looking for, and downloading drivers for it. This just confuses the computer, meaning you can't do anything in the bootloader, because Windows Update doesn't yet have the needed drivers...
Q: Why have you gone over to making a GUI? The batch files, were just fine...
A: I'm going over to making a GUI, because it is easier to use, less work. And I have the option, to just, drag & drop a button, write two lines of code, to make the button functional and then it's just a matter of creating the batch file, converting it to an EXE. Easy as pie. Whereas, with the batch files, to create one more option, you have to write 6 lines of code, then the batch file, and then half of the stuff doesn't work properly, because you didn't debug... If you know, what I mean...
Q: Why are there so many files???
A: This program needs so many files, so it can perform different processes/options/tasks
. But it isn't hard, to find out, what file, does which job
Q: Why is there only a version for windows??
A: I am working on a version, for Mac users, but it will take some time. I'm glad to be nearly finished, with the Windows version
Q: I want to donate to you, but you won't allow it. Why?
A: I don't accept any donations, because I only wrote the program to flash files on to your phone... I don't want to take credit for things, that other people did.
Instead of trying to donate to me, donate to chainfire, ChainsDD, and Kousik Dutta; for creating such brilliant recoverys, Apps (like superuser and ROM Manager) and ROMs...
BTW: If you really want to donate (which you won't ), you can send me some albums ^^ I need house music, to work.. And all my songs/albums have been listened dead -.-
Q: Do you mind if I use this program for commercial use, and post videos(tutorials) on Youtube?
A: As long as you DO NOT create mirrors, and let me know, I'm not that fussed... But then please post the link of the video to me, so that I can tell you if I like the way you did it, or not.
Q: When are you gonna stop talking about things, that don't interrest anyone (the FAQ)??
A: Now, but still thx for reading, other good questions will be posted here, aswell...
Thanks:Many thanks to Kouschik Dutta for creating the recoveries for near-to all Android phones. Yo the man!
And not to forget the awsome app: ROM Manager ^^
Thanks to my good friend Accendare (baddinski), for creating the splashscreen. I appreciate it much
Thanks to Google, for creating the AOSP, for the great developers, to create even greater ROMs, for us!
Also, thanks to Google, for buying Android, and making suh a (rather) bug-free OS!!
If I forgot anyone, please let me know immediatly!!
Downloads:
If you want to flash stock firmware, you will need to install this. This contains all the neccessary files/folders you need:
GSM: to be downloaded, by clicking this...
CDMA: to be downloaded here...
Current version (From the 28.03.2012 02:58 GMT +!) is 2.6.5.5.
There are some new and juicy features, that have come in this update. Especially, for those fellow developers So, give this a try, if you're not too busy ^^ Download here
Before updating, please run this...
Fulll release!! Version 3.0.0.8!!
It's an ISO image. I'll provide a link, to power ISO, should you not have an Image-mounting software, on your computer… If you have Windows 8 CP, you do NOT Need this…
Well, I hope, you will enjoy this new version!!
Download: Beatslei9gher's Root Helper_Install_CD Power ISO 5
Screenshots:View attachment 928851 View attachment 928852View attachment 966857 View attachment 966858
View attachment 966859 View attachment 966860
View attachment 966861 View attachment 966862
View attachment 966863 View attachment 966864
View attachment 966865 View attachment 966866
View attachment 966867 View attachment 966868
View attachment 966871 View attachment 966872
View attachment 966873 View attachment 966874
View attachment 966876
If you want to see more, download it
Installer:The installer will install to your C:\ drive. Some older scripts, are still working with "%homedrive%" so, to make sure, that everything is working, please make sure, that your homedrive is your C:\ drive. Or, if you have a seperate C:\ drive (like me), copy a copy, of the "Beatsleigher_root_helper" folder, to your homedrive. Then it should do the trick. By the tiome, the program is released properly (full) all scripts should be working with "C:\".
Should you have NOT got a C:\ drive, because your homedrive is named differently/you deleted the C:\ partition, see: installation help.
Requests:If you have any requestes (features, etc.), please PM me, or send me an E-Mail!!
Please read!!:
Befor moaning, that there are not enough ROMs/kernels, remember, since 2.6D ALPHA, you can flash both kernels & ROMs via ADB & fastboot!
Download, and see for yourself
Changelog:
Verison 3.0.0.8 (Full release):
All scripts were re-written...
A few changes...
Full release(!!!)
Version 2.6.5.7 (BETA) [Minor 3]
Working context menus!! (On selected forms)
And that was really about it.
Version 2.6.5.5 (BETA) [Minor 2]:
Added some juicy developer features! (Using the ADB shell)
A few options, for n00bs, are in there, aswell...
Added options, to the ADB menu.
Added a complete new form. (Dev. options)
Added a few more scripts. Making the update zise about 6MB, on your HDD
Removed some buggy code.
When navigating, from ADB menu to Dev. Menu, ADB menu closes, but can be re-opened from the "File" menu.
Dev. menu has also got CPU/RAM usage detector!
Download, for more changelog
Version 2.6.5.4 (BETA) [Minor]:
Working progressbars(!!!)
Added CPU/RAM usage detection.
ADB menu has got a makeover.
Added option to enable/disable CPU/RAM usage detection in fastboot menu...
Fixed bug in ADB help menu.
Cleansed the code (again)
I probably forgot the rest, or just find out, for yourself
Version 2.6.5.3 (BETA):
Removed bug that caused phone crash, whilst prompting device name.
Cleansed the code.
Removed two un-used forms.
Repaired the menustripbutton.
Added scripts, to update package.
Removed other scripts, from update package.
Compressed some, of the files (drivers, executables)
Using traditional installer, again.
Installation path set to: C:\Beatsleigher_root_helper\
Version 2.6.5.2 (BETA):
Fastboot menu fully working.
Fastboot help menu, is popping up/has been created, though it has no content.
ADB help menu is working/all buttons have a task.
Some unneeded code has been removed.
A complete list of ROMs & kernels is present (CDMA + GSM).
No change in the IE engine...
All messages giving a tone/sound.
Options have ben added to the ADB menu.
New all-in-one solutions for ADB menu.
Scripts have been edited, for more friendliness
More tooltips.
Progressbars still not working ( )
Maximization has been disabled in ALL windows.
Better usage of RAM, whilst opening other exe - files
Version 2.6.5.1 (BETA)
Added update check-support.
Changed file hoster to mediafire (updates coming from there)
Added ADB reboot options.
Fastboot reboot options working.
Added (hidden) features.
Using a proper installer.
Can be installed anywhere on HDD, will work anyway
Two packages are to be downloaded, not one. This ensures, that updates are working, as planned.
(Hidden features will be released, when version is 2.6.5.3 (next update) )
Version: 2.6 D:
Everything you see, down the bottom is working.
You can now flash a recovery via fastboot menu!!
Kernel and ROMs, I have decided, to take them back out. They were a bit buggy...
The size of the EXE itself, has gone up to, ca. 2.4 MB.
Option to flash stock ROM (LTE + GSM) has been enabled, for fastboot.
Looks a bit more friendly
Icons have been added!
You'll have to find the rest out, yourself
Version 2.6C:
ADB menu has been carried on. You are now able to flash a kernel (LTE & GSM)
It will open the Explorer for you, when you need to copy the file!!
LTE menu is finally working!! It had problems opening, due to a minor type-error.
Though the LTE menu is working, you will only be able to use one button, in about an hour. Once I've completed doing the ADB menu...
(See: "What's to expect", for more info's on what's coming!!)
Version 2.6:
New GUI!
Complete new code.
In-program help.
Direct link to thread.
Seperate fastboot and ADB menus!
More explicit details...
Removed the music, that pops up, upon start. (To many house haters )
All batch files converted to executables... (This prevents tampering with the code)
Fully compatible with 64x machines. Doesn't use as much RAM, but therefore shows up as a process.
Installation help:
Not much can go wrong, when install9ing this program.
Mostly, the reasons, of failure, to use this program, are due to:
Not having a C:\ drive.
Not copying a copy of the root folder, to hamedrive, if C:\ is not the homedrive, of your windows machine.
Tutorial 1:
Problem: I installed the program, but my homedrive is not C:\. I installed to C:\, but I can't use half of the program.
Well, first of all; sorry, for this. I could of said this earlier... I forgot to edit the scripts, to use ONLY the C:\ drive, so it useshalf the C:\ drive, and half your homedrive. But, that's why I posted this tutorial.
It's quick & easy ^^
Tutorial:
Install the program, to your C:\ drive. Close the installer, and re-open it.
Once back in the installer, set the installation path to your homedrive (Where Windows is installed).
Install to that directory, and done
It should now work ^_^
Tutorial 2:
Problem, I don't have a C:\ drive, and the ROM-Full/Less version, isn't available for download... What to do??
This is also no problem!! With a few, simple clicks of your mouse, we will fix this minor problem
Tutorial:
Type following key-combination, on your keyboard; START(WIN)+R.
The "Run" prompt should now pop up.
In the RUN prompt, type: "diskmgmt.msc" and it enter.
Once the disk manager pops up, shrink your homedrive(or, if you have unalocated disk space, which is 3GB or more, right click on that)
Shrink your homedrive, about 3GB. If you can, allocate more space, because you will need quite some space, because of stock ROMs/custom ROMs/kernels and backups.
To shrink, right-click on the partition and select "Shrink Volume". Enter this amount, to shrink: 3072 MB, that should be 3GB. Like I said, feel free to allocate more space.
Now you should see a black field. This is unallocated disk space. Right click on this space and select" Create simple partition" Make sure, you create the exact space, you shrunk, other wise, you will have some unallocated space, on your HDD and this can cause problems, if unnoticed.
Name the partition : C:. Wait, for the Diskman. to create the partition (can take up to 5 Minutes, for that amount of space, depending on size of HDD, CPU clock speed and amount of RAM).
Now, just install Beatsleigher's Root Helper to your C:\ drive and again, to your homedrive. Done! You can now use Beatsleigher's Root Helper.
If you should notice any other problems, please let me know, so I can solve them.
EULA:Please read the EULA, should you not have, during installation. Or, you are interested in installing the prgram.
There is vital information, in this text document!
Some misc. text
Hmm... I'm at the end of my stream of thoughts...
Now, I'm asking YOU!
Please tell me, what would you like me, to add to this program.
Don't forget, if you like this program, and you are happy, to recommend it. Don't be shy, post your thanks, and a comment or two. Hit the thanks button. Even if you are dissatisfied, just post a comment, and I'll try and do it better.
If you are a junior member, send me a PM, and I'll post it for you
I'll ask again;
I know, I'm not that well known, and I know, I've done mistakes (ROM-Full version)
But, I'm trying to make this program, a better enviroment, for everybody. Please, would you give it at least a try, instead of just ignoring this...
NOTE: Short term for: Beatslleigher's Root Helper: "BRH"!!
To prevent confusion, in future!
Well, I mentioned there will be a working version on Linux, right? Well, I only just found out a few days ago, that you can use wine to emulate Windows... :O Well, there you are! It works pretty much fine, but then a agin, there will be a few bugs, so I'll get on to that...
Sorry for not updating this thread, for such a long time... I'm using UBuntu, and I've got quite a lott to do, as the schoolyear is coming to it's end
News, tips & tricks!!
News:
IMPORTANT:
Verizon has just released their version, of the GNex...
Beatsleigher's Root Helper, will be one of the first, to provide their images, for recovery... Other than that, everything will be the same!! I'm updating the files, right now!!!
New concept:Beatsleigher's Root Helper, is written and hosted by one person: me. I have been working hard, and have noticed, that I need to change the concept. Instead of being big, and cluttery. It is now small and efficient. Like a car manufacturer, I am working hard, on producing a very small, but powerfull piece of technology (in this case, virtual technology). And, instead of relying on the user, to type everything, this new version, needs only a few clicks of a button. As an example, the first version, which used a lot of RAM, and waisted processes, used up (with all ROMs/kernels/bootanims) over 1 GB. Now, you can download the ROMs, you wish and kernels, and just flash them, with the click of a button. The best thing is, all of the data, I provide version 2.xx with, the size comes out, at a maximum of 300-350 MB of disk space. (Counting both CDMA & GSM stock ROMs).
Beta has been released!!:After a few weeks of hard work, I can finally say: "I'm almost done!"
It took 4 weeks, 3 Albums, 5 DVDs, 5 Gigs of HDD space, and lot's of testing.
But now, It's nearly done, and I'm proud of it.
This project will NEVER be abandoned. (Unless the GNex gets boring, at some point in time)
It brings a lot of new features with it, including working help menus.
This is also a new part, of the concept, keep it in BETA, untill EVERYTHING works. Of course, I will keep it updated and will constantly change it, to make it better, and easier to use.
If you like it, you may also advertise!! (Just a tip. I also have competition...)
Askng for help?!:Yes, I'm asking you, for help.
After all my hard work. It seems, noone is downloading it...
That's why, I need you, to post requests, and suggest things
I think, it's important, for me to know, what YOU really want, in this program.
Don't be shy, just post your opinion, and suggest someti=hing, to make it better
And if this, doesn't help, I will probably close this thread, and leave this program, as it is, and start other projects, for other phone's, like: HTC devices.
I shall then declare this program as final. This is not giving up, it's you not giving it a chance... But anyways, back to the point: I need you, to tell me your oppinion!!!
Google has done it again!:
After some time, on 4.0.2 (Stock), Google has released the stock version, of 4.0.4, for it's flagship devices (Motorola Xoom WiFi, for some reason, aswell..)
I am currently downloading the factory image, and will be creating an installer, so you can enjoy the joys, of 4.0.4!
So, again, another thing, to look forward to, when using this program!!
Windows metro style app!:After the nearly complete nervous breakdown, of my computer, I have decided, to install Windows 8 Cons. preview.
Whilst installing the new OS, I was downloading the SDK, VS 2011, and decided, because Windows 8 will be available, next month, I shall start creating this program, also as a Metro-styled app.
I, however, have decided, to keep the style secret, and keep on developing, and as soon, as Windows 8 is officially released, I shall also release the new program. If, however, you are lucky, I will have enough time, to work on this new project, and release it in a week, or so
But, as I said it depends, on whether, this program get's downloaded a bit more, or not, and if I am quick enough, on deving this...
Having trouble, with Wndows 8?Well, I have found a solution, to all your ADB/fastboot problems...
Interested? Click here...
The thread contains all info, you need, to install and configure the ADB drivers, on Windows 8...
If you have a problem, please let me know, by either: Answering the thread, sending me a PM, or post your problem here...
New cooperation!!: Because so many of you, are wanting more kernels and ROMs, I have decided, to cooperate, with sonicxml This means, there will be an option, for you, to flash his kernel img, via fastboot. This means, there is one less step, in the al-in-one procedure!!
So, I'm thanking him, for accepting my request
CDMA issues I've come to notice, that some people, are having issues, with their CDMA devices...
This will be fixed, in the next update, release will be, in a few days. I'm very sorry, that this has happened, whilst testing, I didn't have any problems, what so ever...
But, because I guaranteed you, that I will fix ANY and EVERY bug, that you/I can find, I've already started, on a new and better flasher, for 4.0.2 stock flashers...
These will be hosted on my FTP server, in future, so the program can download the files, itself... So that shouldn't be a problem.
Should you have any more problems, please let me know, IMMEDIATLY, because, there is no point, in me updating, uploading the files, and literally half an hour, after release, someone tells me, that they're having problems, for a few days...
So, please. Tell me, I'm always happy to help. That's what I'm here for
Info's on updates...
All-in-one fix: Well, it looks like I've managed to fix the all-in-one problem... It seems, that there was an error, whilst in recovery. Added the feature; it flashes an insecure boot image... This allows the recovery, to stay put, and it grants the ADB remount access... This means, you are as close to stock, as possible, but you are fully rooted...
You shouldn't trust Windows. Period. I dont really get why you say scripting is harder on Linux though.
Batch files are nice, allows one to see what will be done. I would prefer them over a binary, but then again, I dont use Windows.
May the force be with you.
bk
bk201doesntexist said:
You shouldn't trust Windows. Period. I dont really get why you say scripting is harder on Linux though.
Batch files are nice, allows one to see what will be done. I would prefer them over a binary, but then again, I dont use Windows.
May the force be with you.
bk
Click to expand...
Click to collapse
Thx for the force
I said it's harder scripting for Linux, because I'm a noob, when it comes to Linux/Unix... I only just found out, that Linux has the drivers for my laptop a few days ago And I'm used to Windows, that's why I said it.
Is it possible to provide a version without rom to have a good size? 400Mb is big.
Thanks for the time you spent in this project
imfloflo said:
Is it possible to provide a version without rom to have a good size? 400Mb is big.
Thanks for the time you spent in this project
Click to expand...
Click to collapse
Currently working on it I'm just removing some scripts
To all size lovers!
The size has gone down, to under 60 MB.
I'm trying, to keep it under 80MB...
Thanks, for using Beatsleigher's Root Helper!!
Facebook page now open!!
Hey guys, I've created a FB page, for Q&A as well as the Q&A Thread, in the Q&A section (thx imfloflo)
There are also a few other things, which might interest you! So give it a looksee, it's not done yet, it will also take a while, because I'm busy with school and my root helper...
But, here's the link^^ Beatsleigher's Facebook page!
Info on 2.6 ALPHA (GUI version)
Please read!
This builds are only alphas. As most of you know, alphas are very buggy... I'm doing my best, on keeping them bug-free, so please don't complain about them not working properly... Some menus also haven't been taken care of, I know. If you are looking for the version, that works best (at the moment), take/download the ROM-Less 1.2.7 version.
Why did I jump from 1.2.x to 2.6?
There have been many unreleased version, during the batch period. Well, they weren't unreleased as that, they weremore or less kept for private use, because it was too big, to upload/for you to download. So I kept it on my HDD & USB flash drive.
Info on 2.6B ALPHA
ABTextBox1.Visible = FalsDB menu working properly. All buttons have got their purpose. All linken with an "OpenFileDialog" so you can flash like that. You just choose the file you want, open it and click on "push". The same goes for ROMs. Fastboot menu is planned to work in 2.6C or D.
BTW; have you noticed, that the size of everything has shrunk, again? Well, guess what, it will start to rise, soon. Why? The program you asked for is nearly 2 MB :O
Well, I hope you had fun reading, and I also hope, you know, why the updates are taking so long
Ok, the beta will be delayed, again.
I'm currently busy, and not near home...
I'm currently writing a EULA. So, please read it. It will prevent lots of miss understandings... It's not drastically big, nor hard to understand. It will be uploaded, as a txt file, and provided in the next update package. ...
I guess, the update will be released at about 18:00 o'clock GMT +1.
Who care's how I sent IT?
Hey familyguy59!
Thanks for pointing me to your thread, I've installed the helper...I've selected all in one, unlocked and booted the phone in to CWM recovery - the one screen instruction is saying to apply the zip? I think ive missed a step - I'm not sure what zip! I haven't copied one across to the phone!
Any help would be great.
My goal is to flash 4.04 (stock) to the phone.
I have superuser on the phone now...(so it must be rooted right?)
Sorry for my lack of knowledge!
HSKalay said:
Hey familyguy59!
Thanks for pointing me to your thread, I've installed the helper...I've selected all in one, unlocked and booted the phone in to CWM recovery - the one screen instruction is saying to apply the zip? I think ive missed a step - I'm not sure what zip! I haven't copied one across to the phone!
Any help would be great.
My goal is to flash 4.04 (stock) to the phone.
I have superuser on the phone now...(so it must be rooted right?)
Sorry for my lack of knowledge!
Click to expand...
Click to collapse
Well, once you have entered the CWM recovery-program, you should see an option, named: "install zip from sdcard". Once there select: "choose zip from sdcard", and on the SD, you should notice a zip called "su". Install that. That's what's ment with "Apply zip"
But, as you have got superuser, you should have done everything right .
And, it's no problem, your lack of knowledge I'm happy to help everyone, who asks. Should you not have root (no superuser prompts), use the other all-in-one option That should then do the trick.
Now, to installing stock 4.0.4. You can download the zip, and then install via ROM Manager, it should also be present, on your device.
Make sure, though, to create a backup.
Thanks for using Beatsleigher's Root Helper It's very much appreciated
familyguy59 said:
Well, once you have entered the CWM recovery-program, you should see an option, named: "install zip from sdcard". Once there select: "choose zip from sdcard", and on the SD, you should notice a zip called "su". Install that. That's what's ment with "Apply zip"
But, as you have got superuser, you should have done everything right .
And, it's no problem, your lack of knowledge I'm happy to help everyone, who asks. Should you not have root (no superuser prompts), use the other all-in-one option That should then do the trick.
Now, to installing stock 4.0.4. You can download the zip, and then install via ROM Manager, it should also be present, on your device.
Make sure, though, to create a backup.
Thanks for using Beatsleigher's Root Helper It's very much appreciated
Click to expand...
Click to collapse
Thanks for the swift reply!
Is there any way for me to get back in to clockwork (the touch recovery) via the phone alone? When I've tried it (vol up + down + pwr) then recovery...it seems to be the stock one (droid lying down, with red triangle)
I'm installing rom manager now though!
HSKalay said:
Thanks for the swift reply!
Is there any way for me to get back in to clockwork (the touch recovery) via the phone alone? When I've tried it (vol up + down + pwr) then recovery...it seems to be the stock one (droid lying down, with red triangle)
I'm installing rom manager now though!
Click to expand...
Click to collapse
Hmm... It seems, you didn't flash via ROM Manager, or worse, it didn't install onto your phone. I'll get onto that, as soon, as I've got my computer up and running again (The one I'm currenly using, is not mine...).
Well, as soon, as you have flashed via CWM, just choose "Flash recovery" from the fastboot menu, this should then give you the Touch-enabled version.
As I said; once the recovery has been flashed, via CWM, you should be able to access it, by the app, and using VOL UP+DWN and PWR...
No prob, by the way. I always try to reply ASAP.
HSKalay said:
Hey familyguy59!
Thanks for pointing me to your thread, I've installed the helper...I've selected all in one, unlocked and booted the phone in to CWM recovery - the one screen instruction is saying to apply the zip? I think ive missed a step - I'm not sure what zip! I haven't copied one across to the phone!
Any help would be great.
My goal is to flash 4.04 (stock) to the phone.
I have superuser on the phone now...(so it must be rooted right?)
Sorry for my lack of knowledge!
Click to expand...
Click to collapse
Oh, yes. I forgot to mention: The program pushes the zip file automaticly, to your SD, to make the whole process, as comfortable, as possible
familyguy59 said:
Hmm... It seems, you didn't flash via ROM Manager, or worse, it didn't install onto your phone. I'll get onto that, as soon, as I've got my computer up and running again (The one I'm currenly using, is not mine...).
Well, as soon, as you have flashed via CWM, just choose "Flash recovery" from the fastboot menu, this should then give you the Touch-enabled version.
As I said; once the recovery has been flashed, via CWM, you should be able to access it, by the app, and using VOL UP+DWN and PWR...
No prob, by the way. I always try to reply ASAP.
Click to expand...
Click to collapse
It's weird because, I have flashed CWM via the app on the phone, and the flashed the touch version...but still doesn't show up when I manually get in to recovery. But via the app it enters the touch recovery.
sorry, your thread is going a little off topic now!
HSKalay said:
It's weird because, I have flashed CWM via the app on the phone, and the flashed the touch version...but still doesn't show up when I manually get in to recovery. But via the app it enters the touch recovery.
sorry, your thread is going a little off topic now!
Click to expand...
Click to collapse
Yes, that is indeed strange. It could however just be a bug.
If you want to try, you could flash the recovery via BRH, and see if there's a difference.
familyguy59 said:
Yes, that is indeed strange. It could however just be a bug.
If you want to try, you could flash the recovery via BRH, and see if there's a difference.
Click to expand...
Click to collapse
BRH...sorry what is that?
HSKalay said:
BRH...sorry what is that?
Click to expand...
Click to collapse
Short term, for: Beatsleigher's Root Helper
familyguy59 said:
Short term, for: Beatsleigher's Root Helper
Click to expand...
Click to collapse
ha, I should of known that
You wouldn't happen to have a link handy, to the cwm rom i can flash? (or know where i can find it on my machine?!)
*edit its ok, i found it! it was under fastboot...i was in adb
* Second edit, nah, still didn't work.
i'm leaving it for now, don't wanna mess the phone up. I'll blank everything and start again one day.
Hey guys!!
I'm developing a Root Helper (See my signature)
Now I want you, to decide, would you think, would enrichen my Root Helper...
Or, tell me; what do expect, from a good toolbox (My Root Helper...)
What would make you more eager, to use it?
Additions:
I've taken some notes, and I think all of your ideas are good
And, here is another question: You wanted me, to explain, what which tool does, right?
Well, how would you prefer it? As a messagebox, before the program starts; or as a dialog, that pops up, whilst the program is running?
Or; should I put it as a tooltip?
The choice is your!!! The more you "vote" for whichever option, the higher the chance, I will add that to the program
familyguy59 said:
Hey guys!!
I'm developing a Root Helper (See my signature)
Now I want you, to decide, would you think, would enrichen my Root Helper...
Or, tell me; what do expect, from a good toolbox (My Root Helper...)
What would make you more eager, to use it?
Click to expand...
Click to collapse
Multiple recovery options
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems)
Automatic updates for the toolbox
Install Rom of choice or one with easy download from the toolbox
Kernel Options - Advanced user only disclaimer
md5 checker
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case)
Radio updater - Radio of choice
That's all I have for now, just a few ideas that might make it pretty extensive.
thacounty said:
Multiple recovery options
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems)
Automatic updates for the toolbox
Install Rom of choice or one with easy download from the toolbox
Kernel Options - Advanced user only disclaimer
md5 checker
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case)
Radio updater - Radio of choice
That's all I have for now, just a few ideas that might make it pretty extensive.
Click to expand...
Click to collapse
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems) -> Have got that done
Automatic updates for the toolbox -> Working on that ^^
Install Rom of choice or one with easy download from the toolbox -> Got that, too
Kernel Options - Advanced user only disclaimer -> It's a good idea, and would fit perfectly, to the ADB shell options ^^
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case) -> That was pretty much, the first thing, I put in, in both versions ^^
Radio updater - Radio of choice -> Also, a very good idea
Thanks, for the answer It's very much appreciated!! ^^
familyguy59 said:
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems) -> Have got that done
Automatic updates for the toolbox -> Working on that ^^
Install Rom of choice or one with easy download from the toolbox -> Got that, too
Kernel Options - Advanced user only disclaimer -> It's a good idea, and would fit perfectly, to the ADB shell options ^^
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case) -> That was pretty much, the first thing, I put in, in both versions ^^
Radio updater - Radio of choice -> Also, a very good idea
Thanks, for the answer It's very much appreciated!! ^^
Click to expand...
Click to collapse
Awesome, guess I should have read through what you had first! Looks like its going to be a great toolbox!
thacounty said:
Awesome, guess I should have read through what you had first! Looks like its going to be a great toolbox!
Click to expand...
Click to collapse
Well, I'm hoping, that it will keep getting better, and better ^^
And, this is one of my priorities; always ask the consumer
What I would like to see in a toolbox is this:
When you click on an option, say, "unlock bootloader" for example, I would like the toolbox to produce a pop-up describing how this is being done, something like: "This option reboots your device into fastboot mode (which you can do yourself by holding volume up and volume down and then pressing and holding power), and then issues the following command from a command prompt: fastboot oem unlock. This will produce a prompt on your device which you will have to accept or decline." etc. etc.
I would like to see this for everything option available in a toolbox, e.g., flashing a ROM, flashing a kernel, wiping, etc., etc..
This is the only way that we help people learn anything. If we just made everything 1-click, with no explanations, we are breeding ignorance, lack of knowledge, lack of troubleshooting ability, and lack of desire to learn... and a proliferation of "OMG I haz briked my fone" threads.
I agree with efrant. It should be informative and educational as well as functional. Possibly, though, to make it less annoying, make the popups appear only on first use of each of the commands. Also, perhaps make an option to just show all the information at once on demand.
FredFS456 said:
I agree with efrant. It should be informative and educational as well as functional. Possibly, though, to make it less annoying, make the popups appear only on first use of each of the commands. Also, perhaps make an option to just show all the information at once on demand.
Click to expand...
Click to collapse
Well, in my opinion, there is explanation, enough. But that is probably just a personal matter. There are options, to wipe, flash etc...
Sent from my Galaxy Nexus using XDA
efrant said:
What I would like to see in a toolbox is this:
When you click on an option, say, "unlock bootloader" for example, I would like the toolbox to produce a pop-up describing how this is being done, something like: "This option reboots your device into fastboot mode (which you can do yourself by holding volume up and volume down and then pressing and holding power), and then issues the following command from a command prompt: fastboot oem unlock. This will produce a prompt on your device which you will have to accept or decline." etc. etc.
I would like to see this for everything option available in a toolbox, e.g., flashing a ROM, flashing a kernel, wiping, etc., etc..
This is the only way that we help people learn anything. If we just made everything 1-click, with no explanations, we are breeding ignorance, lack of knowledge, lack of troubleshooting ability, and lack of desire to learn... and a proliferation of "OMG I haz briked my fone" threads.
Click to expand...
Click to collapse
Basically this. Some guide that pops up and tells step by step what the manual commands are. 1clicks perpetuate noobs, redundant threads and nerd rage.
zippity doo da.
Multiple recovery options
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems)
Automatic updates for the toolbox
Install Rom of choice or one with easy download from the toolbox
Kernel Options - Advanced user only disclaimer
md5 checker
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case)
Radio updater - Radio of choice
That's all I have for now, just a few ideas that might make it pretty extensive.[/QUOTE]
All of the above plus the option to relock bootloader and restore the phone using a stock image incase it needs to be returned for warranty
niallmcg said:
Multiple recovery options
Easy for n00b use (packages drivers in and uninstalls drivers that cause problems)
Automatic updates for the toolbox
Install Rom of choice or one with easy download from the toolbox
Kernel Options - Advanced user only disclaimer
md5 checker
Obviously backup and restore - maybe works tightly with backup and pulls new backups when the phone is connected to store on pc (just in case)
Radio updater - Radio of choice
That's all I have for now, just a few ideas that might make it pretty extensive.
Click to expand...
Click to collapse
All of the above plus the option to relock bootloader and restore the phone using a stock image incase it needs to be returned for warranty[/QUOTE]
Dang dude. He will need a toolkit for the toolkit. And a crew. Lol.
zippity doo da.
EFS backup and restore for those that may be scared of adb and/or lazy.
Since this is a "Samsung" phone, EFS is (too) easily borked for random/inexplicable reasons.
fail safe file manager to copy files to your phone. I've had a couple of times where I thought I transfered gapps over and then realized as i was flashing a rom it was not there. luckily I was able to boot the phone and then transfer the file and do recovery again.
Flukester69 said:
fail safe file manager to copy files to your phone. I've had a couple of times where I thought I transfered gapps over and then realized as i was flashing a rom it was not there. luckily I was able to boot the phone and then transfer the file and do recovery again.
Click to expand...
Click to collapse
FWIW you can transfer files to your phone via adb when you're in recovery.
mudferret said:
FWIW you can transfer files to your phone via adb when you're in recovery.
Click to expand...
Click to collapse
True. I don't like using adb though.
mudferret said:
FWIW you can transfer files to your phone via adb when you're in recovery.
Click to expand...
Click to collapse
What ever happened to being able to mount storage device to PC in recovery? That is missed.
thacounty said:
What ever happened to being able to mount storage device to PC in recovery? That is missed.
Click to expand...
Click to collapse
The Galaxy Nexus does not support USB Mass Storage mode.
Ok. So I got many options, to add
But, @rbiter is right ^^ I'll need a toolbox, for the "toolbox" xD
But no worrys. I'll get it sorted!!
First off I agree with the comments above about extra help menus to guide each step for n00bs. My idea for a toolkit add on if it is even possable, is to be able to customize the themes on different ROMs.. Like to change all ics blue to green or red.. There are more ROMs now that have been blacked out/inverted but the choices of themes are limited..
XtreemDroid said:
First off I agree with the comments above about extra help menus to guide each step for n00bs. My idea for a toolkit add on if it is even possable, is to be able to customize the themes on different ROMs.. Like to change all ics blue to green or red.. There are more ROMs now that have been blacked out/inverted but the choices of themes are limited..
Click to expand...
Click to collapse
Well, there are help menus, for ADB and fastboot ^^
It's easy for n00bs...
I've added fastboot and ADB commands (ADB/fastboot help menus...)
But I'm still waiting for the answer, to my question...
first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks
CrankyPants said:
first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks
Click to expand...
Click to collapse
Restore you stock ROM nandroid. Look for it in here COLLECTION of Stock backup's seeing as you really didn't bother to provide us with the relevant and more important information such as the CID and Main software version you were on before you decided to mess your phone up and I doubt you made a backup of your device before doing it.
Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.
I guess I will be the "bad guy" but why are you messing with your phone when you have no clue what you are doing?
Everyone starts somewhere. Im sure we all learned a lot of what we know now by making lots of stupid mistakes. This logic rings true for life... not just phones.
lucas.scott said:
Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.
Click to expand...
Click to collapse
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?
CrankyPants said:
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?
Click to expand...
Click to collapse
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.
Jyotirdeb said:
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.
Click to expand...
Click to collapse
How to install a custom recovery via adb and what is adb?
sorry I don't know anything
CrankyPants said:
How to install a custom recovery via adb and what is adb?
sorry I don't know anything
Click to expand...
Click to collapse
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.
I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.
leongwengheng said:
I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.
Click to expand...
Click to collapse
Good choice on the videos, these days reading is a bit to tedious for most people. Heck, they don't even read "STOP" on the STOP signs anymore, just drive straight past
I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app
leongwengheng said:
I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Good luck at school then and later on in your job
Lucky boy having such a commited community here. You could've quite easily ended up with a £600 paper weight. Might want to show some appreciation to everyone holding your hand through a process that you should've read about before doing anything. Must admit, I did like the 'I just kept hitting next without knowing what I was doing', that's probably the best thing I've read lol lol.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
BerndM14 said:
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.
Click to expand...
Click to collapse
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?
CrankyPants said:
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?
Click to expand...
Click to collapse
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.
BerndM14 said:
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.
Click to expand...
Click to collapse
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.
CrankyPants said:
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.
Click to expand...
Click to collapse
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?
BerndM14 said:
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?
Click to expand...
Click to collapse
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.
Jyotirdeb said:
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.
Click to expand...
Click to collapse
To get getvar all you'll need fastboot commands, will fastboot commands even work if he MIGHT not have enabled USB Debugging or for that matter haven't accepted the RSA key?
That's why I asked about the recovery as well though. I saw that on hasoon's toolkit the flashing of a custom recovery was like the next step on the process which means that this guy should at least have a custom recovery already installed.
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.
jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Make sure you are trying to open from the correct location, and put .\fastboot
EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!