[Q] I've rooted my phone, Now what should I do? - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I rooted my phone a little while ago but didn't do anything with it. Am I able to use a custom rom on it now? Are there any recommended apps to get on it now that it's rooted?

Repromise said:
I rooted my phone a little while ago but didn't do anything with it. Am I able to use a custom rom on it now? Are there any recommended apps to get on it now that it's rooted?
Click to expand...
Click to collapse
For starters, open up a terminal and run:
Code:
su
reboot nvbackup
This will write your IMEI and carrier identification stuff stored in nvram to backup partitions. Your phone has built in backup partitions for this data and it will try to restore from them under certain circumstances (usually a flash gone wrong), but by default the backups are blank . Your phone will reboot, you'll see a couple of real quick flashes of little blue text, then it will boot up again normally.
Some other good terminal commands to note the output of would be:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
That will tell you what bootloader and modem your phone is running on. You need to know this if you plan on doing any custom rom flashing. As a general rule don't ever attempt to downgrade bootloaders on this phone; the older ones can actually be downgraded but the newer ones will hard brick if you try it. Research, research, research before you do anything, and don't be afraid to ask questions. XDA forums are a great source of information, but beware of old information. Knox and the secure bootloaders changed how we have to treat this phone around Fall 2013, so following old forum posts or old articles on lifehacker or somewhere like that can be dangerous. Mostly custom rom zips won't touch your bootloader or modem. Its Odin you have to be most careful with, as those packages tend to be full firmware updates.
You're not ready to flash custom roms just yet unless you already flashed a custom recovery too like twrp or philz. You can use an Play store app called flashify to flash a custom recovery too since you're already rooted.
Flashify and Titanium Backup (pro version is very worth the money) are the only root apps I have on my S3.

jason2678 said:
For starters, open up a terminal and run:
Code:
su
reboot nvbackup
This will write your IMEI and carrier identification stuff stored in nvram to backup partitions. Your phone has built in backup partitions for this data and it will try to restore from them under certain circumstances (usually a flash gone wrong), but by default the backups are blank . Your phone will reboot, you'll see a couple of real quick flashes of little blue text, then it will boot up again normally.
Some other good terminal commands to note the output of would be:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
That will tell you what bootloader and modem your phone is running on. You need to know this if you plan on doing any custom rom flashing. As a general rule don't ever attempt to downgrade bootloaders on this phone; the older ones can actually be downgraded but the newer ones will hard brick if you try it. Research, research, research before you do anything, and don't be afraid to ask questions. XDA forums are a great source of information, but beware of old information. Knox and the secure bootloaders changed how we have to treat this phone around Fall 2013, so following old forum posts or old articles on lifehacker or somewhere like that can be dangerous. Mostly custom rom zips won't touch your bootloader or modem. Its Odin you have to be most careful with, as those packages tend to be full firmware updates.
You're not ready to flash custom roms just yet unless you already flashed a custom recovery too like twrp or philz. You can use an Play store app called flashify to flash a custom recovery too since you're already rooted.
Flashify and Titanium Backup (pro version is very worth the money) are the only root apps I have on my S3.
Click to expand...
Click to collapse
++ 1
"all i can really do , is stay out of my own way and let the will of heaven be done"

jason2678 said:
For starters, open up a terminal and run:
Code:
su
reboot nvbackup
This will write your IMEI and carrier identification stuff stored in nvram to backup partitions. Your phone has built in backup partitions for this data and it will try to restore from them under certain circumstances (usually a flash gone wrong), but by default the backups are blank . Your phone will reboot, you'll see a couple of real quick flashes of little blue text, then it will boot up again normally.
Some other good terminal commands to note the output of would be:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
That will tell you what bootloader and modem your phone is running on. You need to know this if you plan on doing any custom rom flashing. As a general rule don't ever attempt to downgrade bootloaders on this phone; the older ones can actually be downgraded but the newer ones will hard brick if you try it. Research, research, research before you do anything, and don't be afraid to ask questions. XDA forums are a great source of information, but beware of old information. Knox and the secure bootloaders changed how we have to treat this phone around Fall 2013, so following old forum posts or old articles on lifehacker or somewhere like that can be dangerous. Mostly custom rom zips won't touch your bootloader or modem. Its Odin you have to be most careful with, as those packages tend to be full firmware updates.
You're not ready to flash custom roms just yet unless you already flashed a custom recovery too like . You can use an Play store app called flashify to flash a custom recovery too since you're already rooted.
Flashify and Titanium Backup (pro version is very worth the money) are the only root apps I have on my S3.
Click to expand...
Click to collapse
How do I open a terminal? I feel silly asking that. I downloaded an app that says what bootloader version I have

Repromise said:
How do I open a terminal? I feel silly asking that. I downloaded an app that says what bootloader version I have
Click to expand...
Click to collapse
You can use adb shell if you have adb set up. Otherwise install a terminal emulator from the play store. Jack palevich's is a good one.

