For those who used the APX/NVFLASH Mathod, Need A Small Help...in middle of rooting.. - Eee Pad Transformer General

At the moment my device running TF Stock NOT rooted 3.1,
I can install prime 1.6 ZIP using this mathod?
Quick guide to unbricking:
Connect cable to computer and turn device on while holding down Volume Up. Screen will stay off, but USB will come on.
(Windows only) Find “APX” device in Device manager and update driver, then point it at usbpcdriver directory from the zip
Run download.sh (linux) or download.bat (windows)
(The quick guide from here http://androidroot.mobi/ )
At the moment I am in the stage where APX driver installed in WIN 7 and TF's screen shows black..so need to know what next :0
Thanks!

If the screen is black and APX is detected you would normally run the script after that. It's important you have the necessary rom files in that directory as well, otherwise is clears and theres nothing to boot there. It's in the guide and video, I'd check the video out if you need more help.
PS: This really should be in Q&A/General.
Sent from my Transformer TF101 using XDA Premium App

Backwardsblade said:
If the screen is black and APX is detected you would normally run the script after that. It's important you have the necessary rom files in that directory as well, otherwise is clears and theres nothing to boot there. It's in the guide and video, I'd check the video out if you need more help.
PS: This really should be in Q/A.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
So should I download the 1.6 Prime zip and extract this Zip into same folder from where I am running the .bat file?
Thanks!!

rommark said:
So should I download the 1.6 Prime zip and extract this Zip into same folder from where I am running the .bat file?
Thanks!!
Click to expand...
Click to collapse
Exactly!
(stupid 10 character crap)

rommark said:
So should I download the 1.6 Prime zip and extract this Zip into same folder from where I am running the .bat file?
Thanks!!
Click to expand...
Click to collapse
I would have to be an appropriate NVflash file that's unzipped in that directory. NVflash zip should contain *.img files that go in that directory.
Sent from my Transformer TF101 using XDA Premium App

I don't think Prime 1.6 is nvflash compatible yet.
Use the Prime 1.4 from here
http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.4.tar.bz2
extract the content to the nvflash folder
Watch the video in this thread
http://tabletroms.com/forums/showthread.php?976-Nvflash-Unbricking-and-forever-root!
If done correctly you'll have Prime 1.4 and CWM recovery installed.
Boot into recovery and flash Prime 1.6
BTW, wrong section for posting question.

Learn to read pinned thread, you have 3 days too do so

Related

USA 1.141.07 update fix with. .img's

Crsdr37 said:
Alright Guys in the USA. I will be posting the .img files to fix your device or update your device to 1.141.07 if you have either used the chinese update fix or some other various fix that left you with a different boot image. The instructions are simple.
1. Connect your tablet to the computer via USB. Put the boot.img and the system.img on your SD Card. Also put the Update.zip then use a file explorer to move the update.zip to the root of your SD card. Which is external SD. If you use Astro. (Alternatively you can just take your SD card out and put it in your computer to put the update.zip.)
2. You need to first push the boot.img
-Open ADB type su then hit enter. (your device will prompt for superuser you must select allow) Then enter the command below.
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p2 (hit Enter)
3. Then push the system.img
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
4. Force shutdown your device when those finish (as your screen may not turn on.)Then hold volume - and the power button "until the green android comes up very important do not let them go just because the device turns on" to start the update.zip. Let it finish (Your device will reboot when it completes.
5. Enjoy the fact your device is back to stock and you can now update when future updates release.
To push the files you will need adb shell. If you dont know what that is look it up, It is part of the android development kit. Second these 2 commands will push the files to their proper mount block. You must push the boot.img first then the system.img These files are for the USA update 1.141.07
http://www.megaupload.com/?d=TNDCAYC8 - System.img -MD5-2b4e2fea567ac883bb483fc96b1fdc9d
http://www.mediafire.com/?7b5llkk8bnmnd23 -Update.zip
http://www.mediafire.com/?3qahjh3twi6jc9t -Boot.img -MD5-4477d6739dd1e3b3ba1dbf94be7fe8f0
Here are 2 Mirrors To download the boot.img you will need to download both as the uploader made it a 2 part file making it easier for some countries to download. Give thanks yo ardatdat if these came in handy.
http://www.zshare.net/download/91195486183633a0/
http://www.zshare.net/download/9119547812fdf5fa/
I will check periodically on this thread if anyone has questions or needs Help. Guve a huge shout out to deckofficer54 as he is a co-worker and friend that dumped these files for me when I screwed my system up.
Click to expand...
Click to collapse
** Alright guys I am just posting this link for when you just do the update.zip because you are already on 1.104.05_COM_GEN1 and you have a different kernel then the update.zip, What will happen is when you reboot the tablet from just doing the update.zip you may have WIFI error. These files should resolve that issue. Once again they are only if you have WIFI Error on reboot. To install these you will need some type of file explorer that has rw access to the file system. I rec. Root Explorer. To install these follow these instructions.
1. Copy both modules to your SD card does not matter where.
2. With your File Explorer/Manager Copy both of these files. (Root Explorer will let you multi-select if you hit the menu button.)
3. Navigate to System/Lib/Modules.
4. **This step is very important- You must Mount your System for RW access. If you don't they will not copy. Once you have RW just hit the paste button and then reboot your device.
5. **This step is for anyone still having wifi error after reboot. (Stop being lazy lol and just do all the steps. From the top by mounting the boot.img and system.img that way your device is 100% stock there for no checksum issues.
http://forum.xda-developers.com/attachment.php?attachmentid=601473&d=1305842073 - This is the wifi modules Download Link.
Thank you thor2002ro for posting these on your kernel modules thread. Which is found here for anyone having any other issues.
http://forum.xda-developers.com/showthread.php?t=1058713
Happy Updating
​
Alright guys here is the list of supporters thus far for the unbricking and or updating of your tablet. If I missed someone let me know.
Supporters:
Euclid's Brother -Awesome tool to flash the images Making your lives easier one click at a time. If you want an easier way download these images and use this app https://market.android.com/details?id=com.interphaze.Acer_ROM_Flasher
bhageman -Donation
aerichards1977 -Donation
Sent from my PC36100 using XDA Premium App
thanks so much for this. to verify my build number is 1.141.07_COM_GEN1 is that right?
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Had a German 1.112 build i guess, bricked it and revocered it with Acer_A500_1.122.01_EMEA_GEN5. Used boot and system image and then updated and it really works!!! Thank you very very very much!!!
EDIT1: I even not lost my settings and can set the language to German too!!
EDIT2: Root gone (as expected), used Gingerbreak (tab version) and everything works fine.
phone.ds said:
Had a German 1.112 build i guess, bricked it and revocered it with Acer_A500_1.122.01_EMEA_GEN5. Used boot and system image and then updated and it really works!!! Thank you very very very much!!!
Click to expand...
Click to collapse
Your Very Welcome. Took me some time to get all the files but this **** works like a frickin charm. I wish it wasnt such a pain in the ass but hey its fixed.
ryutsuke said:
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Click to expand...
Click to collapse
well the only thing I can think of it either the lib modules for wifi are messed up in which case I can post a link with them or the kernel is different. I would use the 2 .img that I posted then use the update zip. That way the images replace your kernel which is always the root cause of wifi errors.
here is a link to the wifi lib modules. You need to use something like root explorer. To mount the system as rw. Then navigate to system/lib/modules and copy those two files into there with the system mounted as rw. Reboot and see if it fixes the issue!!
http://www.megaupload.com/?d=OKU671AP
futty said:
thanks so much for this. to verify my build number is 1.141.07_COM_GEN1 is that right?
Click to expand...
Click to collapse
Yes you are now stock and able to update when they release 3.1
dont we need to flash flexrom.img to be 100% stock?
The flexrom was flashed with the update zip
Sent from my A500 using XDA Premium App
confirmed working as well.
Crsdr37 said:
here is a link to the wifi lib modules. You need to use something like root explorer. To mount the system as rw. Then navigate to system/lib/modules and copy those two files into there with the system mounted as rw. Reboot and see if it fixes the issue!!
Click to expand...
Click to collapse
Am I missing something or did you maybe forget the link =P
Ah **** lol give me 1 second
http://www.megaupload.com/?d=OKU671AP
Sent from my A500 using XDA Premium App
Did those libs help at all?a like I said if they don't the only fix I I now would be to go back to the german or chinese update then flash both. Img then update.
Sent from my A500 using XDA Premium App
Image updates
Maybe some file corruption?! Loaded per the directions and on boot got error:
"Secure Boot Image LNX checksum fail"
Going back to the Chinese Rom.
You get that only when do don't do all three'. Once you reboot after pushing the 2 images. You have to hold down the volume - and the power button it will then run the update zip to complete.
Sent from my A500 using XDA Premium App
Crsdr37 said:
Yes you are now stock and able to update when they release 3.1
Click to expand...
Click to collapse
thanks so much again. you are a god i bet you helped millions by doing this
That was my intentions I came from the evo forums. Everybody there helps each other. Im just hoping people here pick it up and start helping when people have questions.
Sent from my A500 using XDA Premium App
ryutsuke said:
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Click to expand...
Click to collapse
Did you ever get wifi working
Sent from my A500 using XDA Premium App
tomlogan1 said:
Maybe some file corruption?! Loaded per the directions and on boot got error:
"Secure Boot Image LNX checksum fail"
Going back to the Chinese Rom.
Click to expand...
Click to collapse
Were u able to get past the checksum error?
Sent from my A500 using XDA Premium App

Cant install Cynagenmod 7

Someone please help me.
I already ahve a Rooted DHD. With clock mod receovery installed et.c.
(running Android HD)
but if anyone can tell me, I want to switch to Cynagenmod, Looks more good.
One there Wiki page, When installing the ADB.
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK#Windows
Im stucked at the 11 and afterwards. I did everything like it, nothing happend, Plugged in the Mobile with the USB bugging mode and did everything what i can.
But it's not working out, please somebody help.
On my computer the SDK didn't install to c:/ by default; it landed in C:\Program Files\Android\android-sdk\platform-tools
You then have to change step 11 to:
In the "Variable values" section, add at the very end the location of the tools & package-tools folder, with a semicolon separating these two paths from the rest, e.g. C:\Program Files\Android\android-sdk-windows\platform-tools;C:\Program Files\Android\android-sdk-windows\tools.
Click to expand...
Click to collapse
And 12 becomes:
The Google USB Driver package only supports select devices out-of-the-box, we will be downloading a modified file that should provide support for all CyanogenMod supported devices:
Download the modified driver inf file: Download
Unzip the file & inside you will see android_winusb.inf. Copy this file to C:\Program Files\Android\android-sdk-windows\extras\google\usb_driver\ replacing the "stock" android_winusb.inf.
Click to expand...
Click to collapse
Dan
I don't get it...why would you need to install Android SDK and ADB drivers to just go from ARHD to Cyanogenmod7?
anetam said:
I don't get it...why would you need to install Android SDK and ADB drivers to just go from ARHD to Cyanogenmod7?
Click to expand...
Click to collapse
No idea, boot into recovery, and wipe data then install from zip, and job done
Hey can you provide an update with how CM7 compares to ARHD 6 as I think i'm getting tired of ARHD. I keep finding little things in ARHD that annoy me but don't want to go through flashing again for no reason, yet
Sent from my HTC Desire HD A9191 using XDA App

[Guide;How to]Install ADB&Fastboot

Hi everyone
I made this guide to help people that dont understand what adb&fastbooy is and how to install them.
First you need to download this zip file --- http://www6.zippyshare.com/v/76832019/file.html
then download this guide that i made with instructions and pictures --- http://www6.zippyshare.com/v/74547920/file.html
Once you complete those 2 downloads open adb&fastboot installing.docx and follow the instructions...
Hope i made it easy to understand
cheers
which versions of adb and fastboot did you include in the zip?
are they old ones or taken from the tools-download of the latest sdk?
i ask cause the for some functions newest adb is needed and the date of the files in the zip says 2011-1-18...
thx & greetz,
sUsH
sUsH667 said:
which versions of adb and fastboot did you include in the zip?
are they old ones or taken from the tools-download of the latest sdk?
i ask cause the for some functions newest adb is needed and the date of the files in the zip says 2011-1-18...
thx & greetz,
sUsH
Click to expand...
Click to collapse
Are the old ones... :/
Sent from my ASUS Transformer Pad TF300T using xda premium

For those wanting to just root, here's some help

This is for those on ICS only. If you have upgraded to jellybean, this will not work.
There have been other posts, and this one is nothing new, in fact it's a remake of DebugfsRoot so that author gets all credit. I just made a couple of tweaks to help those that might be having a fuss with it. First, this is assuming you are using a windows PC. I don't work on MACs. Next, make sure you have ADB working properly on your PC. To do this:
Go to your start menu and open a command prompt, usually by typing "cmd" in the run blank.
Type adb
If you don't get a whole heap of feedback of how to use adb returned to you, and instead get an error, you don't have it set right. If you're sure you installed the development kit and you have ADB on your PC, do the following:
FIND IT... and add it to your system path variable. adb.exe comes with the root extract, so if you don't have the kit installed, you can use that instead, but seriously, if you want to root and enjoy this hobby to its fullest, install the android kit. The most common location is "C:\Program Files (x86)\Android\android-sdk-windows\platform-tools" - but hey, get this, did you know the asus sync software available from their site also includes it? I just now found that out haha...
To add whichever absolute path to your system path variable, start menu > control panel > system > advanced system settings > environment variables button > In the system variables window, scroll down to path, click it, click EDIT > move your cursor to the very end and add ; again that's (semi-colon) - you'll see other entries there which show you, just follow the pattern. Remember, you only need to do this if your original attempt at typing adb didn't work. Save your settings, return to that command window, and try adb again, you should have better results this time.
Now then, download the root package here:
https://dl.dropbox.com/u/33560221/DebugfsRoot_v1.8.exe
This is the original software with slight enhancements by me...those enhancements are all to the BAT file, and are as follows:
The EXE file is a self-extracting archive which will extract the contents to C:\tabletroot Please don't change this install location. You'll see why in a moment. the RootDebugfs.bat was edited as follows:
Within each push command, I preceeded the file name with C:\tabletroot so it knows exactly where to find what it needs. I found if you just pushed without it, it didn't like it too much.
Last, after each "wait-for-device" command, I added TIMEOUT 120 This forces the batch file to sleep for 2 minutes allowing plenty of time for your tablet to reboot. I found if you didn't do this, it would try to do the next commands way too soon causing failure. This should give enough time for you to get to your desktop before the next command is issued. If you find it's too long and you're ready to go, just press a key and that will kill the clock. If not long enough, edit the batch file with any text editor, and increase the timeout time.
All other files are what was originally found. I didn't update any of the apks or edit any other file than the main batch file. That's it. I used these exact files to root my tf300t on firmware version .30 with no issue of any kind. I hope this helps someone. If you run into trouble, not sure how much help I can be. I'm simply posting exactly what I did. I didn't author anything other than the edits mentioned above. Good luck.
Did the your_path thing and it didn't work.
Could you describe just a bit more which part you're having trouble with and what happened?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I added ;<your_path> at the end of the path and it did not change anything in the CMD window after imputing adb, when nothing happened before.
I'm sure it's something that I did not do that went wrong.
The your path thing was just a descriptor. You need to replace that with the location of your adb.exe file so it would look like ;c:\program files\ ... and so on. I gave a sample path of where mine is but it could vary between systems.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Well if my previous answer doesn't prove I've never rooted anything...
Where do you DL the adb file from?
Couple Choices
10010110 said:
Well if my previous answer doesn't prove I've never rooted anything...
Where do you DL the adb file from?
Click to expand...
Click to collapse
OK, I will assume you do not have the android development kit installed, so you still have a couple of choices here:
ADB comes with the archive I directed you to download, so if you download it and run the EXE, you'll find ADB inside the newly created folder I mentioned, so using this method, you would add... ;C:\tabletroot
ADB also comes with the ASUS sync software found on the ASUS website. If you have / will download and install this software, the ADB file will be located here: C:\Program Files (x86)\ASUS\ASUS Sync or it might be in C:\Program Files\ASUS\ASUS Sync just depends on the type of system you have. I have a 64-bit OS, so I have a Program Files and a Program Files (x86) folder (the x86 is for 32-bit programs) - in this situation, you would want to add ;C:\Program Files (x86)\ASUS\ASUS Sync or ;C:\Program Files\ASUS\ASUS Sync
Remember if you go with option one, download the archive I provided and run it before you add / test to your path variable, because that's what puts ADB in place. Once you have that all done, just go run the BAT file - after you connect your tablet and can see it on your PC as a media device that is
Clarification
So using this method do we need the blob files or was that just for downgrading, and since we don't need to downgrade using this method, everything that we need is in that self extracting exe file? I'm not interested to unlock bootloader -for now-...just want a few tweaks and to install a few root apps
Sorry, I only have experience rooting a couple HTC devices and they were both 1 touch and rooted.
I hear you, and they are legit questions. This is for rooting only. This procedure doesn't unlock your bootloader, which is why i used it. All you need is in the archive.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Another question, do you have to put the tablet into any special mode in order for the batch file to work? If I remember correctly, the phones just had to be on, plugged in via usb (duh) and the batch files did the rest. The batch file has the 120 second pause, but it seems like it does the first part with -
1. waiting for device to be detected
2. daemon not started
3. daemon started successfully
then it just sits there, and its been longer than 2 minutes...what am I missing?
Only mode i know of is to put it in media mode mentioned above. Also I've read to turn off asus sync found in the sync section of settings.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
HandicapFailure said:
Another question, do you have to put the tablet into any special mode in order for the batch file to work? If I remember correctly, the phones just had to be on, plugged in via usb (duh) and the batch files did the rest. The batch file has the 120 second pause, but it seems like it does the first part with -
1. waiting for device to be detected
2. daemon not started
3. daemon started successfully
then it just sits there, and its been longer than 2 minutes...what am I missing?
Click to expand...
Click to collapse
Either unknown sources, or USB debugging might need to be on.
Ah yes forgot those. I'd do both thankya.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
FYI the batch file does not work with windows xp, I searched and seems timeout is not supported. Sucks having an old OS..
I ran the commands manually and the root worked, so thanks anyway!
rickc3k said:
FYI the batch file does not work with windows xp, I searched and seems timeout is not supported. Sucks having an old OS..
I ran the commands manually and the root worked, so thanks anyway!
Click to expand...
Click to collapse
Wow, I didn't know that. Thanks for the tip.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

[Q] HUGE problem! >:_(

Hi,
I was going to install a ROM on my Nexus, so I made a backup and wiped EVERYTHING. Including the SD card so now in clockworkmod
it can not mount the SD card, I cannot mount it to my computer... I am shaking and my hands are cold... I cant flash any rom HELP NOW!!!! ((((
thanks
No need to panic, its a nexus.
can you adb push a ROM zip to your sdcard?
if you can't then you can always flash a factory image with fastboot and you'll be back to normal in no time.
So take a deep breath and chill.
Sent from my Nexus 7 using xda premium
nodstuff said:
No need to panic, its a nexus.
can you adb push a ROM zip to your sdcard?
if you can't then you can always flash a factory image with fastboot and you'll be back to normal in no time.
So take a deep breath and chill.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I have a factory image please tell me how'd I do that in fastboot! (only if they had a begging at knees thing)
ok i will write you some step by step functions to follow in order to get yourself a rom onto your device
Info that is Needed!
Do You Already Have ADB functioning on your Computer
If Yes - Skip to Step 2
If No Proceed from Step 1
----STEP 1----
install the ADB drivers for your device
im going to assume you have a windows machine here so the followthrough will be for windows (i use Win7 but it should be the same)
BOOT YOUR DEVICE INTO RECOVERY WHILE PLUGGED INTO YOUR PC BUT DO NOT CLICK ON ANYTHING
1. Download These Google Drivers for Nexus Devices http://www.themoviedb.org/movie/15092-crank-ii-high-voltage
2. extract the folder
3. press the start button
4. right click on "Comptuer" or "My Computer (XP)
5. Click on Manage
6. in the new window press "Device Manager" on the left
you should see in the tree on the right (a device with a yellow exclamation mark ! probably called nexus)
7. right click it and press update driver software
8. press browse my computer for driver software
9. press let me pick from a list of device drivers on my computer
10. press have disk
11. press browse
12. on the new window navigate to the folder you extracted earlier and select the android_winusb.inf
13. press ok
14. there will either be 1 or 2 options to choose - click Android Composite ADB Interface and then press next
15. tick always trust software from google inc. and then install
your device should now have ADB capablilities
Proceed to step 2
----STEP 2----
this will use adb to push a file to your device while it is in recovery mode which you can then flash
1. Download This - http://www.mediafire.com/?50baad8rykng2j0
these are adb & fastboot binaries which will allow your pc to send files to your nexus via ADB
2. extract the downloaded archive to somewhere easy to remember ( i suggest C:\fastboot )
3. rename your downloaded custom rom to rom.zip (for simplicity) and copy it to the extracted directory (the one with adb.exe & fastboot.exe)
4. bring a command prompt to this directory
- in the directory you extracted (c:\fastboot) hold shift and right click in a blank area of the main window
- click "open command window here"
or
- Windows Key & R
- in the new box type cmd then press enter
- type cd c:\fastboot (where c:\fastboot is the directory where you extracted)
now to push it over
5. in the cmd window type adb devices and make sure your device is listed
your should see something like
list of attached devices
XXXXXXXXXXXXXXXX Recovery
where XXXXX is your devices serial number
6. in your cmd window type adb push rom.zip /sdcard/
this will take a while to complete but once it is down go back to your device and try to install a rom as you usually would
you should see the file in your internal memory to install now
^^ I was too slow!
First install the android SDK (Google it) then you need to put fastboot in your path you need to open my computer, system properties, advanced system settings, environment variables button at the bottom, then in the bottom window scroll down til you see find path and edit it and add the path to the android SDK and in particular the platform-tools folder.
So if you download the android SDK to your C drive, the path you will be adding will be like ";C:\android-sdk\platform tools" (note the semi colon at the start, important to separate entries)
Once the path is set up you can use fast boot in cmd just by typing fastboot xxxxx rather than typing C:\android-sdk\platform-tools fastboot xxxxx every time.
So next thing is to extract the images to somewhere.
Inside the zip is another zip called image-nakasi-jzo54k,
unzip that til you have .IMG files, system.img, boot.img etc.
then once they are extracted you use cmd to CD to that folder where you have the images and you can start to flash them.
fastboot flash system system.img
fastboot flash boot boot.img
You could just use flash-all.bat but and that will flash them all automatically but will wipe your internal SD.
Sent from my Nexus 7 using xda premium
If you JUST read that, I figured it out, and if I can flash all the partitons correctly, I will punch the thanks button.
cburk01 said:
yay new problem
Ok, so I unzipped it, extracted the thing inside, but it was it a weird format Windows recognized as "file". So, I added .zip to the end. WinRAR opened it, I saw the files, began to extract when an error popped up about the archive being damaged. WTF.
Click to expand...
Click to collapse
What was the name of the file that you had problems with?
the first one is a .tgz file then .tar but the one with the images inside that is .zip (looking at it now)
use 7-zip instead of winzip
Sent from my Nexus 7 using xda premium
nodstuff said:
What was the name of the file that you had problems with?
the first one is a .tgz file then .tar but the one with the images inside that is .zip (looking at it now)
use 7-zip instead of winzip
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Now I REALLY DO have a problem. I flashed boot.img, system.img, userdata.img, everything to the right partitons and still have a problem. Boot loop. Sticks on Google logo. Why? I did everything right. I even tried fastboot boot boot.img, no luck. I saw some people having boot loop problems, too on 4.1.2. So now, until you reply, I am going to try a custom kernel. Scratch that I'm using ToolKit to download and install 4.1.1.
If you flashed userdata.img that means your internal SD is wiped.
did you run flash-all.bat that is in the folder?
It would be no harm to do that now since everything is wiped already.
no matter what its still recoverable so don't worry.
Sent from my Nexus 7 using xda premium
nodstuff said:
If you flashed userdata.img that means your internal SD is wiped.
did you run flash-all.bat that is in the folder?
It would be no harm to do that now since everything is wiped already.
no matter what its still recoverable so don't worry.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
*facepalm* with the SD I already wiped that before I flashed. And I didnt run flashall.bat or what ever its called so I am going in to try that. Ran flashall got some weird radio flashing error so now continuing with ToolKit.
Flash-all.bat just automatically flashes all the images by running one command, it simplifies the process.
It just isn't ideal if you wanna keep your SD contents.
that's why you flash images separately, so you don't flash userdata.img but since you already wiped it then you're good to go.
Sent from my Nexus 7 using xda premium
WOOT!!!!!!!!!!!!!!!!!!!! Although I don't know if my backup will work, my tablet is now booted up into Android 4.1.1. Now I am going to root it, install a ROM, restore my data partition from TWRP, and (hopefully) have what I have been waiting for. A updated, functioning Nexus 7. *mashes thanks button*
Hey, should I update to 4.1.2 THEN root or root on 4.1.1 THEN flash the ROM?
cburk01 said:
WOOT!!!!!!!!!!!!!!!!!!!! Although I don't know if my backup will work, my tablet is now booted up into Android 4.1.1. Now I am going to root it, install a ROM, restore my data partition from TWRP, and (hopefully) have what I have been waiting for. A updated, functioning Nexus 7. *mashes thanks button*
Click to expand...
Click to collapse
Your backup is most likely gone, its stored on the SD card and that is wiped. Unless you have it on your computer, then you are all good.
Glad its back to life and now you know how to fix it if anything goes wrong.
What you learned today is very valuable to know.
It's nearly impossible to kill a nexus device (from a software perspective)
Sent from my Nexus 7 using xda premium
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
cburk01 said:
Hey, should I update to 4.1.2 THEN root or root on 4.1.1 THEN flash the ROM?
Click to expand...
Click to collapse
Update first
Sent from my Nexus 7 using xda premium
Yes, I have my backup on my Macbook (running Windows 7). Thanks for all the useful advice. lol about the Nexus devices are hard to kill thing, I imagined a cockroach. And about the valuable lesson thing, I learned fastboot commands and adb stuff all when I was messing with (then soon after fixing) my HTC EVO 3D. Oh, I love XDA. Thanks again.
-cburk

Categories

Resources