Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

I Can't Unbrick NextBook Premium 7PSE

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #1

    I Can't Unbrick NextBook Premium 7PSE

    Bear with me, this story gets pretty sad. I've messed up horribly.

    Serial Number: YF081225252, made in August 2012.

    Yesterday I tried to install this ROM on my tablet:
    Forums - FreakTab
    http://www.freaktab.com/showthread.php?935-NextBook-7P12-SE-Ice-Cream-Sandwich-Finless-ROM-1-2-Root-and-Gplay
    vBulletin Forums


    To start with, the drivers wouldn't install properly. This should've been my first warning, however I forced the device to use the 'RK29 Device' driver. After this, RK29update.exe wouldn't recognise my tablet. This should've been the second warning, but I knew just enough about computers to screw myself over a little more. I opened settings.ini and compared the IDs in the [DEVICE_ID] section to my tablet's. I changed the PID to 0x300A, which I now realise was my biggest mistake.

    After this, RK29update.exe actually recognised my tablet. I made sure every checkbox was ticked except Backup and clicked EraseIDB. It succeeded. I then clicked Run and BAM. Error messages everywhere. The tablet would no longer boot. I went to the NextBook website and downloaded the "Netflix update" for my device, thinking I could flash it with that back to stock using the Rockchip Batch Tool. Version 1.4 of it listed my tablet in pink, with the numbers "1-1-2" under it. I then tried version 1.5 of it. The drivers for version 1.5 actually installed properly, and highlighted my mistake. My tablet is an RK30 device, not RK29. Version 1.5 listed my tablet is dark blue, with the same numbers.

    Not matter what I do now, my tablet won't boot. However it seems I can put it into black screen recovery. Is there ANYTHING I can do to fix my insanely stupid mistakes or should I just send it back and hope for a fix?

    PS. I'd be willing to try any beta software you have to offer.
    Tags: 7pse, bricked, crash, error, nextbook, premium
    #2
    12se or s?

    Hi.

    So, is your tab the 12se, or s model?
    I would think if you can boot into recovery, your still booting
    the tab, therfore it is not bricked.
    From recovery, can you get into adb?
    I believe if you can, all might not be lost....

    kuazar
    "Let me tell you why you're here. You're here because you know something. What you know you can't explain, but you feel it. You've felt it your entire life, that there's something wrong with the world. You don't know what it is, but it's there, like a splinter in your mind, driving you mad."- Morpheus
    nextbook7 #0811 with heavily modded finless 1.4
    huawei activa4g rooted, cwm, mihome

    Comment

      #3
      Hey there, thanks for your reply. The model is NEXT7P12, and the box says NextBook Premium 7SE, so it's the 12SE model.

      The method I used to get into recovery was to press the two volume buttons along with the reset button for two seconds. Then I released the reset button, and one second later, the volume buttons. The recovery screen's meant to be blank, right?

      Also, I've never used adb before, sorry.

      Comment

        #4
        ok

        Bear with me here, I woke up a little bit ago,
        just realized - ran out of coffee!!!
        Going to have to make a run to the store...

        Any way, no, I dont believe it should be blank.
        However, by your saying its blank, I will assume that the tab is on?
        If so, its not a done deal, I would think...
        Below is a link for adb, and a tut on setting it up in windows or mac.
        I dont use either, really, so follow the instructions.
        Once you do, if you do, you might want to do a "adb devices" and "adb shell dmesg | tail"
        without quotes, and verify output.
        Its a start.

        [How To] Setup ADB for Windows/ Mac
        http://forum.xda-developers.com/showthread.php?t=1387527
        For Windows Want to set up ADB or Android Debugging Bridge on your PC, here is a quick guide for you. This tutorial does not need large download or full Android SDK installation. You will just have to download a small compressed file, which is...


        kuazar
        "Let me tell you why you're here. You're here because you know something. What you know you can't explain, but you feel it. You've felt it your entire life, that there's something wrong with the world. You don't know what it is, but it's there, like a splinter in your mind, driving you mad."- Morpheus
        nextbook7 #0811 with heavily modded finless 1.4
        huawei activa4g rooted, cwm, mihome

        Comment

          #5
          The tablet's screen hasn't lit up since I tried to flash it. The charging light on the side and the way it shows up as an RK30 Device when restarted in a certain way are the only signs of life there are.

          I was unable to install PDANet, but I have adb installed in my C:\ drive. adb devices says that there are no devices attached.

          Also, I can boot into Ubuntu if that's easier for you to work with.

          Comment

            #6
            also

            Im back....coffee....

            While my third eye boots up....

            I dont know what version of Windblows(lol) you have,
            but it seems that everything began with the drivers.
            Just for the sake of saying so, Finless has a folder with the
            drivers in his .zip of his roms. Just in case.
            In any event, your going to have to figure that part out.
            Googling " rk30.. windows drivers wont install" or something like that might help.
            Also, randomly changing what block an image is written to would definately hose an install
            of a rom. Finless and other devs pretty much know these tabs and why "things" are where they are.
            No disrespect. Just saying.
            So I would start at the drivers for your OS, and go from there with adb...
            Hope this helps...

            kuazar
            "Let me tell you why you're here. You're here because you know something. What you know you can't explain, but you feel it. You've felt it your entire life, that there's something wrong with the world. You don't know what it is, but it's there, like a splinter in your mind, driving you mad."- Morpheus
            nextbook7 #0811 with heavily modded finless 1.4
            huawei activa4g rooted, cwm, mihome

            Comment

              #7
              no devices

              Originally posted by funkeh View Post
              The tablet's screen hasn't lit up since I tried to flash it. The charging light on the side and the way it shows up as an RK30 Device when restarted in a certain way are the only signs of life there are.

              I was unable to install PDANet, but I have adb installed in my C:\ drive. adb devices says that there are no devices attached.

              Also, I can boot into Ubuntu if that's easier for you to work with.
              Yeah, if you are having problems with the drivers adb would list no devices. Sorry about that.
              Thats why I posted the above, it was an after thought coming from the store.
              Sure if you have Linux try lsusb in a terminal...
              If your so inclined, there are tools to flash from there also.
              You can try that too

              kuazar
              "Let me tell you why you're here. You're here because you know something. What you know you can't explain, but you feel it. You've felt it your entire life, that there's something wrong with the world. You don't know what it is, but it's there, like a splinter in your mind, driving you mad."- Morpheus
              nextbook7 #0811 with heavily modded finless 1.4
              huawei activa4g rooted, cwm, mihome

              Comment

                #8
                so.....

                Were you able to get anywhere with this?

                kuazar
                "Let me tell you why you're here. You're here because you know something. What you know you can't explain, but you feel it. You've felt it your entire life, that there's something wrong with the world. You don't know what it is, but it's there, like a splinter in your mind, driving you mad."- Morpheus
                nextbook7 #0811 with heavily modded finless 1.4
                huawei activa4g rooted, cwm, mihome

                Comment

                  #9
                  Sorry for the late reply. Work and such getting in the way of solving this.

                  So, the entire output of lsusb is:
                  Code:
                  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 2232:1020  
