Database Info

[recovery][32A-OR/NR]RA-magic+-v2.2.1-bladyle

Hello,
I made this port some time ago with little help from seo, but didn't make a new thread for it. Now I want more people to look at it and use it because it have many new futures and make flashing ROMs more fun
So this is actually the amon_RA latest recovery for Nexus One.
What I made is just to port it to work with our phones.
Features :
Reboot system now :: reboot your phone
USB-MS Toggle :: enable/disable USB mass storage (use when the phone is connected to your PC)
Backup/Restore
Nand backup :: Make a selective Nandroid backup
Nand restore :: Restore a Nandroid backup
Backup Google proprietary system files :: Makes a backup of the Google proprietary system files in /cache/google
Restore Google proprietary system files :: Restores the Google proprietary system files from /cache/google
Flash zip from sdcard.
Choose zip from sdcard :: Flash a zip update file from any (sub)-directory on your sdcard
Toggle signature verification :: Toggles the signature verification for zip files.
Wipe
Wipe ALL data/factory reset :: wipes /data + /cache + entire ext partition + all apps installed on your sdcard (froyo a2sd).
Wipe /data :: wipes /data.
Wipe /cache :: wipes /cache.
Wipe /sdcard/.android_secure :: wipes all apps installed on your sdcard (froyo a2sd).
Wipe /sd-ext :: wipes the entire ext partition on your sd (if present).
Wipe Dalvik-cache :: wipes the dalvik-cache located in /cache + /data + /sd-ext is present.
Wipe battery stats :: reset the battery calibration.
Wipe rotate settings :: reset the sensor calibration.
Partition sdcard
Partition SD :: Interactive SD partitioning
Repair SD:ext :: Repair the ext partition
SD:ext2 to ext3 :: Convert ext2 to ext3
SD:ext3 to ext4 :: Convert ext3 to ext4
Mounts
(Un)Mount /system
(Un)Mount /cache
(Un)Mount /data
(Un)Mount /sd-ext
(Un)Mount /sdcard
Other
Fix apk uid mismatches :: Does extacly that
Move recovery.log to SD :: Moves the recovery log file to your sdcard. (Use when you want more detailed recovery log information)
Power off :: Powers off your phone
Click to expand...
Click to collapse
Use the trackball (up+down) to navigate through the menu, press the trackball to select items. Use the Volume-down key to go back to a previous menu.
Download:
recovery-RA-magic+-v2.2.1-bladyle.img
MD5sum: 98A8CAE41C0A7D2AEF69A4F62F2F6475
Install:
From fastboot:
Code:
Copy recovery-RA-magic+-v2.2.1-bladyle.img to a location where fastboot can find it.
Boot your phone into fastboot mode (power on while holding the back)
Connect your phone via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-magic+-v2.2.1-bladyle.img
You can use RadioSwitchGUI_v4 too!
If you want just to try it:
Code:
fastboot boot recovery-RA-magic+-v2.2.1-bladyle.img
Thanks and credits go to :
Amon_RA
seo
carz12

sorry. ask a stupid question.is this recovery for 32a, 32b or both?
Sent from my Dream/Sapphire using XDA App

smartvincent said:
sorry. ask a stupid question.is this recovery for 32a, 32b or both?
Sent from my Dream/Sapphire using XDA App
Click to expand...
Click to collapse
sorry i forgot to mention this...it is for 32a only
I can try to make 32b version too but I need someone to test it.

Bladyle said:
sorry i forgot to mention this...it is for 32a only
I can try to make 32b version too but I need someone to test it.
Click to expand...
Click to collapse
If you make a 32b version i'd gladly test it

I've been using this recovery for some time and it runs perfectly. And it works in both new and old radio. Great work!
Note: It's features and not futures.

using this recovery too and im really happy with this! thank you Bladyle! great job!

thank you guys
BTW I need some testers to PM for 32B/MyTouch 1.2 port

I'm also using this on my Old Radio Magic, haven't tested on new radio yet
it works well

New radio, excellent work
Sent from my Sapphire using XDA Premium App

works like a charm with new radio

Bump. This amazing recovery need to be on the first page!

kanttii said:
Bump. This amazing recovery need to be on the first page!
Click to expand...
Click to collapse
Thanks mate!
This is my default recovery on my device.

