Develop Bugs

[Q] How to root 1.32.651.6?

Can someone please help me. I am googling, xda, phandroid, htcevohacks and not finding any clear cut answer to this question: Can i root my evo running 1.32.651.6 (SD update)? i see there are ways to root with the new update 1.47........., so since i cant find any clear cut answers regarding 1.32.651.6 should i accept the update to 1.47.651.1? I am so confused some people say they have used toast method to root 1.32.651.6 and others who say that it is impossible, can someone please help me. Thank you

Regular simpleroot

I almost feel bad...all I saw was ".6" (Thinking it was referencing 2.2) and I was about to facepalm.
Some have had problems with the original simpleroot (I was one of them)...go here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/Guides_&_Tutorials
and do Toasts Part 1 and Part 2 step for step. If you run into any roadblocks, just post back to this thread and we will be happy to help you out.
I was a total Android/Linux noob when I got the Evo. I came from WinMo and as far as modding goes, it felt like I went from Champ to Chump. Read, make mistakes, read some more, fix your mistakes, and learn. It doesn't get any better than that. Just remember, we are a community that is here to help, not do it for you.

Finally ROOTED!!
OK guys i have rooted my EVO thanks to u guys. I have installed Froyo DeOdexed RevE.1, I have downloaded rom manager from the market. Now do i always have to wipe every time i load a new rooted rom? Also do i have to go into the shell with evo connected to PC to get to the menu for wiping and loading roms? Do i also have to load the updated radios and wimax or do the rooted roms come with them already? Many thanks.

MaverickSITG said:
OK guys i have rooted my EVO thanks to u guys. I have installed Froyo DeOdexed RevE.1, I have downloaded rom manager from the market. Now do i always have to wipe every time i load a new rooted rom? Also do i have to go into the shell with evo connected to PC to get to the menu for wiping and loading roms? Many thanks.
Click to expand...
Click to collapse
Wiping is advised when flashing a new ROM, unless you are upgrading to a newer version of the same ROM (or if the author says no-wipe is required). Wiping is almost always required if you are changing between different ROM.
You can enter recovery by turning phone off, pressing power + volume down, or booting into recovery from apps such as Rom Manager, Spare Parts, Quickboot.

[Q] Moving from WM6.5 to Epic 4G, suggestion?

Let me first tell you about myself.
1. I'm a geek.
2. I don't like programming that much, so I avoid it. I learn stuff to get by, but yes I avoid it. I have access to both XP & Linux, running it as a PDC server at home along w/ VPN server (ClearOS w/ modified bridge OpenVPN ).
Some background about myself that may help you answered my question, or pointing in the right correct direction. (no middle finger to the right.) And here is past experience on mobile device.
I have used Nokia 770 and N800, fun to hack back then but it's pretty useless now. I had SERO 500 , which I just recently upgraded to SERO Premium 500. I have been using HTC TP2 w/ Energy ROM. It has been good, granted TP2 is an older phone w/ older Qualcomm CPU. Energy ROM did help a lot, along w/ a few tweak, I manage to keep the battery to last pretty long and upon boot up I got about 70% memory left to use. So, I'm not exactly new to the custom ROM myself. That said, I'm new to the Android phone and custom ROM. I have been reading in the past 2 weeks deciding between Epic 4G and EVO Shift 4G. Well, I end up w/ Epic 4G as a final choice. Already ordered the phone, but still waiting for it. So, I don't have Epic 4G as off right now. But I would like to start playing w/ it once I get a hold of it. That's why I end up here asking for some wisdom in this forum.
After doing some research, I think I think get the basic concept of flashing custom ROM on a new Epic phone. If I got it wrong, let me know.
prep step 0. get USB drivers.
1. root it, 2 steps root?
2. install CWM3 for recovery.
3. flash new ROM, appearance each chef have difference instruction for the install. That's where it start confusing me.
Few things that are unclear to me, should I update PRL prior to rooting it and flash new ROM or after? Or should I even put DK28 on it prior to start rooting it? I'm guessing a no on 2nd one, as it's not necessary.
Now, rough question, what ROM is close in term of the way it package that most closed to the Energy ROM. I'm leaning toward either Nebula or Bonsai. Since Epic is only on Sprint only, I'm sure some of you have use TP2 or might have even used Energy ROM in the past. If you haven't, I'm sure you know where to look for reference. Again, what I very looking for is a Froyo ROM(if not Gingerbread) that's clean, lean, snappy and stable. In fact I don't even care if the Samsung TouchWiz is totally removed. I even think I might like Touch Flo interface better, but I suppose I won't have it. I think I have read enough to know where to find the TouchWiz apk(s) and remove it, so that's not a big problem.

