Database Info

How to upgrade to new latest Asus firmware through custom recovery

Check the device firmware type by going to Setting - about tablet - built number
Download the right firmware pack for your device.
http://www.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_Infinity_TF700T/#download
Now extract the zip file and you will have another zip file.
Rename that zip file as "EP201_768_SDUPDATE" and place it to an external sd card if you do not have a custom recovery. If you are rooted and unlocked plus you have a custom recovery you don't need to rename it you can place it in internal sd is well.
Now turn off your device. Hold power button including the volume down button and enter custom recovery. For stock recovery it should detect it automatically and will install. once in custom recovery clear your cache and install the file with the name above or whatever name you have. once installation is complete. reboot the system be patient and you have the latest update.
You can obtain root easily using this method.
Just download the DebugfsRoot_Generic_v2.3.zip file from here
http://forum.xda-developers.com/show....php?t=1706588
extract the content and run RootDebugfs, then follow the on screen instruction and you will have root.
Make sure you have USB debugging on.
To get custom recovery. Download goomanager from playstore and you can install TWRP recovery from the option list. which is Option - install OpenRecoveryScript.
I am not responsible if you mess up your device. do these at your own risk. Nonetheless these steps work perfectly for me.

Renaming is not needed.

lafester said:
Renaming is not needed.
Click to expand...
Click to collapse
Exactly thats for people without custom recovery

Isn't this already covered here? http://forum.xda-developers.com/showthread.php?t=1833212
Sent from my EVO using xda premium

rizanx said:
Exactly thats for people without custom recovery
Click to expand...
Click to collapse
does the update push the stock recovery as well?
and root is lost right?

Yes and yes.
Sent from my HTC One X using xda premium

odeccacccp said:
does the update push the stock recovery as well?
and root is lost right?
Click to expand...
Click to collapse
Yes you will lose root.
But you can obtain root easily using this method.
Just download the DebugfsRoot_Generic_v2.3.zip file from here
http://forum.xda-developers.com/showthread.php?t=1706588
extract the content and run RootDebugfs, then follow the on screen instruction and you will have root.
oh and make sure you have USB debugging on.

sorry for the mix up. yes you do lose recovery. Download goomanager from playstore and you can install TWRP recovery from the option list.

rizanx said:
Through custom recovery stock recovery is not pushed! you will still have custom recovery. You will only lose root.
Click to expand...
Click to collapse
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.

Pretoriano80 said:
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.
Click to expand...
Click to collapse
+1 You WILL lose custom recovery with this method. This has all been covered before...
Sent from my EVO using xda premium

Pretoriano80 said:
Wrong, flashing an official rom will make you loose the custom recover too, you will have a clean stock rom once you do that. AND also this thread has nothing to share with the development forum.
Click to expand...
Click to collapse
Thanks for clear up.

MysticMgcn said:
Isn't this already covered here? http://forum.xda-developers.com/showthread.php?t=1833212
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Where in there? Can;t find it?
1) If I am on a custom ROM can I flash the new update or I have to go back to STOCK first?
2) What's the big deal with loosing CWR and Root, it takes like 2 min to put it back, I mean there is another way to not loose it?
Thanks

I also have a question! Will this allow for OTA updates even if our bootloader is unlocked? And will we be able to flash the JB update from ASUS manually if not? Anyone know?

GRIM1337 said:
I also have a question! Will this allow for OTA updates even if our bootloader is unlocked? And will we be able to flash the JB update from ASUS manually if not? Anyone know?
Click to expand...
Click to collapse
No. when you unlocked it clearly stated no more ota updates for you.
Yes. of course you can flash manually just like any other rom.

odeccacccp said:
Where in there? Can;t find it?
1) If I am on a custom ROM can I flash the new update or I have to go back to STOCK first?
2) What's the big deal with loosing CWR and Root, it takes like 2 min to put it back, I mean there is another way to not loose it?
Thanks
Click to expand...
Click to collapse
You don't need to have stock rom. As long as you have the stock kernel your ok. You will of course lose custom recovery but its easy to download again as i have mentioned in my first post.
There is a lengthy way to do this. But why do that when it takes you literally 2 minute to root it with DebugfsRoot .
Hope it went well for you.