Bladyle said:
Thanks mate!
This is my default recovery on my device.
Click to expand...
Click to collapse
For me too. When you first posted it, I didn't dare to try, but after a few days I did..and since then I have been using this all the time! A week ago I tried CWM to see if a ROM could be flashed through that, but since CWM is so frustrating with all the nonononono's I had to get back to yours. And it's amazing as I already said!
Thank you!

Hi bladyle ,
I´ve read this thread about your updated RA-recovery. Because of the fact, that I´ve a google branded magic, I can´t flash this recovery. So my ask to you, if you could make a 32B Version or could tell the steps, how to port a recovery from another device.
Greets

I would also be glad to test a 32B port of this. Just let me know!

Can somebody reupload this? Please...

blaster44 said:
Can somebody reupload this? Please...
Click to expand...
Click to collapse
first post updated

Bladyle said:
first post updated
Click to expand...
Click to collapse
my bad....

Wow...New radio version thanks for the great work
Sent from my HTC Magic

I'm glad you like it

[Q] Enrcyption Support for ClockWorkMod Recovery

Hello,
i have just installed the official stock ICS 4.0.3 Rom to my Nexus S and everything was really fine... until i tried to root it. As someone who tries to take security seriously, i immediately encrypted the device using the tools provided by ics (works ok).
but unfortunatly it's now not possible anymore to mount /sdcard while in recovery, which makes rooting and installing updates impossible (or is there any other way? eg. fastboot?).
therefore my question: will clockworkmod recovery support ics encrypted devices in the (near) future? i know its gonna be a p.i.a. to type a password with only the volume buttons, but hey
i like the encryption and would like to keep it, but not beeing able to use recovery like before is a big drawback...
greetings
Georg

Same for me.
Hope to see encryption support in clockworkmod soon.
I bought Rom manager premium even if I never flash from rm just to support the developers... hope they will be able to get it sorted out

Op -- I'm interested in this for when my phone (EVO 3D) finally gets ICS. Will you post an update to this thread if you hear anything?
BTW, with TWRP getting touchscreen support, it can't be too much longer before CWM gets touchscreen since I think the guys in TWRP were going to start contributing to CWM, from what I've heard anyway. So that would solve the password typing problem.

Georg, thanks for asking this question as I've been wondering the same exact thing. Hopefully we'll get a good answer soon.

Alternatives for ClockworkMod Recovery
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...

mrosensweig said:
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...
Click to expand...
Click to collapse
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S

small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...

I didn't read anything about encryption so did not upgraded to the touch recovery yet

you should lock the bootloader if someone is nagging you

jomir said:
small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...
Click to expand...
Click to collapse
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva

rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S

DarkhShadow said:
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Thanks for the reply, DarkhShadow. The problem is that CWM can't wipe or format these partitions, since it can't mount /sdcard (which is encrypted). If I could only access the external sdcard from within CWM, I could just wipe everything and then install a new rom. But since it can't mount /sdcard, I can't access sd-ext. nvflash is not an option, since my TF101 is B90. Is there a way to either restore the stock recovery (overwrite CWM) or boot from the external SD so I can run a script such as "super wipe full" (http://forum.xda-developers.com/showthread.php?t=1245892)? Maybe there's a way to run the wipe script through adb? If I can just format the partitions (which is what the script does), then CWM would be able to mount /sdcard and, consequently, the external SD and I can flash a new rom (such as revolution HD 3.0.1).
Thanks,
rmsilva

Honestly idk then, try a factory reset on phone(ie booted up) and then maybe it will be unencrypted?
Sent from my ice cream powered Nexus S

The funny thing is that stock recovery on an encrypted phone can write to the disk, but only from a warm reboot (perhaps the kernel stays resident?).
When I say write to disk I say apply the leaked OTA update, 4.0.4 for the VZ Gnex. And correct me if I am wrong, it's writing and mounting the disk, no?
Anyhow, this is done from stock recovery which is open source. So you ask yourself, why can't Koush support mounting the disk from a warm recovery state reboot? Maybe he doesn't know this?
DarkhShadow said:
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse

rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
i did a factory reset (from the settings menu), installed recovery per adb/fastboot and installed cm9 from sdcard in recovery.

Use tmpfs to install a new ROM in crypted system
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...

What about a nandroid backup or restore? How big is /cache?
orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse

Sorry I didn't try with a nandroid backup but I think it is too big to fit the device memory...
You can backup data inside the sd partiton (phone up and running, just to don't lose data...), boot into recovery, format sdcard partition, mount it, put the backup in the sdcard and after install the nandroid backup...
I think that it could work but I am not sure. If after formatting the sdcard you can mount it, the task is done. You can put the backup on it using adb push and flash using recovery.
If you try please give me some news.
Regards

orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)

thx1200 said:
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)
Click to expand...
Click to collapse
First it formats the cache partition. Then mount the /sdcard so that you can access it from your pc. After you mount the /sdcard, you can put your rom zip into it. After the zip has been transferred into /sdcard, you can flash the zip as usual.
Since nexus s doesn't have sdcard slot, it mounts the internal storage as '/sdcard' to treat it like a sdcard, thus 'fake' sdcard. The 'fake' sdcard is around 13GB.