jason2678 said:
For starters, open up a terminal and run:
Code:
su
reboot nvbackup
This will write your IMEI and carrier identification stuff stored in nvram to backup partitions. Your phone has built in backup partitions for this data and it will try to restore from them under certain circumstances (usually a flash gone wrong), but by default the backups are blank . Your phone will reboot, you'll see a couple of real quick flashes of little blue text, then it will boot up again normally.
Some other good terminal commands to note the output of would be:
Code:
getprop ro.bootloader
getprop gsm.version.baseband
That will tell you what bootloader and modem your phone is running on. You need to know this if you plan on doing any custom rom flashing. As a general rule don't ever attempt to downgrade bootloaders on this phone; the older ones can actually be downgraded but the newer ones will hard brick if you try it. Research, research, research before you do anything, and don't be afraid to ask questions. XDA forums are a great source of information, but beware of old information. Knox and the secure bootloaders changed how we have to treat this phone around Fall 2013, so following old forum posts or old articles on lifehacker or somewhere like that can be dangerous. Mostly custom rom zips won't touch your bootloader or modem. Its Odin you have to be most careful with, as those packages tend to be full firmware updates.
You're not ready to flash custom roms just yet unless you already flashed a custom recovery too like. You can use an Play store app called flashify to flash a custom recovery too since you're already rooted.
Flashify and Titanium Backup (pro version is very worth the money) are the only root apps I have on my S3.
Click to expand...
Click to collapse
I downloaded a terminal and used those commands. They came up with the same thing: I747MVLUFNH2. Knowing that if I flash twrp using flashify, do you have any suggestions for a stable custom Rom to use? Thanks for the help!

Repromi64433 said:
I downloaded a terminal and used those commands. They came up with the same thing: I747MVLUFNH2. Knowing that if I flash twrp using flashify, do you have any suggestions for a stable custom Rom to use? Thanks for the help!
Click to expand...
Click to collapse
I like pacman and slim. Candy is good too, but the newest kitkat builds don't work with my modem.

jason2678 said:
I like pacman and slim. Candy is good too, but the newest kitkat builds don't work with my modem.
Click to expand...
Click to collapse
Do you know which slimkat I would use? under s3 I only see i9300 adnd d2lte.

Repromise said:
Do you know which slimkat I would use? under s3 I only see i9300 adnd d2lte.
Click to expand...
Click to collapse
Never flash an i9300 ROM or you'll have a bad day.
You want d2lte.

jason2678 said:
Never flash an i9300 ROM or you'll have a bad day.
You want d2lte.
Click to expand...
Click to collapse
Alright, anything else I should know or am I good just following the instructions posted on the website?
Also I see that it says to install gapps, what is that? and when it says SD card is that just onto my phone storage or an external SD card? Sorry for all the questions lol

Repromise said:
Alright, anything else I should know or am I good just following the instructions posted on the website?
Also I see that it says to install gapps, what is that? and when it says SD card is that just onto my phone storage or an external SD card? Sorry for all the questions lol
Click to expand...
Click to collapse
Please read up some more before you attempt to install a custom rom. Most of the questions you are asking have been covered extensively throughout XDA and other forums. While you are at it, please don't limit yourself to just learning how to install a custom rom, but also learn what you should do in the event of issues. Some issues are general across all android devices and others are phone model specific.
Gapps is one of those basic things that you learn in the process of learning about rooting and installing custom roms and it is constantly being covered in discussions, wikis, and what not. But just to answer what is it: it is a necessary piece for installing most AOSP roms (If you do not know what AOSP is then please do some heavy research) if you want the Google Play store and other Google apps..

aybarrap1 said:
Please read up some more before you attempt to install a custom rom. Most of the questions you are asking have been covered extensively throughout XDA and other forums. While you are at it, please don't limit yourself to just learning how to install a custom rom, but also learn what you should do in the event of issues. Some issues are general across all android devices and others are phone model specific.
Gapps is one of those basic things that you learn in the process of learning about rooting and installing custom roms and it is constantly being covered in discussions, wikis, and what not. But just to answer what is it: it is a necessary piece for installing most AOSP roms (If you do not know what AOSP is then please do some heavy research) if you want the Google Play store and other Google apps..
Click to expand...
Click to collapse
Will do, sorry for trying to be spoonfed. I'll try to do some research, but I'm not really sure where to start. Which is mostly why I'm asking so much

Repromise said:
Will do, sorry for trying to be spoofed. I'll try to do some research, but I'm not really sure where to start. Which is mostly why I'm asking so much
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1802160
this a thread to explain some basics if you want. and as @aybarrap1 explained earlier , if you want direct access to the play store then you have to have the gapps pkg also. it is not necessary for the ROM to run and there are other markets to obtain apps., fdroid , aptoid , etc. ( bundling gapps with AOSP roms is a license thing , which i obviously dont have firm knowledge about. lol ).
as far as stable custom ROMs go it can really vary from device to device. i would suggest to read thru the threads and you can get a general feel for the stability of the ROM.
but once again , you'll probably just have to try some out and see.
some ROMs also require a certain level bootloader/modem to be able to be flashed , but it should state that in the first post.
good luck and happy flashing.
"all i can really do , is stay out of my own way and let the will of heaven be done"

Repromise said:
Will do, sorry for trying to be spoonfed. I'll try to do some research, but I'm not really sure where to start. Which is mostly why I'm asking so much
Click to expand...
Click to collapse
No problem. I just want to make sure you know enough that you can hopefully avoid hard bricking your phone as well as how to fix (or search for fixes) should something happen such as a soft brick or boot loop. If we were just to tell step by step how to install a specific ROM now, you would not be prepared to fix your phone should something go wrong.
The link mentioned by mrrocketdog is an excellent place to start. For the specifics with the d2att, just start reading through the AT&T Galaxy S3 forums by choosing topics about various issues. Make sure you read the stickies...they are there for good reason. If you see a ROM you might be interested in, please make sure you read the OP thoroughly and completely. If you don't understand something stated, go look for what it means. Read through the forum for the ROM...especially posts dated on and after the last modification and updated ROM by the OP. This will give you good information on any issues individuals are running into and what not.

