Related
How to unbrick your ouya as long as adb is on and you have a clockwork mod recovery installed
I bricked my ouya recently so i just thought i would share this,it's going to work even if you completely erased all data and all caches in your clockworkmod recovery,this includes erasing sd card and even if you have boot menu and it won't show your nand as green lit but red lit,the nand is the chip that has the firmware on it if your not sure what it is.
This is for xp but i think it will work in other windows versions but don't quote me?It took 48hrs of perseverance for me to figure this out, And then to write this, i had to flit from page to page online copying links and reading it all over again,some comes from memory,other bits of the tutorial i made up my self and sussed it out on my own with no help,i had to click rename and copy file names in places in this tutorial.But it works and it rebuilds the ouya no mater what you did.
You could have erase the memory in clockworkmod completely,even if you wiped the dalvick cache and/or thesd card patition at the same time and/or clicked full factory reset after, no matter what you erased or how you did it even if you used the whole lot of every erase option applied from clockworkmod recovery on your ouya,
This restores it to factory,it even removes the boot menu software that i added and found [email protected] up my ouya completely after trying to add a boot img for the cynagenmod i put on over the top of my system by accident, then killed all data caches erasing them all i even erased my sd card data leaving my ouya completely bare of anything.
This is for others like me that only have the OUYA? next to device in the device manager in windows xp,i had so much trouble getting it going and i found a very quick easy couple of click fix for it,i could then adb command the ouya over a micro usb cable and rebuild it,You need to have the adk bundle for windows installed and the sets of tools needed for the current platforms this maybe api's not sure? just have the ones i use which are 14,16,17,18,19 and the google usb driver you may not need them all i may have more than needed but i don't know so best use what i have as it works for me,i am not going in depth on adding this but you can look here https://devs.ouya.tv/developers/docs/setup for info on the sdk install procedure just get the platforms i have as well as the guides listed platforms to install you'll see a picture of the sdk on this page so just use that as a guide.
So on with the guide then:
STEPS
STEP 1.Turn on ouya and go into clocklworkmod recovery menu and select install from zip then select sideload adb option and leave the console running in this mode please.Go here http://visualgdb.com/UsbDriverTool/ copy and paste that link in a new tab into the address bar and head down the page a little to the bit that says Downloading click the link that says UsbDriverTool-sfx.exe,you then get a page asking to save the file so save it where you can remember.Leave the page open and move onto step 2.
STEP 2. Open a new tab in the browser and paste this link: http://visualgdb.com/tutorials/android/ouya/ into the address bar and hit enter (return key).Now connect the ouya to the pc via micro usb cable and follow step 2. and step 3. from the current webpage you are on.You should now have Ouya ADB device or similar in the device manager meaning it works now.
STEP 4.install powertoy for windows xp don't ask me for a link this is going to be something you have to do as can't remember,it allows command on right clicking a folder this is a much needed thing for this job.
STEP 3. open a new tab in the browser and go here http://forum.xda-developers.com/showthread.php?t=2266629 and download the file named 1.0.68-r1 Download Changelog click the orange changelog writing to download and copy the downloaded file called RC-OUYA-1.2.995-r1_ota.zip by opening c:/ adt-bundle-windows-x86-20140321 or simlarily named folder residing in c: drive and then go into sdk folder then go into platform tools folder and paste the RC-OUYA-1.2.995-r1_ota.zip file in there, return to the c: drive ,then go to the folder called adt-bundle-windows-x86-20140321 or similarily named folder againand then into sdk folder again then highlight the platform tools folder with right click and click on open command window here leave this window open now.
STEP 4. Provided the command window is now open and the ouya was correctly set and enabled from STEP 1 and STEP 2. earlier,and STEP 3.. is completed you should now have the ouya on micro usb with the adb mode enabled and showing up as such in device manager, and you should now be sitting in the clockworkmod recovery in adb sideload mode on your ouya console ,go to the command window you left open in STEP 3. and simply type adb sideload RC-OUYA-1.2.995-r1_ota.zip ,this should now install the zip and after it is done you reboot the console from restart option in clockworkmod recovery and you should boot up fine and will have successfully repaired (unbricked) the ouya.
JOB DONE PHEW!
PHYSC-1 said:
How to unbrick your ouya as long as adb is on and you have a clockwork mod recovery installed
I bricked my ouya recently so i just thought i would share this,it's going to work even if you completely erased all data and all caches in your clockworkmod recovery,this includes erasing sd card and even if you have boot menu and it won't show your nand as green lit but red lit,the nand is the chip that has the firmware on it if your not sure what it is.
This is for xp but i think it will work in other windows versions but don't quote me?It took 48hrs of perseverance for me to figure this out, And then to write this, i had to flit from page to page online copying links and reading it all over again,some comes from memory,other bits of the tutorial i made up my self and sussed it out on my own with no help,i had to click rename and copy file names in places in this tutorial.But it works and it rebuilds the ouya no mater what you did.
You could have erase the memory in clockworkmod completely,even if you wiped the dalvick cache and/or thesd card patition at the same time and/or clicked full factory reset after, no matter what you erased or how you did it even if you used the whole lot of every erase option applied from clockworkmod recovery on your ouya,
This restores it to factory,it even removes the boot menu software that i added and found [email protected] up my ouya completely after trying to add a boot img for the cynagenmod i put on over the top of my system by accident, then killed all data caches erasing them all i even erased my sd card data leaving my ouya completely bare of anything.
This is for others like me that only have the OUYA? next to device in the device manager in windows xp,i had so much trouble getting it going and i found a very quick easy couple of click fix for it,i could then adb command the ouya over a micro usb cable and rebuild it,You need to have the adk bundle for windows installed and the sets of tools needed for the current platforms this maybe api's not sure? just have the ones i use which are 14,16,17,18,19 and the google usb driver you may not need them all i may have more than needed but i don't know so best use what i have as it works for me,i am not going in depth on adding this but you can look here https://devs.ouya.tv/developers/docs/setup for info on the sdk install procedure just get the platforms i have as well as the guides listed platforms to install you'll see a picture of the sdk on this page so just use that as a guide.
So on with the guide then:
STEPS
STEP 1.Turn on ouya and go into clocklworkmod recovery menu and select install from zip then select sideload adb option and leave the console running in this mode please.Go here http://visualgdb.com/UsbDriverTool/ copy and paste that link in a new tab into the address bar and head down the page a little to the bit that says Downloading click the link that says UsbDriverTool-sfx.exe,you then get a page asking to save the file so save it where you can remember.Leave the page open and move onto step 2.
STEP 2. Open a new tab in the browser and paste this link: http://visualgdb.com/tutorials/android/ouya/ into the address bar and hit enter (return key).Now connect the ouya to the pc via micro usb cable and follow step 2. and step 3. from the current webpage you are on.You should now have Ouya ADB device or similar in the device manager meaning it works now.
STEP 4.install powertoy for windows xp don't ask me for a link this is going to be something you have to do as can't remember,it allows command on right clicking a folder this is a much needed thing for this job.
STEP 3. open a new tab in the browser and go here http://forum.xda-developers.com/showthread.php?t=2266629 and download the file named 1.0.68-r1 Download Changelog click the orange changelog writing to download and copy the downloaded file called RC-OUYA-1.2.995-r1_ota.zip by opening c:/ adt-bundle-windows-x86-20140321 or simlarily named folder residing in c: drive and then go into sdk folder then go into platform tools folder and paste the RC-OUYA-1.2.995-r1_ota.zip file in there, return to the c: drive ,then go to the folder called adt-bundle-windows-x86-20140321 or similarily named folder againand then into sdk folder again then highlight the platform tools folder with right click and click on open command window here leave this window open now.
STEP 4. Provided the command window is now open and the ouya was correctly set and enabled from STEP 1 and STEP 2. earlier,and STEP 3.. is completed you should now have the ouya on micro usb with the adb mode enabled and showing up as such in device manager, and you should now be sitting in the clockworkmod recovery in adb sideload mode on your ouya console ,go to the command window you left open in STEP 3. and simply type adb sideload RC-OUYA-1.2.995-r1_ota.zip ,this should now install the zip and after it is done you reboot the console from restart option in clockworkmod recovery and you should boot up fine and will have successfully repaired (unbricked) the ouya.
JOB DONE PHEW!
Click to expand...
Click to collapse
Quick follow up,you can sideload over adb if it's turned on,this applies to standard recovery as wel.So you can unbrick using the adb sideload method above even with a stock ouya to unbrick it guys/gals.
hi!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.
fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/
_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.
hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?
see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...
jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.
Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse
This is a discussion lifted from [Kernel] TRIM: Speeding up the Galaxy S2 Epic 4G Touch d710, as it is not really relevant in that thread.
Dudebowski said:
heimdall shell scripts for backup and repartition worked as expected. Thank you once again, Lanchon, very straightforward.
CWM backup to removable SD, backup internal storage contents to removable sd, remove the removable SD, adb reboot recovery, run backup script, run repartition script, reboot recovery, format every partition, power down, insert sdcard again, restore CWM backup, run lanchon's recovery trim zip.
[attached lanchon's trim/FPbug kernel, and recovery trimmer. note you'll have to mount all the partitions you wish to trim before executing the zip]
However great that was... I went of the beaten trail and tried reformatting my internal storage space (sdcard0) as ext4. Didn't know CWM had added that option... anyhow, it seems I have some permissions issue with the internal storage space now, can't write to it at all. What did I do wrong?
/storage/sdcard0 rwx rwx --x root:sdcard_r
Click to expand...
Click to collapse
I've been trying all morning, but I can't get Heimdall to see my phone. It never shows up in zadig.exe as "Samsung ..." instead my phone shows up as "Gadget Serial Control" and "Gadget Serial". I can not replace the driver for "Gadget Serial Control". I replaced it for "Gadget Serial", but Heimdall still could not talk to my phone. I tried all 3 different driver options. none of them worked. So far I've tried it on my 2 workstation both with windows 8.1. I am going to try to find a Windows 7 PC later and give it another go.
Kjricker said:
This is a discussion lifted from [Kernel] TRIM: Speeding up the Galaxy S2 Epic 4G Touch d710, as it is not really relevant in that thread.
I've been trying all morning, but I can't get Heimdall to see my phone. It never shows up in zadig.exe as "Samsung ..." instead my phone shows up as "Gadget Serial Control" and "Gadget Serial". I can not replace the driver for "Gadget Serial Control". I replaced it for "Gadget Serial", but Heimdall still could not talk to my phone. I tried all 3 different driver options. none of them worked. So far I've tried it on my 2 workstation both with windows 8.1. I am going to try to find a Windows 7 PC later and give it another go.
Click to expand...
Click to collapse
just use linux! a live pendrive would be enough
linux mint cinnamon 64
or simply ubuntu
to install heimdall type this:
sudo apt-get install heimdall-flash
Lanchon said:
just use linux! a live pendrive would be enough
linux mint cinnamon 64
or simply ubuntu
to install heimdall type this:
sudo apt-get install heimdall-flash
Click to expand...
Click to collapse
I thought about that as well. Easier to do that then find a Windows 7 PC for me
It'll have to wait until tonight though. I put off work too long today. I'll report back once I give that a go tonight.
A few suggestions for Windoze compatibility:
Latest Samsung ADB drivers + installer (works in W8.1, and without keeze or whatever that sammy bloatware is)
http://www.modaco.com/topic/361286-...ver-for-mobile-phones-15490-drivers-win-87xp/
Google's official Android USB driver (says it's only for nexus devices, but I've found it has worked for sammy gear too.)
https://developer.android.com/sdk/win-usb.html
Before installing those, you might want to remove the drivers for whatever devices listed as: adb interface, serial modem, gadget, samsung mobile devices. Anything that suddenly shows up when you plug the phone into the PC.
Do this from device manager (winkey+r, devmgmt.msc) and click 'View -> Show Hidden Devices' to see hardware that's not currently active / plugged in. Right click on treelist entry, 'uninstall'
when installing the new drivers, make sure the phone is NOT plugged into the PC. Once installed, reboot, then plug your phone back in. Whatever drivers necessary for connectivity should be activated now.
Neither of those drivers worked for me either. My phone always comes up in the device manager as modem or gadget. With either gadget serial driver or modem driver. The Google driver installed, but never got used.
Time to switch to a Linux live and give it a try.
Kjricker said:
Neither of those drivers worked for me either. My phone always comes up in the device manager as modem or gadget. With either gadget serial driver or modem driver. The Google driver installed, but never got used.
Time to switch to a Linux live and give it a try.
Click to expand...
Click to collapse
I don't think it is in the cards for me. In Linux Mint I also did not get it to work properly. I got initialization errors. I got it to download the current pit once. Then I tried to repartition with the new pit and I kept getting initialization errors. It would not work any more, not even download the current pit again. I tried different cables and usb ports. SIGH.
Kjricker said:
I don't think it is in the cards for me. In Linux Mint I also did not get it to work properly. I got initialization errors. I got it to download the current pit once. Then I tried to repartition with the new pit and I kept getting initialization errors. It would not work any more, not even download the current pit again. I tried different cables and usb ports. SIGH.
Click to expand...
Click to collapse
its ok. every time u use heimdall you need to restart the phone in download mode again. --no-reboot does not mean the phone keeps listening to commands. this is samsung after all
Lanchon said:
its ok. every time u use heimdall you need to restart the phone in download mode again. --no-reboot does not mean the phone keeps listening to commands. this is samsung after all
Click to expand...
Click to collapse
You gotta be kidding....Each time a Heimdall command is run, the phone needs to be restarted back into download mode. How crazy. I'll try again tomorrow then. I made an Ubuntu live flash drive now. I thought maybe I'd have better luck with it. Once again, thanks for the help.
Kjricker said:
You gotta be kidding....Each time a Heimdall command is run, the phone needs to be restarted back into download mode. How crazy. I'll try again tomorrow then. I made an Ubuntu live flash drive now. I thought maybe I'd have better luck with it. Once again, thanks for the help.
Click to expand...
Click to collapse
lol
Lanchon said:
lol
Click to expand...
Click to collapse
Success!
{
"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 ended up using Mint Linux 32bit installed and ran from a USB flash drive. Ubuntu was awful. I haven't used an Ubuntu live distro of it in a while, and I did not care for it. Neither version of Linux I used had proper drivers for my Nvidia 750TI, but at least with Mint I had a full desktop. With Ubuntu it was like working on and old win95 PC with a resolution of 640x480. YUCK!
Before starting this journey, you should already have your phone running CM11 with a current recovery.
Here are my complete steps.
Get files for install after partitioning
Download CM11 nightly, GAPPS, Lanchon's kernel with TRIM (optional), Lanchon's sensor fix v2 and FL24 modem.
Place the above files on the phone's external SD card. Unmount and eject the card.
Get files for partitioning
Download partition files and scripts provided by Lanchon:
http://forum.xda-developers.com/showpost.php?p=58317191&postcount=83
Unzip the file.
Prep live Linux usb drive
Download Linux Mint Cinnamon 32bit no codecs:
http://www.linuxmint.com/edition.php?id=175
Install Mint Linux onto flash drive using rufus-1.4.12:
https://rufus.akeo.ie/downloads/rufus-1.4.12.exe
Prep repartition files and scripts
Boot PC from usb flash drive into Linux Mint.
Place phone into download mode by turning the phone off. Then press power and volume down. When the warning screen comes on, press volume up to continue into download mode.
Plug phone into PC.
In Linux Mint navigate to the folder where you unzipped the partition files and scripts you downloaded earlier. Copy all the files to the Mint "Download" folder. Select the .sh files and right click them and choose properties. Check the box labeled "Allow executing file as a program." I also set both Group and Others access to "Read and Write". Then select the rest of the files and change their permissions as well. I just changed them all to "Read and Write". I do not know if this step is necessary or not, but it is what I did. Why copy the files to the Mint "Download" folder you ask. Well because I could not change their properties where I had originally saved them. That's why.
Next right click on the above "Download" folder and choose open in terminal. Now you should have a terminal window open at the locations of those files. You can verify it by typing in "ls". You should see a list of the files.
Install Heimdall
In the terminal window install Heimdall, the command is:
Code:
sudo apt-get install heimdall-flash
If you are not sure whether your device is connected, the command:
Code:
heimdall detect
should return Device detected.
Download you current pit
At the terminal prompt type:
Code:
sudo ./download-current-pit.sh
If all goes well you should get 2 new files in the Downloads folder:
downloaded.pit
downloaded.pit.txtIf the downloaded.pit file is 0kb, then something has gone wrong. Don't move forward. Time to figure out what went wrong. If the file is around 4kb, then compare "downloaded.pit.txt" to "d710-stock.pit.txt". If they match, move forward. Otherwise proceed at your own risk.
Repartition Phone
Due to weirdness I don't understand, each time a Heimdall command is done you need to restart the phone in download mode. Since you just downloaded your current pit, you executed a Heimdall command. So turn off the phone. Then restart it in download mode again. No need to unplug the phone from the PC while you do this.
Now , with the phone in download mode again execute the following command in the terminal window:
Code:
sudo ./repartition-now.sh
* This script uses the d710-1GBsys-6GBdata-7.3GBsdcard-8MBpreload.pit file. If you want to use one of the others that were provided, you either do the command manually or edit the .sh file accordingly.
You should see a few lines go by in terminal showing the result and then instructions on what to do next. Following is what I did.
Reinstall CM11
Unplug phone from PC and reboot into recovery. I had a little panic here as it seemed my phone did not want to boot into recovery. I had not unplugged my phone from the PC. Once I unplugged it from the PC I could restart into recovery just fine. I believe the sequence is, turn off the phone, then press power and volume up at the same time.
Once in recovery, follow the instructions from the .sh file listed in the terminal window. Go to "mounts and storage", then format the /system, /cache, /data (as vfat) and /storage/sdcard0. You can try to format /preload, but I always get an error when trying to format that.
Now, insert SD card with the CM11 files you downloaded at the start. Flash the .zips
FL24.zip
cm-11-20150118-NIGHTLY-d710.zip
gapps-kk-20140105-signed.zip
sensor-fix-v2-d710.zip
kernel-Lanchon-TRIM-FPBug-20150113-cm-11-20150111-NIGHTLY-d710.zip (optional)
Reboot the phone and complete the CM11 setup process. If you installed the TRIM kernel listed above, then you may want to run the trim commands. Open the terminal app on your phone and enter the following:
Code:
su -c "fstrim -v /system; fstrim -v /data; fstrim -v /cache; fstrim -v /preload"
Congratulate yourself and then move on with your life.
gald u made it!!!
couple of comments...
you can use bash xxx.sh to run a script that doesnt have execute permissions.
before partitioning, you should compare the downloaded.pit.txt with the stock pit.txt (bundled in zip) and if there's any difference, abort the process!! IMHO anyway.
Lanchon said:
gald u made it!!!
couple of comments...
you can use bash xxx.sh to run a script that doesnt have execute permissions.
before partitioning, you should compare the downloaded.pit.txt with the stock pit.txt (bundled in zip) and if there's any difference, abort the process!! IMHO anyway.
Click to expand...
Click to collapse
Ah okay. I didn't know about bash. So the command then would be "bash xxxx.sh"? So I can remove all the steps about changing the permissions?
I agree about comparing the pit files. I guess I didn't make that clear enough. I'll fix that.
Kjricker said:
Ah okay. I didn't know about bash. So the command then would be "bash xxxx.sh"? So I can remove all the steps about changing the permissions?
I agree about comparing the pit files. I guess I didn't make that clear enough. I'll fix that.
Click to expand...
Click to collapse
sudo bash xxx in this case, but leave it as it is! same thing
Lanchon said:
sudo bash xxx in this case, but leave it as it is! same thing
Click to expand...
Click to collapse
Okay awesome. I added the bit about comparing the 2 files.
Thank you so much for all your help. I laughed, I cried, I learned.
Kjricker said:
Okay awesome. I added the bit about comparing the 2 files.
Thank you so much for all your help. I laughed, I cried, I learned.
Click to expand...
Click to collapse
Thank you thank you, Lanchon and Kjricker! Worked for me! You have my eternal gratitude!
Here are a few observations for any one who is hesitant to try this, especially those who are unfamiliar with Linux:
Linux is the way to go. Follow the instructions. But not every Linux distro works. I have a netbook running a two year-old version of Lubuntu. That didn't work. I flashed the LInux Mint distro in Kjricker's post to a 2gb USB drive and booted into it from the netbook.
From Linux Mint home screen, connect to your network (Ethernet or wireless).
From the Toolbar on the bottom of the screen, select File Manager. Locate on your PC where you copied Lanchon's files, select them in File Manager; and from the right-click menu copy those files to the Downloads folder.
From the Menu, open the Terminal application and install Heimdall (the command is: sudo apt-get install heimdall-flash). (I wasn't sure if Heimdall was already included in Linux Mint so I did it anyway.)
Change to the Downloads directory (the command is cd /home/mint/Downloads).
Now put your phone in Download mode and plug it into the PC.
If you are not sure whether your device is connected, the command heimdall detect should return Device detected.
Ahh yes you must install Heimdall. I'll add that.
Sent from my SM-T700 using Tapatalk
Recently I restored a nandroid backup of Mokee 8-Nov-2014 release. I had made this backup prior to repartitioning. Then I updated the apps and data etc.. After verifying that my phone was running fine, I booted into recovery to do a new nandroid backup.
The backup failed, with a message "couldn't mount /preload". It's been reported in this thread, after partitioning, format of /preload failed.
Still in recovery, I formatted and mounted /preload. Rebooted the system (Mokee, that is) to make sure everything was working. (It was.)
Then I booted into recovery and made a successful nandroid backup.
Anyone please help me..... After Update to Nougat I can't move any file to phone :crying:
Amar5373 said:
Anyone please help me..... After Update to Nougat I can't move any file to phone :crying:
Click to expand...
Click to collapse
Hey Amar,
I am facing the same issue since the time i am using Open beta Nougat versions. I am unable to move any file to phone while connected to a PC (with file sharing option chosen). However, If I boot into recovery, I am able to transfer any file (I am using TWRP recovery).
Can you check if you are able to download any zip file ? I can only download mail attachments but not any other files like rom zips or some files from external links. I am not sure if you have this issue as well.
When connecting to PC, what do you see this device as ? I use ubuntu and I see the device as Android/Internal Shared Storage/. If I boot into twrp and connect then i see the same device as Android/Internal Storage .
I think this is the problem because OOS makes internal storage as shared space between system and data, so we dont have rights to use it unless using ROOT or SU. I tried asking around in different threads about this problem but I didnt get anyt solution. May be its not a common issue but finally I have company to try and fix it
I'm facing only moving problem..... downloading working as well
If u got any solution please inform me
Check and make sure you are in MTP mode. OB10 defaulted to charging only when plugged in for me.
What worked for me when I wasn't able to transfer files was I went to device manager > right click mtp > update driver software > browse my computer > let me pick > mtp USB device > happy me
I have a Chinese max, 32gb. It’s currently on miui 7.5.1.0 stable. When I click check for updates it says no updates available. I’m in china if that makes any difference.
How can I upgrade to a newer software? Can I change to global rom?
I don’t have a windows computer and most guides seems to require windows. Also I don't want a custom rom.
Alternatively, how can I get native update function the to work?
Thanks for help to push mein the right direction.
Screenshot of about phone?
Sent from my Xiaomi MI MAX using XDA Labs
here is the screenshot
nick5000 said:
I have a Chinese max, 32gb. It’s currently on miui 7.5.1.0 stable. When I click check for updates it says no updates available. I’m in china if that makes any difference.
How can I upgrade to a newer software? Can I change to global rom?
I don’t have a windows computer and most guides seems to require windows. Also I don't want a custom rom.
Alternatively, how can I get native update function the to work?
Thanks for help to push mein the right direction.
Click to expand...
Click to collapse
Well, without a pc you have less options, users of miui are on nougat (beta) but in your case must be sure of these things; download (easier) an app from playstore about developer options, open and check at USB debugging, allow, now download a global version from official Miui page for Hydrogen (device name) must be in .zip format and try going to /settings/about device/system update you`ll see four dots upper right and option "select update package", navigate to your downloaded file and try to flash
Thanks. So I downloaded it, went to updater and chose the file, and it says couldn't verify update package.
Tried to download to recovery mode, but then I just get to a screen with the symbol to connect USB cable to computer.
nick5000 said:
Thanks. So I downloaded it, went to updater and chose the file, and it says couldn't verify update package.
Tried to download to recovery mode, but then I just get to a screen with the symbol to connect USB cable to computer.
Click to expand...
Click to collapse
If from this option doesn`t flash your zip either do from mi recovery. Version for China probably is from a phone company if you live there. You need a pc at least to install TWRP (it takes two minutes) and from here you must install last version official beta v8 7.1.19 but you need unlock bootloader
So this is not possible to do with a MAC? what about the terminal commands, can I install a rom from the CLI ?
nick5000 said:
So this is not possible to do with a MAC? what about the terminal commands, can I install a rom from the CLI ?
Click to expand...
Click to collapse
I know this isn't the quickest workaround, but if you're stuck on a Mac you can always bootcamp it for free. Just download Windows 10 (around a 5GB download I think) and install via bootcamp. You don't need a serial to officially install or run WIndows 10 and you can just remove the installation when you're finished.
nick5000 said:
So this is not possible to do with a MAC? what about the terminal commands, can I install a rom from the CLI ?
Click to expand...
Click to collapse
You can use other advance phone (cause this will be busy) like a viewfinder of .img in your computer, with an app from Play Store called DriveDroid, you place some .img in your sdcard and to arrange computer select usb (it`s like a virtual machine) or burn an image in a usb with a linux distro, here is a rescue cd that contain a virtual Windows XP called Hiren`s Boot (500 mb aprox.) but really I don`t know if all that works on a mac.
First read that post, it seems is possible use fastboot on a mac according that: http://htc-one.gadgethacks.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
SubwayChamp said:
You can use other advance phone (cause this will be busy) like a viewfinder of .img in your computer, with an app from Play Store called DriveDroid, you place some .img in your sdcard and to arrange computer select usb (it`s like a virtual machine) or burn an image in a usb with a linux distro, here is a rescue cd that contain a virtual Windows XP called Hiren`s Boot (500 mb aprox.) but really I don`t know if all that works on a mac.
First read that post, it seems is possible use fastboot on a mac according that: http://htc-one.gadgethacks.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Click to expand...
Click to collapse
I tried using fastboot commands on mac to to update, but didn't work.
I guess I'll have to stick with 7.5.10 until I get a new phone.
However wonder why the OTA update doesn't work.
nick5000 said:
I tried using fastboot commands on mac to to update, but didn't work.
I guess I'll have to stick with 7.5.10 until I get a new phone.
However wonder why the OTA update doesn't work.
Click to expand...
Click to collapse
What did you type in fastboot?, zip version is not for fastboot, must be download correct version, but go for the first step, probably you must
unlock bootloader, request to xiaomi, sometimes you got it in 6 hours, depends, probably device is rooted, for this reason don't update ota. Here you have other thread to apply fastboot with other method https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
tried both the flash all except storage.sh and the flashboot flash system commands. it said device it locked. I applied to unlock bootloader, no reply yet, but does that also require a Windows program to unlock the bootloader?
Device is not rooted, but I installed google play, maybe that's what broke the OTA
nick5000 said:
tried both the flash all except storage.sh and the flashboot flash system commands. it said device it locked. I applied to unlock bootloader, no reply yet, but does that also require a Windows program to unlock the bootloader?
Device is not rooted, but I installed google play, maybe that's what broke the OTA
Click to expand...
Click to collapse
No, Google Play can't do that. In my little corner of the world we say "all the roads lead to Rome", I think you need a pc, There is other shorter way of two steps root first with a pc and then download from Google Play an app called "flashfire" you may flash a zip rom from this app. Also you may use a virtual cd or usb with a linux distro like ubuntu or debian running on your mac to arrange computer like a live cd or usb without install on your mac or if you prefer install it on your mac, there's a world of options just root device and can flash any you want and be the real owner of your phone