[Q] [Help] CWM can't mount sd-ext? (LG-P500)

As I was getting low on my LG-P500 phone, I tried looking for some app2sd solution, doing the following steps:
- Backup all SD card content to PC
- Boot into recovery (CWM5.0.2.7)
- From recovery, create sd-ext partition
- From recovery, format the new partition
- From recovery, mount usb device, restore all SD card content from PC.
- Reboot device, installed link2sd and managed to link applications to sd.
Now link2sd seems to work fine- I tried linking quite a few applications and all of them work fine, no complaints. It only gave me an error with some apps which I have previously *moved* to SD using Titanium backup, but upon moving them to internal storage link2sd picked them okay.
However, I noticed that using file explorer, root explorer etc- they all show the sd-ext partition as empty, with size of 0 bytes??
Then, I booted into recovery and tried to mount the sd-ext partition, but I get an error message... (all other partitions I can mount/unmount just fine).
To be sure, after each reboot it looks like all the applications linked2sd work appropiately, so everything looks fine.
However, now I am concerned whether I can create (and restore, of course) nandroid backups- what will happen with all these apps linked to sd? Am I right that CWM may not be able to backup (and therefore restore) anything that is on this partition?
Am I going to lose all these apps and data? Does TiB backup these apps+data and be able to restore them fine to sd-ext? I'm asking about TiB as a mediocre workaround of restoring applications that were in sd-ext (and thus omitted by CWM backup). That is, after restoring nand backup- doing an additional restore from TiB??
Any help/insight is welcome
Ah, yes, some more info:
Phone: LG optimus P500
ROM: Lupohirps CM9 4.0.3 from this thread http://forum.xda-developers.com/showthread.php?t=1558213
Recovery: CWM 5.0.2.7 (By the way, whenever I try to flash 5.0.2.0 I get an error...)

that's weird since the app working. what ekstension do you have on sd card fat? fat32?