Related

How does the GS3 compare to the Vibrant in terms of brickability?

Alright folks, this is directed more at the those that have spent a lot of time modding and flashing their GS3's. I recently got myself a GS3, and I gotta be honest, I haven't gotten the itch to customize it more than root yet because it is just that good already.
I modded the hell out of my Vibrant, constantly flashing Roms, modems, kernels, etc. Ran into a few "bumps" along the road where I thought the phone was done for, but I was always able to bring it back. For instance, a few months before I got the GS3 I was flashing a ROM and although I can't remember the details, something screwed up and I was getting the dreaded Phone to PC symbol. I have had this in the past and had a JIG that would always get me into download mode. This time however, it wouldn't work. I couldn't get ADB to send it into download, nor through the hardware keys, nor with the JIG. I thought for sure I was done for.
I decided to plug it into my computer anyway with ODIN up, and even though it wasn't in download mode, ODIN showed a "yellow COM". I said what is there to lose and so I loaded stock and hit start, lo and behold a few minutes later the ol' Vibrant was booting back up to the familiar sound of the T-Mobile jingle. I thoroughly believe that phone is unbrickable.
Now I know I'm going to get the itch sooner or later, especially as more and more ROM development ensues, but how brickable is the GS3? Anyone know if it's as "tough" as the Vibrant was in that respect, or is it quite a bit easier to brick? What is your experience with it so far?
If you flash am i9300 ROM, you will brick. That's about it.
Sent from my SGH-T999
If you know how to read warnings and have a fully functional brain you won't brick.
Posted from what apple calls "basically an iPhone" SGS3
GS3 should be less likely to brick
I flashed an HTC Rom with the vibrant and was still able to get it back to functionality.. not completely for sure about the GS3. I know of someone that hardbricked their GS3, and they are actually getting close to fixing it, but not fully yet.. just read and flash what ur suppose to.
Sent from my SGH-T999 using xda app-developers app
I use to have a vibrant too. Then I switch to this. I am a flashaholic so far everything good . Havent have anu problem that odin cant fix.
Sent from my SGH-T999 using xda app-developers app
If you do eventually decide to fiddle around with your phone, here's some advice:
1. BACKUP YOUR IMEI. No one's 100% sure what causes it (though there are several theories regarding recoveries and wipe scripts). You can inject your IMEI if you don't have a backup but the process takes maybe 10 minutes and I feel like it would save alot of headaches. There are currently two methods. I recommend you do both and keep a copy of the backup files somewhere safe:
Method 1: http://forum.xda-developers.com/showthread.php?t=1808408
Method 2: http://forum.xda-developers.com/showthread.php?t=1804123 (includes instructions on injecting an IMEI.
2. Try to stick to the thread for your particular GS3. I've heard that ATT Roms and kernels are compatible with the TMO version and vice versa. I take a little more comfort knowing a particular ROM or kernel was developed for my specific GS3 variant. Feel free to experiment with ROMS and kernels from other variants but be sure you know what they contain (be especially attentive to different modems/radios, see #3).
3. IMO the biggest source for bricking involves modems/radios. I haven't flashed any because I'm on wind and most of the new modems released have been for TMO. Flashing the wrong radio can brick your phone. Most ROMS don't flash a modem but it never hurts to ask. Be especially attentive to files that require ODIN as I believe some of these files may include modems and recoveries.
4. Since your posting on TMO forum, I'm going to assume yo have a TMO/Wind/Mobilicity variant of the phone. If your looking to root, I recommend using the method in this thread: http://forum.xda-developers.com/showthread.php?t=1771687. Simply download the image for your cell phone company and follow the instructions in OP. It's basically just flash with ODIN. Then install a recovery. You can install CWM using the method in the post. Or you can install TWRP by downloading the goo.im app and installing it with that application..
5. HAVE FUN
I used to have a vibrant as well and had a few close calls. I was always able to finally get it back. The S3 appears to be just as hearty (as long as you don't flash a i9300 rom).
Flash away.
nicky9door said:
If you do eventually decide to fiddle around with your phone, here's some advice:
1. BACKUP YOUR IMEI. No one's 100% sure what causes it (though there are several theories regarding recoveries and wipe scripts). You can inject your IMEI if you don't have a backup but the process takes maybe 10 minutes and I feel like it would save alot of headaches. There are currently two methods. I recommend you do both and keep a copy of the backup files somewhere safe:
Method 1: http://forum.xda-developers.com/showthread.php?t=1808408
Method 2: http://forum.xda-developers.com/showthread.php?t=1804123 (includes instructions on injecting an IMEI.
2. Try to stick to the thread for your particular GS3. I've heard that ATT Roms and kernels are compatible with the TMO version and vice versa. I take a little more comfort knowing a particular ROM or kernel was developed for my specific GS3 variant. Feel free to experiment with ROMS and kernels from other variants but be sure you know what they contain (be especially attentive to different modems/radios, see #3).
3. IMO the biggest source for bricking involves modems/radios. I haven't flashed any because I'm on wind and most of the new modems released have been for TMO. Flashing the wrong radio can brick your phone. Most ROMS don't flash a modem but it never hurts to ask. Be especially attentive to files that require ODIN as I believe some of these files may include modems and recoveries.
4. Since your posting on TMO forum, I'm going to assume yo have a TMO/Wind/Mobilicity variant of the phone. If your looking to root, I recommend using the method in this thread: http://forum.xda-developers.com/showthread.php?t=1771687. Simply download the image for your cell phone company and follow the instructions in OP. It's basically just flash with ODIN. Then install a recovery. You can install CWM using the method in the post. Or you can install TWRP by downloading the goo.im app and installing it with that application..
5. HAVE FUN
Click to expand...
Click to collapse
I did use that method for rooting already, but I didn't realize the issue with the IMEI so that's good to know for when I get the urge to start flashing again. :laugh:

how to put custom ROM ???

.Hey guys I'm new in this world of rooting ...maybe know someone how to put Omega 7.2 ROM into the Samsung Galaxy Note 2 SGH-I317M. ????
First off there is a Q&A section for questions. They don't go here.
Second that's an international rom you can't just simply flash it like the roms in the Development section. This link can tell you how to port it but if you are new you probably shouldn't try it.
http://forum.xda-developers.com/showthread.php?t=2018411
Sent from my SAMSUNG-SGH-I317 using xda premium
NightHawkUndead said:
First off there is a Q&A section for questions. They don't go here.
Second that's an international rom you can't just simply flash it like the roms in the Development section. This link can tell you how to port it but if you are new you probably shouldn't try it.
http://forum.xda-developers.com/showthread.php?t=2018411
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
NightHawk hit the nail on the head. It would be best for you right now to read up and learn as much as you can about how the forum works as a whole and how development and custom roms recoveries etc work in general.....Here is a good place to start!
My note 2 is on its way,in the mean time ill be reading alot.
Sent from my Desire HD using xda premium
lamartino said:
.Hey guys I'm new in this world of rooting ...maybe know someone how to put Omega 7.2 ROM into the Samsung Galaxy Note 2 SGH-I317M. ????
Click to expand...
Click to collapse
A lot of us would suggest you take a bit of time to read up on what you will need. I short a safe bet is to read twice and flash once. Doing any sort of flashing will void your warranty and you run the risk of damaging your phone. Granted most mishaps are fixable with knowledge and experience. For you however, having a bootloop or a soft brick would not be fun.
I suggest you get the proper drivers for your version of the n2
I suggest you read up on how to root the note 2: read the entire thread...yes it is repetitive,but at least you get an idea of what can go wrong and how to fix it be reading what happened to others. Then decide on what recovery you would like....read up on cwm or twrp and how to install them properly. once you have done all that...then it is time to flash a custom rom.
I think I would recommend you do a bit more reading before deciding wether rooting and flashing a custom rom is for you
There is a lot to absorb when first looking to install a custom rom. I'm a visual person so I like youtube a lot. When you find the forum that suits your particular device, there will usually be a thread something along the lines of "all you need to know about (your phone here)". My own method of learning was to make a list of each individual task that I needed to do and then youtube it to see someone doing it in person so I can get an idea of what it looks like.
Usually the steps to a custom rom are:
1) Root:
methods can differ among devices and developers (youtube your phone for root)
2) Install a custom "recovery"
will typically be either Clockworkmod or TWRP. I've only ever used clockworkmod but people say good things about TWRP also. The custom recovery will be where you "flash" (install) the rom as well as perform other functions such as wipe casche, wipe dalvic, fix permissions, etc., all of which are fairly self explanatory once you finally boot into the recovery, but again, youtube your phone for all of these things. Even seeing it on other phones can be a big help also, as long as what you are trying to accomplish is the same between the devices.
3)Pick a rom, download it to your phone, boot into recovery and follow the directions that the developer will leave in the OP. Someone mentioned read twice, flash once. Great advice. Make sure to have all your ducks in a row and are confident about each step you will be taking. Skipping a step or doing it incorrectly can cause serious headaches and can derail you for hours trying to figure out how to fix it if you are not already familiar with what to do.
Best of luck!!!
topshelf95 said:
There is a lot to absorb when first looking to install a custom rom. I'm a visual person so I like youtube a lot. When you find the forum that suits your particular device, there will usually be a thread something along the lines of "all you need to know about (your phone here)". My own method of learning was to make a list of each individual task that I needed to do and then youtube it to see someone doing it in person so I can get an idea of what it looks like.
Usually the steps to a custom rom are:
1) Root:
methods can differ among devices and developers (youtube your phone for root)
2) Install a custom "recovery"
will typically be either Clockworkmod or TWRP. I've only ever used clockworkmod but people say good things about TWRP also. The custom recovery will be where you "flash" (install) the rom as well as perform other functions such as wipe casche, wipe dalvic, fix permissions, etc., all of which are fairly self explanatory once you finally boot into the recovery, but again, youtube your phone for all of these things. Even seeing it on other phones can be a big help also, as long as what you are trying to accomplish is the same between the devices.
3)Pick a rom, download it to your phone, boot into recovery and follow the directions that the developer will leave in the OP. Someone mentioned read twice, flash once. Great advice. Make sure to have all your ducks in a row and are confident about each step you will be taking. Skipping a step or doing it incorrectly can cause serious headaches and can derail you for hours trying to figure out how to fix it if you are not already familiar with what to do.
Best of luck!!!
Click to expand...
Click to collapse
well done and i completely agree, but for someone who's so new you musn't forget to install the drivers for the device you have onto your pc or laptop or whatever is going to run Odin for you.... no drivers is the easiest and fastest way to ensure your shiny new device is on the short bus to not working right
it is often overlooked and ppl presume that they just do it - installing the drivers that is - and it's often mentioned in the rooting thread, but only in passing.
if you do not have the proper drivers your 700+ dollar device will not last long so do yourself a favor and make sure you have them installed properly and that your computer detects the device properly
when you plug into odin you should see a yellow background with COM and a number in it (changes depending on the usb port you are plugged into) if you don't have that, don't click the start button cuz you gonna be in the hurt locker in all likelihood even if you follow the instructions to a T.
I'm relatively new to all of this, only rooting my Evo, and now my Note 2.
I cannot stress enough how correct all the previous replies are. Read everything you can about your device and rooting in general. Use Youtube. Use this forum, use any information you can find. Learn the language(it can be tricky). Learn as much as possible and ask questions....just make sure you look for the answers before asking them.
Once you feel comfortable, the Devs do a solid job of making it easy for us, follow the steps and you should have success.
Here is a link to some terminology.....make sure to thank ThC23!
http://forum.xda-developers.com/showthread.php?t=1394458
You will make mistakes then become a pro. We all battled endless nights of fixing our devices after misreading one line.
Sent from my GT-N7105 using xda premium

