Hi all,
I'm trying to install Cyanogemod on my i9100 (S2 intl). I'm quite experienced with flashing, rooting and Cyanogenmod in general as I've had it on both my Nexus 7 and my S3 for years. For the S3 I flash it via Heimdall cmd line; quite simple. For the S3, the recovery downloads as an img and just works. But for the S2, Clockworkmod's Recovery downloads as a zip, and not one of the tutorials explain how to use it. Do I flash the whole zip, just part of it or do I need to convert the zip to something else? And is kernel the correct partition to use?
The wiki guide doesn't give any help whatsoever. Everyone talks about zImage, but no where can I find what this is. There's a link on the wiki to download an img but it's broken and I can't find the image anywhere else. I think the wiki needs updating.
Drat, I can't put links in yet. I did have "wiki guide" linked.
I also posted my question to the Cyanogenmod forums, and they replied more quickly. This surprised me a bit; I may be a new account, but I've been a huge fan of XDA-Developers for a long time, and I was expecting a super quick answer. Maybe I posted in the wrong section for this, haha
For future reference, and to provide an answer for this question (and for ways around simple problems after that too):
forum.cyanogenmod.com/topic/96781-how-to-flash-latest-cwm-recovery-via-heimdall/
Turns out I was using the wrong kind of file for flashing via Heimdall. So glad my S3 was easier than this to flash Cyanogenmod.
So problem solved Any questions, I would be happy to elaborate.
1) This phone was released over 3 yrs ago, the S2 forums simply don't see the traffic they saw even 12 mths ago; 9 hrs is nothing.
2) Also, very very few people here use Heimdall as most are running Windoze machines. On Windoze you use Odin, there's no need to complicate things by attempting to use Heimdall.
So that's why you ended up with the first world 'problem' of not getting a response after 9 hrs.
You can elaborate on exactly what you did if you want; you never know, someone might come here one day & actually search for info rather than posting a thread purely because they can and expecting an immediate response.
1) This phone was released over 3 yrs ago, the S2 forums simply don't see the traffic they saw even 12 mths ago; 9 hrs is nothing.
So that's why you ended up with the first world 'problem' of not getting a response after 9 hrs.
Click to expand...
Click to collapse
I guess so. I hope you didn't think I was being too serious; I was only joking that I expected a reply that quickly Some areas of this site, people often reply in minutes, that's all
2) Also, very very few people here use Heimdall as most are running Windoze machines. On Windoze you use Odin, there's no need to complicate things by attempting to use Heimdall.
Click to expand...
Click to collapse
Really? I'm using Windows and I've never had any problems with Heimdall. In fact, I found Odin to be buggy and confusing. Heimdall seems far better (it's not leaked software, for a start), and I like the cmd-line interface.
You can elaborate on exactly what you did if you want; you never know, someone might come here one day & actually search for info rather than posting a thread purely because they can and expecting an immediate response.
Click to expand...
Click to collapse
I can't tell if you're annoyed that I didn't search or if you're joking. In fact I did search but couldn't find any information. And I wasn't going to elaborate here because all this info is in the Cyanogenmod forum thread, but if you insist:
1) Begin by reading the instructions on the wiki page: wiki.cyanogenmod.org/w/Install_CM_for_i9100
1-a) This means READ THE WARNINGS
2) When it tells you to download the recovery, ignore - the link is broken. Download from here: forum.xda-developers.com/galaxy-s2/orig-development/kernel-clockworkmod-recovery-6-0-2-9-t1118693
3) Extract the zImage file from inside and continue with the wiki instructions
4) When it tells you to click replace driver (which, btw, is badly worded - you must select "Install Driver" from the drop-down and it'll turn into "Replace Driver"), use the up-down arrows next to WinUSB to select libusbK. Otherwise you may get errors with Heimdall
5) After flashing the first CWM recovery, if you want to flash CM11, download the newer CWM from here: forum.xda-developers.com/galaxy-s2/development-derivatives/cwm-clockworkmod-recovery-kit-kat-4-4-t2628412
5-a) Start your S2 into Recovery and connect it via USB. On your PC, open a cmd and check that your device is showing up properly (adb devices). It it's not, download and install the Samsung USB drivers from here forum.xda-developers.com/showthread.php?t=2038555 or here forum.xda-developers.com/showthread.php?t=2038555 (or Google it - they're everywhere)
5-b) Use "adb push [recovery-zip-name-here] /emmc"
5-c) On your S2, find and flash the new recovery zip, then reboot into recovery again. You'll now be using the newer CM11-compatible CWM recovery
5-d) Now the device will no longer show up in ADB, even with the drivers installed (if it does for some reason, you can ignore this step). Open Device Manager on your PC and find either something called "i9100" or "Unknown Device" (of which there may be many on some computers - you'll have to work out which). Right-click > update driver software > browse my computer > let me pick > have disk.
5-e) Browse to the file and click ok "SAMSUNG\USB Drivers\16_Shrewsbury\ssadadb2.inf". This folder is normally in Program Files (not x86)
5-f) Continue by clicking next or whatever it is (I forget) to finish the installation of the driver. Test that it was successful (after it's finished) by doing "adb devices" again
6) If you're using the older CWM recovery: Use "adb push [cm<11-zip-name-here] /emmc" and flash it via the recovery
7) If you're using the newer CWM recovery: Use "adb push [cm11-zip-name-here] /storage/sdcard0" and flash via recovery
8) Push the correct gaps package (if using CM11, remember the warnings on the wiki - get the one that's small enough to fit on the S2's system partition) and flash it
9) At this point, you should be safe to wipe the cache and do a factory/data reset. I didn't (not immediately - I did a little later on), and just booted up, and it worked fine, but you'll probably want to do it at some point anyway to get rid of the crapps that are probably still on your S2 and it wipes all your data and settings, so best to do it now
10) Reboot an enjoy a freshly CM'd device! Remember that the first boot can take 5-10 mins. I'm currently using cm-11-20140609-SNAPSHOT-M7-i9100.zip, and so far it's been very stable, fast and reliable, only I've had issues trying to connect to the wifi. As there was a new snapshot released yesterday, I'm going to be updating to cm-11-20140708-SNAPSHOT-M8-i9100.zip shortly
There. It's not a complete beginner's guide, but it may help someone who's having problems with their S2 and Cyanogenmod. Hopefully this will show I don't expect anyone here to do all my work for me or to be at my beck and call; I should rarely be taken too seriously, and while I was genuinely surprised that no one replied faster, it was entirely a happy, curious surprise, not in any way an annoyed or unhappy surprise. Kinda feel like I got off to a bad start with that post
If anyone has any specific questions, I'll be happy to elaborate
Very good! Thanks!
btw, did you ever solved the wifi problema?
Genialt said:
Very good! Thanks!
btw, did you ever solved the wifi problema?
Click to expand...
Click to collapse
You're very welcome
What wifi problem? I've had no issues with the wifi (although, having said that, I don't believe I've actually tested the wifi with the phone since we're just using it as a 3G tether).
Related
Okay, so I've seen these issues dealt with separately, but never in conjunction. Unfortunately, I am having both in conjunction.
Starting with a fresh Droid Eris, I used a one-click root to allow superuser permissions.
From there, I flashed CM7. Along with many other users, I ran into the issue where I had no data or voice signal.
I'll let you know here, that I've wiped EVERY time I did anything. This is NOT a wipe issue.
I flashed the newest radio... No luck. So, I went through clockwork's recovery and reverted back to the original 2.1 ROM. Still no luck on the signal issue. At this point, I decided to reflash CM7 and try to deal with the issue through ADB.
This is where things went wrong. The load for CM7 corrupted (I'm assuming) and gave me a nice case of Bootloop. Thinking everything was fine, (Assuming I'd do a battery pull and just go back to 2.1) I booted into the original Android recovery and NOW the damn track ball will no longer make selections. It will scroll, but not select.
Here's my question: Seeing as I can not boot fully to allow usb debugging, and I can not recover through Android (Thank you, trackball), is there ANY way to reflash the original RUU through ADB?
Thus far, I can't get passed the obvious "This device is not ready," prompt.
Any help is greatly appreciated.
FYI, adb is available when the custom recovery is booted.
what that means is that with the recovery booted you can:
1) drop a smallish (say, less than 100 MB) ROM file into /cache (e.g. "adb push")
2) create an Android command file (/cache/recovery/command) with a single line that points at the ROM file as an update
3) do a "adb shell reboot recovery"
This will cause the subsequent boot to the recovery to automatically install the ROM file you dropped in cache.
Voila. No trackball needed.
The syntax for the command file (/cache/recovery/command) will be a single line:
--update_package=CACHE:your_ROM_file_name_goes_here.zip
See this post for an expanded explanation.
cheers
[ Edit ]
Note that the above is a thumbnail sketch which requires you to fill in the blanks. For instance, wiping /data and /cache and flashing packages after the main ROM. Cumbersome, but you only need to do it once. Once you have a rooted ROM installed, you should flash a trackball-free version of the recovery so you don't need this method for every ROM you install. Instructions for that (using "flash_image" via adb) can be found elsewhere.
Scott,
Whoa! You got a lot going on there...
Okay, I don't have all of the answers here for you, but I know enough to ask a few questions that we'll need a clarification on.
1. Can you tell us your HBOOT version and whether its S-ON or S-OFF?
2. You mentioned that you've used ClockworkMod (not good , but maybe not terrible)...you also have mentioned using/having Amon_RA custom recovery. Which custom recovery do you have currently installed and can you boot into said recovery?
3. By the way, I think the voice/data signal thing is fixable--it sounds familiar to me, but I don't know the answer right off-hand and this is not your primary issue at the moment.
4. You should be able to run the RUU to restore 2.1 back to your phone. It doesn't require a working custom recovery running and/or adb. Although you might simply be asking if you can flash a ROM through adb, then the answer is yes, you can. Although you will need custom recovery running to make sure its adb server is running and that, of course, require USB connectivity (alluding to your "This device is not ready." message).
5. Usually, installing HTC Sync will install the USB drivers necessary for you to use adb. If that doesn't work for you, PM me with your email address and I'll send you about 10MBs worth of USB drivers I've collected over the last year that might help you with this issue.
6. Lastly, there is a version of Amon_RA's custom recovery available that does not require the use of the trackball. You're not really in a position to flash/install that at this point unless you have the S-OFF engineering bootloader.
I'll hold-off with additional info pending your responses to the above.
Cheers!
edit: trumped by the Master himself, LOL! [I knew you'd be along sometime soon, bftb0 ]
scary alien said:
Scott,
Whoa! You got a lot going on there...
Okay, I don't have all of the answers here for you, but I know enough to ask a few questions that we'll need a clarification on.
1. Can you tell us your HBOOT version and whether its S-ON or S-OFF?
2. You mentioned that you've used ClockworkMod (not good , but maybe not terrible)...you also have mentioned using/having Amon_RA custom recovery. Which custom recovery do you have currently installed and can you boot into said recovery?
3. By the way, I think the voice/data signal thing is fixable--it sounds familiar to me, but I don't know the answer right off-hand and this is not your primary issue at the moment.
4. You should be able to run the RUU to restore 2.1 back to your phone. It doesn't require a working custom recovery running and/or adb. Although you might simply be asking if you can flash a ROM through adb, then the answer is yes, you can. Although you will need custom recovery running to make sure its adb server is running and that, of course, require USB connectivity (alluding to your "This device is not ready." message).
5. Usually, installing HTC Sync will install the USB drivers necessary for you to use adb. If that doesn't work for you, PM me with your email address and I'll send you about 10MBs worth of USB drivers I've collected over the last year that might help you with this issue.
6. Lastly, there is a version of Amon_RA's custom recovery available that does not require the use of the trackball. You're not really in a position to flash/install that at this point unless you have the S-OFF engineering bootloader.
I'll hold-off with additional info pending your responses to the above.
Cheers!
edit: trumped by the Master himself, LOL! [I knew you'd be along sometime soon, bftb0 ]
Click to expand...
Click to collapse
Yup bftb0 is a beast at these things, lol
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
The best guide ever is in the development section, it works for your device.
http://forum.xda-developers.com/showthread.php?t=1239185
follow the guide its very easy and worked fine for me
I Return triumphant, and gentlemen, i must say you were incorrect.
The I/O edition does not give you the option to access recovery at any point, even with the Pwr+VOL DN boot.
You can put it into download mode, and certianly use ODIN to install the recovery rom, but you will have no method to actually access recovery to push zip files.
thanks to some quick self education on using fastboot, i was able to root successfully.
To those of you in a similar situation who stumble upon this thread, i invite you to visit:
http://droidbasement.com/db-blog/?p=2439
There you can download CWM in a .img format for use with fastboot.
This link is where you can download fastboot:
http://forum.xda-developers.com/attachment.php?attachmentid=596615&d=1305443483
and you'll need to install PDANet for Android to get the fastboot drivers:
http://junefabrics.com/android/
I belive you'll also need ADB installed from the Android SDK. i do have it installed on this computer, but did not use the ADB command at any point, just fastboot.
Instructions:
1. Download fastboot, PDANet for android, and the recovery image. You'll also need "Samsung_Galaxy_Tab_10.1_root.zip" found in Root.zip from the retail version instructions.
2. Copy the "Samsung_Galaxy_Tab_10.1_root.zip" to the tablet, and and power it off. Disconnect the USB connection
3. Unzip fastboot zip into it's own folder, and then copy your recovery.img file into the same folder.
4. Start the install of PDANet. It will ask you if you want to install drivers about half way through. say yes, and select "Samsung" when the time comes. it will install some drivers and then ask you to try and connect. windows may flare up and say they're unsigned. accept anyway.
5. watch this friendly video on how to start fastboot on your tablet:
http://www.youtube.com/watch?v=sR7vE4IueaU
"fastboot!"
Basically the same as the steps outlined for the retail version, but you will go to the usb icon instead of the box.
6. once the tablet is in fastboot, connect the USB cable. PDA net will recognize it as an ADB connection and try and load itself. it will fail, that's fine. Let the installer exit completely.
7. Open a command line in windows, and get it to the directory fastboot.exe and your recovery image are in.
8. run your fastboot command. i only used it temporarlily, so my command was:
"fastboot boot recovery-cwm_5.0.2.7-sam-tab-10.1.img"
9. the tablet should now boot into the recovery image presented. hooray! follow the remaining instructions from the retail version root, using recovery to load the "Samsung_Galaxy_Tab_10.1_root.zip" and reboot.
10. Once you've done all that, select to reboot. The tablet will reboot. i took the opportunity to disconnect the cable.
11. "Superuser" should now be in your apps, and you're rooted!
Extra Step: Download "Rom Manager" by clockwork from the android market, and install it. from here, opt to flash recovery. Once that's complete, you can now access recovery by launching that program and simply hitting "Reboot into Recovery"
I have no use for this myself but it's not often someone comes back and posts a complete howto on solving their own initial issue. I wish more people would do this. Thanks button clicked.
I just ran into this exact problem and only found this thread after figuring it out on my own. I figured my IO tab just didn't like having clockwork mod installed, but it certainly booted it. I nearly ruined it by accidentally wiping my rom trying to get it to boot at all. I had to repush my install files to the insternal memory using adb after I was able to boot into recovery with fastboot.
I haven't looked around too much (seeing as I only JUST got the damn thing to boot a rom) but is there a fix to that, perhaps installing the retail bootloader?
I'd hate to have to use fastboot everytime my rom doesn't boot. I've gotten used to wiping and installing roms from wherever I am on my other android devices.
I'm not familiar enough with the device to be able to give you a definite answer, but i imagine adding a bootloader from the retail version would give you the recovery option instead of fastboot.
personally, i'm a little more fond of having fastboot around right now, as it's easy enough to get into recovery when flashing things with it, and the bootloader for the I/O is unlocked... i can think of a few fun things to do in the future if i can load any ROM i want into memory, test it, and move on if it's no good... i may even give some of the ICS dailies a try thanks to this.
Always several ways of doing things... glad you got it worked out.
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
RootzFan,
that method is flashing an entirely new rom, down to 3.0, just to gain root access and open recovery so you can then return to 3.1.. it has the added byproduct of installing touchwiz.
IMHO, my way is a little cleaner as there is actually zero flashing needed, and you get to keep everything active and installed.
i recommend just going for custom roms - it comes already rooted - yBoot into recovery and flash a custom ROM
I have the IO tab myseldf and have been flawlessly running GalaxyTask custom ROM - http://forum.xda-developers.com/showthread.php?t=1340064
shane86 said:
I recently purchased a used Galaxy tab 10.1 I/O, and it had already received the 3.1 OTA update.
Now i want root access for various reasons, and can't seem to find a clear guide on how to do so.. I've found plenty about how to do so on the original 3.0 rom, and that it will carry through the 3.1 update, or for the regular version Galaxy Tab 10.1, but it's my understanding the ROMs were fairly different between the I/O and the retail version and that attempting to cross-pollinate root methods may not be a good idea
although I've rooted and ROMed my fair share of HTC devices and Nooks i'm a little more apprehensive with this unit, as it's my first android device to lack an SD card slot of some sort, so bricking seems like a much worse possibility
Click to expand...
Click to collapse
oh, def not the best method... just saying it is nice that there are alternatives.
self delete
Fun Stuff.
So, I have made a major boo boo when it comes to rooting devices and flashing custom ROMs; normally I am not a n00b when it comes to this, but I think I gone done something wrong this time. I have checked Diamondbacks thread as well as many other and have a whole slew of tools downloaded now and I cannot seem to get past the splash screen. ADB recognizes my device as well as Windows in Fastboot mode, just can't seem to figure out how to flash the stock ROM back on this device. I would be willing to donate money to the cause as this has cause me much undue frustration. If you are up and willing to the task, please PM me or even call my cell to walk me through this. Couldn't find XDA's chat, all I am asking is that someone have a heart and help a fellow techie out.
LivioDoubleFang said:
So, I have made a major boo boo when it comes to rooting devices and flashing custom ROMs; normally I am not a n00b when it comes to this, but I think I gone done something wrong this time. I have checked Diamondbacks thread as well as many other and have a whole slew of tools downloaded now and I cannot seem to get past the splash screen. ADB recognizes my device as well as Windows in Fastboot mode, just can't seem to figure out how to flash the stock ROM back on this device. I would be willing to donate money to the cause as this has cause me much undue frustration. If you are up and willing to the task, please PM me or even call my cell to walk me through this. Couldn't find XDA's chat, all I am asking is that someone have a heart and help a fellow techie out.
Click to expand...
Click to collapse
Not sure what recovery you have now but I suggest you go here >>
http://forum.xda-developers.com/showthread.php?t=1615990 and install twrp recovery through the fastboot method. Boot into trwp recovery. After that, download the nvflash files from here http://forum.xda-developers.com/showthread.php?t=1774352
Not saying you should use nvflash at this point but the file also contains a known good adb.exe file. Unzip the file and while in that directory press and hold the shift button while right clicking the mouse. This will bring up a menu select open command prompt here.
Put your rom into the same folder as the adb.exe then in the comand window type adb push /name of your rom.zip /sdcard/ if this doesn't work use /sdcard/media At this point you should be able to install the rom. As for the rom, a good starting point would be androwook rom since it seems to install quite easily (do not unzip). Also when you are performing commands in either fastboot or adb, it is best to copy (control c) from the webpage then in the command window right click and paste, this eliminates errors. Having the files you are flashing in the same directory of fastboot or adb eliminates the need to type pathways, this is where many people run into issues, 1 wrong letter make everything not work....
Thanks Gage_Hero, the TWRP tutorial was just what I needed in getting a custom ROM flashed to the device; however, my next question is, if I did not create a backup of the stock ROM like I should have, will I ever be able to get back to it should I need to update the OS or for any other reason? From what I have read, Asus stock ROMs have a unique ID to every device, making it virtually impossible to use someone else's backup for flashing. Much appreciated for any information you can provide.
LivioDoubleFang said:
Thanks Gage_Hero, the TWRP tutorial was just what I needed in getting a custom ROM flashed to the device; however, my next question is, if I did not create a backup of the stock ROM like I should have, will I ever be able to get back to it should I need to update the OS or for any other reason? From what I have read, Asus stock ROMs have a unique ID to every device, making it virtually impossible to use someone else's backup for flashing. Much appreciated for any information you can provide.
Click to expand...
Click to collapse
Most people don't have a stock backup since once you are unlocked, trying to install the ota update can make the tablet inoperable. So basically when Asus updates the software then the developers here pick up the stock rom and enhance it. This goes anywhere from the base stock rom with root up to taking the rom and customizing it with options, kernel changes and such. The only thing I will say about changing kernels is only use kernels that were developed for the particular rom or you will have trouble. Kind of like taking a Ford motor and trying to mate it to a chevy transmission.
If you do change roms, make sure you wipe cache, dalvik and do the factory reset from within twrp. When you become comfortable, I suggest looking at the NVflash thread in the dev section. This will provide you with a bit of assurance that you can recovery from most software brick situations. Read over the instructions a few times before you go a head and take some time to read through the thread so you know what could potentially go wrong. It really isn't that difficult to do but you should be well informaed before proceding. If you need anything else don't hesitate to ask
Another thing that i find helpful, keep a stock rom in your sdcard. When i semi-bricked my 201, i was able to flash the stock rom using CWM, then do a factory reset. Once back to factory, i was able to boot and start over again.
I need to get my phone back to the original stock Android since Cyanogenmod wrecked it by disabling the phone dialing keys, but I can't because fastboot isn't working. What do I do? Apart from the number keys not working, everything else on the phone is fine.
I've spent 15 hours on this so far and if it doesn't get solved I have to throw my phone in the trash. I've read every word and gone through every step of the how-tos linked below, over and over and over and over.
In the command prompt my commands and responses are:
fastboot devices -> 'fastboot' is not recognized as an internal or external command, operable program or batch file
fastboot-windows devices -> nothing happens
fastboot-windows oem unlock -> <waiting for device>
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
http://forum.xda-developers.com/nexus-4/general/tutorial-nexus-4-update-to-4-4-kitkat-t2534160
http://forums.androidcentral.com/ne...s-4-factory-image-restore-13.html#post3938684
Nexus 4
CyanogenMod 11.0 installer xnpq32p
Android 4.4.4
Do you HAVE fastboot on your computer and are in the correct directory to run the commands? Are you in the right mode on the phone? Check the Device Manager for driver errors?
But why not just update CM? There's obviously something that went wrong there because certainly CM doesn't usually have issues with the Dialer. Or just flash a stock rom in recovery.
es0tericcha0s said:
Do you HAVE fastboot on your computer and are in the correct directory to run the commands? Are you in the right mode on the phone? Check the Device Manager for driver errors?
But why not just update CM? There's obviously something that went wrong there because certainly CM doesn't usually have issues with the Dialer. Or just flash a stock rom in recovery.
Click to expand...
Click to collapse
Yes I had the tool.
Took half a day but I finally found Minimal ADB and Fastboot tool. Fortunately I sensed that everything must to be saved and extracted into one single folder, and the tool installed there - which the step-by-step guides either omit to mention or are vague about.
The dialer problem happened immediately upon installing CM, for the first time, the other day. So that was the latest version. Others have reported the same problem in the past and no one at CM replied. I'm leaving the country on a long trip and can't play with this any longer. I need a completely 100% working phone immediately.
If I had known that a so-called 'factory reset' does nothing of the kind, and getting back to stock is a such massive undertaking, I never would have considered messing with this.
fbtsrg said:
Yes I had the tool.
Took half a day but I finally found Minimal ADB and Fastboot tool. Fortunately I sensed that everything must to be saved and extracted into one single folder, and the tool installed there - which the step-by-step guides either omit to mention or are vague about.
The dialer problem happened immediately upon installing CM, for the first time, the other day. So that was the latest version. Others have reported the same problem in the past and no one at CM replied. I'm leaving the country on a long trip and can't play with this any longer. I need a completely 100% working phone immediately.
If I had known that a so-called 'factory reset' does nothing of the kind, and getting back to stock is a such massive undertaking, I never would have considered messing with this.
Click to expand...
Click to collapse
It's a factory DATA reset, not a restore your operating system option. It works exactly as it should, by removing user data and settings.
But for future reference, this is why you do a backup in recovery - so you can switch back in time of want or need.
times usbeae
es0tericcha0s said:
But for future reference, this is why you do a backup in recovery - so you can switch back in time of want or need.
Click to expand...
Click to collapse
- What do you mean by "backup in recovery"? What is that, and where is it?
- What do you mean by "switch back"? Switch back to what? The original state precisely as it was when I opened the box? Because ideally - if I ever root again - that is what I would like to be able to do in a simpler way than removing a bunch of drivers then installing new ones then enabling and disabling and re-enabling USB debugging then running ADB and fastboot and typing commands.
I guess I'm not clear on how it's possible to install Cynanogenmod by downloading an installer, click on two or three things, bam you're done - whereas removing it is an order of magnitude more complicated.
fbtsrg said:
- What do you mean by "backup in recovery"? What is that, and where is it?
- What do you mean by "switch back"? Switch back to what? The original state precisely as it was when I opened the box? Because ideally - if I ever root again - that is what I would like to be able to do in a simpler way than removing a bunch of drivers then installing new ones then enabling and disabling and re-enabling USB debugging then running ADB and fastboot and typing commands.
I guess I'm not clear on how it's possible to install Cynanogenmod by downloading an installer, click on two or three things, bam you're done - whereas removing it is an order of magnitude more complicated.
Click to expand...
Click to collapse
Well I would never have reason to use an installer (I prefer the "old school" manual methods) but CM couldn't install without a custom recovery, so not really sure how you don't know about that...? You can get to recovery from the bootloader screen accessed while off from Power + Vol Down for a few seconds. In recovery you can flash another rom or a stock based one. If you are S-On, you still need to fastboot flash the boot.img though. Have you checked your Device Manager for driver errors? I never have luck with this vintage of HTCs in fastboot on my Win 8.1 PC. I never have issues in Win 7 though. I actually keep a POS WIn 7 PC around just to work on HTCs.
So yea, the installer is helpful in making it simple to install, however, since you went the "easy" route, it seems like you missed out on a lot of reason to read through some threads and get some idea on what exactly you're doing and what's been done to the phone. It's best to walk before you run.
This thread may help you with your fastboot issues
http://forum.xda-developers.com/showthread.php?t=2277112
So i just decided to join the rest of the world and get myself a rectangle. so i researched the 1 to 200 dollar range for weeks until i found my new shiny metal friend with great specs and a price that wouldn't keep me up at night. the le max 2 x829. but i love tech and was really looking forward to pushing this phone and learn about all it could do! i was really excited.
Until i started to learn about the many confusing programs needed to install custom roms or make a recovery file. things like that All of which need like 6 different programs all of which seem to need some other program in order to functional. I can't seem to even find a starting point! I HAVE NEVER FELT THIS STUPID IN MY ENTIRE LIFE. Someone please help. what programs do i need for a new os ? How does adb fit into the chain of programs needed to mod android? is twrp the first program needed? how does it all sort...fit to gather? Thanks for any help!
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
including adb? what other drivers do i need? xposed? supersu? ...i have done my research by the way...its just not making alot of sense..thats all. i know all you old pros have probably been at it for years but i never even held a smartphone until 6 days ago ha ha
valy_cta said:
Man, honestly this forum is made to help people, but also people should use the search button. This question has been answered a million times already.
Long story short:
- Connect the phone to the PC and install the drivers (including ADB)
- Unlock bootloader (usually it's already unlocked)
- Download TWRP on your PC
- Install TWRP following the developer's steps
- Download your custom ROM
- Put the ROM on the internal memory
- Boot into TWRP
- Install the new ROM according to the instructions given by the developer and you're done...
Click to expand...
Click to collapse
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Serialjwalker said:
Also how do you download twrp on you're pc ? it won't let me i have it on my phone but it just keeps leading me to a website to download again.
Click to expand...
Click to collapse
Do you have it installed on the phone or just downloaded? If it's installed, jump over that step. If it's just downloaded, connect the phone to the pc by cable, transfer the files :cyclops:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
razmth said:
I understand your concern. It's because there are a few ways of doing it, and so novices might be confused when comparing two different tutorials.
This one is very complete: https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
1. Connect your phone, it is supposed to install drivers automatically.
1.1 If not, you'll need to google it, but I believe this toolkit will help you. In fact, this tool is capable of doing all the process for you by simply clicking on some buttons.2. Install ADB Drivers. There are a few options and it is basically
2.1 @greenManGaming recommends 15 seconds ADB installer.
2.2 (Alternative) Minimal ADB and Fastboot. I've used this one.
2.3 (Alternative) ADB and Fastboot (newer) or Universal ADB and Fastboot (older) from the same dev.
OBS: I'm not sure if the toolkit requires or not one of these options to work properly or if it already does this task.3. Download TWRP (on your computer).
3.1 Follow the instructions from the official page. In short, put the img into the ADB folder.4. Follow the commands in the the tutorial mentioned.
4.1 In short, unlock the bootloader, boot twrp, complete backup, reboot into the system, copy the backup to your PC/Cloud service, get back to fastboot mode, flash twrp, then flash your ROM.
OBS: Suggestion for only booting TWRP at the first time is perfectly optional, you can flash it since the beginning but in this case you wouldn't be able to backup the original recovery and everything as the phone came, in case you need go back to request an RMA.
Click to expand...
Click to collapse
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
someone tell me how to delete this thread...i am just going to sell my smartphone i can't look at it anymore. every thing i try to do with it it resists every single inch of the way. nothing works according to instructions. i thought this would be fun but its hell... i give up! ...it wins going to trade this thing for the first 30 dollar burner phone i can find
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
valy_cta said:
Huge drama for nothing. Sell the thing, it's obviously not for you. If you can't follow some simple instructions, then it's better to sell it to some guy who likes to try at least.
Click to expand...
Click to collapse
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Serialjwalker said:
maybe they are laid out to be simple but nothing is working as instructed. i have been at it for a week . so far installing firefox is the best i can seem to do lol simple? theres nothing simple about the gangbang of programs you need to do stuff on these phones. none of which can actually be compelled to function under any circumstances at least for me.
Click to expand...
Click to collapse
If you are not familiar with giving commands with command prompt, installing drivers and needed software (android studio or minimal adb install) then you are in for a challenge, if you are not willing to learn its better to sell the phone or use it with de preinstalled android.
i find myself quite skilled( have flashed several brands of phoned in the last 5 years) and it took me a couple of days to figure out what to do and how to install twrp and my first rom, there are no one click shortcuts for this phone
Why need to install rom? It already work.
Serialjwalker said:
more questions....twrp will only load onto my phone and not my pc? also there are no adb driver folders just an exe. what do i do about that?
Click to expand...
Click to collapse
Did you try watching different videos to have a big picture of the process? It would be the first step. Even if you don't understand English, simply watch it. You'll see what would happen after each action.
Then check the written tutorial. Not a big issue at all. Really. Even for newbies, I've been one when I had a Galaxy 5, my first android that doesn't even needed to flash a custom ROM.
Whether you think you can, whether you think you can't, you're right.
The command to load the TWRP will be done on your PC, however, only your phone will load it. In short, you'll be commanding your phone through your PC.
When you install Minimal ADB and Fastboot, it will install its files in a default folder. Inside its default folder is where you should place the TWRP image.
Sent from my Le X820 using Tapatalk