Can you open Android Terminal (https://play.google.com/store/apps/details?id=jackpal.androidterm) and issue these commands:
su
busybox ls -la /sd-ext/
busybox mount
If /sd-ext doesn't show up in mount, then it is not mounted.
Actually CM9 for P500 lacks file /system/etc/init.d/05mountsd (this file is responsible for mounting /sd-ext). IMHO You should ask ROM developer about sd-ext support.
If you want to test (and potentially restore your Nandoid backup or reflash CM9 afterwards) I can give you this script from CM7 (actually modified version that allows any ext version).

Your sd-ext files are actually in data/sdext2, not in /sd-ext.
Also Try using Amonra 3.0.6, overall it has better sd-ext support, I find it mounts and wipes things like dalvick cache inside the sd-ext partition as well , which is handy, unlike CWM.

Thanks for all your replies!
Sdcard file system is fat32. For the partition I have no idea as cwm didn't ask for any specific (e.g. ext2/3/4) and I haven't seen any way to get this Info...
Anyway, following this thread, I did find that all the app/data is in /data/sdext2- not sure what it means in terms of nandroid backup& recovery but it looks more reassuring..
As to RA recovery, I'm not in particular in love with cwm- it is just what I'm used to from other android devices I've been using. Actually on my htc mt4g I was using ext4 touch recovery and that one I really liked, but it is not supported in lots of devices. That phone was stolen, unfortunately. I'll give it a try, though.
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2

DavisNT said:
Can you open Android Terminal (https://play.google.com/store/apps/details?id=jackpal.androidterm) and issue these commands:
su
busybox ls -la /sd-ext/
busybox mount
If /sd-ext doesn't show up in mount, then it is not mounted.
Actually CM9 for P500 lacks file /system/etc/init.d/05mountsd (this file is responsible for mounting /sd-ext). IMHO You should ask ROM developer about sd-ext support.
If you want to test (and potentially restore your Nandoid backup or reflash CM9 afterwards) I can give you this script from CM7 (actually modified version that allows any ext version).
Click to expand...
Click to collapse
Thanks! Looks likeb system/ cache/ data are all yaffs2, /mnt/Sdcard is vfat and /data/sdext2 is ext4. Not sure what all the output means (relatime, barrier=1, data= ordered etc. etc.)
So, can I figure out where the /data/sdext2 is physically stored? Is it actually the sd-ext/ext4 partition? Looks like must have, as its contents are way bigger than phone's 200MB internal storage...
Thank you all again
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2

jaibar said:
Thanks! Looks likeb system/ cache/ data are all yaffs2, /mnt/Sdcard is vfat and /data/sdext2 is ext4. Not sure what all the output means (relatime, barrier=1, data= ordered etc. etc.)
So, can I figure out where the /data/sdext2 is physically stored? Is it actually the sd-ext/ext4 partition? Looks like must have, as its contents are way bigger than phone's 200MB internal storage...
Thank you all again
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
/data/sdext2 is the mountpoint for the ext4 partition thats on your sd card, physically its obviously on your sd card, but If you use linux, data/ is where the all partitions other then home partition get "attached"/mounted to, the 11link2sd script made by link2sd in yout init.d folder actually mounts it sdext2, the name means nothing, just something link2sd names it as.
---------- Post added at 08:40 PM ---------- Previous post was at 08:30 PM ----------
So Basically nandroid will not back it up under /data/sdext2 as the script runs after recovery, the best way to backup apps that are on the ext partion is back them up using Titanium Backup, as that saves the real apks, and when you restore all your apps, select link2sd to automatically move them to sd-ext partition.

Hi at all,
at first sorry for my bad english.
I had a similar case. If I made a backup with cwm 5.0.2.7, cwm cant mount/read the sd-ext.
In a other thread a user wrote, that cwm 5.0.2.8 had problems with the sd-ext.
And he does downgrade to cwm 5.0.2.0, and than cwm will work.
So, I did this:
I open the rommanager and choose the option "install Clockworkmod", now I choose the "LG Optimus One (old BB)".
But i have the new baseband on my O1.
The basis of this is, if you choose the new baseband in the rommanager, he will install cwm 5.0.2.7. For the old is it the 5.0.2.0 version.
Now, Rommanger made the installation with cwm 5.0.2.0. to my phone.
After this i go in to the recovery and made my nand-backup. It works perfekt!
No problems with the sd-ext, after I did this.
May be this will help.

Fietz said:
Hi at all,
I open the rommanager and choose the option "install Clockworkmod", now I choose the "LG Optimus One (old BB)".
But i have the new baseband on my O1.
The basis of this is, if you choose the new baseband in the rommanager, he will install cwm 5.0.2.7. For the old is it the 5.0.2.0 version.
Click to expand...
Click to collapse
Thanks for the tip..
I have tried in the past to flash cwm 5.0.2.0 via Rom Manager, but I kept getting an error message, so I gave up.
Now I thought to give it a second chance, but as it fails to flash with Rom Manager (in the menu when I choose LG optimus one I don't get any choice between old BB or new or anything- it just reflashes 5.0.2.7) and from the "all recoveries menu I can only choose 5.0.2.0 but it gives an error message), so I downloaded the zip files from this thread http://forum.xda-developers.com/showthread.php?t=1523050 (including also Amon Ra 3.06) and tried to manually flash from recovery.
It flashed and showed recovery as "5.0.2.0" but nothing worked- every submenu that I tried to enter was black screen (with the CWM logo on background) and it gave me the creeps- I don't like being stuck without a functional recovery so I rebooted and flashed 5.0.2.7 again from Rom Manager.
I'll try to flash Amon Ra and see how it works.
[EDIT] flashed AmonRa 3.06 and it seems to work fine- able to mount/unmount all partitions including sd-ext, and it also has an option to check each of them in separate during nandroid backups.
A noobish question: it has also an option to include the ".android_secure" . Isn't this one a redundancy with sd-ext (e.g. contains all the apps/data that has been moved/linked2sd)?

jaibar said:
As I was getting low on my LG-P500 phone, I tried looking for some app2sd solution, doing the following steps:
- Backup all SD card content to PC
- Boot into recovery (CWM5.0.2.7)
- From recovery, create sd-ext partition
- From recovery, format the new partition
- From recovery, mount usb device, restore all SD card content from PC.
- Reboot device, installed link2sd and managed to link applications to sd.
Now link2sd seems to work fine- I tried linking quite a few applications and all of them work fine, no complaints. It only gave me an error with some apps which I have previously *moved* to SD using Titanium backup, but upon moving them to internal storage link2sd picked them okay.
However, I noticed that using file explorer, root explorer etc- they all show the sd-ext partition as empty, with size of 0 bytes??
Then, I booted into recovery and tried to mount the sd-ext partition, but I get an error message... (all other partitions I can mount/unmount just fine).
To be sure, after each reboot it looks like all the applications linked2sd work appropiately, so everything looks fine.
However, now I am concerned whether I can create (and restore, of course) nandroid backups- what will happen with all these apps linked to sd? Am I right that CWM may not be able to backup (and therefore restore) anything that is on this partition?
Am I going to lose all these apps and data? Does TiB backup these apps+data and be able to restore them fine to sd-ext? I'm asking about TiB as a mediocre workaround of restoring applications that were in sd-ext (and thus omitted by CWM backup). That is, after restoring nand backup- doing an additional restore from TiB??
Any help/insight is welcome
Ah, yes, some more info:
Phone: LG optimus P500
ROM: Lupohirps CM9 4.0.3 from this thread http://forum.xda-developers.com/showthread.php?t=1558213
Recovery: CWM 5.0.2.7 (By the way, whenever I try to flash 5.0.2.0 I get an error...)
Click to expand...
Click to collapse
Hi, Jaibar
I have LG Optimus One with JB 4.2.2, CM 10.1.
Here what I have done in order to gain extra space on my internal memory. All the steps that you have followed are the same as I did. BUT! There are two important things that I have followed that had greatly helped to succeed:
1) For every 100Mb internal memory - NO MORE than 512Mb of SD card memory(for my LG I have separated 965Mb on the SD card)
2) INT2EXT+ works with EXT2/3/4 partitions BUT INT2EXT4+ works with ONLY EXT4 partition. After I have watched this short video, and this blog post I have been able to restart my phone with extended internal memory.
Believe me, for three days I have been flashing my phone, trying to find the correct way. At the end I have noticed that the problem was that I couldn't mount /sd-ext I thought that maybe following this two rules will help - and it did!
I hope that it will help! Good luck

flashing custom rom without sd card

my sd card got broken and reflashed to original 2,3 rom. now i want to go back to custom rom. can any1 help me flash custom recovery without sd card. thanks
Sent from my LG-P500 using XDA

mrbulanescu said:
my sd card got broken and reflashed to original 2,3 rom. now i want to go back to custom rom. can any1 help me flash custom recovery without sd card. thanks
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
I doubt that's possible
Sent from my LG-P500 using xda premium

I think you can only flash official roms with kdz because custom roms needs SD card to use "flash zip from sdcard" in the recovery.

There must be a way for flashing ROM through adb.

there is, basically look up how to copy files from PC to phone using adb, and just copy everything in the ROM onto the / (root) of your phone, as all flashable zips do is copy the stuff from your sd card onto your phone

Flash mage
Use Android Commander version 0.7.9.10 by PanPiotr. It has a option to flash your phone under device menu. I have never used it so I don't know if it will work, but it might be worth a try. http://androidcommander.com/ here is the link for the software It is a very powerful application I would recommend to any andriod user, good luck I would like to know if it works for you. All of the features I have used work perfect.

mrbulanescu said:
my sd card got broken and reflashed to original 2,3 rom. now i want to go back to custom rom. can any1 help me flash custom recovery without sd card. thanks
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
I only understoood that you flashed.stock firmware using kdz and have no sd, so steps are as follows:
1.root optimus 1 using superoneclick
2.flash cwm using adb
3.reboot in recovery
4.mount /system
5.then format /system
6.flash rom using adb
or
just copy paste files in /system of your phone
I mean the files which are in zip of custom rom

How to Flash a ROM Without an SD Card
​
This is for all those who don't have a working sdcard, sdcard slot, etc. but want still to flash a new rom
Prerequisites:
Flash an Amon_RA recovery if you're using Clockwork
Access to a computer that had AndroidSDK tools on it - you'll be using ADB
Put whichever ROM.zip you want to flash in your android-sdk\tools folder - I would rename it to something simple. (My example which I'll be using for this tut is: C:\AndroidSDK\toosl\ROM.zip)
Directions:
Reboot into the Amon_RA recovery
Wipe data/factory reset, cache, and dalvik via the recovery menu
Open up cmd/terminal on your computer
Navigate to your android-sdk\tools directory
Enter the following in cmd/terminal:
Code:
adb shell
mount data
*wait a second or two* You may or may not get the "/ #" line returned.
Despite what happens press "Ctrl+C" to break the command and get back to the standard AndroidSDK\tools> directory
Enter the following in cmd/terminal:
(replace "ROM.zip" with the name you're using)
Code:
adb push ./ROM.zip /data/
*this will take anywhere from 30sec to a min depending on the rom.zip size*
Then we do this in cmd:
Code:
adb shell
recovery --update_package=DATA:ROM.zip
Wait for it to finish flashing/updating
Reboot
ENJOY
Brief rundown of what we just did:
Wiped /data/ to free up space for the zip
Put our ROM.zip onto the /data/ partition since we don't have an SD Card to work with.
Told the recovery to flash from our /data/ partition instead of /sdcard/

.......

is there a way to toggle signature verification through adb? My sd card slot is not working and i am trying to flash back to stock to go to sprint for repair but when I run the command and reboot into recover it says signature failed and then I can not pick the update.zip i put in the data partition.
by.adrian said:
How to Flash a ROM Without an SD Card
​
This is for all those who don't have a working sdcard, sdcard slot, etc. but want still to flash a new rom
Prerequisites:
Flash an Amon_RA recovery if you're using Clockwork
Access to a computer that had AndroidSDK tools on it - you'll be using ADB
Put whichever ROM.zip you want to flash in your android-sdk\tools folder - I would rename it to something simple. (My example which I'll be using for this tut is: C:\AndroidSDK\toosl\ROM.zip)
Directions:
Reboot into the Amon_RA recovery
Wipe data/factory reset, cache, and dalvik via the recovery menu
Open up cmd/terminal on your computer
Navigate to your android-sdk\tools directory
Enter the following in cmd/terminal:
Code:
adb shell
mount data
*wait a second or two* You may or may not get the "/ #" line returned.
Despite what happens press "Ctrl+C" to break the command and get back to the standard AndroidSDK\tools> directory
Enter the following in cmd/terminal:
(replace "ROM.zip" with the name you're using)
Code:
adb push ./ROM.zip /data/
*this will take anywhere from 30sec to a min depending on the rom.zip size*
Then we do this in cmd:
Code:
adb shell
recovery --update_package=DATA:ROM.zip
Wait for it to finish flashing/updating
Reboot
ENJOY
Brief rundown of what we just did:
Wiped /data/ to free up space for the zip
Put our ROM.zip onto the /data/ partition since we don't have an SD Card to work with.
Told the recovery to flash from our /data/ partition instead of /sdcard/
Click to expand...
Click to collapse

Flash using kdz uploader. Search and read before flash. There are some tutorials on these forums.

u can also use fastboot

i am following this way but i get error "device not found". please help

Didn't Work For Me
I Want To Flash CM9 ICS On My LG P500. I Followed The Steps EXACTLY LIKE IN THE GUIDE! I Have Amon_RA Build:RA_thunderg-3.0.6-GNM and it said can't install because no such thing exist in that directory...? I DONT Have A SD CARD Also... Is ClockWorkMod Recovery Any Better?

Isn't better buy a new sd card than anticipade some unnecessary problems?

orbit09 said:
Isn't better buy a new sd card than anticipade some unnecessary problems?
Click to expand...
Click to collapse
Sometimes the problem isn't about buy an sdcard, but the phone doesn't recognize any sdcard

orbit09 said:
Isn't better buy a new sd card than anticipade some unnecessary problems?
Click to expand...
Click to collapse
My LG phone doesn't even have an ad card slot. Entire phone is riveted shut so I can't even change the battery if I needed to. So this advice is completely relevant and necessary.

Is not having external SDCard an issue for rooting?

I'll try to explain myself before people jump at me. I saw another thread with same question but seems like people misunderstood the question.
I am not talking about "lack" of memory, or not having another 32/64gb availble, etc.
I'll give you an example to what I am referring to:
Recently I decided that my rooted S2 needs a little 'refreshing', meaning - not just a wipe, but a complete format, to start from scratch. So I formatted everything, including /system and /emmc partitions. I then re-booted to recovery and had my rom file on the SD card so i was able to get a clean install.
Now, the question is - say I am at a stage when I need to 'refresh' the phone and wipe everything out. How do I then access the rom file for new install if I don't have external SD Card?
Thanks.

with adb.

What I do when I want a clean start, is I will load the rom/gapps/kernel to my phone, go to recovery, factory reset (with system if you choose), then flash all the things you want, then go back and wipe internal storage after. Then you're left with a fresh version of the ROM you want to install and no files whatsoever in the memory. Hope that helps.

I had the same suspicions a while ago. Basically with the nexus 5, even without an external sd, you can still do a full wipe of everything other than your storage. There is a path on the internal storage which essentially acts like an sd card, and when doing wipes in recovery it will not be wiped, unless of course you specifically choose to format /sdcard or all of /data. Read here for more info. I found that explanation very helpful.
So to answer your question, no, its not an issue.

Zepius said:
with adb.
Click to expand...
Click to collapse
This.
I have the same issue, with my OCD, that I always need a complete wipe of EVERYTHING.
One option, I recommend if that's not an option at the time of flash, is to simply "reset" in settings. It clears out the whole SD, which is something I usually want to do when I want a FULL flash

justinisloco said:
simply "reset" in settings. It clears out the whole SD, which is something I usually want to do when I want a FULL flash
Click to expand...
Click to collapse
Reset in settings just uses recovery unless something changed I haven't realised?
It should be down to what recovery you have (stock vs custom) as to whether a reset (regardless of how you initiate it) wipes /sdcard or not... or are you saying that's changed now?
Sent from my Nexus 5 using Tapatalk

Zepius said:
with adb.
Click to expand...
Click to collapse
Pardon my ignorance, but what is adb?
spitefulrain said:
What I do when I want a clean start, is I will load the rom/gapps/kernel to my phone, go to recovery, factory reset (with system if you choose), then flash all the things you want, then go back and wipe internal storage after. Then you're left with a fresh version of the ROM you want to install and no files whatsoever in the memory. Hope that helps.
Click to expand...
Click to collapse
Problem with factory reset, as far as I know, is that it does not wipe out everything. When I do factory reset in my S2, I still see old folders (even though empty) from before the wipe. That's why I like to format everything clean. When I mean clean, I don't want to see any old folder in there
justinisloco said:
This.
I have the same issue, with my OCD, that I always need a complete wipe of EVERYTHING.
One option, I recommend if that's not an option at the time of flash, is to simply "reset" in settings. It clears out the whole SD, which is something I usually want to do when I want a FULL flash
Click to expand...
Click to collapse
OK, but if you do that, where do you 'keep' the rom file and how do you flash it?

sbi1 said:
Pardon my ignorance, but what is adb?
OK, but if you do that, where do you 'keep' the rom file and how do you flash it?
Click to expand...
Click to collapse
Android Debug Bridge. It allows you to communicate with your phone via command line tools.
You would keep the rom somewhere on your internal storage (data/media) just like you would on any other phone. Then after wiping, you would simply choose to install zip from sdcard and your rom, along with any other flashable zip on your sdcard will be available to install. Basically when you do a typical full wipe from a custom recovery, the contents of your internal storage/sdcard are not wiped.

Chromium said:
Android Debug Bridge. It allows you to communicate with your phone via command line tools.
You would keep the rom somewhere on your internal storage (data/media) just like you would on any other phone. Then after wiping, you would simply choose to install zip from sdcard and your rom, along with any other flashable zip on your sdcard will be available to install. Basically when you do a typical full wipe from a custom recovery, the contents of your internal storage/sdcard are not wiped.
Click to expand...
Click to collapse
OK, this seems a bit too complicated for me

sbi1 said:
Problem with factory reset, as far as I know, is that it does not wipe out everything. When I do factory reset in my S2, I still see old folders (even though empty) from before the wipe. That's why I like to format everything clean. When I mean clean, I don't want to see any old folder in there
Click to expand...
Click to collapse
Which is why I said wipe your internal storage after
Sent from my Nexus 5 using Tapatalk

rootSU said:
Reset in settings just uses recovery unless something changed I haven't realised?
It should be down to what recovery you have (stock vs custom) as to whether a reset (regardless of how you initiate it) wipes /sdcard or not... or are you saying that's changed now?
Click to expand...
Click to collapse
Lately, I've noticed that it wipes the Data as well. Unless It was only on CWM that it happened? I had installed CM11 with CWM and wanted to reset my SD. I used the reset feature and it erased everything, except the OS
sbi1 said:
OK, but if you do that, where do you 'keep' the rom file and how do you flash it?
Click to expand...
Click to collapse
I would flash the Rom first, then do the factory reset, the only downside is the nandroid you made may be lost, unless you uploaded it to GDrive or something.
---------------------------------------
Using this guide, you will be able to learn about ADB
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
In Step 3-
Chromium said:
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock rom
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into the bootloader. (volume down + power). Once in the bootloader use the volume rockers to scroll onto Recovery Mode, then press power to select it. This should bring you into your newly installed custom recovery. Leave the phone at the home page of the custom recovery.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Click to expand...
Click to collapse
It shows how to "Push" a file to your phone. That is the best way, IMO. But instead of SuperSU, just "adb push ROM.zip /sdcard/"

sbi1 said:
OK, this seems a bit too complicated for me
Click to expand...
Click to collapse
Flashing the rom? Its honestly not any more complicated than flashing a rom for any other device. You download the rom to your internal storage. Boot into recovery. Then do a full wipe:
TWRP Full Wipe:
- Wipe
- Advanced wipe
- Select all, except internal storage
- Swipe to wipe
CWM Full Wipe:
- wipe data/factory reset
- wipe cache partition
- advanced > wipe dalvik cache
- mounts and storage > format /system
Finally you can then flash the rom (and gapps).

sbi1 said:
OK, this seems a bit too complicated for me
Click to expand...
Click to collapse
It's not really and if you're rooting and flashing any device, adb is essential knowledge.
Once you've installed adb (millions of guides on the net) you just boot into recovery then connect to pc via usb.
adb commands are run from cmd prompt.
For example...
adb push c:\users\sbi1\desktop\rom.zip /sdcard
Would push the file on your windows desktop called rom.zip to your sdcard.
You can even sideload from recovery.
Or better yet,.just don't wipe /sdcard. It has no benefit other than looking tidy anyway
Sent from my Nexus 5 using Tapatalk
---------- Post added at 10:20 PM ---------- Previous post was at 10:17 PM ----------
Ok too many cooks... i'm bowing out
Sent from my Nexus 5 using Tapatalk

OK, thank you all. So I should have no worries then. Was just wondering how this is done without external SD and it seems to be working fine. Thanks again!

Chromium said:
CWM Full Wipe:
- wipe data/factory reset
- wipe cache partition
- advanced > wipe dalvik cache
- mounts and storage > format /system
Click to expand...
Click to collapse
Parting note
Philz Touch Full Wipe:
- wipe data/factory reset > clean to install new ROM
(Does all the steps mentioned above at once)
Sent from my Nexus 5 using Tapatalk