[Q] HELP!! Have I bricked my new device!? SO WORRIED!!

Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.

[Q] Phone is rooted, but how do I know what it has (what ROM, etc)? I

I followed instructions to root it and its rooted, but have never been able to get Cyanogenmod to Install (I always get the same error everyone else does), and when I try to check out different ROMS, no one even posts many pics to show what the difference will be to use that ROM.
My phone looks the same as before and I'm just using ADW launcher to set it up the way I want it to look.
So how can I tell exactly what point of rooting my phone has reached? Do I actually have a different ROM, etc? I don't know much about this stuff and I'm not bricking my phone messing around with it until I know exactly where to start.
What custom recovery and bootloader are currently loaded on the phone?
kmodek said:
So how can I tell exactly what point of rooting my phone has reached? Do I actually have a different ROM, etc?
Click to expand...
Click to collapse
Hi!
Go to your phone's System Settings --> About phone.
In there, you should be able to figure out which Android version is currently installed on your phone; if you have a custom ROM, most of the time ROMs developers will also add an additional line somewhere on that screen to tell exactly what revision of their ROM is installed. If not, you may be able to grab some more information by checking your build number or your kernel revision.
If you tap a few times on where it says Android Version, under Settings>More>About Device , it usually does a little animation of the rom version. Im trying to decide on a rom so mine is kit kat 4.2.2 at the moment and dislpays an Android logo in the Kit Kat logo style.
Since the bootloader version is not displayed on the About Phone page, you will need to determine that with another method. A simple way would be with the Samsung Info app from the PlayStore, the one posted by vndnguyen.
I personally use Terminal Emulator commands to determine phone info.
Code:
getprop ro.bootloader
getprop | grep version.baseband
I got the app from the Play store and it shows I'm on 4.4.2, but that the Knox has been tripped (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
kmodek said:
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
i was watching youtube videos of reviews of the different custom ROMs gave a good idea on the features and layout of each rom. I as well am having difficulty deciding on a ROM to flash as this is my first smart phone and am new to it. ive been reading and watching a bunch of tutorials but finding information on whats currently stable for our particular phone can be somewhat dated. i know moderators want to avoid a "best roms" thread but for those of us just starting out with a rooted phone it sure would be handy to have opinions on what ppl use for the SGH-I747 and why, so its easier to decide on one.
is it reccommended to upgrade or downgrade? in order to compare ROMs its watching a video for 15 min to see what features it had at the time the vid was made and reading the developer forums on each mod to see what bugs are present in the current release but its not all compiled anywhere. its that or randomly flash ROMs on there to test them out and risk making mistakes. its usually always better to have advice from those with expertise and perhaps avoid making commonly made mistakes. ive read a bunch of helpful and handy guides on here but doesnt seem any way to easily compare roms or get feedback on what users have decided on sticking with or anything additional specific to this phone that should be considered before flashing certain ROMs.
kmodek said:
I got the app from the Play store and it shows I'm on 4.4.2, but that the Knox has been tripped (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
this thread may help to explain some badic things.
http://forum.xda-developers.com/showthread.php?t=2343223
my advice , for what its worth ...
1) READ READ READ
2) make a backup of your current setup so you have it to fall back on.
3) NEVER downgrade your bootloader , flash any ROM/kernel not meant for your device (sure way to brick it).
theres always risk when flashing anything , but the risks can be minimized by understanding what your doing , or rather the process.
as far as flashing roms , its pretty simple once you understand it (as with most things. lol). reading thru a ROMs thread will give a general idea of any features , issues that the users have. the OP , first post ; will tell you alot about the ROM/features.
good luck and happy flashing.!
"all i can really do , is stay out of my own way and let the will of heaven be done"
kmodek said:
.... (I know it's rooted because I have an app that verifies root), but other than that, I can't tell any difference from how it was originally.
Guess I just thought rooting it would make it look a lot different and after reading through all of the forums, there seems to be 100 steps just to try out one new ROM and I don't even know what you do if you get it and decide you don't even like it. I just don't want to brick my phone.
Click to expand...
Click to collapse
The act of rooting does not outwardly change the look and feel of a ROM in any way. It's what you do after rooting that makes the difference.
Some like the Stock Rom of a device and/or do not want to lose some of its unique features. These people will root but not flash a custom ROM.
I've had two android phones and one tablet. Initially I root a new device but leave it on the stock ROM. At that time I will use an app that requires root to freeze any of the pre-installed apps that I don't use (My definition of bloat.) I don't remove/delete them at the beginning. If freezing them breaks some other functionality I want that app still on the device so that I can unfreeze it and make everything work again. Both of my phones have been Samsungs, a SGS Captivate and a SGS3. After a while on rooted stock I have changed to custom ROMs on each. The Captivate went from stock to CyanogenMod to a CM derived ROM. The SGS3 went from stock to a re-themed, custom ROM based on stock but with much removed (carrier bloat) and some other functions added. I expect to soon change to a later version of the same ROM with even more removed. Others want to have a ROM with every bell and whistle possible to have present. It's all individual preference.
havok6669 said:
i was watching youtube videos of reviews of the different custom ROMs gave a good idea on the features and layout of each rom. I as well am having difficulty deciding on a ROM to flash as this is my first smart phone and am new to it. ive been reading and watching a bunch of tutorials but finding information on whats currently stable for our particular phone can be somewhat dated. i know moderators want to avoid a "best roms" thread but for those of us just starting out with a rooted phone it sure would be handy to have opinions on what ppl use for the SGH-I747 and why, so its easier to decide on one.
is it reccommended to upgrade or downgrade? in order to compare ROMs its watching a video for 15 min to see what features it had at the time the vid was made and reading the developer forums on each mod to see what bugs are present in the current release but its not all compiled anywhere. its that or randomly flash ROMs on there to test them out and risk making mistakes. its usually always better to have advice from those with expertise and perhaps avoid making commonly made mistakes. ive read a bunch of helpful and handy guides on here but doesnt seem any way to easily compare roms or get feedback on what users have decided on sticking with or anything additional specific to this phone that should be considered before flashing certain ROMs.
Click to expand...
Click to collapse
There are so many variations on what is possible that a compilation thread to cover all situations would seem as huge as wikipedia. Your approach, reviewing videos and checking rom OPs, has merit but it also has limitations. Unfortunately some of the devs give you almost no information about the features and customizations of their ROMs. Others will simply state that they have made a change or two to some base, expecting you to be familiar with the base. Which means a lot of more reading/reviewing for a person new to customizing their phone.
To advise any one questioner on what can be installed on their phone a responder must first know what bootloader and modem is on the device, are you already rooted, do you have a custom recovery installed yet, are you willing to risk breaking your warranty; the list goes on. Then the hard part comes - they have to recommend something that is in the realm of what you are expecting, even if you do not know what you are expecting.
dawgdoc said:
To advise any one questioner on what can be installed on their phone a responder must first know what bootloader and modem is on the device, are you already rooted, do you have a custom recovery installed yet, are you willing to risk breaking your warranty; the list goes on. Then the hard part comes - they have to recommend something that is in the realm of what you are expecting, even if you do not know what you are expecting.
Click to expand...
Click to collapse
well i made sure i learned a bunch before even attempting to ask a question so i got as much as possible prepared i'll try to provide the best information i can. my phone is rooted with superuser su2.0 i have cwm 6.0.1.2 installed, ive done a cwm nandroid backup which i copied to my pc as well as a backup of my efs folder and done a titanium backup as well. i have odin 3.07 on my pc and am currently running kitkat 4.4.2 on my sgh-i747m (sasktel version) currently trying to figure out how to determine the modem and bootloader versions . i followed the galaxys3root.com guide galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-android-4-34-4-2-new and the highonandroid youtube vid in order to root my phone and made sure i read re read and was very cautious to follow instructions to the letter also read some worst case scenario information first like how to cause a phone to become bricked and how to fix it should it happen etc so before ive done anything else ive made sure to back everything up and ask a few more questions befor ei take the final plunge :] as for what ROM would tickle my tailfeathers was liking how carbon looked but it seems it hasnt been maintained :[ something good on battery life that runs fast n stable and is has a bunch of customization features is what i was hoping for. the main reason i decided to root my phone was to learn more about it and customize my os away from the stock look and feel and unlock some of the potential it has that a stock rom would otherwise neglect. the more i learn the sooner i can help by giving back to the community :]
havok6669 said:
....
my phone is rooted with superuser su2.0 i have cwm 6.0.1.2 installed, ive done a cwm nandroid backup which i copied to my pc as well as a backup of my efs folder
Click to expand...
Click to collapse
CWM 6.0.1.2 is a bit dated, their latest version is 6.0.4.7 and even it is a bit dated. You may find that to flash a current ROM you will need to update CWM. For some of the newer ROMs even 6.0.4.7 is not current enough. You will need to change to Philz Recovery, based on CWM, or TWRP. Bear in mind that if you change to TWRP you will not be able to use your CWM nandroid. I don't know if the same applies to Philz Recovery.
https://www.clockworkmod.com/rommanager
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/ (page is down at the moment)
http://teamw.in/devices/samsunggalaxys3canada.html (d2can TWRP, though I think you can use d2att, check before using d2att)
There is definitely a newer version of SuperSu (by Chainfire) available. It went through a lot of development to handle issues related to Knox that came out with Touchwiz 4.3. SuperSu is now up to 2.49 and I would recommend upgrading it no matter what ROM you should end up choosing. http://forum.xda-developers.com/showthread.php?t=1538053 There is a zip you can flash from you current CWM there.
It's not a bad idea to have several fallbacks for imei/nvdata. Give this tread a look: http://forum.xda-developers.com/showthread.php?t=1852255&highlight=synergy+nvbackup I used the reboot nvbackup from there and EFS Backup developed by wanam
... am currently running kitkat 4.4.2 on my sgh-i747m (sasktel version) currently trying to figure out how to determine the modem and bootloader versions .
Click to expand...
Click to collapse
Sasktel has released 4 versions of Android 4.4.2, each with a different bootloader and modem. Any should be fine no matter what ROM you choose, even a Lollipop based ROM. But to check you can get Phone Info - Samsung by vndnguyen from the Playstore. Or you could use a pair of commands in Terminal Emulator
Code:
getprop ro.bootloader
getprop | grep version.baseband
... as for what ROM would tickle my tailfeathers was liking how carbon looked but it seems it hasnt been maintained :[ something good on battery life that runs fast n stable and is has a bunch of customization features is what i was hoping for. the main reason i decided to root my phone was to learn more about it and customize my os away from the stock look and feel and unlock some of the potential it has that a stock rom would otherwise neglect. the more i learn the sooner i can help by giving back to the community :]
Click to expand...
Click to collapse
You could either go straight a Lollipop based ROM or start with a KitKat ROM. The KK ROM would probably be a bit more stable, although some of the nightly 5.1.1 LP ROMs are looking good according to many of the people installing the nightly versions. If you want something already customized with options for your choosing look to CM and its derivatives or one of the AOSP roms that are already tricked out. The other direction would be to install the most barebones AOSP ROM you could find and use XPosed with the GravityBox or Wanam module to tweak just about everything, but not both at the same time.
wow thanks that all helps a ton ill work on locating and updating all of that :]