Welcome to android your steps are 1.get drivers 2 dl one click root plus cwm. Once you have it rooted with cwm you can start flashing. If you want to go to the froyo leak then flash the upgrade first then start the root process. If you go with froyo,which I love it and I have bonsai rom and it works perfect, you have some choices when rooting. If you want to stay with the stock Rfs filing system use the one click with cwm v2.5. If you want to run ext4filing system then run the one click root with cwm3. This new clockwork will convert your filing system to ext4 for you. My setup is in my sig and is my favorite. It's up to you to pick the rom you like the best. Make sure before you root turn your USB debugging on. Good luck and welcome to android.

In addition to what was posted, Nrgz is a great chef. I used his stuff for quite some time when I had my TP2.
That being said.. WinMo and Android are 2 different animals.
I think you'll find that you're going to flash each ROM and play with it for a few days to determine which one you prefer.
They are all very nice in their own right. Some of us have favs. The neat thing about android vs WinMo is that after you flash a ROM in Winmo, it's a big pain in the ass to set your device back up (if you weren't using custom scripts).. with android, it's much much easier and can be completed within a couple minutes.
I think you'll enjoy that aspect of it.
Welcome to Android

I'm making the same transition as you, long live the TP2. I followed the how-to recommended by the wiki, but a lot of that is actually a waste of time at this point, except as a learning experience. The steps that actually got me ROMed (I'm assuming you'll pick an Ext4/DK28 ROM:
1. install 32-bit drivers on Windows
2. put phone into debug, connect
3. flash DK28 to phone using ODIN
4. copy zip for ROM of choice to root of sdcard
5. run cwm3 to change file system, root device
6. flash with custom ROM while in recovery
From what I understand, only steps 4 and 6 will have to be repeated when trying other ROMs. Wifi tethering isn't working for me on ViperROM, so I think I'll try something else.

[Q] General rooting and ROM questions

Hi guys, I've had a Bell-branded Desire Z (on AT&T's network) for some time now, but I've never gotten around to rooting / flashing a different ROM on it. Since I have some free time this weekend, I figure I'll finally tackle it. Have a few general questions though:
1) Is the method listed in the guide: http://forum.xda-developers.com/showthread.php?t=928160 still the best method for rooting a desire Z? I've heard bad things about visionary, but every rooting method I've read seem to involve it in some way.
2) with S-OFF, am I free to flash any Desire Z / G2 ROM? or will only certain ROMs work with a Bell Desire Z? Any specific recommendation on ROMs? I'm planning on trying out CM7, then going from there
3) What is the best method for backing up my current image + a few other things (mostly contacts and SMS)? Titaniumbackup gets thrown around a lot, but I only have a handful of apps, and really would rather just redownload them then go through the trouble of backing them up
Thanks

