Database Info

[HOWTO] Acquire root on a German/European Milestone (v2.1.31/34)

Welcome
I am 2 lazy to translate so I just write my own and personal tested HOW-TO for getting root on a German 2.1 Milestone. This should also work with any European version of the Motorola Milestone (not tested!!!)
I take no responsibility for any damages done to your device.
You will void your warranty with rooting your phone!
File and idea sources: http://www.android-hilfe.de/root-ha...1-update-mit-oder-ohne-root-fuer-dummies.html
Required:
BRAIN!
Milestone with Firmware 2.1
Motorola USB Drivers
RSD Lite
Vulnerable Recovery SBF
Sera’s update.zip
Step 1
BACKUP YOUR F.. DEVICE
Dont need to explain that. Keyword: Nandroid
Step 2
Start your device in Bootloader Mode
You do that by pressing D-Pad up (hold it in landscape mode) and while holding this key start it up with power button. The bootloader screen should show up after some seconds.
Step 3
Connect your Milestone to your Computer via USB and be sure your device is recognized correctly!!!
Now start RSD lite, select the Vulnerable Recovery SBF File and hit the start button.
If the button is greyed out try to rename the sbf file so sth. shorter.
If you get an error on this you have to try by commandline:
First of all you should rename the SBF file to something simple like „recovery.sbf“ and copy it to C:\.
Navigate to your RSD directory using the „cd“ command.
Now type f.e. „SDL.exe -f c:\recovery.sbf -t 2“.
RSD should popup and do the job for you
Step 4
After the flashing progress your device is starting up and now everything you have to do is to root your phone. Thats very simple and working with the provided update.zip. Copy this file to the root of your SD-Card.
Now start up the phone in recovery mode with holding your camera button pressed while pressing the power button. The M-Logo shows up after around 5 seconds and after some further seconds there should be a /!\ sign.
Release the keys as soon you see this. Now hold your VOL-UP button pressed while hitting the camera button again.
You should now be in the recovery console. – FINALLY – select the update.zip with the hardware-keypad. This should only take some seconds till ist complete.
Reboot and everything is fine now
Undo root
Use ADB-Shell to run following commands
Code:
mount system
rm /system/bin/su
rm /system/app/Superuser.apk
umount system
Correct me if I forgot sth.

great. i'll give it a try.
many thanks.

Sorry to jump here late.
I'm trying to root my Milestone. Bought this as NAM unlocked phone from Negri but it's clearly stamped as Made in Brazil A853 Model.
tested Step 2 and does:
Code:
Bootloader 90.78
Battery OK
OK to Program
Connect USB
Data Cable
I have the 2.1-update1 firmware.
Any ideas if this will work on my phone?
I been digging around the whole internet and it gets confusing either this will work right or not. Mainly because of the issue regarding the bootloader on the previous 2.0 versions and signed bootloader.
Also I run Ubuntu on my PC although I have a windows7 lap from my wife, but would like to do it under linux. Possible?
(I wonder WHY Motorola manufacture a Linux phone with solely windows drivers?)
Any help appreciated.

milestone
Hi guys, i flashed 2.2 into my milestone. At first, it worked fine but recently, the screen has going bonkers. Like sometimes the icons are being pressed without me pressing and sometimes i cannot unlock my phone. How is this possible?

Solution: Gtablet can not power on or reboot after nvflash

