Develop Bugs

The issues continue......

Hey,
Made a few posts relating to my issues with the galaxy nexus and it not charging etc....
Now I have contacted Samsung and they said send it for repair, not this leaves me in a bit of a pickle seeing as the phone has been rooted since day one.
The issue comes as the phone does not respond to being plugged into the computer despite all drivers being installed.
Has any bright person got any idea's to removing the root on the handset and re-flashing stock .img without the need of adb and fastboot seeing as the phone just comes up as not recognised, probably due to the issues with the USB port on the handset (see initial problem...)
Don't really want to send it back to Samsung rooted as they will just send it back saying its my fault even though its not and its a hardware issue.... not software.
Any advice would be great,
J
P.s. Had a check around the internet on several Google groups about this issue and the only conclusion is send back to Samsung or get a new USB port for the phone from Ebay.

Just flash a stock ROM in recovery then use this app to lock bootloader http://forum.xda-developers.com/showthread.php?p=27878074 and then unroot (SuperSU has this option).

You are my friend is why i love XDA , thanks for the advice.
J

See this post for a much better explanation
http://rootzwiki.com/topic/19864-vz...ockrootflash-romsfaq/page__st__40#entry759280
Essentially that tells you to lock bootloader and then use mobile odin to flash a stock ROM.

mbh87 said:
See this post for a much better explanation
http://rootzwiki.com/topic/19864-vz...ockrootflash-romsfaq/page__st__40#entry759280
Essentially that tells you to lock bootloader and then use mobile odin to flash a stock ROM.
Click to expand...
Click to collapse
Same guide is posted here on XDA, sir.
Thanks for the reference, though =]

Jubakuba said:
Same guide is posted here on XDA, sir.
Thanks for the reference, though =]
Click to expand...
Click to collapse
Yeah I know but I was browsing rootz too and you already posted on the page I was on so was easier to find the guide there

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] Can I flash a new bootloader using recovery (twrp)?