http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
that is going to be your safest way to root your vision. eventhough this is longer, there is a lot less chance of bricking your phone. the one you listed is very simple to do, but runs a high risk of turning your phone into a paper weight.
when you do have your phone completely s off, you now have every right to flash kernels, roms, and other things. you can find all of the things i just listed over in the development forum on the g2/desire z. download rom manager from the market. that allows you to back up your current rom, flash the latest recovery and so on. it just allows you to not have to manually install everything. it has the popular g2 roms under the "download rom section".
in terms of backing up everything, there are a few different options. every contact to save is linked to your gmail account, so whatever rom you flash and load youll always have those contacts coming with you. thats the beauty of google and gmail on a android device! but with rom manager, you can back up your current rom and image with that app and save it to your sd card. BEFORE YOU FLASH ANY ROM, OR BEGIN TO START TRYING OUT ROMS, BACK UP YOUR STOCK ROM. whenever i got my g2 when it first came out, i made a nandroid backup of my stock rom and i still have it. when i originally backed it up, i just named it "stock" and havent messed with it since. i just know that i have the stock image(it helps me sleep at night). jk, heh. for your text messages and stuff, download sms backup from the market and you can back everything up through that. all of the apps that you download, including the paid ones of course, travel with you between roms, etc.
i hope i helped ya out, and i wish you luck. if you have any other questions, just shoot me a private message!

Thanks for that;
I actually went ahead and used that method in the guide since upon further research, it seems that visonary was only causing issues when it was use for perm root; temp root, which is what that method uses visionary for seems to work fine.
So did that, reboot into the bootloader, confirmed that I had S-OFF on the first line.
Installed ROM manager from the market
Flashed Clockwork recovery
Booted into recovery and did a system backup to SD card
Rebooted and decided to download the Virtuous ROM from ROM manager
Told it to reboot into recovery and flash that image, wiping all data and settings
Got stuck on an bootup loop (HTC logo + start up sound -> black screen -> HTC logo + startup sound ad infinitum)
Rebooted into recovery, and did a restore from the backup (whew)
Phone seems to be working fine now
Now I'm trying to figure out what went wrong... any ideas?

K, I redownloaded virtuous from XDA, checked the MD5, and tried to flash it again.
Same problem, infinite loop on startup screen.
Do i need to flash the engineering hboot? I was under the impression that that wasn't necessary for using custom ROMs.
Still can't figure out what's wrong.

did you debrand? http://forum.xda-developers.com/showthread.php?t=835777

Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!

Im new to this stuff here, and i DO want to learn about it as this stuff is very interesting to me! Technology is something i learn very quickly if im directed in the correct direction
The question i have here is about my Desire Z ( Bell Cannada ).
A few months ago we received a OTA update. So its currently running on Android 2.2.1 : Build - 1.84.666.2 CL322105, and its SUPER slow! Is it still possible to root this version?
I want to install the Gingerbread version on my phone, but i cant find instructions to root this OS version to be able to do so.
Or should i wait till the Official gingerbread Os to come out for our phones?
Ive been searching every where's for this info and everything i find is all back dated to last yr and nothing up-to-date after the OTA.
I hope this question is not TOO n00bish as i tried to search every where for it, and ether i could not find it or i did not enter the correct word search to get a result i needed.
Thanks in advance!
Andrew
Edit: NVM my question here.... i have finally found an update post within the wiki ( April 1 2011 )
Sorry for a useless post!
Thank you all for your efforts in posting in this forum! Very informative!

Athrun88 said:
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Click to expand...
Click to collapse
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.

deaththeorist said:
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Click to expand...
Click to collapse
You do not need to debrand to flash custom ROMs to the Bell Canada Desire Z.

makken85 said:
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
Click to expand...
Click to collapse
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.

redpoint73 said:
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
Click to expand...
Click to collapse
Yeah, I assumed that flashing from ROM manager just meant that it rebooted to recovery and flashed it from there. I guess there is a difference.
Either way, been playing with Virtuous 1.0.2 for a few days now, really like this ROM, but I'm itching to try out something different now. Man, I can see this is going to develop into a time consuming hobby.
Plus, I'm going to need a bigger SD card to store all of these ROMs + backup =X
Oh, another noob question; I've come across a few zip files that included a system folder and an META-INF folder. How exactly do I install these?