Lost LTE signal after rooting. Please help!

Hi, I recently decided to root my Nexus 5 using this guide on youtube: /watch?v=J1AKqrrf-5o
But after I'm all done with the rooting process, I noticed that my Nexus 5 has lost its LTE signal. Now it onlyy uses 3G. I managed to put it back on LTE by doing: *#*#4636#*#* and changed my prefered network, but by doing so, I lost my service with T-Mobile. Can't call or send messege with LTE on.
Please help me! I'm very new to Android and rooting but this first experience is not so good. Can you tell me what went wrong? Also, I rooted using the Linux guide.

Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
You might need this first. http://forum.xda-developers.com/showthread.php?p=47156064

jd1639 said:
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).

danny2146 said:
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
Click to expand...
Click to collapse
That's why I have you the second link

If all else fails flash the google stock images

Agreed. A root alone should not have caused an issue with your radio unless something went incorrectly. I would ( personally ) flash Google's stock nexus images and then possibly try again. Gaining root access can be done different ways, you may need to read into other alternatives...

I don't know. I use the ChainFIre CF Auto root on Ubuntu. I did unrooted the device earlier and was able to get LTE and service to work. Though after I use this samw method again, LTE stopped working properly, so I guess something is wrong with this method. Will try the "standard" method later though, if I can get a hold of a windows computer.

Let's back track a bit. What is the goal with root? Are you wanting to keep a custom recovery? What network are you using?
If you are going to just root stock and not go for a custom rom, I'd just flash a custom recovery via fastboot then boot to recovery and flash the SuperSU zip from Chainfire. At that point, you're rooted stock. If you decide to take an OTA update then you'll just need to make sure that you have the stock recovery installed. However, it's just as easy to flash the update when one of our devs packages it as a rom zip to flash via custom recovery, if not easier really.

Frankly, at this point my knowledge about android phone is still very hazy as this is acually my first ever phone, let along rooting, but I am eager to learn. So what's wrong if I didn't get a custom recovery? I just followed the instruction that they (chainfire autoroot) have for Linux and got this. Dunno if it was something in my phone nor the root. I am on T-Mobile BTW.

Yea, I'm baffled by that method affecting anything to do with service. It should be one of the least intrusive ways to root. However, weird things happen. So where are we now? Are you still rooted with the service issues? Which update / baseband are you on? You have the correct T-Mobile APNs? Have LTE(Recommended) selected under Preferred Network Mode in Settings / More... /Mobile Networks? Shouldn't really be necessary to mess with changing stuff in the Hidden Menu in this instance.

I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...

danny2146 said:
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
Click to expand...
Click to collapse
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?

es0tericcha0s said:
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
Click to expand...
Click to collapse
I used the stock flashing method. I only unrooted it though, not lock the boot loader.

danny2146 said:
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
Click to expand...
Click to collapse
Ok. So at this point, I would have the SuperSU zip (contains the SuperSU app and su binary) http://download.chainfire.eu/381/SuperSU/UPDATE-SuperSU-v1.91.zip on your phone, then fastboot a custom recovery like TWRP http://techerrata.com/browse/twrp2/hammerhead (fastboot flash recovery nameofrecovery.img), boot into recovery, and flash the zip. No need to wipe anything. Should just be able to flash and go. Then open SuperSU and make sure the binary is updated.

I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?

danny2146 said:
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
Click to expand...
Click to collapse
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.

es0tericcha0s said:
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
Click to expand...
Click to collapse
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!

danny2146 said:
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
Click to expand...
Click to collapse
Just boot into recovery and see what you have.

If you used CF-Root, then it would not have installed a custom recovery. This is something that you would have done on your own and not likely to have forgotten. If you root access is working properly, I'd suggest installing TWRP from the GooManager app as it's pretty easy and no PC required.
http://teamw.in/project/twrp2/205
Then make a nandroid back up of your phone and make sure to back up the EFS folder too and save them to a safe place. You can back that up in TWRP or from the method described here:
http://forum.xda-developers.com/showthread.php?t=2514095

Let's back up here. Why do you think you need root if you have no idea what you are doing? Are you just rooting because you can or do you have a real purpose?
Sent from my Nexus 5