ZE500CL Rooting and other related stuff

It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.
I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.
Installing Xposed works as well using the ADB method mentioned in the thread linked below:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476
I can add any info you find to the device index in the general section for the 500CL.
Djalaal said:
I've only recently bought the device, and I only rooted it (though I did first get one bootloop already). The method that worked for me is described in this thread: http://forum.xda-developers.com/zenfone2/general/root-ze500cl-z00d-t3116531
The OP of the thread linked above also said that the second method on this thread: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 works as well.
Btw, make sure the drivers are installed, else the computer won't be able to recognize the device when it is in bootloader mode.
Click to expand...
Click to collapse
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?
cmendonc2 said:
I can add any info you find to the device index in the general section for the 500CL.
Click to expand...
Click to collapse
Sure, that post is much more likely to be noticed than this one. Although I might not find out much. I'm a lot less daring without custom recovery. Hence this thread.
crisbal said:
How did you fix/handle the bootloop?
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
Well, seeing that I do not have a custom recovery (bootloader is still locked), I had to do it the hard way, reflash stock rom. Good news is, apparently your userdata (installed apps+settings and internal memory) is not wiped in the process.
First, you gotta download the rom. Get it from http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748. Although I got mine here: http://www.asus-zenfone.com/2015/03/asus-zenfone-2-stock-rom-ze500cl-ze550ml-ze551ml.html, which is the old version.
Second, go into recovery mode (from bootloader mode), and use adb sideload ("apply update from ADB") to flash the .zip downloaded before. This is described under "Flashing Zenfone 2 via ADB" on this thread: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Btw, the bootloop was caused by a mistake I made, not the rooting process.
any news update in our bootloader? hope someone could work for that..
How to get rid off couldn't add widget?
crisbal said:
Do you know if it is possible to update the phone after rooting it?
Click to expand...
Click to collapse
After more than a week of feeling unsure to update mine to WW_12.16.5.118, updating it today after finish uninstalling SuperSU. This is what I have done.
1 - uninstall SuperSU from SuperSU setting - reboot.
2 - update firmware.
3 - re-root using Temporary_CWM method as describe here
Chinaphonearena said:
Method 2: Root through temporary CWM
This is a temporary CWM with the primary purpose of injecting SuperSU onto your Asus Zenfone 2. It doesn't permanently replace recovery. This process looks long, but really is bam 1,2,3 done. Just laid out step by step for the newbie.
link removed due to post count limitation
Unzip the package
Copy SuperSU.zip to the base of your SD card
Enable USB debugging (Settings > Phone info > Tap build 7x > Back button > Developer options > USB debugging)
If you don't already have ADB drivers installed, you may need to [post count restriction] and install them (most PCs have them already, but trying installing these if you're having trouble getting your PC to issue commands to the phone via USB)
With your phone on, attach it to PC via USB
Run 'cai_dat_CWM.bat' from the CWM package
In the black command window that opens, type ACCEPT
Type T4
Phone will reboot into fastboot and you'll see commands being issued from the PC cmd window copying the temporary recovery
You may see some funked up images on your display for a bit. Remove the USB cable and within 30 seconds should then see it booted into CWM
Select install update
Navigate to SuperSU.zip and install
Bam, done.
Click to expand...
Click to collapse
4 - Success!!! now my phone are rooted and all rooted apps installed previously are working.
Note: Previously (before updating FOTA) I also root my ZE500CL using Temporary_CWM since One Click root method aren't working for me.
Recover from bootfreeze while fully stock
Well, after getting a bootfreeze being on a fully (old version) stock ze500cl (Z00D), I figured out something useful. How to recover from a bootfreeze with locked bootloader, non rooted stock rom, without loosing what was saved on your internal storage.
Given that you have not messed with system files (since you aren't rooted), I'm assuming you got either corrupted userdata files or your internal storage is so full, the phone fails to even boot. I had the latter. If system files are the problem, this method might (or probably?) not work. The trick is to use tethered TWRP for backing up your internal storage.
1: Download CWM_Zenfone_2_Intel.zip here: https://www.mediafire.com/folder/w70w7r1a65840/Zenfone_2 (gotten from source 1)
2: Download Recovery.zip here: https://drive.google.com/folderview...T0xRMVRkcTg3MHdlc1o0cVFBc3RPeTQ&usp=drive_web (gotten from source 2)
3: Extract the zip from Step 1.
4: Go to the FB_RecoveryLauncher folder you have extracted, and replace the recovery.zip there with the one downloaded in Step 2.
5: Boot into your stock recovery and connect your phone to the computer. Make sure you have adb and the phone's drivers installed (gotten from source 3).
6. Run the cai_dat_CWM.bat script and you should boot into temporary TWRP recovery after a minute or so.
7. Use TWRP to copy your sdcard folder (internal storage) into your ext_sdcard folder (external storage/microsd) for the sake of backing it up.
8a. In the case of having too full internal storage, simply delete some things in there, and you should be able to boot it again.
8b. Not tested, but in case of corrupted userdata, a factory reset is probably necessary, and will solve the bootfreeze issue.
source 1: http://forum.xda-developers.com/zenfone2/general/root-newbie-root-instructions-zenfone-2-t3114063 (method 2)
source 2: http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532
source 3: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
@cmendonc2 , if you want, you can add this to your index.
Djalaal said:
It seems that few ever talk about the ZE500CL variant of the zenfone 2. I've read a whole lot of posts on rooting, unlocking the bootloader, and installing TWRP, but most do not even mention this variant.
I started this thread to collect some information about this device. I would like to know from those who have this device, what has worked for you so far, and what hasn't? I'm especially interested in finding out the 3 things mentioned above.
Click to expand...
Click to collapse
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:
Xanathide said:
Thank you so much for providing this thread. Found it after hours of scouring the internet in search of help after somehow getting my phone locked in boot-loop. There isn't much support for the ZE500CL, but I will be posting on some blogs while I begin work on mine, and I will reference others to this thread and the few others I've found. Thanks again! :good:
Click to expand...
Click to collapse
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.
Djalaal said:
Sorry, was out of town for 3 months. Glad to be of help. You know where the thanks button is .
I should note that the this phone is now the daily driver of both my parents so I stopped tinkering with it, although I left one of them rooted (and the other not lol). So don't expect more updates from me sadly.
Click to expand...
Click to collapse
That's quite alright, I've had my fun with Z00D, got myself a LG V10 to break now
I dont ask for directions...
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs
cuervo233 said:
This is my first time asking questions as I have always been able to reverse-engineer (R-E) or as the hacker in swordfish would say "the code just comes to me". Ive been around computers since my dad took me to work at UT and commands were issued with punch out cards....I've been a long time android self taught enthusiast turned professional. ITT Alum etc. I research, I surf, I R-E, and I try every possible option etc...only this has me stumped. And this is the first android that has stumped me. I double checked everything but I keep getting this error in BBQLinux: I followed all pre-update instructions to the T.
fw: ATT_12.16.10.92
adb sideload
This package is not for ATT (WW)
E: Error in /sideload/package.zip
(Status 7)
yes I did with root cmd line, yes cd to zip file location, yes I verified correct fw, even tried different fw zips ZE500CL downloaded officially and from here.
I greatly appreciate any help and I do apologize for "asking for directions"
Computer John dba Austin Computer Techs
Click to expand...
Click to collapse
?? Is that att ota youre trying to sideload? Att doesn't have fw, ze500cl does. But just unlock your bootloader, flash twrp, then install whatever, cm, aicp, custom stock or straight stock. http://forum.xda-developers.com/showthread.php?p=64991762
Sent from my MotoG3 using Tapatalk
Cool, I didn't read anywhere about unlocking BL first otherwise Ida made that "turn at the first light". We will ULO thru Asus and continue on our journey. These little Asus trinkets are little buggers being Intel based. Only line of Android devices that have ever stumped me. I am much obliged, fellow XDA brethren. Much obliged.
After pondering a little I came to this conclusion:
UL BL is basically the first step one should take when doing any kind of flashing of internal partitions be it a boot.img, recovery.img, FW etc... at least for the higher end devices. I don't recall having to do that for my sm-n900t recently. Does it only apply for flashing back to stock and not custom roms? Although I didn't have to UL BL first when I heim-dall/Odin flashed my note3 back to stock rom after being boot-looped. Cause once I did that I was able to try out a majority of custom roms available for it whether flashed thru HD/fastboot, Odin, via twrp update zip, or adb sideload. Hmmm, I might understand once I think it thru and look at all the different variables.
Good day gentlemen.
Be vewy vewy quiet, I'm hunting androids...
:good:
@cuervo233 Yes most devices you have to unlock the bootloader first. But there are some devices that already come unlocked. And then there are even some that have bootloaders that cannot be unlocked due to carrier restrictions. In order to get custom recovery to boot you must unlock the bootloader or it must come unlocked. With a custom recovery you can Flash the stock zip file from the Asus website or a custom ROM have fun
Sent from my MotoG3 using Tapatalk
Thank you. I was able to ULBL, flash TWRP, flash to ww 118, root, and now its time to explore the neat wonderful world of custom ROMs. This was by far the hardest yet. Next in line is the cricket Stylo which was also giving me hell, but now I dont think I should have any problem getting it done. I'll keep ya'll posted.:good:
Lg stylo should have way more development, have fun brother. Remember tmobile phones( cricket, walmart family mobile, and metro pcs) you can easily unlock the bootloader . att on the other hand usually has locked down bl.
Sent from my MotoG3 using Tapatalk

Categories

Resources