Related
Hello everybody,
Before telling you about my issue, i should mention that i am a complete newbie regarding flashing kernels. This was my first try, and it didn't work out too well.
I needed to test the USB OTG/Host Functionality for a project at work, and i read that it was possible to enable it on the Nexus S by flashing a custom kernel (kernel_usbhost_build5_icsnexuss from sztupy). It's probably worth mentioning that prior to this i updated the phone to Android 4.0.3.
So i started this morning by rooting it, unlocking the bootloader and installing CWM.
At that point i realized that the recovery mode wasn't accessible : the graphics of the droid with an open belly appears for half a second, and then it gives me the black screen treatment for about a minute before rebooting.
However since there are other ways to flash kernels, i figured i could do without recovery so i didn't look more into it.
I then flashed the kernel using fastboot with this command :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot flash:raw boot H:\data\Downloads\kernel_usbhost_build5_icsnexuss\kernel\zImage
creating boot image...
creating boot image - 3446784 bytes
sending 'boot' (3366 KB)...
OKAY [ 0.422s]
writing 'boot'...
OKAY [ 0.500s]
finished. total time: 0.922s
From the trace i figured that all went well, but when i reboot it stays blocked on the splash screen with the Google logo. Since then i tried flashing several other kernels, without any success. Also tried to flash an update.zip (both ICS and GB) over fastboot but i get this error :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot update H:\data\Downloads\upd
ate.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
So to sum it up i now only have access to the bootloader, without recovery mode.
Before you all jump on me, i know what i did is bad habits (i should have tested the kernel before flashing it), i did it in a hurry without checking i had all sufficient knowledge, and to be honest i would probably have been more careful if was doing it on my personal device.
Truth is now i'm really desperate because i turned my company issued phone into a brick and don't have the slightest idea what to do about it...
Is there any guru out there who knows how i could get out of this ?
Thanks a lot !
Download clockworkmod recovery and use fastboot to flash it.
Fastboot flash recovery yourfilename.img
Enter recovery and mounts and storage and mount USB storage
Transfer the kernel you want to your SD card. The one you flashes isn't a kernel I'm almost sure.
Try a different one.
Then transfer a rom to your SD card.
Factory reset/full wipe, then go to mounts and storage and format everything except your sdcard.
DO NOT FORMAT YOUR SD CARD!!!
Once that is done go to install zip from sdcard and flash the rom and then the kernel and reboot. Should be fine then. Keep me posted.
..
Election Day said:
The image you need would be this ClockworkMod img. Save it somewhere, cd to the sdk/platform-tools/ directory and then do:
Code:
fastboot flash recovery /path/to/saved/file/recovery-clockwork-5.0.2.0-crespo.img
Just drag and drop the file in your terminal, after typing the space after "recovery".
Furthermore, what nodstuff said.
Click to expand...
Click to collapse
Ha ha oops! Forgot that part!
I usually just cd to the one where I have recovery saved!
..
Thanks a lot for answering so quickly !
I'll give it a try on Monday, let you know how it goes.
Election Day said:
Yes, you can also do that, of course. In that case you'd have to provide the full path for fastboot. Or maybe you don't have to on Windows? I don't really use that operating system to be honest.
In that case it would be something like:
Code:
C:\Program Files\Android\android-sdk\tools\fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Looking at OP's quotes that is probably the most logical way in this case, you're right.
Click to expand...
Click to collapse
No I just cd to downloads (where recovery file would be) in terminal, type: fastboot flash recovery xxxxxx img
And that's it.
I set the path to fast boot and adb in environmental variables in device manager.
Maybe that's why.
..
Just tried out your tips, worked like a charm !
However I had to wipe everything twice before it would let me update to 4.0.3, I would get this weird error :
file_getprop: failed to stat "/system/build.prop": No such file or directory
Anyway now I'm back on ICS and, following your advice, i found another kernel to flash : Matr1x. No problem with this one, now I can test USB OTG.
Thanks again, you guys rule !
Ok, so you want to return to GB from ICS, right?
Well I have written a script for AT&T users to get back to GB 2.3.5 from ICS with the fxz patched with the same patch the Chinese forum had used.
It is very simple just download the correct file there is a version for windows users in a batch file, and a shell script for the Linux and Mac users.
This has been tested and will not brick your phone. We have several confirmed cases that this works Even one of our devs soft bricked on ICS today and was able to get back to 2.3.5 from this.
--UPDATE 10/18/2012--
Do NOT use this if you are on leak 2/the soak/the final OTA!!! You will hard brick!!!
This ONLY works for leak 1, that is dated early July in the build date.
--UPDATE 09/26/2012--
Here are the 2.3.6 fxz scripts as well, that alteredikeness put together when the 2nd leak came out, go thank alteredlikeness for these:
Windows:
Download: http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_backto236_win.zip
MD5sum: a937d39d52572843aecab25e1682cda8
Linux/Mac:
Download: http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/a2_backto236_lm.zip
MD5sum: ffc4ebd245e68ad0ce5a9e40d9ba751b
--END UPDATE--
2.3.5 Files:
Windows:
You will download the following zip file:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/a2_return_to_gb_win.zip
MD5sum: 85dd75fc711a723837d927c6de6ca1fa
Then unzip the whole thing, do not drag and drop the files, there is an A2_go_back_win directory with all the files in it... extract this directory to either your desktop or C:\ BE VERY CAREFUL YOU DO NOT DRAG JUST THE FILES TO C:\ but you extract the WHOLE directory there.
Then go to your command line (cmd) and cd to either your Desktop or C:\A2_go_back_win then run the restore-to-gb.bat file
Code:
C:\ > cd A2_go_back_win
C:\A2_go_back_win > restore-to-gb.bat
Linux and Mac:
You will download the following zip file:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/a2_return_to_gb_lm.zip
MD5sum: 58b4c47c02e9ad0a379ca8cc5734687a
Unzip the file and go to the command line and cd to where you unzipped the file to and cd into the A2_go_back directory. Then run the return_to_gb.sh shell script
The following is an example of how to run this. The directory I use is just and example, please cd to the correct directory you extracted the zip to on your machine.
Code:
$ cd ~/Downloads/A2_go_back
$ ./restore_to_gb.sh
This will ONLY work if you are on ICS, I will get something for 2.3.6 and 2.3.5 from, once you have been on ICS, those are "special" cases so PLEASE do not attempt that until further notice.
Thanks to the following users:
jerrycrystal, [email protected], mntlion, KEB64, leifmagnuson, seraphielx, ri4naire, Fall of Enosis, jspugh, rdavisct, cogeary, JRW 28, alteredlikeness, a special thanks to dicksteele.
If I forgot you please PM me, all of those guys deserve for you to hit their thanks button for either testing, or getting the needed files, or other support.
One last thing, if you brick or soft brick I am not responsible, you hacked your phone and made the choice freely, to do so.
Now upward and onward to more android development.
Reserved
jimbridgman said:
Ok, so you want to return to GB from ICS, right?
Well I have written a script for AT&T users to get back to GB 2.3.5 from ICS with the fxz patched with the same patch the Chinese forum had used.
It is very simple just download the correct file there is a version for windows users in a batch file, and shell script for the Linux and Mac users.
This has been tested and will not brick your phone. We have several confirmed cases that this works Even one of our devs soft bricked on ICS today and was able to get back to 2.3.5 from this.
Windows:
You will download the following zip file:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/a2_return_to_gb_win.zip
MD5sum: 85dd75fc711a723837d927c6de6ca1fa
Then unzip the whole thing, do not drag and drop the files, there is an A2_go_back_win directory with all the files in it... extract this directory to either you desktop or C:\ BE VERY CAREFUL YOU DO NOT DRAG JUST THE FILES TO C:\ but you extract the WHOLE directory there.
Then go t your command line (cmd) and cd to either your Desktop or C:\A2_go_back_win then run the restore-to-gb.bat file
Code:
C:\ > cd A2_go_back_win
C:\A2_go_back_win > restore-to-to-gb.bat
Linux and Mac:
You will download the following zip file:
http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/a2_return_to_gb_lm.zip
MD5sum: 58b4c47c02e9ad0a379ca8cc5734687a
unzip the file and go to the command line and cd to where you unzipped the file to and cd into the A2_go_back directory. Then run the return_to_gb.sh shell script
The following is an example of how to run this the directory I use is just and example, please cd to the correct directory you extracted the zip to on your machine.
Code:
$ cd ~/Downloads/A2_go_back
$ ./restore_to_gb.sh
This will ONLY work if you are on ICS, I will get something for 2.3.6 and 2.3.5 from once you have been on ICS, those are "special" cases so PLEASE do not attempt that until further notice.
Thanks to the following users:
jerrycrystal, [email protected], mntlion, KEB64, leifmagnuson, seraphielx, ri4naire, Fall of Enosis, jspugh, rdavisct, cogeary, JRW 28, alteredlikeness, a special thanks to dicksteele.
If I forgot you please PM me, all those guys deserve for you hit their thanks button for either testing getting the needed files or other support.
One last thing, if you brick or soft brick I am not responsible, you hacked your phone and made the choice freely, to do so.
Now upward and onward to more android development.
Click to expand...
Click to collapse
Thanks a lot man for all the hard work you have put on this, it's really appreciated. :good:
not working for me this is what I get
after the flash it sits on the red m and never boots
Checking for phone...
0146DDCC09011007 fastboot
If your phone serial did not show up then exit this,
reconnect your phone, and try again!
If you did see the serial then this will continue
Waiting; if you want to cancel press c (Ctrl+C)
Press any key to continue
Press any key to continue . . .
Allowing bootloader flashing
sending 'mbm' (256 KB)... OKAY [ 0.032s]
writing 'mbm'... OKAY [ 0.470s]
Flashing bootloader mbm.bin
sending 'mbm' (256 KB)... OKAY [ 0.242s]
writing 'mbm'... OKAY [ 0.464s]
Rebooting into bootloader
rebooting into bootloader... OKAY [ 0.281s]
Flashing cdt.bin
sending 'cdt.bin' (16 KB)... FAILED (command write failed (No such file or
directory))
Erasing userdata
erasing 'userdata'... FAILED (command write failed (No such file or
directory))
Erasing cache
erasing 'cache'... FAILED (command write failed (No such file or
directory))
Flashing lbl
sending 'lbl' (16 KB)... FAILED (command write failed (No such file or
directory))
Flashing logo.bin
sending 'logo.bin' (854 KB)... FAILED (command write failed (No such file or
directory))
Flashing ebr
sending 'ebr' (16 KB)... FAILED (command write failed (No such file or
directory))
Flashing mbr
< waiting for device >
sending 'mbr' (16 KB)... OKAY [ 0.010s]
writing 'mbr'... OKAY [ 0.469s]
flashing device_tree.bin
sending 'devtree' (512 KB)... OKAY [ 0.351s]
writing 'devtree'... OKAY [ 0.519s]
Flashing System
sending 'system' (262144 KB)... OKAY [ 24.863s]
writing 'system'... OKAY [ 29.543s]
sending 'system' (229120 KB)... OKAY [ 21.285s]
writing 'system'... OKAY [ 25.757s]
Flashing Boot image
sending 'boot' (8192 KB)... OKAY [ 0.779s]
writing 'boot'... OKAY [ 1.408s]
flashing recovery
sending 'recovery' (9216 KB)... OKAY [ 1.120s]
writing 'recovery'... OKAY [ 1.833s]
Flashing Radio
sending 'radio' (12080 KB)... OKAY [ 1.362s]
writing 'radio'... OKAY [ 1.467s]
Flashing cdrom
sending 'cdrom' (12032 KB)... OKAY [ 1.357s]
writing 'cdrom'... INFOPreflash validation failure
FAILED (remote: )
Flashing preinstall
sending 'preinstall' (262144 KB)... OKAY [ 23.968s]
writing 'preinstall'... OKAY [ 29.349s]
sending 'preinstall' (20480 KB)... OKAY [ 1.945s]
writing 'preinstall'... OKAY [ 1.893s]
Flashing webtop, This will take a LONG time, be patient
sending 'webtop' (262144 KB)...
OK, now that we have a way back, is there any reason to do it for those of us on scv7?
when the ota comes out im sure the development will go crazy.
is this only useful for those that want to have the "official" update? a backup and boot menu should fix most issues with a soft brick right?
thank you for all the time and effort that everyone have put into this!!!
Thanks a lot jim And thanks a lot "Chinese Guy" ^_^
Got few questions :
1.Only At n T users ? I guess thats coz is that the only leak ?
2.Will this work only on ICS leak or will work on SC v7 too ?
3. Back to 2.3.5 and the 2.3.6 OTA can be done as usual ?
regards.
Archmag3 said:
Thanks a lot jim And thanks a lot "Chinese Guy" ^_^
Got few questions :
1.Only At n T users ? I guess thats coz is that the only leak ?
2.Will this work only on ICS leak or will work on SC v7 too ?
3. Back to 2.3.5 and the 2.3.6 OTA can be done as usual ?
regards.
Click to expand...
Click to collapse
1. Yes it is for AT&T users. Jim says that in the first line of the the post.
2. Yes, it should work for SC v7 also as it is based on the same firmware (someone can correct me if I am wrong on this)
3. Yes, I know this for sure, cause I tested it, and I OTA'd to 2.3.6 no problem. :good:
I used the china fix and flashed with rsd with out any issues game back on!
seraphielx said:
I used the china fix and flashed with rsd with out any issues game back on!
Click to expand...
Click to collapse
Cool.. sorry you had issues. Not sure what happened. Glad you got back up and running.
Sent from my SAMSUNG-SGH-I747 using xda premium
For anybody who runs this, if it doesn't go through the first time, just run it again. Its a great utility.
Sent from my MB865 using xda premium
Hey Jim, do you have a script for 2.3.6 to 2.3.5
Tooooooo laaaatttteeeee for me ....
Hope all of you guys will be happy with this .............
Can I get a confidence factor on when the ICS OTA is released that those of us that are on the leak, then return to 2.3.6 using this script, will be alright, even regarding that one file that is ignored? As I said in another thread, I am patiently waiting for the OTA to happen before I go back from the leak, but I want to know how confident the devs feel that the storm is over and its safe to come out from our rocks.
For the record, I am running the leak, rooted, no other build.prop mods or scv7 or anything, about as 'stock' as it can be.
okachowwa said:
Hey Jim, do you have a script for 2.3.6 to 2.3.5
Click to expand...
Click to collapse
just 2.3.6 to 2.3.5, or did you EVER install the ICS leak?
If you did not install the ICS leak, then yes I have a script that this one was ripped from, that I have already completed, and been through beta testing here on the board. If you EVER installed ICS, I do not have a script to get you from 2.3.6 to 2.3.5, just yet, but I am doing some testing for that.
If you want my a2_all_in_one script let me know through PM, and I will reply to you with it.
Don't everyone PM me asking for it. It will be released to everyone very soon, and I will have an option in it to include the script posted in this thread as well, in the near future and before I release to everyone
jimbridgman said:
Cool.. sorry you had issues. Not sure what happened. Glad you got back up and running.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
who knows my machines hate me haha just waiting for the push now
jimbridgman said:
just 2.3.6 to 2.3.5, or did you EVER install the ICS leak?
If you did not install the ICS leak, then yes I have a script that this one was ripped from, that I have already completed, and been through beta testing here on the board. If you EVER installed ICS, I do not have a script to get you from 2.3.6 to 2.3.5, just yet, but I am doing some testing for that.
If you want my a2_all_in_one script let me know through PM, and I will reply to you with it.
Don't everyone PM me asking for it. It will be released to everyone very soon, and I will have an option in it to include the script posted in this thread as well, in the near future and before I release to everyone
Click to expand...
Click to collapse
Jim, correct me if I'm wrong, but (assuming they have installed the ICS leak) could they just go from 2.3.6 to the leak and then use your script again to get back to 2.3.5? I know that's a round-a-bout way. I'm also confirming this for my own interest: If you've already installed leak, but got your way back to 2.3.5 using your script and then ota to 2.3.6, you would have to go the route of installing the leak again in order to get back to stock 2.3.5, right? Otherwise, you would just have to wait for the new script? My apologies if this is obvious...
CapnPez said:
Jim, correct me if I'm wrong, but (assuming they have installed the ICS leak) could they just go from 2.3.6 to the leak and then use your script again to get back to 2.3.5? I know that's a round-a-bout way. I'm also confirming this for my own interest: If you've already installed leak, but got your way back to 2.3.5 using your script and then ota to 2.3.6, you would have to go the route of installing the leak again in order to get back to stock 2.3.5, right? Otherwise, you would just have to wait for the new script? My apologies if this is obvious...
Click to expand...
Click to collapse
Yes, and yes that is a round about way of doing it. I would like to make it easier. I have gone from 2.3.6 to 2.3.5 myself using a "special" patched fxz to do so. But for now until I get the script all worked out, that is an option be it a painful one.
Jim
After flashing this, what BL will we have? 0A.65 or 0A.72?
CapnPez said:
Jim, correct me if I'm wrong, but (assuming they have installed the ICS leak) could they just go from 2.3.6 to the leak and then use your script again to get back to 2.3.5? I know that's a round-a-bout way. I'm also confirming this for my own interest: If you've already installed leak, but got your way back to 2.3.5 using your script and then ota to 2.3.6, you would have to go the route of installing the leak again in order to get back to stock 2.3.5, right? Otherwise, you would just have to wait for the new script? My apologies if this is obvious...
Click to expand...
Click to collapse
The only problem with that is that you can't mod 2.3.6 ie. Install bootstrap because then you wkbt be able to update to ICS to re FKZ back to 2.3.5
Sent from my MB865 using xda app-developers app
farshad525hou said:
The only problem with that is that you can't mod 2.3.6 ie. Install bootstrap because then you wkbt be able to update to ICS to re FKZ back to 2.3.5
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
I was under the impression that you didn't need bootstrap to install the leak ics. I thought it was stock recovery...
Of course, since I still haven't left 2.3.6 yet, I can't speak from any experience . If you're correct, wouldn't that mean people won't be able to get back to the leak if they've returned to 2.3.5 using the script (or am I mis-interpreting?)? I had assumed that with Jim's script people could go 4.0.4 to 2.3.5, then ota to 2.3.6, then stock recovery to 4.0.4 and repeat ad infinitum?
This is a general users guide to unbrick your Transformer tablet.
This guide will help you if your Asus tablet will only boot into recovery
and the command
Code:
adb reboot-bootloader
does not work to get you booted back to bootloader screen ..
If the above command works then skip to the first fastboot command ..
WHAT YOU NEED
An Asus tablet that will only boot into recovery …
Woking adb and fastboot on your PC
Windows drivers (if using Windows)
A fully charged tablet
Asus data cable
Stock firmware blob (from Asus's web site, make sure you get the right one)
_that's bootit.ko (unzipped and placed with fastboot.exe)
Downloads
Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR TRANSFORMER TABLET
click me
_that's bootit.ko----click me
INSTRUCTIONS
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to the same folder as your fastboot.exe or if in linux to your home folder
Unzip the bootit.ko and place it wth the above blob file.
Let start with this command to make sure that your PC can see your table as an ADB device in recovery
Code:
adb devices
OUTPUT
Code:
[email protected] ~ $ adb devices
List of devices attached
015c7d7a445c260c recovery
Then lets push the bootit.ko to the root of the device like this
Code:
adb push bootit.ko /
OUTPUT
Code:
[email protected] ~ $ adb push bootit.ko /
673 KB/s (27690 bytes in 0.040s)
Then lets insmod this .ko file
Code:
adb shell insmod /bootit.ko
This should reboot the tablet into the bootloader menu, lets verifiy.
Once in the bootloader screen lets make sure your PC can see the device in fastboot.
Code:
fastboot devices
OUTPUT
Code:
[email protected] ~ $ fastboot devices
015c7d7a445c260c fastboot
So now its time to erase the misc & cache partitions, as that is most likely the partitions that is making it boot to recovery...
Code:
fastboot erase misc
OUTPUT
Code:
[email protected] ~ $ fastboot erase misc
erasing 'misc'...
OKAY [ 1.021s]
finished. total time: 1.021s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected] ~ $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.096s]
finished. total time: 2.096s
Once these two command run with OKAY as the OUTPUT .
It is time to make sure we can reboot into the bootloader with the hardware buttons
So from where you are at in the bootloader screen use the VOL DOWN & POWER buttons to boot the tab back into the bootloader screen ..
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
fastboot devices
OUTPUT
Code:
[email protected]:~ > fastboot devices
015d2bbce2501405 fastboot
Code:
fastboot erase system
OUTPUT
Code:
[email protected]:~ > fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
fastboot erase recovery
OUTPUT
Code:
[email protected]:~ > fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
fastboot -w
OUTPUT
Code:
[email protected]:~ > fastboot -w
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it will either hangs on erasing 'cache'
Or it will give you an error, either way you will need to
reboot the tablet back into fastboot with the hardware buttons
Once that is done continue on the path
Code:
fastboot erase boot
OUTPUT
Code:
[email protected]:~ > fastboot erase boot
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
fastboot erase misc
OUTPUT
Code:
[email protected]:~ > fastboot erase misc
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected]:~ > fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
fastboot -i 0x0B05 reboot
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
Let it boot into stock ROM ....
Credits
@_that for his bootit.ko
TEAM CROMBi and TEAM ZOMBi-X @sbdags @hardslog
Troubleshooting
Here is some troubleshooting
Check out this thread for fasboot.exe, adb.exe and driver help ...CLICK ME
A message from _that
_that said:
Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770
Click to expand...
Click to collapse
Thx for all your help @_that
Great Guide: a happy Transformer Prime User you made of me!
Dear lj50036,
Thanks so much for your excellent guide. I went along with it all the way to the end and it just worked, splendid! You set up the scenario quite clearly and for those guys who are in the same situation this is a very handy guide.
Excellent piece of work!
My congratulations on your great work!
mitsublw
mitsublw said:
Dear lj50036,
Thanks so much for your excellent guide. I went along with it all the way to the end and it just worked, splendid! You set up the scenario quite clearly and for those guys who are in the same situation this is a very handy guide.
Excellent piece of work!
My congratulations on your great work!
mitsublw
Click to expand...
Click to collapse
I am glad to see you up and running ..... :good:
Thx Josh
Do I need a specific blob other than a US blob considering US is my area?
xerotix said:
Do I need a specific blob other than a US blob considering US is my area?
Click to expand...
Click to collapse
The tablet will tell you what the SKU is ....
When on the bootloader screen in the upper left is will tell you the SKU ...
Thx Josh
I just put together a Win 8 64 bit with a quad core i5...to the best of my knowledge I'm having trouble with it recognizing my tf300t. while it's physically connected on my front and/or rear usb ports, as I hear it recognized physically connecting, no visual signs of it connecting in my file explorer in twrp, prior recovery, and off after having all of the drivers and such installed to the best of my knowledge using your link as well...Suggestion?
xerotix said:
I just put together a Win 8 64 bit with a quad core i5...to the best of my knowledge I'm having trouble with it recognizing my tf300t. while it's physically connected on my front and/or rear usb ports, as I hear it recognized physically connecting, no visual signs of it connecting in my file explorer in twrp, prior recovery, and off after having all of the drivers and such installed to the best of my knowledge using your link as well...Suggestion?
Click to expand...
Click to collapse
Dont use windows 8 ..
That is all I can give you, never used it.
Not going to sit here and fill you with BS like I have all the answers.....
My solution would be to us some kind of a Linux OS .... I prefer Mint but @hardslog hates it .....
He will get a kick out of that ... LOL
Thx Josh
lj50036 said:
Dont use windows 8 ..
That is all I can give you, never used it.
Not going to sit here and fill you with BS like I have all the answers.....
My solution would be to us some kind of a Linux OS .... I prefer Mint but @hardslog hates it .....
He will get a kick out of that ... LOL
Thx Josh
Click to expand...
Click to collapse
I'm trying to figure out how to install Mint on my computer after I partitioned my hard drive to give me the space to install it...I'm searching google for it but haven't run across anything as of yet.
xerotix said:
I'm trying to figure out how to install Mint on my computer after I partitioned my hard drive to give me the space to install it...I'm searching google for it but haven't run across anything as of yet.
Click to expand...
Click to collapse
Is Mint going to go on its own hdd or are you going to dual boot from a hdd with windows on it ?
Thx Josh
lj50036 said:
Is Mint going to go on its own hdd or are you going to dual boot from a hdd with windows on it ?
Thx Josh
Click to expand...
Click to collapse
Dual boot on 2 tb hdd
xerotix said:
Dual boot on 2 tb hdd
Click to expand...
Click to collapse
You're dual booting with windows, yes ?
http://itsfoss.com/guide-install-linux-mint-16-dual-boot-windows/
There is all kinds of info out there ...
Thx Josh
lj50036 said:
My solution would be to us some kind of a Linux OS .... I prefer Mint but @hardslog hates it .....
He will get a kick out of that ... LOL
Thx Josh
Click to expand...
Click to collapse
Lol, LIES. I don't hate MINT. I just like to give @sbdags a hard time when something goes wrong with it. Any popular Linux distro should work well, and if you don't want to install it on a hard drive you can always install it on a USB and run from that
Thank you. You learn something new everyday...lol. I'm about to go to Full Sail here in Orlando where I live for software development. I was told I will be learning a lot in conjunction with Software Development parallel to Android development(which they teach as well)...I'm loving it.
I have tried everything I can think of...turned safe boot off after going into BIOS and searching more in BIOS, nothing thus far...
I have vista on another hard drive...would it work on vista?
xerotix said:
I have vista on another hard drive...would it work on vista?
Click to expand...
Click to collapse
It may work under vista .....
Thx Josh
lj50036 said:
It may work under vista .....
Thx Josh
Click to expand...
Click to collapse
It's gonna be a PITA to install that hard drive on this computer as I built this computer because of that POS. I'm unsure but hopefully I can figure out a way to connect both hard drives and have some sort of dual boot to use this hard drive with my new processor as opposed to the AMG with 1 gb of ram in the previous one from 5+ years ago. I already gutted it cuz it's of no use to anyone other than parting out. I have windows 7 on an old laptop I don't use anymore but I'm unsure of how to use that hard drive as to whether I can connect that one to that of my new desktop in a way/shape/or form so to speak
nexus 5
android 4.4.2
bootloader version: HHZ11K
Secure boot: enabled
unlocked
rooted
encrypted (i have set a pattern to unlock)
TWRP 2.6.3.4
Xposed module (not sure which version or if it is relevant at all)
xprivacy (not sure which version or if it is relevant at all)
suddenly, while i was surfing twitter, the phone restarted and attempted to install an update (not sure if it was 4.4.3 or Lollipop).
The phone went into bootloop.
My concern here , for now, is not how to fix it. I just need to retrieve my data (contacts, pics, calendar,...).
I held the power button and volume down to load into bootloader. from there i started TWRP. I was greeted with "please enter your password". I entered my pattern following the below arrangement
1 2 3
4 5 6
7 8 9
after several attempts which always ended with "Password failed. Please try again" i hit "cancel". This took me to the main TWRP screen.
I was worried about my data so i tried to copy everything to my pc through "adb pull sdcard/ C:\test" through terminal but i only got two folders namely "sys" and "tmp" but none of my personal data
In TWRP i touched "mount" to find the following..
"Select Partition to Mount:"
[ ] System
[ ] Cache
[ ] Persist
[ ] firmware
[ ] USB-OTG
below them there is a line that says "Storage: Internal Storage (0 MB)"
below that it says "Decrypt Data". If i touch it, it asks to enter my password. Again, i enter my password and it says password failed.
The log has this:
Updating Partition details...
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
E:Unable to mount ' /cache'
E:Unable to mount ' /cache'
E:Failed to decrypt data.
I think that i need to update TWRP to 2.8.2.0 at least in order to decrypt my data as previous versions don't support decryption and/or pattern passwords. Am i right?
if so, how can i update TWRP to the latest version ?
I tried flashing 2.8.4.0 through fastboot with no luck. I have tried the following during the flashing process:
1) flashed it and then tried starting TWRP immediately.
2) flashed it and then restarted bootloader and then tried starting TWRP
3) flashed it and then started system, which took me into bootloop, shutdown phone
and restart into bootloader then tried starting TWRP.
No matter what i do it always goes back to 2.6.3.4 :crying:
I tried to update it from within TWRP. I pushed TWRP 2.8.4.0 which was in zip format (jjd-openrecovery-twrp-2.8.4.0-hammerhead.zip which i took from this thread ) to the main directory "/". Then inside TWRP i went to install, choose the zip file, swiped right to confirm flash to only get the following:
at the top it says "Zip install complete"
then in like a feedback window this is written:
E : Mount : unable to find partition for patch '/jj
error flashing zip 'jjd-openrecovery-twrp-2.8.
updating partition details...
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage
finally at the bottom it says Failed (in red)
no need to say that it is still stuck on 2.6.3.4
Am i heading in the right direction ? if yes how can i update TWRP?
If not, Is there any other way to retrieve my data ?
Is it possible to fix this thing with out a wipe and keep my data intact?
Help plz
have you tried flashing only the cache partition through fastboot?
Thanks for your reply
I downloaded the factory image for nexus 5 from "developers dot google dot com/android/nexus/images#hammerhead" (version 4.4.2 (KOT49H) )
I kept extracting the zip file until I arrived at cache.img
copied it to the folder fastboot.exe is located in
run the command
Code:
fastboot flash cache cache.img
through terminal while in fastboot mode
i got the following:
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (13348 KB)...
OKAY [ 0.671s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.983s
I started the phone, it passed by the bootloop but then i got a message that says:
Unfortunately, google search has stopped
Unfortunately, the process com.google.process.gapps has stopped
Unfortunately, Google play has stopped
and couple of other similar messages
then i'm greeted with android setup screen (as if I'm running the phone for the first time; choosing language, time ...etc
while I'm in the middle of the setup process, the phone restarts. and it keeps happening again and again
Is there anything else I can do ?
crobh said:
Thanks for your reply
I downloaded the factory image for nexus 5 from "developers dot google dot com/android/nexus/images#hammerhead" (version 4.4.2 (KOT49H) )
I kept extracting the zip file until I arrived at cache.img
copied it to the folder fastboot.exe is located in
run the command
Code:
fastboot flash cache cache.img
through terminal while in fastboot mode
i got the following:
erasing 'cache'...
OKAY [ 0.125s]
sending 'cache' (13348 KB)...
OKAY [ 0.671s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 0.983s
I started the phone, it passed by the bootloop but then i got a message that says:
Unfortunately, google search has stopped
Unfortunately, the process com.google.process.gapps has stopped
Unfortunately, Google play has stopped
and couple of other similar messages
then i'm greeted with android setup screen (as if I'm running the phone for the first time; choosing language, time ...etc
while I'm in the middle of the setup process, the phone restarts. and it keeps happening again and again
Is there anything else I can do ?
Click to expand...
Click to collapse
That means it's borked. You have to RMA it with Google or send it to LG repair.
BirchBarlow said:
That means it's borked. You have to RMA it with Google or send it to LG repair.
Click to expand...
Click to collapse
I have bought it from google directly but I live overseas.
Tried the local LG maintenance center, they guy there didn't seem knowledgeable on the issue. He said he can try formating it and it might work again but has no idea of recovering the pics and other personal data.
I'm starting to lose hope :crying:
new attempt
I tried wiping cache from twrp and then starting the system. this happen:
Google logo for few minutes
then the four circles merging into white circle animation
then three message pops up,one by one, saying
"Android us upgrading" at the top in blue (this stays in all three messages)
and below it, it says
starting apps
upgrading contacts database
finishing boot
and then it returns to the four circles and then the messages again and again and again
Try flashing just the system.img.
Wakamatsu said:
Try flashing just the system.img.
Click to expand...
Click to collapse
So i extracted System.img from 4.4.2 (KOT49H) and then through terminal while in fastboot i wrote
Code:
fastboot flash system system.img
and the result was..
erasing 'system'...
OKAY [ 0.140s]
sending 'system' (702500 KB)...
OKAY [ 24.866s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 25.178s
What could be the reason for this ?
Sounds like yet another corrupted emmc. The usual test for this is to try locking the bootloader. If nothing happens and it reverts to unlocked it's dead. You could try the lg service but I have no idea if they would accept a warranty /rma
Sent from my Nexus 5 using XDA Free mobile app
Hello !
Well, after long research and testing some solutions, I create this post because I'm stuck at one point.
So, after a wipe in the fasboot mode, my TF700 get stuck into a bootloop with no access to recovery (The more I can have is 5 second with the TWRP splashscreen before rebooting). The ROM that was installed on my tablet is Cromi-kk.
I followed this help thread : http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495 and I'm stuck at the last point
Code:
fastboot -i 0x0B05 flash system boot.blob
Here is what it said on my computer :
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.355s]
sending 'system' (800927 KB)...
but nothing is moving on the computer, and the tablet is still displaying the fastboot screen...
So I really don't know what to do now, I hope one of you can have a solution
Thank you in advance !
Heck! I cannot believe this went undetected for so long!!! @lj50036
Hey Josh, have a look at this and make the edit! LMAO
@nhibel: Assuming you are trying to flash the stock blob in fastboot and you extracted the stock rom zip twice and put the file called just "blob" into your fastboot folder, the command to flash the stock blob is
Code:
fastboot -i 0x0B05 flash system blob
Nothing is happening because fastboot cannot find a file named boot.blob. Which makes sense since it does not exist. Unless you unpacked the blob.....
I don't think it's because of that. On the help thread it is said to rename the blob file into boot.blob, what I've did ^^
I tried again with renaming the file to blob, but it's the same, nothing is happening :/
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system blob
[sudo] Mot de passe de camille*:
erasing 'system'...
OKAY [ 2.431s]
sending 'system' (800927 KB)...
Maybe you can try the BUSTER99 way to access your bootloader.
http://forum.xda-developers.com/showthread.php?t=2179759&page=6
This was ones the sollution for my TF700T.
Good luck.
Scenic-3
nhibel said:
I don't think it's because of that. On the help thread it is said to rename the blob file into boot.blob, what I've did ^^
I tried again with renaming the file to blob, but it's the same, nothing is happening :/
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system blob
[sudo] Mot de passe de camille*:
erasing 'system'...
OKAY [ 2.431s]
sending 'system' (800927 KB)...
Click to expand...
Click to collapse
Show me a screenshot of your fastboot folder with "show extensions" enabled and make sure the blob is not named blob.blob.
I probably would start from scratch: Delete all blobs from the fastboot directory, extract the blob from Asus firmware, drag it "as is" into fastboot directory and use the fastboot flash system blob command
Here is some good news !
At first, I was trying to flash the blob from a Linux computer, but it wasn't working. So I tried again from another computer, which running on Windows 10. Again, it didn't work, exactly the same than on the Linux computer.
Finally, I tried something else. When I was looking for solutions at the beggining of my problem, I've dowloaded a twrp.blob, but I was unable to flash it at this time. I just tried again, and thank of the help of the help thread, I finally succeeded to flash TWRP (I had to try 2 times before the flash succeeded), and I should be able now to flash a rom !
Well, I lost everything that was on my device, but it works !
Thank you so much for spending some time to help me !
berndblb said:
Heck! I cannot believe this went undetected for so long!!! @lj50036
Hey Josh, have a look at this and make the edit! LMAO
@nhibel: Assuming you are trying to flash the stock blob in fastboot and you extracted the stock rom zip twice and put the file called just "blob" into your fastboot folder, the command to flash the stock blob is
Code:
fastboot -i 0x0B05 flash system blob
Nothing is happening because fastboot cannot find a file named boot.blob. Which makes sense since it does not exist. Unless you unpacked the blob.....
Click to expand...
Click to collapse
I am confused ??
Thx Josh
So was I. Never mind. Didn't realise you instructed to rename the blob... @[email protected]
Sent from my K00C using Tapatalk