Losing root after reboot

I seem to be losing root after rebooting. This is a major issue for me as I have the Z3 set up with no soft keys and navigate using GMD Gesture. So when root dissappears I cannot navigate around the phone or exits apps etc.
I have narrowed it down to a potential issue with 'unicon' xposed module, which basically changes the icons at system level. I cannot say for sure that this is causing the issue but it looks very likely.
Also without root I cannot uninstall Supersu or Xposed, but with many reboots and managing to disable and then re-enable Supersu through system settings I now have root again. But as soon as I reboot it's gone again.
Very strange issue never encountered this before.
Some info about my Z3:
ANDROID 4.4.4
LOCKED BOOTLOADER
EDIT:
i have noticed a few more issues:
power button on side is not responding any more.
root is working now that supersu is uninstalled
i cannot boot into recovery both manually and through NDR utilities
If you are in a position to help, please please please do!

You need to disable the RIC
If you are unsure just flash an advanced stock kernel from the development section.

gregbradley said:
You need to disable the RIC
If you are unsure just flash an advanced stock kernel from the development section.
Click to expand...
Click to collapse
What will this achieve? I have completely killed an Xperia Z before and want to make 100% sure before i proceed.
Also please notice my bootloader is LOCKED, i accidentally stated it was unlocked in the OP. I cannot flash a kernel with a locked bootloader can i?
I have noticed another few issues:
power button on side: isn't responding any more.
root is working now that supersu is uninstalled
i cannot boot into recovery both manually and through NDR utilities

rm83855 said:
What will this achieve? I have completely killed an Xperia Z before and want to make 100% sure before i proceed.
Also please notice my bootloader is LOCKED, i accidentally stated it was unlocked in the OP. I cannot flash a kernel with a locked bootloader can i?
I have noticed another few issues:
power button on side: isn't responding any more.
root is working now that supersu is uninstalled
i cannot boot into recovery both manually and through NDR utilities
Click to expand...
Click to collapse
I read your post when you said you had an unlocked boot.
No you cannot flash a custom kernel.
OK, you will need to ensure you installed the recovery correctly.
Run the installer again for dual recovery and post the out put here.
If it goes correctly it will sort everything out for you

gregbradley said:
I read your post when you said you had an unlocked boot.
No you cannot flash a custom kernel.
OK, you will need to ensure you installed the recovery correctly.
Run the installer again for dual recovery and post the out put here.
If it goes correctly it will sort everything out for you
Click to expand...
Click to collapse
I have just this minute managed to correctly install the recovery. Will i be good from now on?
How do you recommend installing Supersu? When i try to install through the recovery the phone just reboots normally. Should i install a flshable zip instead of installing from playstore.
How will i prevent this happening again?

rm83855 said:
I have just this minute managed to correctly install the recovery. Will i be good from now on?
How do you recommend installing Supersu? When i try to install through the recovery the phone just reboots normally. Should i install a flshable zip instead of installing from playstore.
How will i prevent this happening again?
Click to expand...
Click to collapse
Flash this in recovery
http://download.chainfire.eu/695/SuperSU/

gregbradley said:
Flash this in recovery
http://download.chainfire.eu/695/SuperSU/
Click to expand...
Click to collapse
thanks i managed to flash it. The power button issue persists. The screen will stays on and the power button will not turn it off however If i hold it in i get the power menu?
EDIT: I reinstalled Xposed, rebooted and once again root is gone

rm83855 said:
thanks i managed to flash it. The power button issue persists. The screen will stays on and the power button will not turn it off however If i hold it in i get the power menu?
EDIT: I reinstalled Xposed, rebooted and once again root is gone
Click to expand...
Click to collapse
I would flash a stock FTF and re root again from the beginning. You have something wrong. Then install recovery and flash a pre-rooted version of the latest ROM

gregbradley said:
I would flash a stock FTF and re root again from the beginning. You have something wrong. Then install recovery and flash a pre-rooted version of the latest ROM
Click to expand...
Click to collapse
i was afraid you would say this Can you tell me if Lollipop is rootable or should i stick with KK?
Thank you for your help!

