Really didn't want to make a new thread about this but honestly people just jumped to conclusions without being helpful in my previous thread.
Long story short I'm trying to manually get 4.4.2: http://forum.xda-developers.com/showthread.php?t=2664561
I saw that I needed to get s-off, which requires root. Bootloader was already unlocked and so did everything here: http://forum.xda-developers.com/showthread.php?t=2273376
I installed CWM. It said to install a superuser tool so I installed SuperSU.
"You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead." was the next line. <-- I saw that message. Installed a kernel that he recommended: http://forum.xda-developers.com/showthread.php?t=2255900
After reboot I get SuperSU error: There is no SU binary installed and SuperSU cannot install it. If you just upgraded to Android 4.3, you need to manually re-root- consult the relevant forums for your device etc.
Can anyone help me get the proper SU Binary installed? Not a beginner to rooting as I've had had several previous phones before. Never encountered something as annoying as this.
On 4.3, 3.17.502.3.
I had the same issue when I installed 4.4.2 on my international One.
What I done to root was;
- downloaded SuperSU v1.80 zip from here.
- download SuperSu from the Play Store
- in SuperSU, select the option to install binaries via TWRP/CWM. (If it doesn't reboot to recovery, manually enter recovery)
- flash the supersu v1.80 zip and reboot
- open SuperSu and install the binaries using the normal option.
That then enabled my root. I'd tried quite a few different variations and this was the only method that worked for me.
Sent from my HTC One or Note 3 via XDA Premium 4
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
mch277 said:
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
Click to expand...
Click to collapse
You seem very confused about the whole rooting process ... what was the point in flashing the stock recovery ? Are you trying to install the OTAPkg.zip ?
what Rom are you wanting to install and whats flashing stock recovery have to do with it ?
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
mch277 said:
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
Click to expand...
Click to collapse
I wrote the thread you linked too
http://forum.xda-developers.com/showthread.php?t=2659374
and yes it is necessary to have stock recovery to take an OTA, but your post didn't mention taking OTA it said you had no SU installed.
to get into stock recovery
boot to bootloader
choose recovery
wait for black screen, hold vol up and then power
you will see something about sdcard fail .. ignore it till the menu comes up
then choose to flash OTAPkg.zip from sdcard
Related
Do I have root?
First you install the unlock APK, unlock it...Install goo beta, Install Open-Script Recovery, reboot and ill have TRWP? and be able to install custom roms?
IM READY TO JUMP SHIP!
You have your recovery to install everything.....
Inviato dal mio Transformer Prime TF201 con Tapatalk 2
It has its own recovery? or do i need to install one...
David522d said:
It has its own recovery? or do i need to install one...
Click to expand...
Click to collapse
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
also a video showing you how to flash a custom rom, with TWRP and goo manager, is there also
demandarin said:
install one. get goo manager from market place. then go in goo manager, go to settings I believe. then tell it flash open script recovery. It will flash the TWRP recovery for prime. all touch screen based. then with goo manager, you can find all the great toms for prime in there and flash directly from there. plus it'll let you know when there is updates for your custom rom. check it out. IMO, has alot more features and more straight forward that CWM recovery.
actually there a sticky thread in developement section that has video guides for the prime. one of them shows you how to install this recovery I mentioned if you unsure.
Click to expand...
Click to collapse
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Anyone ?
I don't know about goo manager but I flashed cwm touch with fastboot (normal cwm didn't work and twrp wasn't out)
Sent from my sgs2 running cm9
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Yeah steps sound good. you could always flash a ROM that has root. I dont think you need root to install twrp. Double check though. post in twrp thread to make sure.
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
David522d said:
1. Install Unlock APK. Unlock.
2. Reboot, Install Goo Manger, Install Open script recovery. Reboot into TWRP recovery
3. Install ROMS?!?!!?!
As in I don't have to root after I unlock it already does?
I don't have root on this tablet, its on .21. I don't want to brick it, so will these steps be perfect?!
THANKS!!!
Click to expand...
Click to collapse
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
David522d said:
Hate to be a pain the butt
But does anyone know if that method will work 100%
Sorry fellas dont want to end up with a 500$ paprr weight
Click to expand...
Click to collapse
There is nothing that will work 100%, but its pretty close, maybe 98%? Anytime someone does anything with the bootloader, recovery rom, or OS rom, there is a chance for bricking: interuption in the write process, loss of power, corrupted dl (crc check should catch most of those). If your worried about bricking it, leave your TFP stock and await the OTA's - that way if it gets bricked by Asus then they are responsible and you havent nullified your warranty.
Unlocking the bootloader allows the use of non stock bootloaders/recoveries to be installed and used. From the new bootloader/recovery, you can install a rom that either has root, or not. You don't even have to change roms after unlocking. The 2 are independent.
Right -
Unlocking with the APK does not root or in any other way modify or prep the prime for what you're about to do. Depending on your stock ROM revision this is either very easy or a complete pain in the ass, I'll provide both versions:
For Stock ROM ending .15 or earlier -
* DO NOT RUN THE GOO IM.MANAGER FIRST. Follow these steps below.
* Download Sparky's APK to root - it's in the development forum for the TF Prime. Run it. This will get you root access on the system. It's automated and practically idiot proof, just follow the on screen instructions.
* If you're going the Team Win route, once rooted, load up the Goo.im manager, then follow the instructions as per a rooted installation for getting TW Recovery into place. This is pretty painless really and works automatically, approve the Superuser permissions as required. Once the recovery is in, you can reboot into it and then get with the flashy.
-----
If you're on the Stock ROM ending .21, you're going to have to do what I did. As you're already unlocked using the BLOB files to downgrade -will- result in a hard brick. SO!
* Install ADB and Fastboot onto your system, as well as the universal USB naked driver which you can find on this forum.
* Search for DotTech install ADB and Fastboot - follow this guide, it's probably the easiest way to get a working fastboot and ADB environment up and running.
* Enable USB debugging on the tablet under developer options.
* Set up the universal driver, you'll need to reboot your TF201 and hold the POWER and VOLUME DOWN buttons until you see some text in the top corner. Do NOT press volume up to go into Recovery Image mode or you'll just walk into a dead end.
* Shortly after you'll see three icons, press volume down ONCE and then volume UP once, the USB icon in the middle should be highlighted and you should see text saying "Entering Fastboot Protocol" or similar.
* Plug the USB cable into the tab and the PC, test whether you have a working fastboot install by typing fastboot -i 0x0b05 reboot, if your tablet reboots without you touching it, then you've got working fastboot access. Remove the cable, reboot to fastboot mode as described above.
* Meantime, download openrecovery-twrp-2.1.3-tf201.blob from the team win site, and stuff it in the same directory that you set up Fastboot/ADB, rename it to twrp.blob. Plug your tablet back in and then issue the command fastboot -i 0x0b05 flash recovery twrp.blob , if this goes to plan you'll see a couple of lines of text on the command window which will tell you that it's been successfully flashed in. YOU STILL DO NOT HAVE ROOT THOUGH, SO NO SILLY STUFF
* Finally, download the ROM of your choice, place it in the base /sdcard directory, then reboot the tab and hold POWER and VOLUME DOWN, when you see the text, this time hit VOLUME UP, and you'll be sent into the team win recovery suite, at this point you can wipe and flash the newly prepared ROM as per normal.
* For the first occasion I -strongly- recommend you use Virtuous Prime-S as you can generate a solid backup environment out of it, as well as the fact it's not too departed from Stock, so it's a good way to break yourself in.
Hope this helps.
This whole blob thing is new for me since i have always insta-rooted, and CWM'ed any android device i get; but from what I've gathered, it is used by ASUS to lowlevel write the os on locked systems, similar to the way nvflash dumps img's directly to the memory. Once your unlocked with the CWM or twrp, then you can no longer use blobs, just the rom zips. The recovery rom handles the unpacking and dumping of the kernel and OS into the appropriate partitions. Some roms are zipped with install scripts that wipe your cache, user space and dalvik - but its always a safe bet to do that anyways.
Nice writeup Hobbesian
Well, some blobs are fine, but generally they're strictly either Team Win Recovery or Clockwork mod recovery suites, and they need to be slipped in using fastboot (I believe ROM manager and GOO managers use their own scripts to handle installation) as a rough rule. The "big" BLOB files which Asus puts out are a guarantee to hardbrick an unlocked device (some days I wonder if it would kill Asus to offer a route to re-lock and re-stock a device on the proviso that if you brick it doing so you're still out of warranty).
That said - Virtuous Prime is definitely an excellent first step into Custom ROM tinkering, it gives you root and all the associated useful features, as well as the ability to start experimenting with more feature heavy ROM builds such as Cyanogen and AOKP Cornerstone. They're even nice enough to include a partially tweaked build.prop which saves you a lot of the work in modifying that.
I should point out my guide is relevant only if you already applied the unlock APK to your system, if you haven't done so, there's alternative routes including the downgrade blob option to get root without unlocking your device.
paddycr said:
Unlocking will not root your prime. I think Goomanager needs superuser rights so you will need to be rooted to flash TWRP (at least it asks for SU when I check for rom updates).
I use CWM since there have been a few stories floating around of people bricking their primes when trying to restore using TWRP. I am sure it is fine but it just makes me a little nervous...
If you're unlocked, not rooted and want to install CWM follow method 1 here:
http://forum.xda-developers.com/showthread.php?t=1576937
Click to expand...
Click to collapse
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
David522d said:
1. Unlock Prime...
2. Do method 1
3. Then goo manger, install script. Reboot in team win recovery
4. Install AKOP =) !??!?!
yes?
Click to expand...
Click to collapse
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
EDIT: if you're in fastboot and you cannot get adb to recognize your prime you need to install the correct drivers for your pc/mac. Hobbesian describes how to do this a few posts above this. In his nice write up he also describes how to flash TWRP directly from fastboot. If you want TWRP, follow his instructions since you'll have less messing around to do.
paddycr said:
The method 1 in the link will install ClockWorkMod which I use as my recovery. You can completly miss step 3. If you really want to use TWRP then do the goomanager thing.
However, before you do a wipe and install AOKP (ethher from CWM or TWRP) MAKE A BACKUP OF YOUR CURRENT ROM!! That's important (hence caps ) - people are always on here complaining that they are soft bricked because of a bad download and not making a backup.
Click to expand...
Click to collapse
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
David522d said:
And flashing a rom with root therefor should give me root correct?
I sound like an idiot, but just to make sure
Click to expand...
Click to collapse
Yes, all of the roms will have root. Hit my thanks button if it works for you
paddycr said:
Yes, all of the roms will have root. Hit my thanks button if it works for you
Click to expand...
Click to collapse
Would it be easier to install CWM, then install TWR
David522d said:
Would it be easier to install CWM, then install TWR
Click to expand...
Click to collapse
I think both ways are the same. There's no correct answer to that. It depends on whether you would prefer to use CWM or TWRP.
Didn't want to hijack that other thread, so I thought a more explicity thread might help others.
So I followed http://www.youtube.com/watch?feature=player_embedded&v=iMYMR3_Vk8I and got my phone unlocked. I'm unsure what to do next to get a "stock" phone rooted. All I want is to have my phone rooted so I can run SU apps. There are a couple options from the tool, of which I'm not sure what is what:
1. Flash a Recovery (TWRP 2.1) - Not sure what this is for, should I flash it? What does it do?
2. Kernels - Do I download a kernel like: http://forum.xda-developers.com/showthread.php?t=1762537 and Flash Kernel?
3. Perm Root - From the name this sounds like what I want... but can I run it on my freshly restored/unlocked phone? Do I need to run this after one of the above (or both) steps?
1. Yes. A recovery is, put simply, a tool that can be used to flash things to your phone (e.g. custom ROMs and mods). You will need a recovery in order to achieve permanent root, so flashing the recovery is definitely a good idea.
2. The thread that you linked to does not contain a kernel, it contains a custom ROM. Since we do not have any customized kernels for this phone yet, skip the flash kernel step entirely. You may want to go back and use it if a kernel is developed that you prefer, but for now, there are no kernels to flash.
3. Perm root is the step that you want, but you need to flash the recovery first. The perm root script will run and then eventually boot you into the recovery, which you must use to flash SuperSU.zip which is the package that gives you root on your current ROM.
polarimetric said:
1. Yes. A recovery is, put simply, a tool that can be used to flash things to your phone (e.g. custom ROMs and mods). You will need a recovery in order to achieve permanent root, so flashing the recovery is definitely a good idea.
2. The thread that you linked to does not contain a kernel, it contains a custom ROM. Since we do not have any customized kernels for this phone yet, skip the flash kernel step entirely. You may want to go back and use it if a kernel is developed that you prefer, but for now, there are no kernels to flash.
3. Perm root is the step that you want, but you need to flash the recovery first. The perm root script will run and then eventually boot you into the recovery, which you must use to flash SuperSU.zip which is the package that gives you root on your current ROM.
Click to expand...
Click to collapse
Thanks polarimetric for explaining! Hopefully your explanations and my slight quirks below can help some others.
The TWRP reflash worked fine. I had an issue with the Perm Root though... for some reason the SuperSU.zip wasn't actually getting copied over to the phone before it was rebooted into recovery. I ended up mounting the sdcard and manually copying over SU/SuperSU.zip to my sdcard. At that point I ran Perm Root again (which in my case just reboots into recovery). From there I clicked "Install" and selected the /sdcard/SuperSU.zip file. It installed and rebooted.
Successfully rooted!
More advice pleae.
polarimetric said:
3. Perm root is the step that you want, but you need to flash the recovery first. The perm root script will run and then eventually boot you into the recovery, which you must use to flash SuperSU.zip which is the package that gives you root on your current ROM.
Click to expand...
Click to collapse
I flashed a recovery yesterday since I needed to recover. After that my endlessly booting appliance booted successfully.
Now I want to Root. I tried this using the Hasoon2000 thing yet and got a "Simply Brilliant" screen when I rebooted into recovery but then got could not connect message when I tried to permanently root.
Do I need to flash a different recovery?
Wow, this thread got my hopes up til I saw it was bumped.
As of several months ago, we lost the ability to root:
http://forum.xda-developers.com/showthread.php?t=1792514
So, until an exploit is found or verizon says we can do it, we can't root.
Hesacon said:
Wow, this thread got my hopes up til I saw it was bumped.
Click to expand...
Click to collapse
Yeah, the same thing happened to me. I tried HTCDev unlock last night and it didn't work, so I was very surprised to see that as the most recent post. Now I'm extremely disappointed.
i hope i am not getting anyone elses hopes up either.... but man i am disappointed
This phone isn't even relevant anymore... I don't know why Verizon gives a **** about locking us out.
I just used casual to root and unlock my note 2.i have root and it booted up on twrp but I want to check if I am unlocked bootloader. Is there a way I can check? In my about phone my status says normal
If the bootloader was not unlocked it would overwrite any changes you make to recovery and system files. So as long as you can reboot without losing TWRP or any custom ROM you've installed you're golden.
Unlocked Bootloader?
Jiggabitties said:
If the bootloader was not unlocked it would overwrite any changes you make to recovery and system files. So as long as you can reboot without losing TWRP or any custom ROM you've installed you're golden.
Click to expand...
Click to collapse
It's been a while for me since I rooted my phone, and I don't know if I unlocked my bootloader either... I have never installed a custom ROM, I only rooted so I could tether. But now that the new OTA update keeps trying to install itself, I need to fix this because it's extremely annoying. I read a thread that said I need to flash this: http://forum.xda-developers.com/showthread.php?t=2578458, but it said that I need my bootloader to be unloacked, and therein lies my question...
Am I thinking this through the correct way?
If you just want to stop the update notification fteeze SDM 1.0
James Mac said:
It's been a while for me since I rooted my phone, and I don't know if I unlocked my bootloader either... I have never installed a custom ROM, I only rooted so I could tether. But now that the new OTA update keeps trying to install itself, I need to fix this because it's extremely annoying. I read a thread that said I need to flash this: http://forum.xda-developers.com/showthread.php?t=2578458, but it said that I need my bootloader to be unloacked, and therein lies my question...
Am I thinking this through the correct way?
Click to expand...
Click to collapse
That is the correct thread. Easy way to check is to boot into recovery and see if there is a custom recovery installed. Power down your device, hold down the volume up + verizon button, then power up. Hold volume up + verizon button until you see the galaxy note 2 splash screen. If it boots into TWRP than you're still good. But you will probably want to update to the latest version of TWRP before you go installing any new roms.
Jiggabitties said:
That is the correct thread. Easy way to check is to boot into recovery and see if there is a custom recovery installed. Power down your device, hold down the volume up + verizon button, then power up. Hold volume up + verizon button until you see the galaxy note 2 splash screen. If it boots into TWRP than you're still good. But you will probably want to update to the latest version of TWRP before you go installing any new roms.
Click to expand...
Click to collapse
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
James Mac said:
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
Click to expand...
Click to collapse
The firmware update is done in ODIN and the ROM is done in TWRP.
James Mac said:
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
Click to expand...
Click to collapse
Yes start by transferring the files to your SD card.
The firmware package from that thread is meant to be flashed via ODIN. If you are not comfortable in flashing firmware via ODIN then use this in it's place... https://www.dropbox.com/s/lz29kvrvzfttfpu/MJ9ModemParams.zip This is a TWRP flashable version of the firmware.
Place the MJ9 Deodex and the modemparam.zip I linked to above on your SD card. Flash the ROM file first, then the modemparam.zip. Then clear cache/ dalvik and reboot. That should be all you need to do. If when you boot you don't get service, then you will need to go ahead and flash the firmware vid ODIN. Some users have no issues with the flashable version that I linked above, some users do.
Hey,
So I'm a noob at this and I tried to root my phone.
Got the Android unified toolkit from here:
http://forum.xda-developers.com/showthread.php?t=1746680
And followed wwjoshdew's video here:
https://www.youtube.com/watch?v=bPRWk8d0sUQ&hd
I picked the Allinone root option on the toolkit and proceeded. At the next step, when my phone entered download mode, it said I need to flash the recovery, recommended TWRP. But in the video, josh directly opens the root folder on odin and starts that. I did what josh did and that completed successfully. But when my device rebooted, on the toolkit, it said could not find recovery and I should try again. And there is no supersu on my phone either.
What have I done wrong? Do I need to flash the recovery before rooting?
Thanks in advance.
You have did only root.
But... a custom recovery is highly recommended (the better is Philz Recovery, CWM-based with some TWRP function).
Also a root manager is reccomended: Superuser is a great open source alternative to SuperSU, but I can't say you which is the best.
Ps actually I can't see video guide nor thread, my answer is based on what you said in the topic, so at first tell me if phone in "Settings > Info about" menu result with a custom firmware instead official. Otherwise you haven't even did root.
It's showing the stock version. No custom build. I just wanted to root so I could use apps like Greenify.
Do I need to do a flash the recovery first?
psyk789 said:
It's showing the stock version. No custom build. I just wanted to root so I could use apps like Greenify.
Do I need to do a flash the recovery first?
Click to expand...
Click to collapse
I didn't ask you for stock or custom rom. If you did root, in "Info about phone" the system status is showed as "custom".
Greenify should works also without root, but with limitations.
Recovery is highly recommended for you and also for some advanced apps who need this to flash something.
Then also a root manager for security reasons and a better device control is reccomended.
You can't stay without both, but I suggest to have both.
Ps without doing root you can't flash anything, nor via Odin! [emoji6]
It's showing Device Status as Official.
I understand that I need to root first before I can do anything. However when I followed the vid, it said before rooting if I had any recovery installed and needed me to install one first.
That's why I'm confused. I thought it was root first then flash recovery.
psyk789 said:
It's showing Device Status as Official.
I understand that I need to root first before I can do anything. However when I followed the vid, it said before rooting if I had any recovery installed and needed me to install one first.
That's why I'm confused. I thought it was root first then flash recovery.
Click to expand...
Click to collapse
You haven't to be confused: for example CF-Auto-Root do it and automatically flash recovery (CWM) and root manager (SuperSU).
You can flash them by downloading the device specific file (I9300).
If you want to change root manager simply uninstall SupetSU and download by Play Store Superuser (from Chainfire eh!), if you want dislike or want to update recovery, simply flash another via Odin or zip file.
Advice
My advice is this:
1. search for a MD5 file from Philz Touch like here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/
2. Download Odin3.09 from here: http://www.chip.de/downloads/Odin3_12992520.html
3. Go to download mode by pressing volume down, home button and power on
4. Flash it by clicking AP and select the MD5 file
5. boot to recovery pressing volume up, home button plus power on
6. go to philz settings, Reroot system
7. download SuperSu from market
Than you're done
Tkkg1994 said:
My advice is this:
1. search for a MD5 file from Philz Touch like here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/
2. Download Odin3.09 from here: http://www.chip.de/downloads/Odin3_12992520.html
3. Go to download mode by pressing volume down, home button and power on
4. Flash it by clicking AP and select the MD5 file
5. boot to recovery pressing volume up, home button plus power on
6. go to philz settings, Reroot system
7. download SuperSu from market
Than you're done
Click to expand...
Click to collapse
Without root you can't do anything. This option is useful for people who have maintained Philz Recovery on an unrooted system.
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
PytSkee said:
So I got the 5.12.10 update for the weekly developer ROM and it installed stock recovery over TWRP and unrooted my phone. The first time I rooted I managed to flash TWRP with stock recovery, but it isn't working this time. I've had a lot of trouble trying to install via ADB drivers. Help please?
Click to expand...
Click to collapse
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
elaurens said:
Did you rename TWRP to update.zip and put it on the root of the internal storage before flashing? If yes and it still failed, you'll have to give us a bit more info as to why it failed to flash (any error messages f.e.?). Should be fairly trivial to flash TWRP and SuperSU
Click to expand...
Click to collapse
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
PytSkee said:
It wasn't too difficult the first time, but the recovery seems to be using some sort of signature on the ROM's. All it tells me is that "Install update.zip failed! update.zip signature verification failed." It is named update.zip on the root of internal storage.
Click to expand...
Click to collapse
Hm, from what I've found on the miui forum, you're not the first one having this issue. These are the "possible" solutions I've gathered from a couple of threads.
1) Flash TWRP using fastboot (rename twrpxxxx.zip to recovery.zip and place it in the same folder as the fastboot executable):
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
2) Update your current ROM (stable/developer) to the latest version if that isn't the case yet and try flashing TWRP again trough the update app
3) Flash TWRP using Flashify
1. download flashify app from playstore and give root acces
2. download img of twrp for redmi 2 note and put in your sd card (I prefer sdext root folder)
3. Open flashify, select "recovery image", find the img file you've downloaded
4. confirm flash, wait until it's done
4) Re-download a copy of TWRP or use a different one (like this one for example)
Let me know how it went..
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
PytSkee said:
So I tried Flashify and every time I tried to use it, the app froze right before/after selecting the recovery image. I did, however, manage to make the ADB and fastboot methods work on my desktop PC. I have no idea what I did wrong before, maybe the wrong ADB drivers? Anyway, I did get it working, so thank you
Click to expand...
Click to collapse
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
timberwolf60 said:
Used windroid to do all these: http://en.miui.com/forum.php?mod=viewthread&tid=167882&extra=pag
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
I remember seeing this right after I ordered my phone. I had totally forgotten about it by the time I got it though, as it was more than a month later But thanks for reminding me, I already have it installed on my home PC!