G2 only works with at&t
alright here it is my t-mobile G2 won't connect to the t-mobile network at all, I've went through 3 SIM cards because this thing use to kill the SIM card from working on other t-mobile phones and it works perfectly fine on at&t network. so I've unlocked so it will work on at&t just to see if it would work. so i gave p and bought a MT 4G, but i still want to know if the G2 is fixable because I'm just about ready to throw in the towel this is what I've tried to resolve the problem called t-mobile they ended up saying just return the phone but i can't since i didn't buy it from them. Called them again got the unlock code. I've flashed the radio a few times. I've also just got the leaked 2.3.3 update and nothing has worked. It find t-mobile network but says your SIM card isn't allowed to connect to this network then after trying again it says unable to connect to network please try again later.
Just so frustrating i don't know what to do just about to say forget it. this thread is my last resort.
also i still have S-OFF

i used this method on my G2 just yesterday and put on CM7.0.3. the only issues i came across were because i restored everything (should have just done apps and app data) using Titanium, which put me in a boot loop. I'm dumb, so i did it twice before i figured out what was the problem. the thread has a comment about how Visionary is dangerous, but the OP responded that since it is only used to gain temp root, there should be no problems.

[Q] (yet another newbie) Qs relating rooting - PC compatability, past issues etc.

I've searched but can't seem to find anyone else asking the same thing, and I'm not 100% sure I understand the answers to Q2 that I have found so apologies in advance.
Long story short, I'm keen to root my HTC Desire (Bravo).
HBOOT 0.93.0001
Radio 5.09.0530_2
Android 2.2
Baseband version 32.55.00.32U_5.09.05.30_2
A bit of background...
About a year ago, I followed a guide that used HTC sync and required the SDK development kit to be downloaded to be able to force the phone to transfer more apps onto the SD (the phone was, and remains, unrooted - this was linked to Android 2.2 but required a code or something of the sort to be modified via the SDK).
- I had a number of issues doing this, and the whole process never worked as the guide said it should: HTC sync never worked for my phone, and the SDK pack (yes I did triple check it was the right version etc) didn't have all the options etc. And it never appeared to have worked, although it mysteriously had in the end, but I had no idea it had even worked due to the gaps and issues during the process.
Because of this, I'm a bit hesitant to do something more aggressive like rooting if my PC - phone link didn't seem to work (i.e. HTC sync never worked with my phone), so:
1. would it be better to try the root on a Vista 32-bit (my PC) or a windows 7 64-bit (my laptop)?
- I *think*, but am not 100% sure, that I might have also tried to do the above things with the SDK on the laptop, or I might have considered it until I randomly found the process had worked despite nothing appearing to have worked.
2. I plan on following the guide here, which makes sense, however I'm not sure what to do after I root
- I have read a few threads taht talk about recovery, nand-backups, flashing permanent vs temporary ROMs but the more I read the more confused I get as to what I need to do after rooting.
- Essentially I want to root so I can try a custom ROM, but would like to have a "safety net" in case I completely mess it up, so I don't end up with a bricked phone.
Once again, apologies for the likely repetition in questions, particularly Q 2 - have yet to find a clear easy to follow guide that runs from rooting --> loading different custom ROMs, including making a backup in case things go wrong together.
Kudos

[Q] A Few Questions About New Nexus 7

Sorry in advance as I'm sure these questions are added somewhere. Just looking to be pointed to some threads or other places with good info.
I just got a new 2013 N7 and it came with 4.3 build A# JWR66N.
Upon first run, there are a couple of system updates available that I am hesitant to install. I'm guessing they are to update it to the newest 4.4. Just wondering if I should do this or if it will cripple or lock anything else having to do with rooting or flashing custom ROM's
First thing I noticed is it looks just like the custom EOS 4.1.1 I flashed into my Xoom tablet a few years ago and coming from a Galaxy tab, there is no option to clear all recent apps (the Galaxy has a small garbage can symbol in the recent apps list that gets rid of everything with one touch). I was wondering if there is something like this for the N7 (either an app or a custom ROM that has it).
Also, I knew before buying it that OTG was crippled. My friend has one and said he rooted and used stickmount to get full OTG read-write access. Wondering if there is a better alternative (or if there is a custom ROM with this already fixed).
I have been seeing a lot of stuff about a N7 FLO. What is this and how do I know if I have it?
Last, I am definitely interested in unlocking/rooting/adding a custom ROM to it but looking for some good direction for this. I have been searching through these boards and my head is spinning from all the different info. Last time I rooted and flashed a custom rom was a few years ago with my Motorola Xoom and I did it all manually with ADB and some other stuff and it went smooth. It seems like everything written on here is made for people that already know what they are doing and although I have done it before, and have no problems following instructions, it's been a few years I am looking for a good link or links to some beginner guides so I can kinda go back to the beginning and refresh myself before going into this. I am also not opposed to using WUG's toolkit or similar but would still like to better understand doing things manually in case something goes wrong.
Any info you can provide would be greatly appreciated.

