Shadowofzeus Guide to flashing CM7 SRC (Source) on Windows revision 2
Disclaimer: I am by no means responsible if you brick your phone doing this. Flashing new roms can cause problems with your phone, as can flashing new recoveries, but I cannot foresee you bricking your phone by doing this. Even if you screw up flashing a recovery image you should be able to just flash the old image back and things should be back to normal. I will answer any questions you might have as I am sure many other forum members will too.
First off you must be fully rooted if you are not then you need to get there including having the ENG bootloader. Here is a link on how to get to that point.
G2 Wiki Root and ENG HBoot method
Second download the android sdk for windows from
Android Developers SDK Site
I recommend this file installer_r08-windows.exe because it is easier to work with. The nice thing about the windows files is it comes with fastboot in the package already.
Third if you are not comfortable with fastboot, adb, ClockworkMod Recovery, and windows command prompt then maybe this is not the right thing for you to be doing.
Fourth you need to understand a few things.
As of right now if you decide to bite the bullet and go and try this beta of the release client remember that Cyanogen and his team are not supporting it. Also this is not really meant to be a everyday driver sort of rom. It works well enough to be, but some releases break things so remember that.
Fifth, you will not as of when I am writing this be able to flash back to any of the Foyo roms because the new version of Clockwork Mod Recovery still seems to have trouble flashing them. Gingerbread requires the rom to be flashed to a partition with ext4 files scheme which Foyo is not compatible with. So if you want to fall back you will need to flash back to an older version of ClockworkMod Recovery.
And finally Clockwork Mod Recovery is not the same thing as Rom Manager. Rom Manager is a visual front end for some of the features of Clockwork Mod Recovery. Its version number is independent of ClockworkMod Recovery.
Screenshot of Rom Manger
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot of Clockwork Mod Recovery
Okay now to the tutorial.
The tutorial is based on the idea of a clean flash. Meaning that all of your apps will be erased and will need to be downloaded again. I recommend that you do a Titanium backup and restore you apps after you're done flashing for the first time. Titanium backup is available in the market.
First download a recovery img, rom and gapps package from ether
gridlock32404's site
Recovery Images
Roms
Google Apps
or
rhcp0112345's site
Everything in one place
and Now the Nightlies!
Rom Look for Vision
Recovery
Once everything is downloaded. Go to where you downloaded the files and copy them to the tools folder of where you installed your android sdk.
Now open a command prompt window by ether typing in “cmd” in the run box on the start menu (windows XP) or in the search box on the start menu (Windows Vista, 7).
Also you can go to “start menu > programs > accessories > command prompt”.
Now on the command prompt type cd < the path to your android sdk tool's folder> and hit enter.
Now type
“adb reboot bootloader”
Once it loads and says “fastboot usb” type
“fastboot flash recovery <name of recovery.img file>”
You will see some text about sending the file and flashing successfully.
Then type
“fastboot erase system -w”
This will erase your system and some personal setting so that you can flash with a clean install.
Next on the fastboot screen press the power button to go to the bootloader screen.
Wait for it to load and then press down on the volume down button once and then press the power button.
Wait for it to load in to you new ClockworkMod Recovery Version 3.0.0.5
Now we need to do somethings first before flashing the rom and Gapps.
Hopefully you know how to navigate ClockworkMod if not then this really is not the best thing for you to be doing. Scroll down to “wipe data/factory reset” and select it. Let it do its thing.
Then scroll down to “wipe cache partition” again let it do its thing. Next scroll down to advance and select it. Here select “Wipe Dalvik Cache” and let it again do its thing.
Ok now hit the power button to go back to the root menu. From here click on “install zip from sdcard”.
Ok now its time to transfer the file to your phone.
<Side note if you would perfer to transfer the files using the mount usb setting here is a tutorial on how to set it up by Ganii
http://forum.xda-developers.com/showthread.php?t=901449
>
Type in the command prompt window.
“adb push <name of the rom> sdcard/”
This will take a few minutes depending on your computer and your sdcard.
Once it finishes type
“adb push <name of gapps package> sdcard/”
Let it do its thing.
Now back on the phone you should see the “choose zip form sdcard” Select it and scroll down till you see the name of the rom you pushed using adb.
Select it and then scroll down to “Yes – Install <name of rom file>” and select it.
Lets begin the file install.
Now there are two way to do the next part, you can ether install the gapps package with out mounting the system and data partitions or you can mount them and install that way. I will be doing it using the mounting method because I know that works.
Now once the rom file installs it drops you back to the “Apply update from .zip file on SD card” menu
Press the back button and it should take you back to the root menu. On the root menu scroll down and select the “mounts and storage”
On this menu screen select “mount /system” and then “mount /data” next press the power button to go back.
Then scroll back down to “install zip from sdcard” and repeat the flashing sequence that we used for the rom but select the file for the gapps.
After it flashes press the power button to go back to the root menu and scroll down to “advanced”
On the Advance menu select “Fix Permissions”
Let it do its thing.
Once it is done then press the power button to get back to the root menu. Select “reboot system now”
and wait and see if it works.
I hope this has helped clear up some confusion people have been having with all of this.
Shadowofzeus
Why did you label this as a "RC" when there is not even a nightly posted yet of CM7?
You forgot that for fastboot, they'll need a ENG bootloader, or it'll fail. Otherwise, pretty good write up.
dictionary said:
You forgot that for fastboot, they'll need a ENG bootloader, or it'll fail. Otherwise, pretty good write up.
Click to expand...
Click to collapse
That's why I mentioned that they need to be fully rooted, but I will change it to mention the ENG bootloader and point them to the tread about root and installing the bootloader.
ztmike said:
Why did you label this as a "RC" when there is not even a nightly posted yet of CM7?
Click to expand...
Click to collapse
Because that is how its been labeled. As RC0 meaning that its not even a release candidate yet.
Fyi...
RC = Release Candidate
Sent from my HTC Vision using XDA App
PabloCafe said:
Fyi...
RC = Release Candidate
Click to expand...
Click to collapse
This.
"RC0" makes it sound like a release candidate. It isn't.
HTC Roms are real PITA for me. I would like to try one custom rom before my Desire Z changes owner.
You guys are super technical and noob like me can't find step by step directions for one single rom.
I have no problems flashing my SGS. I bet I wrote wrong place again.
How safe is flashing the ENG HBOOT? I want to flash it to my phone when I root it but I'm sorta scared, I"m pretty comfortable with rooting it, but if you screw up on the ENG HBOOT, you will have an unrecoverable brick. I'm no noob to cell phone modding, I used to mod Motorola's back in the day before Android and I have the new 14 RAM HBOOT and Radio on my G1. Is flashing the ENG HBOOT safe?
EDIT: Oh and I wouldn't link or tell people to root with the VISIONary method, that method is "fake" and EXTREMELY unsafe, I would link them to the tutorial in the Wiki, I haven't seen a single person brick with that method yet, and other people say the same(from what I hear at least.)
KoolKidsKlub said:
How safe is flashing the ENG HBOOT? I want to flash it to my phone when I root it but I'm sorta scared, I"m pretty comfortable with rooting it, but if you screw up on the ENG HBOOT, you will have an unrecoverable brick. I'm no noob to cell phone modding, I used to mod Motorola's back in the day before Android and I have the new 14 RAM HBOOT and Radio on my G1. Is flashing the ENG HBOOT safe?
Click to expand...
Click to collapse
I think the main risk with the ENG hboot is that if you make a mistake with the command that does the actual flashing:
dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
Click to expand...
Click to collapse
You can indeed brick your phone.
I have not changed my hboot for this reason and because there doesn't seem to be a whole lot of benefit for me to it. Having it _does_ give you a little additional recourse in case both your recovery and your ROM get screwed up though so it may well be worth it if you are running experimental recovery (as CWM 3.x is right now) and a highly experimental ROM (as CM7 is right now).
shadowofzeus said:
Because that is how its been labeled. As RC0 meaning that its not even a release candidate yet.
Click to expand...
Click to collapse
I think to a lot of people (myself included) seeing the letters "RC" does indeed indicate that it's a release candidate. I got all excited when I saw your thread in the topic list.
On the flashing eng hboot thing, I agree with raitchison. All of the stuff to do with rooting/S-OFF etc has a certain degree of risk, it's not 100% "safe". But if you carefully read up on everything in advance, and then carefully carry out the necessary procedures, you will have to be pretty unlucky to end up bricked.
Specifically with the eng hboot, when you have copied the file to your phone, before dd'ing it you should run a checksum on it for safety's sake, to make sure you have downloaded and copied a valid file and not a corrupt one. The checksums are in the Wiki.
As long as you do this and are then very careful in typing that instruction to do the "dd" itself (copy and paste can help reduce the possibility for error), then the only thing that could go wrong really is your phone losing power or crashing right in the middle of the dd. I think you'd have to be extremely unlucky for that latter possibilities to happen.
steviewevie said:
On the flashing eng hboot thing, I agree with raitchison. All of the stuff to do with rooting/S-OFF etc has a certain degree of risk, it's not 100% "safe". But if you carefully read up on everything in advance, and then carefully carry out the necessary procedures, you will have to be pretty unlucky to end up bricked.
Specifically with the eng hboot, when you have copied the file to your phone, before dd'ing it you should run a checksum on it for safety's sake, to make sure you have downloaded and copied a valid file and not a corrupt one. The checksums are in the Wiki.
As long as you do this and are then very careful in typing that instruction to do the "dd" itself (copy and paste can help reduce the possibility for error), then the only thing that could go wrong really is your phone losing power or crashing right in the middle of the dd. I think you'd have to be extremely unlucky for that latter possibilities to happen.
Click to expand...
Click to collapse
Ah alright, I feel more comfortable flashing the ENG HBOOT now, I guess I'll go ahead and flash it after I've rooted it, thank you.
When I try to flash the recovery it says the syntax of the command is incorrect.
No I am not putting in the quotes, I even copied and pasted it and put the name of the recovery in there, I keep getting the same error. What to do?
James_Caliber said:
When I try to flash the recovery it says the syntax of the command is incorrect.
No I am not putting in the quotes, I even copied and pasted it and put the name of the recovery in there, I keep getting the same error. What to do?
Click to expand...
Click to collapse
Can you press ctrl alt print scrn on your keyboard and upload the picture of your command prompt please and let me look at it.
shadowofzeus said:
Can you press ctrl alt print scrn on your keyboard and upload the picture of your command prompt please and let me look at it.
Click to expand...
Click to collapse
Now it's saying this
James_Caliber said:
Now it's saying this
Click to expand...
Click to collapse
alright type it just like this
fastboot flash recovery rec.img
shadowofzeus said:
alright type it just like this
fastboot flash recovery rec.img
Click to expand...
Click to collapse
TY
Why did you remove the <>, should I do that for the rest of the commands?
Something to do with win 7?
In CWM Recovery I'm getting a bunch of errors.
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/command
etc etc and it continues. What'd I do wrong?
James_Caliber said:
TY
Why did you remove the <>, should I do that for the rest of the commands?
Something to do with win 7?
Click to expand...
Click to collapse
I put those in there as place holders. Your files names replace those.
Don't worry about that stuff. It will say that because you just erased those partitions.
Related
-------due to the brick phones-------(and im not talking nokia)
I have started this thread to get some clarification on Nandroid back ups. Now i know there is already a thread with step by step instructions in the sticky's. But with all these G1 ones getting bricked due to the new spl incompatibility with the old radio is it safe to use. I ask this only because one of the steps is to have a recovery.img and the only recovery image i can find is for jf1.43 and one other. But none for the adp 1.5 builds. I am worried that if i were to flash a old recovery image, and it down grades my radio i may get bricked. I'm not really sure if that's how it works (if not please correct) and thats why i want to recovery image from the new builds ( i am using Dudes Cupcake 1.1)
Do they exist and if they do and i just haven't search hard enough please tell me. Or is the recovery image what i create when i do the back up. I ask all these perceivable noob questions because i really like my G1 and would hate to brick it.....
Please post some useful Replies... I think this thread could be potentially useful
Doing a nandroid backup creates a boot.img, data.img, and system.img of your phone. Flashing those three, restores your phone exactly as it was when you created the backup. As long as you do a backup of your system when it's stable, then it doesn't matter what you do to your phone. As long as you can get into fastboot, then it can be fixed in less than 5 minutes.
Dunno if that was the answer you were lookin for, but that's how I understand it. And it works....I did a nand backup of my Dude build just yesterday, and flashed over to haykuro's 6.0 to check it out...test drive it. I didn't like it, so I flashed the nandroid backup, and was back up and running in minutes.
You mentioned recovery.img....I don't know what that is or what you do with it.
Assuming you have fastboot setup, just do the steps in this post and you're golden-
http://forum.xda-developers.com/showpost.php?p=3311708&postcount=2
the recovery.img is what the phone boots in recovery mode... the recovery.img that your referring to allows you to create NAnd backups easily with NANDroid... the recovery img is totally independent from your SPL (bootloader), Radio, and Firmware
ESKIMOn00b said:
the recovery.img is what the phone boots in recovery mode... the recovery.img that your referring to allows you to create NAnd backups easily with NANDroid... the recovery img is totally independent from your SPL (bootloader), Radio, and Firmware
Click to expand...
Click to collapse
Right on, thanks for that. Knowledge is power.
So the op says that he found the JF1.43 recover.img....That's the one we all have and the one he needs, right?
yep, they're all the same
All the recent ROMs EXCEPT for the official HTC ADP use the same recovery.img found in the previous JF ROMs (1.42, etc.). You can safely reflash the recovery image from fastboot without touching the radio, the SPL or even data, boot or system if you want and it won't hurt anything.
remember when you orig rooted your phone and the recovery mode didnt have the fractal background and you had to press alt+l to show the text? thats the OLD recovery img, the fractal bkgrnd (v1.43) one is the new one, and so far the latest "cooked" recovery.img
Like i said im kinda noobish. So after i downloaded the drivers, and the sdk for 1.5 i still need to download fastboot (to my pc) as well.
Great post. +1
pshadey said:
Like i said im kinda noobish. So after i downloaded the drivers, and the sdk for 1.5 i still need to download fastboot (to my pc) as well.
Click to expand...
Click to collapse
correct...
the fastboot.exe is how your PC will interface with the FASTBOOT mode in the SPL
if you didnt have it DL'ed when you tried to fastboot, your computer would kickback that fastboot isnt a valid command or the like (depending on os)
so im reading all these tutorials, and im getting confused a little... to use fast boot through adb does my phone need to be at the boot loader (skateDroids) or are there commands that i would need to enter in order to get there....
I appriciate every answer i am trying to learn as much as i can. This has really spark a interest in my life and i really enjoy it.
fastboot is not part of adb, and yes your phone needs to be in bootloader to FASTBOOT, after entering bootloader plug in the usb cable and press the back button, your phone should read FASTBOOT rather than serial0
adb works almost anywhere (after splash1/g1 logo) except bootloader...
for reference ADB stands for Android Debug Bridge
I am still slightly confused how do i create a nandroid back up, i am using dudes cupcake 1.1. Is it the same as JF's alt-b
pshadey said:
I am still slightly confused how do i create a nandroid back up, i am using dudes cupcake 1.1. Is it the same as JF's alt-b
Click to expand...
Click to collapse
Yep. Boot your phone with home+power, then Alt+B. It'll create a folder on your sdcard called nandroid. All the .img files will be in there.
i dont think i have the right recovery image though do i just download the zip file. and do the whole rename to update.zip and install alt-s.
I only ask because i opened the file and found a recovery.img which made me ponder.
thats the Nand dump of your recovery partition... you figured it out...
if you made the backup you have the right recovery img.... the old one doesnt have it...
~edit~
I see I misunderstood the question. Duh
ESKIMOn00b said:
thats the Nand dump of your recovery partition... you figured it out...
if you made the backup you have the right recovery img.... the old one doesnt have it...
Click to expand...
Click to collapse
and when i booted in recovery mode i dont have the option alt-b. so i must have the old recovery image.
so now i need to (already have) download the recovery image zip file from jfs blog, rename it update.zip and flash it....right????
This is what your recovery mode will look like after you update it-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't answer your question about how to update to it though. Mine's been this way since waaay back when I flashed JF's RC33.
yea, thanks bro. mine definitely does not look like that. but now i need to know for sure how to update it.
pshadey said:
and when i booted in recovery mode i dont have the option alt-b. so i must have the old recovery image.
so now i need to (already have) download the recovery image zip file from jfs blog, rename it update.zip and flash it....right????
Click to expand...
Click to collapse
I am having the same problem... I am on the Dude's Cupcake 1.1a but I dont see ant Alt-B option...
Android system recovery utility
E:Can't open /cache/recovery/command
Home+Back - reboot system now
Alt+L - toggle log text display
Alt+S - apply sdcard:update.zip
Alt+W - wipe data/factory reset
Click to expand...
Click to collapse
Thats all i have on my screen.
Flashing ROMs/Mirror Links - Sending Files in CWM Via ADB! & Flashed TF201 Recovery?
I'm seeing alot of people are having issues with people loosing system images/soft bricking devices but its all avoidable!
If you download a Custom ROM also make sure you download the latest ASUS Stock ROM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you create a folder on your internal SD called ROMs if anything happens you can always flashboot CWM and then you can use CWM to install new ROMS.
ROM MIRRORS: https://docs.google.com/folder/d/0B_7VIwxjudWvLUllSVpyUW9oSDQ/edit
At the moment we dont have mount via USB or external SD so if you loose access to your internal system you could be stuffed without these files.
Also make sure you create a CWM backup
Pushing files in Recovery via ADB
Step 1: Boot into recovery ( To access it, shutdown your tablet and press Power + Vol Down, then press Vol Up before the 5s timeout)
See Picture: https://docs.google.com/open?id=0B_7VIwxjudWvUWRJRmpOd3M4WFk
Step 2:Open Windows device manager and you will probably see https://docs.google.com/open?id=0B_7VIwxjudWvNUhOVWVmSDhjWjA Transformer device listed but not mounting in ADB Devices.
Step 3:Download the ASUS USB Drivers from https://docs.google.com/open?id=0B_7VIwxjudWvLTJuQnlZU1B1TVU and extract them to where you want.
Step 4: Watch this video to install the ADB Drivers https://docs.google.com/open?id=0B_7VIwxjudWvXzJmT09RZjlPdlE
Step 5: Using ADB "Adb Push c:\romfolder\rom.zip /sdcard" wait for it to finish then using recovery you should be able to flash it now.
Flashed TF201 Recovery in ROM Manager?
Follow these steps to recover your semi-bricked TF300T Tablet All the files you need are in the ROM Mirrors link. You need to make sure you have installed the drivers as above to be able to send recovery via Fastboot. You need our TF300T Recovery and the Asus Stock ROM.
Step 1: We need to flash our recovery onto the tablet. As you probably have already done this I have copied the info from http://forum.xda-developers.com/showthread.php?t=1668173 Thanks to XpLoDWilD for this!
Step-by-step guide
Unlock your bootloader with Asus Unlock app
Connect your tablet to your computer
Shutdown your tablet
Hold Power + Vol Down until a message appears ("Press Vol. Up to enter RCK (5s)") : DON'T PRESS VOL UP
After 5 seconds, a new menu appears. Press Vol Down once to change to the USB icon, then press Vol. Up to validate (you have to do this in less than 10 seconds, otherwise your tablet will boot Android OS)
At this point, your computer should recognize Fastboot device (Windows will notify you here, OSX/Linux stays calm)
Flash recovery image with fastboot: fastboot -i 0x0B05 flash recovery recovery.img (if we suppose recovery.img is in your current directory)
Once the operation is done, type fastboot -i 0x0B05 reboot to reboot your tablet
You now have CWM installed. To access it, shutdown your tablet and press Power + Vol Down, then press Vol Up before the 5s timeout. After a few seconds, you'll be in CWM interface.
Step 2:Repeat Steps 4-6 to boot back into Fastboot
Step 3:NB: If you have followed what I said about keeping Stock ROMs on the Internal SD Card just use CWM to reflash that and you are done! If not contiune with these steps
Now you need to have the Asus Stock ROM you want to flash, Extract the ZIP so you can see the BLOB file and take note of the location you have extract too! This is the file we will send via Fastboot. You can rename the file to update.blob so it follows the picture below and save into the directory you have your fastboot command.
At the command Prompt type fastboot -i 0x0B05 flash system update.blob
Step 4: fastboot -i 0x0B05 reboot
Picture https://docs.google.com/open?id=0B_7VIwxjudWveFlOVFdHT2ZjeHM
Special Thanks to XpLoDWilD for the Dev work and BlakeC90 for recovering his tablet through this brick. I copied the details for the thread below.
http://forum.xda-developers.com/showthread.php?t=1687015
Good idea to do this, thanks!
Great post, should be stickied. This will help the people new to flashing immensely.
Cheers guys, I've also uploaded some ROMs now.
I will Mirror the CM9 ROMs and will also mirror Stock ones
I have my tf300, acer a100 and my Samsung galaxy blaze all rooted, but have yet to flash a custom rom. if someone can just clarify something that would be awesome
a nandroid back is same thing as backing up current rom threw recovery?
to even get into recovery, do you have to unlock ur bootloader first? if so after you unlock it. will you still receive firmware updates threw Asus ota. If not, is all you do is wait till rom or build.prop gets updated with the same features and just update that way. if not, what the hell do you do then. kinda confused about that lol
lastly, this might be a stupid question but a custom rom is basically a tweaked
operating system. that has more features then HC or ICS. and all the good stuff like overclocking build in? am i missing any other major features. if im even on the right track in the first place lol
if anybody can help. will be appreciated
Trevor OBrion
trevor7428 said:
I have my tf300, acer a100 and my Samsung galaxy blaze all rooted, but have yet to flash a custom rom. if someone can just clarify something that would be awesome
a nandroid back is same thing as backing up current rom threw recovery? Yes
to even get into recovery, do you have to unlock ur bootloader first? if so after you unlock it. will you still receive firmware updates threw Asus ota. If not, is all you do is wait till rom or build.prop gets updated with the same features and just update that way. if not, what the hell do you do then. kinda confused about that lol If you device unlock then you wont get OTA updates, you need to manual install them or install custom ROM
lastly, this might be a stupid question but a custom rom is basically a tweaked
operating system. that has more features then HC or ICS. and all the good stuff like overclocking build in? am i missing any other major features. if im even on the right track in the first place lol
ROMs like CM9 are based off pure Google Code rather than all the tweak/bloatware that Asus put in and yes OC is possible with custom kernals
if anybody can help. will be appreciated
Trevor OBrion
Click to expand...
Click to collapse
See above
Unlock is a permanent voiding of your warranty as well.
Sent from my SCH-I510 using XDA
Updated to recover from Flashing TF201 Recovery
Thanks for the nice Thread.
What if the TF300T cannot boot into recovery?
Code:
Android cardhv-user bootloader <2.10 e> released by "WW_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image
Jake2kOne said:
Thanks for the nice Thread.
What if the TF300T cannot boot into recovery?
Code:
Android cardhv-user bootloader <2.10 e> released by "WW_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image
Click to expand...
Click to collapse
Can you get into the fastboot menu?
Step 1 of the TF201 recovery?
Nope. When pressing Power + Vol Down will directly show message above.
I think it's over, but maybe someone has an idea.
Jake2kOne said:
Nope. When pressing Power + Vol Down will directly show message above.
I think it's over, but maybe someone has an idea.
Click to expand...
Click to collapse
Just a thought if seems it looking for a stock image? So have you tried putting the ww.29 zip file on the external SD card and seeing if it picks it up?
Also see if it detects in Windows Device manager?
Oh, forgot to mention: It even won't boot up.
It boots neither Android, nor recovery.
No joke.
Jake2kOne said:
Oh, forgot to mention: It even won't boot up.
It boots neither Android, nor recovery.
No joke.
Click to expand...
Click to collapse
Yeah I don't mean into Android, if you put the ww.29 on a external card and boot it into
Code:
Android cardhv-user bootloader <2.10 e> released by "WW_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image
It might be looking for a firmware, last fail attempt recovery?
When its switched on in the above state does anything show in device manager?
Although its for the TF101 seems you are having the same issue http://forum.xda-developers.com/showthread.php?t=1622343 ?
It's not mine so I have to forward each idea.
Tried with the external SD card but didn't work. Too bad.
Tested with normal boot up (stucked on ASUS logo) and tested it with the recovery mode (or whatever it is called like...)
The link could be the same problem but has no solution.
Tomorrow UPS get the tf300.
The ASUS Bootloader Unlock Tool bricked it totally. Seems like to be the first device at all.
The User said he just used the tool, restarted, stucked. Really good.
Jake2kOne said:
It's not mine so I have to forward each idea.
Tried with the external SD card but didn't work. Too bad.
Tested with normal boot up (stucked on ASUS logo) and tested it with the recovery mode (or whatever it is called like...)
The link could be the same problem but has no solution.
Tomorrow UPS get the tf300.
The ASUS Bootloader Unlock Tool bricked it totally. Seems like to be the first device at all.
The User said he just used the tool, restarted, stucked. Really good.
Click to expand...
Click to collapse
Let us know how you get on with the warranty, if Asus reject it under its been unlocked or not.
All I have to say is I hope this works. I was dumb and was curious to see after installing sparky's stock rooted rom I selected factOry restore from the devices menu in settings. It erased all! Luckily I have my tiBU saved on my ext sd.
It's pushing virtuous now by using the \data media option
My experience in using the adb push method
everything went smoothly. I didnt back up everything properly the first time i flashed a rom so i had to push a rom on the transformer.
This is important and please add it on the first post. If the files you pushed on the device dont appear on it. Restart your computer and try again. (i didnt get any errors while pushing but i couldnt find the files on the device and i fixed it by restarting my pc and pushing them again)
ok, so im lost!.. lol
I have a soft brick, im trying to push a stock rom to my tab, but can not for the life of me get my tab to show up as a ADB. It will show as a Fastboot Interface, and if i go into recovery it just shows Transformer like in the pic in the original post. I have tried installing the driver just like the youtube vid shows, but its not working.
backstory is i tried to flash a new custom ROM over another custom ROM, i wiped my usual, cache, dalvik, and wiped system, to have a fresh install, but kept getting a broken ROM with the new one, and when i flashed back to my old one. i then clicked format internal data like a tard and wiped my entire SD Card.
Any advice you guys can give would be appreciated.
UPDATE: Ok i got ADB working (i think... lol) it shows in device manager, but im not getting anything when typing adb devices in cmd prompt. I also got fastboot to reboot the device but when i try to flash the update.blob i get.... error: cannot load 'update.blob'
If i use qtADB it will flash the recovery.img for some reason i just cant get it to wok when using the actual cmd prompt. (in cmd prompt i was getting the error cant load xxxx.blob or xxxx.img regardless of where ii placed the image or blob file on my computer)
Now you need to have the Asus Stock ROM you want to flash, Extract the ZIP so you can see the BLOB file and take note of the location you have extract too! This is the file we will send via Fastboot. You can rename the file to update.blob so it follows the picture below and save into the directory you have your fastboot command.
At the command Prompt type fastboot -i 0x0B05 flash system update.blob
Step 4: fastboot -i 0x0B05 reboot
I try this but i get this error
C:\Users\VaHiD\Desktop\Fastboot>fastboot -i
0x0b05 flash system blob
sending 'system' (799748 KB)...
OKAY [138.170s]
writing 'system'...
FAILED (remote: (InvalidSize))
finished. total time: 214.335s
what is the ((InvalidSize)) error?!
I try to install recovery twrp and cwm but do not install any .....
Can you help me?
So I followed the instructions in this link so I could root my N4:
http://www.androidrootz.com/2012/11/how-to-root-nexus-4-on-mac.html
I get this when I reach the point in the video where he instructs me to enter recovery mode.. why ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You aren't flashing your recovery properly in bootloader mode.
fastboot flash recovery <nameofrecovery>.img
Choose either: Clockwork Recovery of Team Win Recovery Project (TWRP) as your recovery. Put the .img file in the same folder as fastboot.exe.
I recommend TWRP.
So for example,
http://teamw.in/project/twrp2/129 Scroll down to recovery image method
Place the .img file in the same as fastboot
go into bootloader mode on your phone
fastboot flash recovery openrecovery-twrp-2.3.3.2-mako.img
it should say sending.... then done!
then use vol keys and you should be able to get into bootloader and the android with red ! isnt there.
And thank you for not using the toolkit <3
zephiK said:
You aren't flashing your recovery properly in bootloader mode.
fastboot flash recovery <nameofrecovery>.img
Choose either: Clockwork Recovery of Team Win Recovery Project (TWRP) as your recovery. Put the .img file in the same folder as fastboot.exe.
I recommend TWRP.
So for example,
http://teamw.in/project/twrp2/129 Scroll down to recovery image method
Place the .img file in the same as fastboot
go into bootloader mode on your phone
fastboot flash recovery openrecovery-twrp-2.3.3.2-mako.img
it should say sending.... then done!
then use vol keys and you should be able to get into bootloader and the android with red ! isnt there.
And thank you for not using the toolkit <3
Click to expand...
Click to collapse
This did not work
You have the latest version of Android Fastboot Binary? Bootloader unlocked?
.img file in the fastboot-mac folder
The error is pipe properties. Whatever that is.
BLL00 said:
This did not work
Click to expand...
Click to collapse
Check my post (#13) in this thread. http://forum.xda-developers.com/showthread.php?t=1997684
If you received an ota you have to delete a couple files to get the recovery to stick.
Edit: the pic I quoted didn't show up in the app. I'm not sure what that error means.
Sent from my Nexus 7 using Tapatalk HD
my problem is that after i flash recovery-clockwork-6.0.1.9-mako.img, it refuses to enter cmw and shows the icon I showed in my picture.
BLL00 said:
my problem is that after i flash recovery-clockwork-6.0.1.9-mako.img, it refuses to enter cmw and shows the icon I showed in my picture.
Click to expand...
Click to collapse
When you type fastboot-mac devices... your device shows up right?
zephiK said:
When you type fastboot-mac devices... your device shows up right?
Click to expand...
Click to collapse
BLL00 said:
Click to expand...
Click to collapse
Hmm okay well I don't know how a mac works. I know that you don't need drivers. I'm going to say that it's something wrong with the fastboot binary file. It's the error that you're seeing there. On the guide you used, the error is nonexistant in his picture. Bootloader is unlocked right?
You have the latest version of Android Fastboot Binary? Bootloader unlocked?
.img file in the fastboot-mac folder
The error is pipe properties. Whatever that is.
Click to expand...
Click to collapse
ensure USB debugging is enabled as well.
zephiK said:
Hmm okay well I don't know how a mac works. I know that you don't need drivers. I'm going to say that it's something wrong with the fastboot binary file. It's the error that you're seeing there. On the guide you used, the error is nonexistant in his picture. Bootloader is unlocked right?
Click to expand...
Click to collapse
-Yeah I unlocked my bootloader.
-The pipe properties error is gone, it was just a matter of switching usb ports!
I need to mention that when I flashed the cmw img and hit start on the fastboot menu, IT DID in fact enter cmw, but somewhere in there, I think I've done something wrong and my phone restarted normally. Now, I upload the zip file into the sdcard path and restart my phone into fastboot again, when I hit recovery mode, it then shows that icon!
BLL00 said:
-Yeah I unlocked my bootloader.
-The pipe properties error is gone, it was just a matter of switching usb ports!
I need to mention that when I flashed the cmw img and hit start on the fastboot menu, IT DID in fact enter cmw, but somewhere in there, I think I've done something wrong and my phone restarted normally. Now, I upload the zip file into the sdcard path and restart my phone into fastboot again, when I hit recovery mode, it then shows that icon!
Click to expand...
Click to collapse
Did you read my post?
From efrants android 101 sticky:
I just flashed CWM, but every time I try to boot into CWM, I keep seeing the stock recovery. Why?
If you updated your Android build using an OTA update file (either manually or over-the-air), the update placed two files on your device that re-flash the stock recovery every time you reboot your device. These two files are:
/system/etc/install-recovery.sh <== this is the script that installs the patch file
/system/recovery-from-boot.p <== this is the patch
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
Click to expand...
Click to collapse
El Daddy said:
Did you read my post?
Click to expand...
Click to collapse
yes i did and if you noticed in the photo i uploaded, there's an iphone under my nexus 4 so I'm VERY new to this. I couldn't find the system path ???
BLL00 said:
yes i did and if you noticed in the photo i uploaded, there's an iphone under my nexus 4 so I'm VERY new to this. I couldn't find the system path ???
Click to expand...
Click to collapse
You have to use a app that has root functionality. Go outside of the /sdcard/ folder and go into /system/
So basically here's what you want to do. By the way good job at switching USB port and having that work.
- Flash CWR
- Flash the superuser zip file to obtain root
- download a file manager that lets you go outside /sdcard/ and then go to the path el daddy mentioned and delete those files.
https://play.google.com/store/apps/...yLDEsImNvbS5qcnVtbXkucm9vdC5icm93c2VyZnJlZSJd here is a file manager you can use.
basically press "..." and go into /system/etc/ find file install-recovery.sh
and/or /system/ and find file recovery-from-boot.p
You have to rename (or delete) one or both of them, then re-flash your custom recovery. Now it will stick.
@El Daddy: He's just a little new. Don't be so harsh (you probably weren't and thought he didn't see it), I mean after all he didn't use the toolkit so, I have respect for him.
the first path is /system/etc/ delete install-recovery.sh
the path to the other file is /system/ find recovery-from-boot.p and delete that
You'll need root access first.
So basically, flash the custom recovery then boot into recovery.
Flash the su.zip file.
Boot into the OS and use a file explorer and delete those files.
Then the custom recovery will stick.
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
zephiK said:
@El Daddy: He's just a little new. Don't be so harsh (you probably weren't and thought he didn't see it), I mean after all he didn't use the toolkit so, I have respect for him.
Click to expand...
Click to collapse
I didn't mean to come off harsh. Sometimes demeanor doesn't translate well through text.
El Daddy said:
the first path is /system/etc/ delete install-recovery.sh
the path to the other file is /system/ find recovery-from-boot.p and delete that
You'll need root access first.
So basically, flash the custom recovery then boot into recovery.
Flash the su.zip file.
Boot into the OS and use a file explorer and delete those files.
Then the custom recovery will stick.
---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------
I didn't mean to come off harsh. Sometimes demeanor doesn't translate well through text.
Click to expand...
Click to collapse
Yeah agreed. Same goes with sarcasm in text. Just takes some patience with the new people, but I honestly don't mind as this is the Q&A section after all. As long as they're not using the toolkit I won't be upset hehe
zephiK said:
Yeah agreed. Same goes with sarcasm in text. Just takes some patience with the new people, but I honestly don't mind as this is the Q&A section after all. As long as they're not using the toolkit I won't be upset hehe
Click to expand...
Click to collapse
Yep. I'm willing to help anyone, (for as long as it takes) who wants to put the time in and learn. Anyone not using a toolkit is a win for me. :laugh:
El Daddy said:
Yep. I'm willing to help anyone, (for as long as it takes) who wants to put the time in and learn. Anyone not using a toolkit is a win for me. :laugh:
Click to expand...
Click to collapse
Amen, amen. Free training for these people to help others the non-toolkit way so people like us can take a break and relax
Thanks everybody for helping out. I managed to root my phone and this is what I have done to bypass that android logo with it chest open and a "!" floating on top of it:
1-Restarted phone into fastboot mode
2-Flashed CWR's .img
3-Went straight into recovery mode after flashing and was able to enter CMW and complete the procedure.
Next thing you wanna do is GET RID OF THAT TASK MANAGER! Let android work its magic... Enjoy !
Sent from my Nexus 4 using Tapatalk 2
Just to mention when you fastboot flash or use goo manager for twrp recovery it will automatically add .bak to the recovery- from-boot.p file
Sent from my Nexus 4
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder. Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
subodhverma21 said:
Everything went well till step 5.
In terminal window of phone i could find select..... but after that how to proceed I donot know.......... what commands should i use on TWRP terminal...........
Phone didn't get detected in ADB even in TWRP terminal
pl. help
Click to expand...
Click to collapse
TWRP termnal is just so that your phone will connect as adb to your pc.
eg0097 said:
TWRP termnal is just so that your phone will connect as adb to your pc.
Click to expand...
Click to collapse
my problem got resolved.........
actually driver was the only problem which was not allowing ADB to detect device in RECOVERY mode, though device was detected in FASTBOOT mode
So I reinstall the driver to get ADB Interface installed in system> device manager
and then followed your remaining steps i.e. 6 onwards
Thanks a lot.....
Not really sure about the following, but I hard-bricked my phone while rooting it a few days ago. Black screen, phone wasn't visible in ADB / fastboot, LED didn't change after plugging in the charger etc.
The only thing that helped: holding the power button for at least 2 minutes. The device restarted afterwards w/o any issues.
Can't find the source of it anymore ...
Very useful guide, I revived my soft - bricked Moto G
still not working
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
sascha-1102 said:
on my xt1032 moto g 16gb version I just have the warning screen that the bootloader is unlocked.
followed a lot threads but nothing helped till now.
tried your verswion and from point 1 to 7 all went well.
But I can't flash the rom. i've tried out about 6 various rom's but everything it says fail. on the screen in the twrp always stands unable to mount /data /system /storage
what can I do to fix this problem?
Click to expand...
Click to collapse
|Could someone help please? I am in the same boat and when try to run the above command, I also get this error and no file appears in the sdcard hence cant flash it.
Thanks
My Moto G is working again since one week with stock 4.4.2. I had to do it ain a bit different way...
First, I could get into bootloader and recovery. after several hours my pc recognizes my phone again, but till now I don't know why and how.
Wanted to reflash stock 4.4.2 kitkat again, but this won#t work. so I figured out that after unpacking, I had to replace the gpt.bin with the one from the 4.4.4 stock update. (see down as zip file)
Then I flashed the 4.4.2 stock again to my phone and all went well. It started again. (now I'm on stock recovery)
If you want to do the OTA 4.4.4 Update, there have to be a few things on your phone, otherwise update always fails.
1. if you have x-posed frameworks installed - uninstall it completely
2. if rooted, go into super su preferences and activate unroot all
3. do not activate developper options, or if done before, just uncheck the mark
4. you must be on stock recovery!
5. restart your phone
6. now search after update in about phone.
if bootloader is unlocked - doesn't matter - can stay unlocked
with me it first installed the 176.* OTA because my flashed stock was still 175.*
this went well, then again searched for update and 210.* (4.4.4 kitkat) could be downloaded ota. after it was done, click to install and it should work well - took a bit time.
now you are on stock 4.4.4, but without root atm.
if you want root back - now flash the newest twpr recovery 2.7.7.1 to phone, because here an OTG USB stick will be also recognized - OTG cable needed before. (don't need to push files first to phone)
copied before the su.zip to usb stick and sticked it to phone, then go into recovery. here you can install super user or better su.zip. restart phone and you got your root back on 4.4.4 stock kitkat rom
I solved this issue with twrp sideload.It worked great.
Thanks it worked for me..BUT !!!
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Ysharief said:
Hi and thanks a lot.. it worked for me but you have to add some more option for who are still having troubled in unbricking. like i had..
but it can't be done without your method as on OP..
how i got bricked !!! my Moto g dual (indian)
i tried to downgrade from 4.4.4 to 4.4.2 to flash custom Rom and got system partition corrupt.
again i tried to flash stock images but no use, actual problem was System and data was not formatting.
even if you try million times and you can never successfully flash stock images without error..
however i was checking many threads in xda to resolve this problem but couldn't figured it out, as i was not new to XDA i had confidence that i can come out from this issue. until this thread gave me a hint but not a solution but still this thread is a part of the solution
let come to the unbricking method (only for those who cant flash Stock firmware from fastboot)
Reboot to fastboot..
flash Philz recovery first. get it from here.. http://forum.xda-developers.com/showthread.php?t=2639626
better to use Kernel Flasher by my old buddy Ghostfreak NB http://forum.xda-developers.com/showthread.php?t=2214724,
you just need to extract and copy the recovery to extracted kernel Kernel_Flashing_Tool_v2.0 in IMG folder and run kernel Kernel_Flashing_Tool_v2.0.bat.
press 1 and it will flash recovery, press enter it will reboot to Philz recovery,
now format System, data and whatever you can!!\
next reboot to Bootloader from Recovery,
and then follow procedure as OP
if you want to flash stock rom get from here http://forum.xda-developers.com/moto-g/development/4-4-3-moto-g-stock-rom-t2804891 and adb push as advise by OP. now you have stock rom running without any issues
Edit..
You can also flash custom ROMs with ease.
Note you better flash recovery through kernel flasher tool..
Click to expand...
Click to collapse
I get this error
When im typing adb push AOSP ( i renamed to that name ) /sdcard/ attacks me this: not found. Any help?:crying: Plez :c
eg0097 said:
So you've bricked your phone. Well as long as the boot loader works then your "brick" is just a soft-brick. Follow this simple guide and flash a custom rom in a couple of minutes. I am not claiming ownership of this method, but its the first time Ive seen it and it helped me so here Good Luck!
Download the attachments.
Unzip both files to a folder on your desktop.
Run the adb setup file and press (Y) all 3 times.
Next unzip the twrp.zip folder. Then flash the twrp recovery by using the "fastboot flash recovery twrp.img" command. Make sure phone is in fastboot mode.
Next boot the phone into the recovery and select advanced. Then click on terminal command and navigate to the /sdcard/ folder.
Lastly click "select" on the bottom right corner.
Now download whatever rom and gapps you would like to install on your phone and rename them to something short. Then open a command prompt at the directory where the rom and gapps are. In the command prompt enter these commands "adb push NAMEOFROM.zip /sdcard/" and "adb push NAMEOFGAPPS.zip /sdcard/".
The command prompt will not show change for a few minutes. After you notice the command prompt is ready for the next command it is okay to exit it.
Now just flash the rom and gapps normally and hopefully your phone will be okay.
Need any additional help? Feel free to ask This should work on all Moto G models that have a TWRP image and have a bootloader unlocked.
Click to expand...
Click to collapse
I haven't actually bricked my phone but looks like my ROM.
So, I am trying to make a ROM previously in First Built the ROM didn't even wrote System [That was my fault as I wrote the the 'system' folder in Zip as 'System' and in update scripts 'system' to be extracted in '/system']
But , now the ROM has written /system but remains on Warning Boot loader Locked screen and starts to warm up I have tried Installing Kernels to fix it but no luck please help.
Device->Moto G Falcon XT1033
ROM Details->Custom ROM based on stock 5.1
Priority of problem->5 ,as I use MultiRom and have this Custom ROM as Secondary and CM 13 as primary ,but suggest a fix ASAP .
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
@Sid_Sun - Flash the latest factory firmware image for your model. Once that boots, proceed to custom ROMs if desired.
Factory Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Sid_Sun said:
My device is booting up I am trying to make a ROM which is not booting and the booting method is by MultiRom the not booting ROM is as secondary so I can use CM 13 as primary but not boot my Custom ROM I want a fix to that issue.
Click to expand...
Click to collapse
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
lost101 said:
The MultiROM thread would be the place to ask:
http://forum.xda-developers.com/moto-g/development/modmultirom-v30wip08-01-2014-t2997071
I have no experience with MultiROM, but I believe a Kernel with kexec-hardboot support is required.
Click to expand...
Click to collapse
This isn't MiltiRom's Fault probably but nvm I will flash The Custom ROM as primary and see how it goes .
Friend in step 3 you say "Run the adb setup file and press (Y) all 3 times." But what is the file?
In the list there are only 2 to download files
adb-setup-1.3.zip
twrp.zip
Where do i put the command in the 4th step?
Please help
Notice: Rooting your device will break OTAs because they require an unmodified system, so you might want to check for updates before rooting your X. However, there is a workaround:
Boot into TWRP via step 5E below, but DO NOT flash it (step 5D)!!
Do a backup of your completely stock, unrooted ROM
Root the device by flashing SuperSU...zip
When an OTA hits, you can get it by doing this:
Boot into TWRP again without flashing it (same as step 1 above)
Restore your stock, unrooted ROM (from step 2 above)
Apply the update from stock recovery
Backup the unmodified ROM with the update if you want, then re-root as above.
Note: You will lose any changes, mods or app data since you did the backup, but hey, at least the OTA is applied.
If you get stuck with an update that won't flash and you haven't backed-up your unrooted ROM as above, look here:
[Guide] How to Install OTA's with TWRP, and please hit thanks for @SpiritBreak3r :good:
_____________________
Disclaimer: Rooting does not void the OnePlus X’s warranty, though damaging your hardware (i.e., burning up your CPU by overclocking, hardbricking the device) will. You proceed at your own risk! I accept no responsibility for what you do with your phone. Follow the directions closely, and the odds are you will succeed without any trouble. If you are not sure what you are doing, do some more research before you try. If you get confused with terminology, try looking here for answers or Google it. If you get stuck, post a question in the thread—we're here to help you.
Preliminary steps
1. Make sure that your phone is always charged above 50%!!!
Running out of battery in the middle of flashing something could brick your phone.
2. Make sure that your computer can properly communicate with the device:
We will be issuing commands to the phone from your PC via the USB cable using Android’s SDK tools, in particular ADB and fastboot. If you have not done so already, you must install the following on your Windows computer for this to work:
Java runtime
The Universal Android ADB Driver for Windows.
SDK tools for Android (alternately just ADB & fastboot). Remember where this is installed on your harddrive for later!
You can verify the connection between your PC and phone by running the following procedure:
A. With the phone booted normally, connect it to your computer with the USB cable.
B. Enable Android debugging by going to Settings > About phone and tapping on “Build number” 7 times.
C. Go to Settings > Developer options and check “Android debugging”. A dialogue box will appear asking you to authorize your computer’s RSA fingerprint. Click “Always allow...”
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
D. Open a command prompt in Windows and navigate to the folder where you put SDK tools for Android (ADB & fastboot) above.
E. Type the following command:
Code:
adb devices
You should get a return like this:
If you cannot get the connection to work:
1. Check your USB connection, then verify that Android debugging is enabled in settings and that your computer’s RSA fingerprint has been authorized.
2. Still not working? Open Device Manager in Windows and make sure that you don’t have a yellow exclamation point next to something like “Android Device” or “One.” This would indicate a driver problem that must be resolved. Try re-installing the Universal Android ADB Driver for Windows, and make sure to restart your computer. Once you’ve rebooted, if you still have a yellow triangle, right-click on the device and select “Update Driver Software,” then “Search automatically for updated driver software.”
3. If you still have a yellow exclamation point, then try forcing the driver to install:
In Device Manager, right-click on the device and select “Update Driver Software.”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “ADB Interface” from the list
Select manufacturer “Google”
Select “Android Testing Interface Version xxx”
Click “Next.” If you get a warning, select “Yes” to continue and wait for the driver to install properly.
3. Know how to enter “fastboot mode” on the OnePlus X
To root the device, you must be competent at booting it into fastboot mode. There are two ways to accomplish this:
Power off the phone. Then simultaneously hold down the volume up & power buttons until it vibrates. When done correctly, you will see the words “Fastboot Mode” on a black screen. If not, you dumb-thumbed it, and the device will boot normally into Android. Power off the device and try again.
With the phone running Android normally and Android debugging enabled (see above), open a command prompt in Windows, navigate to the folder where you installed SDK tools (ADB & fastboot) and type:
Code:
adb reboot bootloader
Rooting the OnePlus X
There are three essential steps to rooting the device:
Unlock the bootloader
Flash or boot into TWRP custom recovery [For OxygenOS 3.1.3 use TWRP blu_sp★rk r175]
Flash SuperSU...zip from recovery [For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta]
However, we're going to add a few more to protect your data and device in case something gets borked.
1. Backup your phone’s data
Unlocking the bootloader will involve doing a factory reset resulting in the loss of all accounts, emails, texts, apps and app data, pictures, music, etc. on the device. Move anything you need to keep onto your PC or a cloud service like DropBox.
2. Unlock the bootloader
2A.Go into Developer Options and enable bootloader unlocking
2B. Boot the device into fastboot mode. (Simultaneously hold down the volume up & power buttons until it vibrates.) You should see a black screen with the words “Fastboot Mode”.
2C. Plug in the USB cable.
2D. Verify that your device is connected with this command:
Code:
fastboot devices
You should get a return like the image above under Preliminary Steps
2E. Unlock the bootloader using the following commands:
Code:
fastboot oem unlock
The device will unlock the bootloader, erase all user data and reboot itself into Android. You will have to set up everything from scratch.
3. Re-enable Android debugging
3A. Re-enable Developer options by going to Settings > About phone and tapping on “Build number” 7 times.
3B. Go to Settings > Developer options. Check “Android debugging” and re-authorize your computer’s RSA fingerprint.
4. Download SuperSU zip
4A. Head over to Chainfire’s CF-Root thread and download the SuperSU access management tool from the “CWM / TWRP / MobileODIN installable ZIP” link. It will probably called something like UPDATE-SuperSU-v2.XX.zip. This zip file will root your device and install the SuperSU access management app in one smooth motion. Hit the thanks button for Chainfire or donate to his Paypal account and buy him a Coke.
NOTE: For OxygenOS 3.1.3 use SuperSU v2.78 SR1 beta
4B. Copy UPDATE-SuperSU-v2.XX.zip to your phone’s SD card.
5. Flash TWRP custom recovery
5A. Download TWRP recovery.
NOTE: For OxygenOS 3.1.3 use TWRP blu_sp★rk r175
5B. Place file you downloaded above to the location where you installed SDK tools (ADB & fastboot).
5C. Boot the device into fastboot mode and connect it to your computer with the USB cable.
5D. In this step, we will replace your stock recovery with TWRP recovery.
Note: This step is optional. If you want to root but preserve stock recovery, skip straight ahead to step 5E below. Thanks @rockuppl for the reminder. :good:
Open a command prompt in Windows and navigate to the folder where you installed SDK tools (ADB & fastboot). Type the following commands:
Code:
fastboot flash recovery twrp-3.0.0-0-onyx.img
5E. Reboot into TWRP recovery with the following command.
Code:
fastboot boot twrp-3.0.0-0-onyx.img
You should now see the custom recovery you just flashed, not the stock recovery.
6. Backup your stock ROM before making any changes
In TWRP press “Backup.” <--- See how simple this is???
Don’t be a noob—backup your device!!! Right now we don't have stock boot debuggable image files for the OnePlus X, so borking your device could leave you with a nice paperweight until we do. :crying: Restoring from a backup in recovery is easy, and only works if you've backed-up first
7. Root the device
7A. The device should still be in recovery from step 6 above. Go back to the main menu and press “Install,” find UPDATE-SuperSU-v2.XX.zip on the SD card, then flash it.
7B. Reboot the phone. It is now rooted!
7C. Go to the app drawer and open SuperSU. Update the binary if prompted. Its icon looks like this:
7D. Download and install Root Checker from the Play Store to verify that you have root access.
Yes I already own the phone and I see the bootloader unlock switch in dev options. I also checked the stock recovery which gives options to flash files from phone memory or otg. So it must be fairly easy. But I still don't want to risk it without it being tried and tested. If there were a custom recovery I could have also backed up the factory image. Only choice is to wait and see I guess
I could try today evening... will update here.
@CafeKampuchia
Is it ok to flash supersu.zip with stock recovery.
Before flashing supersu.zip, will unlock bootloader . Will follow the guide from oneplue two procedure to unlock..
Flashing supersu is safe on hundreds of devices, but I don't have the X so I can't say one way or the other.
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
CafeKampuchia said:
I wouldn't try flashing a recovery for another device, especially if the stock recovery isn't available.
I'm surprised that supersu wouldn't flash from stock, though.
Click to expand...
Click to collapse
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Knockys said:
I tried the OnePlus One tutorial to unlock bootloader and root it thanks to this guide.
When it comes to install TWRP, adb tells me it's ok but when I boot into recovery, it's the "official" one that show up.
Even from this recovery, I tried to install the SuperSU.zip, but it keeps telling me it failed, so I think I'll just wait for someone to do it correctly
Click to expand...
Click to collapse
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Knockys said:
Well I thought that TWRP was for all devices and I already went to the stock one before installing TWRP without success to flash SuperSU.
But apprently, installing TWRP the way I did wasn't the right way because I still boot to the stock recovery :/
Click to expand...
Click to collapse
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
CafeKampuchia said:
No, TWRP is definitely not for every device. You have to use the version made for your specific device.
Click to expand...
Click to collapse
My bad then ahah
mjose said:
Hi, after unlocking bootloader, you are not able to update/flash supersu.zip from stock recovery? right?
if it so, then we need to wait for custom recovery to flash root.
Thanks.
Click to expand...
Click to collapse
Yes it fails on stock recovery, we'll have to wait for a custom one indeed...
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Savya said:
THIS WORKS! But beware using the recovery imagine provided there as in is in Mandarin, not English. Other than that it works fine! Already rooted
Click to expand...
Click to collapse
Hey i need your help, i installed the custom recovery in Mandarin but i don't understand anything! Could you please tell me where i should go in this recovery to wipe dalvik cache and flash super su? Step by step? Thanks!
Works for me too ! I'll try to install Xposed now ahah !
Hope they'll release TWRP in English soon !
EDIT : Xposed installed and working ! For those who don't know how to do, see here
mjose said:
Hi, finally its available in oneplus forum
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/
Thanks.
Click to expand...
Click to collapse
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
CafeKampuchia said:
I'll update the OP, but I won't make it a noob friendly guide until we have an English TWRP from a known/trusted developer.
Edit: I tried thanking your post, but I'm out of thanks for the day--8 post limit
Click to expand...
Click to collapse
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Savya said:
I've requested the OP for an English version and hopefully he'll post a link soon.
And that's okay you can thank me later xD
Click to expand...
Click to collapse
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
ukanth said:
I have english version repacked from original source
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
Click to expand...
Click to collapse
Just flashed it now!
Confirmed that its working and its in English!
Thanks a ton mate!
Also do i have your permission to post your link in the oneplus forums? As there are many users there too waiting for an english version.
@ukanth : shared the recovery on my post on the OP forums
https://forums.oneplus.net/threads/...om-recovery-root-take-efs-backup-more.401713/