Can I flash a new bootloader using recovery (twrp)? (flashed plenty of ROMs and Kernels wasn't sure if the steps are the same for a bootloader)
So if I plug my rooted Nexus 7(2013) in to any usb cable on any computer, it is just not detected(assuming usb port is dead at this point, only charges), Cannot even get adbd wifi to start and listen on port 5555 went through every possible scenario.( basically tried everything you can will throw at me, (MTP/PTP, usb debugging on/off, new cables, new computers, remove every possible android driver and re-install)
I saw one post where someone seemed to have a similar issue but was able to update the bootloader and his problem was solved!
Now I am not sure how he did it since I can't seem to find any good info on updating the bootloader directly from say TWRP I have no other access into the device remotely or via USB

kernelsandirs said:
Can I flash a new bootloader using recovery (twrp)? (flashed plenty of ROMs and Kernels wasn't sure if the steps are the same for a bootloader)
So if I plug my rooted Nexus 7(2013) in to any usb cable on any computer, it is just not detected(assuming usb port is dead at this point, only charges), Cannot even get adbd wifi to start and listen on port 5555 went through every possible scenario.( basically tried everything you can will throw at me, (MTP/PTP, usb debugging on/off, new cables, new computers, remove every possible android driver and re-install)
I saw one post where someone seemed to have a similar issue but was able to update the bootloader and his problem was solved!
Now I am not sure how he did it since I can't seem to find any good info on updating the bootloader directly from say TWRP I have no other access into the device remotely or via USB
Click to expand...
Click to collapse
Yeah it's possible, I did it for the Nexus 4 before. Usually the bootloader update files are found within the OTA zip updates. Usually the bootloader is composed of multiple files, not just one. You can take those files and put them in a flashable zip and make sure the script flash the files to the correct partition of the device, all the info are in the updater-script file in the zip.
It look like this is the last OTA update for the N7 that have the bootloader files: http://android.clients.google.com/p....signed-razor-KTU84L-from-KOT49H.df43279b.zip
So you can use make a flashable zip for those bootloader files or I can do it later.
I guess a smarter person would be able to dump these partitions from their device, maybe just by using "dd" command while in recovery's ADB.

I previously flashed a pre-rooted 4.4.4 OTA Stock ROM which is what I have been running ever since.
I really don't know if, or why the bootloader would affect my ability to use the USB port or not, but I guess I just had some hope based on one other post that seemed to work with.
I am not sure how to make a flashable zip from an existing ROM image, only flashable zips I made came from Titanium backup producing the flashable files for me
eksasol said:
Yeah it's possible, I did it for the Nexus 4 before. Usually the bootloader update files are found within the OTA zip updates. Usually the bootloader is composed of multiple files, not just one. You can take those files and put them in a flashable zip and make sure the script is flash it to the correct partition of the device, all these infos are usually found in the official OTA zip. The problem is not all OTA zip have bootloader files, just the one that specifically update it.
It look like this is the last OTA update for the N7 that have the bootloader files: http://android.clients.google.com/p....signed-razor-KTU84L-from-KOT49H.df43279b.zip
So you can use make a flashable zip for those bootloader files or I can do it later.
The next one will be for Android 5, so we'll look forward to that also. I guess a smarter person would be able to dump these partitions from their device or something.
Click to expand...
Click to collapse

So your computer doesn't recognize the tablet when it's at the bootloader? Can you even get into bootloader? Tried different cables? Different USB ports?

I can get to TWRP, but no usb not recognized there, cannot use the mount feature in TWRP, tried all items in pretty much every post I could find that were related, inlcuding the items you suggest yes.
Maybe something with the stock rooted ROM has gone wacky, Been very good to this tablet as far as babying the usb port, as I have had other devices have broken ports as my kids would yank cables etc.
So really the only thing I have not done since this trouble started was just do a factory reset and re-flash the ROM, just afraid that is something goes wrong durring flash I will be out of luck restoring anything since I cannot get to the filesystem to put new ROMS etc unless I download them to SD before I begin the process while I have access to the OS and wifi.
nhizzat said:
So your computer doesn't recognize the tablet when it's at the bootloader? Can you even get into bootloader? Tried different cables? Different USB ports?
Click to expand...
Click to collapse

[snip]

Thanks @eksasol I think I may just let this sucker chill until the stock rooted Lollipop ROM, I was already on 4.02 I just thought there was a newer one, I think the Lollipop version has a 4.04 bootloader.
I greatly appreciate your time on this.
So I would assume that if the flash fails for any reason I will be the proud new owner of a nexus 9 shortly after

@eksasol do you have a flashable 4.04 bootloader or know a guide to making a bootloader flashable, I did use your 4.02 and it worked great, but for the Lollipop version I need 4.04 but can only find .img that needs fastboot, which I do not have access to since USB does not seem to work still.

kernelsandirs said:
@eksasol do you have a flashable 4.04 bootloader or know a guide to making a bootloader flashable, I did use your 4.02 and it worked great, but for the Lollipop version I need 4.04 but can only find .img that needs fastboot, which I do not have access to since USB does not seem to work still.
Click to expand...
Click to collapse
You will need to wait until the OTA zip for KitKat to Lollipop become available, it will include the proper 4.04 bootloader files needed for flashing.

OK cool, guess I am just impatient

@eksasol any chance you can throw a flashable 4.04 bootloader together, i see several others looking for one that are in the same boat as me, i looked around for a tutorial on making one but did not find any so far. Anyway if you get a chance or have some info on making one i would be grateful.

Here is the Android 5.0 bootloader version 4.04. For Nexus 7 WiFi only (Flo, Razor), again it will check to see if it's the correct device before proceeding with flashing. Go to this link: http://forum.xda-developers.com/nexus-7-2013/general/flashable-factory-image-zips-android-5-t2939599
kernelsandirs said:
@eksasol any chance you can throw a flashable 4.04 bootloader together, i see several others looking for one that are in the same boat as me, i looked around for a tutorial on making one but did not find any so far. Anyway if you get a chance or have some info on making one i would be grateful.
Click to expand...
Click to collapse
You didn't have to remind me every single day.

Thanks for this. I'm alright with adb and fastboot (i.e. I can follow directions) but I'm running the Windows 10 tech preview and it absolutely does not support either. Drivers are fine, it just won't do it. Won't happen at all. Then I throw it all on a flash, take it to work (Win7 Pro), and it works just as easy as you like, so it's not (likely) user incompetence... I woulda waited but figured someone else might have asked. So, much appreciated!

dragontology said:
Thanks for this. I'm alright with adb and fastboot (i.e. I can follow directions) but I'm running the Windows 10 tech preview and it absolutely does not support either. Drivers are fine, it just won't do it. Won't happen at all. Then I throw it all on a flash, take it to work (Win7 Pro), and it works just as easy as you like, so it's not (likely) user incompetence... I woulda waited but figured someone else might have asked. So, much appreciated!
Click to expand...
Click to collapse
They decided to skip 9?
I posted the full device's image in flashable zip formats here:
http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/

unbricking Alcatel OT 4037T evolve 2

Hey guy's,
Hopefully This is in the right place. Please assist in anyway you possibly can. This phone is not a brick, but it might aswell be. I have tried literally every kind of reset unbrick guide I can find for the past 2 months, and nothing works.
From what I can tell it is a driver issue, but even installing the meta mediatek preloader, and drivers does not seem to work. I have tried a fresh install of windows 8.1, windows 7, and xp. nothing works. I can not install the adb drivers for this device, because the phone will not even boot into recover. Recovery is corupted or something. I do have an mtkdroidtools backup, but can not flash it with sp flash because it always gives the error "THIS IS A SECURE BASEBAND CHIP PLEASE LOAD AUTHENICATION FILE". I've worked with kirito9 which was a big help in understanding a few things, but we could not get it sorted. I will stop talking now, and post something useful.
BTW:mobile upgrade tool s does not work either. I get terminal read failure.
As of now im on windows 8.1 with drivers installed. I have posted a couple of videos to show whats going on. Hopefully they will help. I can post some logs, but I honestly dont know which ones you would want, I have a lot of them, and have tried so many things I dont know where to begin again. In the zip file there is 2 videos, and the original mtk.log.
I forgot to mention that, this all started when I wanted to root, and install a custom recovery. I believe I used the guide on here but cant remember seeing as it was a while ago. Also the phone does not vibrate at all. Like I said I have a backup, but I dont remember much about it I dont know how reliable it is, and if I read back with sp flash or not. I believe I had to right? idk. thanks in advance.
https://drive.google.com/file/d/0B_DyVUIoGhqBSXlhbkNhdVNCR1k/view?usp=sharing

Wow I cant believe nobody has run into this problem. That or you guy's are just busy which I totally understand.. I'm just really frustrated. I think I am going to try to return it to t-mobile. You gotta know when your defeated, and this is it. This phone has been a nightmare.... I just hate giving up. I broke it, and I wanted to fix it.
Anyway if this was in the wrong lace to post please let me know. thanks.

I called t-mobile, and told them it didnt work. They asked the normal questions, and agreed to replace it. The guy said they are going to check it out to verify condition. Once they play with it enough to power it on they will see the flash error.
Is this something to worry about? also, is there a way to make sure it doesnt power on? I know thats shady, I just cant afford the deductible right now seeing as i'm out of work at the moment.

TireIron431 said:
I called t-mobile, and told them it didnt work. They asked the normal questions, and agreed to replace it. The guy said they are going to check it out to verify condition. Once they play with it enough to power it on they will see the flash error.
Is this something to worry about? also, is there a way to make sure it doesnt power on? I know thats shady, I just cant afford the deductible right now seeing as i'm out of work at the moment.
Click to expand...
Click to collapse
Hey man, I cant really help with unbricking it. Mediatek chips are not my strong point but i just wanted to say logically if the recovery is corrputed and the rom is corrupted and the bootloader is not playing ball then unless the chips have a write counter/modification check then you should be okay I reckon.
Good luck though

I still have it because I wanted to at least make it boot ok, but to no avail. I got the replacement and made a good back up with mtk droid, but I still get the error.
The phone is an Identical copy of my last one, and still no go. I even tried to flash it with the new phone, I get the same error. so I guess im a monkey, and cant do it right. If it's doing the same thing with the new phone as it is with the bricked one, than its me right?
I did notice that I cant create a scatter file with the create scatter button(its greyed out) I can only make one through the firmware.info.
This is the phone info from both phones.
Hardware : MT6581
Model : ALCATEL ONE TOUCH 4037T
Build number : ALPS.KK1.MP1.V2.10
Build date UTC : 20140918-073410
Android v : 4.4.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V34.P13, 2014/09/18 15:26
Kernel v : 3.4.67 ([email protected]) (gcc version 4.7 (GCC) ) #1 SMP Mon Sep 8 10:47:59 CST 2014
Uboot build v : ----- should be root shell
LCD Driver IC : 0-nt35512_dsi_vdo_tdt_lcm_drv
From what I have read this is actually a 6572 chip. Is this correct? I was just thinking that maybe droid tools wasn't reading it right, or backing it up right. Droid tools creats a 6582 scatter file, but my phone says 6581, and I saw 6572. Which one is it? I cant find or make a 6581, so I do not know what to do. I have tried both phones with all of the different drivers, with the different scatters, and I always get error 5000 secure baseband chip.

Hello TireIron, in these moments I am passing through the same despair that you suffered with your telephone, I have done the same steps exactly than for the ones that you passed, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.I have done the same steps you passed for, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.
I don't know, if at the end you could solve the problem and recovering the telephone, if so, what solution did you find? I would thank you for if you shared the solution.
Thanks from the start.

danymt87 said:
Hello TireIron, in these moments I am passing through the same despair that you suffered with your telephone, I have done the same steps exactly than for the ones that you passed, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.I have done the same steps you passed for, although with less results, not even I have been able to find the scatter of the device to use sp flash tool.
I don't know, if at the end you could solve the problem and recovering the telephone, if so, what solution did you find? I would thank you for if you shared the solution.
Thanks from the start.
Click to expand...
Click to collapse
Your issue is you flashed with the secure bootloader still active, as to why your having issues flashing it back... I've been searching around for a Custom Recovery/ROM, I'll check back in if I find anything on Disabling the Secure Bootloader, as I see it your not going to be able to restore (even to STOCK) without Unlocking the Bootloader/ And/Or Reactivating it upon re-flash.... So far no luck on finding a way to disable it, but just started a couple hours ago....
Mike
UPDATE:
ok Upon more searching it appears at the moment you need an NCK BOX...
https://www.google.com/search?q=unl...-8#newwindow=1&q=disable+secure+boot+on+4037t
http://www.ebay.vn/mo-ta-san-pham-281534386171.html

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