Problem in Mobile (htc ADR6350) - Verizon Droid Incredible 2

I have a problem in Mobile (htc ADR6350), or what is called (HTC Incredible 2) almost
When you turn it on and then up to the slogan (HTC) and then restart frequently.
I'm doing tried scanning manufacturers (FACTORY RESET) or repair (recovery) of (HBOOT)
But as soon as you press the power button to select one of them the restart and so
Knowing There is a full backup
I hope you help me resolve this problem .... appreciate your cooperation and apologize for the bad translation.
system info:
vivo_w XB ENG S-OFF RL
HBOOT-0.96.200 (PG3210***)
RADIO-1.09.01.0722
OS Ver.-1.34.605.4

yshai1 said:
I have a problem in Mobile (htc ADR6350), or what is called (HTC Incredible 2) almost
When you turn it on and then up to the slogan (HTC) and then restart frequently.
I'm doing tried scanning manufacturers (FACTORY RESET) or repair (recovery) of (HBOOT)
But as soon as you press the power button to select one of them the restart and so
Knowing There is a full backup
I hope you help me resolve this problem .... appreciate your cooperation and apologize for the bad translation.
system info:
vivo_w XB ENG S-OFF RL
HBOOT-0.96.200 (PG3210***)
RADIO-1.09.01.0722
OS Ver.-1.34.605.4
Click to expand...
Click to collapse
Let me be the first to say this.
What?
Sent from my ADR6350 using xda app-developers app

