Related
Ok let me see if I can explain my problem right. I got an android locked to t-mobile USA I am planning to but an unlock code for this phone but the problem that I encountered before buying the code is this this phone come with an application that when it start up it asks you to to set up your gmail account but I am in mexico I am not interested in having a gmail account how can I delete this application or stop it or skip it otherwise I am not going to be able to use the phone what can I do I like this phone but it is useless in the state that it is help
Not having a gmail account means you wont be able to use the market, your contacts wont sync, the included calendar app wont work very well. There may be other issues as well.
Do you hate google or what? A gmail account is free.
no thats not the reason I dont hate google it is just that at the moment when my android turns on it start up with this message
Setting up your T-Mobile G1 I tried to register but it wont register and I can not even use the phone functions the android stays on trying to register this what I do
i try to register then a message comes up that says that it may take up to five minutes but after a while another message show up and it says
there is a problem comunicating with google servers
this could be a temporary problem or your sim card may not be provioned for data services. If it continues call customer service
well the bottom line I really want to use this phone but how can I get pass this registering bull
here in mexico we run into this problems all the time our cell carriers suck basically i just want to be able to use the phone functions only if anyone can help I will apreciate it.
http://forum.xda-developers.com/showthread.php?t=452316
You may need to downgrade to RC29 depending on what version your phone is currently running.
Also, I'm not sure if your carrier, or any at all, block by IMEI if a phone is reported stolen. I'm not accusing you of stealing, but, you know...
elvences said:
no thats not the reason I dont hate google it is just that at the moment when my android turns on it start up with this message
Setting up your T-Mobile G1 I tried to register but it wont register and I can not even use the phone functions the android stays on trying to register this what I do
i try to register then a message comes up that says that it may take up to five minutes but after a while another message show up and it says
there is a problem comunicating with google servers
this could be a temporary problem or your sim card may not be provioned for data services. If it continues call customer service
well the bottom line I really want to use this phone but how can I get pass this registering bull
here in mexico we run into this problems all the time our cell carriers suck basically i just want to be able to use the phone functions only if anyone can help I will apreciate it.
Click to expand...
Click to collapse
Ok... Long story short:
The G1 is a "google" phone and is dependant on data services and a google account to operate. That being said, the only way you can work around this without having a solid data connection (through your cell provider) is to go the process to root your phone and use one of the builds that allows you to skip google registration. I know TheDude's build lets you, I'm not sure which other builds do. By skipping the sign-in process you would still be able to use wireless internet to get your phone to sync with google once you turn on wifi.
Of course, your phone will have to be unlocked if it's not already.
I suggest you look at the development forum and start reading the links from the "round-up" sticky on the very top.
Thank you everybody for your quick responses but it seems that i am still stuck in the setting your account bull.- i try to root my android but i can even get to format my m sd card as a follow instruction in how to root phone it says to wait until mount show up on my screen how am i suppose to do that when my phone wont get past the setting up account screen can i format m sd card with adapter and then load the rc29 and put it back on my android and follow the rest of the intructions will that work i dont want to try it just like that has anyone else done like this is this going to brick my android.
elvences said:
Thank you everybody for your quick responses but it seems that i am still stuck in the setting your account bull.- i try to root my android but i can even get to format my m sd card as a follow instruction in how to root phone it says to wait until mount show up on my screen how am i suppose to do that when my phone wont get past the setting up account screen can i format m sd card with adapter and then load the rc29 and put it back on my android and follow the rest of the intructions will that work i dont want to try it just like that has anyone else done like this is this going to brick my android.
Click to expand...
Click to collapse
Yes, if you have a card reader you could put the dreaimg.nbh, update.zip and recovery on your sd card and never have to mount your phone to the pc.
Or just use another device with a memory card reader or writer. Or even better, install ADB, go into the recovery window by pressing home+power and on your computer enter the ADB interface and type in
adb mount /sdcard/
adb push (location of firmware).nbh /sdcard/
and voila.
Hey I downloaded android-sdk-windows-1.5_r2 isnt this file suppose to have everything I need to work in my android but it doesnt where is ADB at and I am suppose to have and update zip and restore it doesnt say anything about that in development. I am liking this but it seems difficult but thats why I like it just show me where this files are at and I promise that I will at least brick my android lol not really but I hope I get it working. Well this are the instructions in how to root.
Format your phone's SD card to FAT32 mode:
Hook your phone up to your computer using a USB cable and then wait for the notification to show up in your title bar of your phone.
Click the notification, and then click "Mount".
A new removable disk should show up on your computer. Right click it and select Format, and select FAT32 as the file system type.
Download and unzip the RC29 or RC7 image file. Copy the DREAMIMG.nbh file to the SD card. (RC29 for US, RC7 is for UK)
Turn the device power off.
Hold Camera button, and press Power button to entry bootloader mode. You should see a gray/white screen with instructions to flash your phone with the update on your SD card. If you don't see that, make sure you followed the instructions properly.
As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT DO ANYTHING TO INTERRUPT THIS PROCESS.
After it is finished, perform the restart your phone.
see it doesnt say that I need and update zip and a recovery. But I might be wrong so where are this files at
skri11a said:
I suggest you look at the development forum and start reading the links from the "round-up" sticky on the very top.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=442480
http://forum.xda-developers.com/showthread.php?t=455860
http://forum.xda-developers.com/showthread.php?t=502010
http://forum.xda-developers.com/showthread.php?t=517874
I have cut to the chase and given you the direct links in the stickies that you were supposed to have already read if you were following the very good advice from skri11a.
After reading this, you should have all of the knowledge you need to make your phone work... If not, come back here and we can clarify any further questions.
If you continue to refuse to help yourself, there is a good chance that this thread will be locked, closed, fired, deleted, or shot into space.
Well I am back after reading and trying all that I have to say and I am probably going to get this thread close is this. I can get adb to run I downloaded sdk copied to C installed drivers for my android and nothing happens. I also tried using a memory adapter and formated my sd to fat 32 and then copied DREAIMGRC29 and then tried to run it and nothing happen I am the dummest person in the world.
I don't think this is the phone for you. Just sayin.
elvences said:
Well I am back after reading and trying all that I have to say and I am probably going to get this thread close is this. I can get adb to run I downloaded sdk copied to C installed drivers for my android and nothing happens. I also tried using a memory adapter and formated my sd to fat 32 and then copied DREAIMGRC29 and then tried to run it and nothing happen I am the dummest person in the world.
Click to expand...
Click to collapse
Did you happen to rename/extract the DREAIMGRC29? It needs to be the DREAIMG.NBH. Also "Dumbest" not "Dummest".
elvences said:
Ok let me see if I can explain my problem right. I got an android locked to t-mobile USA I am planning to but an unlock code for this phone but the problem that I encountered before buying the code is this this phone come with an application that when it start up it asks you to to set up your gmail account but I am in mexico I am not interested in having a gmail account how can I delete this application or stop it or skip it otherwise I am not going to be able to use the phone what can I do I like this phone but it is useless in the state that it is help
Click to expand...
Click to collapse
to unlock your g1......... CALL T-MOBILE!
it will be free, so don't go buying into those sites on the net.
also, go HERE
most or all of you modding, hacking, and basic information will be answer by reading that guide.
mrcrs said:
to unlock your g1......... CALL T-MOBILE!
it will be free, so don't go buying into those sites on the net.
also, go HERE
most or all of you modding, hacking, and basic information will be answer by reading that guide.
Click to expand...
Click to collapse
He can't, he is in Mexico.
hamshu said:
He can't, he is in Mexico.
Click to expand...
Click to collapse
he still can call.
and i'll even list the number: 1-800-937-8997.
all they need is the IMEI number, then they give the correct unlock code contingent on that.
and it'll be obvious that he's in mexico and needs his g1 to be unlock, so i'm sure they'll supply that code for him.
granted he's been with tmo for 90 days or more.
nolageek said:
I don't think this is the phone for you. Just sayin.
Click to expand...
Click to collapse
This is a great phone and it is for me aned I going to get to the bottom of this even if I end up bricking my phone.(I can not use it so if I brick it will have the same use)
hamshu said:
Did you happen to rename/extract the DREAIMGRC29? It needs to be the DREAIMG.NBH. Also "Dumbest" not "Dummest".
Click to expand...
Click to collapse
My man well since english is not my first language I apologize for any mistakes in my writing but you still got my point. And yes I did extract the file and its name is DREAIMG.NBH BUT WHEN I TRY TO RUN IT WONT.
mrcrs said:
to unlock your g1......... CALL T-MOBILE!
it will be free, so don't go buying into those sites on the net.
also, go HERE
most or all of you modding, hacking, and basic information will be answer by reading that guide.
I can get the code. The problem is I can type in the code the phone wont let me pass the setting an account.
Click to expand...
Click to collapse
What do you mean? I have a quick question for you though, who is your carrier, and do you have the proper APN set up?
So, i'm sure there's many posts about this, but I thought I'd drop in my 2 cents. Basically, the purpose of this post is to try and help completely new users get acquainted with the world of Android "ROMing". I know there's beginners tutorials and wiki's and such, and I'm very grateful for all the time put into them by their writers, but the fact remains that they're written by experts, and as such, their expertise shines through and can sometimes confuse new users such as my self.
Up front: I'm an AT&T customer who's using a Rogers branded HTC Magic purchased from ImportGSM. I'm using Rogers cause Rogers has the same 3G bands as AT&T. I am coming from a Sony-Ericsson dumbphone. I use Gmail for my primary email and applied for a Google Voice account a while ago (got the account before getting the phone). I'm a practicing computer engineer so if I lapse into jargon, I apologize.
READ THE ENTIRE POST BEFORE PERFORMING THESE ACTIONS
OK, so you got an android phone (if you're on this forum, its most likely an HTC Magic/Dream/Hero) and you want to install new ROMs onto it (for whatever reason, just to do it, to get more functionality, to remove the carrier 'branding', whatever). You've done your research. You've read through the wikis (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking) and you're still a little confused as to where to start, or you're worried you're gonna brick your phone.
First, relax, as long as you follow the instructions, there's little chance of bricking your phone.
Second, some vocab:
SPL: Secondary Program Loader. don't worry too much about this, you shouldn't have to mess with it. I like to think of it as your phones BIOS. There's an off chance that you'll have a "perfected" SPL (.0006 or .0010), which basically means that you have a phone that is hardened against hackers, but as long as you use the one touch root method described below, you won't even notice it. You won't be able to use the Adb/Fastboot/Android SDK method mentioned below, you'll just get a "no access" error when you try to terminal into your phone.
ROM: Catch all term for software to be loaded onto your android. Generally comes in two flavors, a Recovery ROM, and what I call an Operating System ROM. A Recovery ROM is what gives you root access. An Operating System ROM is the user experience (where Amon_Ra or Cyanogen or others mix and match features to make a better user experience). I know that Operating System ROM might be misleading, but its the closest computer analogy I could come up with.
Now, this process will completely refresh your phone, removing all of your contacts, apps, etc. So before you start, if you have stuff on your phone you want to save, best copy them somewhere off your phone now. There's free apps out there to do all of this.
Lets get started.
Now, the first thing you're gonna wanna do is get something called "root" access to your phone. This allows you to install those fancy homebrewed ROMs that people are talking about. To get root, you have to install a recovery ROM. Installing a recovery ROM is is roughly similar to flashing a new BIOS on your computer. Except in this case, its on your phone and it gives you unrestricted access to the phone (like the Root user in Linux). There's two ways of getting Root. The first way is to install the Android SDK onto your computer and image your android with one of the recovery ROMs via your computers command line. I won't get into details on this one because its not the method I chose, and instructions are all over the web on this one. NOTE that this method doesn't work with updated Rogers phones. They installed the 'Perfected' .0010 SPL effectively removing remote command line access thus making this method a non-starter. The other way is to use the "one click root" program, which is a program you install on your Android phone. To do this, go to the one click root website (http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/). Download the .apk file and drop it onto the SD card in the Android phone (you'll have to connect the phone to your computer via USB, and select "Mount SD card". then simply drag and drop the .apk onto the SD card in your computer's file browser). Then, on the android phone, open up your file browser (I suggest Astro or Linda, both free downloads from the market) and open the .apk using the default Android application launcher. It should be a dark screen with a text box and a few buttons. The textbox should have a URL in it pointing to a .img recovery image (This is the cyanogen one). You'll first want to make a backup of your current (factory) ROM by pressing the (i believe) botton button. It'll work for a few seconds. Then you're ready to flash the recovery ROM. You can either accept the default (the cyanogen, which works fine) or specify a different ROM (such as Amon_Ra's which has slightly more capabilities) by entering in a different path (URL or path to SD card if you have a recovery image stored on the SD card). Then hit the first button to begin the flash. Wait for it to finish. DO NOT DISTURB THE PHONE WHILE FLASHING.
Once its finished flashing, congrats, you've rooted your phone. Now power off the phone, and power it back on while while holding power and Home. Hold Power and Home the entire time till you see an 'old computer' style menu come up. Should have some options such as reboot, install update.zip, install other .zip, wipe data/factory reset, etc. you should be able to use the trackball to cycle through the selections. The botton should have something like <cyanogen/Amon_Ra> recovery vX.X.X. If you see this screen, then you've successfully rooted your phone. Congrats.
Now, before you do anything else, IMMEDIATELY perform a nandroid backup. This should be on of the options in the recovery ROM. What this is doing is creating a backup of your current phone configuration so if anything goes wrong with installing the hacked ROM, you can revert to the state the phone is in now.
Next, perform a data wipe. There should be a selection for "wipe data/factory reset" or something similar. Select that. Wait for it to finish wiping your data from the SD card.
Now to install other hacked ROMs, just download whatever ROM you want to install from the xda site. Check the bottom of this page for a listing of the main ones (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking). It should download as a .zip. Copy the .zip file (DON'T UNZIP IT) onto the root of the SD Card (you can do this while in recovery mode by mounting the SD card or by physically removing the SD card from the phone and putting it into a card reader on your computer and copying the files). Once you have the ROM .zip on the SD card, with the SD card in the phone, select "install other .zip" or something similar and select the .zip file of the ROM you want to run. Should be some combination of the creators name (Amon_Ra or CM (for CyanogenMod)), what board the .zip is for (32A, 32B), what version the ROM is (4.1.1 or something). Then select "home" to confirm that you want to do this and wait for the periods to stop appearing. Once it stops, you should be able to select "reboot".
After it reboots (you should see different splash screens than when it was factory configured, except for the very first screen which on mine is "Rogers". Mine goes from Rogers to "Android" spelled out in blue text) you should have a fully functioning phone running a hacked ROM.
If it doesn't boot fully (which mine did a few times), try a different ROM or try wiping your data again. If all else fails, go into your recovery ROM (power and Home) and restore the Nandroid recovery image you made earlier.
Once it boots, it should have a tutorial on how to use Android.
When you get to the google login, I would suggest setting up your APN settings prior to doing that. At the google login screen, hit the menu button and select "APN Settings". Select add new APN (either an on screen choice or brought up by the menu button) and add in the APN details for your provider. You can find these easily by googling "<your provider> APN settings". Log into Google and you should up and running.
I just kinda threw this semi-tutorail together, so it may be a little confusing, but I tried to explain everything as best as I could. I know that i found all of the different ways to get root and the different ROMs and such to be very confusing. Just throwing out how I went about doing it.
Disclaimer: one click root works by exploiting a vulnerability in Android, which was closed by Google on Aug 11 or so. Therefore, if you have a factory Android build from that was released after Aug 11, one click root may not work for you, and you'll have to go the SDK route. I updated my Rogers phone in mid oct 2009, and my build was still prior to Aug 11, so don't just assume cause its after Aug 11 that it won't work on your phone.
thanks alot for the tutorial! you're a saint, i've been looking all over for something exactly like this!
i will test this out and let you know!
Edit:
I was successful! Huzzah! Thanks for the guide again!
What rom did you load onto your phone?
Also,
Could you give a brief tutorial on what exactly changing the radio and spl are?
Yay, I've finally found a reliable way to do this. After completing these steps, you'll be able to install any GSM Hero ROM. Still, neither I, nor anyone else, can be blamed if something goes wrong and you end up with a shiny paperweight.
-2. Changelog
16/11/09
Updated to Amon_RA's latest recovery image
15/11/09
First release of the guide!
-1. Thanks!
This guide would not have been possible without:
TheUnlockr (great guides)
Amon_RA (recovery image)
xda-developers (need I say more?)
MoDaCo (Excellent ROM)
QMAT (GoldCard)
craig0r (first to root the Telus Hero)
pi3ch (copy from cmd)
And everyone involved in rooting the Dream, the Sapphire, the Hero, and Android in general. Many thanks to everyone involved!
0. Before we start!
If you haven't installed all the drivers for your phone already, follow the instructions on this page to do so. It also shows you the basics of ADB.
Also, a forewarning: there are reports that not all microSD cards work. If yours doesn't work, try another one. Hopefully you'll still have some dough in your wallet by the time you find one that works. Just kidding.
Also, not all microSD readers work either. I have one that just refused to write the GoldCard image to the card, but thankfully, my laptop's SD slot worked.
And, these steps have only been tested on Windows XP 32bit. If you use anything newer, it may or may not work, but most importantly, if you want any chance of it working, you'll want to run most of these apps and commands in Administrator mode.
Finally, make sure you have a Wi-Fi connection, as your data connection will be lost at some point while you need to download something from the Market.
1. Downloads!
You'll want to get all your downloads before starting this.
HxD
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
flashrec
Amon_RA's recovery image
Updated radio
2. Prepare your phone!
On your phone, go to:
Settings > Applications > Development
There, check USB debugging.
3. Backup your APN settings!
Go to the Market and install APN Backup and Restore. Run it, and backup your APN settings with it. This is necessary to restore data access after rooting.
4. Get your GoldCard image!
The GoldCard bypasses some weird check on the phone and allows you to flash ROMs that are otherwise rejected, due to them being older versions, or some other reason that HTC decided it'd be so.
With the USB cable plugged in, open the notifications shade and tap HTC Sync. It doesn't matter if it can't sync, but what matters is you can enter the adb shell. If you don't know how, you haven't done step 0.
Now, go in adb shell and run this command:
Code:
cat /sys/class/mmc_host/mmc1/mmc1:*/cid
The output is your microSD card's serial number. Right click anywhere in the command prompt, and click on Mark. Then, select the serial number, and right click. The serial is now copied into the clipboard, so open up Notepad and paste it there.
Now, with that serial number written down, paste it into my lame GoldCard hex reverse. Please credit me if you use that page in your guide!
Next, do as my page says, grab the reversed serial number and get your GoldCard image with it.
5. Create your GoldCard!
So now you have your GoldCard image. Remember, this GoldCard image is valid only for the card from which you got the serial number. If you use another card, get another image.
Turn off your phone, take the microSD out and plug it into the your preferred reader. Again, not all readers work. Not all microSDs work.
Now, unplug from your computer any removable storage except for the microSD. This is to avoid confusion in the next step.
Before making the GoldCard, backup anything you need from the microSD, as it may get erased in the process. Most importantly, backup the APN settings that we got earlier, from APN Backup and Restore.
Now open up HxD. From here, you'll open two things. Your microSD in the raw, and the GoldCard image in the raw.
To open your microSD go to:
Extras > Open disk
In the pop up, under Physical disks, select the (supposedly only) Removable Storage. If there are two, I don't know which one is the right one, so unplug more stuff from your computer.
Before you click OK, be sure to uncheck Open as Readonly. We can't make a GoldCard if we can't write on it, right?
To open your GoldCard image, go to:
Extras > Open disk image
There, select your downloaded goldcard.img file, and click Open, and then OK.
Now you should have two tabs open in HxD, one being the microSD, and the other, active one being the GoldCard image.
Press Ctrl+A on your keyboard to select all, then Ctrl+C on your keyboard to copy. Switch to the microSD's tab, make sure the cursor is at the complete top-left corner, and then press Ctrl+B to paste, and then Ctrl+S to save. Accept the risk and your GoldCard should be made.
To verify, close the microSD's tab, eject it, unplug and replug it, and reopen it in HxD like we did earlier. It should still have the GoldCard image written at the beginning of it. If not, either the microSD or the reader or both don't like making GoldCards, so you'll want to try a different combination of card and reader.
6. Downgrade!
Let's flash the downgraded ROM now. Plug your microSD, now a GoldCard, into the phone and turn it on. After it finishes booting, turn on HTC Sync. Again, it doesn't need to actually synchronize.
Now, run the RUU you downloaded earlier and follow the steps. If the GoldCard works, it should flash and you'll end up with a downgraded phone. If not, then you either didn't write down the microSD's serial number correctly, or the microSD doesn't like to do its job.
Set up the downgraded phone with the default settings, and turn on Wi-Fi. Get on your Wi-Fi network and install Linda File Manager.
Now, on the phone, check:
Settings > Applications > Unknown sources
Now turn on USB Storage, and copy flashrec and Amon_RA's recovery image to the microSD. Rename the recovery image to recovery.img to save a headache later. You may as well put the backed up APN files back on the microSD too, if they got erased.
Disconnect USB storage, load up Linda, go in the SD card, and install flashrec using Package Installer. Now, load up Recovery Flasher, press on backup, then type in:
Code:
/sdcard/recovery.img
Now press Flash recovery.
7. Update the radio
The radio that came with the downgrade is quirky in North American networks. We'll update to the latest IU radio, which works with our networks here.
First, reboot into the new patched recovery. Turn off the phone, and then turn it back on while holding the Home button. Keep holding it until you see the recovery menu.
Once you're there, scroll down using the trackball to turn on USB Mass storage. Plug the phone in the computer if it wasn't plugged already. The microSD will show up on the computer. Copy the updated radio zip to the root of the microSD wait a few seconds, then turn off USB Mass storage on the phone.
Now, select Flash update image, and then Apply sdcard:choose zip. There, the radio zip should show up. Select it and flash it.
8. You're pretty much done at this point.
Follow any guide to install a Hero ROM, to partition your microSD, etc. After you install a custom ROM, be sure to reinstall APN Backup and Restore from the market, and restore your APN settings. This will restore data.
well the "asroot" method of rooting from the guide in the CDMA forum may be worth trying...perhaps they haven't fixed the vulenrability?
http://forum.xda-developers.com/showthread.php?t=581577 (all the way up to before the recovery image)
Ya tried that method don't work
yeah I would love to root this thing.
To be honest this is my first smartphone and I'm new at this rooting thing. I did manage to throw on a hack for my ipod nano (colored version)
I'm loving this phone so far - got it first day they announced their new network. I'm so impressed
Did either of you buy another SD card? Where did you grab yours if you did?
My Telus Hero has been rooted since Friday.
Check it:
http://forum.xda-developers.com/showpost.php?p=4909063&postcount=16
Yeah I just saw. I'll get familiar with the process then update the first post.
Thanks a bunch!
I posted in the other thread (so... sorry for the double post), but I think that this thread is more relevant to the question/issue of rooting.
Could someone who still has the stock Telus ROM post the Baseband version? (Home -> Settings -> About phone -> Baseband version)
I'm just curious as to whether we Telus users should upgrade or downgrade the radio version after rooting the phone, as I seem to be having dialing issues (long distance numbers require a "+" in front of the "1" or it won't connect.)
I dunno if this issue would be related to the radio, or to the fact that there are no North American locales selectable within the custom ROM.
Stock Baseband
63.18.55.06DAU_6.35.08.20
Still wating to see how others are successful with rooting their Telus Hero.
sjeffrey said:
63.18.55.06DAU_6.35.08.20
Still wating to see how others are successful with rooting their Telus Hero.
Click to expand...
Click to collapse
Same here. My stock Telus Hero reports the same version as above (just to add to the data pool). I'll be watching this thread for more details on rooting.
I rooted using the goldcard>2.73.405>recovery>modaco2.9>IU baseband and it works no problem. I can dial 611, long distance numbers dont need a + or a 1 for that matter, and market enabler lets me buy paid apps. Device seems quicker. I had to try 3 different sd cards though. I know I was doing the first one wrong, but one of them definately did not work.
I mentioned in the other Telus Hero thread that I updated my radio to the IU version, and my dialing issues have gone away. Thought I should mention it here as well.
I'm still waiting for a method that doesn't require calling Telus to fix settings though.
Say, is your Hero the black or white one? And, is it a HERO130 or a HERO100?
I keep getting an invalid model ID error when I try flashing the downgrade. Is that what you had the times it didn't work for you?
Soaa- said:
I'm still waiting for a method that doesn't require calling Telus to fix settings though.
Say, is your Hero the black or white one? And, is it a HERO130 or a HERO100?
I keep getting an invalid model ID error when I try flashing the downgrade. Is that what you had the times it didn't work for you?
Click to expand...
Click to collapse
Yeah, I'm pretty sure that's the error I got when I didn't have a proper Gold Card. If you've tried the same SD card a number of times and it's still not working, maybe grab a cheap Sandisk 1GB card. That's what I used.
And you shouldn't have to call Telus, because I've already gone through the pain of figuring all this stuff out. Just make sure you grab the APN settings from the other thread, and update to the latest radio (IU) and you're good. A call to Telus was required because I couldn't receive MMS messages, but that had nothing to do with rooting the phone, I would've had to call them anyway.
When I look up "Model Number" in my phone's settings, it just says HTC Hero. So I dunno. The custom ROM probably did that. I guess.
the model name might be written in the battery compartment area. i know on my htc tytn the name is there as "HERM200"
pretty sure it was mentioned that the telus hero is HERO130
As profets said, the model ID is under the battery. Mine says HERO130, and in bootloader mode, it says HERO13000. Since the downgrade ROM is for HERO10000, it threw an invalid model ID error.
Soaa- said:
As profets said, the model ID is under the battery. Mine says HERO130, and in bootloader mode, it says HERO13000. Since the downgrade ROM is for HERO10000, it threw an invalid model ID error.
Click to expand...
Click to collapse
Ah cool. I just checked under the battery, it's a 130. So you should still be able to downgrade.
Really strange. I tried a Kingston 2GB like they said on the guide and verified that the GoldCard image was well written on the card. Yet it still throws error 130.
Soaa- said:
Really strange. I tried a Kingston 2GB like they said on the guide and verified that the GoldCard image was well written on the card. Yet it still throws error 130.
Click to expand...
Click to collapse
I used the 2GB sd card comes with the phone to create goldcard. Rooted.
No problem at all, I don't know why you guys wanna use other SD cards.
I'm pretty sure I've tried all my cards... I'll try again tonight.
Hah! Got it to work. Guide is done.
I also quickly put together a webpage to reverse the CID of the microSD. That way, people won't need to download QMAT anymore. The page can be found here: http://hexrev.soaa.me
Enjoy!
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
First go here and download the RUU:
http://www.pcdphones.com/downloads/Eris%20MR1.zip
Next you need to go to verizon's website and login to your account. Click "Suspend/Resume Service" and suspend your phone. You can resume service on the phone after you are done here with no penalties or charges.
Please follow these directions, taken from the first root thread
bftb0 said:
Steps:
[Binny knows this, but if anyone else is reading, it is the same as a factory reset - you will lose all your settings and apps (but not the contents of the SD card)]
1) Unpack the 1.16.605 RUU - by running it as if you were going to actually do the RUU using the USB cable and your host PC, but stop right before you would apply the update to the phone. Pull the "rom.zip" file out of the temporary area that the RUU installer unpacks.
(Poke around under C:\Documents and Settings\<Username>\??? (I can't remember - you'll see folders with names that look like registry entries). You have to do this while the RUU installer is sitting there waiting for you - if you cancel the install, it will nuke everything it unpacked. I just made copies of the entire subtrees.
2) Cancel the RUU install.
3) Move the ROM.ZIP file to the root folder of your SD card, and rename it PB00IMG.ZIP
4) You can cancel the RUU install session on the PC, and unplug the USB cable if you want (so long as you have a well-charged battery!)
3) Power down the phone, and boot it back up holding the Call and End buttons simultaneously
4) Scroll down (or whatever it asks) to go from Fastboot mode to HBOOT mode
5) The phone will automatically discover the PB00IMG.ZIP file, and unpack it and verify it.
6) It will ask you if you want to install; when you (select and) enter Yes, the phone will reboot, and come up again - appearing as if it is repeating the same thing. This time, however, it won't stop and ask you - it will just begin the install.
7) Wait... Wait... Wait... Wait... and then wait some more. If I recall correctly, it seems to hang a little bit at the HTC splash screen after the reboot. That is normal - just WAIT and let the phone do it's thing.
That's it, except for:
8) You probably will want to dial *228 and choose option 1 to complete the programming of your phone - it will reboot after it completes.
Click to expand...
Click to collapse
After you are done, DO NOT start the OTA update that it prompts you to do.
Now we are going to install wireshark and setup the capture environment:
Download wireshark from http://www.wireshark.org/download.html for your versions of windows
Install it - make sure you also install WinPcap
At this point you should turn off any wireless encryption on your router. I know it's not necessary but it makes it easier to go through the captures.
Setup the wireless on your phone to connect to your wireless router and turn off your mobile data connection.
After you have turned off the wireless security on your router, we are going to start the wireshark capture.
Run wireshark - if you are on vista or windows 7 make sure to run it as an administrator
Click "Capture" then "Interfaces"
Click "options" next to the interface that your computer has an IP for
Make sure to check "Capture packets in promiscuous mode"
In the Capture Filter box, type "host <ip_address>" where <ip_address> is the ip address your router gave your phone
Make sure that "Automatic scrolling in live capture" is checked so you can ensure the capture is working
Click "Start"
At this point, you should browse the web with your phone. You should see lots of stuff scrolling by in the wireshark window.
If there isn't, you messed up something above and should try again.
If there is a lot of stuff scrolling by, continue:
Close the browser
In wireshark, click "Capture" then "Restart"
Reboot your phone
On your phone, go to "Settings" -> "About Phone" -> "Check for Updates" and go through with the OTA update
After the update is done and your phone is rebooted, go to wireshark and click "Capture" -> "Stop"
Then click "File" -> "Save As" and give it a name.
Upload that file to Megaupload, or Mediafire, or some other file sharing site, or any private server that I can get access to.
After you have uploaded the file please message me through the forums with a link to the file.
Thanks a ton.
e-mail me at [email protected] i got my wifes phones todo this to shes still on 1.5
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
FireSokar said:
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Click to expand...
Click to collapse
You CANNOT downgrade from 2.1 to 1.5.
Videofolife13 said:
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
Click to expand...
Click to collapse
We don't need the location of the update file, we need all the extra network traffic that surrounds the OTA process.
Ah. My bad.
We need to know, exactly, how the update process works.
I'm currently working on downgrading 2.1. Will post back a tut if i get it working
Can't we create an AVD to run with a custom rom and use the Eris MR1 ROM to do it?
Scratch that. I don't think AVDs will get OTAs.
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Sadly I tried this a while ago when messing around with AVD Skins but wasn't able to figure it out. If anyone can figure it out please let me know how you do it! -_-"
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Wait can't you set it to wireless only mode and get the OTA through wireless? (Simulated by your network connection)
nindoja said:
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
...
Thanks a ton.
Click to expand...
Click to collapse
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
FYI,
When you roll back to MR1, the phone seems to have already grabbed and downloaded the OTA update... in less time than it takes to hand-configure the phone. If you want to observe the OTA process via wireless, you need to prevent the phone from having Mobile network access, since that comes up by default after a FR or MRx rom burn.
Here's a long shot. Perform the MR1 rollback inside a cell dead zone, and conduct a MIM attack by setting up a server on the wireless net so the phone downloads a different OTA zip. You control DHCP for WiFi, so you also in principle control the DNS and routing the phone sees via WiFi. In principle, it's not possible because https should prevent Man-In-the-Middle... but if that (Google) server isn't correctly configured, maybe the phone is not really being too careful about certificate problems. (Either that or the Google server is tuning its' responses based on UA strings).
bftb0
bftb0 said:
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Click to expand...
Click to collapse
bftb06: could you please PM me? I am going to trade my phone this week if you understand what I am getting at.
nindoja said:
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
Click to expand...
Click to collapse
Sorry, my bad. I didn't read carefully enough.
I could probably attempt what you are asking for - I am quite familiar with wireshark (and even hardware sniffing of WiFi, so long as you have the right nic), but the fact that the phone seems to go and look for updates immediately after a FR or MRx update means that the "check for updates" thing may not do anything useful for you if there is already an update on the phone waiting to be installed by the time you start pressing menu buttons. (Thus the idea about "do MR1 in a cell dead zone")
Beyond that, there is a possibility that the update app does not do a wildcard host bind() when it sets up the socket when it inquires about updates with the Verizon servers - for instance, MMS service works exactly that way (it will only use the mobile network interface), and precisely so because of security considerations. Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
bftb0 said:
Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
Click to expand...
Click to collapse
You can force updates to occur over WiFi if the mobile network is turned off. Do you think this would work:
1. on 1.17 do a factory reset but do not activate the phone.
2. Initiate the downgrade process
2a. while downgrading, turn on packet capture
3. When the phone boots back up and wants you to call a number to activate, hang up
I think if you can skip the activation the phone will not have a mobile data connection, which would allow you to turn on wifi and initiate the update process.
Im still on 1.5 PM me and ill help if needed
Do you guys still need this?
Hello, ladies and lads!
Here's a short version of where I'm at: after installing Wondershare' s dr.phone Recovery on my mom's PC and using it on her phone:
its screen won't respond to touch (can't enter SIM card's PIN nor open screen lock)
the On/Off button won't turn off the phone on long press (maybe due to screen lock)
on restart there's a yellow text that reads "Set Warranty Bit : kernel"
the physical buttons still work
I can see the phone's files and folders only through PC's command prompt, using ADB ('This PC\Galaxy Grand Prime' folder in Win Explorer says it's empty).
Ideally I want to keep her data (FB Messenger, Skype, Chrome, WiFi passwords, etc), and her phone to function again. What do you think I should do?
I think I need an advice and suggestions from someone more experienced than me - I don't even know trusted sites where to download the firmware roms from.
The phone's details are (I'm afraid you'll have to walk me through to get more details to this list, as I'm new to the forum):
Phone: Samsung Grand Prime
Model name: SM-G530FZ
Firmware version: G530FZXXS1BQC2 (Android 5.0.2 with Baltic bloatware, I guess)
Now in detail:
My knowledge and experience regarding the smartphone software & restoration is very basic (I've only restored the firmware to a LG-L70 once some years ago, and that's it).
Before the problem I lost some over 600 media files from that phone by Cutting and Pasting a folder from phone's internal SD to PC's disc. Now I learned never to Cut-Paste important or irreplaceable files. The files ended up on the phone, because a folder with over 800 files couldn't be uploaded to the Google Drive (the camera's folder had over 1k files in it, so I moved some of them to another folder, which the phone created on the internal partition rather than the SD Card, where the original folder was from).
Instead of using a trusted software, I foolishly Googled a photo recovery program for phones, using my mom's PC. A list of bogus recovery program sites appeared (had to look them up on her PC, as I found only legit, widely trusted programs now, using my laptop. Those darn Google's personalized search result algorithms!).
Before using the dr.fone Recovery software I synced most of the data to her account.
Used the "free" dr.fone Recovery software as per its site's instructions, the phone did a restart and the touchscreen went unresponsive to touch. Later the software showed the lost files it found, and offered to restore them for a sum. Naturally I declined.
The software said that to return the phone to normal I need to disconnect the USB cable. I did so, but the phone's screen remained unresponsive to touch, even after restart (long-press [Pow] + [Vol-]).
I tried connecting an USB mouse via the dongle, but the mouse cursor didn't appear (maybe this phone doesn't have this functionality).
Now, after using that FAIL-covery program, I was overly cautious not to make things even worse.
I wanted to make a copy of the phone's internal SD state (or is it called a phone's hard drive?), to get the media files from the clone and to have a backup of mom's files.
But I failed: I downloaded APK, ncat, KingoRoot and BusyBox. Tried to follow the steps in this video: youtu[dot]be/KKkvkCgMeMA. Got stuck at "busybox not found" at about 10:27 mark in that video ("dd if=/dev/block/mmcblk0" "busybox nc -l -p 8888"). Turns out you need to run some of the apps from that phone prior to that step, and I don't know any workarounds.
Then I remembered that the files were on the external SD in the first place. Well duh! I then connected the Micro SD card to PC's reader via a Micro SD adapter. To make a copy of the SD card's 1s & 0s, and to restore the media files from said copy I used ZAR (Zero Assumption Recovery) z-a-recovery[dot]com/. The backup creation (an .ISO file or some such) and media recovery are free of charge.
Now I only need to remove duplicates and blurry pics (I think I had a Moleskinsoft's Clone Remover from an old PC magazine's CD lying around somewhere for the latter). Oh, and I better not forget to run a malware scanner on her PC and remove the mr.fone installed services and folders from it. Went a bit off-topic here, sorry!
Last I pulled a wifi passwords file with "adb pull /data/misc/wifi/wpa_supplicant.conf" command as per instructions on this page: mashtips[dot]com/see-wifi-password-android/. I don't know whether putting the file back on that phone will do the trick or not.
That's pretty much all.
I hope the situation can be resolved and I appreciate your input! :fingers-crossed: Maybe someone has come across a similar post, has constructive commentary or knows something obvious that I haven't come up with? Thank you in advance!
Edit 30 Jan '19: Got the phone working. Accessed the phone with a Chrome browser extension (name here). All accounts except some mail account were gone. WiFi didn't work.
Found a stock ROM here: (address here).
Found the Odin3 tool here: (address here). It came with a different locale ROM.
Flashed the 1st ROM with Odin. The screen started to work.
Flashed the 1st ROM with Odin again. The WiFi started working.
I'll update this with links soon.
I've got the exact same problem after using Dr Fone app!
Hi there.
I've got the same problem with my Samsung Galaxy Grand Prime after using Dr Fone, like you. I contacted Wondershare website from which I downloaded the app but they haven't bothered replying. Not happy at all!!
I contacted Samsung's support team and after trying different things (the usual stuff: reboot; remove the battery and SIM card; restart in Safe Mode; etc) which didn't solve the problem, they ended up telling me to reset the phone to the factory settings but that didn't work either.
Now my phone is stuck on the Samsung Galaxy Welcome screen which asks me to choose the language I want on my phone. The touchscreen is still unresponsive.
How did you manage to fix the problem if the touchscreen was unresponsive?
Thanks in advance for your help!
Your-Mum said:
Hello, ladies and lads!
Here's a short version of where I'm at: after installing Wondershare' s dr.phone Recovery on my mom's PC and using it on her phone:
its screen won't respond to touch (can't enter SIM card's PIN nor open screen lock)
the On/Off button won't turn off the phone on long press (maybe due to screen lock)
on restart there's a yellow text that reads "Set Warranty Bit : kernel"
the physical buttons still work
I can see the phone's files and folders only through PC's command prompt, using ADB ('This PC\Galaxy Grand Prime' folder in Win Explorer says it's empty).
Ideally I want to keep her data (FB Messenger, Skype, Chrome, WiFi passwords, etc), and her phone to function again. What do you think I should do?
I think I need an advice and suggestions from someone more experienced than me - I don't even know trusted sites where to download the firmware roms from.
The phone's details are (I'm afraid you'll have to walk me through to get more details to this list, as I'm new to the forum):
Phone: Samsung Grand Prime
Model name: SM-G530FZ
Firmware version: G530FZXXS1BQC2 (Android 5.0.2 with Baltic bloatware, I guess)
Now in detail:
My knowledge and experience regarding the smartphone software & restoration is very basic (I've only restored the firmware to a LG-L70 once some years ago, and that's it).
Before the problem I lost some over 600 media files from that phone by Cutting and Pasting a folder from phone's internal SD to PC's disc. Now I learned never to Cut-Paste important or irreplaceable files. The files ended up on the phone, because a folder with over 800 files couldn't be uploaded to the Google Drive (the camera's folder had over 1k files in it, so I moved some of them to another folder, which the phone created on the internal partition rather than the SD Card, where the original folder was from).
Instead of using a trusted software, I foolishly Googled a photo recovery program for phones, using my mom's PC. A list of bogus recovery program sites appeared (had to look them up on her PC, as I found only legit, widely trusted programs now, using my laptop. Those darn Google's personalized search result algorithms!).
Before using the dr.fone Recovery software I synced most of the data to her account.
Used the "free" dr.fone Recovery software as per its site's instructions, the phone did a restart and the touchscreen went unresponsive to touch. Later the software showed the lost files it found, and offered to restore them for a sum. Naturally I declined.
The software said that to return the phone to normal I need to disconnect the USB cable. I did so, but the phone's screen remained unresponsive to touch, even after restart (long-press [Pow] + [Vol-]).
I tried connecting an USB mouse via the dongle, but the mouse cursor didn't appear (maybe this phone doesn't have this functionality).
Now, after using that FAIL-covery program, I was overly cautious not to make things even worse.
I wanted to make a copy of the phone's internal SD state (or is it called a phone's hard drive?), to get the media files from the clone and to have a backup of mom's files.
But I failed: I downloaded APK, ncat, KingoRoot and BusyBox. Tried to follow the steps in this video: youtu[dot]be/KKkvkCgMeMA. Got stuck at "busybox not found" at about 10:27 mark in that video ("dd if=/dev/block/mmcblk0" "busybox nc -l -p 8888"). Turns out you need to run some of the apps from that phone prior to that step, and I don't know any workarounds.
Then I remembered that the files were on the external SD in the first place. Well duh! I then connected the Micro SD card to PC's reader via a Micro SD adapter. To make a copy of the SD card's 1s & 0s, and to restore the media files from said copy I used ZAR (Zero Assumption Recovery) z-a-recovery[dot]com/. The backup creation (an .ISO file or some such) and media recovery are free of charge.
Now I only need to remove duplicates and blurry pics (I think I had a Moleskinsoft's Clone Remover from an old PC magazine's CD lying around somewhere for the latter). Oh, and I better not forget to run a malware scanner on her PC and remove the mr.fone installed services and folders from it. Went a bit off-topic here, sorry!
Last I pulled a wifi passwords file with "adb pull /data/misc/wifi/wpa_supplicant.conf" command as per instructions on this page: mashtips[dot]com/see-wifi-password-android/. I don't know whether putting the file back on that phone will do the trick or not.
That's pretty much all.
I hope the situation can be resolved and I appreciate your input! :fingers-crossed: Maybe someone has come across a similar post, has constructive commentary or knows something obvious that I haven't come up with? Thank you in advance!
Edit 30 Jan '19: Got the phone working. Accessed the phone with a Chrome browser extension (name here). All accounts except some mail account were gone. WiFi didn't work.
Found a stock ROM here: (address here).
Found the Odin3 tool here: (address here). It came with a different locale ROM.
Flashed the 1st ROM with Odin. The screen started to work.
Flashed the 1st ROM with Odin again. The WiFi started working.
I'll update this with links soon.
Click to expand...
Click to collapse