Database Develop

[TUT] Unbrick\Restore to Factory Condition from Linux

I did not see anything that really walked through what you should do in one place. This is the method I used to restore my device to factory condition. It can also be used to unbrick the device.
You should be comfortable with the command line before proceeding. You cannot downgrade at this tome, so download the version that was on your phone previously.
Files needed:
Verizon 5.5.959 or Verizon 5.6.890
moto-fastboot for linux, download the appropriate version for your arch
HowTo:
1. Extract the zip you downloaded and moto-fastboot.zip to the same working directory. You will get several .img files, moto-fastboot, and an .xml
2. Create a new file named "reset" in your working directory and fill it with the following code.
Code:
#!/bin/bash
./moto-fastboot flash mbm allow-mbmloader-flashing-mbm.bin
./moto-fastboot reboot-bootloader
sleep 30
./moto-fastboot flash mbmloader mbmloader.bin
./moto-fastboot flash mbm mbm.bin
./moto-fastboot reboot-bootloader
sleep 30
./moto-fastboot flash cdt.bin cdt.bin
./moto-fastboot erase userdata
./moto-fastboot erase cache
./moto-fastboot flash lbl lbl
./moto-fastboot flash logo.bin logo.bin
./moto-fastboot flash ebr ebr
./moto-fastboot flash mbr mbr
./moto-fastboot flash devtree device_tree.bin
./moto-fastboot flash system system.img
./moto-fastboot flash radio radio.img
./moto-fastboot flash boot boot.img
./moto-fastboot flash recovery recovery.img
./moto-fastboot flash cdrom cdrom
./moto-fastboot flash preinstall preinstall.img
./moto-fastboot reboot
3. Change directory to your working directory. Make moto-fastboot and the script executable.
Code:
chmod a+x moto-fastboot
chmod a+x reset
4. Execute the script you created in step 2 (with supercowpowers). It should read "< waiting for device >"
Code:
sudo ./reset
5. Make sure your phone is >%50 charged for good measure. Turn off your phone. Hold the 'M' key on the keyboard and turn your phone back on. Press Vol - to scroll down to "AP Fastboot". Press Vol + to select. Connect the USB cable.
6. Sit back and relax, the phone is now flashing back to factory. It will reset a few times. Eventually it will boot up like normal and you'll be all set!
Notes:
You can change sleep to 10 seconds to speed it up. I recommend 30 because I don't know how fast your system picks up usb devices.
The parameters I used to create the script are from the .xml file, in case you were wondering.
[Source for files]
http://rootzwiki.com/showthread.php?5103-SBF-Droid-3-Fastboot-files-(5.5.959-and-5.6.890)
If this helped you, press thanks so others know
If it didn't, please post why to help improve this guide

We have a easier method now, rsd.
Sent from my DROID3 using XDA App

ourtut said:
We have a easier method now, rsd.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
RSD doesn't run natively on Linux

I get it now. Good tut for ppl with linux.
Sent from my DROID3 using XDA App

Thanks for this! I hate having to drop to windows for this kind of stuff, especially considering that linux is under the android framework.
Sent from my DROID3 using XDA App

thank you now i never have to mess with rsd lite and windows .. and drivers you know. thanks
Sent from my DROID3 using Tapatalk

Why does the script need superuser (sudo)? I like the script and will for sure use it, thank you for sharing. I think it would work fine without sudo though
Sent from my DROID3 using XDA App

jweber228 said:
Why does the script need superuser (sudo)? I like the script and will for sure use it, thank you for sharing. I think it would work fine without sudo though
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I don't feel like trouble shooting peoples permissions issues. Running as superuser will eliminate those problems. Some systems\configurations do require those permissions.

Why is this thread no stickied? all other RSD lite threads are, and we cant use RSDlite in linux.

Darksurf said:
Why is this thread no stickied? all other RSD lite threads are, and we cant use RSDlite in linux.
Click to expand...
Click to collapse
because you have to msg the forum mod...cheif_tony and request it

thanks for this one!
a few questions,
is this possible with the new 906 zip?
http://forum.xda-developers.com/showthread.php?p=27315518#post27315518
can you please explain points 3 and 4 more detailed for newer linux/ubuntu users?
what do you mean "3. Change directory to your working directory. Make moto-fastboot and the script executable." and "Execute the script you created in step 2 (with supercowpowers)" how do i get supercowpowers?

