Yesterday, I installed the MidNIGHT ROM and after applying the zip from my sd card and booting, my phone vibrates and soft boots so I had to Odin back to DK28 for the night to be functional.
Today, I decided to try Bonsai. I followed the instructions to a T on this page h**p://code.google.com/p/bonsai/wiki/Install . Started from stock DK28, rooted with OneClickRootCWM3.zip, phone booted, got into Recovery mode with the 3 finger salute. CWM3 did its thing and converted the file system to EXT4 and then I applied the Bonsai4All_Leafless_v2.0.0.zip ROM file. No errors, phone booted and the same issue, soft boots and vibrates randomly. Can't get to recovery but could go to download mode no problem so back to stock DK28 again.
Anyone having the same issue and figured it out? Thanks in advance for anyhelp, would love to try out one of these ROMs.
Weird. You're sure it converted to ext4 just fine? It sounds like a kernel issue. Try a rom that has both rfs and ext4 support and see if that boots properly. Or flash the dual fs kernel over bonsai or midnight.
Well, I wouldn't be able to flash the dual fs kernel over bonsai or midnight because when the phone gets to that weird state I can't get to recovery mode, only download mode.
I guess I could try one of the older ROMs of the same flavor that mentions support for both file systems.
I won't have time for another attempt until tomorrow, so would also appreciate any other feedback as well. Thanks.
Solution
Check which clockwork version you boot into when flashing the EXT4 roms. I've had this exact problem before. When you boot into recovery with 3 fingers, you'll probably be in CWM 2.1.1.0 (or something ending in 2**.0). This is a RFS only CWM and won't be able to write or read from EXT4. When your in this CWM go to advanced and reboot your recovery. you should now enter into CWM 2**.2 or CWM 3 if you just flashed a rom like midnight or Bonsai 1.1.4 (note, you cannot go from stock rooted to Bonsaie 2.0.0 without installing a more recent version of CWM that can read EXT4 to flash a rom that is purely EXT4 based.
If you still can't get it to work, your best bet is to odin back to stock DK28 and start over by using the CWM3 one-click root.
Thanks, I'll check for that on my next attempt. Also after the initial installation of CWM3 that I ran from the bat file then it booted my phone. Then I went to recovery with 3 fingers and that is when it automatically kicked off the file conversion process where all the output is on my phone.
Is there a way to modify the bat file to pipe the output to a log file so I can troubleshoot afterwards?
comtrade said:
Thanks, I'll check for that on my next attempt. Also after the initial installation of CWM3 that I ran from the bat file then it booted my phone. Then I went to recovery with 3 fingers and that is when it automatically kicked off the file conversion process where all the output is on my phone.
Is there a way to modify the bat file to pipe the output to a log file so I can troubleshoot afterwards?
Click to expand...
Click to collapse
Instead of double-clicking the bat file, run it from a terminal as "run.bat > logfile"
You won't see any output from the program on your screen when you do this though.
Does this seem as all went well?
The 1st part after clicking on the bat file while connected to pc
Original one click made by joeykrim and one click installer made by noobnl and f
iron
busybox by skeeterslint
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Copy and run the exploit (may take up to two minutes). Ignore messages about re-
logging in.
If more than five minutes pass, reboot the phone and try again.
109 KB/s (5392 bytes in 0.048s)
1 KB/s (43 bytes in 0.021s)
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
[*] checking NPROC limit ...
[+] RLIMIT_NPROC={2382, 2382}
[*] Searching for adb ...
[+] Found adb as PID 6503
[*] Spawning children. Dont type anything and wait for reset!
[*]
[*] If you like what we are doing you can send us PayPal money to
[*] [email protected] so we can compensate time, effort and HW costs.
[*] If you are a company and feel like you profit from our work,
[*] we also accept donations > 1000 USD!
[*]
[*] adb connection will be reset. restart adb server on desktop and re-login.
Wait for phone to reconnect...
Mount system as r/w, cleanup old files, do some basic configuration
72 KB/s (4793 bytes in 0.064s)
Copying files onto phone...
142 KB/s (26264 bytes in 0.179s)
633 KB/s (196521 bytes in 0.302s)
869 KB/s (486948 bytes in 0.546s)
9 KB/s (479 bytes in 0.046s)
Setting permissions...
Installing busybox...
Installing clockworkmod redirector
105 KB/s (6473 bytes in 0.059s)
push: recoveryfiles/recovery -> /system/bin/recoveryfiles/recovery
push: recoveryfiles/postrecoveryboot.sh -> /system/bin/recoveryfiles/postrecover
yboot.sh
push: recoveryfiles/nandroid-md5.sh -> /system/bin/recoveryfiles/nandroid-md5.sh
push: recoveryfiles/fix_permissions -> /system/bin/recoveryfiles/fix_permissions
push: recoveryfiles/adbd -> /system/bin/recoveryfiles/adbd
5 files pushed. 0 files skipped.
1576 KB/s (921434 bytes in 0.570s)
push: recoveryres/images/progress_fill.png -> /system/bin/recoveryres/images/pro
gress_fill.png
push: recoveryres/images/progress_empty.png -> /system/bin/recoveryres/images/pr
ogress_empty.png
push: recoveryres/images/indeterminate6.png -> /system/bin/recoveryres/images/in
determinate6.png
push: recoveryres/images/indeterminate5.png -> /system/bin/recoveryres/images/in
determinate5.png
push: recoveryres/images/indeterminate4.png -> /system/bin/recoveryres/images/in
determinate4.png
push: recoveryres/images/indeterminate3.png -> /system/bin/recoveryres/images/in
determinate3.png
push: recoveryres/images/indeterminate2.png -> /system/bin/recoveryres/images/in
determinate2.png
push: recoveryres/images/indeterminate1.png -> /system/bin/recoveryres/images/in
determinate1.png
push: recoveryres/images/icon_installing.png -> /system/bin/recoveryres/images/i
con_installing.png
push: recoveryres/images/icon_error.png -> /system/bin/recoveryres/images/icon_e
rror.png
push: recoveryres/images/icon_clockwork.png -> /system/bin/recoveryres/images/ic
on_clockwork.png
push: recoveryres/keys -> /system/bin/recoveryres/keys
12 files pushed. 0 files skipped.
259 KB/s (59209 bytes in 0.222s)
Installing clockworkmod recovery...
1277 KB/s (313888 bytes in 0.239s)
1530 KB/s (6726500 bytes in 4.290s)
RedBend Update Agent 6,1,14,1
FOTA : Make Block Device Nodes
lcd_init(498): start!
lcd_init(507): fb0 open success
lcd_init(514): width = 480, height = 800
page_msize: 4096, phy_unit_size: 262144
src: /data/local/tmp/zImage
dst: /dev/block/bml8 partition size: 0x780000
part_size: 0x780000
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 262144 bytes
read 172900 bytes
read finished
Cleaning up files...
Press any key to exit the script.
Press any key to continue . . .
Then I disconnect from PC after reboot and 3 finger into CWM3 it automatically starts this part
Checking for ext4 partitions...
Checking /system...
E:failed to mount /system (invalid argument)
/system may be rfs. Checking...
Checking /data...
E:failed to mount /data (invalid argument)
/system may be rfs. Checking...
E:failed to mount /cache (invalid argument)
/system may be rfs. Checking...
Filesystem needs to be converted to ext4.
A backup and restore will now take place.
If anything goes wrong , you backup will be
named before-ext4-convert-1296248584. Try restoring
it in case of error. SD Card Space free: 12581 MB
Backing system...
Backing up data...
Backing up .android_secure...
Backing up cache...
No sd-ext found. Skipping backup of sd-ext.
Generating md5 sum
Backup complete!
Checking MD5 sums...
Restoring data...
Restoring .android_secure...
Restoring cache...
No sd-ext found. Skipping restore of sd-ext.
Generating md5 sum
Restore complete!
So am I converted to ext4 or did it fail?
it looks ok. Open a terminal program on your phone and type "mount"
Look for /dev/block/stl9 /dev/block/stl10 and /dev/block/stl11 and see if they have ext4 to the right of them.
Worked!!!! Thanks to all.
The thing I did different was wipe each of these 3 times
--Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete
- Wipe cache partition
-- Wiping cache...
Formatting /cache...
Cache wipe complete.
Then went to Advanced
- Wipe Dalvik Cache
E:unknown volume for path [/sd-ext]
Dalvik Cache wiped.
comtrade said:
Worked!!!! Thanks to all.
The thing I did different was wipe each of these 3 times
--Wiping data...
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete
- Wipe cache partition
-- Wiping cache...
Formatting /cache...
Cache wipe complete.
Then went to Advanced
- Wipe Dalvik Cache
E:unknown volume for path [/sd-ext]
Dalvik Cache wiped.
Click to expand...
Click to collapse
LMAO this is hilarious. i think its so weird that you have to wipe 3 times to install roms. why 3? so strange...
Better safe than sorry
Wiping jokes side... I think it's just to make sure it actually succeeds in doing so... And the "3" is not a set number.
Btw, I had a similar experience as the OP- vibrate, boot loop dealy. I was able to do the 3 finger (up volume, then down) to get back in to CW.. Wipe and flash a diff rom w/no probs. Truly epic and quantum are the only ones that have worked smoothly for me on EXT4
Sent from my SPH-D700 using Tapatalk
Skrewup5 said:
LMAO this is hilarious. i think its so weird that you have to wipe 3 times to install roms. why 3? so strange...
Click to expand...
Click to collapse
At one point there was a question of whether cwm 2.x was properly wiping certain partitions so people started suggesting that you do the wipe 2-3 times to be sure. And with all the new people that show up on the forum, it is easier to tell them to wipe everything 3 times than repeatedly explain the situation. People only seem to have an intermittent problem with the wipe. Most roms are set to wipe before they install. I usually just wipe everything once and then flash with no problem. But if I *do* have a problem, I go back and wipe everything 3 times just to make sure.
DiGi760 said:
At one point there was a question of whether cwm 2.x was properly wiping certain partitions so people started suggesting that you do the wipe 2-3 times to be sure. And with all the new people that show up on the forum, it is easier to tell them to wipe everything 3 times than repeatedly explain the situation. People only seem to have an intermittent problem with the wipe. Most roms are set to wipe before they install. I usually just wipe everything once and then flash with no problem. But if I *do* have a problem, I go back and wipe everything 3 times just to make sure.
Click to expand...
Click to collapse
thanks for the explanation,i just got used to wiping three times every time i put a new rom on so its not even an issue haha.
Using midNight 3.0 EXT4 with some themes from SuperNova.
Themes and Add-Ons from SuperNova page:
- Blue 2.0 THEME ONLY DOWNLOAD - CWM 3.0
- Add AOSP Lockscreen - CWM3
- SamsungWidgets - CWM3
- Sprint Apps - CWM3
- Battery Full Pop-up Fix - CWM3
- ANIMATION #1
- MMS/SMS BLUE -
So far okay, except twice I have to take out the battery because my screen will not come on. It went to display off mode and power button will not bring it up. When hitting the power button, the display will stay off but the bottom 4 menu buttons light up only.
Has anybody seen this problem? Comments are welcome.
Thanks in advance
was gettin the weird vibration thing and ALOT of google.framework forceclose..
with midNIGHT never had a problem before.. odined to DK28 did one click CWM3
tried flashing again and it did the stock sprint boot with the SDK android boot flashing in teh middle and then alot of forceclose like swipe and a few other programs forceclosing took my battery out odin'd back to dk28 one clicked AGAIN lol and did the no journal.. and bonsai and now its working fine dont midNIGHT and Bonsai have the same kernal or is my phone just having is monthly bleeding from the usb port deal XD and just being a ass with roms.
midNIGHT 3.2
I am missing the AIO a little on the new BYOR. Have to go flash happy. Like the idea though. Maybe there is a way to get both. Can someone tell me how to get the fixes in the AIO with a BYOR action? Mod the ROMs zip? Thank in advance.
this happens alot to me all you do is reboot into clockwork and reflash ontop of your rom and it works the second time usually
comtrade said:
Yesterday, I installed the MidNIGHT ROM and after applying the zip from my sd card and booting, my phone vibrates and soft boots so I had to Odin back to DK28 for the night to be functional.
Today, I decided to try Bonsai. I followed the instructions to a T on this page h**p://code.google.com/p/bonsai/wiki/Install . Started from stock DK28, rooted with OneClickRootCWM3.zip, phone booted, got into Recovery mode with the 3 finger salute. CWM3 did its thing and converted the file system to EXT4 and then I applied the Bonsai4All_Leafless_v2.0.0.zip ROM file. No errors, phone booted and the same issue, soft boots and vibrates randomly. Can't get to recovery but could go to download mode no problem so back to stock DK28 again.
Anyone having the same issue and figured it out? Thanks in advance for anyhelp, would love to try out one of these ROMs.
Click to expand...
Click to collapse
I would recommend flashing Bonsai a second time. That might clear up the problem. The path from a stock DK28 is particularly rocky. Would recommend that if you have ever flashed stock DK28, that you NOT go back to stock when flashing Bonsai or midNight. You just make things harder on yourself and it does not accomplish anything.
To those who are suggesting going to another kernel that supports both RFS and EXT4, the kernel in Bonsai and therby midNight does still support both RFS and Ext4. We just don't support it...
If you flash to some other kernel, you are guaranteed to break your phone.
Skrewup5 said:
thanks for the explanation,i just got used to wiping three times every time i put a new rom on so its not even an issue haha.
Click to expand...
Click to collapse
With Bonsai or midNight, there is no reason to go through the wiping exercise. That is handled by the install process. It really is as easy as we describe it in the install instructions (linked in my sig). We have not left out steps...
Related
Well i used the OTA Simple Root and it worked, but now everytime i try to go into recovery (power plus volume down) it searches the files again and tries to run all the updates and reboot the system. Then when i skip that and try to go to recovery to update a rom i get a black screen with a red triangle and cant get to the recovery menu even. I did one time and i was in boot loop.
My questions are these, how can i set my phone back to completely stock with nothing on the sd card but what i need.
Is there anyway to fix this with out having to start all over again?
Easier fix is to install Rom manager. Once inside tell it to flash clockwork recovery. Boom. Have recovery again.
Sent from my EVO
Delete any files named PC36IMG.zip from the root of your SD card. Then either flash Amon_RA's or Koush's Clockwork recovery.
===============================================================
===============================================================
Simple Root 1.47.651.1 OTA Edition
===============================================================
===============================================================
* server not running *
===============================================================
Pushing files, PLEASE WAIT!.....
===============================================================
* daemon not running. starting it now *
* daemon started successfully *
912 KB/s (26172 bytes in 0.028s)
1209 KB/s (655360 bytes in 0.529s)
160 KB/s (1813 bytes in 0.011s)
17 KB/s (424 bytes in 0.024s)
107 KB/s (1754 bytes in 0.016s)
cannot stat 'PC36IMG.zip': No such file or directory
Pushing complete!
Press any key to continue . . .
I formated my sd card and tried to start simple root over again and after step one i get this message, what does it mean and how can i fix it? thanks for the fast replies.
twigums said:
===============================================================
===============================================================
Simple Root 1.47.651.1 OTA Edition
===============================================================
===============================================================
* server not running *
===============================================================
Pushing files, PLEASE WAIT!.....
===============================================================
* daemon not running. starting it now *
* daemon started successfully *
912 KB/s (26172 bytes in 0.028s)
1209 KB/s (655360 bytes in 0.529s)
160 KB/s (1813 bytes in 0.011s)
17 KB/s (424 bytes in 0.024s)
107 KB/s (1754 bytes in 0.016s)
cannot stat 'PC36IMG.zip': No such file or directory
Pushing complete!
Press any key to continue . . .
I formated my sd card and tried to start simple root over again and after step one i get this message, what does it mean and how can i fix it? thanks for the fast replies.
Click to expand...
Click to collapse
Download whichever PC36IMG.zip file is relevant to that method and place it on the root of your SD card.
me thinks the PC36IMG.zip is in included in the OTA simple root zip file, just copy it to the root of your SDCARD using the phone as a USB drive
whit's "Start over" method will work since he has partial root. and it'll update radios appropriately.
Try use toast method 2 nand unlocking and flash the recovery image. Should work just fine.
Sent from my PC36100 using XDA App
i think i found the problem, down load was messed up for simple root, redld it and having no problems so far (crosses fingers)
Hi,
I have a device HTC One X (endeavor).
Looks like I've destroyed the partitions in trying to make swap. Now it looks like:
Code:
ls /dev/block
loop0 loop2 loop4 loop6 mmcblk0 mmcblk0p13 mmcblk0p17
loop1 loop3 loop5 loop7 mmcblk0p12 mmcblk0p15 platform
~ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Error: /dev/block/mmcblk0: unrecognised disk label
~ # parted /dev/block/mmcblk0p12 print
parted /dev/block/mmcblk0p12 print
Error: Error opening /dev/block/mmcblk0p12: Invalid argument
~ # parted /dev/block/mmcblk0p13 print
parted /dev/block/mmcblk0p13 print
Error: Error opening /dev/block/mmcblk0p13: Invalid argument
~ # parted /dev/block/mmcblk0p15 print
parted /dev/block/mmcblk0p15 print
Error: Error opening /dev/block/mmcblk0p15: Invalid argument
~ # parted /dev/block/mmcblk0p17 print
parted /dev/block/mmcblk0p17 print
Error: Error opening /dev/block/mmcblk0p17: Invalid argument
Please, help.
Maybe try running a RUU.
Sent from my HTC One X using XDA Premium 4 mobile app
RUU is not working. In stage sign update it says "wrong image". Tried several RUU from different sources.
Actually the problem is CWM can't mount any of /data /system /cache /sdcard
I found that I can't use RUU for my hboot 1.72.
And also I can't downgrade hboot without S-OFF.
And S-OFF is impossible for endeavor (jtag only?)
So, any way to restore partitions manually?
Reflash your firmware only using the flashtool..btw..can be that you need more than one try..i had a similar problem solved with this..
Sent from my HTC One X using XDA Premium 4 mobile app
Alex-V said:
Reflash your firmware only using the flashtool
Click to expand...
Click to collapse
What do you mean? fastboot flash zip rom.zip?
The problem is I've mistook /dev/block/mmcblk0p14 with /dev/block/mmcblk0. I've tried delete it and recreate it. So now any custom rom is going to boot loop.
Any recovery says "Can't mount /sdcard". The same for /data, /system and /cache.
Ibrix said:
What do you mean? fastboot flash zip rom.zip?
The problem is I've mistook /dev/block/mmcblk0p14 with /dev/block/mmcblk0. I've tried delete it and recreate it. So now any custom rom is going to boot loop.
Any recovery says "Can't mount /sdcard". The same for /data, /system and /cache.
Click to expand...
Click to collapse
yes...flash hboot (its contained in firmware) new...using this tool
http://forum.xda-developers.com/showthread.php?t=1924003
and for firmware
http://forum.xda-developers.com/showthread.php?t=1957376
Alex-V said:
yes...flash hboot (its contained in firmware) new...using this tool
http://forum.xda-developers.com/showthread.php?t=1924003
and for firmware
http://forum.xda-developers.com/showthread.php?t=1957376
Click to expand...
Click to collapse
Ok, for instance I'm trying to flash 1.39 hboot.
Code:
D:\>fastboot flash zip firmware.zip
sending 'zip' (12876 KB)...
OKAY [ 1.556s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 2.647s
It's because I already have 1.72 hboot. Any ideas how to flash it? Or make S-OFF?
Ibrix said:
Ok, for instance I'm trying to flash 1.39 hboot.
It's because I already have 1.72 hboot. Any ideas how to flash it? Or make S-OFF?
Click to expand...
Click to collapse
As far as I understand which HOX version you have, there's no S-OFF available. However, if you're on 1.72 hboot you may need to get the firmware from 4.18.401 ROM - I believe this one matches your 1.72 hboot. You'll find appropriate firmware (and if it works also ROM) on android-revlution. (I can't post links so far, so just google for "android revolution rom download" and you'll find HTC ONE X section there with a link to firmware downloads, you'll find mentioned 4.18.401 in 401 folder).
Good luck, let us know how it works!
Well, I just tried few stock 4.18.401.2 roms from different sources. All of them was unable to flash.
Code:
D:\>fastboot flash zip rom.zip
sending 'zip' (697216 KB)...
OKAY [ 83.700s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 114.712s
Ibrix said:
Well, I just tried few stock 4.18.401.2 roms from different sources. All of them was unable to flash.
Code:
D:\>fastboot flash zip rom.zip
sending 'zip' (697216 KB)...
OKAY [ 83.700s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 114.712s
Click to expand...
Click to collapse
Lol you can't Fastboot flash a rom.zip !!! You supposed to get the firmware zip from the official OTA file !
And as i see Alex already told you about a firmware.zip ...... that's not a rom zip
And read the threads he linked you to. Especially the placeholder thread. Its explained in the OP how to flash the firmware
Mr Hofs said:
Lol you can't Fastboot flash a rom.zip !!! You supposed to get the firmware zip from the official OTA file !
And as i see Alex already told you about a firmware.zip ...... that's not a rom zip
Click to expand...
Click to collapse
O'rly? AFAIK rom.zip from RUU can be fastboot flash (if hboot version is compatible).
I do not familiar with rom.zip taken not from RUU. So, how to flash "stock odexed 4.18.401.2" room from android-revolution? (I can't mount sdcard in CWM, remember?)
And how can help flashing firmware.zip in itself? However, I've flashed it (of course) before try to flash rom.zip. It doesn't solve my problem. I am unable to mount any partition in CWM.
What if you sideload the rom.zip to the sdcard. Look for that ?
Mr Hofs said:
What if you sideload the rom.zip to the sdcard. Look for that ?
Click to expand...
Click to collapse
SDcard doesn't recognized by windows. But I can see it as a device in MiniTool Partition Wizard. I've tried to initialize it both as MBR or GPT, create partition fat32 or ext2 - in any case it's unable to mount from recovery. Even if put there some file.
I was able to:
1. Following this steps: http://forum.xda-developers.com/showpost.php?p=26030990&postcount=17
2. Restore vfat sdcard partition
3. SD card still not recognized by windows
4. adb push rom.zip /sdcard/rom.zip (rom.zip is a http://forum.xda-developers.com/showthread.php?t=1546970)
5. Flash boot.img from rom.zip
6. Flash stock recovery also from http://forum.xda-developers.com/showthread.php?t=1546970
7. Re-lock
8. Load, reload, factory reset, recovery...
Normal load just stuck with white screen "HTC quietly brilliant". Recovery and factory reset show me this (attached).
View attachment 2362949
Interesting thing,
From philz_touch_5.15.9 recovery I am still unable to mount any partitions, and from adb shell:
Code:
~ # ls /dev/block
ls /dev/block
loop0 loop2 loop4 loop6 mmcblk0 platform
loop1 loop3 loop5 loop7 mmcblk0p17
~ # parted /dev/block/mmcblk0 print
parted /dev/block/mmcblk0 print
Error: /dev/block/mmcblk0: unrecognised disk label
~ # parted /dev/block/mmcblk0p17 print
parted /dev/block/mmcblk0p17 print
Error: Error opening /dev/block/mmcblk0p17: Invalid argument
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.2 GB, 31268536320 bytes
4 heads, 16 sectors/track, 954240 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
~ # fdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
Disk /dev/block/mmcblk0p17: 0 MB, 1024 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/block/mmcblk0p17 doesn't contain a valid partition table
openrecovery-twrp-2.4.0.0 (it's latest version which is works with touchscreen) at start asking me "please enter your password". Adb shell wont work. From the recovery terminal I can see that only mmcblk0 exist in /dev/block/, and fdisk -l show me it's empty and "doesn't contain a valid partition table".
BTW, from any recovery it is the same:
Code:
cat /proc/emmc
dev: size erasesize name
mmcblk0p5: 00800000 00001000 "recovery"
mmcblk0p4: 00800000 00001000 "boot"
mmcblk0p12: 50000000 00001000 "system"
mmcblk0p13: 14000000 00001000 "cache"
mmcblk0p17: 00200000 00001000 "misc"
mmcblk0p1: 00600000 00001000 "wlan"
mmcblk0p2: 00200000 00001000 "WDM"
mmcblk0p20: 00200000 00001000 "pdata"
mmcblk0p3: 00600000 00001000 "radiocab"
mmcblk0p14: 650000000 00001000 "internalsd"
mmcblk0p15: 89400000 00001000 "userdata"
mmcblk0p19: 01600000 00001000 "devlog"
mmcblk0p16: 00200000 00001000 "extra"
Any ideas?
I had the same problems with error in partitions..so I flashed stock recovery for my cid and did the factory reset through bootloader...after s few times and also flashing firmware zip I didn't got any more those issues..flashed again custom rom...used for few hours went back to apx mode and since then even with accessing recovery I can't flash anything as it gives errors etc...I was finally able to flash stock boot.IMG and stock recovery and relocked bootloader...know the repair service has my phone and I wait since nearly two weeks for anything from them...if I won't get the phone tomorrow I will call them...maybe the forgot to sent back or so xD...
Gesendet von meinem HTC Desire HD With Beats Audio mit Tapatalk 4
I don't think HTC will replace my phone after this... xD (see attachments)
The problem was he has discharged with stock recovery and boot stuck, and for some reason wont to charge in hboot or any else available screen for the moment. It also disallow me to flash anything while "low battery". Well, I figured it out... xD
But it is another story...
Ibrix said:
I don't think HTC will replace my phone after this... xD (see attachments)
The problem was he has discharged with stock recovery and boot stuck, and for some reason wont to charge in hboot or any else available screen for the moment. It also disallow me to flash anything while "low battery". Well, I figured it out... xD
But it is another story...
Click to expand...
Click to collapse
If you're careful enough with the reassembly HTC will still replace your phone, though if hboot is accessible they probably wont replace it because of your tampered bootloader, also, you could of charged it while powered off?
Sent from my HTC One X using Tapatalk
humzaahmed155 said:
If you're careful enough with the reassembly HTC will still replace your phone, though if hboot is accessible they probably wont replace it because of your tampered bootloader, also, you could of charged it while powered off?
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
For some reason it wouldn't charge while powered off.. Have no idea why. I've charged it "manually" and now I carefully keeping battery level. From recovery CWM or any else recovery it is charging normally.
So you think if I'll flash stock recovery, boot and rom, relock it - HTC may replace it with new device?
However, it's not so interesting as manually restore partitions table...
Hi evreyone !
I spent hours trying and reading posts everywhere I could without any success.
I'm trying to follow this rooting guide: http://forum.xda-developers.com/showthread.php?t=2634196 (Root and Dual Recovery for Locked Bootloader) and I'm stuck in a bootloop at step 10.
I'm using the last Z1C-lockeddualrecovery2.7.117-BETA.installer.zip and I noticed an error during recovery installation (after DEVICE WILL NOW REBOOT!):
Code:
##########################################################
#
# Installing XZDR version 2.7.117 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
Copy recovery files to system.
Copy mr wrapper script to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW REBOOT!
=============================================
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:101)
at com.android.commands.am.Am.main(Am.java:82)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
=============================================
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
Waiting for your device to reconnect.
After entering CWM for the first time, reboot to system to complete this installer if you want it to clean up after itself.
=============================================
Installation finished. Enjoy the recoveries!
=============================================
(Note that I'm using Linux... I tried to run the bash script both as a user or as root)
If I continue the rooting process by flashing D5503_14.2.A.1.114_Generic UK.ftf (step 9), I'm stuck at step 10 as I can't boot any recovery. The phone is stuck in a bootloop, and after the green light pressing vol up (ou down) won't do anything...
I tried the whole process (from the begining: docomo) several time and end up everytime with the same result: an error at the end of the recovery installation and a bootloop at step 10 that prevent me from entering any recovery...
I'm out of ideas ! What can I do to manage the installation of the recovery ?
OldBeurt said:
What can I do to manage the installation of the recovery ?
Click to expand...
Click to collapse
Try a newer guide - http://forum.xda-developers.com/showthread.php?t=2688933
Thanks for your answer !
XperienceD said:
Try a newer guide - http://forum.xda-developers.com/showthread.php?t=2688933
Click to expand...
Click to collapse
Since I don't have access to any recovery, I don't understand how I can follow this guide (step 5: Go to recovery menu[...]).
What did you meant ?
OldBeurt said:
I don't understand how I can follow this guide (step 5: Go to recovery menu[...])
Click to expand...
Click to collapse
Read the requirements and it links to how to root, and if you can't or won't unlock your bootloader then you're going to have to jump through hoops.
XperienceD said:
Read the requirements and it links to how to root, and if you can't or won't unlock your bootloader then you're going to have to jump through hoops.
Click to expand...
Click to collapse
Of course I red the requirements. The root method described is the same (http://forum.xda-developers.com/showthread.php?t=2642081) than the one I followed (http://forum.xda-developers.com/showthread.php?t=2634196). And so the result is going to be the same: being stuck in a bootloop after flashing the recovery form the computer (flashing witch returns an error that I quoted above).
I need help to "recover" the recovery, I mean to be able to properly flash the dual recovery on my phone (whether I wish to unlock the bootloader or not is not the point for now, since I need to root with the locked bootloader in the first place).
It's obvious that there is an error while installing dualrecovery. However I don't know what could cause that error. I advise you to try install it on a fresh ubuntu / Windows client.
Edit: You are executing the install.sh script right? Because at first you select option 3, which is missing in your output. It looks like you are simply executing installrecovery.sh which is of course wrong.
Thanks for your input !
zxz0O0 said:
It's obvious that there is an error while installing dualrecovery. However I don't know what could cause that error. I advise you to try install it on a fresh ubuntu / Windows client.
Click to expand...
Click to collapse
I don't know where the error came from, but I tried several times (about 10) and it end up the same way ! I will try on another machine (Linux too).
zxz0O0 said:
Edit: You are executing the install.sh script right? Because at first you select option 3, which is missing in your output. It looks like you are simply executing installrecovery.sh which is of course wrong.
Click to expand...
Click to collapse
Yes I'm using install.sh, I just pasted the relevat part of the output, but here I paste all of it:
Code:
Will attempt to get root to install!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Step1 : Waiting for Device.
=============================================
Succes
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
0 KB/s (29 bytes in 0.056s)
362 KB/s (17768 bytes in 0.047s)
325 KB/s (15578 bytes in 0.046s)
11 KB/s (501 bytes in 0.043s)
272 KB/s (11791 bytes in 0.042s)
3186 KB/s (44383 bytes in 0.013s)
70 KB/s (3082 bytes in 0.042s)
9 KB/s (385 bytes in 0.041s)
3645 KB/s (657704 bytes in 0.176s)
3521 KB/s (2597754 bytes in 0.720s)
3936 KB/s (1842873 bytes in 0.457s)
5217 KB/s (2447499 bytes in 0.458s)
193 KB/s (8124 bytes in 0.041s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using rootkitXperia now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread on XDA for more details.
=============================================
ro.build.product=C6903
ro.build.id=14.1.G.1.534
search kallsyms...
1 2 3 4
(kallsyms_addresses=c0899410)
(kallsyms_num_syms=00014df1)
kernel dump...
1 2 3 4 5 6 7 8 9
prepare_kernel_cred=c00b89f4
commit_creds=c00b8518
ptmx_fops=c0ea365c
Succeeded in getroot!
##########################################################
#
# Installing XZDR version 2.7.117 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
Copy recovery files to system.
Copy mr wrapper script to system.
Copy chargemon script to system.
Copy dualrecovery.sh to system.
Copy rickiller.sh to system.
Installing NDRUtils to system.
Copy busybox to system.
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW REBOOT!
=============================================
Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system running?
at com.android.commands.am.Am.run(Am.java:101)
at com.android.commands.am.Am.main(Am.java:82)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:235)
at dalvik.system.NativeStart.main(Native Method)
=============================================
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
Waiting for your device to reconnect.
After entering CWM for the first time, reboot to system to complete this installer if you want it to clean up after itself.
=============================================
Installation finished. Enjoy the recoveries!
=============================================
I put ARHD ROM and everything was fine, until i put Fonter module and changed font and then HOX stuck at quietly brilliant screen..
I was in panic and i wiped everything, and sdcard, and data, and system, everything.. And then i f**** up all..
So now i can go into recovery, i can go in fastboot, everything is working, just i cannot get sdcard to work. I think that it should be formatted but it won't work.. I tried several ways that i googled and on every i stuck
I tried put TWRP but it stuck on swipe to unlock and it won't work, i tried several versions, still nothing..
I tried this How to: Fix a corrupted DATA partition on the HTC One on ARHD webpage ( I cannot put links )
And when i put this
Code:
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
It say
Code:
Could not stat /dev/block/mmcblk0p37 --- No such file or directory
Then i tried this
Code:
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Once all that's done, your recovery program should be able to mount both the /data and /cache partitions. If that's true, you're pretty much done! One thing I found was that I couldn't directly install a new OS (I tried both Cyanogen and Ultimate). In both cases, it would look for stuff in the davik-cache that it couldn't find, so something wasn't installing correctly I think. So, if that happens, flash back to the stock PB31IMG.zip (put it in the root of your /sdcard/ and let hboot install it), and then root your phone anew. That's what I ended up doing.
Again, huge credit for this goes to -Steveo- and ciwrl for helping me figure out which partitions were the right ones (and for supplying parted, which I hadn't been able to find anywhere). If something doesn't end up working, just drop me a pm and we'll see what we can do.
And here it wont when i put command
Code:
parted /dev/block/mmcblk0 mkfs ext2
it say
Code:
Error: /dev/block/mmcblk0: unrecognised disk label
But when i do this
Code:
fdisk -l /dev/block/mmcblk0
it say
Code:
Disk /dev/block/mmcblk0: 31.2 GB, 31268536320 bytes
4 heads, 16 sectors/track, 954240 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0 doesn't contain a valid partition table
I am sorry for bad english, but i really need help, i were searching the web for 10hours and nothing worked.. I need to full format sdcard, so could anyone help me?
Thanks
Please help someone, i need my phone
So nobody wants to help me??
lepi991 said:
So nobody wants to help me??
Click to expand...
Click to collapse
Flash Philz recovery 5.15.9 and mount sd card search in Q&A section I sheared via google drive
I tried that and when i go to Mount SD card it give me only to choose UnMount
lepi991 said:
I tried that and when i go to Mount SD card it give me only to choose UnMount
Click to expand...
Click to collapse
un mount and mount and wait 2 minutes or unmount and wait 2 minutes work with sure on 5.15.9
That didnt worked, when i enter sd card there is only unmount and when i choose that nothing happend..
Finnaly i fixed with busybox and formated card completely and then through adb shell pushed ROM and installed it..
You can lock thread
Read-Me First
1) This procedure may brick your phone and make it useless. Use this procedure at your own risk.
2) This procedure is not official, so it is not supported by Oppo company.
3) This procedure is only for advanced users with a good low-level knowledge of Android storage and adb-fastboot commands.
4) This procedure WILL ERASE ALL YOUR PERSONAL DATA on your phone. Please BACKUP ALL YOUR DATA before using this procedure.
5) This procedure has been tested only on Oppo Find 7 (x9076) phone.
6) This procedure will use an external Micro-SD card to make user run some scripts.
Goal/Purpose
This procedure will resize the two partitions ("userdata" and "sdcard") used by Oppo Find 7 to store personal data, such as apps, photos, images, and so on.
Due to the fact the Oppo Find 7 (x9076) uses an only-3GB "userdata" partition to store apps, while all the remaining space (24 GB) is used for "sdcard" partition to store other data, this matter doesn't provide with enough space to store apps and their related data.
This procedure should be used to enlarge the size of "userdata" partition, to let user have more space for apps and less space for personal data in order to use some ROMs that currently do not provide with support for unified storage ("Unified Storage Layout" or LVM), such as Color OS, CyanogenMod and other ROMs based on CyanogenMod rom.
With the provided compressed file, you will receive some ".sh" files to be used to resize the storage partitions. The namefile of these scripts just means two numbers, the first one is the new size (in GB) of "userdata" partition, while the second one is the new size (in GB) of "sdcard" partition. So, for example, the script "8_19.sh" should be used to have 8 GB for the resized "userdata" partition, and "19 GB" for the resized "sdcard" partition.
How to
1) Make a backup of all your data on your phone.
2) Download and unzip the compressed file.
3) Just unzip the included "external_sd.zip" file on root of your external MicroSD card.
4) Restart into recovery.
5) Run terminal window and execute "adb shell" to go into adb shell.
6) Run command "cd /external_sd/new_scripts".
7) Be sure that all .sh files are in folder "/external_sd/new_scripts".
8) Run one of the provided ".sh" file. Do not unplug the usb cable and wait until the end of the procedure. If you've selected "unified.sh" script, please remember that you have to update the custom recovery (as described in thread "Unified Storage Layout" - http://www.oppoforums.com/threads/tutorial-unified-storage-layout-for-oppo-find-7a.17952/).
9) Enjoy your new storage partitions.
Issues
1) If the procedure will end with the error "Persist partition is damaged. After rebooting into recovery, please run persist_fix application.", you have to reboot into recovery again, and then run the script included inside "persist_fix" folder (it is part of the zipped file "external_sd.zip").
Make sure that "persist" partition will have the "ext4" formatting, because it is happened, many times, that during backup and restore of "persist" partition, something happens to damaged the "ext4" formatting.
2) It is happened, once only, that you cannot reboot into recovery again due to some problems during backup-restore procedure of "recovery" partition. This problem may be simply solved flashing the recovery with "fastboot" command.
Tips & Hints
1) I suggest users of Oppo Find 7a, to use alternate unified procedures (such as “Unified Storage Layout” or LVM) instead of this procedure, due to low storage sizes. It is a non-sense to waste space for two partitions (one dedicated only to the apps, and the other one to user’s data) when you can use only a big one, shared for both apps and data.
2) If you have not enough know-how to use this procedure or if you are afraid of doing something wrong using this procedure, you can wait for a definitive decision from Oppo about storage layout. With last final release of ColorOS (2.0 kitkat), Oppo still continues to use two partitions, with only 3GB dedicated to apps, and the remaining storage space dedicated to user’s data.
There are some rumors about Oppo regarding storage layout, that is Oppo will use the LVM storage layout in the future. Anyway we hope that Oppo may release the guidelines for storage as soon as possible, maybe with next ColorOS release.
3) This procedure makes a backup of the most important partitions in order to restore them after the resizing procedure. The backup is stored on the external MicroSD card at the end of the procedure, so please keep the backup for future reference and to restore it if something goes wrong in the future.
Please take note that only ColorOS is bundled with updated images of few partitions (some of them managed by the backup/restore procedure), but not for all partitions, so the only way to restore an image of a partition currently is to restore it from a stored image (such as the images stored by this procedure).
4) During testing period, I’ve discovered that “persist” partition, managed by this procedure, may lose the “ext4” file system formatting during the backup/restore procedure. On Internet there is a lot of mainstream about this partition, but mainly there is a lot of confusion regarding it. Someone even suggests formatting (so erasing it) this partition whenever users encounter problems on using phone.
As far as I understand, “persist” partition is a mountable partition, it contains important code (binaries and data), mainly regarding wi-fi connections. It is used by all ROMs, including stock and custom ones.
So it is mandatory to preserve the contents of this partition to avoid bootloops, missing or poor wi-fi connections and other serious problems on using this phone.
If you want to know what is the contents of this partition, you can simply boot your ROM, use a terminal prompt, input “su” (you need root permissions) and simply go into “/persist” folder (it is mounted by the ROM).
At the end of the resize procedure, the “ext4” formatting will be checked in order to prevent any problems on “persist” partition. If “ext4” file system formatting is lost, a message will be shown to the user. The user must reboot into recovery, and then use the script included inside “persist_fix” folder (included in “external_sd.zip” file). This script will restore an image of “persist” partition and then check if the problem is solved or not. Please use this script whenever you have problems on “persist” partition (on Internet there is a lot of mainstream about “persist” partition, not only related to Oppo Find 7).
Copyrights
Some scripts included in this procedure are based on scripts written by Coldbird and included into "Unified Storage Layout" procedure. All rights are reserved to Coldbird.
Thanks
1) Thanks to Coldbird, to aut0mat3d and to all people involved into "Unified Storage Layout" procedure.
2) Thanks to all people involved into "LVM Partition Remapping" procedure.
3) Thanks, in advance, to all people that will test this procedure.
References
Why there is only 9.x GB user space on Find 7a (http://www.oppoforums.com/threads/faq-why-there-is-only-9-x-gb-user-space-on-find-7a.11787/)
Unified Storage Layout (http://www.oppoforums.com/threads/tutorial-unified-storage-layout-for-oppo-find-7a.17952/)
Partition Repairscripts for Oppo Find7, Find7a (http://www.oppoforums.com/threads/tool-partition-repairscripts-for-oppo-find7-find7a.20271/)
LVM Partition Remapping (http://forum.xda-developers.com/find-7/orig-development/ref-lvm-partition-remapping-t2865843)
Tested ROMs
1) Color OS – releases 1.2.6 and 2.0.0 Kitkat.
2) AICP – Release 20141018.
Issue: it is not possible to use the "sdcard0" mounting partition, it is set to read-only permission. To solve this issue, you have to flash another ROM before this, reboot and let it write its own folders onto "sdcard0" partition. Finally you can flash AICP rom and use it normally.
3) AOKP – Nightly 2014-10-18.
4) CyanogenMod CM11 – Nightly 20141025.
5) Dirty Unicorns – 20141011 v8.0 weekly.
Issue: bootloop – When a window, for selecting the language, appears, it seems to be blocked and after 5 seconds it reboots.
6) Mokee – 141025 release
7) Nameless ROM – 20141027 nightly
8) Omnirom 20140923 nightly and 20141031 nightly
Issue: bootloop – When a window, for selecting the language, appears, it seems to be blocked and after 5 seconds it reboots.
9) Paranoid Android – 4.6 beta 5 20141021
Issue : no boot – This ROM doesn't boot at all.
Tested also with 4.6 beta 4 20141007 – no problem.
Tested machine
Custom Recovery : TWRP 2.8.0.1
Google Apps : gapps-kk-20140606-signed.zip
New Internal Storage : 8 GB for "userdata" + 19 GB for "sdcard"
External Storage : 32 gb micro-sd class 10
I've tried this method. And I choose unified.
but I can't see that unified (like the pic).
Here the log from command
H:\adt\sdk\platform-tools>adb shell
~ # ←[6ncd external_sd
cd external_sd
/external_sd # ←[6ncd external_sd
cd external_sd
/external_sd/external_sd # ←[6nls
ls
new_scripts
persist_fix
/external_sd/external_sd # ←[6ncd new_scripts
cd new_scripts
/external_sd/external_sd/new_scripts # ←[6nls
ls
10_17.sh
11_16.sh
13_14.sh
8_19.sh
parted
stock.sh
unified.sh
/external_sd/external_sd/new_scripts # ←[6nsh unified.sh
sh unified.sh
=================================================
Retrieving the size of all partitions.....
userdata = 6291456s sectors
sdcard = 50000000 sectors
=================================================
rm: can't remove '/tmp/backup': No such file or directory
=================================================
Unmount all partitions except external_sd ....
=================================================
=================================================
Backup partitions into /tmp folder.....
=================================================
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 0.809779 seconds, 39.5MB/s
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.440292 seconds, 36.3MB/s
3072+0 records in
3072+0 records out
1572864 bytes (1.5MB) copied, 0.036449 seconds, 41.2MB/s
2+0 records in
2+0 records out
1024 bytes (1.0KB) copied, 0.000651 seconds, 1.5MB/s
16+0 records in
16+0 records out
8192 bytes (8.0KB) copied, 0.000746 seconds, 10.5MB/s
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.025429 seconds, 39.3MB/s
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.396552 seconds, 40.3MB/s
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 0.829321 seconds, 38.6MB/s
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 0.840793 seconds, 38.1MB/s
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.424749 seconds, 37.7MB/s
16384+0 records in
16384+0 records out
8388608 bytes (8.0MB) copied, 0.221377 seconds, 36.1MB/s
131072+0 records in
131072+0 records out
67108864 bytes (64.0MB) copied, 1.573372 seconds, 40.7MB/s
253919+0 records in
253919+0 records out
130006528 bytes (124.0MB) copied, 3.915451 seconds, 31.7MB/s
=================================================
We remove and create new partitions .......
=================================================
unified.sh: line 94: can't open /external_sd/new_scripts/parted/find7_unified.pa
rted: no such file
=================================================
Restore partitions from /tmp folder.....
=================================================
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.495464 seconds, 32.3MB/s
3072+0 records in
3072+0 records out
1572864 bytes (1.5MB) copied, 0.199716 seconds, 7.5MB/s
2+0 records in
2+0 records out
1024 bytes (1.0KB) copied, 0.000620 seconds, 1.6MB/s
16+0 records in
16+0 records out
8192 bytes (8.0KB) copied, 0.005822 seconds, 1.3MB/s
2048+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.139941 seconds, 7.1MB/s
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 2.644259 seconds, 6.1MB/s
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 5.312673 seconds, 6.0MB/s
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 5.498313 seconds, 5.8MB/s
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 2.608278 seconds, 6.1MB/s
16384+0 records in
16384+0 records out
8388608 bytes (8.0MB) copied, 1.549714 seconds, 5.2MB/s
131072+0 records in
131072+0 records out
67108864 bytes (64.0MB) copied, 11.840047 seconds, 5.4MB/s
253919+0 records in
253919+0 records out
130006528 bytes (124.0MB) copied, 3.924011 seconds, 31.6MB/s
=================================================
We format userdata, cache and sdcard partitions.....
=================================================
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=userdata
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
196608 inodes, 786432 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=805306368
24 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.14 (22-Dec-2010)
Setting maximal mount count to -1
Setting current mount count to -1
Setting interval between checks to 4294880896 seconds
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=cache
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
32768 inodes, 131072 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=134217728
4 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 28 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.14 (22-Dec-2010)
Setting maximal mount count to -1
Setting current mount count to -1
Setting interval between checks to 4294880896 seconds
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=sdcard
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1564672 inodes, 6250000 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
191 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
tune2fs 1.41.14 (22-Dec-2010)
Setting maximal mount count to -1
Setting current mount count to -1
Setting interval between checks to 4294880896 seconds
=================================================
We restore and check the persist partition.....
=================================================
65536+0 records in
65536+0 records out
33554432 bytes (32.0MB) copied, 4.838189 seconds, 6.6MB/s
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p16: 28/320 files (0.0% non-contiguous), 1085/1280 blocks
=================================================
We copy all /tmp folder into external sdcard....
=================================================
=================================================
End of resizing partitions....
=================================================
Model: MMC 032GE4 (sd/mmc)
Disk /dev/block/mmcblk0: 61071360s
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 16384s 147455s 131072s fat16 modem
2 147456s 148479s 1024s sbl1
3 148480s 148543s 64s dbi
4 163840s 163903s 64s DDR
5 180224s 182271s 2048s aboot
6 182272s 183271s 1000s rpm
7 196608s 229375s 32768s boot
8 229376s 230375s 1000s tz
9 230376s 232423s 2048s pad
10 232424s 235495s 3072s modemst1
11 235496s 238567s 3072s modemst2
12 238568s 259047s 20480s oppodycnvbk
13 259048s 279527s 20480s oppostanvbk
14 294912s 3006463s 2711552s ext4 system
15 3006464s 9297919s 6291456s ext4 userdata
16 9297920s 9363455s 65536s ext4 persist
17 9363456s 10412031s 1048576s ext4 cache
18 10412032s 10444799s 32768s recovery
19 10444800s 10447871s 3072s fsg
20 10452992s 10452993s 2s fsc
21 10452994s 10453009s 16s ssd
22 10453010s 10455057s 2048s misc
23 10455058s 10487825s 32768s LOGO
24 10487826s 10553361s 65536s DRIVER
25 10553362s 10618897s 65536s reserve1
26 10618898s 10651665s 32768s reserve2
27 10651666s 10668049s 16384s reserve3
28 10668050s 10799121s 131072s reserve4
29 10813440s 60813439s 50000000s ext4 sdcard
30 60817408s 61071326s 253919s grow
Done.
/external_sd/external_sd/new_scripts # ←[6n
Maybe I make a mistake but can you explain more detail what's wrong?
Thanks
OldClass said:
I've tried this method. And I choose unified.
but I can't see that unified (like the pic).
Here the log from command
.......................
Maybe I make a mistake but can you explain more detail what's wrong?
Thanks
Click to expand...
Click to collapse
May you kindly show me the output of command "ls -l /external_sd/new_scripts/parted/", because I am worried about upper/lower case of extracted files. Thanks.
italianquadcore said:
May you kindly show me the output of command "ls -l /external_sd/new_scripts/parted/", because I am worried about upper/lower case of extracted files. Thanks.
Click to expand...
Click to collapse
Here is the output :
K:\adt\sdk\platform-tools>adb shell
~ # ←[6nls -l /external_sd/new_scripts/parted/
ls -l /external_sd/new_scripts/parted/
/external_sd/new_scripts/parted/: No such file or directory
~ # ←[6nls -l /external_sd/external_sd/new_scripts/parted/
ls -l /external_sd/external_sd/new_scripts/parted/
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
-rwxrwxrwx root root 872 2014-11-06 23:36 find7_10_17.parted
-rwxrwxrwx root root 872 2014-11-06 23:36 find7_11_16.parted
-rwxrwxrwx root root 872 2014-11-06 23:36 find7_13_14.parted
-rwxrwxrwx root root 872 2014-11-06 23:36 find7_8_19.parted
-rwxrwxrwx root root 868 2014-11-06 23:36 find7_stock.parted
-rwxrwxrwx root root 872 2014-11-06 23:36 find7_unified.parted
~ # ←[6n
i'm sorry has make mistake when put extracted folder in my sd card
now i can repart my internal Find 7 X9076
thanks for your help
OldClass said:
i'm sorry has make mistake when put extracted folder in my sd card
now i can repart my internal Find 7 X9076
thanks for your help
Click to expand...
Click to collapse
I've just updated the "how-to" procedure in order to avoid this problem in the future. I'am happy that it worked. Thanks for your testing.
It's work. Tested on my x9076 using ColorOS KitKat 33 (Chinese Full)
Hello,
i was on unified storage (coldbird method) and this method take me to brick my x9076
I have recovered it with the method QHSUSB_BULK on Oppo forums, and then, when i have a stock layout, i try again with this method.
It works like a charm! Thank youuuuuuu!! :laugh: :laugh: :good:
Hi.
If i go to recovery and execute adb shell, "device not found" error appears. Seems that i missed to install a driver. But i installed the oppo driver, adb driver from google... Nothing of that works.
Trinaaa said:
Hi.
If i go to recovery and execute adb shell, "device not found" error appears. Seems that i missed to install a driver. But i installed the oppo driver, adb driver from google... Nothing of that works.
Click to expand...
Click to collapse
Enable USB Debugging under Developer options in ColorOS and disable MTP under the mount menu in TWRP, then reconnect the phone to PC.
Done everything before, but i´ve got an old twrp version which doesn´t show me the "diasble mtp" option. With your hint i installed the newest twrp and it works! Thank you!
Thank you!!!
Worked like a charm.
Regards,
Samit.
X9006
hi
is this work for x9006 device too?
thanks
@italianquadcore,
Thanks for this great mod.
I had a few issues, which I am posting below.
(I am using Linux)
1. copied the scirpt external_sd folder to external sd on the phone.
2. rebooted to recovery. (Since I was going to use unified.sh, so flashed the unified twrp recovery before hand)
3. connected to phone to pc.
4. from pc: sudo adb shell
5. cd external_sd/external_sd
6. ./unified.sh
Result ... Unification failed.
During the execution, the script encountered 2 problems.
1. The script was not able to find /external_sd/new_scrtipts/parted/find7_unified.parted on line no 94.
So i copied find7_unified.parted to new_scripts folder and modified line no 94 of unified.sh as follows:
parted /dev/block/mmcblk0 < /external_sd/new_scripts/find7_unified.parted
2. The other problem for me was that the script find /dev/block/mmcblk0p15 mounted.
So ran umount /dev/block/mmcblk0p15 script manually.
Result ... Unification successful.
I am posting this so that it can be helpful to others.
May I ask what exactly the unify version does? Does it properly unify the system or is the entire storage made only for apps? For example, running Coldbird's version in a non-unified ColorOS will result in the user being able to use the entire storage for apps, but you can't download files or add them through USB
ganeshbiyer said:
@italianquadcore,
Thanks for this great mod.
I had a few issues, which I am posting below.
(I am using Linux)
1. copied the scirpt external_sd folder to external sd on the phone.
2. rebooted to recovery. (Since I was going to use unified.sh, so flashed the unified twrp recovery before hand)
3. connected to phone to pc.
4. from pc: sudo adb shell
5. cd external_sd/external_sd
6. ./unified.sh
Result ... Unification failed.
During the execution, the script encountered 2 problems.
1. The script was not able to find /external_sd/new_scrtipts/parted/find7_unified.parted on line no 94.
So i copied find7_unified.parted to new_scripts folder and modified line no 94 of unified.sh as follows:
parted /dev/block/mmcblk0 < /external_sd/new_scripts/find7_unified.parted
2. The other problem for me was that the script find /dev/block/mmcblk0p15 mounted.
So ran umount /dev/block/mmcblk0p15 script manually.
Result ... Unification successful.
I am posting this so that it can be helpful to others.
Click to expand...
Click to collapse
"5. cd external_sd/external_sd" is wrong. Is it a typo? Folder "new_scripts" (and all its related subfolders) must be put on "external_sd". So you should have "/external_sd/new_scripts/unified.sh" script to be working.
"So ran umount /dev/block/mmcblk0p15 script manually." mmcblk0p15 is mounted as "data" under TWRP recovery, so all the scripts simply unmount "data" mounting partition. Did you use another recovery?
Thanks for your testing.
idir_muse3k said:
hi
is this work for x9006 device too?
thanks
Click to expand...
Click to collapse
Please refer to paragraph "Tips & Hints" (here above), item 1.
farenteria said:
May I ask what exactly the unify version does? Does it properly unify the system or is the entire storage made only for apps? For example, running Coldbird's version in a non-unified ColorOS will result in the user being able to use the entire storage for apps, but you can't download files or add them through USB
Click to expand...
Click to collapse
For questions regarding "Unified Storage", please refer to thread on Oppo Forum ( http://www.oppoforums.com/threads/tutorial-unified-storage-layout-for-oppo-find-7a.17952/ ). Thanks.
to Italianquadcore
This is so freakin brilliant i screwed up my partitions (with 48mb internal space-lol) and followed your very well written gui, and bingo i got the partition sizes i want again....:highfive::highfive:
Worked like a charm on my x9076 qhd, which i was about to give up on!! Thankyou thankyou so much Pal
Gonna throw a small donation your way soon (not enough to buy a airplane., sorry) money is not what i have most off, just to show my appreciation!
:good:
Hello, I repartitioned the internal memory of my oppo 7 ( rom color os 2.0.0i) by your guide (13GB for data and the rest for storage) and it works perfectly and for that I m very happy because to have 3GB maximum for the app was something really limiting.
I wanted to ask you a question, if I try to change the my actually rom into one of those that you tested (for repartition memory) in the first post of the thread, i must repeat the procedure repartitioning? I must do wipe data / factory and flash the rom and I maintain the same memory repartitioned or i must redo the repartitioning procedure again? With rom tested in the first post i risk a brick of device? I say this because I want to change the color os because I would like to reduce the high consumption of battery and switch to a rom with consumption lower than, or at least let me flash the kernel sensei (the only kernel undervolted available for oppo7) with which to make a undervolt decent. To this end, I take this opportunity to ask you this too, that your opinion and what the best rom with low battery consumption (or what rom where i can flash the kernel sensei) that allows me to maintain this repartitioning already done in my color os 2.0