1. Are you ready for the Galaxy S20? Here is everything we know so far!

Got Phone Back Up, But No Auto Setup

Discussion in 'Android Devices' started by Kamau, Dec 30, 2012.

  1. Kamau

    Kamau Android Expert
    Thread Starter

    After thinking about it most of the night, I finall got my phone back up. It took a lot of going back & forth, but it's working....somewhat.
    Once it got going again, it did not auto set up like it did the last few times. I"ve got internet going, and it is connected to my wireless router, but I do not have the play store, google search, maps or any of the Google apps. The wifi & 3g icons are also a different color than before. They use to be light blue, but now they are grey. These are the particulars of what I am runnin:

    mazada's AKOP rom version 4.1.2
    Hboot 1.04.200
    0.97.10.0530 radio
    Kernel 3.0.51-ck1DIRT-MOD-Kernel SHOOTER

    Could this again be a radio issue? How can this be resolved?
    Again, in advance, Thanks.
     



    1. Download the Forums for Android™ app!


      Download

       
  2. ramjet73

    ramjet73 Android Expert

    For most AOSP based ROM's you need to install the google apps (gapps) unless the developer has already done that which you can tell by reading the OP thoroughly. For mazda's AOKP, the gapps are linked right below the ROM and you want to use the 20121011 version for the current 3.5.2 build since it's based on Android 4.1.

    ramjet73
     
    scotty85 and Kamau like this.
  3. Kamau

    Kamau Android Expert
    Thread Starter

    Please tell me you're joking?
    I thought gapps was a specific program like bloatware, where if you wanted it back, you could download it.
    Color me............:thinking:
     
  4. zaius42

    zaius42 Member

    Newp, google apps are google apps. And a gapp is a google app, and google is google, etc etc etc.
     
  5. Kamau

    Kamau Android Expert
    Thread Starter

    Google Apps = Gapps...................:banghead:

    ^me
     
    scotty85 likes this.
  6. Kamau

    Kamau Android Expert
    Thread Starter

    Just in case it helps anyone, here is how I solved my problem.
    First off, the problem was that I had no internet connectivity. I also could not access my sd card either through recovery or the computer because of a PG86IMG .zip file that was on the sd card. This file kept the bootloader from doing anything but wanting to update the file. Choosing yes only updated the file and then went back to reboot. Choosing no only took the bootloader back to reboot as well. In either case, I was stuck with no way of deleting the file because, even through the computer you need to open the usb connect in the phone, and I could not gain access to the phone because I had a blank screen after the bootanimation logo. I did not have a card reader to put the card in, nor does my home pc have a slot for a sd card. In short, I was up that creek without a paddle.
    In short, I needed to gain access to the sd card but could not do it in the conventional way. So this is what I came up with that worked.

    1. I removed the battery and sd card from the phone.
    2. I connected the phone to my pc using a usb cable.
    3. I put the battery back in (without the sd card, and also without replacing the back cover).
    4. I powered up the phone, and then held down the volume down button
    to put it in bootloader.
    5. Because the card was not in the phone, it went into a normal bootloader
    mode. I then used the volume down button to choose Recovery.
    6. Carefully, I removed the battery while still connected to the pc. This
    allowed the phone to stay powered up even while the battery was
    removed (believe me, I tried to remove it at points before, but the
    phone always shut off.). I then placed the sd card back into the slot,
    and replaced the battery.
    7. I then used the pushed the power button, and it sent the phone into my
    recovery.
    8. I was then able to choose the usb connect option, where I was able to
    delete the file that was causing the problem, allowing me to do a
    complete wipe, and start over from the beginning.

    For me, and what I needed to do, I had to do those things 3 different times because I had to install an Hboot, PRI and Radio, one at a time. That meant I had to do the whole process 4 times, being the 3rd one was to actually boot phone up. Remember, all I had was a blank screen at first, so I had nothing to work with. It was bothersome and annoying, but at least now I'm back up & running.
    Maybe someone with a bit more knowledge can find an easier way to do it, or maybe already knows of one. I'm just putting this out there as reference for anyone that might run into a simular situation.
     
  7. mrawesome22

    mrawesome22 Android Enthusiast

    You need a card reader.

    Remove card from phone.

    Plug card into pc.

    Delete file.

    Done.
     
    scotty85 likes this.
  8. ramjet73

    ramjet73 Android Expert

    scotty85 likes this.
  9. Prinny

    Prinny Resident Linux Nutcase

    ramjet, I'm assuming that method is for S-Off users, correct?

    Reason I'm asking, is because I'm going to attempt to S-Off again today. I think I figured out what I was doing wrong, and that is using a 64 bit OS even though it says that you need a 32bit.
     
  10. Kamau

    Kamau Android Expert
    Thread Starter

    As I stated.
    I did not have a card reader.
    This was for general information.
     
  11. Kamau

    Kamau Android Expert
    Thread Starter

    I did not know that, and I guess I learned two things today.
    I'm still banging my head against the wall about the gapps thing.

    :banghead:

    edit: That may be something that should be included in the fix everything thread. I followed it to the letter because it says don't try any workarounds doing it. I took that literally.
     
  12. ramjet73

    ramjet73 Android Expert

    I would normally say yes, except for files signed by HTC like the rom.zip extracted from the RUU.exe. But scotty85, the OP of that thread, is pretty knowledgeable and says this towards the bottom of the first post:

    AFAIK, you cannot flash zip files from the bootloader when S-ON unless they are signed by HTC, but I'll PM scotty85 to clarify that since things may different on the Rezound or using the fastboot method. I can't really test as I'm S-OFF and don't want to set S-ON for that.

    I'm sure you will be successful in getting S-OFF soon and that won't be an issue for you anymore. Good luck!

    ramjet73
     
    scotty85, Kamau and Prinny like this.
  13. Prinny

    Prinny Resident Linux Nutcase

    I assumed as much. I've used that fastboot flash zip method before, for the RUU. Wine+Linux didn't run the full RUU, so that's how I did it.

    Reading this part here:

    1)make sure the file only contains changeable images-i.e. boot,system,or recovery
    2)make sure the android info document contains the same or higher main version than what is on your phone currently.

    Makes me think that it would be more for ROM updates and whatnot, instead of radios/hboot/etc. I could be wrong, though.
     
    scotty85, Kamau and ramjet73 like this.
  14. Kamau

    Kamau Android Expert
    Thread Starter

    Hope you guys don't mind me ear-hustling.

    :smokin:
     
  15. ramjet73

    ramjet73 Android Expert

    Hey, it's your thread. ;)

    ramjet73
     
  16. scotty85

    scotty85 Extreme Android User

    flashing files from hboot is definately not s on or off specific. if youre s-on,its just more of a pain,as there are more rules that apply when s on,but thats the case for any type of flashing,really,and why most of us strive for s off :)

    i mess with lots of htc phones,and its become quite cumbersome to physically keep moving files on and off the sd card,so ive been using the "ruu" method for awhile.
    pretty much all the newer htcs behave the same way. the rezound is quite similar to the 3d in specs,ram,processor,etc.

    you can flash files from hboot on the sd card,or with the fastboot method while s-on. basically while s-on:
    1)unsigned files must be only the allowed partitions(system,boot,recovery)
    2)signed by htc files must have the bootloader relocked since they normally contain partitions that are not changeble with an unlocked phone(hboot,radio,etc)
    3)wether signed,or unsigned, files must pass all the "usual" checks-main version,cid,etc. before the bootloader willallow the flash in hboot,or from fastboot.


    since the info on the android info text document is relevant with s-on, its a good habit to get into,to flash the main version low zip prior to any flashing. when i first got the rezound it drove me nuts trying to figure out why some PxxxIMG file would flash,and some wouldnt :eek: flashing the main version low zip sets the main version to 1.00.000.0 so that pretty much anything relying on a main version check will pass it.(note that changing the main version alone will not let you dowgrade to older firmware while s on. the phones are checking more than just that to flash whole,signed pacakages)


    while s-on,this is pretty much true. you can run "rom.zip" extracted from a .exe utility via the fastboot method,if the utility is giving you fits.

    bout the only other reason,really,to use it with s-on,would be if you want to flash "mini-ruus" rather than relocking and running whole ruus. before getting s-off on the rezound,i used to pull the boot and system images from leaks,pack them up and flash them,so i wouldnt have to upgrade to leaked firmware that may suck ;)

    the fastboot flash command can easily be used to flash recoveries and boot images,and is a a couple less steps than the fastboot ruu method,so thats typically how i changed kernels when i was s on.

    i typed that kinda fast,so hope it makes sense. just holler if you have further questions :)
     
    ramjet73 likes this.
  17. ramjet73

    ramjet73 Android Expert

    Thanks a lot for the clarification. If anyone that's S-ON needs the SetMainVersionLOW.zip it's attached to this post, and can be flashed from recovery as long as the phone is rooted. It's already been tested successfully to allow EVO V S-ON users who have taken the OTA update to install the RUU (exe or zip) after flashing it and relocking the bootloader, since the hboot level did not change with the OTA.

    ramjet73
     

    Attached Files:

    scotty85 likes this.
Loading...
Similar Threads - Got Phone Auto
  1. Ambee47
    Replies:
    2
    Views:
    664
  2. ocnbrze
    Replies:
    13
    Views:
    976
  3. The_Chief
    Replies:
    21
    Views:
    3,982
  4. Papamalo
    Replies:
    2
    Views:
    659
  5. Hannibal 99
    Replies:
    4
    Views:
    744
  6. Milo Williamson
    Replies:
    6
    Views:
    2,108
  7. Josie4077
    Replies:
    3
    Views:
    1,491
  8. TuBitMittens
    Replies:
    2
    Views:
    2,977
  9. and200cc
    Replies:
    16
    Views:
    2,513
  10. dontpanicbobby
    Replies:
    33
    Views:
    5,152

Share This Page

Loading...