A few days ago Koush published his new CWM recovery v.5.5.0.4 for TF101.
Many (most?) of those who flashed it are experiencing trouble booting normally:
the device goes straight into CWM recovery unless you cold-boot by holding the Vol(-) key at boot time.
This thread is meant to support those who are in this situation.
Also, this thread is to warn others not to flash CWM 5.5.0.4 for the time being.
Also, also, this thread is to gather information that will help devs to fix our problem.
Note:
The previous thread found here got locked (I was told) because of FUD and general lack of clarity.
Please keep it clean and flame-free.
If you are new to Android and TF101, please refer to good guides such as this one:
http://forum.xda-developers.com/showthread.php?t=1494230
You can save yourself from much trouble by educating yourself a little.
UPDATE:
If you have 5.5.0.4 installed and have not used any apps for booting into recovery you likely don't have the problem described above.
We now have two reports of being able to successfully flash an alternate recovery and escape 5.5.0.4
See posts #3 and #67.
UPDATE2:
See post #3 for continuing contributions from @gee one (thanks!):
http://forum.xda-developers.com/showpost.php?p=23257966&postcount=3
UPDATE3:
There is some progress. More testing to be done ...
Money post: http://forum.xda-developers.com/showpost.php?p=23301594&postcount=105
UPDATE4:
We have a solution courtesy of @gee one and @leetlikeawping and the fearless tester @trtk.
This solution does NOT involve NVFlash or has anything to do with the boodloader, so it should apply to all SBK versions (and SN's).
There are comments from people with B70 and B80 (as well as below) reporting success.
The repair can be done in several ways. I have tested the scenario of when you cannot cold-boot into the system, but have a correctly set-up adb access.
while booted into CWM 5.5.0.4 ...
step 1: use adb to push a good recovery [I used Rogue XM v1.3.0 (CWM-based v5.0.2.7)]***
step 2: flash the zip
step 3: use the adb shell to execute the following command
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
*** Do not flash stock recovery. There is no good reason to do it (stock recoveries are generally pretty useless) and you are flirting with trouble if there are signature checks that your custom components might fail. Use trusted custom recoveries
Click to expand...
Click to collapse
(If you entered the shell, don't forget to exit at the end.)
Now you should "Reboot system".
When rebooting, you will notice the ASUS splash screen with a blue progress line. This indicates that the /staging partition got picked up and is being processed (i.e. your payload is being flashed to the recovery partition).
When you next boot into recovery, you should NOT see the 5.5.0.4 screen.
Continue by flashing your ROM if you need to.
Word of the day: teamwork. Peace!
UPDATE 5: Roach2010 published a fixed version of CWM v5.5.0.4
You may find it here. You still need to clear the boot-recovery flag by following the procedure described above or using the command line, as explained by Roach2010 here.
My personal observations so far are that, after flashing Koush's CWM 5.5.0.4, I cannot replace it with any other CWM's I've tried (roach, solarnz, using the RecoveryInstaller app).
The available recovery blobs get written to the staging partition (mmvblk0p4) but appear to not be touched on boot.
I have the 9.2.1.11 bootloader on B70 with SBK v.2
I flashed both ways and got stuck not being able to flash using the staging partition, which is the typical way to reflash recovery. So if you flash this, there is no way to unflash it. I think it also uses a different sdcard mount, so it makes it a little tougher to get a fresh zip to flash onto there.
When it's working normally, cwm will flash to the staging partition on reboot. When it's recovery bootlooping, the flash to staging will be skipped, which makes it difficult to flash a new recovery. I looked at the init.rc files and noted that the cwm 5.5.04 version doesn't even touch the staging partition, so it will be ignored completely.
I did have success reflashing a full rom- EBT, LNX, SOS, and APP or bootloader, boot.img, recovery, and system. This might work for others too, although I never had a problem of always booting into recovery. If it boots into recovery after flashing a full rom, then it might not work since we'll be stuck with the same init.rc.
I don't know all the inner workings of what happens at the boot process, so does anyone have any ideas about what is causing this.
Some things I found out:
to mount the internal sdcard so that you can push a new rom- use adb shell
mount /dev/block/mmcblk0p7 /data/
ls /sdcard/
exit
then from your pc, type:
adb push /path/to/your/rom.zip /data/media
There are other ways too- I think cwm will mount data when you try to flash a zip from the sdcard.
Here's the init.rc's
part of 92111 stock recovery init.rc
Code:
on early-init
start ueventd
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /sdcard
mkdir /staging
mkdir /system
mkdir /data
mkdir /cache
mkdir /btmac
mount /tmp /tmp tmpfs
mount ext4 /dev/block/mmcblk0p1 /system wait
# mount ext4 /dev/block/mmcblk0p1 /system ro remount
mount ext4 /dev/block/mmcblk0p2 /cache wait nosuid nodev
chown system cache /cache
chmod 0770 /cache
mount ext3 /dev/block/mmcblk0p4 /staging wait nosuid nodev
chown system staging /staging
chmod 0770 /staging
mount ext4 /dev/block/mmcblk0p7 /data wait nosuid nodev
chown system system /data
chmod 0771 /data
part of cwm init.rc
Code:
on early-init
start ueventd
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /sdcard
mkdir /staging
mkdir /system
mkdir /data
mkdir /cache
mount /tmp /tmp tmpfs
mount ext4 /dev/block/mmcblk0p2 /cache wait nosuid nodev
chown system cache /cache
chmod 0770 /cache
---------- Post added at 01:53 PM ---------- Previous post was at 01:18 PM ----------
Does mounting and clearing/formatting cache do anything for anyone stuck in the recovery loop?
I thought this issue popped up before too- are we reinventing fire?
feisty_noodle said:
I have the 9.2.1.11 bootloader on B70 with SBK v.2
Click to expand...
Click to collapse
Same specs here, installed ROM Manager via market, purchased premium ROM Manager, installed recovery via ROM Manager.
I have attempted to restore to previous ROM using recovery and it restores system but fails data.
I have attempted the restore to stock and unrooted using the methods listed in XDA, and because it will not allow a reboot after flashing the factory unrooted firmware it does not work. I had actually seen mention of a soft brick if unable to reboot and thought that is what had happened. After flashing the factory unrooted firmware I was unable to cold boot.
Sent from my Transformer TF101 using xda premium
sandiegopaneraiguy said:
Same specs here, installed ROM Manager via market, purchased premium ROM Manager, installed recovery via ROM Manager.
I have attempted to restore to previous ROM using recovery and it restores system but fails data.
I have attempted the restore to stock and unrooted using the methods listed in XDA, and because it will not allow a reboot after flashing the factory unrooted firmware it does not work. I had actually seen mention of a soft brick if unable to reboot and thought that is what had happened. After flashing the factory unrooted firmware I was unable to cold boot.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I used the free version and I don't get the bootloops. Can you check something for me- in /sdcard/clockworkmod/download/ there will be a file there maybe something like -210115432
look around and see if you can find something like this:
Code:
{
"name": "Asus Transformer",
"flash_recovery": "dd if=%s of=/dev/block/mmcblk0p4 ;",
"version": "5.5.0.4",
"init": "init.ventana.rc",
"key": "tf101",
"lunch": "cm_tf101-userdebug"
}
These seem to be the parameters that cwm uses to flash the recovery. See if they are any different.
Add me to the forced recovery boot list, but I have a twist to add. I flashed via Rom Manager and I'm running Revolver 4.0 beta 1.2.
Reboot #1 after flashing the new CWM 5.5.0.4 went as usual - no forced recovery
Reboot #2 also worked fine
Reboot #3 - I forced a shutdown, then rebooted fine
Reboot #4 - this time I forced a reboot into recovery, and now I'm stuck in the recovery loop unless I hold down the volume button.
So...until I booted INTO recovery, everything was working fine.
pooh-bah said:
Add me to the forced recovery boot list, but I have a twist to add. I flashed via Rom Manager and I'm running Revolver 4.0 beta 1.2.
Reboot #1 after flashing the new CWM 5.5.0.4 went as usual - no forced recovery
Reboot #2 also worked fine
Reboot #3 - I forced a shutdown, then rebooted fine
Reboot #4 - this time I forced a reboot into recovery, and now I'm stuck in the recovery loop unless I hold down the volume button.
So...until I booted INTO recovery, everything was working fine.
Click to expand...
Click to collapse
are there any recovery commands in your /cache or /cache/recovery folders?
gee one said:
are there any recovery commands in your /cache or /cache/recovery folders?
Click to expand...
Click to collapse
/cache is empty
/cache/recovery has one file, "last_log" - this appears to be a log of when I first entered the recovery about 30 min ago.
Regarding your question about /sdcard/clockworkmod/download/ - I see the same as you posted above.
I got the same thing as Poo-Bah.
Everything was fine until I booted into recovery, now that's all I can boot into unless I cold boot into android.
I'm on bootloader 9.2.1.11 on a B90.
I was wondering if there are any files that tell the system what to boot into and if those are something we can edit. Sorry, I don't have a lot of experience with android, but I'm willing to help as much as I can.
Here is what is in my cache file...
Starting recovery on Sun Mar 4 19:12:16 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
ClockworkMod Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /staging ext3 /dev/block/mmcblk0p4 (null) 0
4 /data ext4 /dev/block/mmcblk0p7 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=IML74K
ro.build.display.id=IML74K
ro.build.version.incremental=eng.koush.20120226.195010
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Sun Feb 26 19:50:53 PST 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=Transformer
ro.product.brand=asus
ro.product.name=US_epad
ro.product.device=tf101
ro.product.board=ventana
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=tf101
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.2.1.11-20120221 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.2.1.11-20120221:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=tf101
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dataroaming=false
ro.cm.version=9.0.0-RC0-tf101-KANG
ro.modversion=9.0.0-RC0-tf101-KANG
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=0388924343df52d7
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=wifi-only
ro.bootloader=unknown
ro.hardware=ventana
ro.revision=0
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=stopping
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Sent from my Transformer TF101 using xda premium
---------- Post added at 09:56 PM ---------- Previous post was at 09:53 PM ----------
gee one said:
I used the free version and I don't get the bootloops. Can you check something for me- in /sdcard/clockworkmod/download/ there will be a file there maybe something like -210115432
look around and see if you can find something like this:
Code:
{
"name": "Asus Transformer",
"flash_recovery": "dd if=%s of=/dev/block/mmcblk0p4 ;",
"version": "5.5.0.4",
"init": "init.ventana.rc",
"key": "tf101",
"lunch": "cm_tf101-userdebug"
}
These seem to be the parameters that cwm uses to flash the recovery. See if they are any different.
Click to expand...
Click to collapse
I have seven files in that folder, none of which match the one you mention.
I opened each of them with the text viewer and found nothing like what you are seeing. I posted the contents of my recovery log above.
OK- I have recovery bootloops now. Does any one have them and isn't running on Revolver4? I did not get them with stock or team eos, but those roms don't have a reboot to recovery that works, as far as I could tell. I had to flash to Revolver4 to get them.
gee one said:
OK- I have recovery bootloops now. Does any one have them and isn't running on Revolver4? I did not get them with stock or team eos, but those roms don't have a reboot to recovery that works, as far as I could tell. I had to flash to Revolver4 to get them.
Click to expand...
Click to collapse
I'm running stock rooted.
AlcoholicDoc said:
I'm running stock rooted.
Click to expand...
Click to collapse
Do you have any mods that allow you to reboot into recovery from the power menu?
gee one said:
Do you have any mods that allow you to reboot into recovery from the power menu?
Click to expand...
Click to collapse
Nothing. With the exception of being rooted and having CWM installed, I'm bone-stock.
Thanks, that helps. I had a stock-ish rom and I couldn't get the recovery bootloops. Very curious.
Anyone think NVFlash CWM will work? I have a B50 model that can take NVFlash, I just don't know the exact steps of getting it done. I downloaded the NVFlash CWM. Do I just throw that into the nvflash folder and go from there?
kxs783kms said:
Anyone think NVFlash CWM will work? I have a B50 model that can take NVFlash, I just don't know the exact steps of getting it done. I downloaded the NVFlash CWM. Do I just throw that into the nvflash folder and go from there?
Click to expand...
Click to collapse
NVFlash should be able to fix this issue. Use one of the tutorials to unbrick to stock with NVFlash. Then re-root. You'll be fine
I wish I had a B50, I'd be done with this crap already.
The good news is that there is just the recovery.img nvflash, so I don't have start from stratch with my rom. The bad news is that the link to download the NVFlash folder keeps telling me to check back later. :/
kxs783kms said:
The good news is that there is just the recovery.img nvflash, so I don't have start from stratch with my rom. The bad news is that the link to download the NVFlash folder keeps telling me to check back later. :/
Click to expand...
Click to collapse
I'm in the same predicament and want to try the same thing as you. Could you provide a link to the Recovery only NVFlash thread please? I've tried to search but cannot find the one you are talking about.
Can anyone link me to another NVFlash download for the Transformer, other than the one going through the AndroidRoot.mobi website. That one leads me to a FileFactory link that download it, but it appears to not be working at the moment. Thanks.
---------- Post added at 06:06 PM ---------- Previous post was at 06:04 PM ----------
ShadowZephyr said:
I'm in the same predicament and want to try the same thing as you. Could you provide a link to the Recovery only NVFlash thread please? I've tried to search but cannot find the one you are talking about.
Click to expand...
Click to collapse
Here you go buddy, but it's not working for me(the files download link that is.) http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
Related
I've seen a lot of threads detailing how to create an Ext4 partition using Gparted but if you don't want to download the image and would rather do it all on your phone, here's how:
This entire procedure should take less than 5min so you can go back to messing with your phone in other ways.
REQUIRES:
CLOCKWORK MOD RECOVERY
ADB
FINGERS
I am not responsible for any damage done to your phone doing this process. =.=
1. Download the zip file provided.
2. Extract the zip file to the same folder you have ADB in. (You should now have a folder named ext4 in the same folder you have ADB)
3. Reboot the phone into MAGDLR. Then select the option to boot into the recovery.
4. Make sure that /system/ is mounted using the option to mount partition in Clockwork Recovery.
5. Open a command (cmd) prompt and cd into your folder with ADB.
6. Run these commands in the command prompt. (Commands are in BOLD)
adb push ext4 /system/etc/
adb shell
parted /dev/block/mmcblk0
print (make note of the total size of your partition here)
resize 1 0 xxxx (where xxxx is the size you want for your FAT32 partition. It should equal total size of your partition that you gleaned from print minus 1024 for the ext4 partition you're about to set up)
mkpartfs primary ext2 xxxx yyyy (where xxxx is where your previous partition ended and yyyy is the total size of your sdcard)
.... (Let it do its thing. Shouldn't take more than a minute)
print (Make sure that everything is correct: You have a fat32 partition running from 0 to xxxx and an ext2 partition running from xxxx to the total size of your partition)
quit
Now to utilize the two files we previously pushed to /system/etc/
chmod 777 /system/etc/tune2fs
chmod 777 /system/etc/e2fsck
/system/etc/tune2fs -j /dev/block/mmcblk0p2 <- You now have ext3
/system/etc/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2 (Note: CAsE SEnSitiVE)
/system/etc/e2fsck -fpDC0 /dev/block/mmcblk0p2 (Note: CAsE SEnSitiVE) <- You now have ext4
7. You can check that it's truly ext4 by:
parted /dev/block/mmcblk0
print (It should now read that you have a FAT32 and an ext4 partition.)
quit
You're all done! Now you have a 1GB ext4 partition for all your data and apps. If you know what you're doing, these same steps can be modified so that you have two ext4 partitions if you'd like. You can also alter the size of your ext4 partition to something smaller if you don't have that many apps to install or have a smaller SDcard (512MB should be sufficient in most cases, 1GB is slightly overkill IMO)
i will try with my HD2. I need more space to install app on sd not on phone. Thanks so much
Hi, I follow your instruction but when I get a "Permision deined" error when I type in the following commond
/system/etc/tune2fs -j /dev/block/mmcblk0p2
Can you please help?
Many many thanks!!
justj said:
Hi, I follow your instruction but when I get a "Permision deined" error when I type in the following commond
/system/etc/tune2fs -j /dev/block/mmcblk0p2
Can you please help?
Many many thanks!!
Click to expand...
Click to collapse
Crap. I forgot a step. You have to type
chmod 777 /system/etc/tune2fs
chmod 777 /system/etc/e2fsck
prior to using those files. That should fix the permission denied error.
I've edited the OP to reflect the changes, thanks for pointing that out.
Thanks man
Thanks Bro I have successfully make ext4 and I am enjoying my new Rom
Using HTC Desire runnymede 5.0
Amazing. I will keep it for future reference, although I partitioned my SD with CWM recovery and Gparted.
What kind of partition is made when using CWM? I made a 1GB partition on my card that way, and it works great. But I've heard good things about having it as ext4. How does this guide reflect the fact that I already have an SD-EXT on my card that's not necessarily ext4?
Thanks!
please help
please help me i cant get it to work... its same with /system mounted and unmounted...not even one 3rd app is working for me on my win 7 64x when i want to create ext4 this is my last hope. card is brand new 8gb ultra speed its working fine so cant be problem there. it seems like chmod 777 will delete that file..
Code:
C:\Users\OgziR\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>adb
push ext4 /system/etc/
push: ext4/tune2fs -> /system/etc/tune2fs
push: ext4/e2fsck -> /system/etc/e2fsck
2 files pushed. 0 files skipped.
1573 KB/s (603400 bytes in 0.374s)
C:\Users\OgziR\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>adb
shell
~ # /system/etc/tune2fs -j /dev/block/mmcblk0p2
/system/etc/tune2fs -j /dev/block/mmcblk0p2
/sbin/sh: /system/etc/tune2fs: Permission denied
~ # chmod 777 /system/etc/tune2fs
chmod 777 /system/etc/tune2fs
~ # /system/etc/tune2fs -j /dev/block/mmcblk0p2
/system/etc/tune2fs -j /dev/block/mmcblk0p2
/sbin/sh: /system/etc/tune2fs: not found
~ #
Hye... I have 2 question...
My phone is a HTC HD2 running an NexusHD2.ICS.CM9.HWA.V2.3 ROM... The cmd prompt cant seem so fine my device. Do have any advice on this???
Secondly, what do i do with the ext4.zip file??? I mean, do it extract it, or put in same folder with ADB??
Btw, i am Super Noob on this, so i apologize if my question offends anyone... 1000 apologizes...
OK, first of all, do you have adb installed correctly? If cmd prompt can't find your device that is the most likely problem.
As for what to do with ext4.zip, you need to extract it to your adb folder.
Sent from my Vivid 4G using xda app-developers app
I have a nexus 7 16 GB tablet with a busted screen. There's some files I want to get off it but I can't figure out how to do it. I have several clockworkmod backups on the device that I was trying to get off it through adb but couldn't do it.
I tried adb pull /data/media/clockworkmod/backup but it says the folder doesn't exist
I also tried adb pull /sdcard/clockworkmod/backup and same result.
I also tried using holo backup but it requires me to unlock the device but since the screen is broken I can't do this without using an otg cable which I don't have.
What I'm really after are some songs I created using the autorap app by Smule. If there's another way I can retrieve these files I would greatly appreciate it.
Did you not have it set to connect to your computer as an mtp media device? If so, just pull what you want from there.
This seems overly obvious to me, so clearly there is something that I am missing, and I don't want to make it sound like I am being a complete tool or anything.
Sent from my Nexus 7 using Tapatalk
jma9454 said:
Did you not have it set to connect to your computer as an mtp media device? If so, just pull what you want from there.
This seems overly obvious to me, so clearly there is something that I am missing, and I don't want to make it sound like I am being a complete tool or anything.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
It connects as a media device and it's rooted and has usb debugging enabled. When I go into the tablet on the computer there's no backup folder under clockworkmod. I can enter recovery mode and all my backups show up but I can't access the backups when it's connected to the computer. I read somewhere that clockworkmod puts their backups in /data/media to prevent people from messing things up I guess but the adb pull method gives me that error. I don't know what else to do besides buying an otg cable and hooking up a usb mouse.
OK, yeah, I can't think of anything. When you're in recovery mode, is there a way to push files to the computer within recovery? I have never dealt with CWM, as I used TWRP on my kindle fire, and haven't added a bootloader to my nexus 7 yet.
Sent from my Nexus 7 using Tapatalk
jma9454 said:
OK, yeah, I can't think of anything. When you're in recovery mode, is there a way to push files to the computer within recovery? I have never dealt with CWM, as I used TWRP on my kindle fire, and haven't added a bootloader to my nexus 7 yet.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Not that I know of. When the tablet is in recovery mode it won't connect to the computer.
You can use adb in cwm recovery so no problem to download everything to computer.
One more thing I can try to recommend, and I'll get more information on this, is that there was an "app" called terminal, and you might be able to push the files you want into your computer from that. Give me a few hours while I contact someone that knows about that app to see if it would work on the nexus 7 and where to find it.
--EDIT--
Never mind, that would require keyboard input from you. I don't know what I was thinking. If there isn't a way to mount everything from CWM then I don't know what else I can do for you. Sorry.
Sent from my Nexus 7 using Tapatalk
jkkk88 said:
You can use adb in cwm recovery so no problem to download everything to computer.
Click to expand...
Click to collapse
So you're saying even though the adb pull method won't work when the tablet's on it will mysteriously work when in recovery? I don't see why that would make a difference. I feel the files I'm looking for might be in a different folder than /data/media/clockworkmod/backup or /sdcard/clockworkmod/backup.
Boot into CWM recovery mode, connect n7 to computer with USB cable and do what do you need. Adb daemon is started in CWM recovery automatically without any user interaction and n7 setting. I didn't tried it yet but there is command "adb backup <switches>" you can try to put content of n7 to computer or use standard adb commands. As I don't use nandroid backups I can't say where they are located but when you issue
Code:
adb pull /sdcard
and
Code:
adb pull /data
you will find them in you computer.
On n7 GSM here is output of some commands in recovery mode (in my case twrp but cwm will be the same):
Code:
[[email protected] ~]$ adb shell
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)~ # mount /dev/block/mmcblk0p3 /system
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p10 on /data type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /sdcard type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p5 on /cache type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
# mount point fstype device
#/sdcard datamedia /dev/null
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
/radio ext4 /dev/block/platform/sdhci-tegra.3/by-name/RDO
/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
~ # ls -l /dev/block/platform/sdhci-tegra.3/by-name/APP
lrwxrwxrwx 1 root root 20 Nov 1 08:36 /dev/block/platform/sdhci-tegra.3/by-name/APP -> /dev/block/mmcblk0p3
~ # mount /dev/block/mmcblk0p3 /system
jkkk88 said:
Boot into CWM recovery mode, connect n7 to computer with USB cable and do what do you need. Adb daemon is started in CWM recovery automatically without any user interaction and n7 setting. I didn't tried it yet but there is command "adb backup <switches>" you can try to put content of n7 to computer or use standard adb commands. As I don't use nandroid backups I can't say where they are located but when you issue
Code:
adb pull /sdcard
and
Code:
adb pull /data
you will find them in you computer.
On n7 GSM here is output of some commands in recovery mode (in my case twrp but cwm will be the same):
Code:
[[email protected] ~]$ adb shell
~ # mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)~ # mount /dev/block/mmcblk0p3 /system
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p10 on /data type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p10 on /sdcard type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
/dev/block/mmcblk0p5 on /cache type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
# mount point fstype device
#/sdcard datamedia /dev/null
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
/radio ext4 /dev/block/platform/sdhci-tegra.3/by-name/RDO
/usb-otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
~ # ls -l /dev/block/platform/sdhci-tegra.3/by-name/APP
lrwxrwxrwx 1 root root 20 Nov 1 08:36 /dev/block/platform/sdhci-tegra.3/by-name/APP -> /dev/block/mmcblk0p3
~ # mount /dev/block/mmcblk0p3 /system
Click to expand...
Click to collapse
Ok I figured it out. The folder I was trying to pull really didn't exist. I just did adb shell to find what files were in there but I can't find the autorap files I was looking for. They may have gotten deleted.
>>> Please note that Vashiru reworked this guide for reliability and alternate values, so I recommend you check his various posts in this thread starting with this one. <<<
Click to expand...
Click to collapse
THE PROBLEM
As many of us have noticed, it is fairly easy to get an "Out of space" message when installing apps on our phones because, for some weird reason, Oppo decided that the storage part of the device should linger in the dark ages, when /userdata and /sdcard were separate partitions and you only had 2GB of data storage, even if your phone was a 32GB model.
Now, imagine that you are running KitKat and would like to try ART. This may be a bad idea as, if your data partition is more than 30% full, you will find that while converting your apps to this new format, Android will run out of space.
At OppoForums, a few bright people started looking into the issue and, of course, there is a way to improve the situation.
WARNING!
If you follow the steps below correctly, you should not run in any trouble. If you do not, however, you may end up spending much more time fixing your phone.
FIRST, THE THANKS SECTION
Anders tinkered with his device’s partition table until he got to where he had grown the /userdata partition to something useable. Yes, it’s some people’s definition of “play”
Jousa11 is the first person trying to put a guide together explaining the steps to reproduce Anders’ work. WARNING: I did no get to see said guide as Jousa quickly deleted it due to the risks involved. So, take that in account!
Rockman for providing the last resort rescue tools in case you brick your phone
Lucky for providing the WiFi fix
Please let me know if you are not on this list and I forgot to give you credit!
YOU WILL NEED
The hardware:
An Oppo Find5 phone(!)
A computer (Windows/Linux/Mac) with adb installed and working
A USB cable
On your computer:
adb
[Optional] fastboot
On your phone (SDCard):
parted + mke2fs + tune2fs
mmcblk0p21_persist_ext4.img
openrecovery-twrp-2.6.3.0-find5-TP-patch.img
[Optional] gdisk
You will use parted to work on your partition table; mke2fs and tune2fs to create ext4 filesystems on some of these partitions (parted does not know how to create ext4 partitions)
mmcblk0p21_persist_ext4.img is an image that you need to restore your /persist partition and avoid issues such as non-working WiFi.
openrecovery-twrp-2.6.3.0-find5-TP-patch.img is a patched recovery image. I know: you already have a recovery image if you are going through these steps. However, we are going to wipe it so you want to install this guy before rebooting. Note that if you forget, you can always flash it later using fastboot.
On your computer:
adb to access your phone recovery, push files to SDCard, reboot...
[Optional] fastboot. You will only need fastboot if you mess up your recovery partition.
WHAT IF SOMETHING GOES AWFULLY WRONG?
You may “brick” your phone. Apparently it’s near impossible to hard brick your Find5, though. See below.
First, Anders recommends making a backup of your partition table. I didn’t because I felt that if I messed something up, it would be a partitions’ content rather than the partition table but that’s not the wisest approach.
Furthermore, if you are really worried about what stilly error your fat fingers will cause (I know I should be!) you can also backup your partitions.
Backing up your partition table:
On your phone:
Code:
gdisk -b /sdcard/gpt.bin /dev/block/mmcblk0
Backing up a single partition:
On your phone:
Code:
dd if=/dev/block/mmcblk0p<partition id> of=/sdcard/backup-<partition id>.bin
On your computer:
Code:
adb pull /sdcard/gpt.bin
adb pull /sdcard/backup-<partition id>.bin
LAST RESORT
OK. So, you've bricked your phone. Now what?
First, you will need Windows. So if you're on a Mac or Linux and have no access to a Windows machine/VM, er..don't brick your phone.
- Download drivers and tools
- Download and follow the instructions
READY ? LET'S GET STARTED
>>>>>>>>>>>> First, Download The Files <<<<<<<<<<<<
Then...
On your computer:
UPDATE As dixxa pointed out, mke2fs and tune2fs may already be present on your device. It was not the case for me but you should check first; it seems like a good idea to use existing binaries.
Code:
adb reboot recovery
adb push parted /sbin
adb push mke2fs /sbin
adb push tune2fs /sbin
On your phone:
Code:
chmod 755 /sbin/parted /sbin/mke2fs /sbin/tune2fs
umount /cache
umount /sdcard
umount /emmc
umount /data
parted /dev/block/mmcblk0
You are now in the parted shell.
CAREFUL! Do not delete any partition below 20 or you will enter "Big Oops" territory. I recommend typing carefully and, yes, staying away from copy/paste operations that may swallow a character like, say, the '2' in '20'
Note that the size value I am using here is '4GB' for /userdata (rather than 2GB). I guess you could make /userdata bigger than 4GB, in which case you would have to recompute all the offsets in the commands below(!)
Code:
# rm sdcard
rm 29
# 28 thru 23 are reserved
rm 28
rm 27
rm 26
rm 25
# rm recovery
rm 24
# rm misc
rm 23
# rm cache
rm 22
# rm persist
rm 21
# rm data/emmc
rm 20
# now, re-create partitions but data is bigger
mkpart primary 1325 5421
name 20 userdata
mkpart primary 5421 5430
name 21 persist
mkpart primary 5430 5967
name 22 cache
mkpart primary 5967 5968
name 23 misc
mkpart primary 5968 5979
name 24 recovery
mkpart primary 5979 6012
name 25 reserve1
mkpart primary 6012 6019
name 26 reserve2
mkpart primary 6019 6028
name 27 reserve3
mkpart primary 6028 6062
name 28 reserve4
mkpart primary 6062MB 100%
name 29 sdcard
# exit parted shell
q
Let's create a file system on the partitions that require one. Note that I am formatting the SDCard using VFAT as, yes, EXT4 is a better FS, but it is also incompatible with Oppo's ROM and some apps may not require the proper permissions etc.
Code:
# Notes:
# -m 0: no reserved blocks
# -c 0: no max mount count
# -C -1: no mount count
# -i -1: max_int interval between checks
mke2fs -t ext4 -m 0 -L userdata /dev/block/mmcblk0p20
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p20
mke2fs -t ext4 -m 0 -L persist /dev/block/mmcblk0p21
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p21
mke2fs -t ext4 -m 0 -L cache /dev/block/mmcblk0p22
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p22
# Hey look it’s an ext4 SDCard!
mke2fs -t ext4 -m 0 -L sdcard /dev/block/mmcblk0p29
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p29
# Actually to avoid errors like unable to write to root of sdcard:
mkdosfs -n sdcard -F 32 /dev/block/mmcblk0p29
mount -t vfat /dev/block/mmcblk0p29 /sdcard
At this point, we have clobbered the /persist partition and this could cause issues as mentioned earlier. Let's restore it.
Code:
# Restore /persist partition
mount -t ext4 /dev/block/mmcblk0p29 /sdcard
# On computer
adb push mmcblk0p21_persist_ext4.img /sdcard/
# On phone
dd if=mmcblk0p21_persist_ext4.img of=/dev/block/mmcblk0p21
IMPORTANT! Flash your recovery partition now. If you wait until after rebooting, you will need to use fastboot instead.
Code:
# Recovery partition: on computer
adb push openrecovery-twrp-2.6.3.0-find5-TP-patch.img /sdcard/
# On phone
dd if=openrecovery-twrp-2.6.3.0-find5-TP-patch.img of=/dev/block/mmcblk0p24
Admire your work
Code:
parted /dev/block/mmcblk0 print
Reboot into your new recovery and install your favorite ROM
FAQ
Q: Is this dangerous?
A: Yes. Yes, it is.
Q: Any tip?
A: Yes. Follow these instructions carefully and if something wrong happens, unless you know what you are doing, leave your device alone and come here to ask for help.
Q: Can I hold you responsible for any damage to my phone/etc?
A: As usual, the answer is 'No'
Q: I found an error in your write-up!
A: Please let me know immediately.
-Chris.
You should probably use the latest TWRP 2.6.3.1 found here: http://techerrata.com/file/twrp2/find5/openrecovery-twrp-2.6.3.1-find5.img
Looks good to me. Just be very carefully doing this.
Sent from my Find 5 using xda app-developers app
gdisk -b /sdcard/gpt.bin /dev/block/mmcblk0
those commands need to be typed in recovery even that one ?
Yes although I imagine this particular command should also work when booting system.
Sent from my Find 5 using Tapatalk
This thread is fine the only problem here is with those 2 binaries: mke2fs and tune2fs
You don't need to push them or chmod them since they are already in the recovery
Except that that thread is perfect.
Since we're at toying with partition, can't we merge the partitions in some way ?
Just wondering is there any way to build a script to do this in an automated way thus avoiding user errors and typos?
There is a thread on the oppo forums
http://www.oppoforums.com/threads/guide-resizing-internal-storage-on-find-5-32gb.8361/
Hello everyone,
is the guide for the 32 or 16 gb model?
I have 16 gb Oppo find 5.
Thanks.
PS: what "on your phone" is supposed to mean"?
Click to expand...
Click to collapse
If you don't know what does that mean don't do it you'll screw your phone.
hi
Please would you make something like this for oppo find 7a x9006?
thanks
Anyone willing to recompute all the offsets dor just one 16gb partition?
Scribed henceforth from thy G pad.
Hi all, I am trying to do this mod and I am half way through it with a problem
I am stuck on the new file system, I cannot use mke2fs or tune2fs, i get
Code:
mke2fs: not found
like it doesn't even exist, but it does I can see it. I get the same error for tune2fs. but parted and gdisk work fine.
Yes I did push them and chmod 755 them.. and I have tried running it from the /sbin directory.
Help!
Hello!
I'm getting the same error over and over again creating /dev/block/mmcblk0p21 to /dev/block/mmcblk0p22:
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p21
"Bad magic number in super-block while trying to open /dev/block/mmcblk0p21"
"Couldn't find valid filesystem superblock"
So i can't create a file system on the created partitions. I have been looking everywhere for an answer. Somebody have an idea?
U should just wait. Andrew dodd found a way to make find7a have unified partition and he claims he can make it work on find5 as well. Let's give him a bit to figure it out tho.
Scribed henceforth from thy G pad.
Gdisk not working...
Ok guys sort of a noob here... Firstly, totally appreciate what you guys are doing here... I wants it bad, thass why i'm here.
So far... I have i have done...
"adb reboot recovery"
"adb push gdisk /sbin"
I figured that's how you are supposed to install it ... hope i'm not wrong, but i guess it pushed through fine
But after rebooting to system in TWRP , i opened terminal emulator and when i use the command
"gdisk -b /sdcard/gpt.bin /dev/block/mmcblk0"
I get ...
"/system/bin/sh: gdisk: not found"
now i'm too scared to proceed without backing up the partition tables... so please help...
edit - FYI , i'm running the last build of Asylum Carbon... should i just go back to latest oopo stable stock rom and then root my device again and then try all this again... would that help... ???
Directly from Andrew Dodds g+ " IT HAS BEGUN.
The first phase of Find 7a/7s LVM testing is here.* See linked post for details.* (Sorry to disappoint, but the first phase is "make sure we don't break existing configurations")
Once this phase is complete, the remaining list is:
Fix up the remaining TWRP issues (make RECOVERY_SDCARD_ON_DATA runtime instead of compile-time)
Make user-friendly conversion processes
Once things are solid on Find 7, I'll work on Find 5 and N1."
Stay thirsty my friends. Good things ahead
Sent from my A0001 using Tapatalk
Does this work for the 16gb model?
Can someone help please?
I'm trying to do this, but after enter in parted [parted /dev/block/mmcblk0] when i try to do "rm 29", i get "can't remove 29: no such file or directory
I'm doing the "on your phone" commands in TWRP command line., is that correct?
I'm running stable colorOS 1.0.9i
Finally I finish the process.
My notes:
Goal:
Keep my current system intact (stable colorOS 1.0.9i , because i have no patience to format, install a new ROM and reinstall/recofigure everything
So I backup everything on phone with TWRP and I push sdcard content (wich include the system backup i made) with ADB
1 - If I push mke2fs and tune2fs IT WILL NOT WORK. I flash the last find 5 recovery (openrecovery-twrp-2.8.1.0-find5.img) and I dont push or chmod anyting, parted, mke2fs, tune2fs are all already in the recover and that's the only way I could run mke2fs and tune2fs
edit: 1.5 - The phone commands had to be enter via ADB shell. In TWRP command line, after you enter in parted it will not accept commands.
2 - To "rm 29", i had to "umount /dev/block/mmcblk0", otherwise "rm 29" fail due to partition in use
3 - after this instruction:
mount -t vfat /dev/block/mmcblk0p29 /sdcard
(the last one on the 4 block of code)
We have this:
# Restore /persist partition
mount -t ext4 /dev/block/mmcblk0p29 /sdcard
This instruction was the only one that give me a error, so I move to the next ones.
The error was that the partition was busy, what makes senses because in the last instruction we mount the same partition on the same folder but with different file system!!??
So I move to the next instruction. I have no idea if it's a instructions mistake but it looks like, because it says "# Restore /persist partition" but the command has nothing to do with /persist
4 - FINISH
5 - Reboot in recovery. Push sdcard backup to /sdcard. restore system backup with TWRP restore
Voila, my phone exactly as before but with 3,76GB for APPS. Finally!!! The "running out of space" message on a flagship quad-core 2GB RAM phone!!!!!!?????? Was driving me CRAZYYYYY
Thanks Fickx for the up to date information, I just did my re-partition successfully, here's what I did:
- Use Rashr update the recovery to twrp-2.8.1.0
- reboot into recovery
- connect to PC (Make sure adb works, "adb devices")
- on PC:
> adb shell
> umount /cache
> umount /sdcard
> umount /emmc
> umount /data
> umount /dev/block/mmcblk0p29
> parted /dev/block/mmcblk0
> rm 29
>...
> rm 20
> mkpart primary 1325 5421
> name 20 userdata
> ...
> name 29 sdcard
> q
> mke2fs ...
> ...
> mount -t -vfat /dev/block/mmcblk0p29 /sdcard
Open another PC command terminal
> adb push mmcblk0p21_persist_ext4.img /sdcard/
> adb push openrecovery-twrp-2.8.1.0-find5.img /sdcard/
Back to original terminal in "adb shell".
> dd if=/sdcard/mmcblk0p21_persist_ext4.img of=/dev/block/mmcblk0p21
> dd if=/sdcard/openrecovery-twrp-2.8.1.0-find5.img of=/dev/block/mmcblk0p24
> exit
> adb reboot recovery
Flash the rom.
Q&A for [HACK] Grow your data partition
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HACK] Grow your data partition. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
killerskincanoe said:
Directly from Andrew Dodds g+ " IT HAS BEGUN.
The first phase of Find 7a/7s LVM testing is here.* See linked post for details.* (Sorry to disappoint, but the first phase is "make sure we don't break existing configurations")
Once this phase is complete, the remaining list is:
Fix up the remaining TWRP issues (make RECOVERY_SDCARD_ON_DATA runtime instead of compile-time)
Make user-friendly conversion processes
Once things are solid on Find 7, I'll work on Find 5 and N1."
Stay thirsty my friends. Good things ahead
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Any update ?
abuthabet87 said:
Any update ?
Click to expand...
Click to collapse
I'm working on it, got a base for the find5 on the omni gerrit already. Though far from usable
Sent from my One X+
2 questions
Is this Hack [suficient] safe, or should I wait for LVM?
If i do a full backup of my current system (colorOS 1.0.9i Stable) and after the hack, restore the ROM, will my phone be exactly the same than before but with 4GB for apps?
Thanks for the great work
LVM needs ALOT of work right now :/
I'm trying to do this, but after enter in parted [parted /dev/block/mmcblk0] when i try to do "rm 29", i get "can't remove 29: no such file or directory
I'm doing the "on your phone" commands in TWRP command line., is that correct?
I'm running stable colorOS 1.0.9i
Guys, After I exit parted shell, I can't execute mke2fs/tune2fs commands! I get:
/sbin/sh: mke2fs: not found
though I can find them (mke2fs and tune2fs) inside /sbin/ after I cd into it!
How can I solve this ?
Edit:
Solved ... I just rebooted into recovery again.
I did it It works hehehe
Thank you very much for this amazing instructions.
I had some difficulties while executing some of the instructions, but I did some search and tried unplugging then plugging the cable or rebooting into recovery again when the shell was giving me a hard time, and everything is back as it was except now I have 4GB internal storage !!
Does this have to be done while the phone is running ColorOS? I started the procedure on my 16GB phone, running CM11, but didn't get too far.
There is no /sbin. Found tune2fs and mke2fs in /system/bin. No parted there.
From PC over USB, copied parted to Download directory.
On phone, opened a Terminal, then 'su root'.
Remounted /system/bin rw: 'mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system'
Copied parted from Download to system/bin.
chmod 755 /system/bin/parted
Most of the umount commands fail.
Started 'parted /dev/block/mmcblk0'
Fails on first 'rm 29' because it is not unmounted.
I gave up there.
Interesting, automated repartioning:
www <dot> youtube <dot> com / watch?v=2CoTIojZGlI
Shame it doesn't have a 4GB option.
@Redfoox (in dev thread), did you push mke2fs and tune2fs at the beginning of the procedure or did you use the ones already included in TWRP?
I got this error?
Code:
/sbin # mke2fs -t ext4 -m 0 -L userdata /dev/block/mmcblk0p20
/sbin/sh: mke2fs: not found
The command also does not work in TWRP!
Anyone any idea what I should do now?
---------- Post added at 02:40 PM ---------- Previous post was at 02:36 PM ----------
Vashiru said:
@Redfoox (in dev thread), did you push mke2fs and tune2fs at the beginning of the procedure or did you use the ones already included in TWRP?
Click to expand...
Click to collapse
I did push the mke2fs and tune2fs at the beginning. Probably shouldn't have done that?
I have to wait each post for 4 minutes to post a new one
I've tried doing that during my second attempt, but got stuck at exactly the same point.
The fact that it shows mke2fs: not found tells me that you have both pushed it and CHModded it.
Push the files again, this time don't CHMod them and try it from the TWRP Terminal Emulator (from ADB shell just gives you permission denied but I didn't try it from TWRP that time).
If that doesn't work try CHModding them from TWRP. If that also doesn't work I'm out of a clue. All you could do at that point is use the last resort method (saved my device 2 times) and try the procedure again without pushing the files first.
Tried it and it gives the same errors. Cannot even chmod it through the terminal emulator.
I will go for the last resort method than
Too bad. Alright, feel free to ask questions if you run into trouble when you try again.
It worked i have 4GB now!
The only thing now is that my wifi does not work and I did do the following:
Code:
# Restore /persist partition
mount -t ext4 /dev/block/mmcblk0p29 /sdcard
# On computer
adb push mmcblk0p21_persist_ext4.img /sdcard/
# On phone
dd if=mmcblk0p21_persist_ext4.img of=/dev/block/mmcblk0p21
output of terminal:
Code:
/sdcard # dd if=mmcblk0p21_persist_ext4.img of=/dev/block/mmcblk0p21
16384+0 records in
16384+0 records out
8388608 bytes (8.0MB) copied, 3.260498 seconds, 2.5MB/s
Any idea how to restore this? I even redid this step without succes.
---------- Post added at 07:21 PM ---------- Previous post was at 06:27 PM ----------
Got it working now. I had tot install modem 4.2.
Nice, enjoy the 4 GB!
Please help guys this is turning out to be a really frustrating experience...T___T
How are you guys even pulling this off... T___T
My adb works when the phone is booted but after "adb reboot recovery" and once in TWRP it cant see the device... and hence i cant proceed with the commands in Adb shell when the phone is connected and in twrp. i am running Liquidsmooth rom but i went back to the original rom to try this.
I'm able to execute
" chmod 755 /sbin/parted /sbin/mke2fs /sbin/tune2fs
umount /cache
umount /sdcard"
But not these ...
"umount /emmc
umount /data"
It says file or Directory not found.
then when i enter parted with the next command "parted /dev/block/mmcblk0"
I enter into parted, but cant see any of the following
"# rm sdcard
rm 29
# 28 thru 23 are reserved
rm 28
rm 27
rm 26
rm 25
# rm recovery
rm 24
# rm misc
rm 23
# rm cache
rm 22
# rm persist
rm 21
# rm data/emmc
rm 20
# now, re-create partitions but data is bigger
mkpart primary 1325 5421
name 20 userdata
mkpart primary 5421 5430
name 21 persist
mkpart primary 5430 5967
name 22 cache
mkpart primary 5967 5968
name 23 misc
mkpart primary 5968 5979
name 24 recovery
mkpart primary 5979 6012
name 25 reserve1
mkpart primary 6012 6019
name 26 reserve2
mkpart primary 6019 6028
name 27 reserve3
mkpart primary 6028 6062
name 28 reserve4
mkpart primary 6062MB 100%
name 29 sdcard
# exit parted shell
q"
Now i'm totally clueless on how to proceed further... Would appreciate if you guys can shed a bit more clarity... This is really turning out to be a frustrating experience. Please guys...
Going back to Liquidsmooth to use my phone ... will again reinstall original os tomorrow and try again. :crying:
OK, so I got TWRP running sweet and now following the improved descriptions in main thread post #34.
Got stuck here, all before has been ok:
mke2fs -t ext4 -m 0 -L persist /dev/block/mmcblk0p21
Message back is:
Could not stat /dev/block/mmcblk0p21 --- no such file or directory
The device apparently does not exist; did you specify it correctly?
Now what?
EDIT - think I have it sorted. I didn't scroll down enough in the post #34 windows and missed some 'parted' commands!
EDIT - 'adb shell' had quit, and it wouldn't connect again. Tried to reboot TWRP to recovery, but it didn't recover, now stuck at Oppo text logo, can't connect by adb, doesn't respond to power button. Bricked.
EDIT - was able to access the phone by fastboot only, not adb. Flashed TWRP recovery again, it rebooted and took quite a while, now it is stuck at the cyanogenmod 12 boot up spinning arrow for 10+ minutes, maybe it will recover eventually. If not, I'll try to reflash CM12 too.
Hello
Today was the third try to get this thing working ^^
But somehow i cant get past the first command.
Every time i try to unmount things like /cache or /dev umount only returns "invalid argument.
I never pushed the files from the zip. TWRP 2.8.3.0 is used.
I tried to attach a screenshot to help, but im too new to do that -.-
Thanks in advance
In case this helps anyone, these are the steps I took to check internal storage for errors:
In Android, get the mount points for /data and /system
Code:
$ su
$ grep /data /fstab.qcom
/dev/block/bootdevice/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr,inline_data wait,check,encryptable=/dev/block/bootdevice/by-name/metadata
$ grep /system /fstab.qcom
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait
Boot to recovery (TWRP)
Unmount /system, just to be safe
(You can use adb shell or the TWRP terminal)
Code:
umount /system
Check /system for errors using e2fsck (since it's an ext4 filesystem)
(The mount points are a little bit different in TWRP)
Code:
e2fsck -fv /dev/block/platform/soc.0/by-name/system
In TWRP, go to Mount, check System, uncheck everything else
Check /data for errors using fsck.f2fs (since it's an f2fs filesystem)
Code:
fsck.f2fs -f /dev/block/platform/soc.0/by-name/userdata
Reboot
Or, you could just use any old Terminal app, do:
su
touch /forcefsck
... and reboot.
Tomo123 said:
Or, you could just use any old Terminal app, do:
su
touch /forcefsck
... and reboot.
Click to expand...
Click to collapse
I read that but it didn't work for me. Have you tried it on a Moto G 2015?
Tomo123 said:
Or, you could just use any old Terminal app, do:
su
touch /forcefsck
... and reboot.
Click to expand...
Click to collapse
... isn't / still part of the initrd, and hence volatile? afaik android doesn't pivot_root