Database Info

[Q] My phone bricked. Need help please..

My phone is unlocked and rooted. My problem is that when I go to FASTBOOT MODE, then go into RECOVERY, then when I press 'apply update from /sdcard' it shows nothing in there. So, I just stuck and unable to flash any rom at all. I tried to go into the SD card through my computer to install a ROM so that I have something to flash, but nexus s has only internal storage. Please help?

Hi
Hi, I bought my nexus s, immediately after I tried to root, and failed, this left me in the same situation as you.
You NEED to install the adb drivers, and boot using odin files. It was pretty tricky but i got there in the end, i was bricking it too , but dont worry, there's a 98% chance its not bricked, ill find the files for you now...

Go to mount drives and mount your storage from there. That's what I did.

Right, first of all, boot into the bootloader on your Nexus S, and i'm assuming that all your drivers are working fine because you have already unlocked your bootloader.
Place the files in the zip download inthe following places
WIN32bitOS: Program files/Android/Android-sdk/tools
WIN64bitOS: Program files (x86)/Android/Android-sdk/tools
Next, open a command prompt, and type in the following commands, (C: is your windows installation hard drive letter, leave as default if you dont know what this means)
if your 32bit type this w/o quotes "cd C:/Program files/Android/Android-sdk/tools
64bit "cd C:/Program files (x86)/Android/Android-sdk/tools
and click enter.
Next you want to make sure that your Nexus S is in bootloader mode, connected to your pc.
Type the following.
fastboot flash boot boot.img
[click enter & wait until it says successful]
fastboot flash recovery recovery.img
[click enter & wait until it says successful]
fastboot flash system system.img
[click enter & wait until it says successful]
fastboot flash userdata userdata.img
[click enter & wait until it says successful]
Reboot and you should go into android 2.3
Next time make a nandroid backup in clockwork mod!
Download link : http://www.megaupload.com/?d=GI9P4F5I

cdaly985 said:
Right, first of all, boot into the bootloader on your Nexus S, and i'm assuming that all your drivers are working fine because you have already unlocked your bootloader.
Place the files in the zip download inthe following places
WIN32bitOS: Program files/Android/Android-sdk/tools
WIN64bitOS: Program files (x86)/Android/Android-sdk/tools
Next, open a command prompt, and type in the following commands, (C: is your windows installation hard drive letter, leave as default if you dont know what this means)
if your 32bit type this w/o quotes "cd C:/Program files/Android/Android-sdk/tools
64bit "cd C:/Program files (x86)/Android/Android-sdk/tools
and click enter.
Next you want to make sure that your Nexus S is in bootloader mode, connected to your pc.
Type the following.
fastboot flash boot boot.img
[click enter & wait until it says successful]
fastboot flash recovery recovery.img
[click enter & wait until it says successful]
fastboot flash system system.img
[click enter & wait until it says successful]
fastboot flash userdata userdata.img
[click enter & wait until it says successful]
Reboot and you should go into android 2.3
Next time make a nandroid backup in clockwork mod!
Download link coming in 9 mins... data uploading
Click to expand...
Click to collapse
hi cdaly, can you point me to some information on how to install nandriod backup and making/restore a backup right after installing CWM (right after "unlocked" but didnt install Super user yet)?

Yeah
Yeah sure,
Root your phone, go to market place, download rom manager. Open the app and click the button that says, Fash Clockwork Recovery.
Shut down your phone when the operation has completed. Go inot bootloader mode, click recovery. Navigate to backup and restore. Go into backup and restore, click backup. Voila.
If you ever need to restore do the same but click restore. Pretty simple when you know what to do
If this has left you confused, look around on XDA/google, there are a ton of guides
Link added!

Thanks, appreciate it.

Thanks for that. I am using mac computer. Would it be the same typing command for mac as you had mentioned?