gregbradley said:
I would flash a stock FTF and re root again from the beginning. You have something wrong. Then install recovery and flash a pre-rooted version of the latest ROM
Click to expand...
Click to collapse
i actually just remember about a TWRP backup i did the day i rooted the phone, i have this saved on my pc would this work, or would it be better to start from scratch?

rm83855 said:
i was afraid you would say this Can you tell me if Lollipop is rootable or should i stick with KK?
Thank you for your help!
Click to expand...
Click to collapse
There is no lollipop for any sony phones so no one knows
Unless you mean custom roms and of course they are rootable.
Just flash a .93 FTF, root, install recovery and then flash a prerooted zip made with PRFCreator.
EDIT
If you think that backup does not have this issue on it then restore it.
However, if you are unsure its best to start again and then you can eliminate the problem.

gregbradley said:
There is no lollipop for any sony phones so no one knows
Unless you mean custom roms and of course they are rootable.
Just flash a .93 FTF, root, install recovery and then flash a prerooted zip made with PRFCreator.
EDIT
If you think that backup does not have this issue on it then restore it.
However, if you are unsure its best to start again and then you can eliminate the problem.
Click to expand...
Click to collapse
i backed up the day i rooted so should be good. I somehow had the opinion Sony were among the first to process updates, no idea where i got that idea from
Just restored and everythings working great, although all my lovely zoopers are gone
Thanks for your help man, appreciated

gregbradley said:
There is no lollipop for any sony phones so no one knows
Unless you mean custom roms and of course they are rootable.
Just flash a .93 FTF, root, install recovery and then flash a prerooted zip made with PRFCreator.
EDIT
If you think that backup does not have this issue on it then restore it.
However, if you are unsure its best to start again and then you can eliminate the problem.
Click to expand...
Click to collapse
so everything was great, then i installed the following apps:
GMD Gesture
Udn pro (xposed)
Xblast (Xposed)
Flat bars (xposed)
I now have no root again. Completely sucks i just set the goddamn phone up again and now back to square one!
How can one of these apps have the power to remove root?! my backup works flawlessly and i can reboot and still have root, it is 100% one of these apps

rm83855 said:
so everything was great, then i installed the following apps:
GMD Gesture
Udn pro (xposed)
Xblast (Xposed)
Flat bars (xposed)
I now have no root again. Completely sucks i just set the goddamn phone up again and now back to square one!
How can one of these apps have the power to remove root?! my backup works flawlessly and i can reboot and still have root, it is 100% one of these apps
Click to expand...
Click to collapse
It will not be removing root... but it might be messing with it.
Its a slow process but try this
Restore the backup and setup again, then take a backup before you insall those 4, then start adding them one at atime, take a backup in between each one so you can restore it. It may be that on their own they are fine but together they could conflict.
At any point you may want to take a logcat and share it... Just a thought..

gregbradley said:
It will not be removing root... but it might be messing with it.
Its a slow process but try this
Restore the backup and setup again, then take a backup before you insall those 4, then start adding them one at atime, take a backup in between each one so you can restore it. It may be that on their own they are fine but together they could conflict.
At any point you may want to take a logcat and share it... Just a thought..
Click to expand...
Click to collapse
the thing is ive managed to get rid of xposed and all modules and now supersu is mucked up and wont stick after a reboot.
Therefore one of these apps must not only be messing with root but changing some system file to make Supersu not stick after a reboot?
Does that make sense? My responses may well go downhill from here, I'm losing the will to live
I will try that and post back. Thanks

rm83855 said:
the thing is ive managed to get rid of xposed and all modules and now supersu is mucked up and wont stick after a reboot.
Therefore one of these apps must not only be messing with root but changing some system file to make Supersu not stick after a reboot?
Does that make sense? My responses may well go downhill from here, I'm losing the will to live
I will try that and post back. Thanks
Click to expand...
Click to collapse
In which case, go back to stock and start again.. The process works, somewhere along the line you have borked something.
Flash .93, root with griefrrot, install recovery flash a prerooted latest firmware..
That process works.

gregbradley said:
In which case, go back to stock and start again.. The process works, somewhere along the line you have borked something.
Flash .93, root with griefrrot, install recovery flash a prerooted latest firmware..
That process works.
Click to expand...
Click to collapse
Quick update: i have found the problem app and identified it as "LG Optimus Lockscreen". This app was asking for root privileges and was somehow disabling the home button through a setting to ensure someone couldnt unlock the phone by pressing the home button. It was also causing the issue with losing root.
Shame because the lockscreen is awesome

