how can check memory of one plus one when phone stuck on logo i have recived many times one plus one hang on logo and customer dont no how much memory in this phone how can check plz help thnx
ahmerp said:
how can check memory of one plus one when phone stuck on logo i have recived many times one plus one hang on logo and customer dont no how much memory in this phone how can check plz help thnx
Click to expand...
Click to collapse
If the device has a white back cover, it's the 16gb version and if i'ts the sandstone black cover then it's the 64gb version, ofcourse this is only true when the owner hasn't replaced their back cover!
if user change back cover then bcz to much refurbish phone in market last night black back cover 16gb phone i recived for firmware update that is reason today i post this
ahmerp said:
if user change back cover then bcz to much refurbish phone in market last night black back cover 16gb phone i recived for firmware update that is reason today i post this
Click to expand...
Click to collapse
if it has a customer recovery built in boot into recovery and plug in the cable and see how much memory there is
fastboot format cache
waiting for device >
rasing 'cache'...
KAY [ 0.197s]
ormatting 'cache' partition...
reating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
reated filesystem with 11/32768 inodes and 4206/131072 blocks
ending 'cache' (10432 KB)...
riting 'cache'...
KAY [ 0.624s]
inished. total time: 0.823s this is the procedure to check memory
Related
All,
I am hacking my way through some ROM development - trying to learn how it all works.
I have been trying to get started modifying the system.img from the Stock ICS 4.0.4 ROM for the GT-P5100, following this guide
All good - and I have done my mods to the files (actually all i have done is added an APK) to reduce the variables if something goes wrong.
When I try to "repack" using:
Code:
./mkuserimg.sh -s /some/directory/with/files ./factoryfs_custom.img ext4 ./temp 512M
I get
Code:
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
error: do_inode_allocate_extents: Failed to allocate 2925 blocks
I am guessing this is because of the block size? So the question is what should this be for the Tab 2 10.1 P5100?
Have you tried using a larger value for the temp size?
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
Have you tried using a larger value for the temp size?
Posted from my Fascinate using XDA Premium
Click to expand...
Click to collapse
I honestly am not really sure what the value does - so no... any suggestions for a value? Or suck it and see?
What impact does it have on the final image?
patonar said:
I honestly am not really sure what the value does - so no... any suggestions for a value? Or suck it and see?
What impact does it have on the final image?
Click to expand...
Click to collapse
OK - so i bit the bullet, change the size to 1024M and repacked the FS, tar'd the file, and flashed using ODIN.
Worked a dream
I think I am going to write a guide on the basics, as there is so much info out there - but not many sources for beginners pulling it all together.
Go for it! More information is never a bad thing!
Posted from my Galaxy Tab with CM10
Need Help: OPO will reboot after boot animation, when on CM set language page( Initial Setup page)
How do I re install 38R again ?
I have access to CM recovery & Fastboot by pressing Power & Volume keys.
Device not rooted.
ashishk2 said:
Need Help: OPO will reboot after boot animation, when on CM set language page( Initial Setup page)
How do I re install 38R again ?
I have access to CM recovery & Fastboot by pressing Power & Volume keys.
Click to expand...
Click to collapse
I have the same exact issue. I restored all the same images and still the same thing. Trying something different now. You need to download the factory image from the bottom of this page : https://cyngn.com/products/oneplusone/
LaNsLyDe said:
I have the same exact issue. I restored all the same images and still the same thing. Trying something different now. You need to download the factory image from the bottom of this page : https://cyngn.com/products/oneplusone/
Click to expand...
Click to collapse
Hope it works bud ! So need the phone back and running.
Keep me posted
Will do, do you know where the thread went for the 38R flashable zip?
also when you download the fastboot zip extract it into where you have fastbooto n your pc and do these commands. will most likely wipe data and you can replace the recovery it flashed with a custom one:
Start the fastboot tool and run the following in the command line (that means, windows+r, type cmd, press enter), in sequence:
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
---------- Post added at 12:17 PM ---------- Previous post was at 12:01 PM ----------
ashishk2 said:
Hope it works bud ! So need the phone back and running.
Keep me posted
Click to expand...
Click to collapse
i found the fix!
Do this it worked for me :
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
After a helpful session with +Ricardo Cerqueira of +Cyanogen Inc., here's a fix. While your phone is booted to TWRP, run these commands on your computer:
adb shell
make_ext4fs /dev/block/mmcblk0p15
A similar fix appeared earlier on the XDA Developers forum, but this single command is easier, runs faster, and doesn't require any downloads.
Here's the output of the command:
make_ext4fs /dev/block/mmcblk0p15
Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
Once everything is over, the OnePlus One should be restored without any data loss. We still don't know what causes the partition to get corrupted in the first place, but at least we all now know what to do if it does.
LaNsLyDe said:
---------- Post added at 12:17 PM ---------- Previous post was at 12:01 PM ----------
[/COLOR]
i found the fix!
Do this it worked for me :
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
After a helpful session with +Ricardo Cerqueira of +Cyanogen Inc., here's a fix. While your phone is booted to TWRP, run these commands on your computer:
adb shell
make_ext4fs /dev/block/mmcblk0p15
A similar fix appeared earlier on the XDA Developers forum, but this single command is easier, runs faster, and doesn't require any downloads.
Here's the output of the command:
make_ext4fs /dev/block/mmcblk0p15
Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
Once everything is over, the OnePlus One should be restored without any data loss. We still don't know what causes the partition to get corrupted in the first place, but at least we all now know what to do if it does.
Click to expand...
Click to collapse
I'm not rooted or custom recovery ! What do I do ?
Thread closed ! "corrupt persist.img"
Thank you
@justinblaine23 for posting the link.
@markbencze for proving detailed instruction for the fix.
@other who posted solutions.
The issues for caused bcoz of corrupt persist.img. If anyone faces the same issue reboot after boot animation or 0Mb in recovery kindly following the instruction on this link
Caution: Dont press and hold the power button to rest the phone, this caused the error on my OPO.
Hello i erased my efs partition and i didnt have a back up, so after one week i found the ****in solution.
First you need a twrp recovery maybe it will work and with others but i used that.
Second you need to download coloros (version COS_2.0.1i_11.zip) : http://forum.xda-developers.com/oneplus-one/general/rom-4-4-2-coloros-2-0-36beta-t2955853
download oxygenos (version 1.0.3) : https://forums.oneplus.net/threads/update-oxygenos-1-0-3-with-the-latest-stagefright-patches.354409/
download pesist.img : http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Now we have everything.
1. Go to recovery mode.
2. Wipe factory reset.
3. Flash coloros (dont worry wont mess anything)
4. Wipe
5. Flash oxygenos (boot it and now you will have a wi-fi bluethooth and sim-card)
6. Go to recovery again.
7. Wipe
8 Go to fastboot mode
9. fastboot erase persist
10. fastboot flash persist persist.img
11. Go to recovery mode againd
12. Advanced -> terminal command -> select (right bottom corner)
13. type: su
14: type: make_ext4fs /dev/block/mmcblk0p15
You will see:
Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
And after that you are good to go.
Big thanks to all guys and their articles.
And again you will be able to flash others roms and to have wi-fi, audiofx and etc...
Took you long enough... lol
Glad you solved it my friend.
Tom 2.0
Hi
I am searchin for a System dump for HTC U11+.
Can someone help me please?
Thank you and regards
damigor said:
Hi
I am searchin for a System dump for HTC U11+.
Can someone help me please?
Thank you and regards
Click to expand...
Click to collapse
You can decrypt RUUs using HTC RUU/ROM Decryption Tool to obtain the system.img and other .img files.
goodman_east said:
You can decrypt RUUs using HTC RUU/ROM Decryption Tool to obtain the system.img and other .img files.
Click to expand...
Click to collapse
Thank you very much. I guess you helped me a lot but I have no Idea how to make this stepsl So I will read instructions and try to understand them
Can I ask you for further information if I need some help?
damigor said:
Thank you very much. I guess you helped me a lot but I have no Idea how to make this stepsl So I will read instructions and try to understand them
Can I ask you for further information if I need some help?
Click to expand...
Click to collapse
Of course.
Hi
as supposed it has not work. See Log. :-/ Do you have any idea?
d to open keydata file: C:/adb/OUT/tmp/use_keyfile.bin
ERROR: could not decrypt file 'zip_23.zip' (res=247)
Decrypting (25/25) 'zip_24.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
failed to open keydata file: C:/adb/OUT/tmp/use_keyfile.bin
ERROR: could not decrypt file 'zip_24.zip' (res=247)
DecryptZIPs took 6.433 seconds.
Restoring '2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_hTC_Asia_TW_1.01.709.3_Radio_8998-002772-1710131105_release_514337_combined_signed_2_4.zip' to normal folder
Removing unneeded work folders
Overall process completion time: 3 minutes 48.735 seconds.
Finished: Tool has finished but there was an error, please
check the console output and your OUT folder
'C:/adb/OUT'
goodman_east said:
Of course.
Click to expand...
Click to collapse
What do you think?
damigor said:
d to open keydata file: C:/adb/OUT/tmp/use_keyfile.bin
ERROR: could not decrypt file 'zip_23.zip' (res=247)
Decrypting (25/25) 'zip_24.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
failed to open keydata file: C:/adb/OUT/tmp/use_keyfile.bin
ERROR: could not decrypt file 'zip_24.zip' (res=247)
DecryptZIPs took 6.433 seconds.
Restoring '2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_hTC_Asia_TW_1.01.709.3_Radio_8998-002772-1710131105_release_514337_combined_signed_2_4.zip' to normal folder
Removing unneeded work folders
Overall process completion time: 3 minutes 48.735 seconds.
Finished: Tool has finished but there was an error, please
check the console output and your OUT folder
'C:/adb/OUT'
Click to expand...
Click to collapse
You need a keyfile or hosd.img to decrypt a RUU.
Here is the keyfile you need.
goodman_east said:
Of course.
Click to expand...
Click to collapse
goodman_east said:
You need a keyfile or hosd.img to decrypt a RUU.
Here is the keyfile you need.
Click to expand...
Click to collapse
thank you very much. Where I have to put this Keyfile?
goodman_east said:
You need a keyfile or hosd.img to decrypt a RUU.
Here is the keyfile you need.
Click to expand...
Click to collapse
Ok. I got it.
Thank you very much. I have right now just Boot.img and system.img. I have flash a Boot.img but when I tra to flash System.img I recieve this error:
C:\adb>fastboot -w flash system C:\adb\OUT_2Q4D_1.01.709.3\system\system.img
target reported max download size of 2392800000 bytes
Invalid sparse file format at header magi
Creating filesystem with parameters:
Size: 121274105856
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29607936
Block groups: 904
Reserved block group size: 1024
Created filesystem with 11/7405568 inodes and 512922/29607936 blocks
Creating filesystem with parameters:
Size: 234881024
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 57344
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/14336 inodes and 1961/57344 blocks
erasing 'system'...
OKAY [ 0.192s]
sending sparse 'system' (2325171 KB)...
FAILED ()
finished. total time: 1.370s
C:\adb>
damigor said:
Ok. I got it.
Thank you very much. I have right now just Boot.img and system.img. I have flash a Boot.img but when I tra to flash System.img I recieve this error:
C:\adb>fastboot -w flash system C:\adb\OUT_2Q4D_1.01.709.3\system\system.img
target reported max download size of 2392800000 bytes
Invalid sparse file format at header magi
Creating filesystem with parameters:
Size: 121274105856
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29607936
Block groups: 904
Reserved block group size: 1024
Created filesystem with 11/7405568 inodes and 512922/29607936 blocks
Creating filesystem with parameters:
Size: 234881024
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 57344
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/14336 inodes and 1961/57344 blocks
erasing 'system'...
OKAY [ 0.192s]
sending sparse 'system' (2325171 KB)...
FAILED ()
finished. total time: 1.370s
C:\adb>
Click to expand...
Click to collapse
command
Code:
fastboot flash -S 1G system C:\adb\OUT_2Q4D_1.01.709.3\system\system.img
fastboot flash boot C:\adb\OUT_2Q4D_1.01.709.3\system\boot.img
goodman_east said:
You need a keyfile or hosd.img to decrypt a RUU.
Here is the keyfile you need.
Click to expand...
Click to collapse
nenebear said:
command
Code:
fastboot flash -S 1G system C:\adb\OUT_2Q4D_1.01.709.3\system\system.img
fastboot flash boot C:\adb\OUT_2Q4D_1.01.709.3\system\boot.img
Click to expand...
Click to collapse
Thank you very much! This has worked but now I am in bootloop :-/
damigor said:
Thank you very much! This has worked but now I am in bootloop :-/
Click to expand...
Click to collapse
Are your device is htc_ocmdugl ?
nenebear said:
Are your device is htc_ocmdugl ?
Click to expand...
Click to collapse
Yes I am. Still having Bootloop :-/
damigor said:
Yes I am.
Click to expand...
Click to collapse
Plz upload the download mode photo of your U11 plus
goodman_east said:
Plz upload the download mode photo of your U11 plus
Click to expand...
Click to collapse
Here you go. Thanks guy for your support
damigor said:
Here you go. Thanks guy for your support
Click to expand...
Click to collapse
you can flash ruu 1.01.709.3, or 1.03.1405.1 after mid and cid changed
goodman_east said:
you can flash ruu 1.01.709.3, or 1.03.1405.1 after mid and cid changed
Click to expand...
Click to collapse
sorry, I need some more informaion. :-/
damigor said:
Here you go. Thanks guy for your support
Click to expand...
Click to collapse
cidnum: HTC__034 -- HTC Europe
OS-0.81.709.10 -- HTC TW
Change cidnum: 11111111 than flash RUU_1.01.709.3
flash HTC RUU use this tool -- adb tool
download mode
Code:
fastboot oem writecid 11111111
fastboot oem rebootRUU
flash flash zip RUU_name.zip
fastboot reboot
goodman_east said:
you can flash ruu 1.01.709.3, or 1.03.1405.1 after mid and cid changed
Click to expand...
Click to collapse
nenebear said:
cidnum: HTC__034 -- HTC Europe
OS-0.81.709.10 -- HTC TW
Change cidnum: 11111111 than flash RUU_1.01.709.3
flash HTC RUU use this tool -- adb tool
download mode
Code:
fastboot oem writecid 11111111
fastboot oem rebootRUU
flash flash zip RUU_name.zip
fastboot reboot
Click to expand...
Click to collapse
Thank you very much. This has worked but I am still in Bootloop
Hi,
years ago i installed the Teamsuperluminal's CM13 on my Xiaomi Mi 4c and it it worked for a long time without major issues. Lately the phone started to auto power down when the battery reached appr. 50% charge. I would hook it up to a charger and reboot it and charge it back up again. Then it was fine again, this has been going on for months now. But yesterday it auto powered down again and after reboot it showed the CM boot logo for an unusual amount of time, after that it started preparing apps for start. When it was done with that it would just immediately reboot and start over again. So it is now stuck on a preparing apps reboot loop.
What i have tried so far:
1. Wipe cache and dalvik in TWRP and reboot. Didn't help
2. Tried to reformat a partition that might be corrupted due to brown out with:
Code:
make_ext4fs /dev/block/mmcblk0p15
It shows the following error:
Code:
Creating filesystem with parameters:
Size: 131072
Block size: 4096
Blocks per group: 32768
Inodes per group: 16
Inode size: 256
Journal blocks:1024
Label:
Blocks: 32
Block groups: 1
Reserved block group size: 7
error: ext4_allocate_best_fit_partial: failed to allocate 1005 blocks, out of space?
But there are more than 2GB of free space available and mmblk0p15 is then missing from /dev/block/ , so if i run the same command again i get:
Code:
Need size of filesystem
How can i repair this or what log file might be interesting?