cdaly985 said:
Yeah sure,
Root your phone, go to market place, download rom manager. Open the app and click the button that says, Fash Clockwork Recovery.
Shut down your phone when the operation has completed. Go inot bootloader mode, click recovery. Navigate to backup and restore. Go into backup and restore, click backup. Voila.
If you ever need to restore do the same but click restore. Pretty simple when you know what to do
If this has left you confused, look around on XDA/google, there are a ton of guides
Link added!
Click to expand...
Click to collapse
Thanks very much cdaly.. I am just a bit confused regarding phone is rooted or not.
I got to the point flash recovery was sucessfuly in command prompt, but when i try to install "su-2.3.6.1-cd-signed.zip" from SD card, it wasn't successful, as in there is no "superuser" icon after reboot and i have tried wifi tether and it says my phone is not root.
Now i havent tried "su-2.3.6.1-ef-signed.zip" because i accidently bricked my phone for some stupid things i did. but my phone is NOT root as long as I don't see the superuser program right?
I thought nandroid is an actual program but it just means backing up through bootloader?
Thanks for all your help!!!

Thanks very much cdaly.. I am just a bit confused regarding phone is rooted or not.
I got to the point flash recovery was sucessfuly in command prompt, but when i try to install "su-2.3.6.1-cd-signed.zip" from SD card, it wasn't successful, as in there is no "superuser" icon after reboot and i have tried wifi tether and it says my phone is not root.
Now i havent tried "su-2.3.6.1-ef-signed.zip" because i accidently bricked my phone for some stupid things i did. but my phone is NOT root as long as I don't see the superuser program right?
I thought nandroid is an actual program but it just means backing up through bootloader?
Thanks for all your help!!!
Click to expand...
Click to collapse
I dont know if NANDROID is a program or not, it just use it via clockwork mod recovery menu and it works so I'm not complaining aha
If you want to root your nexus s, download this zip file and extract, make sure that your nexus s is in bootloader mode and double click "install-superboot-windows" Bingo, you have root.
Thanks for that. I am using mac computer. Would it be the same typing command for mac as you had mentioned?
Click to expand...
Click to collapse
It wouldn't hurt to try but I dont think so. If you can go into boot-camp or use a friends PC. Or you can try this.
Change your folder to the plaform-tools folder. I dont know how to do this, just referencing off of http://rootzwiki.com/wiki/index.php/Samsung_Nexus_S
Next type
"./fastboot flash boot boot.img"
"./fastboot flash recovery recovery.img"
"./fastboot flash system system.img"
"./fastboot flash userdata userdata.img"

Hi cdaly985
I'd tried it and it works 100%. And, just to share for mac to add on the command "./fastboot-mac ....". I am really impressed with your help. Thanks very very very much.

Hi cdaly985
Now everything is ok with the phone except that it won't be able to go into recovery mode. I had tried by using Rom manager v.4.. and also by pressing vol + power, all failed.
Please help me on this problem. Thanks.

[SD CARD][HOW TO] Cant Mount SD Card or SD Card Corrupted

For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.

So if I got this right if I have busybox already I only have to do is step 7.

Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium

Step 4, a quicker way: adb shell su , get you into shell as root right away

AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.

Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?

AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.

Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.

AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.

Updated with a link to another good tutorial about pushing ROMs to the phone

Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.

Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.

AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!

AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium

$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps

Dude add S3 stock recovery please.

Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.

AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.

Help, Moto g won't boot up any rom

I unlock the g bootloader got it to root I have the latest cwm recovery been trying different ones also, but some how when I try to install any rom that's out there it won't boot up it only stays on the boot screen . Any ideas

Me too
I have this problem too.

Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.

forgotter said:
Guys, please search the forum before posting, so your issues would get resolved quickly.
OK, Now towards your problem.
A lot of people are getting the same error and the results from corruptioning of /data. First try factory reset from fastboot, then reboot. If it doesn't help then do a factory reset again and reboot your phone. If doesn't seen to help either then the only option left is to flash stock firmware through PC. Search the forum and you will get the desired result. Beaware that you will end up losing all your apps and SD card data.
Click to expand...
Click to collapse
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem

chente323 said:
I have factory reset from fastboot a couple of times also been Goin to stock a few times, been searching everywhere I haven had any luck the phone just been doing the same thing all the time.
I have rooted, install roms, an customized over 20 android devices I have own an never had this problem
Click to expand...
Click to collapse
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.

forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
This is the same thing a friend told me to do we did it had no luck Did it 2 times just in case I dint do it right the first time

Moto g not booting up.
I hope you have an unlocked boot loader.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC rename it to "CM.zip" and extract the contents to adb folder (adb folder should be in C drive i.e. C:/adb ). You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push C:/adb\system /system/"
"fastboot flash boot boot.img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push C:/adb\boot.img /data/"(to verify whether /data is writable or not)
"fastboot push C:/adb\boot.img /cache/"(to verify whether /cache is writable or not)
"fastboot push C:/adb\CM.zip /data/media/0/"(to push the CM11rom to sdcard to flash it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data. Then go to wipe and wipe /data and /sdcard and then again push CM.zip to /data/media/0/. If you don't see this error, then choose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11.zip or you can flash stock firmware through mfastboot.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.

forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Thanks I will give it a try tomorrow since it's wife phone I don't have it w me now. I'll get back at u let u know if it work

forgotter said:
So here's a detailed instruction for you to follow.
1. In fast boot mode connect phone to PC.
2. In CMD (adb) in PC type the command "fastboot devices" without quotes and post the reply to me.
3. In the CMD, type the command "adb erase userdata","adb erase cache" without quotes. (It will wipe all your data and SD card)
4. Now download the firmware (new firmware download it in case there may be issues with the old one you have downloaded) and also TWRP-2.7.0.0.falcon by dhacker. Copy both the files in the adb folder.
5. Rename the twrp-2.7.0.0.falcon.IMG to recovery.img
6. Connect your phone to PC in fastboot mode and flash the recovery by topping command "fastboot flash recovery recovery.img"without quotes.
7. On your phone scroll to recovery option and long press volume up key until the phone vibrates. The phone will boot into recovery.
8. In recovery goto advanced-file manager. And check whether your /datafilleris empty or not (it will be empty)
9. In recovery go to wipe and wipe /system /data /cache. Next reboot your phone to boot loader mode.
10. Flash any firmware from your PC through fastboot. Then reboot your phone.
If it doesn't help either reply to me, there's other workaround too.
Click to expand...
Click to collapse
Hi forgotter! I have the same problem... won't boot with any ROM. I've followed your instructions but stil stucked on the boot logo. I will try the second method you provided now, hope that works :crying:

@notnowjohn
Didn't know why first method didn't worked for you but the second one would definitely work. If you get any error then reply to me, and yes in my second method post by mistake there are some extra space added after full stop (.) e.g. in boot. img (it is boot.img ) do please avoid that.

forgotter said:
I hope you have an unlocked boot loader and have TWRP(2.7 by dhacker) installed.
The first thing you need to find out is that are your phone's partition writable and readable.
1. Download the latest CM11 nightly to your PC and extract the contents to adb folder. You will get boot. img , system (folder), and others.
1. connect your phone to PC in fastboot mode.
2.In adb type the below commands one by one without quotes. And let one command get processed before typing other.
"fastboot devices" (in response it must show you something like TJ9*****)
"fastboot erase userdata"
"fastboot erase cache"
"fastboot push system /system"
"fastboot flash boot boot. img"
"fastboot flash recovery recovery.img"(flash the philz recovery now)
"fastboot push boot.img /data"(to verify whether /data is writable or not)
"fastboot push boot. img /cache"(to verify whether /cache is writable or not)
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery)
Then boot your phone to recovery. And see the logs, it should show
/system mounted
/data mounted
/sd-ext error mounting /sd-ext
/cache mounted
If it shows /data can't be mounted or error mounting /data.Then go to wipe and wipe /data and /sdcard. If you don't see this error, then chose to wipe to install a new rom. After this remount /system /data /cache and flash the CM11. zip.
This method will definitely work since I, myself had this very same issue and got it resolved the very same way.
P.S. Try this method and only of you get some error then reply as I an sure it will solve your issue.
Click to expand...
Click to collapse
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone

notnowjohn said:
Hi again Sir, I've followed all the instructions, but when I check the logs it says "Can't Mount" of "Can´t open" for everything.
This is what i saw during the proccess
"fastboot devices" (in response it must show you something like TJ9*****) T08830R89M
"fastboot erase userdata" OK
"fastboot erase cache" OK
"fastboot push system /system" Doesnt do anything, show adb commands
"fastboot flash boot boot. img" I deleted the space between . img. Phone says Mismatched partition size (boot)
"fastboot flash recovery recovery.img"(flash the philz recovery now) Phone says Mismatched partition size (Recovery)
"fastboot push boot.img /data"(to verify whether /data is writable or not) Doesnt do anything, show adb commands
"fastboot push boot. img /cache"(to verify whether /cache is writable or not). Again deleted the space between . img. Doesnt do anything, show adb commands
"fastboot push CM.zip /data/media/0/"(to push the CM11rom to sdcard to flag it through recovery) Doesnt do anything, show adb commands
Its anthing more I can do??
Thank you very much! I can believe I brick my phone
Click to expand...
Click to collapse
Don't worry your phone is fine.
Whenever adb shows m mismatched partition it's fine and usual.
I understand your problem now, I just think if I your device now , I would have repaired it within minutes. Never mind, follow the below steps .
Download the philz recovery to your PC, flash it through fastboot on your phone. Then go to recovery on your phone immediately and choose wipe-wipe data and sdcard. And then flash the stock firmware through mfastboot or install any ROM through recovery.

Anyone report which step what must i do to solve this prob

sinkadorable said:
Anyone report which step what must i do to solve this prob
Click to expand...
Click to collapse
Read post #7 on page 1.

I cant push system to device. What tools must be i have?

If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.

pluiz halp!
forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:

jamiethomaswhite said:
I'm having similar issues as everyone else here. I unlocked my bootloader following Motorola's instructions on their website, then I used Superboot to root the phone (which I don't think worked as CWM and TWRP kept asking to install SU on reboot). After that I put CM 11 M4 on sdcard and flashed.
This is where it went wrong. I rebooted and got a bootloop, so I looked around online and ended up wiping everything and trying again. It still didn't work so I followed instructions to reflash stock firmware, this didn't work either. By this time the phone had been on ages and went dead. Now it won't turn back on and won't register as charging from USB or from wall plug.
I have no idea what to do as nothing worked before hand and now I can't access it to resolve the issue.
I'm panicking atm because I'm contracted to Virgin Mobile in the UK and this voids the warranty. I just don't know what to do D:
Click to expand...
Click to collapse
Plug the phone to wall charger and leave it to charge for the whole night, the next when you'd restart the phone it should boot up. Sometimes the phone discharged itself to such a level that it didn't have enough juice left to show the battery charging status even.
After that follow instructions from post #7 on page 1 and paste all output commands you see. Well, the phone should boot up.

forgotter said:
If you can't push system to device don't worry , it's of no use at all because you'll format it before flashing the rom. But if you're flashing through recovery then make sure to push CM. zip to /sdcard/.
You need adb tools on your PC, just search Google for adb tools and download it. You need stock firmware of your phone on PC if you'd flash the rom through mfastboot and you need philz recovery ( to flash it on your phone.)
If you can't get anything or don't understand anything then do search the forum for help because all the things are already mentioned and if i had to answer it mostly would be copy-paste. But still if you need help, I am there. Just post your problem.
Click to expand...
Click to collapse
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:

sinkadorable said:
now my phone was stuck on UBL warning message and cannot enter recovery
when i flash recovery fastboot say Mismatched partition size (Recovery) :crying:
Click to expand...
Click to collapse
Mismatched partition size is usual , no need to worry about that. What do you mean by UBL warning message? And yes, after you flash recovery, enter in recovery mode and wipe data and sdcard and then flash any ROM from fastboot.
And if you get into an error or solution doesn't work then post your problem but detailed so I can get to the main cause of the problem.

Problem [BOOTLOADER]

Describing my problem :
Since yesterday my OPO did some random reboots. I was running Paranoid Android and it worked perfectly...
Yesterdayevening after it rebooted another time, my OPO didn't start at all... It seems that my bootloader won't load the OS.
This morning, I did a complete wipe and I've put the stock ROM from the CM site back on my OPO ( XNPH33R signed boot).
-Fastboot works
-Recovery works
-Bootloader won't load OS. ( only the One Plus logo pops up (not the bootanimation)). After that it reboots over and over...
Update 1 17:30 5/10/2014 :
I'm in a bootloop, I have no ROM. I have the TWRP recovery. And the bootloader is LOCKED.
So I tried to unlock the bootloader with the toolkit for the OnePlus one. ( I tried it also manually with cmd).
----WHAT IT DOES in CMD/ Phone-------
In CMD : " OKAY [0.012 s]
Finished. total time : 0.012 s
OPO : It opens up my TWRP recovery but it does not unlock the bootloader
Update 2 19:52 5/10/2014 :
I've been able to unlock the bootloader...
with the command " fastboot oem device-info" , I received :
Bootloader tampered : True
Bootloader unlocked : False ( because the toolkit only did " fastboot oem unlock " , I did an adb sideload with a zip "OnePlusOne-OnlyBootloaderToggle" from the thread
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912. Now my bootloader is back UNLOCKED.
I hope the bootloop will stop when I do a factory / reset.
10:40 6/10/2014 :
I tried several times to flash stock roms from the official site / from the forum. None of them 'work'.
Can someone please help me?? He still bootloops!!! How frustrating thazt is,I tried everything from threads on the forum. Nobody is ansering my thread. Any reason for that ?

My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
From there just flash the ROM like you would flash any other ROM.
Transmitted via Bacon

Failure with E:
timmaaa said:
My suggestion is this: grab one of the recovery flashable versions of CM11S from here, boot into your TWRP recovery and use adb to push the ROM zip to your phone, then use the install function in TWRP to flash it.
To push the zip to your phone you first need to put it in your adb/fastboot folder (wherever you have adb.exe and fastboot.exe located on your PC), make sure your phone is booted into TWRP and connected to your PC, open a command prompt from within your adb/fastboot folder (shift + right click anywhere in the folder, then select open command prompt here), and issue this command:
Code:
adb push <name of file.zip> /sdcard/
*Please note the '<' and '>' symbols are not included in the command.
Transmitted via Bacon
Click to expand...
Click to collapse
Pushing the zip into sdcard :good:
Installing the zip gives a message about E:
example :
something with E: path
E: unable to wipe
E: error executing updater binary in zip 'sdcard/cm11.0... .zip
Proberly more

Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon

timmaaa said:
Are you sure you're attempting to flash one of the recovery flashable zips? What's the full filename?
Transmitted via Bacon
Click to expand...
Click to collapse
cm-11.0-XNPH33R-bacon-signed
Links
1. Recovery flashable zips of the complete ROMz:
XNPH22R
XNPH25R
XNPH33R
From your link
EDIT-----
1. I had flashed the stock recovery back.
2. Did a factory reset
3. Wiped cache
4. Wiped media
5. Flashed TWRP back
6. ADB push zip in /sdcard/
7. Flashed the zip SUCCESSFUL after these steps
I still have a bootloop

Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone

Who can even solve this?...
playya said:
Have you tried to format your internal sd card and flash your zip. Remember if you format though you will lose everything on your sdcard. Make sure you backup everything first if you want to try this. Also if you do this you will have to push your zip back to the phone
Click to expand...
Click to collapse
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?

VictorByttebier said:
My internal storage was already formatted. I just have the TWRP and the zip on my phone.
[Q] In the TWRP recovery menu in 'Advanced' what has to be between Copy Log to SD and Terminal Command? There is a blank spot ,there should be button normally?
How is it even possible i have nothing but the recovery and the zip and I still got a bootloop...
Is there somebody that knows something else that i can try?
Is it possible to flash perhaps with odin?
Click to expand...
Click to collapse
definitely not odin thats Samsung my friend. Partition SD Card is whats missing in TWRP for you. I asked about formatting internal because a similar thing happened to my friend. We had to format internal then adb push recovery and rom and all was well again. If you have tried this recently then my bad but if you have not it wont hurt to try it again in that order
format internal
adb push recovery
adb push rom
reboot
Take a look in here as well http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061

Bootloop fixed
It finally worked!!! How weird that i already found a zip like on the thread but with XNPH33R and also with the persist and recovery.img and flash-all etc... but it didn't work.
Now i just have to update from the settings
At beginning I was convinced that a bootloop could be fixed with factory/reset would do it. Like it always worked on my previous smartphone.
Thank you playya and timmaaa for the responses!:good: You are awesome! See me sitting here with a

ROOT Nextbook Ares 8 with Windows

Update: When you flash the recovery and supersu files make sure to have the remove encryption file on sd card aswell and add it to the list and flash and if you hang at boot screen.. boot into recovery and wipe cache.. reboot.
WINDOWS USERS ONLY.... USE AT YOUR OWN RISK
Make sure you have the proper drivers and make sure you have a real good usb cable... This rar has the usb drivers and the files already in the folder just drop onto desktop and run cmd.exe
Files Needed: http://www.filedropper.com/nocturnaladbfastboot
http://www.filedropper.com/removeencryption
DO NOT FORMAT SYSTEM!!!!!!!!!!!!!
Make sure you are in bootloader or this will not work..
Key combo to get into bootloader or recovery via hard keys.
power off
volume up + power = recovery
volume down + power = bootloader
from bootloader you have several choices to boot, just pres volume down to choose, power to select.
1. To make sure you are connected run command (adb devices) enter
2. Once you see your device run command (adb reboot bootloader) Then..
3. Run command (fastboot boot boot.img) wait for downloading dialog...
4. Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure...
5. once the screen says okay on tablet.. push the vol down button until you see recovery mode and then push power to start twrp recovery..
6. Once in twrp flash SuperSU246.zip and recovery.zip remove_encryption.zip then reboot... you should have root on reboot:good:

Instructions
I think I understand your instructions but I have a few questions.
Am I typing all of the commands on my pc? (- SuperSU)
Step 3 has “Run command “(fastboot boot boot.img)” I see 2 files and so those are two separate commands to run correct?
Step 4 Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure... Again is this 2 commands to run? I see the twrp_recovery.img file but no fastboot flash recovery file?
In step 4 should I be using theses 2 commannds;
fastboot flash boot boot.img
fastboot flash recovery recovery.img

ahunter said:
I think I understand your instructions but I have a few questions.
Am I typing all of the commands on my pc? (- SuperSU)
Step 3 has “Run command “(fastboot boot boot.img)” I see 2 files and so those are two separate commands to run correct?
Step 4 Then run command (fastboot flash recovery twrp_recovery.img) and make sure you have the proper files on sd card.. i put all files in the folder on my sd card to make sure... Again is this 2 commands to run? I see the twrp_recovery.img file but no fastboot flash recovery file?
In step 4 should I be using theses 2 commannds;
fastboot flash boot boot.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
run them just as there posted make sure all files on the sd card and you should be fine..

Thanks for your reply. Those commands are run on the PC in the cmd window right? and I copied the files in the directory to my SD card I installed on the nextbook should that be a problem. Shoul this be the SD card or internal memory? I didn't run the commands the way they were written last night & didn't have success. I am getting hung up on 3. Run command (fastboot boot boot.img) wait for downloading dialog...
My pc and tablet are seeing eachother but they both say waiting, I don't think my files are being seen.

ahunter said:
Thanks for your reply. Those commands are run on the PC in the cmd window right? and I copied the files in the directory to my SD card I installed on the nextbook should that be a problem. Shoul this be the SD card or internal memory? I didn't run the commands the way they were written last night & didn't have success. I am getting hung up on 3. Run command (fastboot boot boot.img) wait for downloading dialog...
My pc and tablet are seeing eachother but they both say waiting, I don't think my files are being seen.
Click to expand...
Click to collapse
Make sure you uninstall and reinstall the usb drivers in the folder and run the cmd from the folder and if still nothing try a new cable and usb port... when you run command adb devices do you see your listed as numbers and some letters?

After the adv devices command it gives me; listed devices YFGV0815002950 device. That should be the tablet, it’s the only thing attached w/usb & it also shows up in explorer.
After the adb reboot bootloader cmd the tablet reboots into bootloader with “Fastboot CMD WAITING “ at the bottom of the screen.
After the fastboot boot boot.img cmd my pc cmd rompt says <waiting for device> and my tablet stillhas the Fastboot screen mode & FASTBOOT CMD WAITING at the bottom of the screen
That is as far as I get. I copied all of the files in your download link in the .rar format and to a directory on my internal tablet storage. It seems like the tablet is waiting for a file but I don't understand why.

ahunter said:
After the adv devices command it gives me; listed devices YFGV0815002950 device. That should be the tablet, it’s the only thing attached w/usb & it also shows up in explorer.
After the adb reboot bootloader cmd the tablet reboots into bootloader with “Fastboot CMD WAITING “ at the bottom of the screen.
After the fastboot boot boot.img cmd my pc cmd rompt says <waiting for device> and my tablet stillhas the Fastboot screen mode & FASTBOOT CMD WAITING at the bottom of the screen
That is as far as I get. I copied all of the files in your download link in the .rar format and to a directory on my internal tablet storage. It seems like the tablet is waiting for a file but I don't understand why.
Click to expand...
Click to collapse
there is a problem after you boot into bootloader i had the same problem for days.. i just played with cables and drivers use the ones inside the folder they worked for me...

I'll keep trying. It has be the drivers.

I followed these directions to a T, but for some reason the device can not read the SD card while in recovery. Any clues as to why this is happening?

So I was online shopping for my first tablet when I came across this thread. . . It led me down to the local WALMART and I picked one up. I successfully completed the process, or so I thought. I went to reboot after flashing everything, and twrp says " no OS installed! Are you sure you want to reboot?"
What did I do wrong?

I have tried several times to download the remove encryption file must be a bad link or something. Is there another download site or can someone send to me plz

Nvm I ran it over with my car because I couldn't get the download link to work. If anyone wants it for parts send me a message. Its brand new only been used maybe 2 weeks. The most wear and tear on it was my Buick regal hitting it at about 45 mph in a pissed off rage. don't think all the insides are smashed tho. Possibly a good fixer upper

Is this fastboot and adb custom versions?
I have adb and fastboot in my path (runable from anywhere)..
ADB says the version release is the same number.
do I need to use your versions for the tablet?
http://www.filedropper.com/removeencryption
does not work, link changes to http://www.filedropper.com
and asks me to upload a file?

Link working sorry...
http://www.filedropper.com/roottwrpremoveencryption
TWRP 3.0
http://www.filedropper.com/twrp3recovery

C:\Users\Fuzzy\Desktop\root_twrp_remove_encryption>fastboot flash recovery twrp_
recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (15558 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.830s
C:\Users\Fuzzy\Desktop\root_twrp_remove_encryption>
Copied the two zip files to both a 4gb fat32 formatted microsdhc
and internal storage via MTP to the device then ran ADB 1.0.32
and rebooted to bootloader. (adb finds device fine)
fastboot devices reported device number fastboot.
flashed TWRP in package you uploaded yesterday.
it says both internal and external cards are empty?
internal card has files that the manufacturer put there,
but TWRP can't see them?
What am I doing wrong?
Any ideas how to fix?
log says 'unable to find crypto file'
and it couldn't mount /data or /storage filesystems
>>>
installed TWRP3 that allowed the installs although it still
could not open /data. It did find the external card installed
from there.
I am guessing the forced encryption made /data unreadable.
hopefully now with the encryption removed the /data
partition will be readable.
>>>
I reran recovery to check and log now has no failures!!!
I'm guessing the changed boot.img fixed the issues it was having.
*smiles*

cant get files. takes me to a site to sign up. can you dropbox link them please?

I just won this tablet in a contest. Anyone have the remove_encryption.zip file? I managed to find all of the other required files but none of the links in this thread work anymore.

whats the problem with the links? site says free but wants me to pay. losing my head here, and it seems im not the only one

Bad filedropper links
Filedroper no links available, asks us to register and pay for stuff that's not there anymore
can you like put them on Google drive, SendSpace, DropBox, Mega.nz and/or ZippyShare