Lollipop and root....

I'm S - offed through sunshine (gotta love them guys) and had temp root with stock recovery, I assumed the lollipop update would fail but late last night it updated and I lost root. Any idea how to root again?

Well u have s off so flash twrp then flash su
Sent from my Nexus 6 using Tapatalk

How to flash su
Sent from my Xperia U using XDA Free mobile app

The issue is I don't have access to my personal computer for the weekend. Any other way to flash twrp? Flashify says I need root so it won't do it. Twrp manager I'm leery of because I heard the partition it puts it in is wrong thereby bricking the phone.

Unfortunately I don't believe Jcase has Sunshine working for lollipop yet... But that doesn't mean all is lost, just means you have to go a different means and you need to know how to use adb commands. Follow this address below and you will have a custom recovery and then you can install whatever custom rom or a pre-rooted LP OTA if that's all you want.
http://www.teamw.in/project/twrp2/226
Scroll down and follow the instructions under either.... 'Download - ADB / Terminal method:' or 'Download - Fastboot Method:'
You might be able to try to install the Goo Manager app from the play store to do the recovery install for you. Just not sure if that works without having root. TMWN says it just needs s-off so you may be good. Wouldn't need a computer either for that method. Just make sure you get your download of whatever rom saved on your phone before you wipe your current rom.

beeper10 said:
The issue is I don't have access to my personal computer for the weekend. Any other way to flash twrp? Flashify says I need root so it won't do it. Twrp manager I'm leery of because I heard the partition it puts it in is wrong thereby bricking the phone.
Click to expand...
Click to collapse
Download this and move it to your ext-sd card (not in any folder) using htc file manager. Rename it to 0P6BIMG.zip
https://www.androidfilehost.com/?fid=95916177934537454
Then reboot to bootloader and allow it to flash. This will give you back the latest TWRP. Boot back up and delete that zip off your sd card. IF you don't delete or rename it you won't be able to get to recovery via bootloader (it will keep trying to load that zip).
Then download this (doesn't matter to where-just remember where).
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
REboot to TWRP manually and flash it. Bam... done.....

It's not flashing - hopefully the rename is OP6 and not zeroP6. When I go to recovery then bootloader nothing happens and if I apply from SD card from recovery it says "no package selected and access denied", I'm sure I'm doing something wrong but I don't know what.

beeper10 said:
It's not flashing - hopefully the rename is OP6 and not zeroP6. When I go to recovery then bootloader nothing happens and if I apply from SD card from recovery it says "no package selected and access denied", I'm sure I'm doing something wrong but I don't know what.
Click to expand...
Click to collapse
zero P it is...

Last question.... I hope, I can't get to twrp recovery. It just takes me to stock recovery with no option to get to a custom recovery.

beeper10 said:
Last question.... I hope, I can't get to twrp recovery. It just takes me to stock recovery with no option to get to a custom recovery.
Click to expand...
Click to collapse
Did you flash this in bootloader?

I power phone off, hold volume down and hit power. Usually at this point I have recovery, bootloader, etc, now I have no options just shows the zip running and a question to update or not.... Either option goes to not updating.

Ok - apparently sometimes I'm a little slow..... All worked incredibly well once user error was taken out of the equation. Thanks Mr. Dottat, you're truly an asset to this forum!!

beeper10 said:
Ok - apparently sometimes I'm a little slow..... All worked incredibly well once user error was taken out of the equation. Thanks Mr. Dottat, you're truly an asset to this forum!!
Click to expand...
Click to collapse
Missed the part about deleting eh? Lol.
Glad you got it sorted.

When it came to update or not to update, I assumed I had to use the volume rocker then hit the power button to invoke the action. I was trying to go volume down to get to update when in reality volume down was the action needed to deny the update!! ?

[Resolved] Installed TWRP on phone with a locked bootloader - now stuck in boot loop

I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.

if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk

EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.

i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk

I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done

EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.

Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks

Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!

IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?

mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.

Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.