happy4ya said:
Sorry in advance as I'm sure these questions are added somewhere. Just looking to be pointed to some threads or other places with good info.
I just got a new 2013 N7 and it came with 4.3 build A# JWR66N.
Upon first run, there are a couple of system updates available that I am hesitant to install. I'm guessing they are to update it to the newest 4.4. Just wondering if I should do this or if it will cripple or lock anything else having to do with rooting or flashing custom ROM's
First thing I noticed is it looks just like the custom EOS 4.1.1 I flashed into my Xoom tablet a few years ago and coming from a Galaxy tab, there is no option to clear all recent apps (the Galaxy has a small garbage can symbol in the recent apps list that gets rid of everything with one touch). I was wondering if there is something like this for the N7 (either an app or a custom ROM that has it).
Also, I knew before buying it that OTG was crippled. My friend has one and said he rooted and used stickmount to get full OTG read-write access. Wondering if there is a better alternative (or if there is a custom ROM with this already fixed).
I have been seeing a lot of stuff about a N7 FLO. What is this and how do I know if I have it?
Last, I am definitely interested in unlocking/rooting/adding a custom ROM to it but looking for some good direction for this. I have been searching through these boards and my head is spinning from all the different info. Last time I rooted and flashed a custom rom was a few years ago with my Motorola Xoom and I did it all manually with ADB and some other stuff and it went smooth. It seems like everything written on here is made for people that already know what they are doing and although I have done it before, and have no problems following instructions, it's been a few years I am looking for a good link or links to some beginner guides so I can kinda go back to the beginning and refresh myself before going into this. I am also not opposed to using WUG's toolkit or similar but would still like to better understand doing things manually in case something goes wrong.
Any info you can provide would be greatly appreciated.
Click to expand...
Click to collapse
Do not use a toolkit. If there is one thing you take from this response, take that.
N7 2013 has two models, flo and deb. flo is the wifi version, deb is the LTE version.
Updating a Nexus device will not hinder your ability to root/unlock the bootloader. Other OEMs do this, and that's why I'm not using their devices anymore. Done with them.
Clear all recents button is removed on later Android versions. Custom ROMs or Xposed/GravityBox to get it back.
OTG/Stickmount issue: I believe that if you have a custom kernel that supports it, not an issue, don't need Stickmount. No experience in this area, however.
The stock look of a Google OS is standard AOSP. That's why the ROM you flashed on your Xoom looks very similar.
If you are new to Nexus devices, I would probably recommend using stock for a while. When you become tired of the absolute lack of customization, switch to SlimKat and use Banks' minimal gapps package. The gapps thread is in the N5 apps section, but works just the same on N7.
If you are going to unlock the bootloader anyhow, here is what you want to do to update to the newest version without the extra steps.
You need to install the drivers, get ADB+fastboot, and download the KTU84P factory image for your device. All links in signature. If you have the wifi model, razor, if you have the LTE model, razorg. razor=flo, razorg=deb.
You can find the fastboot tuts all over the internet, and it's too long to type. But basically, you want:
fastboot oem unlock (this will wipe your device, but only needs to be done one time)
fastboot reboot-bootloader
<you can run the flash-all.bat file that came with your fasctory image now>
after that's done, you'll want to go back into bootloader mode and flash TWRP (link in signature).
fastboot flash recovery twrp.img
That's a lot of information written with very poor coherence. If you need elaboration, just ask. But it has you pointed in the right direction.