Bus 002 Device 003: ID 8086:0189 Intel Corp. 
Bus 002 Device 004: ID 2207:300a
                  However, it seems that only the last line is relevant. It should be noted that the last line only appears when the tablet is in recovery mode. It doesn't appear when the tablet is fully off.

                  Comment

                    #10
                    Also, adb devices reports no devices attached when the tablet is recognised by lsusb or when it's not.

                    Comment

                      #11
                      ok. all is not lost then

                      Originally posted by funkeh View Post
                      Sorry for the late reply. Work and such getting in the way of solving this http://esausilva.com/2010/05/13/sett...-linux-ubuntu/ .

                      So, the entire output of lsusb is:
                      Code:
                      Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubBus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 2232:1020  
Bus 002 Device 003: ID 8086:0189 Intel Corp. 
Bus 002 Device 004: ID 2207:300a
                      However, it seems that only the last line is relevant. It should be noted that the last line only appears when the tablet is in recovery mode. It doesn't appear when the tablet is fully off.

                      Go to the below link and carefully follow instructions to get linux to identify device. Your vendor ID would be 300a
                      Setting Up ADB/USB Drivers for Android Devices in Linux (Ubuntu) - Esau Silva
                      http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
                      Setting up ADB in Linux Ubuntu to access Android Phones


                      And set up adb.

                      Then go to below link and VERY carefully (lol) follow instructions to flash rom.

                      [TOOL] rkflashtool for Linux and rk2808, rk2818 and rk2918 based tablets
                      http://forum.xda-developers.com/showthread.php?t=1286305
                      Hi, Because I don't run Windows nor NetBSD, I rewrote rkflash from scratch with the use of libusb-1.0, so you can now read and write your rk2818-based tablet's flash memory under Linux (also w/o the need to root your tablet). Credit for...


                      Good luck! Let me know how it goes or if you need my help

                      kuazar
                      "Let me tell you why you're here. You're here because you know something. What you know you can't explain, but you feel it. You've felt it your entire life, that there's something wrong with the world. You don't know what it is, but it's there, like a splinter in your mind, driving you mad."- Morpheus
                      nextbook7 #0811 with heavily modded finless 1.4
                      huawei activa4g rooted, cwm, mihome

                      Comment

                        #12
                        Thank you so much. I'll try this out tonight, but it looks like it'll work.

                        Comment

                          #13
                          No problem. Glad to help you.
                          Just let me know if you run into any problems....

                          kuazar
                          "Let me tell you why you're here. You're here because you know something. What you know you can't explain, but you feel it. You've felt it your entire life, that there's something wrong with the world. You don't know what it is, but it's there, like a splinter in your mind, driving you mad."- Morpheus
                          nextbook7 #0811 with heavily modded finless 1.4
                          huawei activa4g rooted, cwm, mihome

                          Comment

                            #14
                            OK, so I've set up my adb and the tablet doesn't show up when it's connected. It still shows up in lsusb. I also set up my phone and that appears in both lsusb and adb. I guess the tablet needs to be on and have USB Debugging enabled.

                            As for rkflashtool, it wouldn't detect my tablet as it's an RK30 model, not RK28 or 29. So I'm a bit stumped now. This is a stubborn little tablet. Also, I know it's not important if rkflashtool doesn't work, but how should I open update.img to read the HWDEF file? Thanks!

                            Comment

                              #15
                              oops

                              Originally posted by kuazar View Post

                              Then go to below link and VERY carefully (lol) follow instructions to flash rom.

                              [TOOL] rkflashtool for Linux and rk2808, rk2818 and rk2918 based tablets
                              http://forum.xda-developers.com/showthread.php?t=1286305
                              Hi, Because I don't run Windows nor NetBSD, I rewrote rkflash from scratch with the use of libusb-1.0, so you can now read and write your rk2818-based tablet's flash memory under Linux (also w/o the need to root your tablet). Credit for...


                              Good luck! Let me know how it goes or if you need my help

                              kuazar
                              So sorry. Totally slipped my mind that you had an rk30.
                              So. Before you compile as per instructions in above link, your going to have to
                              replace the mount points in the code for the rk30's mount points, and then compile.
                              You can get the mount points from the windows flash tool in Finless' rom.
                              Just make sure you use the original ones and not the changes you made.
                              If you run into any problems, you might want to hit up 900supersport.
                              He knows more about the rk30.
                              But I think it should be pretty straightforward.
                              Try that please.
                              As for update.img. Honestly, I have to look into it for you.
                              I dont know if you can use the same tool for the rk30 to pack it.
                              I just dont want you to run into the same thingas above. My oversight.
                              So try the above. I should have an answer shortly.
                              Sorry about forgetting to add thatI have to do some running around.
                              Be back in a few if you need help

                              kuazar
                              "Let me tell you why you're here. You're here because you know something. What you know you can't explain, but you feel it. You've felt it your entire life, that there's something wrong with the world. You don't know what it is, but it's there, like a splinter in your mind, driving you mad."- Morpheus
                              nextbook7 #0811 with heavily modded finless 1.4
                              huawei activa4g rooted, cwm, mihome

                              Comment

                              Previous 1 2 template Next

                              What's Going On

                              Collapse

                              There are currently 3438 users online. 2 members and 3436 guests.

                              Most users ever online was 63,956 at 18:56 on 20 March 2025.

                              Working...
                              X

                              We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                              By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                              I Agree