Related
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
mowassasin said:
I'm sure theres a few of you out there who've bricked their Xoom in the same way I did:
Locking the boot loader after having custom rom and kernal running on it or something similar and come across an error upon boot that says
Failed image LNX 0x0002
RSD mode 2 initiated
or something to that respect
Then tried to do fastboot oem unlock, only to have the Xoom not be recognised.
The solution for me was to make a Motorola Factory cable as per guide here
For some reason, the Xoom would be instantly recognised by my computer and all fastboot commands would work, as well as RSD Lite (Did not do me any good as there is no Xoom Wifi SBF released)
That should fix the booting problem
If it still does not, follow one of the other guides on how to flash using fastboot, another rom now that you have fastboot working again!
Cheers!
Click to expand...
Click to collapse
So I went and bought the factory cable from the Black Hat guys, and luckily haven't had the need to use it. Any advice you'd like to give in case I need to at some point?
I guess the only advice I can give is: don't re-lock the boot loader when you have a custom rom loaded
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
It wouldn't recognise any fastboot commands nor the RSD Lite program for me.
But if it does, then thats good.
Merely a heads up for those who were in the same situation I was
bwcorvus said:
You don't need the cable. I have recovered 4 times myself and walked many others through on irc. We all use the stock cable that came with the device.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
yaturner said:
you won't care to share how you did it? You have no idea how frustrating it is to see someone say they know how to fix something and leave it it at that.
Click to expand...
Click to collapse
Over the course of a few hours I was able to fix this, so I am going to write this little walkthrough for you using a rom from bwcorvus's page (CLICK HERE) and then used the guide from dirtymindedx -(CLICK HERE)
The reason it took me this long (as well as doing other things) was because I used the wrong set up to unroot my tablet. I was using the Unofficial images that are on bwcorvus's link. Because I didn't read thoroughly enough in his breakdown, I made myself look like a fool...
What you want is NOT
UNOFFICIAL STOCK IMAGES
Click to expand...
Click to collapse
because you will not be able to lock the bootloader (IF you want it to be that way, which I did, and so it gave me a 0x000004 Error, and yes i see that you are having a 0x000002 but somewhere i read this could help that.) I just wanted to get rid of Clockwork Recovery Manager cause it was not working on my 3.2 rooted tablet, and thought that because i messed up teh whole image with playing around and upgrading and seeing how i could break the image without overclocking, i thought i should actually try and make it back to stock too. With this... I needed to do these steps...
1. Upgrade the Motorola drivers while the XOOM was plugged in, so then I would be able to use the Fastboot Correctly.
2. Download the correct roms for my tablet, (Wi-Fi is mine, just grab the one that fits your version and just follow along.)
3. Upgrade my ADB from google because for soem odd reason my fastboot did not like the xoom till i did that...
4. Used the STOCK CABLE. I can Confirm that the STOCK CABLE that allows you to recharge the phones, WILL WORK for this...
5. Once the ADB was set up, I restarted it, aka Hit the red X and then loaded it back up and then closed it again, just to make sure the services were updated somewhat...
6. Opened Command prompt and navigated to the folder that help the zipfile for the fastboot flashing guide (aka dirtymindedx's guide at the top), be using CD (Drive Letter):/location/of/the/folder/that/is/unzipped
7. I then checked over the information in the folder by using dir /a and then proceeded to read through the guide
7-1. A note here... I did the fastboot erase userdata instead, because I wanted to see if it would brick it again... (sorry, I was in a fowl mood with the world last night so I was waiting for it to get bricked so i had a reason to use it as an ice scraper on my car... (not like i would really do it... just wanted a reason for justification haha)
8. ???
9. Profit
This is only to get rid of a "already slightly bricked" device... which I had done after relocking the Rom that was not official to Motorola and now, after a few updates, i now have Android 4.0.3 for the Xoom that was OTA'ed, looking to see how easy it will be to root to reload my rpg game saves that i got caught up in (hence my disappearance from the forums haha...) but I hopefully helped you out in a direction to heads towards... and as long as you don't lock the boot-loader (which someone posted about it before i did...) you should be fine with any changes to the rom after the updates... Also, you can skip steps on this too... you can just flash the image and not the recovery menu and so forth, allowing you to keep other settings that are not part associated to the rom image.
Also sorry for the insanity in my words... I have been up for a good 36 hours with a half hour nap somewhere in there...
Hey guys,
i just started with falshing and those things. So i'm not so familiar with building and unlocking.
I bought a M2 with QUWERTY. I had and still has bootloop problems according to: http://forum.xda-developers.com/showthread.php?t=1457373
While analysing my bootproblem, i just realized, that i have a Fastboot Bootloader installed on this phone, what seems a little special.
Next step may be, to use the fastboot get this phone work, step after, use fastboot for improve this forum . But as i said, i'm new in this deep hardware near software-things, so need all your help for that .
greetz
how strange this in your bootloader, is similar as in the Atrix? So you installed it? I would like to know more about this topic
Looks like you have a dev phone. There are a couple of forum users with dev phones
Does rsdlite recognize it? I think you should try to have a look in Motorola Defy Android Development: there is a thread named ''experimental: trying to unlock the bootloader " (look at pages 60-75) .
I think someone wrote about some particular roms to be flashed in case of unlocked phones....
Does anyone know a way to extract this bootloader??
If so, I believe that lowering the fastboot and giving the command would be possible to unlock the MS2
Fastboot => http://www.mediafire.com/?2zdhukq3ha1qlrd
1) "fastboot oem unlock" to see the Station ID
2) "fastboot oem unlock ID" to unlock the bootloader
Hi everyone,
I'm following a thread about bootloader unlocking on the Defy section and scholbert suggested to make this little experiment:
Code:
dd if=/dev/block/mmcblk1 of=/sdcard/mmcblk1.raw bs=512 count=2048
then zip the raw file and upload it to the thread so that he can compare different dumps of that particular section of the rom, to discover a pattern which might lead to further understanding of how the lock works.
Source:
http://forum.xda-developers.com/showpost.php?p=21885753&postcount=735
Click to expand...
Click to collapse
djlooka said:
Hi everyone,
I'm following a thread about bootloader unlocking on the Defy section and scholbert suggested to make this little experiment:
Code:
dd if=/dev/block/mmcblk1 of=/sdcard/mmcblk1.raw bs=512 count=2048
then zip the raw file and upload it to the thread so that he can compare different dumps of that particular section of the rom, to discover a pattern which might lead to further understanding of how the lock works.
Source:
Click to expand...
Click to collapse
i think you can send PM to MKSilver.
Lutis said:
i think you can send PM to MKSilver.
Click to expand...
Click to collapse
I already did
Anyway I think the more dumps are posted, the better it is!
Hey there,
well I just started to read the experimental thread of the defy section.
Problem may of course be, that my phone here is in bootloop and at the moment I'm back at my old Nokia 6230i
If new Information comes arround I will report it here.
MKSilver said:
Hey there,
well I just started to read the experimental thread of the defy section.
Problem may of course be, that my phone here is in bootloop and at the moment I'm back at my old Nokia 6230i
If new Information comes arround I will report it here.
Click to expand...
Click to collapse
Did you tried simply wipe via moto recovery?
Or flash different sbf.
Have you tried the "fastboot oem unlock" command?
First things first:
at any RSD lite Version my phone is recognized as: "NS Flash OMAP 3630"
I saw, that the behavior of the phone while flashing is different in how i access the bootloader.
I can go into BL through:
A) "X"+"arrow up"
or also
B) "vol+" + "vol-"
while using A) I got a normal bootloader modus.
while using B) I got fastboot modus bootloader.
may someone test this with his phone and post it here?
another special thing: I can only access recovery while pluging the phone into a wallloader and pressing x, with or without the battery.
without the loader pluged in, recovery is not coming.
While access with fastboot and using it:
Code:
C:\where\my\sdk\is> fastboot devices
################ fastboot
-> the # means each a hex sign.
Code:
C:\where\my\sdk\is> fastboot oem unlock
...
FAILED <remote failure>
finished total time: 0.03s
next point while flashing my phone with a SBF_Flash under linux, there was an error with a SBF File, which doesn't throw errors under Windows and RSD.
About the defy forum: still reading, cause i don't want to brick the phone more than it already is, while haven't read all the knowledge.
greetz
MKSilver said:
First things first:
at any RSD lite Version my phone is recognized as: "NS Flash OMAP 3630"
I saw, that the behavior of the phone while flashing is different in how i access the bootloader.
I can go into BL through:
A) "X"+"arrow up"
or also
B) "vol+" + "vol-"
while using A) I got a normal bootloader modus.
while using B) I got fastboot modus bootloader.
may someone test this with his phone and post it here?
another special thing: I can only access recovery while pluging the phone into a wallloader and pressing x, with or without the battery.
without the loader pluged in, recovery is not coming.
While access with fastboot and using it:
Code:
C:\where\my\sdk\is> fastboot devices
################ fastboot
-> the # means each a hex sign.
Code:
C:\where\my\sdk\is> fastboot oem unlock
...
FAILED <remote failure>
finished total time: 0.03s
next point while flashing my phone with a SBF_Flash under linux, there was an error with a SBF File, which doesn't throw errors under Windows and RSD.
About the defy forum: still reading, cause i don't want to brick the phone more than it already is, while haven't read all the knowledge.
greetz
Click to expand...
Click to collapse
Well, I have bootloader 70.12. To get into BL I have 2 options:
1) arrow up
2) Camera + Volume down
Both ways leads to standard BL. Fastboot devices doesn't list my phone, just as before. I never tried to update my BL but I don't think it will do any difference.
I've tried it with bootloader 70.13.
Only option A works to get into Bootloader mode (not Fastboot).
Next "funny" fact.
While Flashing SBF with "normal" bootlaoder modus, everythings works with RSD lite.
While Flashing SBF with "fastboot" bootloader modus, I get an error after creating image files:
"Failed flashing process. Failed flashing process. Phone [0000]: Error getting subscriber unit information. Device API Error: 0xE0000042 Command: RQHW (0x0805041); phone connected"
Then is Result:"FAIL" and the phone stays in bootloader modus (fastboot).
May be I have wrong RSD lite calibration. Will investigate this, how it behaves in linux.
Ok, so googling "unsigned motorola milestone 2 SBF" turned up this as the first
Perhaps if that link is dead you could ask endless7 if he would be so kind as to re-upload it, or perhaps it is available elsewhere.
I say this because I remember reading somewhere that once it's unlocked you can only use unsigned SBF's.. pretty sure it was the bootloader unlock progress thread in the defy forums.. but I'm sure it's been said in our forums too
Just wrote a pm to Endless7. If thats true, it could help me get this device work (even in chinese) and than i can take a look forward, while using adb for example.
Hopefully!
Does anyone else know fo any other unsigned sbf's kickin around the web possibly better than a chinese one?
DreadPirateDan said:
Hopefully!
Does anyone else know fo any other unsigned sbf's kickin around the web possibly better than a chinese one?
Click to expand...
Click to collapse
Dan,
I'm not sure, but I don't think he is limited to flashing only unsigned stuff. The difference from developer phone to production phone, besides fastboot, is that the first one doesn't check signatures during boot chain. Theoretically speaking he is able to flash and boot any Milestone2 ROM he likes. I also suspect that he is able to downgrade from gingerbread to froyo, unlike us. There should be something else preventing him to boot the phone. That's just my opinion and it maybe wrong
Hey guys,
well enough is enough, bought today a second phone for the time the m2 is still dead.
I'm about to finish the defy thread today. Already learned a lot.
Well it is correct that i can flash signed SBFs. While booting into "normal" BL Mode.
But i can also boot into Fastboot and the RSD Lite Name starting with NS seems to show me something special.
So i risk something today and flash a froyo: It worked but still bootloops. The flash was successful and the M Logo turned gray.
At GB it is Red at my M2.
But now it would be great for an unsigned SBF, some more Ideas how to get it boot, or how to manipulate it over fastboot to get it work. Cause without get it into Android we can't go on analyse the bootloader.
PLZ help me. Will also ask a guy from the defy thread, who seems to know a lot about the milestone 1 and bootloaders/OMAP cpus. May he has a great idea what he wrote there was very clever and full of knowledge.
Greetz
Having been a member on this forum for years I must admit it has been incredible the wealth of information I've gained from it. I've had all sorts of phones/pdas and I'ved used this site to help me get the most out of it and to help m "tame" the device and stop rubbish from the vendors being installed on there when I don't want it.
A couple of years ago I got an HTC Desire. Great phone although limited memory. I was happy with it. Didn't bother to root it or anything. I then got a Motorola Xoom. Didn't bother rooting that either. I got myself an HTC Sensation now. I decided one day that I was going to unlock/root the thing to see if I could do it.
Somehow, I think I managed it. I haven't really noticed a difference but then I haven't put a custom rom on it. On all my old Windows mobiles I always had a custom rom.
Now, going back to the Xoom. It's an original Xoom. I bought it in May 2011. It is running Android 3.2 after Motorola sent out an update. All is good.
However, I would like to have ICS on it. This is where my problems begin. I've tried following so many different how-to's on how to do this unyet none so far have worked. So, either I'm completely stupid or, the guides are not easy to follow or the process (that is always touted as easy) is not very easy.
So I am asking for help. Here is what I understand are the steps that I need to acheive.
1. I need to unlock the device
2. I need to install a recovery image
3. I need to install ICS
Questions: I *think* I have done 1. How do I check? After what I believe is a convoluted process, I have installed the Android SDK. I have the drivers for the device on the [Windows 7 64bit] PC and I can see it listed when I type adb devices.
Why do I need to unlock the device? What does the act of unlocking it do? When I followed this:
http://forum.xda-developers.com/showthread.php?t=1242241
I got to step 3. I typed in the first command:
adb reboot bootloader
After much faffing around I found out from another site I needed USB Debugging enabled. Nobody told me this. No, it isn't obvious that I need this.
The boot screen appeared and gave a message at the top and then I typed in:
fastboot oem unlock
I followed the instructions on the screen. I unlocked the device. It took a while. When it rebooted I found I had to set the device back up again as if it was the first time I'd used it. "Great!" I am thinking, I've lost everything. Thankfully I backed up what I wanted so I am not bothered. Slowly the apps appeared to come back after it synched with Google. I'm assuming stuff gets backed up somewhere.
I typed:
fastboot reboot
It rebooted.I typed:
adb reboot bootloader
It rebooted into the bootloader. Now here is where things started to go off track. I typed the next command:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
I get this:
unknown partition 'recovery-Tiamat-R4c-100611-1150-cwm.img'
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img'
So what now?
I cannot believe the process to unlock and flash a rom is so unbelievably convoluted. I've read dozens of walkthroughs, how-to's and forums and each one seems to be very similar unyet there is always something different on there to what I get on my screen or something doesn't happen quite the same way.
Here is what I am trying to acheive:
I have Android 3.2 on my Xoom and I would like it to be ICS.
We'll assume that I am completely stupid and need serious handholding to get to ICS. Is there anyone that can help with these seemingly simple steps?
One thing I keep reading is about the recovery image file. Is this related to Cyanogenmod? I am assuming as it is called a recovery image file it helps you get back when things go wrong.
Thanks and much love to the person that takes up the reigns and helps me out here.
Hi!
If you are rooted already that's pretty easy. But if not, try using LordAIOTool to root (yea it's mine and I think it's worth a try). After you are rooted flash a new recovery - download from development section - after, rename the recovery to recovery.img and then use the following commands on adb, fastboot and this recovery folder (simultaneously)
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Then after keep clicking the vol- after 2s of your tablet appears on Motorola logo. Then keep cycling until appears Android Recovery then press vol+
You are on recovery now, just select install zip from sdcard...
Good luck
Sent from my MZ601 using XDA Premium HD app
If you wanted your xoom rom'd, then you could try wesamothman's guide: http://forum.xda-developers.com/showthread.php?t=1717402 It is great for beginners and the experienced alike.
This is for the wifi only xoom MZ604. There is another guide by him i believe for the MZ602
Do I need to flash a new rom to get root on my MZ604? What is the easiest way to just root the stock 4.0.4 firmware? I have no desire for a different rom. I just want to root it.
Hey there.
If you don't want to flash a custom ROM and only want to root it, try this:
1) unlock your bootloader.
2) thru ADB, flash a recovery image.
3) thru Recovery, flash superuser flashable zip: http://www.4shared.com/zip/g3yzbrIa/...?cau2=403tNull
I ran the first couple of steps to unlocking. That is as far as I have got. As I said, I have tried so many of these walkthroughs and not one of them has all the steps. They all make an assumption somewhere along the line.
For example: xxlordxx replied with:
"If you are rooted already that's pretty easy".
I'm not, that is the problem.
Again:
1. adb reboot bootloader
2. fastboot flash recovery recovery.img <---- This didn't work and gave me the error I pointed out earlier and that is where it all stopped. Noone explains what to do when it goes wrong.
Anything passed this stage is irrelevant until I can sort out the problem above.
yosterwp, you mentioned wesamothmans guide. I will try that one as it looks a bit more "dummies guide-like" and it is for my exact device which is the MZ604 wifi only. I hadn't seen this one as it was only posted a couple of days ago
Just so I know, can someone anser these questions? I'm sure they're very simple but I don't know.
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
2. Is unlocking the same as setting s-off?
3. If not, what is the difference?
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
5. What is Cyanogenmod and do I need it or is this another custom rom?
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Thanks for everything so far. I will let you know how I get on with wesamothmans guide.
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
wesamothman said:
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
Click to expand...
Click to collapse
You did
Much love!
Hi guys,
I decided to root my Nexus S with Nexus root toolkit, and then I tried to install CyanogendMod 10.
Then, it rebooted, and now when booting it stuck at a moving circle with the CyanogendMod text in it. after 30 minutes I had to remove the battery to shut it down.
Now I can access to the Fastboot mode (bootloader version I9020XXLC2)
it says Lock State : unlocked. But a recovery shows a robot on it's back with an exclamation mark on top of it during some minutes and then it try to but normally again and get stuck at the circle.
Update :
thanks to http://forum.xda-developers.com/showthread.php?t=1069032
I can now access to download mode, and I'll try to do something with ODIN, I'm on my way to tutorials.
And it's still recognize in windows as : Android ADB Interface in the computer management window (but no USB hard drive in the computer menu).
Any suggestion to help me out ?
ps : as you can guess, I'm quite a beginner, and may not get the meaning of all technical word in flashing phones.
Thanks for reading.
DO NOT use Odin for things like that. Think of Odin as a last resort thing rather than a tool you can use daily.
The Nexus line of phones is super easy to deal with.
Flash your recovery using fastboot.exe while in bootloader mode.
http://wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img
Download for recovery (rightmost column):
http://www.clockworkmod.com/rommanager
Once that is done, boot to recovery, and wipe data + flash your prefered ROM.
Edit: Apple pie is awesome.
polobunny said:
DO NOT use Odin for things like that.
Edit: Apple pie is awesome.
Click to expand...
Click to collapse
Yes they are awesome indeed.
And I saw your message after I did use Odin, and saved my phone.
I regret having use a nuclear bomb to cure my little bug, but I'm relieved having solve my problem.
Now I'm back on rooting & stuff and I won't forget to back things up first.
Tartopom said:
Yes they are awesome indeed.
And I saw your message after I did use Odin, and saved my phone.
I regret having use a nuclear bomb to cure my little bug, but I'm relieved having solve my problem.
Now I'm back on rooting & stuff and I won't forget to back things up first.
Click to expand...
Click to collapse
At least nothing is broken. That's the problem with Odin. It's easy to mess things up more than they are already. The Nexus line, and more precisely the Nexus S is a near bulletproof thing when used with the recommended tools-> ADB, fastboot and CWM. It's so rare you'll need to resort to Odin you might as well not recommend it.
polobunny said:
At least nothing is broken. That's the problem with Odin. It's easy to mess things up more than they are already. The Nexus line, and more precisely the Nexus S is a near bulletproof thing when used with the recommended tools-> ADB, fastboot and CWM. It's so rare you'll need to resort to Odin you might as well not recommend it.
Click to expand...
Click to collapse
I get you, but the thing is din is damn easy to use, once you get all the correct files.
I'm a basic user, and the link you posted, I hardly get the message in it, and now I'm fighting against my lazyness to find some fastboot solution for a 64bit windows.
Because : Never give up, never surrender! I'll understand how to root that thing and how to install my mod!
or I'll die trying.
But I'll rather succeed tbh.
Tartopom said:
I get you, but the thing is din is damn easy to use, once you get all the correct files.
I'm a basic user, and the link you posted, I hardly get the message in it, and now I'm fighting against my lazyness to find some fastboot solution for a 64bit windows.
Because : Never give up, never surrender! I'll understand how to root that thing and how to install my mod!
or I'll die trying.
But I'll rather succeed tbh.
Click to expand...
Click to collapse
Fastboot is actually really easy to use, just as is ADB.
You need your ADB drivers to be installed properly.
Then to install something via fastboot it's pretty much
fastboot recovery recovery.img
fastboot bootloader bootloader.img
fastboot radio radio.img
And so on. Doesn't get much easier than telling fastboot which partition to write to then which file. Once all is said and done, you switch to your custom recovery to flash stuff and voilà!
polobunny said:
Fastboot is actually really easy to use, just as is ADB.
You need your ADB drivers to be installed properly.
Then to install something via fastboot it's pretty much
fastboot recovery recovery.img
fastboot bootloader bootloader.img
fastboot radio radio.img
And so on. Doesn't get much easier than telling fastboot which partition to write to then which file. Once all is said and done, you switch to your custom recovery to flash stuff and voilà!
Click to expand...
Click to collapse
You're helping me not giving up, I'll help you to understand the gap between your knowledge and ease, and mine :
On your link : wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img I'm stuck at the second point.
I found one fastboot for x64 through rootzwiki.com/topic/4551-guide-making-fastboot-work-on-64-bit-windows-7-systems but now I don't know how that new tool work, and I can't even launch it
But I remember how to launch a command script and basically that's all.
Tartopom said:
You're helping me not giving up, I'll help you to understand the gap between your knowledge and ease, and mine :
On your link : wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img I'm stuck at the second point.
I found one fastboot for x64 through rootzwiki.com/topic/4551-guide-making-fastboot-work-on-64-bit-windows-7-systems but now I don't know how that new tool work, and I can't even launch it
But I remember how to launch a command script and basically that's all.
Click to expand...
Click to collapse
You need to make sure you have installed the ADB drivers for your phone. I highly recommend using the PDANet for Android drivers as they support a lot of phones.
http://junefabrics.com/android/
Then you need to use fastboot. There's no fastboot for Windows 7 64bit or 32bit and so on. There's one fastboot for Windows and it works with all newest platforms, so you don't need a specific one.
Here's a package containing fastboot and adb instead of download the whole Android SDK tools
http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
Then you're pretty much ready to go.
polobunny said:
You need to make sure you have installed the ADB drivers for your phone. I highly recommend using the PDANet for Android drivers as they support a lot of phones.
http://junefabrics.com/android/
Then you need to use fastboot. There's no fastboot for Windows 7 64bit or 32bit and so on. There's one fastboot for Windows and it works with all newest platforms, so you don't need a specific one.
Here's a package containing fastboot and adb instead of download the whole Android SDK tools
http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
Then you're pretty much ready to go.
Click to expand...
Click to collapse
Damn I'm a genius!
I discovered the same thing almost on my own
Thanks a lot mate ! Lost of apple and pie for you, you deserve it very much.
The difficulty is, with the sdk the fastboot command has to be launch in platform-tools folder, not the tool folder.
Yeah yeah yeah I know, it's writen almost everywhere, but I didn't saw that earlier and wasted hours to make it work.
Tartopom said:
Damn I'm a genius!
I discovered the same thing almost on my own
Thanks a lot mate ! Lost of apple and pie for you, you deserve it very much.
The difficulty is, with the sdk the fastboot command has to be launch in platform-tools folder, not the tool folder.
Yeah yeah yeah I know, it's writen almost everywhere, but I didn't saw that earlier and wasted hours to make it work.
Click to expand...
Click to collapse
Bravo, you're getting there. You'll be an adb master in no time.
At least you are now a user that knows how to use fastboot and fix issues that arise from flashing ROMs and relying on automated stuff.
Besides actual hardware issues most issues people have on their device are by some automated form of something. Tool kits/ROM manager and so on. All of which can be fixed up right away with fastboot and a basic understanding of what you're doing.
So now you're better off. All nexus devices work the same way as well.
First off, my tablet isn't bricked. I can boot it up fine. But when I try to install the factory downloaded software it just hangs on boot indefinitely. Similar things happens if I try to enter recovery. It goes fine until I have to press Volume ^, then it just freezes and I have to hold down the power key for 10 seconds. I've searched around and all I can find is threads from people stuck in a boot loop. Any help appreciated
A little more information. This tablet has been sitting for a while because it was such a disappointment. Before I decided I was fed up with it, it looks like I unlocked and rooted it. Iooks like I may have also tried to install Clockwork Mod on it. Trying to fix it has reminded me of why I stopped using it in favor of my nexus 7. The UI feels like it was designed specifically to make people not want to use tablets.
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
berndblb said:
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
Click to expand...
Click to collapse
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
RussTdesign said:
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
Click to expand...
Click to collapse
The first thing you should have done is upgrade your bootloader to the latest version. I would not actually use TWRP 3.0 for anything at this point if I were you. I have no idea if TWRP 3.0 works with that ancient JB 4.1 BL you got there, but I would not chance it. As a matter of fact, since you have to flash either stock rom or just the bootloader (and for both you use your recovery) I would highly recommend you flash an older TWRP version that is compatible with your BL. That combo - BL and recovery - is nothing you want to screw around with. You should go back to TWRP 2.4.1 or so.
TWRP Manager forced the latest TWRP version (developed for MM roms) on you and that's why I hate these apps! They do not check for compatibility at all....The proper way to flash a recovery is in fastboot and in fastboot only.
so I am going to give you a bunch of links and a general plan of attack, but you will have to do a fair share of reading.
First things is: Get fastboot working on your PC!!!!!! The first part of this guide I wrote way back tells you how: http://forum.xda-developers.com/showthread.php?t=2688891
Once you got that working flash TWRP 2.4.1 - instructions on how to are in the same thread. Reboot the tablet, then boot into TWRP.
Now flash the latest bootloader (Packaged with a slightly younger TWRP version from here: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
Reboot the tablet, then boot back into TWRP.
Now you again need to update your recovery to a version you can use with a current rom. I'd recommend this baby and it comes in a zip you can flash in your current recovery: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Flash the Kang recovery, then reboot and boot back into TWRP.
Format your data partition in TWRP. It takes an hour or so but it does a great job of leaving you with a clean slate for the new rom and is required before you flash a major change (which you are doing in any case).
Now you are ready to flash a rom.
I am going to recommend a really old one and a really new one. There are plenty of others to choose from in the Development section, but none of them is still under active development.
CROMi-X Resurrected. Based on Asus stock anno JB 4.2.1 but modded and fine tuned to the gills. LMK still puts out an update now and then, but those are more fine tunings of the fine tuning. Very slight changes - nothing major is going to happen here anymore. But it's a very stable and well working rom for those that actually like the Asus interface. http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
KatshMallow by Timudru. Yeah, Android MarshMallow for the TF700. Most Android users are still dreaming about MM and you can rock it on this ancient machine. And it's a beauty, just absolutely unbelievable what Tim has cooked up for this hardware. Trust me! Fantastic rom! http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
For both of them you should convert your data partition to f2fs which you can do in recovery. Instructions are here: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Actually, for CROMI-X Resurrected you don't have to do this - it's build into the rom installer.
You could try to short cut all this and just flash a new bootloader/recovery combo in your current TWRP 3.0. Maybe it works. Maybe it hardbricks your tablet. Nothing worse than trying to do something substantial (like flashing a bootloader) in an incompatible recovery....
Ok, now I shut up and let you read.
Have fun!
@berndblb thank you so much. I really appreciate you taking the time to help me out with this. This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions. I will get back later and let you know how it goes.
RussTdesign said:
@berndblb This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions..
Click to expand...
Click to collapse
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
berndblb said:
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
Click to expand...
Click to collapse
I have fast boot running and back-checked it via the fastboot devices. I downloaded twrp-2.4.1.0-tf700t.blob. the tried to load it. I keep getting a FAILED( command write failed (Invalid Argument)). Any thoughts
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Got fastboot running properly on my work computer with windows 7. I've gotten everything installed up to formatting the data partition. Doing that now. Super stressful & hard not to mess with it while it makes its way through a hour long process.
What did the trick to get fastboot working?
berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Looks like I got it sorted. Decided on going with the KatKiss rom. And the performance is night and day. Thanks so much for all your help. Next time I will probably do more reading before I try anything more... But then again I tell myself I will read the instructions before I start assembling ikea furniture & never do. So only time will tell. Anyway. Thanks again.
berndblb said:
What did the trick to get fastboot working?
Click to expand...
Click to collapse
Installing it on a different computer. This one runs windows 7. My laptop runs windows 8.1, could be as simple as that. But who knows.