Aerowinder said:
Do not use a toolkit. If there is one thing you take from this response, take that.
N7 2013 has two models, flo and deb. flo is the wifi version, deb is the LTE version.
Updating a Nexus device will not hinder your ability to root/unlock the bootloader. Other OEMs do this, and that's why I'm not using their devices anymore. Done with them.
Clear all recents button is removed on later Android versions. Custom ROMs or Xposed/GravityBox to get it back.
OTG/Stickmount issue: I believe that if you have a custom kernel that supports it, not an issue, don't need Stickmount. No experience in this area, however.
The stock look of a Google OS is standard AOSP. That's why the ROM you flashed on your Xoom looks very similar.
If you are new to Nexus devices, I would probably recommend using stock for a while. When you become tired of the absolute lack of customization, switch to SlimKat and use Banks' minimal gapps package. The gapps thread is in the N5 apps section, but works just the same on N7.
If you are going to unlock the bootloader anyhow, here is what you want to do to update to the newest version without the extra steps.
You need to install the drivers, get ADB+fastboot, and download the KTU84P factory image for your device. All links in signature. If you have the wifi model, razor, if you have the LTE model, razorg. razor=flo, razorg=deb.
You can find the fastboot tuts all over the internet, and it's too long to type. But basically, you want:
fastboot oem unlock (this will wipe your device, but only needs to be done one time)
fastboot reboot-bootloader
<you can run the flash-all.bat file that came with your fasctory image now>
after that's done, you'll want to go back into bootloader mode and flash TWRP (link in signature).
fastboot flash recovery twrp.img
That's a lot of information written with very poor coherence. If you need elaboration, just ask. But it has you pointed in the right direction.
Click to expand...
Click to collapse
Thanks for all the info. So I definitely have the FLO model.
I would like to use Titanium Backup for Root and a few other things that need root access so I definitely want to do this.
Also, being that this tablet has no micro SD, I definitely want to have read-write access with a USB drive. I've had this for almost a week already and I haven't loaded anything into it yet because I figured I'd be wiping it. I really don't want to mess with stock because of the lack of a few things. I really just can't stand having devices with restricted use. That's not what I paid for.
I never used Kit Kat before and not sure if I'll like it. Do you know if you can go back to 4.3? I know with some of the other devices (like my Galaxy S3 phone), once you update it OTA, they lock stuff up and you cannot roll back.

Also, does anyone have any idea on a completely new out of the box unit what is killing the battery so fast? On my galaxy 7 tab, it would last over a week in standby. This thing was dead in about a day and a half after I took it off the charger. and I charger it full a couple of times already. Or does battery life just suck on this tablet?
I did find a post somewhere that said to turn off google location and I just did that. We'll see if it does anything.

happy4ya said:
Also, does anyone have any idea on a completely new out of the box unit what is killing the battery so fast? On my galaxy 7 tab, it would last over a week in standby. This thing was dead in about a day and a half after I took it off the charger. and I charger it full a couple of times already. Or does battery life just suck on this tablet?
I did find a post somewhere that said to turn off google location and I just did that. We'll see if it does anything.
Click to expand...
Click to collapse
You can roll back to 4.3. Google hasn't gone full Apple yet. But I strongly advise against doing so, as it's a large step backwards.
Understood on stock OS, agree no options anywhere. Slimkat+franco.kernel+banks gapps. You won't look back. Also in developer options, switch to ART. Dalvik sucks. If you're using Banks' minimal gapps, the lack of some syncing libs (for the AOSP calendar nobody uses) will cause random FCs until you reboot a second time. Nothing to worry about. Just grab the Google Calendar, or whatever calendar you use, from the play store and freeze the AOSP one with TiBu. Another FC you might see is gms.location. It should only happen once. Something with play services.
Once you are rooted, you can grab BetterBatteryStats to see what's killing your battery. On stock installs, it's mostly going to be location-based stuff keeping it awake. You already turned off reporting, but you also need to switch location mode to Device only.