The original post's "Verizon 5.6.890" link to the 890 install brings me to LNX.lu and requires a login. I've been waiting a while for their emailed account confirmation - is there another place to grab this file?
Also, you mention Arch - is this process the same in Ubuntu?
EDIT: Hah! Works like a charm. One last step - THANK YOU GamezR2EZ!

[boot.img] obsolete please lock

Hi all. Quick notice:
Usual disclaimers apply.
This is an Unsecure boot.img I made for Android 4.2 on the Nexus 4.
Okay cool... but what is an insecure boot.img?
An insecure boot.img allows the device to be booted with permissions to be mounted as root. This is a way of being able to push SuperSU/Superuser.apk to /system/app and the Su Binaries to /bin
adb shell
su
mount -o remount,rw /system
exit​
See more here: External Link
_____________________________________________________________________________________________________________
To use this you must be unlocked, not familar with unlocking a Nexus device? Easy. In fastboot mode type "fastboot oem unlock" this wipes all data on the device (virtual sd included).
A nice article regarding this thread was published here: http://www.addictivetips.com/android/root-google-nexus-4-install-clockworkmod-recovery/
To boot this boot.img:
must be in the platform-tools folder in the android-sdk
must be in fastboot mode (power+vol-)
First use: fastboot boot "boot.img" (no ")
Why boot? I have not tested this image as I don't have a Nexus 4 as of yet.**
**Some users report flashing the image makes the phone in need of a fastboot stock flashing session, stick to booting for now.​
Thank you for helping!
-fkrone
-Ranguvar
-USSENTERNCC1701E
This is mainly for development purposes to obtain root on this device, it will be an easier process when a recovery is published and you can flash a su.zip. (see attached)
DOWNLOAD HERE: http://www.androidfilehost.com/?fid=9390169635556426389
Note, this is in Nexus 7 folder as Nexus 4 does not have its own atm.​
Click to expand...
Click to collapse
Please Lock!

Placeholder reserve

Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
I wouldn't be lazy and do it myself but PC is off
Sent from a phone
Click to expand...
Click to collapse
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?

Ranguvar said:
sgs2ext4 doesn't work on the recovery.img and the image isn't mountable by itself in Windows.
Too lazy to reboot into Linux, for now.. any other way to crack it open?
Click to expand...
Click to collapse
Pull it apart in hex editor
Sent from my HTC Explorer A310e using xda app-developers app

Harry GT-S5830 said:
Anyone able to get me recovery.fstab from recovery image and ill try make a cwm6 touch recovery for us.
Sent from a phone
Click to expand...
Click to collapse
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.

USSENTERNCC1701E said:
I've got the recovery.img, can I get the .fstab out without loop mounting? I don't have a linux machine set up right now.
Click to expand...
Click to collapse
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
I could probably do it without this, but it probably wouldn't mount data/media (what emulates the SD) so it would be relatively useless as that's where zips are
Also this might prove useful: http://forum.xda-developers.com/showthread.php?t=1494036 (requires Cygwin or Linux environment)

Harry GT-S5830 said:
Old fashioned HxD
See here: http://forum.xda-developers.com/showthread.php?t=443994
Click to expand...
Click to collapse
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.

USSENTERNCC1701E said:
Hell, I wouldn't trust myself to rip it out with a hex editor. I'm setting up a VM right now, but I could just upload the recovery.img for you. I pulled it out of the stock image that google uploaded today.
Click to expand...
Click to collapse
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex

Harry GT-S5830 said:
Cheers, that's where I had mine but I corrupted it :/ ill try pull it apart on the 600MHz wonder pico
Or perhaps not... 3.2" is too small for hex
Click to expand...
Click to collapse
Lol, I'm having a hell of a time getting Slax as a cooperative VM, might have to go all out with ubuntu

Got it!
Thanks for the tutorials. It was just fun to to something short after midnight (Germany). I was a little bit bored Would be nice if you can mention me in the people helped to create this recovery
http://www.mediafire.com/?mlv72phch1tgd5y Mediafire-Mirror

Dammit, beat me to it!
Serves me right for making dinner first
http://ompldr.org/vZ2ExYQ/recovery.fstab

Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???

pikachukaki said:
Can i ask something as a future buyer of nexus 4 and older user of another phone...the fastboot is the "bootloader" (pink screen on my older phone) the state of the phone where i can connect it to my computer and see the folder containing the recovery.img boot.img...etc???
Click to expand...
Click to collapse
That's not quite how it works. These .img files we are talking about are pictures of the stock version of those paritions. Try reading this article for an explanation of Android partitioning.
There is also a great graphic here. The site is in Spanish, I haven't used Google to translate it, but the picture there is in English. Take your time with it, there's a lot of info there.

To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.

Stryder5 said:
To get into Fastboot mode, do you just hold the volume down button while powering on? Never used a Nexus device before. Have been strictly on HTC up until now. I'm picking up my Nexus 4 in the morning and don't mind trying, as long as there's a way to undo anything in case something goes wrong.
Click to expand...
Click to collapse
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.

USSENTERNCC1701E said:
Or you can enable adb and
Code:
adb reboot bootloader
The command
Code:
fastboot boot boot.img
is temporary. All it does is boot, one time only, the image you specify. Once you've mounted system as rw however, everything you do in /system before rebooting is permanent.
Click to expand...
Click to collapse
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.

Stryder5 said:
So does adding the su binaries and the superuser apk give you permanent root after this then?
And exactly what binaries are needed to gain root? I've never gained root using that method before so am a little unfamiliar in this territory.
Click to expand...
Click to collapse
Woops, wrong thread.
Yes, if you push the su binary from a superuser flashable zip to /system/bin/ and chmod 0655, plus the superuser apk, you will have permanent root after.
Also, there is a recovery.img now, so you can test that out, if it works, flash it from fastboot, then flash a superuser zip from that recovery.

Thank you for getting it (recovery.fstab), looks like someone beat me to it though!
Sorry for late response I have to sleep as I'm in last school year
Ill cook up a recovery just to make your efforts worthwhile
It's in OP, its probably 99.9% the same as the other guys so i'm not going to make duplicate thread, use who evers recovery you wish.
____________________________________________________________________________________________________________________________________
Reason I say fastboot boot first is because it allows you to boot the image without permanently (well, unless you flash another over) flashing a partition without knowing it works.

Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?

Stryder5 said:
Booted fine when I ran fastboot boot boot.img, but when I actually flashed it, it's giving me a boot loop now Booting back into fastboot shows secure boot still enabled. Any suggestions? Or do you have the original bootloader image?
Click to expand...
Click to collapse
Not at my comp now or I'd upload it, bit of you rip open the fa Tory image from the Google servers you should find it
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
On a side note, what possessed you to do that?

[Q] Want me to try Ubuntu on RAZR i ? Answer my questions :D

ok so here we go:
i have cwm and a backp.
- does flashing a broken boot.img breaks my phone for ever?
- if not how would i recover it?
- modifying the boot.img is simply changing the text in a hex editor? i need to add some values for ubuntu...
- replacing fastboot userdate will format the complete root system correct?
- when fastbot flash userdata an ubuntu img it will fill the root system with ubuntu correct?
- when only replacing the userdata with ubuntu, would the phone still boot up?
- how would i get smthng like stack traces about what is not working?
i guess i will add questions
if those are answered till tomorow after school (18 hours to go) i will start trying
//Robert

Robbilie said:
ok so here we go:
i have cwm and a backp.
- does flashing a broken boot.img breaks my phone for ever? Nope. We got fastboot files now.
- if not how would i recover it? RSD Lite or manually flashing. 'fastboot flash boot boot.img'
- modifying the boot.img is simply changing the text in a hex editor? i need to add some values for ubuntu... We can pack and unpack it now, no hex editor needed thanks to turl1. Check his thread on the subject
- replacing fastboot userdate will format the complete root system correct? Userdata is /data/, not /system/
- when fastbot flash userdata an ubuntu img it will fill the root system with ubuntu correct? Nope, the /data/, not /system/. You would want 'fastboot flash system system.img'
- when only replacing the userdata with ubuntu, would the phone still boot up? We don't know yet. For sure will have fastboot access no matter what to fix anything in system and boot and userdata.
- how would i get smthng like stack traces about what is not working? Can't help ya there sorry.
i guess i will add questions
if those are answered till tomorow after school (18 hours to go) i will start trying
//Robert
Click to expand...
Click to collapse
I answered what I could

strange the nexus 7 tutorial only includes using the userdata partition, i guess becsuse irs the largest hum?
i need a "cat/proc/partitions" of a nexus 7 to verify this theory...
well lets see...
Sent from my XT890 using xda premium

[Q] Flashing Custom Recovery

I'm having hard time flash custom recovery. I installed ROM Manager, when I tried to go to recovery I got stuck at android logo with EXCLAMATORY POINT. I already followed this instructions http://forum.xda-developers.com/showpost.php?p=10467058&postcount=1638 (deleted these files /system/etc/install-recovery.sh and /system/recovery-from-boot.p)
Followed these instructions:
via fastboot
Code:
Copy recovery-RA-passion-v2.2.1.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the trackball)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-passion-v2.2.1.img
Click to expand...
Click to collapse
via terminal app
Code:
Copy recovery-RA-passion-v2.2.1.img to the root of your sdcard
start the terminal app
su(press enter)
flash_image recovery /sdcard/recovery-RA-passion-v2.2.1.img(press enter)
reboot recovery(press enter)
Click to expand...
Click to collapse
I also installed 4Ext Touch Recovery, but I think it need a wifi to connect to server, but I can't access a wife connection as of now.
What am I missing? I'm about to flash a ROM, my problem is just the recovery.. Anyone can help me with this? :crying:

i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!

demkantor said:
i dont think you are missing anything just boot into recovery and flash your rom.
dont use rom manager to flash recovery, dont use 4ext recovery control app.
if you used one of the two methods you mentioned above (terminal or fastboot) and it was successful
then you have a recovery on your phone, boot into it and install your rom of choice, of course some roms will need custom mtd partitions whcih can be managed through blackrose, but for now just flash one within your parameters so you can begin
happy flashing!
Click to expand...
Click to collapse
I really dont know what is happening. Still I can't go to recovery. Btw, does locking/unlocking bootloader affects in flashing custom recovery. But I think I already unlock mine, how would I know if unlock or lock my bootloader?

... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium

demkantor said:
... Yea very much so, and I believe I misread you first post, I take it you didn't root your phone properly. First of all check what boot loader you have by booting into your hboot. There are a few ways to get there but for now just power off and then power back on holding your volume down key, here will be a screen with some words and androids skateboarding, write down everything from that screen here.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
*BlackRose - Made by Lecabel(dla5244) *
jb-260/10/166
NEXUSONE PVT ENG S-OFF
HBOOT-7.35.5017 (PB9911000)
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-5.08.00.04
Apr 21 2012, 04:53:16
HBOOT
VOL UP
VOL DOWN
TRACKBALL
FASTBOOT
RECOVERY - when I select this, I will be stuck at android logo with !
REBOOT
POWERDOWN

Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium

demkantor said:
Well you are better off than just an unlocked bootloader, you have black rose installed which essentially is an engineering bootloader that allows custom mtd partitions.
Right now you have 260 for system, 10 cache and 166 for data, this should be fine for any chance ROM but may consider changing later on depending on ROM you want to run
For now you need these things
ROM of choice and anything else the dev thinks you need (gapps etc)
Put that on root of sdcard, make sure it is partitioned to fat32 and not in any folder
Also need to have fastboot working, I'm assuming you are using windows.
You will need fastboot.exe usually found in the android SDK and elsewhere.
Proper drivers installed, and although not necessary its nice to add fastboot and adb into path in environmental variables.
If all this is done great. If not go do it now.
Now get recovery, let's say amonra. Open cmd in the same directory as the recovery image, make sure you name it recovery.img (if you don't change command to fit)
Boot into hboot, and put phone into fastboot mode and connect to computer
In cmd type
fastboot devices
If you see your serial # good, if not then you missed something earlier
Now type
fastboot flash recovery recovery.img
If the output say done then you are good, select recovery from within hboot menu and reboot there, once in recovery do a nandrpoid backup (good practice) then do a full wipe, (yes wipe everything you possibly can - side note fastboot -w is cleaner for future reference) then flash ROM, gapps, whatever you need
Let me know if you get stuck
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Finally.. Thank you so much.. I can now go to custom recovery.. Now I will backup and wipe then flash.. :good::good: Will press THANK button now, maybe a million times.. hehe

No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium

demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Okay. I will try to read my left time for this day. Thanks a lot..