FordNate said:
Let me be the first to say this.
What? [/QUOT
Okay, I agreed ... but, let's try to be helpful to OP whose native language is obviously not English.
I believed s/he is trying to say the device is doing an endless boot-looping and cannot get into Recovery - looking for help from us here.
OP, what carrier or home system (CDMA or GSM) are you using the phone on? Did it worked before? What were you doing with the device before this happened - trying to flash a new/different ROM, kernel or radio, etc. ??
You will need to learn and use ADB, read the sticky in this Forum and/or get someone familiar to help you with it. In the unlikely situation of being on Verizonwireless CDMA system, you can flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.
Click to expand...
Click to collapse

thanks Letitride,,,,help my
Letitride said:
FordNate said:
Let me be the first to say this.
What? [/QUOT
Okay, I agreed ... but, let's try to be helpful to OP whose native language is obviously not English.
I believed s/he is trying to say the device is doing an endless boot-looping and cannot get into Recovery - looking for help from us here.
OP, what carrier or home system (CDMA or GSM) are you using the phone on? Did it worked before? What were you doing with the device before this happened - trying to flash a new/different ROM, kernel or radio, etc. ??
You will need to learn and use ADB, read the sticky in this Forum and/or get someone familiar to help you with it. In the unlikely situation of being on Verizonwireless CDMA system, you can flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.
Click to expand...
Click to collapse
thanks Letitride
* yes....the device is doing an endless boot-looping.
* using carrier or home system (CDMA).
* What do you mean (ADB)?
* How do (flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.)
and Where did it get them?
please help my
Click to expand...
Click to collapse

yshai1 said:
Letitride said:
thanks Letitride
* yes....the device is doing an endless boot-looping.
* using carrier or home system (CDMA).
* What do you mean (ADB)?
* How do (flash the RUU file and restore it to stock (unrooted) and start over - after getting it activated again & restore all the factory settings.)
and Where did it get them?
Click to expand...
Click to collapse
It sounded like you are a complete newcomer to all this and you are going to need extra help to avoid bricking your device completely into a useless paperweight.
ADB is Android Debug Bridge, see the "Wiki" section above here on XDA and read about it, you can also google for details & how to.
Please answer, was your DI2 working before? Is (was) it activated on Verizonwireless? Was it working before this endless boot-looping?
To give you a very general idea of what is involved here, and it isn't simple but most of us learned it, sometimes - the hard way !! So be careful, very careful on what you are about to do !! If you are not confident or comfortable, don't even attempt to try & do it.
http://forum.xda-developers.com/showthread.php?t=2357721
http://forum.xda-developers.com/showthread.php?t=1876073
Do you have the HTC device drivers loaded & working on your PC? Does it recognize the DI2 when it is connected?
The links to the RUU might be broken but please answer the questions above and I will try to offer some suggestions on how best to proceed.
If all of these are "foreign" to you and you are completely lost, you need expert help instead of trying a DIY (Do It Yourself) ...
Click to expand...
Click to collapse

thanks mr. Letitride,,,,help my
Letitride said:
yshai1 said:
It sounded like you are a complete newcomer to all this and you are going to need extra help to avoid bricking your device completely into a useless paperweight.
ADB is Android Debug Bridge, see the "Wiki" section above here on XDA and read about it, you can also google for details & how to.
Please answer, was your DI2 working before? Is (was) it activated on Verizonwireless? Was it working before this endless boot-looping?
To give you a very general idea of what is involved here, and it isn't simple but most of us learned it, sometimes - the hard way !! So be careful, very careful on what you are about to do !! If you are not confident or comfortable, don't even attempt to try & do it.
http://forum.xda-developers.com/showthread.php?t=2357721
http://forum.xda-developers.com/showthread.php?t=1876073
Do you have the HTC device drivers loaded & working on your PC? Does it recognize the DI2 when it is connected?
The links to the RUU might be broken but please answer the questions above and I will try to offer some suggestions on how best to proceed.
If all of these are "foreign" to you and you are completely lost, you need expert help instead of trying a DIY (Do It Yourself) ...
Click to expand...
Click to collapse
I apologize for the delay ... Because of the circumstances
These answers your questions:
was your DI2 working before?
yes
Is (was) it activated on Verizonwireless?
yes
Was it working before this endless boot-looping?
yes
Do you have the HTC device drivers loaded & working on your PC?
yes
Does it recognize the DI2 when it is connected?
yes
Click to expand...
Click to collapse

yshai1 said:
... was your DI2 working before? yes
Is (was) it activated on Verizonwireless? yes
Was it working before this endless boot-looping? yes
Do you have the HTC device drivers loaded & working on your PC? yes
Does it recognize the DI2 when it is connected? yes
Click to expand...
Click to collapse
Here is a dropbox link to the OEM/stock RUU file released from VZW that I've saved & restored to dropbox from my collection - https://dl.dropboxusercontent.com/u....01.1111_NV_VZW1.92_release_225831_signed.exe
Please download this to your PC (linked file will be removed after 72 hours) - and prepare your DI2 by making sure it's 75% to 100% charged first. Make backup copies of your mSD card to a safe location, just in case.
Next, power on your DI2 and connect it to your PC via the micro-USB cable, then run or launch this RUU file. Read the warnings and click thru to run it - it will flash & restore your phone to factory fresh, stock condition and result in your DI2 being UN-rooted again. However, it will not change or affect SIM unlocking (if it was already done) - and, the process should take about 10 minutes or so, and when it is finished, power down & reboot the smartphone - and it should take you to the initial Startup/Setup Screen menu - follow it and get it activated again, including downloading the latest PRL from OTA.
When it is finished, you will need to follow the steps & guides to root it, install a custom recovery and SU, etc. Then, you can install your choice of custom ROM and/or kernet, etc.
The above approach is more fool-proof than using ADB to flash a different bootloader and to try to restore it to working conditions etc. with the tradeoff of losing root, which can be easily reversed again.
Let me know if you decided to go ahead and the results/outcome, etc.
Option #2 - If, however, you do not want to lose root and you can boot your device into Custom Recovery (CWM - not stock recovery) - use this link here - http://forum.xda-developers.com/showthread.php?t=1599767
Follow it & download the "Stock" PG32IMG from CS, copy it to your mSD card, boot into Recovery & flash the zip file - it SHOULD get your device backup and running again (it might NOT, I haven't done this in a while) and as long as you don't need to mess with the bootloader again (which might be corrupted or damaged, etc.) - you are good to go. Once it's up & running, you can restore & setup your APPS again - and/or install other custom ROM of your own choice, at your own risk, of course. But, make a CWM Backup first before doing so in between.
Good Luck & Regards !

i am havig troble with my HTc ADR350
my phone keep shutting down how do i resolve this?

Related

[USB-BRICK] All you need to know about USB-Bricks

[USB-BRICK] All you need to know about USB-Bricks
Fix here: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/ or http://forum.xda-developers.com/showthread.php?t=691639
What is this thread for?
The main goal of this thread is to inform all Desire owners of the USB-Brick.
Especially the ones considering rooting / flashing ROM's.
And of course the people who have already bricked their phone...
There's many threads about rooting and current development on the matter,
but a thread that summarizes the issue was lacking in my opinion.
Index
What is this brick you're talking about?
How to recognize a USB-Brick?
When does this bricking occur?
Any numbers on this bricking?
I want to root and/or flash ROM's, what should I do?
I can wait, but for what?
I'm USB-Bricked what should I do?
Fix for SD Card and (maybe) Cellular Radio
Proxity Sensor Bug, never heard of it?
I'd like to return my device and want to flash an official ROM, how can I do that?
Disclaimer
This thread is useful, how can I help?
Sunday 30 May
Tuesday 1 June
Thursday 3 June Paranoid Rooting.
[*]What is this brick you're talking about?
The brick known as USB-Brick will mess up the USB Connectivity with the Desire.
How to recognize a USB-Brick?
Symptoms:
Unable to connect your phone using USB when booted into Android.
Unable to connect your phone using USB in Custom/Pushed Recovery.
FM Radio Malfunction.
Bluetooth Malfunction.
Wall charging doesn't start immediately.
Radio Malfunction. (Fix below)
SD Card Malfunction. (Fix below)
[*]When does this bricking occur?
Unfortunately it happens randomly. Some people experience it at their attempt at rooting,
others after 10 times of successful flashing. And there's people out there who have flashed
their device a 100 times and they're still fine.
Some people have blamed flaky USB Connections (through Cables and Hubs), others thought it was Apps2SD.
But it also occurs with all possible precautions and without Apps2SD, so noone really knows...
[*]Any numbers on this bricking?
On MoDaCo some guy named 'afiorillo' started gathering info from all flashing users.
This thread can be found here: http://android.modaco.com/content/h...-usb-disabling-bricking-issue-data-gathering/
'eVil D:' also started a poll in http://android.modaco.com/content/h...-or-legends-lets-get-a-count-55-and-counting/
but this thread is outdated.
This is the current poll: http://android.modaco.com/content/h...-or-legends-lets-get-a-count-66-and-counting/
[*]I want to root and/or flash ROM's, what should I do?
You can now, since the fix is out, make sure you backup the misc partition /dev/mtd/mtd0 in case it gets corrupted, it's very easy to flash the
original image back.
I'd suggest you use PaulOBrien's r5 rooting method. r5 added a nohup, which should prevent recovery from ending because of a flaky USB connection during flashing.
http://android.modaco.com/content/h...e-now-with-hboot-0-80-and-os-to-1-21-support/
ahmgsk released a different custom recovery http://forum.xda-developers.com/showthread.php?t=689778
This recovery supports wiping of ext partitions which is usefull for people using Apps2SD.
The method behind both recoveries is the same, so that might be because fewer people are willing to take the risk.
ahmgsk flashes over 30 times a day and his phone is fine. But this is no guarantee.
'ieftm' on XDA mentioned this command for linux
sudo ./adb-linux shell sh -c "nohup /sbin/recovery &"
See here: http://forum.xda-developers.com/showpost.php?p=6624079&postcount=81
And ahmgsk has updated his recovery script with this line.
[*]I can wait, but for what?
You can still wait for a safer recovery (one that doesn't corrupt the misc partition)
[*]I'm USB-Bricked what should I do?
Get it fixed, follow this link: http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
You have two options here; fix what you can and wait for a fix or you send your device back. If you chose the latter, they will most likely replace your mainboard.
You might want to revert to a non-rooted official ROM even though this won't fix your problem.
[*]Fix for SD Card and (maybe) Cellular Radio
Boot into fastboot. Open a terminal. Navigate to folder where fastboot binary is located (Android SDK or whatever you used for rooting your phone)
fastboot oem enableqxdm 0
Source: http://forum.xda-developers.com/showpost.php?p=6634033&postcount=115
[*]Now I have cellular reception, but in calls I lose the connection after a few seconds?
This is called the 'Proximity Sensor Bug'.
It's unknown if it's related to the USB-Brick or the ROM you were flashing.
[*]Proxity Sensor Bug, never heard of it?
It seems that due to this bug cellular connection is lost whenever the screen turns off.
But there's no fix for this issue. And only a small subset of the USB-Brickers
has this problem.
[*]I'd like to return my device and want to flash an official ROM, how can I do that?
You can find many official ROM's here: http://forum.xda-developers.com/showthread.php?t=677513
Check this thread: http://android.modaco.com/content/htc-desire-desire-modaco-com/307683/howto-unroot-your-htc-desire/
Be wary that you can't downgrade your bootloader.
[*]Todo
Proper formatting for the forum.
[*]Disclaimer
This summary is a result of me gathering information from both XDA-developers forum and MoDaCo forum + IRC for several days.
If you believe that something is wrong or missing, feel free to PM me so I can correct/add it.
[*]This thread is useful, how can I help?
If you're also into this issue, you'd do me (and many others) a favour by using this thread to keep us updated with interesting links to other topics, tweets or quotes from IRC.
Keep it short and simple.
[*]Sunday 30 May
ahmgsk updated his recovery with ieftm's recovery command line.
http://forum.xda-developers.com/showpost.php?p=6634416&postcount=3
[*]Tuesday 1 June
Integrated the fix into the whole story.
[*]Thursday 3 June - Paranoid Rooting
Since there's still no new recovery that prevents USB-Bricks from happening, I've added a few simple steps to the original rooting process to make it even easier when you brick your device the first time.
[-] Perform step 1 of the rooting guide.
[-] Boot your device as your normally would
[-] Check SD and USB functionality, if all is well, continue at [a]
[-] If you're already bricked, which is highly unlikely, continue at
Do the USB-Brick Fix, and save the working misc.img somewhere safe and skip [a]
[a] Backup your mtd0 / misc partition while it's still good, to do this, open a shell, become root by typing 'su' and then '/mount /sdcard' type: 'cat /dev/mtd/mtd0 > /sdcard/mtd0.img' to copy the contents of this partition into /sdcard/mtd0.img and save the proper misc.img somewhere safe.
[-] Continue with step2 of the rooting process and flash the rootedupdate.zip, or any other custom Rom.
[-] Happy flashing.
Very useful guide.
Thanks
-------------------------------------
Sent via the XDA Tapatalk App
Recovery Getting update
nothing major ->
just addition of ->
'ieftm' on XDA mentioned this command for linux
sudo ./adb-linux shell sh -c "nohup /sbin/recovery &"
Click to expand...
Click to collapse
Just rooted and i was about to flash froyo until i read this, it's not worth the risk i think i am just going to unroot and wait for a fix or the official update
oawalker said:
Just rooted and i was about to flash froyo until i read this, it's not worth the risk i think i am just going to unroot and wait for a fix or the official update
Click to expand...
Click to collapse
If you are rooted there is no point in un-rooting! You can't do any damage unless you are in recovery and flashing. Stick with your current rom and sit tight for a new recovery
There's no reason to unroot if you've successfully rooted. The only risk comes when actively flashing the device - i.e. you've already gotten past the part where you could have broken it. There's no reason to go back - just sit tight where you are until it's fixed.
Edit:\\ Wow, nice timing, sock. Great minds think alike.
as my firend say in upper case
very usefull guide,m8
10ks
pls continue with exelent job
Hi, I have a noob question: How do you restore the phone to an official rom after the brick if you need the device to be connected to a PC to run the.exe? (I m asking because I can hardly resist trying froyo, and if I can return my phone after the brick, I ll take the risk.)
bee55 said:
Hi, I have a noob question: How do you restore the phone to an official rom after the brick if you need the device connected to a PC to run the.exe? (I m asking because I can hardly resist trying froyo, and if I can return my phone after the brick, I ll take the risk.)
Click to expand...
Click to collapse
Details are in the first post here by Rudolfje.
[*]I'd like to return my device and want to flash an official ROM, how can I do that?
You can find many official ROM's here: http://forum.xda-developers.com/showthread.php?t=677513
Check this thread: http://android.modaco.com/content/ht...ur-htc-desire/
Be wary that you can't downgrade your bootloader.
Click to expand...
Click to collapse
You can connect in fastboot mode, where USB still works, and flash one of the official RUUs. This will completely restore the phone software-wise, but will not restore USB-related device function.
I'm going to bow out here for now and let you carry on Prof. lol. There is no point in us both answering the same questions, and I have to get my house in order for the mrs coming over
OK, thanks for the reply. I just wasn't sure if you can still establish some kind of USB connection after the brick. I m off to flash froyo then .
socktug said:
I'm going to bow out here for now and let you carry on Prof. lol. There is no point in us both answering the same questions, and I have to get my house in order for the mrs coming over
Click to expand...
Click to collapse
Hah, my fault. Have a good one.
Good luck, FroYo flasher!
recovery just got v1.1 -> now u can start recovery via pc
then remove usb
still recovery works
ahmgsk said:
recovery just got v1.1 -> now u can start recovery via pc
then remove usb
still recovery works
Click to expand...
Click to collapse
This sounds ideal, nice work, AHMGSK you are prolific with your work on the desire, the desire comunity would be far less interesting without you so thanks
Does usb-bricking only happens with Desire? or n1 is also prone to that?
The Desire and the Legend. The N1 has an easy unlock, there's no worries.
Lots of people are now attributing this bricking issue down to using a usb hub.... I heard up to 85 percent of people bricked are using hubs.
Any thing that might help is a step forward,
JD
JupiterDroid said:
.... I heard up to 85 percent of people bricked are using hubs.,
JD
Click to expand...
Click to collapse
really, is this true? can we ask anyone here who is bricked to confirm this - if you are usb-bricked just post a quick ' yes bricked using hub ' or not !
For numbers, check out this thread\post: http://android.modaco.com/content/htc-desire-desire-modaco-com/309615/all-users-usb-disabling-bricking-issue-data-gathering/#

Noob in Need

So I'm new to the HTC One, (Literally, just got it 25 minutes ago) and coming from the Note 2 about 6 months ago, was the last time I rooted and Rom'ed a phone. Since then, I have had a completely stock Galaxy S4, and since I was unable to ROM it up, I stopped caring. Now that I just got the HTC One, I searched up the forums and see things from Bootloader isnt unlocked, to S off, etc. I am so lost, and I'm unsure where to begin. I just honestly want to find out the steps in which I need to install a ROM, since its been so long. I read the stickies, and I don't understand what is the difference between S Off, Bootloader etc. I dont even know what S Off is! lol
Thank you for helping me out, and just point me to the right direction of what to do first. Please don't be snobby, I have searched, I just dont see what you have to do first, and so on.
Also, is there a way to do any of this on a Mac? If not, I can use my laptop, but just prefer on my mac.
Thank you again!
ONLY FLASH ROMS YOU FIND IN THE VERIZON HTC ONE SECTION - roms you get from the general htc one section or ANY OTHER section will not work and will cause you major headaches. Read through this Q&A section and you will see what happens when you try and flash things you shouldnt.
Before the first thing you do you need to get the adb/fastboot stuff download the sdk from here - Android SDK - the main things you will need from the zip file you download is the "platform - tools" folder. This will give you adb and fastboot. I would suggest renaming the folder to something simple and moving it to the root of the C: drive. Any file you send to your phone via adb or fastboot needs to be in this folder.
Well the first thing you will need to do is figure out what software version you are running. To do this you need to boot your phone into the bootloader. The bootloader is a special part of the phone where you get access to fastboot, you use fastboot to flash things like recoveries, boot/system and such images as well, you also can get to the RUU tool from fastboot. To boot into the bootloader I find it easiest to power down the phone completely, once completely powered off press and hold the volume down button and power button until you get to the boot loader
Here is an image of the bootloader screen - http://www.blogcdn.com/www.engadget.com/media/2013/04/att-one-bootloader-unlocked.jpg
In the bootloader you use the volume buttons to move up and down and the power button to select.
The software version of your phone is the number next to the "OS-" in the bootloader screen it will be "OS-1.10.605.x". Once you know what software version you have, download the rumrunner tool - [s-off] rumrunner s-off for Verizon HTC One - READ the post more then once and make sure you follow the instructions exactly, with any luck you should get s-off without much trouble.
S-Off means you can change any aspect of your phone, this is a double sided sword because once s-off have more ways to turn your awesome phone into a fancy desk paperweight
Unlocked Bootloader - this is for people who unlocked there phones via htcdev, the phone is not s-off so you can not do things like install custom kernels but you do get the ability to install custom recoveries.
Custom Recovery - The tool you use to flash roms, backup your current rom, wipe your phone and restore nandroids. With the Verizon HTC One you get Clockwork or TWRP, personally I like TWRP.
Post back here when you get Rumrunner to work and I will post more instructions.
http://forum.xda-developers.com/showthread.php?t=2473644
very meticulously follow these directions. you should try to understand what s-off, unlocking the bootloader, root etc. all specifically. that said, this exploit does it all for you.
you're going to need the htc one windows drivers (if you're on windows), minus the actual htc manager software (google/search these forums for them) and you're going to need adb/fastboot, which you can find in the android sdk (google it), or in a smaller download somewhere on this forum.
Thank you. Once I finally finish movie night with the wife I want to read this all and follow through. Thank you
Sent from my HTC6500LVW using Tapatalk
No, you can't use your mac, unfortunately. Ya gotta use your pc.
So I cant download RUU for my phone, the webpage is down? Im trying to download it for 1.10.506.8 (whatever the last digit is for 8)
justinisloco said:
So I cant download RUU for my phone, the webpage is down? Im trying to download it for 1.10.506.8 (whatever the last digit is for 8)
Click to expand...
Click to collapse
RUU or Rumrunner? At this point, unless there has been a step you did not tell us, you should just need to run Rumrunner. RUU would be used to flash back to stock at some future point.
The links to Rumrunner seems to be having issues. I have been having problems with most of the links coming from goo.im. Here is a mirror you can use:
http://rumrunner.us/downloads-2/
There is a lot on this page, but assuming you are running the .8 firmware on your phone right now use this link:
http://rumrunner.us/rumrunner_downloads/rumrunner_m7wlv_1.10.605.8.zip
calash said:
RUU or Rumrunner? At this point, unless there has been a step you did not tell us, you should just need to run Rumrunner. RUU would be used to flash back to stock at some future point.
The links to Rumrunner seems to be having issues. I have been having problems with most of the links coming from goo.im. Here is a mirror you can use:
http://rumrunner.us/downloads-2/
There is a lot on this page, but assuming you are running the .8 firmware on your phone right now use this link:
http://rumrunner.us/rumrunner_downloads/rumrunner_m7wlv_1.10.605.8.zip
Click to expand...
Click to collapse
Yes I meant romrunner. I tried last night but it would say "don't pet your phone" stuff then it would fail. Ill try again
Sent from my HTC6500LVW using Tapatalk
justinisloco said:
Yes I meant romrunner. I tried last night but it would say "don't pet your phone" stuff then it would fail. Ill try again
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I too had a few issues getting it to work at first. Make sure you read the prerequisites very well and everything is perfect. Also make sure any anti-virus and firewall programs are disabled or completely uninstalled even. My firewall was causing it to hang up. Then even after that it took a few trys to get it to take. And make sure you have the correct version of rumrunner for the version of firmware your phone is using.
I also had issues getting the recover to flash, and I ended up having to update my SDK Tools and run the CMD from inside that folder where I also put the recovery. This may be common knowledge but at the time I didn't know that.
justinisloco said:
Yes I meant romrunner. I tried last night but it would say "don't pet your phone" stuff then it would fail. Ill try again
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Few things to make sure you have done for Rumrunner to work
- YOU HAVE TO USE USB2.0 if you use USB 3.0 the program will not work
- Uninstall HTC Sync and any other programs on your computer that are used with your phone
- Enable USB Debugging
- Disable Fastboot
- Enable "Unknown Sources"
- Disable "Verify Apps"
- Make sure there is no security on your phone, no passcodes, faceclock or anything else
- Disable Lock Screen Security
- Make sure you run the soju,exe with admin privileges
If that doesnt work, copy the text from the program so I can see where it went wrong.
Wozzie said:
Few things to make sure you have done for Rumrunner to work
- YOU HAVE TO USE USB2.0 if you use USB 3.0 the program will not work
- Uninstall HTC Sync and any other programs on your computer that are used with your phone
- Enable USB Debugging
- Disable Fastboot
- Enable "Unknown Sources"
- Disable "Verify Apps"
- Make sure there is no security on your phone, no passcodes, faceclock or anything else
- Disable Lock Screen Security
- Make sure you run the soju,exe with admin privileges
If that doesnt work, copy the text from the program so I can see where it went wrong.
Click to expand...
Click to collapse
I have all of that. I updated to 1.10.605.10 so maybe that may work, and rebooted my pc. I'm just getting home now so I'll see if anything changes
Sent from my HTC6500LVW using Tapatalk
OK Here is my Log-
==================== rumrunner S-OFF 0.0.3 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
ERROR: run rumrunner again and READ
Press ENTER to exit
Click to expand...
Click to collapse
justinisloco said:
OK Here is my Log-
Click to expand...
Click to collapse
Make a Ubuntu live cd, that might help. A lot of people have success with that when windows was failing them.
Edit: Depending on your computer, you might be able to make a Live USB. Live USB's are my preference but your bios has to support booting to the usb drive.
---------- Post added at 07:11 PM ---------- Previous post was at 07:08 PM ----------
Wozzie said:
Make a Ubuntu live cd, that might help. A lot of people have success with that when windows was failing them.
Edit: Depending on your computer, you might be able to make a Live USB. Live USB's are my preference but your bios has to support booting to the usb drive.
Click to expand...
Click to collapse
Use this to download Ubuntu - Ubuntu Desktop Download - make sure you download the 32-bit version.
When loading Ubuntu, you do not have to install it, you can click "Try Ubuntu" when prompted and not have to worry about having things setup on your computer to have two os's.
Wozzie said:
Make a Ubuntu live cd, that might help. A lot of people have success with that when windows was failing them.
Edit: Depending on your computer, you might be able to make a Live USB. Live USB's are my preference but your bios has to support booting to the usb drive.
Click to expand...
Click to collapse
May have to be my first time. Finally an excuse to try it out. just curious, can I run this OS on a Mac? From a flash drive? I can use my windows but it's mainly for work and now that I think of it they may have put some internet blocking thing on there (not antivirus) because of sensitive information
Sent from my HTC6500LVW using Tapatalk
as a complete noob myself, this thread was very helpful. Thanks guys
justinisloco said:
OK Here is my Log-
Click to expand...
Click to collapse
That looks like a Driver issue. Verify you can connect with ADB, if not you need to double check you have the HTC drivers installed correctly. Sometimes you have to let the phone site for a bit for all the drivers to connect correctly the first time.
calash said:
That looks like a Driver issue. Verify you can connect with ADB, if not you need to double check you have the HTC drivers installed correctly. Sometimes you have to let the phone site for a bit for all the drivers to connect correctly the first time.
Click to expand...
Click to collapse
Can you point me in the correct direction for the Drivers?
Usually, if I'm not mistaken, they usually automatically download on Windows when I plug the phone in. When I used to root the Nexus 7 for example, it wouldnt connect. The HTC I am able to connect to my PC and trade out storage, and I do not have HTC Sync installed on the Windows becauase I have nothing but work stuff on there anyway.
Im at work right now, maybe I'll use this computer and see if this helps rather than my laptop at home.
justinisloco said:
Can you point me in the correct direction for the Drivers?
Usually, if I'm not mistaken, they usually automatically download on Windows when I plug the phone in. When I used to root the Nexus 7 for example, it wouldnt connect. The HTC I am able to connect to my PC and trade out storage, and I do not have HTC Sync installed on the Windows becauase I have nothing but work stuff on there anyway.
Im at work right now, maybe I'll use this computer and see if this helps rather than my laptop at home.
Click to expand...
Click to collapse
It is listed as a requirement in the rumrunner thread: http://forum.xda-developers.com/showthread.php?t=2473644 If you dig in the thread a bit there are some good links. I think this may be the one you will end up needing:
http://forum.xda-developers.com/showthread.php?t=2376761
calash said:
It is listed as a requirement in the rumrunner thread: http://forum.xda-developers.com/showthread.php?t=2473644 If you dig in the thread a bit there are some good links. I think this may be the one you will end up needing:
http://forum.xda-developers.com/showthread.php?t=2376761
Click to expand...
Click to collapse
Alright, Work computer is a no go. When I get home, I will download those drivers and try this again. Im getting so used to keeping my phone stock at this point that I dont even know if its worth it! LOL.
Thanks again for your (and everyone so fars) help. It is appreciated!
FINALLY GOT PAST THE SCREEN!
Call me an idiot, but I didnt have USB Debugging enabled! I Couldve sworn it was already enabled! I feel like a total noob!
Now I will just follow the directions in that first thread and I should be good to go?

[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.

M9 with 5.1 OS rootable?

Earlier today, I finally made the jump to HTC after owning multiple versions of Samsungs over time. The OS version (AT&T) is confirmed as the latest 5.1. Being brand new to HTC, I know I have some learning to do in terms of rooting. Honestly I just want to have root to run a few pieces of software, but I'm not looking right now at messing with custom ROM flashes or anything like that. Mainly interested in using TiBu to do some de-bloat, and I also have an interface app needed for my car stereo that needs the root access. FYI, I used to jailbreak iPhones ages ago, plus I've had tons of luck keeping all my Samsung phones and tablets done. I consider myself somewhat techie, but need to do adequate reading on the HTC methodology so something doesn't get all gummed up in the works.
Soooo, can someone point me to a good step-by-step starting point thread? Also want to be sure 5.1 didn't close up the holes people have been using over time. Many thanks in advance!
~Vol
A follow-up question too. I'd like to make a full 100% safety backup for desktop PC archiving purposes before attempting to touch anything. What is best method to do that on HTC? Thx.
Vol4Ever said:
A follow-up question too. I'd like to make a full 100% safety backup for desktop PC archiving purposes before attempting to touch anything. What is best method to do that on HTC? Thx.
Click to expand...
Click to collapse
1) go to HTCdev.com and request an unlock token. It will walk you through the complete process of unlocking bootloader. *note* this process wipes internal storage
http://www.htcdev.com/bootloader
2) read the first three posts of the twrp thread.
http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
3) click the downloads tab of the twrp thread and download "twrp-2.8.7.1_CPTB-B1-hima.img" to your fastboot folder (during step 1 you got fastboot working on your computer).
4) reboot boot into download mode and flash twrp from a command line ("fastboot flash recovery twrp-2.8.7.1_CPTB-B1-hima.img")
5) reboot to bootloader and use the volume down button to highlight boot to recovery and press the power button to select that.
6) at the first twrp screen screen select to leave system read only
7) select backup
8) place a check next to system image. You can deselect everything else...or leave boot, data and system selected, but you really don't need them. System image is what you need to get back to stock. Data might be useful if you ever flash a custom rom and want to go back to stick, but I don't know about that. Swipe to start backup. You now have an unmodified system image that you can restore later.
9) back out to main menu, select reboot and reboot back to recovery
10) this time on the opening screen swipe the bottom to make the system r/w
11) go to reboot and select system, swipe to reboot. You're going to get a notice saying you're not rooted and ask if you want to install supersu. Swipe to do this.
12) once the phone boots up, go to the app drawer and you'll see an icon for supersu. Open that and follow the instructions on screen to finish the process. This will probably include downloading a file and rebooting into twrp again. But like I said, just follow the instructions in the app.
You're now rooted.
Hope this helps. Enjoy.
Outstanding level of detail, my friend. Will attack this tomorrow.
And congrats on being in Nashville. My wife and I have looked seriously in that area in the past. Not sure when, but I see us living in the Franklin / Brentwood area at some point in the future. Thanks again for the checklist. I'll report back when I've had a chance to complete.
Vol4Ever said:
Outstanding level of detail, my friend. Will attack this tomorrow.
And congrats on being in Nashville. My wife and I have looked seriously in that area in the past. Not sure when, but I see us living in the Franklin / Brentwood area at some point in the future. Thanks again for the checklist. I'll report back when I've had a chance to complete.
Click to expand...
Click to collapse
We're in Franklin. Post if you run into any issues.
One more thing, since you mentioned the backup. The HTCdev unlock process will wipe your entire phone. So be sure you backup anything you don't want to lose first, like photos.
iElvis said:
One more thing, since you mentioned the backup. The HTCdev unlock process will wipe your entire phone. So be sure you backup anything you don't want to lose first, like photos.
Click to expand...
Click to collapse
Yep. I figured he would read that in the dev unlock process, but it was nice of you to point that out specifically.
I was trying to keep it simple and promote reading. But I added this warning to step one.
jollywhitefoot said:
Post if you run into any issues.
Click to expand...
Click to collapse
Thanks for the tips on backups, but it is still a brand new phone. Haven't even started moving apps, music, pics, etc yet. And my first issue, as luck would have it, has appeared on your step #1 (ugh). Following through the links, I wound up here:
http://www.htcdev.com/bootloader/unlock-instructions
It talks about doing the volume down & power sequence and states the phone should go into bootloader mode. Mine actually goes into download mode, but there is a menu item there to reboot to bootloader. When I do that, it pulls up a different output screen / menu:
*** Software status: Official ***
*** LOCKED ***
*** S-ON ***
Reboot
Reboot to bootloader
Reboot to download mode
Reboot to recovery mode
Power down
The problem is that the instructions are telling me to get to "fastboot" mode before proceeding to the next steps. That particular setting doesn't show up in either the bootloader or download mode menus. Is it something simple I'm missing??
Vol4Ever said:
Thanks for the tips on backups, but it is still a brand new phone. Haven't even started moving apps, music, pics, etc yet. And my first issue, as luck would have it, has appeared on your step #1 (ugh). Following through the links, I wound up here:
http://www.htcdev.com/bootloader/unlock-instructions
It talks about doing the volume down & power sequence and states the phone should go into bootloader mode. Mine actually goes into download mode, but there is a menu item there to reboot to bootloader. When I do that, it pulls up a different output screen / menu:
*** Software status: Official ***
*** LOCKED ***
*** S-ON ***
Reboot
Reboot to bootloader
Reboot to download mode
Reboot to recovery mode
Power down
The problem is that the instructions are telling me to get to "fastboot" mode before proceeding to the next steps. That particular setting doesn't show up in either the bootloader or download mode menus. Is it something simple I'm missing??
Click to expand...
Click to collapse
The instructions aren't updated yet. The "fastboot mode" only exists on older HTC phones. The M9's "fastboot mode" is actually the "download mode".
Flippy498 said:
The M9's "fastboot mode" is actually the "download mode".
Click to expand...
Click to collapse
That got it. Bootloader unlocked & confirmed through screen menus!! Now to proceed with the rest of the backup / root procedure . . .
Thanks again.
Vol4Ever said:
That got it. Bootloader unlocked & confirmed through screen menus!! Now to proceed with the rest of the backup / root procedure . . .
Click to expand...
Click to collapse
Once you're rooted, it's really worth getting s-off through Sunshine. It's $25, but it will allow you to flash the most current firmware on your phone instead of waiting for your carrier to push it out, in addition to some other goodies like being able to change your splash image. This phone had some serious issues at launch that have since been fixed with the most recent 5.1 updates, so you don't want to be stuck on old firmware.
Well jollywhite's instructions went right down the middle and helped accomplish every line item I requested. THANK YOU!!!
So Elvis, what is this sunshine thing? I've already started cleaning up bloat with TiBu, but don't have any additional flashing on the radar. Root is good so I can now start moving all my stuff over.
Vol4Ever said:
Well jollywhite's instructions went right down the middle and helped accomplish every line item I requested. THANK YOU!!!
So Elvis, what is this sunshine thing? I've already started cleaning up bloat with TiBu, but don't have any additional flashing on the radar. Root is good so I can now start moving all my stuff over.
Click to expand...
Click to collapse
Congratulations on successfully unlocking & rooting your phone. It's a good feeling to learn how to do it and then get it done, and why XDA is such a great place.
Sunshine (currently on version 3.1) is a paid software solution that will get you S-OFF on your M9. It's developed by XDA members for aficionados - the cost is to cover their costs for materials and work done. There are some limitations and caveats, so be sure to read the thread carefully (http://forum.xda-developers.com/showthread.php?t=2792487).
[edit]Re-reading your post, it seems that you may not need or want S-OFF. If you are satisfied with a custom recovery and root, S-OFF doesn't add anything you need[/edit]
Vol4Ever said:
Well jollywhite's instructions went right down the middle and helped accomplish every line item I requested. THANK YOU!!!
So Elvis, what is this sunshine thing? I've already started cleaning up bloat with TiBu, but don't have any additional flashing on the radar. Root is good so I can now start moving all my stuff over.
Click to expand...
Click to collapse
Glad everything worked out. Good job.
At some point you're probably going to want to s-off. Waiting for AT&T to approve updates can be excruciating at times. For example, AT&T didn't release lollipop for the M8 until freaking April, where international firmware for lollipop was available in December or early January.
That said, I would probably wait because there's really not a need right now. At&t just pushed new firmware so you can run any rom you like at the moment. I'm pretty sure I read you were on 5.1 right? That means you should be on the new 2.6 firmware.
jollywhitefoot said:
That said, I would probably wait because there's really not a need right now. At&t just pushed new firmware so you can run any rom you like at the moment. I'm pretty sure I read you were on 5.1 right? That means you should be on the new 2.6 firmware.
Click to expand...
Click to collapse
Yeah, that was really surprising, AT&T actually pushed it out before Europe, which I've never seen happen before. But no guarantee that will continue.
Vol4Ever, they're correct that you can wait on s-off for now, until you're more comfortable being rooted and modding your phone. There's little real benefit in doing it at the moment.
Flippy498 said:
The instructions aren't updated yet. The "fastboot mode" only exists on older HTC phones. The M9's "fastboot mode" is actually the "download mode".
Click to expand...
Click to collapse
Thanks for this info it's were I was stuck
Sent from my HTC One M9 using XDA Free mobile app