I hope my post will help somewhat those buddies who had the same problem or who will probably have this problem in future.
I had the problem that my gtablet couldn't power on after I did Nvflash. I'd been frustrated in the past week for searching the internet to find the way out.
The similar problem that tcrews had. (http://forum.xda-developers.com/showthread.php?t=903684)
Also some posts I browsed:
http://forum.xda-developers.com/showthread.php?t=999287
http://forum.xda-developers.com/showpost.php?p=10951417&postcount=1
http://forum.xda-developers.com/showthread.php?t=927006
http://forum.xda-developers.com/showthread.php?t=971608
http://forum.xda-developers.com/showthread.php?t=938706
I am grateful to tcrews and a lot of other buddies for their inputs which saved me lots of time, though i didn't find a right solution from their posts. Acidburn89's solution in tcrews's post (page 9) didn't work out for me either.I don't know whether tcrews solved his problem in acidburn89's method.
I tried all the methods I could find and nothing worked out for me. The only way I can turn the tablet on is to follow tcrews's post on rebooting the tablet by using nvflash (nvflash --bl bootloader.bin --download 9 recovery.img --go)
Some background of bricking my gtablet:
1.my gtab had CWM0.8.and was running rom "zpad clean 3.0" (before that it was TNTL, not any problem)
2.one week ago, I was trying to flash a rom from a chinese website, which was modified from the official malata zpad rom. This was the problem started from. After flashing (nvflash method),the tab was rebooting and stuck at "Tegra II" logo and couldn't never start with the new rom. At this moment, i could still power on and off the tab.
3.next I flashed my tab by following this link (http://forum.xda-developers.com/showthread.php?t=861950) After flashing it, the tab couldn't not reboot, and could not power on. Every time I pressed the power button, it just went to the APX mode authomatically
(with black screen).Only using the above-mentioned method (from tcrews) I could start the tab.
The solution I finally tried out: (Take out your sdcard from the tab if you have one in it)
1.Have these two files ready: recovery-stock.img (download the attached recovery-stock.zip and change zip to img), and original gtablet update.zip. I copied this original update.zip file from my gtab and saved in my pc, i think you can also find links in this forum for the original gtablet roms,like this http://forum.xda-developers.com/showpost.php?p=9837354&postcount=3 (not sure whether these are same as I extracted from my gtab originally, if not working, I can upload my rom for downloading)
2.Copy recovery-stock.img into the nvflash folder.
3.Start the tab by nvflash (tcrews' method)
4.Mount/Activate USB conncetion, and copy the original update.zip into the tablet internal sdcard.
5.(Not sure this step is a must or not). Download cwmod-internal.zip in the line http://forum.xda-developers.com/showthread.php?t=865245, extract it and copy the folder "recovery" including the command file to the sdcard.
6.Power off the tab.
7.Power on to make sure you enter APX mode (you will see the black screen, but hear a bing sound)
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
9.Press and hold the Volume + on the Gtablet and press enter on the PC to execute the above line. You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashing ! Dont worry.
10.Repeat step 7 and 8, and press enter (do NOT hold volume +!)
11.The tab will start to the TnT like the original one you had, and Magic now: you can turn off and turn on the tab NORMALLY!!
I tried this method with and without CWM. Both worked. So don't worry whether you tab has CWM or original recovery. My advice: flash your favorite rom using sdcard method instead of nvflash. If you want to nvflash it, save all the files we have used for possilbe repeation of our above job to get your tab back to life!!
I've received a lot of information and help from xda-development before, and hope my first post could contribute to our community a little bit.

Just noticed that idocinthebox has the same idea of correcting recovery.img in this post:
http://forum.xda-developers.com/showthread.php?t=994046

Master
Wow. I followed every instruction to a 'T' and was bricked for the past 6 hours with the APX boot loop.
Finally I stumbled across your thread and was 'reborn' into my G Tablet.
Thank you so much for taking the time to post this. It saved me from wasting even more sleep. (smile)

Well done! If this helps anybody mash the thanks button ;-) ^^^^^^^^^^^

Exact same issue
Can you provide your stock update.zip file? I have not been able to find a file that works for me. So far I have repeated this process many times with many update.zip fules but its still wont start on its own.

I can fin a update.zip.... can you posted here?
Thanks.

I follow this thread but still my gtab is power on APX (only). I was using the stock 3588 and went to the new 4349... start to having issues decided to go back to 3588 using the nvflash. it worked at the first time (until I had the tablet on) As you turned of and turned on, just a black screen (apx) and the only way to get it back is running the nvflash again but if I turned off have to do it again.
Please help!!!!
I can't figure it out on my own.

The solution I finally tried out: (Take out your sdcard from the tab if you have one in it)
1.Have these two files ready: recovery-stock.img (download the attached recovery-stock.zip and change zip to img), and original gtablet update.zip. I copied this original update.zip file from my gtab and saved in my pc, i think you can also find links in this forum for the original gtablet roms,like this http://forum.xda-developers.com/show...54&postcount=3 (not sure whether these are same as I extracted from my gtab originally, if not working, I can upload my rom for downloading)
*** could you posted your original (stock rom) update.zip? The one above mention is not in zip format. I did a zip format but still not working.
2.Copy recovery-stock.img into the nvflash folder. (i did that)
3.Start the tab by nvflash (I did that)
4.Mount/Activate USB conncetion, and copy the original update.zip into the tablet internal sdcard.
*** the only way I could put the update.zip in the internal sdcard on the tablet was after nvflash the tablet power up, then I plug a usb drive (with update.zip in it) and copy to the internal sdcard... i did not plug the tablet to the computer.
5.(Not sure this step is a must or not). Download cwmod-internal.zip in the line http://forum.xda-developers.com/showthread.php?t=865245, extract it and copy the folder "recovery" including the command file to the sdcard.
*** I did that the same way above mention from a usb drive.
6.Power off the tab.
7.Power on to make sure you enter APX mode (you will see the black screen, but hear a bing sound)
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
9.Press and hold the Volume + on the Gtablet and press enter on the PC to execute the above line. You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashing ! Dont worry.
10.Repeat step 7 and 8, and press enter (do NOT hold volume +!)
11.The tab will start to the TnT like the original one you had, and Magic now: you can turn off and turn on the tab NORMALLY!!
6,7,8,9,10,11 **** I did all but at the end still my tablet only work with nvflash unless I never turned off!!!

that download is corrupt...
Err it's the img ranamed... by bad..

Naysses and jettajon:
I uploaded the original update.zip I extracted from my G-tab. Try it to see whether it can help u.
w w w.mediafire.com/?fywhca6fi514toq
(remove space between "w"s)

I have the same problem, however your solution didn't fix it...Not sure what went wrong but I followed your directions exactly

Citi said:
I have the same problem, however your solution didn't fix it...Not sure what went wrong but I followed your directions exactly
Click to expand...
Click to collapse
I ran across this post http://forum.xda-developers.com/showthread.php?t=1010659 which says that the BCT part of the nvflash isn't the same for all the GTablets and that's my experience.
I couldn't get nvflash_gtablet_2010110500.zip (from the dropbox repository of nvflash files) to work, but nvflash_gtablet_46_2010112600.zip worked fine.
The problem was that I couldn't get CM7 installed on my GTablet, but then I hacked the gtablet.cfg file to swap partitions 7 and 8 by merely cutting and pasting the partition 8 (name=OGO stuff) and putting it before the partition 7 (name=BLO stuff) to match the order of the gtablet.cfg in nvflash_gtablet_2010110500.zip.
Now CM7 has installed and seems to be working fine for me.
BTW- I didn't nvflash the CWM recovery since I was trying to minimize the number of things I was messing with. I assume it'll work, but I already had CWM installed on the internal emmc (SDCARD2) so really didn't even need to nvflash it.

Nope, I have tried both files and neither worked for me

kaluna00 said:
Wow. I followed every instruction to a 'T' and was bricked for the past 6 hours with the APX boot loop.
Finally I stumbled across your thread and was 'reborn' into my G Tablet.
Thank you so much for taking the time to post this. It saved me from wasting even more sleep. (smile)
Click to expand...
Click to collapse
guobug you are a hero
same thing happened to me
and because of you it works!!!
( followed the steps and used your updat.zip)
BUT I have another problem
when I tried to install CW
it says "Can't open sdcard/recovery.log"
now I dont know what to do
because I want to install another rom
I think there is something corrupted in the device after apx boot loop

You are a life saver. Worked like a charm. Have been reading through 50 million threads the last 3 days, and happened to find this one. Absolutely amazing. Thanks.

In step 8 I don't know where to type the code in, which Dos command, the dos command window which nvflash step opened( and I didn't press enter to close that window), or I have to open a new one( or make a new .bat file with the code).
I do it and cann't see it install the original rom( "You will see it starts to installing the original rom..(about 3 minutes)..and then power off autmotically after finishing flashingtes" as you wrote in step 9)
So I still cann't fix my problem.
Please help me!

guobug said:
8.Type in the Dos Command: nvflash --bl bootloader.bin --download 9 recovery-stock.img --go
Click to expand...
Click to collapse
Do I manually open the Dos Command, or should this open on it's own... I'm opening Command Prompt, and pasting what you're saying to use. I'm getting
"nvflash is not recognized as an internal or external command, operable program or batch file."
Obviously I'm doing something wrong.

BrandonJay21 said:
Do I manually open the Dos Command, or should this open on it's own... I'm opening Command Prompt, and pasting what you're saying to use. I'm getting
"nvflash is not recognized as an internal or external command, operable program or batch file."
Obviously I'm doing something wrong.
Click to expand...
Click to collapse
That error means the command 'nvflash' is not in the path for the windows command line.

Where do you type the DOS command at? Thanks.

when I hold the volume up and hit enter on the keyboard I get a bad command prompt. What am I doing wrong?

[Q] Emergency Problem trying to Un-Root

The transformer is the first android device I've owned and I bought it off someone who had previously rooted it. Ive had it for a week and finally decided I wanted to unroot it. So i did my homework, got the adb up and running and followed this thread: http://forum.xda-developers.com/showthread.php?p=14050214&posted=1#post14050214 as a guide for unrooting it. Well like I said there I... pushed the asus firmware blob with no problem then typed "adb shell" to get to root and copied and pasted "dd if=/data/local/blob of=/dev/block/mmcblk0p4" and pressed enter. Upon reboot, I saw the progress bar fill up and then the Transformer rebooted. Now it is in a continual loop where it restarts (and my windows xp recognizes it), makes a click noise, shows the 'EEE Pad-with-the-ASUS-logo-below' start up screen, then after about ten seconds restarts to the home screen, then repeats the process all over again. If i try to start in recovery mode it attempts it enter it (shows a progress bar), then switches to an image of a triangle with an orange exclamation point in it next to the android logo. I seriously think I'm fuc*ed. I knew I shouldn't have tried this. AND I REALLY NEED HELP! please I'm begging anyone. I've only had the thing for a week!

Were you on a custom rom before trying to revert or just rooted stock?

Have you tried wiping data? You can hold volume down + power an in 5 seconds it will suggest wipe the data. But before that you should better try "adb shell" while your device in boot loop and root device again to fix it or "adb logcat" to find out what's broken. It will not work if you wipe your data as adb will be disabled, which is your best friend now. You are pretty close to brick.
Sent from my Transformer TF101 using Tapatalk

lordgodgeneral said:
Were you on a custom rom before trying to revert or just rooted stock?
Click to expand...
Click to collapse
Yeah, MoDaCo Custom Rom the latest version...

Thats probably the problem. I don't know if the stock recovery plays well with custom roms. Did you make a nandroid after you rooted before you flashed madaco? It may be best to reflash the CWM blob and restore to as close to stock as you can before reflashing the stock recovery blob.

ivan.volosyuk said:
Have you tried wiping data? You can hold volume down + power an in 5 seconds it will suggest wipe the data. But before that you should better try "adb shell" while your device in boot loop and root device again to fix it or "adb logcat" to find out what's broken. It will not work if you wipe your data as adb will be disabled, which is your best friend now. You are pretty close to brick.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Well it won't stay on long enough for me to try anything. My computer is recognizing it as new hardware when it boots as an Asus Android MTP Device. I have all the drivers installed so no problem there, or at least there shouldn't be. But when I attempt to use adb to "see" the connected devices by typing "adb devices" in the prompt its returning a blank:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Eric Moss>CD C:\AndroidSDK\platform-tools
C:\AndroidSDK\platform-tools>adb devices
List of devices attached
After I determined adb was not finding the device. I tried to wipe datam but no luck...this was last night. I think I'm screwed.

lordgodgeneral said:
Thats probably the problem. I don't know if the stock recovery plays well with custom roms. Did you make a nandroid after you rooted before you flashed madaco? It may be best to reflash the CWM blob and restore to as close to stock as you can before reflashing the stock recovery blob.
Click to expand...
Click to collapse
Yeah I have the nandroid backup on my computer right now and on my microSD, but it was taken before I updated the custom ROM to its latest versioun. I bought the Transformer from someone who already rooted it so I didn't have the opportunity to create a nandroid backup pre-rooting. Problem is when I boot into recovery mode all I get is a grayed out progress bar for a few seconds at most, and then the image of the exclamation point within the triangle pops up. I cant even access CWM in order to reflash it...

I guess about the only other thing you can try is to unpack the update on your micro sd card (manually apply the update), and see if rebooting into the stock recovery picks up the asus update and applies it

lordgodgeneral said:
I guess about the only other thing you can try is to unpack the update on your micro sd card (manually apply the update), and see if rebooting into the stock recovery picks up the asus update and applies it
Click to expand...
Click to collapse
Tried that too...still get the exclamation point. It's like it doesn't even recognize anything on the MicroSD.

HOw about booting into clockwork recovery from your microsd card? Then loading a rom.

thaddyusmaximus said:
HOw about booting into clockwork recovery from your microsd card? Then loading a rom.
Click to expand...
Click to collapse
With the CWM zip file on my microSD and attempting to boot into recovery, I still get the exclamation point. It's booting into the stock recovery mode instead of CWM...why? I do not know. Does it matter what file system the card is using, ie FAT, FAT32, etc.

Not sure what's going on with the boot loops.
I reset mine following steps 6-11 (what I wrote in the other thread) and had no problem. Might be something to do with the latest firmware.
The only thing I did different (and should have mentioned) was to restore the original nandroid you made right after rooting.
Not sure if it'll help but try using the 8.2.3.9 firmware. Extract and rename US_epad_user-8.2.3.9.zip to EP101_SDUPDATE.ZIP and put it in the root of your microsd. Power off the transformer and reboot. See if it applies. If it doesn't try going to recovery and see it applies there. Other than that not sure what could be done. Maybe wait for someone who knows more about Android to reply.
http://www.megaupload.com/?d=7MHBZY46
http://forum.xda-developers.com/showpost.php?p=13365642&postcount=105

I got stuck the first time I did mine too this way.
Make sure you hold down vol down + power until you see the eeepad logo then let go of power but keep holding down.
It should give you a little writing at the top to press vol up for recovery and you have 5 seconds to do it.
Otherwise it'll just sit at the exclamation point.
Let us know if that helps

jrizk07 said:
I got stuck the first time I did mine too this way.
Make sure you hold down vol down + power until you see the eeepad logo then let go of power but keep holding down.
It should give you a little writing at the top to press vol up for recovery and you have 5 seconds to do it.
Otherwise it'll just sit at the exclamation point.
Let us know if that helps
Click to expand...
Click to collapse
Yeah I get to the point where i get the writing at the top that says press vol up for recovery. I press the volume up button and get an image of a grayed out progress bar for a few seconds. That image then jumps to an image of the Android robot logo with an exclamation within a triangle next to it. I have another working transformer with me (not the one I am trying to bring back to stock), and when I boot to recovery mode I get the exact same greeting, so the unrooted one is obviously reacting in the expected manner. If I put anything on the micro sd card, such as updates, or cwm, the tablet I am attempting to unroot does not recognize it. I'm guessing because it lost root during the unrooting process...not sure though.

I'm not expert, but what I think needs to be done is this:
Take an official ASUS blob. Unpack the blob to get each specific partitions' data. Repack (if needed?) each separate partition as a blob (much like our CWM_BLOB which is just the recovery). Then, in theory, you could use 'dd' to write the partitions back to their respective partition (mmcblk0p7 appears to be /system, for example).
Flashing the ASUS zip in CWM fails on assert stuff. Using the entire blob and dd back to /dev/block/mmcblock0p4 doesn't work because you are trying to write over 500MB of data into the recovery partition which I am sure isn't that large.
Partitions:
Code:
cat /proc/partitions
major minor #blocks name
179 0 31256576 mmcblk0
179 1 524288 mmcblk0p1
179 2 542208 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 542208 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 29616640 mmcblk0p7
179 8 7772160 mmcblk1
179 9 7771136 mmcblk1p1
/proc #
In short: The asus blob contains several partitions, and needs to be split out and flashed separately.
Edit: By the way sorry, but I don't think this will help you. You would need access to 'dd' on the eeePad.

sirmx said:
I'm not expert, but what I think needs to be done is this:
Take an official ASUS blob. Unpack the blob to get each specific partitions' data. Repack (if needed?) each separate partition as a blob (much like our CWM_BLOB which is just the recovery). Then, in theory, you could use 'dd' to write the partitions back to their respective partition (mmcblk0p7 appears to be /system, for example).
Flashing the ASUS zip in CWM fails on assert stuff. Using the entire blob and dd back to /dev/block/mmcblock0p4 doesn't work because you are trying to write over 500MB of data into the recovery partition which I am sure isn't that large.
Partitions:
Code:
cat /proc/partitions
major minor #blocks name
179 0 31256576 mmcblk0
179 1 524288 mmcblk0p1
179 2 542208 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 542208 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 29616640 mmcblk0p7
179 8 7772160 mmcblk1
179 9 7771136 mmcblk1p1
/proc #
In short: The asus blob contains several partitions, and needs to be split out and flashed separately.
Edit: By the way sorry, but I don't think this will help you. You would need access to 'dd' on the eeePad.
Click to expand...
Click to collapse
Yeah I cant access DD without using ADB correct? And I am having problems with that so...This seemed a little over my head anyways. But thanks for trying!

fullthrottleenergy said:
Not sure what's going on with the boot loops.
I reset mine following steps 6-11 (what I wrote in the other thread) and had no problem. Might be something to do with the latest firmware.
The only thing I did different (and should have mentioned) was to restore the original nandroid you made right after rooting.
Not sure if it'll help but try using the 8.2.3.9 firmware. Extract and rename US_epad_user-8.2.3.9.zip to EP101_SDUPDATE.ZIP and put it in the root of your microsd. Power off the transformer and reboot. See if it applies. If it doesn't try going to recovery and see it applies there. Other than that not sure what could be done. Maybe wait for someone who knows more about Android to reply.
http://www.megaupload.com/?d=7MHBZY46
http://forum.xda-developers.com/showpost.php?p=13365642&postcount=105
Click to expand...
Click to collapse
That's seems the only option left. Theoretically, it is possible to restore using nvflash if you manage to get sbk key from Asus support, but this is completely unexplorered territory for Transformer. I recovered my GTablet this way. Try to contact Asus support?
Sent from my Transformer TF101 using Tapatalk

Looks like you still have a chance:
http://forum.xda-developers.com/showthread.php?t=1093403
Make sure you did the right thing with the sdcard update zip, check file name and extension.
Sent from my Transformer TF101 using Tapatalk

You have to dl stock fw and name it in a specific way in microsd root and use stock recovery to flash. There is a tut about unrooting in dev section
Sent from my Transformer TF101

Unbrick g2x Alternative method....(xp not needed :D) WORKS ON WIN 7

This is what worked for my phone....i'm not responsible from what happens to your phone your responsible for your own action...DO THIS AT YOUR OWN RISK! THIS METHOD doesn't require XP
OK so your phone is bricked because of the update by lg and your are stuck at the s/w screen...and The other method of flashing the KDZ file and program keeps freezing and not working even on XP ...if you haven't tried that method first you should its much easier and faster if you have and it's FAILED then hopefully this will help.
EASIEST FIX!!! This is for KDZ just encase you havn't tired this first my method is below....
Credit to bullseye69....THIS WORKs FOR WIN 7 ....so i guess you could try vista...but i'm not sure.
http://forum.xda-developers.com/showthread.php?t=1183168
READ FIRST!!!!
FOR BULLSeye69 his phone was working SO he used DIAG MODE BUTTT
IF your at s/w screen OR HAVE NO BASEBAND and NO BATTERY and NO IMEI...DO everything the same EXCEPT!!!! change DIAG to CS_emergency AND IT WILL WORK...give it a couple tries ....if it doesn't work first 2 - 3 times it's ok go to task manager and Right CLICK on the LGUPDATE tool in the process list and change set priority to HIGH and it should go through. HOPEFULLY THIS FIXS IT GOOD LUCK G2x owners
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IF the Above method Does not work after like a million tries LOL there one more at the bottom ...Scroll down
~
~
~
~
~
~
~
~
OTHER METHOD : ONLY use this IF KDZ methods did not WORK (again at ur own risk)
hopefully this method will help you....(tried to be noob friendly as possible) READ THE WHOLE AT Thing LEAST ONCE
(PS download all those files they tell you to download because you will need them and i take no credit for those programs and files just this method on how i used them)
OK my phone condition was (2.2) s/w update screen....and was able to boot into cwm(clockwork recovery but not stock) using the ONE CLICK RECOVERY (internal sd flash)
So on stock 2.2 stuck on s/w update screen
my first mission is to just get past the s/w screen since i tried flashing a nandroid backup which i downloaded and it didn't work. (ps download the nandroid file "LG-P999-V10f.rar" credit to the dude who uploaded it )
Extract it using winrar or whatever program.
Now once you have the nandroid file you should see one md5 file and 6 .img files like recovery, system, etc....
so we gotta flash each one at a time....pain in the *** but if it works you'll thank me
OK so i was thinking like this kdz flash thing didn't work for me so i want to do everything manually ...alot of work but i have a 500$ paper weight...tough to figure the language but give it a little time.
LIST OF WHAT YOU NEED
One click recovery
Drivers installed
Nandroid file
so (assuming you have all the programs downloaded and installed) take all the img files (not the md5 one) and paste them into the nvflash folder of
the one click recovery folder.
Now open command prompt (type in search cmd)
we will used Command prompt next take battery out and press and hold up AND down volume buttons together and plug in your phone
(Apx driver should be recongized if drivers are installed)
Command i found to use (again credit to who made the command)
normally command promt (cmd) it starts with "c:\user\user"
so change this to where you saved the oneclick file...(easier to save the one click and other file right on c drive not into other folders)
For example my file is save in C:\oneclick\nvflash
SO this means i saved the file in c drive, and i need acess to "nvflash" folder inside "one click" since the nvflash program is in that
folder...
So change the location to where you want to access type in
cd C:\oneclick\nvflash (this is my file location obviously)
command language
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 8 .android_secure.img
NOW UNDERSTAND THE LINE SO YOU CAN FIGURED IT OUT EASIER...i'll try to be noob friendly as possible
"nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --"
this line for you noobs out there (not trying to insult lol) is just copy paste ok BUT
the second part ""download 8 .android_secure.img""" download is standard so that's also copy that
but SEE the 8 that number is the partion number ...bascially divsions on a harddrive so the 6 img (image)
file goes in their own number...so i'll post where .img file went in which partition but you may have to play
with the number to find ur phone's particular number...i'll explain futher
SO partiton number 8 is where my android_secure.img flashed and went throught without an error
so now i'll post the command for each img file that worked for me hopefully works for your G2x
(REMEMBER!!! after each command goes through the phone will turn on to the S/w screen , Once it says SUCCESSFUL (on CMD) unplug and plug back in hold the 2 volume keys)
for the android secure img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 8 .android_secure.img
for the cache img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 9 cache.img
for the boot img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 11 boot.img
for the system img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 7 system.img
for the data img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 15 data.img
~**NOTE IT IS BROUGHT TO MY ATTENTION THAT its possible that by COPYING PASTING ADDITIONAL SPACES MAY have been enter into the line so double check there are no extra spacing because then the command line becomes useless and doesn't work~****
NOW if they show an error like NV 120000 000 or something like partition error... then the NUmbers of your partition of where
these files go are different on your phone So it's not the END OF THE WORLD just play around with the numbers they are usually
very close so if number 15 doesn't work for the data.img then try 13, 14 or 16 they should be just one or two numbers away from
mine. (sometimes if says nvflash started and nothing happens you just have to unplug and plug again holding the 2 buttons)
Trial and error is how i obtained these numbers.
once all these files are sucessful goes through do a test but putting in your battery and going into recovery or just try booting (you not suppose to be plugged in for this)
it normally if it shows LG logo and goes to another LG logo with a LOading bar at the bottom wait for it may reboot,
IF it doesn't reboot it's OK because (after the normal boot) the S/w screen doesn't show up you have SUCCESS because the nandroid file SHOULD
work.
(IF your S/w screen has not gone away YOU Might HAVE TO wipe everything using CWM(Recovery holding power and down) and i mean everything format everything for every option that
(you get in CWM (recovery) go through what i did ....but THAT's only if you cannot get rid of the s/w screen )
(and then try again from the begining REMEMBER WIPING = LOSS in BASEBAND aka calling connectivity so through CWM make a backup of your file and save to your computer you may need later)
OK so we don't need cmd (command pompt) anymore you got your s/w screen to go away.
Now use NVflash and click the "one click recovery" button
(plug in the phone again (no battery) holding 2 volume buttons) and flash CWM to INTERNAL SD (not external)
IT's the first Button on the left (you should see 3 buttons to click on )
once it goes successful you can close the window and unplug.
pop in battery reboot holding POWER AND DOWN VOLUME KEY ...KEEP HOLDING till you see ANDROID RECOVERY (has like pictures of apps falling or something)
then the menu should pop open go to the mounts and storage and then all the way at the bottom (use volume keys to go up and down) mount usb storage option
and (make sure usb plugged in now) hit power button to open STAYY!! in that menu to acess the Storage on the phone...don't exit or hit unmount
nothing will happen if you do by accient exit...just it's easier to explain this way lol
now you should see on the PC (in my computer or automatically open the drive storage for your phone) in there you should see your folders and one of them is clockworkmod
in that there should a folder called "backup" if not make one, all small letters "backup" in there copy the whole LG-p999-v10f file you extracted into the backup folder.
now on the phone (once it transfered the file) hit unmount or hit go back using power button and go back to the first menu
above the mounts and storage option there should be the "backup and restore" option ...open that and hit the restore option and
you should see the LG-p999-v10 file there and hit power on that and go down to yes option and hit open and let it run should take roughly 5 mins.
let it go till it comes to the menu again... now hit reboot system...phone should turn off...if it doesn't turn on within 2-3 mins you can turn it on
your self and android should up and running YAY!!!!
(This is for only people who did a full format when they couldn't get rid of the S/W screen)
Now i have had some battery/signal issues....Thats because i did the full wipe of everything some people may or may not have this same problem hopefully someone can post a radio file zip or something ....cyogenmod is another option but i haven't tested it yet
will post result of the battery issue later
EDIT:I have put cyanogen mod (credit to cyanogen mod guy lol) on and seemed to fix the battery reading issue.
EDIT:
IF NO BASEBAND AND NO BATTERY TRY METHOD 1 again at top of the page
KDZ in CS_emergency mode ...and if on windows 7 setup the KDz as in the link above (bulleye69) then proceed to flashing it in CS_emergency mode
HOPEFULLY THIS HELPS ALL THE REST G2x semi-bricked owners....DON"T FORGET TO HIT THE THANKS BUTTON!!!!!

kosh2thamax said:
This is what worked for my phone....i'm not responsible from what happens to your phone your responsible for your own action...DO THIS AT YOUR OWN RISK! THIS METHOD doesn't require XP
OK so your phone is bricked because of the update by lg and your are stuck at the s/w screen...and The other method of flashing the KDZ file and program keeps freezing and not working even on XP ...if you haven't tried that method first you should its much easier and faster if you have and it's FAILED then hopefully this will help.
EASIEST FIX!!!
Credit to bullseye69....THIS WORKs FOR WIN 7 ....so i guess you could try vista...but i'm not sure.
http://forum.xda-developers.com/showthread.php?t=1183168
READ FIRST!!!!
FOR BULLSeye69 his phone was working SO he used DIAG MODE BUTTT
IF your at s/w screen OR HAVE NO BASEBAND and NO BATTERY and NO IMEI...DO everything the same EXCEPT!!!! change DIAG to CS_emergency AND IT WILL WORK...give it a couple tries ....if it doesn't work first 2 - 3 times it's ok go to task manager and Right CLICK on the LGUPDATE tool in the process list and change set priority to HIGH and it should go through. HOPEFULLY THIS FIXS IT GOOD LUCK G2x owners
IF the Above method Does not work after like a million tries LOL there one more at the bottom ...Scroll down
OTHER METHOD : ONLY use this IF KDZ methods did not WORK (again at ur own risk)
hopefully this method will help you....(tried to be noob friendly as possible) READ THE WHOLE AT Thing LEAST ONCE
(PS download all those files they tell you to download because you will need them and i take no credit for those programs and files just this method on how i used them)
OK my phone condition was (2.2) s/w update screen....and was able to boot into cwm(clockwork recovery but not stock) using the ONE CLICK RECOVERY (internal sd flash)
So on stock 2.2 stuck on s/w update screen
my first mission is to just get past the s/w screen since i tried flashing a nandroid backup which i downloaded and it didn't work. (ps download the nandroid file "LG-P999-V10f.rar" credit to the dude who uploaded it )
Extract it using winrar or whatever program.
Now once you have the nandroid file you should see one md5 file and 6 .img files like recovery, system, etc....
so we gotta flash each one at a time....pain in the *** but if it works you'll thank me
OK so i was thinking like this kdz flash thing didn't work for me so i want to do everything manually ...alot of work but i have a 500$ paper weight...tough to figure the language but give it a little time.
LIST OF WHAT YOU NEED
One click recovery
Drivers installed
Nandroid file
so (assuming you have all the programs downloaded and installed) take all the img files (not the md5 one) and paste them into the nvflash folder of
the one click recovery folder.
Now open command prompt (type in search cmd)
we will used Command prompt next take battery out and press and hold up AND down volume buttons together and plug in your phone
(Apx driver should be recongized if drivers are installed)
Command i found to use (again credit to who made the command)
normally command promt (cmd) it starts with "c:\user\user"
so change this to where you saved the oneclick file...(easier to save the one click and other file right on c drive not into other folders)
For example my file is save in C:\oneclick\nvflash
SO this means i saved the file in c drive, and i need acess to "nvflash" folder inside "one click" since the nvflash program is in that
folder...
So change the location to where you want to access type in
cd C:\oneclick\nvflash (this is my file location obviously)
command language
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 8 .android_secure.img
NOW UNDERSTAND THE LINE SO YOU CAN FIGURED IT OUT EASIER...i'll try to be noob friendly as possible
"nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --"
this line for you noobs out there (not trying to insult lol) is just copy paste ok BUT
the second part ""download 8 .android_secure.img""" download is standard so that's also copy that
but SEE the 8 that number is the partion number ...bascially divsions on a harddrive so the 6 img (image)
file goes in their own number...so i'll post where .img file went in which partition but you may have to play
with the number to find ur phone's particular number...i'll explain futher
SO partiton number 8 is where my android_secure.img flashed and went throught without an error
so now i'll post the command for each img file that worked for me hopefully works for your G2x
(REMEMBER!!! after each command goes through the phone will turn on to the S/w screen , Once it says SUCCESSFUL (on CMD) unplug and plug back in hold the 2 volume keys)
for the android secure img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 8 .android_secure.img
for the cache img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 9 cache.img
for the boot img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 11 boot.img
for the system img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 7 system.img
for the data img file:
nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 15 data.img
NOW if they show an error like NV 120000 000 or something like partition error... then the NUmbers of your partition of where
these files go are different on your phone So it's not the END OF THE WORLD just play around with the numbers they are usually
very close so if number 15 doesn't work for the data.img then try 13, 14 or 16 they should be just one or two numbers away from
mine. (sometimes if says nvflash started and nothing happens you just have to unplug and plug again holding the 2 buttons)
Trial and error is how i obtained these numbers.
once all these files are sucessful goes through do a test but putting in your battery and going into recovery or just try booting (you not suppose to be plugged in for this)
it normally if it shows LG logo and goes to another LG logo with a LOading bar at the bottom wait for it may reboot,
IF it doesn't reboot it's OK because (after the normal boot) the S/w screen doesn't show up you have SUCCESS because the nandroid file SHOULD
work.
(IF your S/w screen has not gone away YOU Might HAVE TO wipe everything using CWM(Recovery holding power and down) and i mean everything format everything for every option that
(you get in CWM (recovery) go through what i did ....but THAT's only if you cannot get rid of the s/w screen )
(and then try again from the begining REMEMBER WIPING = LOSS in BASEBAND aka calling connectivity so through CWM make a backup of your file and save to your computer you may need later)
OK so we don't need cmd (command pompt) anymore you got your s/w screen to go away.
Now use NVflash and click the "one click recovery" button
(plug in the phone again (no battery) holding 2 volume buttons) and flash CWM to INTERNAL SD (not external)
IT's the first Button on the left (you should see 3 buttons to click on )
once it goes successful you can close the window and unplug.
pop in battery reboot holding POWER AND DOWN VOLUME KEY ...KEEP HOLDING till you see ANDROID RECOVERY (has like pictures of apps falling or something)
then the menu should pop open go to the mounts and storage and then all the way at the bottom (use volume keys to go up and down) mount usb storage option
and (make sure usb plugged in now) hit power button to open STAYY!! in that menu to acess the Storage on the phone...don't exit or hit unmount
nothing will happen if you do by accient exit...just it's easier to explain this way lol
now you should see on the PC (in my computer or automatically open the drive storage for your phone) in there you should see your folders and one of them is clockworkmod
in that there should a folder called "backup" if not make one, all small letters "backup" in there copy the whole LG-p999-v10f file you extracted into the backup folder.
now on the phone (once it transfered the file) hit unmount or hit go back using power button and go back to the first menu
above the mounts and storage option there should be the "backup and restore" option ...open that and hit the restore option and
you should see the LG-p999-v10 file there and hit power on that and go down to yes option and hit open and let it run should take roughly 5 mins.
let it go till it comes to the menu again... now hit reboot system...phone should turn off...if it doesn't turn on within 2-3 mins you can turn it on
your self and android should up and running YAY!!!!
Now i have had some battery/signal issues....Thats because i did the full wipe of everything some people may or may not have this same problem hopefully someone can post a radio file zip or something ....cyogenmod is another option but i haven't tested it yet
will post result of the battery issue later
EDIT:I have put cyanogen mod (credit to cyanogen mod guy lol) on and seemed to fix the battery reading issue.
EDIT:
IF NO BASEBAND AND NO BATTERY TRY METHOD 1 again at top of the page
HOPEFULLY THIS HELPS ALL THE REST G2x semi-bricked owners....
Click to expand...
Click to collapse
Thanks. it worked!!!!!!!!!!!!!!!!!!!!!!!!!!!

@ rapswiller no problem glad it worked

you my friend, are quite awesome indeed, this is the only thing that fixed my phone after nothing else did, so thanks... like really... you are badass for knowing this stuff
+1 awesomeness

saaif88 said:
you my friend, are quite awesome indeed, this is the only thing that fixed my phone after nothing else did, so thanks... like really... you are badass for knowing this stuff
+1 awesomeness
Click to expand...
Click to collapse
Hey no problem.... took me days to figure this out so i thought people can save some time and give this a shot if all else fails LOL Glad it worked and fixed your phone

I'm about try this method as i bricked my g2x after attempting to put cyanogenmod on it.. i got everything ready except nandoid. where can i find this file?
-done my phones working again im crying right now

omg omg omg i will love you forever kosh2thamax I can't be any happier right now! God bless you.

dokjon said:
omg omg omg i will love you forever kosh2thamax I can't be any happier right now! God bless you.
Click to expand...
Click to collapse
LOL thanks for the love ...happy it worked

I tried the command method cause KDZ keep force closing halfway and after that i flashed clockworkmod. When i restarted it still has the stock recovery, i got rid of the s/w but the problem now is that it gets stuck on lg logo with blue line and the menu buttons light up. I tried going into apx mode and s/w but the phone doesn't, it boots to the lg logo and the the blue lines.
Is there's any way to fix this?

Check the rom for recovery thread in Dev section, it will nvflash your phone to 2.3.3 gb rom. It will basically fix any brick and is our saving grace, huge props to iluha for creating it!
Sent from my LG-P999 using xda premium

Use --resume
it keeps using the running bootloader on your phone....

lilizblack said:
I tried the command method cause KDZ keep force closing halfway and after that i flashed clockworkmod. When i restarted it still has the stock recovery, i got rid of the s/w but the problem now is that it gets stuck on lg logo with blue line and the menu buttons light up. I tried going into apx mode and s/w but the phone doesn't, it boots to the lg logo and the the blue lines.
Is there's any way to fix this?
Click to expand...
Click to collapse
ok so you got passed the S/w screen at boot from my understanding and assuming that you manually flashed each file into it's partition...so now you used NVflash to flash and get clockworkmod recovery ? ok what happens when you pressed and held both the power and volume down what do see rather?

bigmixxx said:
it keeps using the running bootloader on your phone....
Click to expand...
Click to collapse
Ummm when does it say this exactly? like when manually flashing?

What did I do wrong? I tried the kdz method but it never worked after many, many, tries. My phone was stuck on the S/W Upgrade screen so I have to use the 2nd method.
I pressed the volume up/down buttons and put the usb cable in, waited for the driver to load (NVIDIA USB Boot-recovery driver for Mobile devices), let go of the two buttons, and I ran the first line "nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin--" (without the quotes) and the cmd window stuck at "Nvflash started" but didn't budge and the S/W Upgrade screen didn't appear so I pulled out the USB cable and in the command window it stated "uid read failed"
Here's the cmd window info:
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>nvflash --bct 1108_Hynix_5
12MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin--
Nvflash started
uid read failed
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
Now it doesn't boot at all, no S/W Upgrade appears, nada. *Update I got the S/W Upgrade screen back after reinstalling CWM.

Core Memory said:
What did I do wrong? I tried the kdz method but it never worked after many, many, tries. My phone was stuck on the S/W Upgrade screen so I have to use the 2nd method.
I pressed the volume up/down buttons and put the usb cable in, waited for the driver to load (NVIDIA USB Boot-recovery driver for Mobile devices), let go of the two buttons, and I ran the first line "nvflash --bct 1108_Hynix_512MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin--" (without the quotes) and the cmd window stuck at "Nvflash started" but didn't budge and the S/W Upgrade screen didn't appear so I pulled out the USB cable and in the command window it stated "uid read failed"
Here's the cmd window info:
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>nvflash --bct 1108_Hynix_5
12MB_H8TBR00U0MLR0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin--
Nvflash started
uid read failed
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
C:\Users\Toshiba M4001050\Desktop\WIND and T-Mobile LG Optimus 2X (T-Mobile G2X)
LG-P999\One-Click-G2x-recovery-flasher-09-23\NVFlash>
Now it doesn't boot at all, no S/W Upgrade appears, nada. *Update I got the S/W Upgrade screen back after reinstalling CWM.
Click to expand...
Click to collapse
Ummmm usually the if it says that it started and nothing happens you just do it again (unplug it & close program (battery is not in) press up/down volume buttons plug it in ..then thingy pops up as verified let go...and open program and try) now I couldn't help but notice your file name...but just make sure your phone is LG G2x not LG optimus 2x.... right?

d12unk13astard said:
Check the rom for recovery thread in Dev section, it will nvflash your phone to 2.3.3 gb rom. It will basically fix any brick and is our saving grace, huge props to iluha for creating it!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
can u post the link plz

Awesome...
I registered at xda just to post that this is the best solution ever. Thanks a lot OP!
I'm still stuck at a boot loop but I'll figure it out from there!

Gryncc said:
can u post the link plz
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using xda premium

NP hopefully the manual single file flashing with the backup restore should get you out of the loop

this did not work still no baseband and no signal plz help plz

[Q] broke asus tf101 eee pad transformer

Hi.
It's been some time since i tried fixing my Asus Transformer...
The problem is : If it has battery life. It boot's and gets stuck on the first screen.
With the logo "eee pad" .
If i turn it off, it automaticly reboots and gets stuck in the same screen.
If i try to get into recovery mode.
Vol down, Powerup... and the vol up , i can see the few line's of code , saying it will boot into recovery mode.
but while trying to start recovery mode the icon changes to a fallen android and an "! triangle above it
I've been looking around forums evrywhere but i cant find a solution for my exact problem.
can anyone help?

Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.

Lethe6 said:
Quickly, with the info you provided, I would think your firmware or storage may be damaged.
Can you access ADB? Sometimes you can while it boots, even if it doesn't fully boot. That would allow you to check logs and back up data.
Can you access APX? It has nothing to do with Android, it's a part of the device made by Asus to allow you to "inject" a firmware inside the device while it's in "brick" state.
If you can access ADB, you can "pull" the files you want from the device to your computer. You can see information on ADB here. Basically you install the package from google and connect the device to your computer, then run a set of commands.
If you can access APX (chances are you can unless there's hardware damage), then EasyFlasher can push a stock firmware back to the device. This will wipe your device 100% back to stock and you will lose all your files.
Click to expand...
Click to collapse
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?

DarkCloud98 said:
With my Ubuntu, if i do the command ./adb device
Then i can see a number. So the device is connected i think.
I am not sure if i can access APX, i do not yet how to test tis yet.
Is there an easy way to see / test this in ubuntu ?
Click to expand...
Click to collapse
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
http://www.xdafileserver.nl/Files/A...OMS/ICS .27/NVFLASH_ICS_9.2.1.27_WW_NOROOT.7z

*Detection* said:
APX mode is just a black screen, but your PC will install drivers and see the device when you enter that mode
Hold Volume up & Power until the USB connect sound appears, now you are in APX mode - there will be nothing on the screen of the transformer until you are flashing a new ROM maybe
What serial number is your TF ?
NVFlash is the quickest way to get back to 100% working stock
Click to expand...
Click to collapse
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926

DarkCloud98 said:
I tried the "hold volume up & power" when connected to my Windows PC.
I did see the "usb connection" and heard the sound.
But it says the installation failed.
my serial number of my TF is B60KAS032926
Click to expand...
Click to collapse
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin

*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Click to expand...
Click to collapse
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash

DarkCloud98 said:
Ok, i'l try that right now.
The APX driver is installed now.
i'l try NVFlash
Click to expand...
Click to collapse
I edited my post with quick instructions
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin

*Detection* said:
NVFlash is supported for your serial number, make sure you are running the download.bat as Administrator (Right click > Run as Admin)
Remove any other USB devices from the PC (apart from your keyboard and mouse)
Connect the TF to the PC > Power off the TF > Hold Vol up and Power until USB connects, run download.bat as Admin
Click to expand...
Click to collapse
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server

DarkCloud98 said:
When do i know if it's done. And is there any other thing required?
I used the NVFLASH_ICS_9.2.1.27_WW_NOROOT
and running download.bat with admin its starts a terminal.
after this is done, i see 2 lines of information on my Asus transformer. only chip Uid and Nv3P server
Click to expand...
Click to collapse
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF

*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help

DarkCloud98 said:
ok sweet, thx !
i hope it'l boot soon
after that...i'l need to root it again i think. ...but thats for later.
Now it would be awsome to let it work again.
thx again for the help
Click to expand...
Click to collapse
You could flash the pre-rooted versions too although I think it's easy enough to root yourself these days
This is the XDA Fileserver for different ROMs if you need them
http://www.xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)
I was just reading someone else who had the same display stuck on their TF while trying to use NVFlash and they said re-downloading the ROM and trying it again fixed it
So if this fails for some reason, try another NVFlash ROM from the XDA Server

*Detection* said:
That's good, its working, you can watch command prompt I think if it stays open to watch the progress as it sends the files across, can't remember exactly, but the TF should reboot on its own when its done
It can take 10mins or more iirc so just leave it to do its thing, then it shoot boot up
The only thing I remember having to do, was once it had booted, and I manually reboot the TF, it would hang on a black screen (Only that first reboot though) holding power for around 30 seconds, then powering on normally fixed it and it never does it again, just that first boot
Might not even happen on yours, could be a fault on my TF
Click to expand...
Click to collapse
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?

DarkCloud98 said:
seems to still do nothing more.
sure i'm not missing the something i should add to the NVFLASH ?
Click to expand...
Click to collapse
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
http://forum.xda-developers.com/showthread.php?t=1123429

*Detection* said:
NVFlash contains everything you need, ROM and NVFlash tools to install it to the TF, I've used that exact same download on mine so it should be working
Did you have any progress showing in command prompt ?
It should say something like
Deleting partition
1
2
3
4
5 etc
Then creating partiton
1
2
3
4
5etc
Then sending boot.img
sending system.img <<<<< This one takes a while
Try it a few times until you start seeing progress in CMD, if you don't see it after a few minute, cancel it again try again
There is also a Linux version of NVFlash you could try
Click to expand...
Click to collapse
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?

DarkCloud98 said:
i see =
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
/ 786432/1454712 bytes sent
and when it's done , the cmd closes and thats about it.
so'l best try it a few times?
Click to expand...
Click to collapse
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
http://www.portableandroid.co.uk/androidDL/new Windows.zip

*Detection* said:
Did the TF not reboot on its own ?
Have you tried booting it manually by holding power for 30 seconds then powering on normally ?
That all looks like its working fine, sending the files across
EDIT - I`ll upload an older version that I have saved, it has a different file structure and uses .img instead of .blob
EDIT - Try this NVFlash
Click to expand...
Click to collapse
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
EDIT: And the other NvFlash version you linked me, does the same...after it being sent, the CMD closes and thats it

DarkCloud98 said:
I Just Tried the linux NvFlash.
and the boodloader sending = send succesfully
but the next step it says : "File not found: recovery.img"
Failed executing command .... NvError 0x4
Command failure: create failed.
I'm nog going to try the last NVversion you linked with my Windows PC
Click to expand...
Click to collapse
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way

*Detection* said:
I think maybe the linux version is the older .img version, and the files are .blob so it can't find anything
The one I linked you is the .img windows version, hopefully you'll have more luck with that
If not, put all the .img files into the linux folder and try it that way
Click to expand...
Click to collapse
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!

DarkCloud98 said:
It worked !!!
By using the linux download.sh but by adding all the files in the from the windows folder that were missing.
Thank you very much !!!
Click to expand...
Click to collapse
Great news! Linux vs Linux did the trick
How long have you been without your TF until now? It'll be like having a new toy again I would imagine