demkantor said:
No problem, fastboot is a key skill to learn with any android device that supports it
Here is a guide I made a while back
http://forum.xda-developers.com/showthread.php?p=27796375
Its meant for a different phone but the basics are the same, I would suggest to read up on it a bit and you will have a much easier android experience
Happy flashing!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi, I have a follow up question regarding sd partition, I will just raise my question here than making another thread. I have 4GB SD card but I forgot how much ext partition I made before but my total space in my SD card is 3.21GB. I want to partition my sd card again and increase it maybe to 1gb. If I will increase my partition should I flash again my ROM (VJ CM10.1 | Jelly Bean 4.2.2 - v6.0) and execute a2sd command in terminal emulator? or it's okay to partition my sd card without flashing the ROM again?

You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app

demkantor said:
You can partition SD without fllashing rom again
On this phone the easiest way to check what you have is in 4ext recovery under info, or if you have a Linux distro run gparted
You could also run df through adb shell or if not by a computer, open a terminal and type
such
df
But being it sounds like you want too repartition I would just flash 4ext recovery and do everything from there
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
I think a2sd is not working in my device. When I tried to install a2sd or reinstall it there was a line written in termenal emulator (/dev/block/mmcblkop2) I think that the reason why I easily having internal memory full, even I already partition my sd card, with 1024 ext partition using 4ext touch recovery. Check my screenshot in titanium backup showing my memory status..
Sent from my Nexus One using xda app-developers app

It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium

demkantor said:
It looks like its working, just need to move what you want from data to ext partition shown by titanium as a2sd. What ROM are you running? It does support having apps on ext correct?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the reply. Im using VJ CM10.1 | JB 4.2.2 V 6.0. How to move data to ext partition? I will post screenshot in my internal storage too.
Sent from my Nexus One using xda app-developers app

if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition

demkantor said:
if the rom doesnt have the feature built in then use an app from the market to do it, ive never used this rom so i dont know what options it has
also if you want an easy to see graph style layout of you partitions download Disk Usage from the market, you can easily see what is stored in which partition
Click to expand...
Click to collapse
Thanks. Btw what rom are you using?
Sent from my Nexus One using xda app-developers app

Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app

demkantor said:
Cyanmobile
Yes it has apps2ext built in, go into settings to activate
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Thanks, Btw, what if I wanted to change my ROM, what procedure should I follow? Should I go back to Stock ROM before flashing a new ROM?

Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium

demkantor said:
Nope, boot to recovery, do a nandroid backup, wipe everything, wipe twice even, hell fastboot wipe (most issues people have when flashing a new ROM is not clean wiping)
Then flash ROM like you did first time, and being you have a huge partition for system right now I would suggest to shrink it a bit first, maybe around 170 if your going to use cyan mobile. If you do this you propably should be prepared to flash recovery again as well
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply. So, you're saying that I should partition my system first and flash recovery just like what you taught me in our previous posts? Just to be sure and making all things clear to my self.

[GUIDE] How to update to Android M-Preview-2 from V1 without loosing your data

If you are in M-preview-1 and don't want to lose your dat/apps you can follow this guide, after that, you'll havw M-preview-2 installed and a rooted device.
Firstly, you need to have a pc with adb working. There are several wyas to achive that, but I presume that if you are already in M preview V1, you have it.
Then, you need to have an unlocked bootloader, again I assume that you have it.
======Skip this is you have adb and unlocker bootloader===========
In any case, in linux there is a very trivial way to get both things (probably in windows and mac is more or less the same):
In a terminal:
sudo apt-get install android-tools*
Then plug your N5 to your computer with a usb cable (depuration mode enable), check that everything is working fine:
sudo adb devices
Then;
sudo adb reboot bootloader
sudo fastboot oem unlock
Then reboot
========================================================
Again, if you are not coming from M-preview-1 I do not recommend this method
1. Download M-preview-2 from this page.
2. Download twrp from here.
3. Create a folder, move twrp to that folder and extract M-preview-2 to the same folder (no sudir, all the files in the same folder), extract again image-hammerhead-MPZ79M.zip in the same folder.
4. Download Despair kernel in your device.
5. Download SuperSU beta 2.49 in your device.
Now, we are ready to flash everything:
6. Open a terminal and cd to the folder where you keep everything from previous steps.
7. Plug your device using a usb cable
8. Type the following commands in the terminal (if you are not in Linux, use the same commands but without "sudo"):
sudo device (just to check that adb ·see your device)
sudo adb reboot bootloader
sudo fastboot flash bootloader bootloader-hammerhead-HHZ12h.img
sudo fastboot flash boot boot.img
sudo fastboot flash radio radio-hammerhead-M8974A-2.0.50.2.26.img
sudo fastboot flash system system.img (this step takes a while)
sudo fastboot flash cache cache.img
sudo fastboot flash recovery twrp-2.8.7.1-hammerhead.img
9. Reboot in recovery (just using the vol up or down and the on buttom).
10. Flash Despair kernel
11. Flash SuperSU
12 Wipe Dalvik and cahe (just in case)
13. Reboot