Newbie! Zenfone 2 now rooted...now what!

Hi all,
I have a zenfone 2 that I have just rooted....so now what?
Basically I wanted to optimise my phone so I am able to disable annoying notifications which are greyed out (although since rooting and checking this it still greyed out) I want to remove bloatware and I would actually like to customise my own android system, starting from a 'vanilla' base where I can build it up myself.
I have also read that I need to install a android recovery programme on asap after rooting.
So sorry about this but I really do need 'stupid' instructions as using hi tech words will just baffle me. lol
I have played around with computers in the past and learned about them so this is the phone stage now!
Thanks in advance and for your patience with this newbie!
Kerry
Yankeegal said:
Hi all,
I have a zenfone 2 that I have just rooted....so now what?
Basically I wanted to optimise my phone so I am able to disable annoying notifications which are greyed out (although since rooting and checking this it still greyed out) I want to remove bloatware and I would actually like to customise my own android system, starting from a 'vanilla' base where I can build it up myself.
I have also read that I need to install a android recovery programme on asap after rooting.
So sorry about this but I really do need 'stupid' instructions as using hi tech words will just baffle me. lol
I have played around with computers in the past and learned about them so this is the phone stage now!
Thanks in advance and for your patience with this newbie!
Kerry
Click to expand...
Click to collapse
Hi Kerry,
First thing you should now do after rooting your device would be flashing a custom recovery that is specific to your device (make sure your devices boot loader is unlocked first). This will allow you to make a backup of everything just in case anything were to go wrong, flash custom ROMs and useful zips. You can pick your favorite custom recovery such as Team Win Recovery Projects custom recovery (TWRP), Clock Work Mods custom recovery (CWM) or Philz Touch recovery based off of CWM although personally I would recommended twrp.
There are multiple ways to do this: Using the TWRP/CWM recovery installer from the play store or the more complicated way of flashing it from your computer. If you were to choose to install TWRP from their app on the play store (grant it root permission) you can select your device from the supported device section within the app, pick the latest recovery, hit the install button and let the app work its magic. If all works correctly you can now reboot to recovery and you will see TWRP is installed. Now you should create a backup to be on the safe side and you're good to go!
To best optimize your device I would recommend installing a custom ROM (look up custom ROMs for the Zenfone 2) and install the zip through recovery. (make sure to pick the right ROM for your device and version otherwise you may soft brick your smartphone) Now with a custom ROM you can better optimize your device and fully customize it to your liking. Make sure to look up custom ROM installation instructions for your device for better detail.
As far as removing system apps/bloatware you can use a "root app delete" tool from the play store but be careful what you remove as some applications are required!
Make sure to take your time and be careful when attempting any of these things and be careful what you modify! Just remember that no question is a stupid question as we all have to start somewhere!
Hope I was able to help you even if it was just a little, good look and have fun!
Rooted Droid Thanks you so much!!! First of all thanks for being so patient with me and secondly thanks for the useful (and easy to read) information.
I will go and install a back up on my phone from the ones you have suggested.
Hopefully you will be around over the next few days if I have more questions. Not planning on doing this all at once but rather taking the time and doing it right.
Thanks so much again!! :good::good::good:
Ooops sorry....how do I do this please?? ---> (make sure your devices boot loader is unlocked first)
Yankeegal said:
Rooted Droid Thanks you so much!!! First of all thanks for being so patient with me and secondly thanks for the useful (and easy to read) information.
I will go and install a back up on my phone from the ones you have suggested.
Hopefully you will be around over the next few days if I have more questions. Not planning on doing this all at once but rather taking the time and doing it right.
Thanks so much again!! :good::good::good:
Click to expand...
Click to collapse
Not a problem! I'm always happy to spread some knowledge and appreciate when people do the same to me! I also went ahead and checked the TWRP app and the Zenfone 2 is supported so it looks like your good to go. And yes absolutely, there's no rush so take all the time you may need and everything will go smoothly! I'm always around and will try my best to answer questions.
---------- Post added at 08:02 AM ---------- Previous post was at 07:41 AM ----------
Yankeegal said:
Ooops sorry....how do I do this please?? ---> (make sure your devices boot loader is unlocked first)
Click to expand...
Click to collapse
Check this site out:
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
All devices have a different method for unlocking bootloader (some don't even have locked bootloaders) but this is an official bootloader unlocking method for the Zenfone 2 from Asus itself. I suggest following its directions and you should be able to unlock it this way.
Ok I followed the link but now I am confused. I have version ww_2.20.40.63_201......
Apparently I need a later version. What started off with just adding an APP means me doing other things before I even get to that point (hence the confusion! lol)
I never updated the phone via OTA as I was told it would invalidate my warranty and also I have killed a phone before using that so can you walk me through please...if you have the time....or could I just check if I have it unlocked already??
I haven't even gotten to the part where I create a backup...tee hee
Yankeegal said:
Ok I followed the link but now I am confused. I have version ww_2.20.40.63_201......
Apparently I need a later version. What started off with just adding an APP means me doing other things before I even get to that point (hence the confusion! lol)
I never updated the phone via OTA as I was told it would invalidate my warranty and also I have killed a phone before using that so can you walk me through please...if you have the time....or could I just check if I have it unlocked already??
I haven't even gotten to the part where I create a backup...tee hee
Click to expand...
Click to collapse
Hi sorry for the late reply, I'm in Canada so it was 2am when I was last talking to you so I went to bed haha. Anyway as far as unlocking the Zenfone 2's bootloader I wouldn't have experience unfortunately as I'm using a Nexus 5. The easiest way to go about this now would be to go to your device specific forum and find a way to unlock it there.
The following way to unlock the bootloader requires you have ADB installed on your PC. This is a guide for installation on Windows :
http://www.android.gs/install-android-sdk-adb-windows/
And here is a thread specific to unlocking the Zenfone 2 using adb:
http://www.xda-developers.com/asus-zenfone-2-bootloader-unlocked-without-asus/
BTW as you mentioned "updating may invalidate your warranty" things like rooting, installing a custom OS, unlocking the bootloader, installing a custom recovery and other things like that all (in most cases) void your warranty.
Sorry I can't personally help with the bootloader as I've not personally unlocked it on a Zenfone. Still feel free to ask any questions if you need to. Good luck!

Categories

Resources