Related
Can i install CWM on locked bootloader?
Ben Ling said:
Can i install CWM on locked bootloader?
Click to expand...
Click to collapse
Yes.
An 'exploit' has recently become available for ROOTING the Nexus 7 without unlocking the BOOTLOADER.
This 'exploit' works... I have tested it myself.
Until recently, I believed that because FASTBOOT wasn't an option (as a result of a LOCKED BOOTLOADER), there was no way of FLASHING anything.
Happily, I was disabused of this notion by bftb0... and I can confirm, you can indeed install CWM (or TWRP) with a locked BOOTLOADER.
-----------------------------
Here's how...
First, you need to run this 'exploit' to acquire ROOT.
Upon reboot, you should now be rooted, with Chainfires SuperSU package and associated SU binary installed.
It's important that you are ROOTED before you proceed.
Next, get Android Terminal Emulator from PlayStore.
Download a CUSTOM RECOVERY .img of your choice... either CWM (Both 'Grouper' and 'Tilapia' variants are available)...
...or TWRP for 'Grouper' (N7 WiFi) or TWRP for 'Tilapia' (N7 3G).
Rename it to recovery.img... and copy it to the root of the Nexus 7's internal storage (emulated SD card).
In Terminal Emulator, run the following command...
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Upon completion of this command, shutdown and reboot your device into the BOOTLOADER, and from there, boot into your CUSTOM RECOVERY... in pretty much the same way had you FASTBOOT FLASHED it.
-----------------------------
You are now free to flash whatever ROMs or kernels you like.
However, a word of caution... because the BOOTLOADER remains locked, FASTBOOT is strictly off limits; it simply won't work.
So the first thing you should do after flashing TWRP or CWM is...
*** MAKE A NANDROID BACKUP ***
If the device becomes 'wedged/bootlooped' as a result of some ROM flash gone wrong, then you will have no choice but to unlock the BOOTLOADER (with full wipe) in order to fix it.
But if you have a NANDROID backup... piece of cake... just restore.
-----------------------------
Credits and kudos must go to XDA members, nhshah7, who made this 'exploit' available and bftb0, whose post pointed me in the right direction, with regard to the 'dd' command.
-----------------------------
I can confirm all of this works... my Nexus 7 is currently rooted, running a custom recovery (TWRP), with a custom ROM and Kernel (see sig) installed - all sitting behind a LOCKED BOOTLOADER.
...no Factory Reset (wipe) required...
...and no Unlocked Padlock Symbol upon boot.
Rgrds,
Ged.
Previously I installed cwm and can boot,just 1 time.
I tried to boot into but nothing.
What to do?
Sent from my Sony Xperia™ sola using XDA Premium App
@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"
SSyar said:
@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"
Click to expand...
Click to collapse
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.
GedBlake said:
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.
Click to expand...
Click to collapse
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium
Ben Ling said:
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium
Click to expand...
Click to collapse
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.
GedBlake said:
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.
Click to expand...
Click to collapse
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App
Ben Ling said:
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
Shut down the tablet completely.
Press and hold the VOL DOWN button... whilst holding, press the POWER button.
This will boot you into the BOOTLOADER.
Using the VOL buttons, navigate to RECOVERY.
Press the POWER button to select.
Rgrds,
Ged.
Just tested this method... again... (using dd to install a Custom Recovery)... with both CWM and TWRP... and in both instances, the installations survived a reboot. So I'm puzzled why there seems to be a problem here.
---------------------------------
I have semi-automated the process in order to avoid typing long complicated commands into Android Terminal Emulator. A process, which, by it's nature, is subject to typographical error.
Here's how...
Download the Custom Recovery of your choice to your Nexus 7.
Rename it to recovery.img
Copy it to the root of the emulated SD card (internal storage).
---------------------------------
Download this script file...
writerecovery.zip
Unzip and copy it to the root of the emulated SD card (internal storage).
(Alongside the recovery.img).
---------------------------------
Install Script Manager from Google Playstore.
Open Script Manager and locate the script file writerecovery.sh on the root of the emulated SD card.
Press ENTER on it...
Select OPEN AS... Script/Executable...
Select SU (root) from the toolbar...
Select Run...
The script will now execute the following command...
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
...writing the recovery.img to the recovery partition.
See attached thumbnails for the sort of thing you should expect to see.
---------------------------------
I have tested this method several times... switching between CWM and TWRP. And performing multiple reboots, to ensure that the Custom Recovery 'stuck' in each instance.
---------------------------------
Hope this works... if it doesn't... then I'm at a loss to explain why.
Maybe somebody with more technical knowledge can assist.
All I know, is it works for me... on my Nexus 7.
Rgrds,
Ged.
well i installed recovery using goo manager ,.,. got this response from other thread and is working for me ,.,., goo manager also has the option to restart in recovery so really good for me
Help with my Condition
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.
junisheikh said:
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.
Click to expand...
Click to collapse
Hi, junisheikh...
To answer your question...
junisheikh said:
"WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?"
Click to expand...
Click to collapse
Yes, you should be able to.
---
The bootloader lock state is irrelevant when it comes to flashing stuff via a Custom Recovery (such as CWM or TWRP).
All an unlocked bootloader does, is it allows the device to accept fastboot flash commands from a connected PC or Mac, and which is the usual way of flashing a Custom Recovery, and then subsequently rooting it.
I would, however, advise against using CWM. ClockWorkMod Recovery is old and hasn't been updated for quite some time, and may cause problems.
Instead, you should take a look at TWRP (TeamWin Recovery Project). This Custom Recovery has a better user interface, and is less likely to cause you problems.
---
Although your bootloader is locked, you have managed to acquire root via KingRoot... which means you can flash a Custom Recovery with the Flashify app...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
This app allows you to flash Recoveries and Boot images (stock and custom) directly from the device itself, providing the device is rooted. The free version of Flashify has a limit of 3 flashes per day. This shouldn't be a problem though... Custom Recoveries aren't something you generally flash on a regular basis.
(See my attached screenshots for a flavour of how Flashify works.)
---
You can find the latest version of TWRP for the Nexus 7 WiFi model here...
http://techerrata.com/browse/twrp2/grouper
Download to your Nexus 7, and use the Flashify app to flash.
And then download whatever Custom ROM+GAPPS you like, and flash via TWRP.
Incidentally, the NANDROID backup you've already created with CWM is NOT compatible with TWRP. So you'll need to create a new NANDROID backup, should you choose to flash TWRP.
---
junisheikh said:
This is going to be a one way ride for me, if I brick I have a paperweight.
Click to expand...
Click to collapse
This is possible, because you don't have access to fastboot (due to your broken USB port) you won't be able to fastboot flash back to Google Factory stock should you not be able to boot Android (for whatever reason) after flashing some Custom ROM. But providing you have a NANDROID backup and a Custom Recovery (CWM or TWRP) installed, you **should** be able to recover from softbricks such as bootloops. But having said that, I would tread carefully.
Hope this helps, and good luck.
Rgrds,
Ged.
Hello.
Im looking to get some help with an issue i have on my gs4 att, stock + root.
My device keeps loosing root access after a while.
I have unrooted and flashed stock 4 times, but i cant figure out the problem and cant find any information on the fourms.
What version stock?
TheAxman said:
What version stock?
Click to expand...
Click to collapse
stock 4.2.2 UCUAMDL
do do you think it ha anything to do with removing stock samsung apps like hub and att [email protected]?
gsr101 said:
Hello.
Im looking to get some help with an issue i have on my gs4 att, stock + root.
My device keeps loosing root access after a while.
I have unrooted and flashed stock 4 times, but i cant figure out the problem and cant find any information on the fourms.
Click to expand...
Click to collapse
Here I did it before and I never got a message says root access has been lost.
1. Odin it back
2. Root by using causal method
3. When phone reboot itself into recovery TWRP
4. Don't back up just reboot into welcome screen
5. It should ask you to install superuser, just install it
6. Finally, reboot into recovery and make nandroid back up.
On step four, I back up by using nandroid before superuser install. When I change rom, message always telling me I have lost root access quite often this way.
LeonKnight12 said:
Here I did it before and I never got a message says root access has been lost.
1. Odin it back
2. Root by using causal method
3. When phone reboot itself into recovery TWRP
4. Don't back up just reboot into welcome screen
5. It should ask you to install superuser, just install it
6. Finally, reboot into recovery and make nandroid back up.
On step four, I back up by using nandroid before superuser install. When I change rom, message always telling me I have lost root access quite often this way.
Click to expand...
Click to collapse
thats usually what i do, i tried 4 times. It doesnt ask me to install su, its already installed.
i might just have to update and wait for new root method.
Download a superuser/supersu zip file and flash it through your twrp/cwm recovery and reboot.when I first rooted my I337 ATT S4
It would loose just as I would enter recovery and my recovery would ask if I wanted to fix it before rebooting. After flashing the supersu zip file
I have had zero issues with root.
jball said:
Download a superuser/supersu zip file and flash it through your twrp/cwm recovery and reboot.when I first rooted my I337 ATT S4
It would loose just as I would enter recovery and my recovery would ask if I wanted to fix it before rebooting. After flashing the supersu zip file
I have had zero issues with root.
Click to expand...
Click to collapse
thanks for the share, do you happen to have link to the file or thread?
Sorry for the late reply I don't get notification for this site.I Google everything and most of the time it will bring u to xda for what u search .I don't post links cause I don't want trouble from nobody thinking I'm try n to take credit if u know what I mean.just helpful words
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
tigas68 said:
Hi.
I had my nexus 4 with 4.2.2 stock rom rooted with the Nexus Root toolkit from WUG. TWRP recovery also instaled.
Last night using this software, i flash the 0.84 radio in order to install the factory image of the new 4.3 android (downloaded from google developers site).
I also did that using the Wug software.
Now i already have the 4.3 android on my nexus, but lost root and also twrp recovery. I can´t get to recovery mode and since i'm not rooted anymore, can´t flash any zip, includind the SU from chain fire.
How can i get my recovery mode back and root the phone again??? The phone is unlocked!
thanks.
Click to expand...
Click to collapse
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
thanks. :good:
tigas68 said:
thanks. :good:
Click to expand...
Click to collapse
Still isn't working...
When i tried to fastboot the recovery img the device turns off and never turns on again on is own!
Help please!
I like my root...!
here's the screens of waht happens.
This his what happens when i try to go into recovery mode...
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
zephiK said:
first of all, dont ever use a toolkit.
1. turn phone off
2. plug the phone in via usb
3. hold volume down + power until a screen pops up.. you're in bootloader mode.
4. you better have adb / fastboot environment setup, if not then google and find out how to do it.
5. fastboot flash recovery <nameofrecovery>.img
6. volume down to recovery
7. flash superuser zip
Click to expand...
Click to collapse
zephiK,
Already done that! I flashed the CWM recovery throught fastboot. The device turned off. When i turn it on again and tried to go into recovery mode, so i can flash the SU from chain fire, but got the image on my post!
The phone is unlocked!
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Johnsonyc said:
I can confirm the SU work on 4.3 Stock ROM for TWRP I recommend to flash the CWM first and then replace with TWRP it will be easier.
Click to expand...
Click to collapse
I used the sctock rom downloaded from the google developers website!
Johnsonyc said:
That mean you didn't flash the CWM to your phone ~ The image you showing is Official Recovery Mode Screen!
Click to expand...
Click to collapse
What he said. The recovery flash isn't going through.
Sent from my Nexus 4 using Tapatalk 4 Beta
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
spicediablo said:
Use adb to flash SU. But I've heard SU is not working well with 4.3. Find the instructions below:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
kzoodroid said:
Google fixed the vulnerability that was used to gain superuser rights in Android. Chainfire has a semi working version of SuperSU but from what I read only TWRP can flash it properly. On Koush's Google+ feed he says Chainfire had to do a real hack job to get superuser working, thus why it's not working well. He is not sure if he can even get his own open source superuser to work again and made no mention of fixing CWM Recovery to be able to flash SuperSU. As I no longer really need root for any thing I'll just wait and see what Koush can come up with.
Click to expand...
Click to collapse
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Johnsonyc said:
I am flash my SuperSU from CWM it does work. I am working so hard to get off the ROOT ! But Root Explorer slap my face, I can't live without it.
Click to expand...
Click to collapse
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
sn0warmy said:
Yeah, I've read the same. In the meantime I've really just learned to love stock Android for what it is. At least until one of the mad geniuses finds a 100% working fix.
Agreed. The only main thing I need root for is to use Root Explorer. I can't believe after all the time I still use the hell out of that app. :laugh:
Click to expand...
Click to collapse
I don't even really use root explorer anymore just like having the ability to make nandroid backups. But after doing a clean install of 4.3 in fastboot and it only took 30 minutes from start to finish including app and data restores nandroids to me are not that useful anymore (I don't flash custom ROMs anymore). Google automatically re-installed all my apps as soon as I reconfigured my WIFI, they also restored my APN and my work WIFI settings but not Bluetooth. And I used Helium to restore the user app data and all my texts and helium doesn't need root access to work.
Here is the start of Koush's post on Google+ where he talks about superuser on 4.3.
I finally had a chance to dig into seeing why Superuser is broken on Android 4.3. https://android.googlesource.com/platform/dalvik/+/9907ca3cb8982063a846426ad3bdf3f90e3b87c2
Basically /system is mounted as nosuid to any zygote spawned process (ie, all Android apps). Root will still continue to work via adb shell, etc.
This is a pretty nasty change. It seems that SuperSU works around this by replacing install-recovery.sh to run a su daemon that pipes subsequent through it. Pretty hacky, but understandable why it was done this way.
Will need to look into how to do this in a less invasive fashion, if that is even possible. Of course, if building from source, this change can simply be reverted.
Here's a better explanation about superuser from Android Police.
http://www.androidpolice.com/2013/0...n-but-chainfires-supersu-works-and-heres-why/
Rooting for me is used for restoring my apps and stuffs using titanium backup. Another useful thing about rooting is the ability to check saved wifi passwords.
Just install twrp from fastboot and then flash the su zip file in twrp
Sent from my Nexus 4 using Tapatalk 2
EddyOS said:
Why do people seem to think it's any different than with 4.2.2? It's the same bloody procedure!
Now, if you were ***** enough to use a toolkit and not learn how to use fastboot/adb yourself then that's your own fault but seriously there are guides everywhere on how to flash a custom recovery and it's the EASIEST thing in the world
Click to expand...
Click to collapse
@EddyOS
Your answer is what forums are not about! Instead of helping you had an atitude of an ass...!
@ Everyone else
After 5 or 6 attemps, doing it by the book, the CWD worked and i now have a Recovery mode! I didn´t did anything different, so i couldn´t really understand what went wrong before... SU from chainfire works perfectly! It´s now Rooted! And yes, the tuturials are idiot proof!
There´s something that´s bothering my mind... I can´t unistall some trash that cames with the 4.3 version using titanium backup, because he can´t find the apk files...! I could do it with the 4.2.2 version, but not with this one. I'm using the deoxed version.
Does anyone has the same problems?
I accidentally tried doing a factory reset, and flashing an incorrect rom. So I lost the stock rom, and have no other rom to use. I tried using TWRP to flash ASUS's stock firmware from asus's support website, under firmware. Using firmware file: "UL-Z00T-WW-1.16.40.763-user.zip"
but TWRP tells me "E:Error executing updater binary in zip '/sdcard/TWRP/Stock.zip'
Error flashing '/sdcard/TWRP/Stock.zip"
I still have access to both adb, fastboot, and TWRP but I cant get an OS to install.
Any help with this would be greatly appreciated, haven't even had this phone a day yet, and already may have broken it.
I don't have an answer to your question , just got this phone yesterday and am in the process of figuring out how to root and install a custom recovery for this specific device.. I have found many methods to root but none for my specific model. I think you have the same model as I do and was hoping you could lead me to the place that will give me the files I need.. the box my phone came in has the model as ASUS_Z00TD (ZE551KL).. Sorry I wasn't of any help to you, hope you manage to figure out how to flash something that will get your device running again!
tmjm28 said:
I don't have an answer to your question , just got this phone yesterday and am in the process of figuring out how to root and install a custom recovery for this specific device.. I have found many methods to root but none for my specific model. I think you have the same model as I do and was hoping you could lead me to the place that will give me the files I need.. the box my phone came in has the model as ASUS_Z00TD (ZE551KL).. Sorry I wasn't of any help to you, hope you manage to figure out how to flash something that will get your device running again!
Click to expand...
Click to collapse
I used @rczrider 's post in this thread, and was able to get root. http://forum.xda-developers.com/zenfone-2-laser/general/wip-root-ze550kl-1-16-40-763-t3275760/page3, good luck!
willrox15 said:
I accidentally tried doing a factory reset, and flashing an incorrect rom. So I lost the stock rom, and have no other rom to use. I tried using TWRP to flash ASUS's stock firmware from asus's support website, under firmware. Using firmware file: "UL-Z00T-WW-1.16.40.763-user.zip"
but TWRP tells me "E:Error executing updater binary in zip '/sdcard/TWRP/Stock.zip'
Error flashing '/sdcard/TWRP/Stock.zip"
I still have access to both adb, fastboot, and TWRP but I cant get an OS to install.
Any help with this would be greatly appreciated, haven't even had this phone a day yet, and already may have broken it.
Click to expand...
Click to collapse
Happy to know that it works for you.
Whenever you got stuck in this situation, just flash stock recovery & you will able to flash stock rom again.
rajlko said:
Happy to know that it works for you.
Whenever you got stuck in this situation, just flash stock recovery & you will able to flash stock rom again.
Click to expand...
Click to collapse
Do yo mean this stock recovery? http://forum.xda-developers.com/showpost.php?p=64441364&postcount=9
How do I flash it? just "fastboot flash recovery stock_recovery.img" ?
If so, I've tried that, and TWRP still boot when I try to enter recovery. Also, once I've flashed the stock recovery, do I just place the firmware on the root of the sdcard as 'update.zip' and try to install it from there?
Thanks for your help already, and sorry about the repetitive questions!
willrox15 said:
Do yo mean this stock recovery? http://forum.xda-developers.com/showpost.php?p=64441364&postcount=9
How do I flash it? just "fastboot flash recovery stock_recovery.img" ?
If so, I've tried that, and TWRP still boot when I try to enter recovery. Also, once I've flashed the stock recovery, do I just place the firmware on the root of the sdcard as 'update.zip' and try to install it from there?
Thanks for your help already, and sorry about the repetitive questions!
Click to expand...
Click to collapse
This is not stock recovery, this one is twrp recovery.
once you flashed stock recovery, flash stock rom as you do it.
This one is stock recovey
http://forum.xda-developers.com/showpost.php?p=64440791&postcount=8
rajlko said:
This is not stock recovery, this one is twrp recovery.
once you flashed stock recovery, flash stock rom as you do it.
This one is stock recovey
http://forum.xda-developers.com/showpost.php?p=64440791&postcount=8
Click to expand...
Click to collapse
Thank you! That worked perfectly!!
hello guys,
is there any custom frimeware for the galaxy grand prime sm-g532f ? i looked everywhere but can't find one.
i need one because there is no more space in my phone, the system took almost everything, 6.5go of the 8 availble, so i can't install big apps even with an sd card ! any solution ?
i was about to install a stock rom, but someone told me that it will take the same space as my current rom .
thank you.
I don't think any developer is interested in this device, it could be due to non-availability of unlocked bootloader, firmware sources, etc. I am thinking of getting rid of mine and move to another device that supports open hardware/software.
In possible solution if you managed to root it the use system app remover to get rid of Samsung bloat.
Good luck.
sga-pingo said:
I don't think any developer is interested in this device, it could be due to non-availability of unlocked bootloader, firmware sources, etc. I am thinking of getting rid of mine and move to another device that supports open hardware/software.
In possible solution if you managed to root it the use system app remover to get rid of Samsung bloat.
Good luck.
Click to expand...
Click to collapse
yes i have the same thought there will be no custom rom did you tried to install a stock rom ?
did you tried to install a stock rom ?
Click to expand...
Click to collapse
All phones when you unbox are on factory ROM (aka stock ROM). I think you are referring to rooting and installing custom recovery, I failed and phone always go into boot-loop making me to re-flash stock boot and recovery images.
sga-pingo said:
All phones when you unbox are on factory ROM (aka stock ROM). I think you are referring to rooting and installing custom recovery, I failed and phone always go into boot-loop making me to re-flash stock boot and recovery images.
Click to expand...
Click to collapse
thanks, i think i will try to root my phone, maybe it will work for me. my last hope :/
Please post your results, I am hopeless with this severely bloated device.
Update:
Managed to root using TWRP.
1. Install TWRP recovery.img using ODIN (Windows) or Heimdall (Linux) including SU. Details in this thread:
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j2-t3616589
Reboot to TWRP > format Data partition > while you are connected to PC > copy SU.zip to data and flash it.
2. Get SU.zip from here;
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
Good luck.
sga-pingo said:
Update:
Managed to root using TWRP.
1. Install TWRP recovery.img using ODIN (Windows) or Heimdall (Linux) including SU. Details in this thread:
https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j2-t3616589
Reboot to TWRP > format Data partition > while you are connected to PC > copy SU.zip to data and flash it.
2. Get SU.zip from here;
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
Good luck.
Click to expand...
Click to collapse
i didn't have a lot of time these days to search for a working "rooting methode", so thank you very much.