Flashing over preview 1 won't bring additional issues?

migueldbr said:
Flashing over preview 1 won't bring additional issues?
Click to expand...
Click to collapse
Of course II'm still testing, but it seems that there is not new bugs (yet).

All I did was edit flash-all.sh, removed the '-w', then run it Anyone who has flashed the first version will already have the tools installed.
I wouldn't recommend using alternate kernels as they won't be designed for preview 2.

does your guys system app crash if you open data usage (set language to something except english) ?

tugler said:
does your guys system app crash if you open data usage (set language to something except english) ?
Click to expand...
Click to collapse
Yes

I just did a clean flash via fastboot manually. Booting now. I ain't got time for issues.

Is there a reason the OP links to TWRP 2.8.6.1 instead of the latest version (2.8.7.1)?

Anyone else having trouble flashing the despair kernel? I'm getting assert failed: getprop("ro.product.devices") (Status 7) when trying to flash. I tried sideloading and got the same errors followed by E: Error in /tmp/update.zip. Clearly I'm doing something wrong. Any ideas?

6spdsc4 said:
Anyone else having trouble flashing the despair kernel? I'm getting assert failed: getprop("ro.product.devices") (Status 7) when trying to flash. I tried sideloading and got the same errors followed by E: Error in /tmp/update.zip. Clearly I'm doing something wrong. Any ideas?
Click to expand...
Click to collapse
I'm still transferring my nandroid backup to my PC and haven't tried yet, but it's possible that the kernel won't flash on preview 2 because it's not yet updated for preview 2. As @TonyHoyle said, it's probably not a great idea to use one until they've specifically been updated for preview 2.

TonyHoyle said:
All I did was edit flash-all.sh, removed the '-w', then run it Anyone who has flashed the first version will already have the tools installed.
I wouldn't recommend using alternate kernels as they won't be designed for preview 2.
Click to expand...
Click to collapse
can u explain more detailed?

Flashable zip for multirom
flashable zip to use with multirom, please ?

As TonyHole suggested, just remove the -w; basically this will do: (you can do below on a command line as long as you are in the extracted TGZ file and in the hammerhead-MPZ79M folder/directory)
fastboot flash bootloader bootloader-hammerhead-HHZ12h.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-M8974A-2.0.50.2.26.img
fastboot reboot-bootloader
fastboot update image-hammerhead-MPZ79M.zip
This works for me no issues as data is left intact but everything else is updated ; suggesting NOT to do this from an Android L to Android M Preview 2 and do a proper wipe
This will rebuild the ART app optimize on reboot
OP: Next time make a guide for doing STOCK update FIRST ; save the kernel and root for a SEPERATE post or a seperate section in the post

Hellscore kernel works great
Clean flash
I don't understand why any one would do a dirty dirty install with a preview no less
Sent from my Nexus 5 xda-dev app

The OTA is out and it will do the same process end result as the dirty flash method I did, keeps Data and app rebuild on reboot.

NPS_CA said:
The OTA is out and it will do the same process end result as the dirty flash method I did, keeps Data and app rebuild on reboot.
Click to expand...
Click to collapse
Do you have a link?
Sent from my Nexus 5

Is there zip file available
Sent from my Nexus 5 using XDA Premium 4 mobile app

thesebastian said:
Do you have a link?
Sent from my Nexus 5
Click to expand...
Click to collapse
Is this a real question?
Sent from my Nexus 5 using Tapatalk

Ben36 said:
Is this a real question?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah I was asking about the official OTA. Since only the link for Shamu was captured so far.
Sent from my Nexus 5

thesebastian said:
Yeah I was asking about the official OTA. Since only the link for Shamu was captured so far.
Sent from my Nexus 5
Click to expand...
Click to collapse
Surely if you go about phone. System update. Then you'll either have it or not if it's been pushed out to your device?
Sent from my Nexus 5 using Tapatalk