WARNING: LENOVO P780 8GB VERSION ONLY!!! DO IT WITH YOUR OWN RISK.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This modification is for you who need large space to install application in internal memory (mod 5.5 GB)
Materials Required:
1. STOCK ROM ROW S119 8GB (Other ROM can also be used of JB)
2. FILE TOMOD PARTITION P780 8GB
contained-in this mode:
EBR2_4000MB -> file data into 4GB
EBR2_5000MB -> file data into 5GB
EBR2_5500MB -> data file to be 5.5GB
HOW:
Extract Stock rom on PC, extract target_bin
Extract Partition mode P780 8GB, then copy it to a folder target_bin
Since we will be using a custom EBR2, please rename Checksum.ini to __Checksum.ini I found a folder target_bin
Turn off the phone
Run Flashtool (available in the rom pack)
click scatter-loading (a)
input file MT6589_Android_scatter_emmc from target_bin (b)
DA, DL All With Checksum (c)
make sure all components checked. (d)
6. Click on EBR2 in flashtool and select the sizes that you want - (4GB, 5GB, 5,5 GB)
7. Click Firmware> Upgrade and wait flashtool finish search then connect the USB phone to pc.
Wait until the indicator turn green.
After modification (5.5GB)
Note: This is screenshot of my own device
Once done you can install other ROM aswell, I even had installed KITKAT too (MIUI V6 5.4.10)
REPARTITION WITHOUT PC. (not tested)
This will makes 7.26GB with 4.40GB free storage
Download: P780ROW_8Gb_ReParted_Data_no_int_sd_no_backup.zip
1. Put on sdcard
2. Getting into CWM Recovery
3. Make a full backup
4. Install zip from sd > choose P780ROW_8Gb_ReParted_Data_no_int_sd_no_backup.zip
DO NOT reboot AFTER FINISH
5. Go to Backup & Restore
6. Advance Restore > Restore DATA alone!
7. reboot
To return to the original partition just flash back stock rom or install zip in CWM:
P780ROW_8Gb_ReParted_to_original.zip
GOOD LUCK ....
Thanks bro. I'm giving it a try now on a CN based ROM.
Corrupted my data partition. I tried the flash zip. I'm going to have to try to reflash the FT rom to fix my data partition. Thanks for trying.
Supermatt01 said:
Corrupted my data partition. I tried the flash zip. I'm going to have to try to reflash the FT rom to fix my data partition. Thanks for trying.
Click to expand...
Click to collapse
sorry for that I told you its tested on ROW only I will try to find CN process
NISHANTJ_2K said:
sorry for that I told you its tested on ROW only I will try to find CN process
Click to expand...
Click to collapse
It's all good bro. I fixed the partition using the flash tool. Thanks for your effort. Often the 8 gig device gets forgotten about.
Supermatt01 said:
It's all good bro. I fixed the partition using the flash tool. Thanks for your effort. Often the 8 gig device gets forgotten about.
Click to expand...
Click to collapse
i doubt if there is no 8gb version in china. there is not an single post regarding 8gb repartiton on other side 4gb have two ways to it even in CN base
NISHANTJ_2K said:
i doubt if there is no 8gb version in china. there is not an single post regarding 8gb repartiton on other side 4gb have two ways to it even in CN base
Click to expand...
Click to collapse
Right, no love for the 8 gigabyte version in CN. Thanks for the help though.
greaat.. helped bro thks
Related
Hi everyone, seasons greeting's and all that
So, I have successfully rooted my phone (after lots of reading etc) with the SpeedMod kernel which IMHO makes my phone fly, quite impressed indeed.
I'm unfortunately a novice and I am having trouble installing a ROM, although it works perfectly well when I have to flash back to stock with odin.
I completed the required wipes as suggested is always performed when installing new ROMs. I placed the zip (tried this with CheckROM and Hyperdroid on numerous occasions) on the internal memory (external 2gb memory still in situ) and via CWM proceeded to "install zip from sdcard" and then "choose zip from internal sdcard", the flash process took all of 1.5mins which I thought was far too quick.
When prompted, I reboot the phone with the option on CWM and basically get stuck at the image in the pic below, even after waiting 30-60mins
Any help greatly appreciated as I am really keen on trying some great ROMs from some great devs.
Many Thanks, Rizur.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Are you selecting 'flash zip' or 'install zip from SD card' then selecting the file?
1.5 minutes also sounds about right.
Sent from my GT-I9100
Sorry, I am indeed selecting "install zip from sdcard" and then "choose zip from internal sdcard".
Get back into recovery and flash the file again, or restore a previous backup. Otherwise get into download mode and flash a rom that was specifically made to be flashed through odin, there's a few of them.
Cheers! I'm currently on stock with SpeedMod kernel, I may try and flash again or find those odin based ROMs you speak of.
flash a rom with odin like lighning to see if its working
I am currently on UltraToxic ROM, mainly because I'm struggling to flash via CWM.
All is well so far though so I'm happy
A clue ??
Copy custom rom zip xxxx .zip or whatever its called to internal sd card .
Boot to recovery cwm .
select Install zip from sd card .
choose zip from sd card or depending upon CWM version choose zip from internal sd card .
Navigate to named zip file xxxx.zip select then answer yes in the next window .
Should now install and boot .
If fails it would be worth checking your version of cwm and maybe even install a new cwm and root kernal or start over and wipe the phone .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
followed by cwm and root
then your custom rom of choice .
jje
What I can say is these.
Turn off phone.
Enter cwm again.
Wipe everything.
Try reflash and it should work now.
Good luck!
Sent from my Galaxy Tab 8.9 using Tapatalk HD
Thanks guys!
JJEgan, I will try your advice mate, hopefully I will get this thing running CheckROM as I would like
I'm in no hurry but would be nice to be able to test out more ROM's!
Once again much appreciated guys!
Rizur.
Basically, there are 3 types of flash method for K900
SDFUSE
OTA Recovery
MFT (Manufacturing Flash Tool)
There is a lot of question, asking about why same version of VIBEROM_V1.0_1411_ST_K900 have so many method of flashing.
There are too many information from the general thread. so I create new thread here for beginner to understand more about flashing.
From my understanding, there are only one version ROM (eg. VIBEROM_V1.0_1411_ST_K900).
But there are a few format for different flashing method.
1) SDFUSE
This format usually flash by create sdfuse folder in internal SD. Normally for update ROM
Copy files system.img.gz, boot.bin, dnx_firmware.bin, etc. (or .inb file which is the one and only one file) into sdfuse folder.
Shutdown and boot up by pressing power + volume up for couple of seconds
select SDUpdate and press power to start.
After done select power off, then power on again. (direct reboot may cause boot loop)
2) OTA Recovery
The format of rom is in ZIP. The zip is signed and there will be checksum (SHA1 and MD5) during flash. so the zip is unable to modified before flashing.
this method normally for update ROM too.
Copy update.zip file into sd card (recommended is at root of SDCard) and shutdown.
Boot up by pressing power + volume up for couple of seconds, then select recovery.
wipe data / Factory reset and wipe cache partition ( optional, which will wipe all data in sdcard)
apply update from internal storage and select update.zip
system will reboot after done.
This does not works for me to upgrade to 4.3 where I am on Qubex Vibe ROM v4.
But there are a lot of K900 user able to flash original Vibe ROM v7 and follow the above method and upgrade successfully.
Refer this http://forum.xda-developers.com/showpost.php?p=51069544&postcount=3142 or
http://forum.xda-developers.com/showpost.php?p=51128922&postcount=3199
if you are using official Vibe Rom v7. There are a easier way to flash.
copy the downloaded OTA zip file into SD Card.
Go to System upgrade, swipe left get menu, and select tools.
Touch Install specified update package and browse for OTA Zip file in sd card.
Touch install Now.
3) MFT
This method require computer with driver and software installed and USB cable for sure.
Refer this http://forum.xda-developers.com/showpost.php?p=51162040&postcount=3245
I got this method successfully when I am on non-official Vibe rom.
Please correct me if I am wrong.
Thanks to Onesjy at lenovo forum.
http://bbs.lenovo.com/forum.php?mod=viewthread&tid=154595&extra=page=1
Edited:
From my experience, the MFT method is always succeed.
Url for latest 1418_DEV MFT : http://forum.xda-developers.com/showpost.php?p=52500023&postcount=3745
MFT
i know how to use it but where can i find Manufacturing Flash Tool 6.0.2??
As far reported to me by QuBeX the ADB mode is not working on that device... I guess for the issue we have with MFT, it is the only solution we can look for also because I haven't forum (and have to open it) a thread where to speak about the recovery of a stock ROM.
About the Method N.3, most of the compatibility issues are related to the OS you are working on.
For the Settings you have to apply what you see below...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
... about the libraries, instead, download that packages and replaces (if so) the files already present in the 32 / 64bit Windows' system folders: https://drive.google.com/file/d/0B282FXce0kggSHpHSDRROFNZaEU/edit?usp=sharing
You can find the Applications as well the Drivers you need directly starting from that shared folder: https://drive.google.com/file/d/0B282FXce0kggSHpHSDRROFNZaEU/edit?usp=sharing
imei changed to null
i tried to flash viberom using sdfuse method but after flashing imei changed to null how to retore it
help
Hello
I'm having problems finding the error causing the incorrect storage space being reported on my compact; 16GB instead of 32GB. Has anyone encountered this before?
It's definitely something I am doing with adding the recovery - as a virgin 32.3.A.0.376 flash reports 32 GB correctly.
I've tried rootkernel 5.23, and the androplus kernel, and also with and without root/SuperSU. Previous installation of TWRP 3.0.2 on 32.2.A.0.305 with SuperSU displayed correct storage spaces with my Device Key intact.
Is anyone able to give me a hint as to what I should be looking for? I might try again and this time check with SD Maid or Apps2SD what the filesystem is doing once it does it's Google first boot setup. I was using TWRP in recovery and the default Storage Menu in Nougat settings to check previously.
Thanks
Just reverted to Marshmallow and it's interesting that it now reports 16GB. I have no idea what is happening
NeoBeum said:
Just reverted to Marshmallow and it's interesting that it now reports 16GB. I have no idea what is happening
Click to expand...
Click to collapse
happened with mine on both marshmallow and nougat, tho it corrected itself after a few restarts
Ok, thanks. I don't know if I'm game enough to test to see what happens if I fill up my marshmallow internal storage beyond 16gb, backup, flash Nougat, and revert... I'm curious though
Is there anything out of place in this? I'm new to Linux, I only just installed Ubuntu on my laptop today, and am learning
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know why it's doing this now... a moderator can delete this thread - tis related to TWRP + Nougat + Rootkernel
Had the same problem. I could solve it:
I flashed the stock rom. Then I restart mobile phone. Then flash the kernel and TA...
When i dont start the phone between flashing rom and kernel, then it's always 16 gb...
f4t1 said:
Had the same problem. I could solve it:
I flashed the stock rom. Then I restart mobile phone. Then flash the kernel and TA...
When i dont start the phone between flashing rom and kernel, then it's always 16 gb...
Click to expand...
Click to collapse
ah ok... i might look at what the persist files are doing in TWRP, i think when you do a restart, after the stock rom is flashed, it creates the data partition for the internal.
in the current build for rootkernel and twrp - i think it needs a prexisting directory
NeoBeum said:
I know why it's doing this now... a moderator can delete this thread - tis related to TWRP + Nougat + Rootkernel
Click to expand...
Click to collapse
Not a Nougat specific problem, it can happen on MM too. Speaking from experience.
I'm going to put TWRP on to a Virtual Device as part of my mini project... I just made a Z5 Compact skin for Android Virtual Device Manager
In twrp one can select data and or system, to repair, don't wipe it!
There one can press also repair and or resize wich may help. Maybe reboot needed but it has helped me before, also with nougat
The permission and partition information is not always correct during both format and wipes, that's the problem
jutphaas said:
In twrp one can select data and or system, to repair, don't wipe it!
There one can press also repair and or resize wich may help. Maybe reboot needed but it has helped me before, also with nougat
Click to expand...
Click to collapse
Jutphaas is correct, if you are performing a DRM fix with Root procedure via fastboot and TWRP then the wrong drive size will be stored. Booting into TWRP, advanced wipe, repair filesystem, resize filesystem, backing out and then going to install or somewhere else where you can select storage and selecting the onboard drive should now show the full amount of storage instead of the halved amount. This worked for me on Oreo, thanks Jutphaas.
Hello everyone. I really need help with this problem and would be very grateful if you helped me.
I accidentally took out my MicroSd card from my phone, when I tried to put it back in it wouldn't read it so I went ahead and plugged it to the computer, when I try to access it it says "The disk in drive H is not formatted. Do you want to format it no?" I always press no.
Here's what it says in the Disk Management
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. The card is fake
2. Use mini partition tool to format or repartition
3. Search online for SanDisk repair tool Chinese version
4. Use Linux related OS to check partition size
5. Worse state use hirens boot CD , boot the system on hirens based on Windows XP format it from device management. It will restore your total volume when you are able to get the tricks right.
Skyhuppa said:
1. The card is fake
2. Use mini partition tool to format or repartition
3. Search online for SanDisk repair tool Chinese version
4. Use Linux related OS to check partition size
5. Worse state use hirens boot CD , boot the system on hirens based on Windows XP format it from device management. It will restore your total volume when you are able to get the tricks right.
Click to expand...
Click to collapse
Lol I've been using this card for over 3 years and it always had 31 gb of data without a problem so it being fake is out of the question. I need to retrieve the data out of it before formatting
Pugnaq said:
Lol I've been using this card for over 3 years and it always had 31 gb of data without a problem so it being fake is out of the question. I need to retrieve the data out of it before formatting
Click to expand...
Click to collapse
That is the behavior of sandisk, is of low quality you might not believe this. Your data is corrupted. After bringing back the volume it may corrupt again.
That is the best options I have provided. I had SanDisk recovery tool but my system had crash severally. The best way is to use hirens boot cd.
Sent from my Infinix X573 using Tapatalk
Skyhuppa said:
1. The card is fake
2. Use mini partition tool to format or repartition
3. Search online for SanDisk repair tool Chinese version
4. Use Linux related OS to check partition size
5. Worse state use hirens boot CD , boot the system on hirens based on Windows XP format it from device management. It will restore your total volume when you are able to get the tricks right.
Click to expand...
Click to collapse
Skyhuppa said:
That is the behavior of sandisk, is of low quality you might not believe this. Your data is corrupted. After bringing back the volume it may corrupt again.
That is the best options I have provided. I had SanDisk recovery tool but my system had crash severally. The best way is to use hirens boot cd.
Sent from my Infinix X573 using Tapatalk
Click to expand...
Click to collapse
But this happened when I tool out my microsd card out off my phone without safely ejecting it first. I can always get a new card I just want to recover my data hopefully. When I use a partition program it says no partition found
Pugnaq said:
But this happened when I tool out my microsd card out off my phone without safely ejecting it first. I can always get a new card I just want to recover my data hopefully. When I use a partition program it says no partition found
Click to expand...
Click to collapse
If you have,
1. digital camera insert it to check storage.
2. Old phone that can read 32gb microsd can repair it.
I use these native methods to recover my staff.
Sent from my Infinix X573 using Tapatalk
I found this twrp on afh by @Camerado
It's a collection of TWRPs. I haven't tested since I am yet to unlock my device. So if anyone wants to try it out here's the file.
not found | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
-------------
Reply whether it's working or not so I'll remove this post
fastboot boot C:\Users\Designer-PC\Desktop\recovery.img
Click to expand...
Click to collapse
I renamed it. Give me a blackscreen. Am i doing it wrong
edit: Made it to TWRP menu. I will write a tutorial asap
makiothekid said:
I renamed it. Give me a blackscreen. Am i doing it wrong
edit: Made it to TWRP menu. I will write a tutorial asap
Click to expand...
Click to collapse
Is it workable?
khanhdx said:
Is it workable?
Click to expand...
Click to collapse
Sorry not atm
makiothekid said:
Sorry not atm
Click to expand...
Click to collapse
I also tried to boot that TWRP, after a while of black screen, cell phone restarts itself
sundhar88 said:
I found this twrp on afh by @Camerado
It's a collection of TWRPs. I haven't tested since I am yet to unlock my device. So if anyone wants to try it out here's the file.
not found | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
-------------
Reply whether it's working or not so I'll remove this post
Click to expand...
Click to collapse
I have tried this twrp we need to flash it on both slots a and b after that we can boot to twrp. I jave tried flashing miui china beta but it is unable to flash. After flashing this twrp device will not boot normally it will stuck on lock screen and showing 0% battery and we meed to flash fastboot rom again freshly.
One more thing is there to test i have read it in somewhere that when we have 2 slots a & b then we need to switch them once to flash the rom successfully on slot a for example.
When we booted the twrp on slot a at first we need to switch to slot b reboot twrp and then again switch to slot a and reboot twrp. I don't know weather this thing will work to flash a rom are not. But need to give it a try.
I have tried the steps like i said in my previous comment, here is the update.
After flashing twrp on both slots a & b and rebooting to twrp it works normal till here, since i didn't wipe the rom i am able to see my internal storage both in device and my system so i have tried dirty flash of china beta rom but it didn't worked below is the screenshot.
Now i have wiped everything and formated internal storage also. Then connected the device to pc and copied the beta rom file to internal it copied successfully.
But the file is not visible in internal storage when i was checking in twrp either in pc again .
Here is another thing if we want to make visible of internal storage in pc we need to mount storage and again if we want to make visible of internal storage in device again we need to unmount storage.
I think we need a big update on this twrp are els we can't use it properly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cherri said:
I have tried the steps like i said in my previous comment, here is the update.
After flashing twrp on both slots a & b and rebooting to twrp it works normal till here, since i didn't wipe the rom i am able to see my internal storage both in device and my system so i have tried dirty flash of china beta rom but it didn't worked below is the screenshot.
Now i have wiped everything and formated internal storage also. Then connected the device to pc and copied the beta rom file to internal it copied successfully.
But the file is not visible in internal storage when i was checking in twrp either in pc again .
Here is another thing if we want to make visible of internal storage in pc we need to mount storage and again if we want to make visible of internal storage in device again we need to unmount storage.
I think we need a big update on this twrp are els we can't use it properly.
View attachment 5321069
Click to expand...
Click to collapse
Did you turn of the description?
makiothekid said:
Did you turn of the description?
Click to expand...
Click to collapse
I didn't turned on anything.