Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

PMIDi 13 FEL mode...

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    PMIDi 13 FEL mode...

    Well this is embarrassing! I'm trying to work on my PMID701i 13 to put elektricity ROM on it and I can't get into FEL mode! I've tried the method on the support site, to no avail....

    Any of you 701i 13 owners wanna help me? I'm going insane here!

    Steps I followed:

      1. Press and HOLD the MENU button (do not release).
      2. Insert the USB cord into the tablet (while holding MENU).
      3. Quick-press the POWER button 3 times (still holding MENU).
      4. Quick-press the HOME button (still holding MENU).
      5. Release the MENU button.
    https://public.bay.livefilestore.com...ion.png?psid=1

    #2
    Originally posted by elektrik View Post
    I'm trying to work on my PMID701i 13 to put elektricity ROM on it and I can't get into FEL mode!
    The tablet may not be really and truly off. Try pressing the power button for a long time (say, 15 seconds). If it doesn't start up and stays off, then it wasn't really "off". If it does start up, then shut it down normally and retry using another button (by rights, any button should work but some seem more reliable than others).

    Comment


      #3
      Originally posted by dolorespark View Post
      The tablet may not be really and truly off. Try pressing the power button for a long time (say, 15 seconds). If it doesn't start up and stays off, then it wasn't really "off". If it does start up, then shut it down normally and retry using another button (by rights, any button should work but some seem more reliable than others).
      Ya, I know where you're going with that-I was even hoping that was the case, but sadly it's showing up in device manager when I key in the combo (holding down menu button while quick pressing power, etc.). I know it's working in regards to drivers, but Live suite just isn't picking up the update......

      UPDATE: I got it-I 'uninstalled' from the Device Manager, but didn't delete the actual driver files (Windows 7 gives me that option). When I did that and reinstalled the live suite drivers, the 701i detected properly.

      ***NOTE: A word of warning to all-Polaroid in their infinite wisdom has yet again screwed up in that if you have multiple Polaroid devices, apparently from what I can tell, you have to make sure to only have ONE DEVICE installed at a time. In my case I had been working on the 701C and this screwed up being able to access the 701i (even though it had the same device ID in Device Manager). I need to sift through the registry to see if these two devices are close enough to share the same vendor ID's***

      Ugh, much fun
      https://public.bay.livefilestore.com...ion.png?psid=1

      Comment


        #4
        Hey dolorespark-thanks for the attempt to assist-turns out the PMID701i 13 is more different than I thought. it wasn't that things weren't working with the driver-it turned out to be my Live Suite image that just plain was bad and didn't want to flash. I've basically had to recreate elektricity ROM for this specific tablet....Curious to dissect it to see if it's more like the newer tabs...

        Anyhow, thanks again-cheers!
        https://public.bay.livefilestore.com...ion.png?psid=1

        Comment


          #5
          actually i think all of the allwinner based tablets have the same Vendor and device id's. nobody changes them in the builds so they all stay the same as the factory prototype board.

          Comment


            #6
            Originally posted by sabercatpuck View Post
            actually i think all of the allwinner based tablets have the same Vendor and device id's. nobody changes them in the builds so they all stay the same as the factory prototype board.
            Ya-it turns out the 13 on this model stands for A13! this sucker is an Allwinner A13! of course, I can't create a livesuite image for some reason :-( but at least I know the *why* to alot of questions I've been asking myself, lol!
            https://public.bay.livefilestore.com...ion.png?psid=1

            Comment


              #7
              Originally posted by elektrik View Post
              Ya-it turns out the 13 on this model stands for A13! this sucker is an Allwinner A13! of course, I can't create a livesuite image for some reason :-( but at least I know the *why* to alot of questions I've been asking myself, lol!
              As I discovered yesterday, the standard Livesuite files for each chip are different, producing the problem you (and I) got. I don't know if you tried removing then reattaching the USB cable, but if you had you would have gotten this highly informative message "PNPFelln: Invalid ID".

              I just got a 7-inch A10 and tried to make a new CM10 ROM for it. Since the vendor doesn't publish a stock ROM, I based my LiveSuite image on files taken from my A13's image. When I tried to flash it, L/S sat there & did nothing until I unplugged & replugged the USB cord - then it gave me the error. After messing with the driver, searching Google for an answer (forget it), etc, I remembered your predicament. This prompted me to recreate the image with stock files taken from an A10 ROM. When I retried, it flashed without a problem.
              Last edited by dolorespark; 13 January 2013, 04:46.

              Comment


                #8
                Originally posted by dolorespark View Post
                As I discovered yesterday, the standard Livesuite files for each chip are different, producing the problem you (and I) got. I don't know if you tried removing then reattaching the USB cable, but if you had you would have gotten this highly informative message "PNPFelln: Invalid ID".

                I just got a 7-inch A10 and tried to make a new CM10 ROM for it. Since the vendor doesn't publish a stock ROM, I based my LiveSuite image on files taken from my A13's image. When I tried to flash it, L/S sat there & did nothing until I unplugged & replugged the USB cord - then it gave me the error. After messing with the driver, searching Google for an answer (forget it), etc, I remembered your predicament. This prompted me to recreate the image with stock files taken from an A10 ROM. When I retried, it flashed without a problem.
                Ya-that was a little trick I learned from one of the other ROM developers here...comes in handy-if you can rebuild the 'stock' image, you at least have a working base to start from...
                https://public.bay.livefilestore.com...ion.png?psid=1

                Comment

                Working...
                X