This is an unoffical alpha build of CyanogenMod 12.1 for Tab-plus. Let's have the first taste of the colorful Lollipop.
Please read "Note on reporting issues" first
For change log, source & donation, please refer to my GalaxyTab 7.7 thread. You may vote for the next ROM to port there.
Screenshots: http://forum.xda-developers.com/showpost.php?p=56829635&postcount=2
Downloads: :highfive:
hosts: AndroidFileHost, Dev-Host
mirror: 百度网盘 ***Request from China.
Latest Delta Gapps: http://forum.xda-developers.com/showthread.php?t=2997368
Note on reporting issues:
1. You need a Factory reset/wipe data after flashing.
2. ART requires longer to boot. Wait for at least 10 mins. in boot animation before hard reset.
3. Check the know issues in my GalaxyTab-7.7 thread first.
4. Post as detail as possible here. Which rom, which model, what happen, etc...
5. With a screenshot and/or video is better.
6. Don't send to my Paypal e-mail. I seldom check it.
Tips:
1. Use ONLY my TWRP2.8.6.x or above to flash.
2. See the 7.7 thread for details
This rom is for users with experience. If you don't know how to flash, please try other ROMs first.
screenshot provided by @BuTaJIu4eK
{
"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"
}
You're Awesome
---------- Post added at 11:14 AM ---------- Previous post was at 10:30 AM ----------
Fail
installation aborted!
Can't mount system
you are the best!!!!!!!!!!!!
I haven't touched my Tab in such a long time and WOW! It's going to be amazing! Thanks @daniel_hk
it could not work on my plus,When I was ready to flash，the twrp 2.8.0.0 say "unable to mount system". I try to write with cwm, but still can not.
As of time of writing, a fix is in the works for this problem. Please wait until then.
Hasn't worked Could you flash it in Heimdall, @daniel_hk?
gwhite5 said:
Hasn't worked Could you flash it in Heimdall, @daniel_hk?
Click to expand...
Click to collapse
5.0 use different way to flash. Without modifications, old methods are not working.
I think updater-binary not execute. The same updater-binary works on 7.7. Might be another security reason.
Can you (or anyone) copy the TWRP log to sdcard and send it to me?
1. Reboot to TWRP.
2. Flash the Rom.
3. Copy the log:
Advanced button > Copy log to SD button.
The file recovery.log will be in /sdcard
daniel_hk said:
5.0 use different way to flash. Without modifications, old methods are not working.
I think updater-binary not execute. The same updater-binary works on 7.7. Might be another security reason.
Can you (or anyone) copy the TWRP log to sdcard and send it to me?
1. Reboot to TWRP.
2. Flash the Rom.
3. Copy the log:
Advanced button > Copy log to SD button.
The file recovery.log will be in /sdcard
Click to expand...
Click to collapse
Oh I understand now why it uses block_image_update().
I will do it after I get home, but there is no other error messages on the screen.
@daniel_hk you are very great indeed. Keeping galaxy tab plus alive still is very nice of you. I will certainly try this one as soon as a working build is release. Thank you very much sir....
@daniel_hk, here is the log file.
Code:
-----------------------------[cut here]---------------------->8
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/otasigcheck.sh] with 1 args
erasing 212992 blocks
blkdiscard failed: Invalid argument
writing 92710 blocks of new data
write failed: No space left on device
lseek64 failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12-20141129-UNOFFICIAL-p6200.zip'
Error flashing zip '/sdcard/cm-12-20141129-UNOFFICIAL-p6200.zip'
Updating partition details...
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p9', current file system: 'ext4'
I:Data backup size is 58MB, free: 12027MB.
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'auto'
It must be due to system.transfer.list OR block_image_update();
Oh yeah, and another thing, the system partition is not correctly formatted AFTER installing CM12 so some ROMs which do not format /system during installation crash with 'Unable to mount /system' too. I presume it's because blkdiscard did not do its job.
I found where in the recovery code it is failing!
I found where in the recovery code it is failing!
https://github.com/CarbonROM/androi...5276bda1f1a9f70bbde42/updater/blockimg.c#L561
---------- Post added at 08:23 PM ---------- Previous post was at 08:22 PM ----------
@daniel_hk it must be the image itself or the system.transfer.list.
Plus system.new.patch is 0kb, is that normal?
gwhite5 said:
@daniel_hk, here is the log file.
Code:
-----------------------------[cut here]---------------------->8
I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
I:Legacy property environment initialized.
about to run program [/tmp/backuptool.sh] with 2 args
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/otasigcheck.sh] with 1 args
erasing 212992 blocks
blkdiscard failed: Invalid argument
writing 92710 blocks of new data
write failed: No space left on device
lseek64 failed: Invalid argument
I:Legacy property environment disabled.
E:Error executing updater binary in zip '/sdcard/cm-12-20141129-UNOFFICIAL-p6200.zip'
Error flashing zip '/sdcard/cm-12-20141129-UNOFFICIAL-p6200.zip'
Updating partition details...
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p9', current file system: 'ext4'
I:Data backup size is 58MB, free: 12027MB.
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'auto'
It must be due to system.transfer.list OR block_image_update();
Oh yeah, and another thing, the system partition is not correctly formatted AFTER installing CM12 so some ROMs which do not format /system during installation crash with 'Unable to mount /system' too. I presume it's because blkdiscard did not do its job.
Click to expand...
Click to collapse
I get the same on TWRP 2.8.0
---------- Post added at 08:44 AM ---------- Previous post was at 08:35 AM ----------
People that flashed this successfully what recovery and version are you using?
Great daniel please fix file for p6200. Many thanks.
Sent from my GT-I9300 using XDA Free mobile app
looking forward to testing this when a working build is out.
Sreen Rotation
So now that we are into lollipop I figure some light on the screen rotation glitch from KitKat has been shed.
Was the issue inherent to KitKat and therefore the reason the glitch is gone with lollipop??
OR was the culprit causing the glitch fixed outside of the lollipop - ?
If so could the fix be back ported to the kit kat roms to fix the glitch in them??
Just Curious but a non rotating glitch in the latest Omni Kit Kat would be awesome.
tjsooley said:
I get the same on TWRP 2.8.0
---------- Post added at 08:44 AM ---------- Previous post was at 08:35 AM ----------
People that flashed this successfully what recovery and version are you using?
Click to expand...
Click to collapse
They're probably running the test build that daniel_hk sent out to us testers.
Perfect now running on p6200. I test it many thanks Daniel.
Sent from my GT-I9300 using XDA Free mobile app
Trying to flash with twerp 2.8.2.0 I get the following error error executing updater binary in zip I have verified the MD D5 of the zip and the zip is valid
Sent from my HTC One using Tapatalk
magicozero said:
Perfect now running on p6200. I test it many thanks Daniel.
Sent from my GT-I9300 using XDA Free mobile app
Click to expand...
Click to collapse
how to install the rom? edit some config or new recovery? please save our 6200...
Related
CWM is finally here on I9003 for XXKPE
HOW TO:
- Install the latest CWM with EXT4 support;
- do a full backup with nandroid;
- install the attached script (DO NOT REBOOT AFTER THIS STEP);
- restore backup.
IMPORTANT: Read this topic on Edify scripting used on update.zip. The partitions must be mounted before copying files:
Code:
run_program("/sbin/busybox", "mount", "-t", "auto", "/dev/block/stl9", "/system");
Flashing Zip Files:
If in the updater-script there isn't the "mount /system" option you must - before apply the zip - mount manually /system under "Mount and Storage" menu and then flash your zip.
Feature:
- Added EXT4 filesystem support for the kernel;
- CWM with double RFS / EXT4 filesystem support;
- Busybox;
- Juwe11's RamScript from http://forum.xda-developers.com/showthread.php?t=1111145 ;
THANKS:
A big Thanks to the Skin1980 (this CWM is heavily based on it's project).
Thanks also to koush that made the Clockworkmode Recovery.
Attached you will find the CWM for each FW... just flash with ODIN selecting in the PDA source the CWM file.
UPDATE: 08/02/2011 Added the support for Juwe11's RamScript
Just press "Thanks" if you like my work...!!!
So this is it! Thanks X 2 mate! I'm installing the converter immediately
@OP: Thanks, does this support init.d script, so I can use a script like juwe's ram script?
Root issue!
The same as Skin's first version of ext4 converter :
The installation was completed, but when I come back to CWM main menu, recovery writes :
E:Can't mount /cache/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And when I reboot, it's stucking to the boot screen ("Galaxy S Super Clean LCD")
@pralinos: at work now, can't try it, but did you mean it got stuck at boot screen after you tried to root or even before it? I haven't root my phone and only want to do an ext4 conversion.
Pralinos said:
The same as Skin's first version of ext4 converter :
The installation was completed, but when I come back to CWM main menu, recovery writes :
E:Can't mount /cache/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And when I reboot, it's stucking to the boot screen ("Galaxy S Super Clean LCD")
Click to expand...
Click to collapse
After the third step (in the instructions), do not reboot the phone.
Updated the instructions for the same.
Let me know how it goes.
bigeyes0x0 said:
@pralinos: at work now, can't try it, but did you mean it got stuck at boot screen after you tried to root or even before it? I haven't root my phone and only want to do an ext4 conversion.
Click to expand...
Click to collapse
My phone was rooted before I applyed the ext4-format.zip. You need root access to use CWM.
amit.bagaria said:
After the third step (in the instructions), do not reboot the phone.
Updated the instructions for the same.
Let me know how it goes.
Click to expand...
Click to collapse
It doesn't work :
Checking MD sums...
Restoring system...
Error mounting /system
Skipping format...
Can't open /system
I think I lost root access just after I applyed the zip, because the error messages appeared as soon as I came back to CWM main menu.
@amit, I have just flashed XXKPE with CWM as per these posts, http://forum.xda-developers.com/show...6#post16169086 and http://forum.xda-developers.com/show...&postcount=537.
Now if I want to convert to Ext4 (Internal memory or internal SD card or both??), I believe I have to flash the files in this thread? Will I lost all my apps and data?
Amit, the same happened to Skin when he first released ext-format.zip for Froyo.
See http://forum.xda-developers.com/showthread.php?t=1151704&page=53
You musn't be far from succeeding.
Pralinos said:
Amit, the same happened to Skin when he first released ext-format.zip for Froyo.
See http://forum.xda-developers.com/showthread.php?t=1151704&page=53
You musn't be far from succeeding.
Click to expand...
Click to collapse
There is nothing wrong in the version I posted. Basically if you have rebooted the phone after running ext4 conversion update script, then it won't work. You would need to reflash the vanilla XXKBE and then perform the steps listed in the instruction (Obviously skipping the 2nd step, since I assume, you would have already done nandroid backup )
@amit: how high did the i/o quadrant scored? Gonna try this later
Sent from my GT-I9003 using XDA Premium App
ok i copied the ext4-format.zip in my sdcard n booted to cwm recovery
now i select install zip from sdcard>choose zip from sdcard.but i cant see the ext4-format.zip.
am i doing something wrong.would appreciate a more detailed explanation on what to do.
jit_devil2 said:
ok i copied the ext4-format.zip in my sdcard n booted to cwm recovery
now i select install zip from sdcard>choose zip from sdcard.but i cant see the ext4-format.zip.
am i doing something wrong.would appreciate a more detailed explanation on what to do.
Click to expand...
Click to collapse
For CWM sdcard = External SD Card
Copy again to external SD card and give it a shot
whats this ext4-format?
Quadrant Scores
{
"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"
}
amit.bagaria said:
Click to expand...
Click to collapse
Great.! Do u have advanced quadrant? It's more detailed
Sent from my GT-I9003 using XDA Premium App
@amit... how to check above ss & whats d ext4 support?
soodgautam said:
For CWM sdcard = External SD Card
Copy again to external SD card and give it a shot
Click to expand...
Click to collapse
thnks trying it now
it works perfectly 2156 in quadrant.
awesome work.now waiting for ram script
*** WARNING: This is a risky procedure that could damage your phone - PROCEED AT YOUR OWN RISK ***
ONLY FOR P690 - NOT P698 OR OTHER DIFFERENT MODELS
for p698 look at this thread : http://forum.xda-developers.com/showpost.php?p=25103749&postcount=1
*** ONLY INSTALL THE LATEST VERSION AVAILABLE ***
Hello everyone,
I've succesfully ported the CyanogenMod Clockworkmod recovery for our *beloved* Net Optimus Some details:
-> REQUIREMENTS:
-- ROOT
-- ADB
-- KNOW HOW TO CHECK THE MD5SUM OF A FILE -> HowToMD5SUM - Guide for Windows and Linux
The Recovery can be installed as follow:
Download recovery.img from the link attachment
IMPORTANT: Check MD5SUM - This is to ensure that during the download / copy the file is not corrupted
Copy recovery.img to the SD
download Flash_image, unzip and copy it to SD
Now you must install the recovery through ADB (the commands must be entered one by one in the shell, waiting a couple of seconds between one and another.
Code:
$ adb shell
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image> /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
# flash_image recovery /sdcard/recovery.img
# reboot recovery
Note: the command
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
could give you an error "File not found", ignore it.
If all goes well, the menu with a cheerful hat ClockworkMod background confirms that the boot recovery occurred in CW.
Also ignore the error below: "E: bad boot message" is not a real error.
The recovery functionality is simple:
- The volume keys to scroll
- The back button to go back
- The power button to select a menu item.
If you have problems, you can select Advanced / Error Reporting. This will generate a log into SD (recovery.log). You can use it to understand the problem.
---------------------------------------- Changelog - --------------------------------------------------------
v1 beta.1 (MD5SUM 5707de3d7463072e3bf9d3c1d6108ef1)
updated to 5.0.2.8
Original Thread : [TEST] Custom Recovery per LG Optimus Net - Clockwork 5.0.2.7 - Androidworld.it
Thanks to:
save80
Disclaimer:
Neither I nor XDA consider ourselves responsible for any damage caused to the telephone,
install this recovery at your own risk.
RELEASES :
5.0.2.8 -> https://rapidshare.com/files/2585790621/recovery.img (258e95cd2a697d902c2c139893d83063)
Please give me feedback about recovery functionalities.
Help me
I'm newbie. I'm using LG Optimus Z, everyone show me install clockworkmod for Optimus Z, please....
Thanks very much.....
---------- Post added at 03:57 PM ---------- Previous post was at 03:40 PM ----------
jst_tsj said:
Post Reserved for future updates.
Please give me feedback about recovery functionalities.
Click to expand...
Click to collapse
Please help me install clockworkmod for LG Optimus Z . Thanks very much...
Every body, help me ,please....
Hmm... no feedback... is it good or bad? Does this works for anybody?
Am gonna try it now hope i dont get bricked!
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
What do you mean by :-
you must install the recovery through ADB (the commands must be entered one by one in the shell, waiting a couple of seconds between one and another.
Click to expand...
Click to collapse
IT WORKED!!!
IT Worked man!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
---------- Post added at 07:41 PM ---------- Previous post was at 06:52 PM ----------
{
"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"
}
Really would like some Nice ROM's and OC kernels plz!!!
can you show some screen shot please
sorry i stuck at $adb remount nothing happen. but it show permission denied
help me please
Seems like you are using windows 7. Ryt click on cmd and run as administrator.
Sent from my LG-P690 using xda premium
Urmas1 said:
Hmm... no feedback... is it good or bad? Does this works for anybody?
Click to expand...
Click to collapse
all worked fine guy
i successfully installed the cwm recovery on my optimus net.....thanks
but i didnt used remount command , when i use this command it says permission denied.. is there any problem?? but cwm is installed
i m unable to flash new ROM by this recovery..... i have tried 4-5 times but it stuck in LG logo then i have to go back to recovery mode and recover to my old firmware...
anybody installed CM7 or other ROMs reply by..
is there any more feedbacks? i would like to use it
work for optimus net dual?
New version available... Sorry I've disappeared, but I'm here again now
could you provide me official kdz of 2.3 please....
Please can we have the new one! thanks
UPDATE
New version available
** Fixed a problem with sd-ext mounting, please update in order to avoid problems with sd-ext partition
recovery link : https://rapidshare.com/files/2585790621/recovery.img
md5sum : 258e95cd2a697d902c2c139893d83063
http://forum.xda-developers.com/showpost.php?p=19626804&postcount=2
jst ive been following your thread for lg optimus net in italian forum and waiting for your best update that less bugs...looking forward to that day
Welcome guys, with this short guide you'll be able to wipe any number of SD-EXT partitions with the help of a powerful feature inside TWRP recovery. Furthermore you'll get always fresh ext4 partitions without journal in just one shot.
TOOLS
1. MiniTool Partition Wizard (Google it if you don't have it already installed).
2. TWRP recovery 2.3.6.0 for Pico (click here).
INSTRUCTIONS
1. Get your ext4 partions done with MiniTool Partition Wizard. You can see here a very good guide.
2. Insert your SD card into Pico and boot into TWRP recovery.
3. Once inside TWRP, click MOUNT button. Check that SD-Ext is not selected (unmounted), otherwise you could damage your partition.
{
"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"
}
4. Go back to start screen and tap ADVANCED button then TERMINAL COMMAND button. Check that it is in Root folder (/). Tap SELECT button.
5. Write the folowing inside the command window and press enter.
Code:
mke2fs -t ext4 -O ^has_journal /dev/block/mmcblk0p2
6. Repeat the process if you have more sd-ext partitions, you just have to edit the last number in the command line and press enter (for 2 sd-ext partitions mmcblk0p2 is first partition and mmcblk0p3 is second partition).
7. Now you have fresh formated ext4 partitions and without journal for maximum speed. Now flash your favorite ROM that supports multiple sd-ext partitions and ENJOY!
8. Repeat this process (from number 3) whenever you'll flash a new ROM. I hope one day TWRP incorporates multiple SD-ext partitions handling.
SPECIAL THANKS
@#define for porting awesome TWRP recovery to Pico.
@Dees_Troy and TeamWin project members for making the best Recovery out there.
@cute_prince for his great idea of multiple sd-ext partitions and OC for Pico.
you could also try using the Aroma File Manager for shell access
http://forum.xda-developers.com/showpost.php?p=42928510&postcount=1 I have to follow the whole procedure or only PART 1 : Preparing The SDcard . I already have Single SD-EXT partition.
droidbot678 said:
http://forum.xda-developers.com/showpost.php?p=42928510&postcount=1 I have to follow the whole procedure or only PART 1 : Preparing The SDcard . I already have Single SD-EXT partition.
Click to expand...
Click to collapse
Just the part related to creating the partitions! One sd-ext can be created with any recovery. For more than one we need MiniTool.
thewisenerd said:
you could also try using the Aroma File Manager for shell access
Click to expand...
Click to collapse
But the good thing is TWRP has it all!
cornholio_rules said:
Just the part related to creating the partitions! One sd-ext can be created with any recovery. For more than one we need MiniTool.
Click to expand...
Click to collapse
Thanks, btw in that guide (http://s11.postimg.org/yjknyd51v/image.png) SD-DATA and SD-CACHE were done. And Amal said that partition should be SD-SYSTEM , SD- DATA. I'm confused here.. PFA of my sdcard partition!
droidbot678 said:
Thanks, btw in that guide (http://s11.postimg.org/yjknyd51v/image.png) SD-DATA and SD-CACHE were done. And Amal said that partition should be SD-SYSTEM , SD- DATA. I'm confused here.. PFA of my sdcard partition!
Click to expand...
Click to collapse
Don't worry, names doesn't matter, just the order. First ext4 partition from top to bottom (in MiniTool) will be mmcblk0p2 and so on.
But twrp doesn't mount sd-ext 4 from mini tool
ahmadmemon said:
But twrp doesn't mount sd-ext 4 from mini tool
Click to expand...
Click to collapse
That was like 10 years ago dude!
cornholio_rules said:
But the good thing is TWRP has it all!
Click to expand...
Click to collapse
IMO, I find it easier to type in Aroma's Terminal, even though I have TWRP
Is there any way to type the command conviently？
---------- Post added at 07:06 AM ---------- Previous post was at 06:56 AM ----------
icame to a key called kill.is it alright
?
wsdyleon said:
Is there any way to type the command conviently？
---------- Post added at 07:06 AM ---------- Previous post was at 06:56 AM ----------
icame to a key called kill.is it alright
?
Click to expand...
Click to collapse
The keyboard in TWRP is very good but tiny as everything in Pico, just tipe in carefully.
Don't touch that 'kill' button, leave the magic work. Kill is always bad!
no os found
after creating 3 ext as ext 2 ,3 n 4 ........i success fully installed rom but i found error as no os found ??? help
I have 3 ext4 partitions, created via MiniParition Tools
SD-SYSTEM ---> EXT4 ---> 500 mB is enough
SD-DTA ----> EXT4 ----> 1 GB
SD-CACHE ---> EXT4 ---> 150 MB
SD-EXT unmounted, and command "mke2fs -t ext4 -O ^has_journal /dev/block/mmcblk0p2" (last digit 3 and 4) doesn't work. But sometimes it works...
Can't understand why...?
and
Deleted
Flacito13 said:
I think I bricked my Poco F2 Pro (Redmi K30 Pro). I installed LuckyPatcher to disable disable signature verification. When I LuckyPatcher rebooted, I got stuck in a bootloop (the phone booted to Fastboot instead of System). I now want to format data in my TWRP to flash a new ROM and start from scratch. However, when I format data I get the following error in my TWRP: Failed to mount 'system_root' (Read-only file system).
I tried unsuccessfully tried fixing it by starting Terminal in TWRP and typing "mount -o rw,remount /system". I get "mount: can't find /system in /etc/fstab. with "mount -s system", I get a bunch of text but nothing that makes sense to me.
I hope somebody can help me out here...I just bought it :crying:
Click to expand...
Click to collapse
I have the same issue. Just install fresh rom with xiaomi tool and everything should be fine.
Koziol87 said:
I have the same issue. Just install fresh rom with xiaomi tool and everything should be fine.
Click to expand...
Click to collapse
I successfully flashed, but I still get "failed to mount /system_root (read-only file system)"...
{
"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"
}
When I reboot after flash, it simply boots to FastBoot again...someone please help me (
Flacito13 said:
When I reboot after flash, it simply boots to FastBoot again...someone please help me (
Click to expand...
Click to collapse
have you tried with XiaomiTools?
Flacito13 said:
When I reboot after flash, it simply boots to FastBoot again...someone please help me (
Click to expand...
Click to collapse
Did You flash 4 part file?
Koziol87 said:
Did You flash 4 part file?
Click to expand...
Click to collapse
What is 4 part file?
kevinmonja said:
have you tried with XiaomiTools?
Click to expand...
Click to collapse
I tried, but I get this error:
Flacito13 said:
I tried, but I get this error:
Click to expand...
Click to collapse
what rom are you trying to flash?
What TWRP version did you install? I recommend 3.4.2B from LR.Team.
batuken said:
What TWRP version did you install? I recommend 3.4.2B from LR.Team.
Click to expand...
Click to collapse
I have it...the problem is still that the system_root is "read-only"...:crying::crying::crying:
EDIT: after flashing with the xiaomitool, I now get error when formating data: failed to mount /odm invalid argument
kevinmonja said:
what rom are you trying to flash?
Click to expand...
Click to collapse
The one automatically downloaded by the flash tool. It is: lmi_eea_global_images_V12.0.2.0.QJKEUXM_20200730.0000.00_10.0_eea_7a4654b9f8
I tried formatting data again, but now I get another error: "failed to mount /odm invalid argument"
Flacito13 said:
The one automatically downloaded by the flash tool. It is: lmi_eea_global_images_V12.0.2.0.QJKEUXM_20200730.0000.00_10.0_eea_7a4654b9f8
I tried formatting data again, but now I get another error: "failed to mount /odm invalid argument"
Click to expand...
Click to collapse
Try to flash Xiaomi.eu ROM in TWRP.
batuken said:
Try to flash Xiaomi.eu ROM in TWRP.
Click to expand...
Click to collapse
failed to mount '/odm' (invalid argument)
Flacito13 said:
failed to mount '/odm' (invalid argument)
Click to expand...
Click to collapse
I had this problem a few days ago. To solve it, I had to reflash the rom (without formatting any partition) from twrp, ignoring the errors. (I'm on xiaomi.eu stable rom)
The important thing is to never modify the system partition (via lucky patcher or other tool) after installing Magisk, otherwise the phone won't reboot.
Lowxorx said:
I had this problem a few days ago. To solve it, I had to reflash the rom (without formatting any partition) from twrp, ignoring the errors. (I'm on xiaomi.eu stable rom)
The important thing is to never modify the system partition (via lucky patcher or other tool) after installing Magisk, otherwise the phone won't reboot.
Click to expand...
Click to collapse
Look the picture, I reflashed the rom with twrp. I still get the error cannot mount.
I see that some people have solved it by external rom installation, using adb sideload? How do I do that?
Deleted
Flacito13 said:
Look the picture, I reflashed the rom with twrp. I still get the error cannot mount.
I see that some people have solved it by external rom installation, using adb sideload? How do I do that?
Click to expand...
Click to collapse
I tried flashing via adb sideload in twrp, my devices wasnt recognized. Had to use my OTG USB Flashdrive.
ok i try side loading
I had same problem and go to twrp,format data type YES then reboot to twrp and clean cache,data,dalvik,interal,not wipe system...and reboot to twrp,put stable rom from xiaoimi.eu and flash it
So I was able to get my APN settings applied once using the methods on here, but since then, the APN stopped working and I am unable to repeat the process to get my Verizon SIM to have data.
Looking at another thread, the APNs are stored in /system/product/etc/apns-conf.xml
That file contains mostly Asian market APNs, but I did see a few for T-mobile, which explains why that service usually works.
I'm trying to use lsec6315update to replace the apns-conf.xml file but it's failing. Is this a root issue or something I'm missing?
Code:
#!/system/bin/sh
#
mv /system/product/etc/apns-conf.xml /system/product/etc/apns-conf.xml.bak
cp -rf /storage/sdcard1/apns-conf.xml /system/product/etc/apns-conf.xml
chmod 0644 /system/product/etc/apns-conf.xml
Thanks!
can't use lsec6315update to with in /system partition
You should use FYT Firmware Workbench (linux) and put the file manually inside, then recompile and flash only the kernel (with lsec6315update)
Cheers !
mariodantas said:
can't use lsec6315update to with in /system partition
You should use FYT Firmware Workbench (linux) and put the file manually inside, then recompile and flash only the kernel (with lsec6315update)
Cheers !
Click to expand...
Click to collapse
OK, so to use the workbench, I need ADB to the system or does the tool mount my FYT unit?
(I'm new to mods, but do have a Linux system to execute with, so that's a thing)
This tool wil decompile your firmware (file named 6315_1.zip) and recompile it (when decompiled and mounted, you can replace your files inside /system /vendor /product etc) !
mariodantas said:
This tool wil decompile your firmware (file named 6315_1.zip) and recompile it (when decompiled and mounted, you can replace your files inside /system /vendor /product etc) !
Click to expand...
Click to collapse
OK, so I need to extract the firmware using a different tool, then can run the scripts?
Got it, now I just need to choose which 6315_1.zip to use. 4PDA has some nice modded ones that add USB tethering, which is compelling.
FYT Factory (mine) and gfo to -> Kernels !
mariodantas said:
FYT Factory (mine) and gfo to -> Kernels !
Click to expand...
Click to collapse
yep, got that one from another thread.
now for troubleshooting.
I tried to mount it but got the following:
Code:
BROTLI -- Handling socko.new.dat.br...
Converting socko.new.dat file into socko.img file
Creating _mountpoint/socko folder...
Adding '128 Mb' extra size to _tmp/_firmware/socko.img ...
128+0 records in
128+0 records out
134217728 bytes (134 MB, 128 MiB) copied, 0.0375032 s, 3.6 GB/s
e2fsck 1.46.5 (30-Dec-2021)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open _tmp/_firmware/socko.img
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
resize2fs 1.46.5 (30-Dec-2021)
resize2fs: Bad magic number in super-block while trying to open _tmp/_firmware/socko.img
Couldn't find valid filesystem superblock.
Easy solution: go to config.ini and remove socko from partitions to handle, later I'll try to handle this
{
"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"
}
mariodantas said:
Easy solution: go to config.ini and remove socko from partitions to handle, later I'll try to handle this
View attachment 5752349
Click to expand...
Click to collapse
Actually, it's giving the same error for all the images, not just socko.
Mount points and sub folders are created, but nothing is mounted and folders are empty.
Code:
Cleaning workbench...
Unmounting and deleting folder '_mountpoint'...
Unmounting product.img ...
umount: /home/john/Downloads/Radio/FYT-Firmware-Workbench/_tmp/_firmware/product.img: not mounted.
Unmounting system.img ...
umount: /home/john/Downloads/Radio/FYT-Firmware-Workbench/_tmp/_firmware/system.img: not mounted.
Unmounting vendor.img ...
umount: /home/john/Downloads/Radio/FYT-Firmware-Workbench/_tmp/_firmware/vendor.img: not mounted.
Unmounting elable.img ...
umount: /home/john/Downloads/Radio/FYT-Firmware-Workbench/_tmp/_firmware/elable.img: not mounted.
Deleting _mountpoint ...
Deleteing folder '_tmp'...
All done !
Workbench clean now !
Which linux distro are you using ?
mariodantas said:
Which linux distro are you using ?
Click to expand...
Click to collapse
DISTRIB_ID=Pop
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Pop!_OS 22.04 LTS"
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os
update:
after some python3 tweaks, I was able to get my apns_conf.xml loaded into the unit, but it didn't help, I still get no data on Verizon. I may have to do the drastic and factory reset to see if that fixes anything since I think the unit is wonked but good.