Related
ok so im confused. I was reading the "how to flash cupcake" thread and came across this post by ridli. i tried following the instructions below but they failed, it seems like it works for him. if this truly works then there is no need for fastboot to reflash a nandroid back up. please help. thnx. BTW dudes .8 G build is awesome. (posted from my G1-modded w/root and gloss suite theme)
I tried the below on my G1 using recovery mode from JF-RC33 and i get:
error opening /sdcard/bu/system.img: no such file or directory.
I have checked the sdcard and its there, please help.
ridli said:
You can do the same without linux or any other SO.
1) Download cupcake
2) copy IMG files to a DIR in your SDCARD
3) reboot the phone in recovery mode
4) press ALT+X for go to console
5) #mount -a (for mount all partitions, without this you dont have flash_image becouse it is in /system/bin/)
6) use flash_image for flash the partitions
Code:
#flash_image system /sdcard/<dir>/system.img
#flash_image boot /sdcard/<dir>/boot.img
#flash_image userdata /sdcard/<dir>/data.img
7) #reboot
Optional: Do a backup of the phone with nandroid from the recovery mode, this do a img of system, data and boot partitions of your phone and copy to your sdcard. If you have any problem you can reflash your phone with you img.
Click to expand...
Click to collapse
It didn't work for me either, but it said I could not remount system as r/w because it was busy.
Anyway, I find instructions on how to do it via PC a lot easier. And if your phone would not boot, and you are stuck without backup, you can always pull it with adb.
Karolis:
System shouldn't be busy in recovery mode... also, it shouldn't be mounted if you're trying to write a fs image
And... no, if your phone can't boot, it can't boot. That includes starting adbd.
If you can enter recovery/spl, it's booting just fine.
flak0:
Have you checked the sdcard from the shell in android, or from your computer?
If it's the latter, you should make sure you can access the file from android.
I would recommend that you copy the flash_image binary out of /system (and /data), because you're rewriting that partition
Okay, don't use the forums when on a bad connection... my browser thought it lost connection, and decided to refresh, and send my post again... *Looks for a delete button*
this does not work
just so everyone is clear
DOES NOT WORK!
Note To Self, do not follow tutorials from junior members
arteshiftedscreen said:
this does not work
just so everyone is clear
DOES NOT WORK!
Note To Self, do not follow tutorials from junior members
Click to expand...
Click to collapse
Ummmm actually this does work if you do itcorrectly. Note to self no bashing people that are just trying to help.
so how is it done?
korndub said:
Ummmm actually this does work if you do itcorrectly. Note to self no bashing people that are just trying to help.
Click to expand...
Click to collapse
And could a Gscript or similar be written to do something like this? I'd be psyched to have the option to restore my phone on the fly. And of course, if you could do that, what would stop you from having a Nandroid restore point saved for a number of different builds? I would love that.
Out of curiosity, and I've never tried this method myself, are you just entering the following exactly?
#flash_image system /sdcard/<dir>/system.img
#flash_image boot /sdcard/<dir>/boot.img
#flash_image userdata /sdcard/<dir>/data.img
Click to expand...
Click to collapse
Or are you changing <dir> to the directory of your nandroid backup? Because if you aren't it certainly won't work.
ei8htohms said:
And could a Gscript or similar be written to do something like this? I'd be psyched to have the option to restore my phone on the fly. And of course, if you could do that, what would stop you from having a Nandroid restore point saved for a number of different builds? I would love that.
Click to expand...
Click to collapse
But it would be very unsafe to flash a fs image when the partition is actually mounted and your gscript is probably in it.
the only way is to do it in recovery mode.
one little problem though: i copied flash_image to /cache and chmod, but the shell kept telling me no such file. why is that?
billc.cn said:
But it would be very unsafe to flash a fs image when the partition is actually mounted and your gscript is probably in it.
the only way is to do it in recovery mode.
one little problem though: i copied flash_image to /cache and chmod, but the shell kept telling me no such file. why is that?
Click to expand...
Click to collapse
flash_image is a binary, should not be moved. why did you move it to cache? of course it wont work...
Unfortunately, flash_image does not support writing yaffs2 images. Look in the code, there's no support for writing the OOB data to the NAND. If it was possible I would've integrated backup AND restore in nandroid 2.0, and JesusFrekes recovery image would then also have a restore option. But alas, it's not to be.
Perhaps in a future release I can find a C coder who can add the code to the flash_image source, so that this becomes possible. But I'm not even sure if that can be done (because you need kernel driver support as well).
infernix said:
Unfortunately, flash_image does not support writing yaffs2 images. Look in the code, there's no support for writing the OOB data to the NAND. If it was possible I would've integrated backup AND restore in nandroid 2.0, and JesusFrekes recovery image would then also have a restore option. But alas, it's not to be.
Perhaps in a future release I can find a C coder who can add the code to the flash_image source, so that this becomes possible. But I'm not even sure if that can be done (because you need kernel driver support as well).
Click to expand...
Click to collapse
Can't we just use nandwrite from mtd-utils to do this? I haven't tried it yet (I'll build it for ARM when I get home from work), but it appears to be the right tool for the job. I'm really interested in getting a menu-driven restore in my recovery image.
cyanogen said:
Can't we just use nandwrite from mtd-utils to do this? I haven't tried it yet (I'll build it for ARM when I get home from work), but it appears to be the right tool for the job. I'm really interested in getting a menu-driven restore in my recovery image.
Click to expand...
Click to collapse
Oh that would be sooooooooo sweet!
Seems that a refurbished G1 I received has 3 blocks stuck and marked in eccUnfixed for some time, pulled the info from command:
Code:
cat /proc/yaffs
Issues:
I'm thinking as our G1s are getting older and with ROM flashing abuse we are killing NAND blocks on them fast. Researching at various sites linux-mtd & Yaffs.net, the garbage collector of Yaffs should be marking and removing these if Yaffs was controlling the ECC mode. However since Yaffs G1 android setting relies on NANDecc for marking bad blocks I'm not so sure which is cleaning up and not retiring these blocks, maybe NAND and YAFFS are in disagreements or one has ability to retire these blocks and end this problem. It seems though that while flashing ROMs data is being written on to these areas and after a remount it is evident that something may be wrong.
Experiences:
An app could go missing or a file or folder name with invalid characters may happen or a phones feature may suddenly stop workin such as scanning for wireless networks timing out.
The issue is reproducable on freshly erased partitions via fasboot erase system -w.
If a dev would like to co-ordinate with me I will grant them remote access to a system with said phone connected via usb with adb port redirection/remote adb or desktop access with adb and fastboot and vnc client with vnc server on phone .
Workaround:
Working with xda member Licknuts we tested numerous times with a few ROMs 1.6 and 2.1 and came up with this for a quick work around that basically involves erasing /system via fastboot then in recovery lock /system from being formatted and unmounted after ROM Flashing you then tarball /system partition to /sdcard do a reboot into fastboot and erase system again reboot into recovery and untarball back to /system.
Prerequisite:
A phone that suffers missing apps in /system or odd phone behavior features after fresh ROM flash.
ADB with Fastboot, USB Cable connected to your Phone.
Adapt the procedure bellow for issues stemming from the /data partition.
<Go for it>
Going to have to clear out system as it probably has corruption.
Code:
fasboot erase system
Note:::
Hboot spl dictates reboot & some engineer spls have no menu option and engineer spls do not reboot to recovery with an empty partitions when USB cable is connected so disconnect it and reboot then reconnect when in recovery console or just fastboot flash system system.img using HTC 1.6 system.img extracted from their zip.
FYI:::
Haykura sapphire spls (aka: danger spl / death spl) are able to boot to recovery with only radio/hboot/recovery partitions intact as long as it is instructed to do so other wise you get G1 screen with red[fastboot] with USB cable attached (might be the missing safety mode for bricked G1s but not certain).
Anyhow just Reboot to recovery console from menu option or [send][menu][hang] quickly hold [home]
Using adb shell we can lock system partition from being formatted and unmounted by ROM Flash scripts instructions in scripts.
Code:
adb shell
mount -a
cd /system
flash ROM and any updates from Recovery console on phone as normal...... and then we tarball the /system partition before it remounts on reboot and corruption happens
While still in adb shell and hanging out in /system, issue these commands to mount the sdcard and create a tarball of /system.
Code:
mount /sdcard
tar -cvf /sdcard/system.tar /system
sync
reboot bootloader
in fastboot we erase system again because most likely data will corrupt because the Flashing procedure may have written to bad blocks and when mounted or remounted it will corrupt, this is why we tarballed /system before it happens.
Code:
fastboot erase system
then reboot back to recovery console
using adb shell we un-tarball system.tar back to /system mountpoint with YAFFS that supposedly knows about these bad blocks so writing filles out these should be checked and avoided.
Issue these commands:
Code:
mount /sdcard
mount /system
tar -xvf /sdcard/system.tar -C /
sync
reboot
reboot as normally would and with some luck files wrote out avoiding those marked bad blocks.
Resolutions and notes:
flash_image and ROM flashing scripts may be flashing directly to device level which does not have YAFFS bad block information and once mounted with a file system, corruption happens from file system having bad block information.
Using sapphire spls (danger spl) we have access to fasboot oem task 28 & fastboot oem task 29 will low level format, repair, report and mark blocks bad but doesn't seem to resolve issues maybe YAFFS doesn't sync or care about the blocks marked in NAND mtd.
Possibly we need a compiled kernel and complete compiled tool set to fully work on Nand device mtd and format tools for Yaffs and scripts to automate some tasks. Seems Nandroid and /system/xbin, /sbin, /system/bin and recovery console tool-sets are limited as well.
*I think and type fast so note that typos may exists hopefully not in coding but elsewhere and if you exist solely to point out grammar and spelling of others on internet forums or broken English of members from other countries, then respect my preemptive "go **** yourself".
If my help aided in getting your phone in working order then give a family member or friend a call or donate some $ to the devs that keep our phones fun to use.
Have you got any more in-depth info on this?
The way I see it, you erase with fastboot... What does this accomplish that doesnt happen if one from the recovery console or adb, dd /dev/zero into the MTD device?
Or, better yet, wouldn't tarring the system partition after its written just copy the bad files that existed on the bad erase block(s)?
Or am i seriously not understanding what your instructions are doing.. To me:
Erase in some way once. What this does, i'm unsure.
Flash
Mount /system and tar to sdcard
Erase again (again what this does to assist the process is uncertain to me)
Boot to recovery
Mount everything
Untar from sdcard.
Tell me if I understand this wrong?
as some blocks are reserved to replace bad blocks , most of the time you won't see a problem
However, once these are used up you will effectively see partition 'shrinkage'
we can limit this 'shrinkage by using lbcoder's custom MTD via the kernel command line
I have a relatively simple way of implementing this
http://forum.xda-developers.com/showthread.php?p=7061471#post7061471
Thanks Phonekenstein for such a great input. I never knew this thread was exist until now but I found this and read the title, damn this is exactly what my case is!
Follow your instruction and re-install the rom, every single headached weird behaviors are disappear and the system runs like butter. It seems my phone is finally fixed!
I think this thread should get more attention.
(bump)
This is a great find! I will be trying this on my HD2 as I have some bad blocks also causing Android builds to go wack.
Another ArchiKitchen project. But first...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Given that, this ROM, is PURE STOCK, with root (if you choose that option). This is here to save your butt because you de-bloated some apps, or otherwise bricked your tab and forgot to make a nandroid first. This will bring you back to the latest version (3.1.0.42).
Please NOTE: This ROM is only designed for the WW SKU only! If you have a different SKU, and are that desperate, find another way first!
Because this is untouched stock, everything should work. Please recognize I have not tested this myself, as I have not found the need to use it (and the alternatives - that is, the ways to get out of it if it fails - are limited). So, if anyone finds their way to have to use this, please continue to note any success or failure, and any considerations in the comments - be it this thread, or the Q&A thread.
DOWNLOAD:
I am offering two versions these days (the old two had an updater-binary incompatible for the CWM provided) - a slightly modified version (built by the "bb" command in ArchiKitchen, accepting all the prompts - so permissions and symlinks are redone), and the other with the same but with root and SuperSU tacked on in the updater-script. If you are wondering which version to use, the former has been tested (at least once), but the latter is more straightforward.
K00L_Back_To_Stock_Updater-Binary.zip (MD5: 47ed2e94221c1d70bee17f39fd62bdff)
K00L_Back_To_Stock_With-SuperSU.zip (MD5: e78b6a4022a4f707e4d54f9440761be4)
INSTRUCTIONS:
Download ROM above
Download SuperSU update zip (optional, if you want root and using the first zip)
Connect your tab to the PC with appropriate adb, fastboot, and drivers available
If your device is bricked, enter fastboot and unlock bootloader with these instructions (or skip this part for post #3 instructions instead)
Download CWM to your PC (since the aforementioned link is down, post #62 has a source, and now I do as well)
Having completed that, reboot into fastboot and issue the following commands (or use the method in post #3):
Code:
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
Your tab will reboot into CWM
Push file(s) to your SD card ("adb push K00L_Back_To_Stock.zip /sdcard/" )
Nandroid/Back up broken device (optional, but highly recommended)
Wipe cache and data/factory reset (especially if you used XPosed - you can try dirty flashing, but from what I hear the data partition gets bunged after flashing anyway - thinks it is encrypted - so you are better off with the previous step and then salvaging from there)
Install ROM
Wipe Dalvik cache
Reboot
Enjoy!
RESOURCES:
CWM-based recovery
MeMO Pad 8 General Discussion
CREDITS:
Androtab.info
Chainfire for SuperSU
JustArchi for ArchiKitchen
Did I miss anything? I appreciate the feedback, and any thanks as well!
Alternate Flash / Other Info...
DD-BASED FLASH:
Thanks go to @t-mobile_mda for this method.
Since I have encountered others unable to flash the ROM zip in their CWM, I am providing a precursor that is more forgiving, but harder to accomplish, and as it is more forgiving, it is up to the end user to ... know what you are doing. So to recap...this ROM is for:
ASUS MeMO Pad 8 (ME180A)
Code named K00L
WW region only
With that out the way, you will need (besides the above device):
boot and system images
rebooted into CWM (see methods in posts above and/or below this post), and backup made
When ready, run the following commands:
Code:
adb devices
adb push boot.img /external_sd/
adb push system.img /external_sd/
adb shell
su
mount -o rw,remount /system
dd if=/external_sd/boot.img of=/dev/block/platform/emmc/by-name/boot
dd if=/external_sd/system.img of=/dev/block/platform/emmc/by-name/system
If CWM does not understand the logical mounts:
Code:
adb devices
adb push boot.img /external_sd/
adb push system.img /external_sd/
adb shell
su
mount -o rw,remount /system
dd if=/external_sd/boot.img of=/dev/block/mmcblk0p3
dd if=/external_sd/system.img of=/dev/block/mmcblk0p6
With all that successful, then factory reset and reboot.
RECOVERY FSTAB:
For anyone who wishes to make their own ROM...small piece of the puzzle
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/emmc/by-name/system /system ext4 noatime,nodiratime,noauto_da_alloc,discard wait
/dev/block/platform/emmc/by-name/userdata /data ext4 noatime,nodiratime,nosuid,nodev,noauto_da_alloc,discard wait,encryptable=/dev/block/platform/emmc/by-name/hidden
/dev/block/platform/emmc/by-name/cache /cache ext4 noatime,nodiratime,nosuid,nodev,noauto_da_alloc,discard wait
/dev/block/platform/emmc/by-name/parameter /parameter emmc defaults defaults
/dev/block/platform/emmc/by-name/misc /misc emmc defaults defaults
/dev/block/platform/emmc/by-name/kernel /kernel emmc defaults defaults
/dev/block/platform/emmc/by-name/boot /boot emmc defaults defaults
/dev/block/platform/emmc/by-name/recovery /recovery emmc defaults defaults
/dev/block/platform/emmc/by-name/backup /backup emmc defaults defaults
/dev/block/platform/emmc/by-name/adf /adf emmc defaults defaults
/dev/block/platform/emmc/by-name/apd /apd emmc defaults defaults
/dev/block/platform/emmc/by-name/hidden /hidden emmc defaults defaults
/dev/null /sdcard datamedia defaults defaults
/dev/block/mmcblk1p1 /external_sd auto defaults defaults
#/devices/platform/rk29_sdmmc.0/mmc_host/mmc /external_sd auto defaults voldmanaged=sdcard1:auto
#/devices/platform/usb20_otg/usb auto auto defaults voldmanaged=usbdisk:auto
Alternate way to install CWM
Thanks go to @mm2dd...
You may find that any attempt to unlock the bootloader to install CWM will ultimately fail. This provides another way.
First you need a Debian, Ubuntu, or derivative - essentially a GNU/Linux OS that handles .deb packages. This can be achieved with a VMWare or VirtualBox virtual machine, if you don't have (or want) a dual-boot setup.
Follow the steps to download, install, and run the RkFlashKit package:
http://www.hotmcu.com/wiki/Flashing...Using_The_Rockchip_Tool#Installing_RkFlashKit
Make sure the tab is plugged into the PC (and having the appropriate Windows drivers if using a VM) and the tab is in Rockchip bootloader mode before running RkFlashKit.
With the CWM Recovery files saved to the Linux Box (be it computer or virtual machine), make sure "Devices" is no longer blank (if it is, a step above got skipped), and set "NAND Partitions" to "Recovery".
You may want to "Backup Partition" before continuing.
Under "Image file to flash", choose the recovery_cwm.img file.
When ready, press "Flash Image"
Repeat for misc_reboot-recovery.img to the misc partition, and when done, select "Reboot Device", while holding the magic keys to get into recovery.
@OfficerJimLahey
This thread saved my ME180A Thank you so much and also androtab too...so sad there is no custom roms for this model and im noob to make my own Rom...anyways thanks again.
Hi there,
This thread could save my tablet from a loooong time mistake..
but.. when i arrive to the part of installng cwm, small issue, in fastboot..
Everything is good, drivers and adb installed, the tab appears when i give the command adb devices, but when in fastboot (well.. think it is.. the screen stays black..) , once i give the next command it stays at ''waiting for device'' .. and i cant see the device anymore when typing adb devices..
.. what can be the issue?
puss2puss said:
Hi there,
This thread could save my tablet from a loooong time mistake..
but.. when i arrive to the part of installng cwm, small issue, in fastboot..
Everything is good, drivers and adb installed, the tab appears when i give the command adb devices, but when in fastboot (well.. think it is.. the screen stays black..) , once i give the next command it stays at ''waiting for device'' .. and i cant see the device anymore when typing adb devices..
.. what can be the issue?
Click to expand...
Click to collapse
When in fastboot mode, use fastboot command instead.
OfficerJimLahey said:
When in fastboot mode, use fastboot command instead.
Click to expand...
Click to collapse
Thanks for the reply
Well actually, i do use fastboot commande once in fastboot mode.. but it was not detected but i noticed that when in fastboot, it use a different driver so when booting in fastboot, i replaced manually the driver kool for one that contain the words bootloader and it now detect it, but when writing the command ''fastboot devices'' it gives 123456789 ... but now i can give the commands from fastboot to reboot etc..
BUT.. ..when i type :
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
.. it says something like failed, device is locked..
puss2puss said:
Thanks for the reply
Well actually, i do use fastboot commande once in fastboot mode.. but it was not detected but i noticed that when in fastboot, it use a different driver so when booting in fastboot, i replaced manually the driver kool for one that contain the words bootloader and it now detect it, but when writing the command ''fastboot devices'' it gives 123456789 ... but now i can give the commands from fastboot to reboot etc..
BUT.. ..when i type :
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
.. it says something like failed, device is locked..
Click to expand...
Click to collapse
Yup, the bootloader will be locked. Post one is one way to go about it (bullet point four), post two is the other way.
OfficerJimLahey said:
Yup, the bootloader will be locked. Post one is one way to go about it (bullet point four), post two is the other way.
Click to expand...
Click to collapse
I know, if i.m asking for help, its because it fails on my side
after commands, it gives:
Writing 'recovery' ...
FAILED (remote: device is locked)
And if i try the commands ''fastboot oem unlock61646
fastboot oem unlockD696E'' , it gives:
FAILED (remote: oem admunlock not requested)
..what am i missing..
puss2puss said:
And if i try the commands ''fastboot oem unlock61646
fastboot oem unlockD696E'' , it gives:
FAILED (remote: oem admunlock not requested)
..what am i missing..
Click to expand...
Click to collapse
Yeah, that fails for whatever reason for some. If I gambled any amount I would say different device batches. The workaround would be post two. The advantage with that one is that you don't need to unlock the bootloader for CWM this way, at the downside of it's a bit more work (especially if you don't have access to a GNU/Linux PC or even a PC with a GNU/Linux live CD).
I never did this method (never had to) so unfortunately, my capability for help with this part is very limited.
.. in post 2 you explain how to make a rom.. not sure it will help me.. ah well.. thanks anyway and keep up the good work.
puss2puss said:
.. in post 2 you explain how to make a rom.. not sure it will help me.. ah well.. thanks anyway and keep up the good work.
Click to expand...
Click to collapse
Sorry, meant post three, titled "Alternate way to install CWM".
Well ubuntu did the trick i loaded latest ubuntu yesterday and boom everything went as expected i am now installing the stock rom! The story of this tablet is finally getting an happy ending lol..
When i bought the tablet long ago, i rooted it and deleted some apps and then i was never able to update it, but was using it everyday, utill the day it magicly fell on the ground.. glass broke.. tears crawld my cheeks.. then bought win8.1 tablet.
.. but a couple of weeks ago i ordered a glass and digitizer from aliexpress for 16$, repaired it, and now updating it from a fresh stock rom
Thanks for your great work here, keep it up mate!
Small question: do you (or anyone else) knows if kitkat is available somewhere for it? I read that its suppose to run kitkat but i cant find any direct info..
And when i click to update it doesnt find anything..
Not a big deal, but would be great
puss2puss said:
Small question: do you (or anyone else) knows if kitkat is available somewhere for it? I read that its suppose to run kitkat but i cant find any direct info..
And when i click to update it doesnt find anything..
Not a big deal, but would be great
Click to expand...
Click to collapse
I have heard something in passing recently somewhere along those lines. I don't think anything amounts to that or maybe someone was mistaken between the MeMO Pad models (ME181C has Kitkat).
Given this is a device released in 2013, ASUS would have long given up on it.
Yah thats what i think to..
And the more i read, the more i realize its the other models, its now clear.
Last year i was working on a rom but ţe progress stopped when the tab took a 'brake' .. ..so, now i wanna get back to it.
Where to start if i wanted to include an updated android into the rom?
puss2puss said:
Yah thats what i think to..
And the more i read, the more i realize its the other models, its now clear.
Last year i was working on a rom but ţe progress stopped when the tab took a 'brake' .. ..so, now i wanna get back to it.
Where to start if i wanted to include an updated android into the rom?
Click to expand...
Click to collapse
I know a little about that. You will need a device tree. Problem is, I don't think one is available.
Sent from my ASUS_Z00AD
Hi there!
I'm trying to install a new ROM on my MemoPad 8 (K01H), but I keep getting errors
When I type
Code:
fastboot flash recovery recovery_cwm.img
I get an error which says I have to unlock first. Even if this tutorial says I don't need to unlock it for CWM, I tried, but I get another error saying: "remote: unknown oem command".
I have 5.0.1 on my tab, I checked in the developer menu, and I don't have enable OEM unlock option at all o.o
I tried every possibilities I found and nothing worked. My tab is rooted. What I did wrong?
Yaime said:
Hi there!
I'm trying to install a new ROM on my MemoPad 8 (K01H), but I keep getting errors
When I type
Code:
fastboot flash recovery recovery_cwm.img
I get an error which says I have to unlock first. Even if this tutorial says I don't need to unlock it for CWM, I tried, but I get another error saying: "remote: unknown oem command".
I have 5.0.1 on my tab, I checked in the developer menu, and I don't have enable OEM unlock option at all o.o
I tried every possibilities I found and nothing worked. My tab is rooted. What I did wrong?
Click to expand...
Click to collapse
Wrong model. Please see first post on what this is for. Please don't continue to try to flash this ROM, or that CWM to your device. You will end up in a worse hole.
OfficerJimLahey said:
Another ArchiKitchen project. But first...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Given that, this ROM, is PURE STOCK, with root (if you choose that option). This is here to save your butt because you de-bloated some apps, or otherwise bricked your tab and forgot to make a nandroid first. This will bring you back to the latest version (3.1.0.42).
Please NOTE: This ROM is only designed for the WW SKU only! If you have a different SKU, and are that desperate, find another way first!
Because this is untouched stock, everything should work. Please recognize I have not tested this myself, as I have not found the need to use it (and the alternatives - that is, the ways to get out of it if it fails - are limited). So, if anyone finds their way to have to use this, please continue to note any success or failure, and any considerations in the comments - be it this thread, or the Q&A thread.
DOWNLOAD:
I am offering two versions these days (the old two had an updater-binary incompatible for the CWM provided) - a slightly modified version (built by the "bb" command in ArchiKitchen, accepting all the prompts - so permissions and symlinks are redone), and the other with the same but with root and SuperSU tacked on in the updater-script. If you are wondering which version to use, the former has been tested (at least once), but the latter is more straightforward.
K00L_Back_To_Stock_Updater-Binary.zip (MD5: 47ed2e94221c1d70bee17f39fd62bdff)
K00L_Back_To_Stock_With-SuperSU.zip (MD5: e78b6a4022a4f707e4d54f9440761be4)
INSTRUCTIONS:
Download ROM above
Download SuperSU update zip (optional, if you want root and using the first zip)
Connect your tab to the PC with appropriate adb, fastboot, and drivers available
If your device is bricked, enter fastboot and unlock bootloader with these instructions (or skip this part for post #3 instructions instead)
Download CWM to your PC
Having completed that, reboot into fastboot and issue the following commands (or use the method in post #3):
Code:
fastboot flash recovery recovery_cwm.img
fastboot flash misc misc_reboot-recovery.img
fastboot reboot
Your tab will reboot into CWM
Push file(s) to your SD card ("adb push K00L_Back_To_Stock.zip /sdcard/" )
Nandroid/Back up broken device (optional, but highly recommended)
Wipe cache and data/factory reset (especially if you used XPosed - you can try dirty flashing, but from what I hear the data partition gets bunged after flashing anyway - thinks it is encrypted - so you are better off with the previous step and then salvaging from there)
Install ROM
Wipe Dalvik cache
Reboot
Enjoy!
RESOURCES:
CWM-based recovery
MeMO Pad 8 General Discussion
CREDITS:
Androtab.info
Chainfire for SuperSU
JustArchi for ArchiKitchen
Did I miss anything? I appreciate the feedback, and any thanks as well!
Click to expand...
Click to collapse
hi..
i am getting error while installing ROMs.. can u pls check it.?
Hi everyone,
Are there any custom ROMs that will allow me to write to the system folder? More specifically, I have a few files that need to go into /system/bin/ for a tasker task.
I have tried while rooted the classic way with the Stock rom, but every time I reboot, the files get erased after I place them.
I have tried it on LineageOS as well, and get the same result.
I have an Android Device, GPD XD+, with CleanROM installed, and I am able to write files to the /system/bin/ folder for my Tasker task with no issue. I just want to be able to replicate that on my Pixel 4A.
The furthest I have gotten on my own is to try to disable verity, but that doesn’t work on any of the ROMS.
Without trying to install every ROM and testing, is there a ROM out there that will allow me to write to /system/bin/ without it erasing it on the reboot?
Thank you all!
try
Code:
adb shell
mount --remount / -w
this should allow you to write to the system partition. copy the files you need onto any folder on your phone first and then move them to their destination.
THEGAZINGVOID said:
try
Code:
adb shell
mount --remount / -w
this should allow you to write to the system partition. copy the files you need onto any folder on your phone first and then move them to their destination.
Click to expand...
Click to collapse
I left something out of my post, whoops. In the process of trying to reflash the stock image after LineageOS, I accidentally made it so my phone does not boot after the fast boot screen. I can fix it when I have some more spare time this weekend, but for the time being my phone isn’t useable without more flashing. I was thinking I could post here and have a brainstorming session before I dive back in (since I spent half of Saturday trying to get it to work).
I will try that command first thing though once I get my phone up and running again. If it was that simple, I’ll be kicking myself for sure. Thanks for replying so quick!
oh no! well, best of luck then. crossing my fingers for you!
THEGAZINGVOID said:
oh no! well, best of luck then. crossing my fingers for you!
Click to expand...
Click to collapse
Scary times, haha. Thanks!
Update: just flashed back to stock rom successfully, so now I can try any suggestions!
THEGAZINGVOID said:
try
Code:
adb shell
mount --remount / -w
this should allow you to write to the system partition. copy the files you need onto any folder on your phone first and then move them to their destination.
Click to expand...
Click to collapse
Ok, so I tried this, and it says: “‘dev/block/dm-1’ not user mountable in fstab.”
I found this zip file, but am not sure what to do with it with only Magisk:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
damn, i just noticed that i missed a crucial step! your phone has to be rooted. then, in terminal/cmd enter
adb shell
su
grant root permission in the popup on your phone
mount --remount / -w
THEGAZINGVOID said:
damn, i just noticed that i missed a crucial step! your phone has to be rooted. then, in terminal/cmd enter
adb shell
su
grant root permission in the popup on your phone
mount --remount / -w
Click to expand...
Click to collapse
Ohhh ok. I’m out right now, but as soon as I get home, I will try that!
Ok, got home, and it says: "'/dev/block/dm-1' is read-only"
Also, I checked the build is a user build.
Hi guys,
Here, for those who are interested, I'm maintaining the packages to use postmarketOS on bare-metal hardware.
I only tested the A750FN variant.
Check it out!
Feedbacks are welcome!
Many thanks:
@VDavid003 for kernel sources
Thanks alot for making this contribution
M0Rf30 said:
Hi guys,
Here, for those who are interested, I'm maintaining the packages to use postmarketOS on bare-metal hardware.
I only tested the A750FN variant.
Check it out!
Feedbacks are welcome!
Many thanks:
@VDavid003 for kernel sources
Click to expand...
Click to collapse
After a week or 2 i can get back home and test it , so keep making these and I'll test them and tell you about my experience
Hello, can you share how you did it? I can't find any files for flashing on the postmarketos wiki page, I have TWRP installed.
Arm1nas said:
Hello, can you share how you did it? I can't find any files for flashing on the postmarketos wiki page, I have TWRP installed.
Click to expand...
Click to collapse
I haven't tested it yet , but you'll have to use the pmbootstrap tool to build a zip that you can flash through the TWRP
The wiki of postmarketOS explains how to use the pmbootstrap tool. Go check it out
animegamer4422 said:
I haven't tested it yet , but you'll have to use the pmbootstrap tool to build a zip that you can flash through the TWRP
The wiki of postmarketOS explains how to use the pmbootstrap tool. Go check it out
Click to expand...
Click to collapse
I figured it out. I created an Ubuntu VM and built it. I am not sure why but now the phone doesn't boot to pmOS, it just spits out some errors or there is only a terminal. TWRP says it can't mount /system, maybe I have to reflash the recovery.
Arm1nas said:
I figured it out. I created an Ubuntu VM and built it. I am not sure why but now the phone doesn't boot to pmOS, it just spits out some errors or there is only a terminal. TWRP says it can't mount /system, maybe I have to reflash the recovery.
Click to expand...
Click to collapse
I don't think it's a issue with the recovery and also it's normal for TWRP to not be able to mount the system
Let's try to diagnose it by going through the error
Could you upload the log and also the screenshot of the error that it spits out
Also upload the built image to some cloud service and send the link here so that i don't have to go through and build the image again
Thanks for testing it out and I'll join you soon so keep trying and I'll try to do everything i can to help you , Have a good day.
animegamer4422 said:
I don't think it's a issue with the recovery and also it's normal for TWRP to not be able to mount the system
Let's try to diagnose it by going through the error
Could you upload the log and also the screenshot of the error that it spits out
Also upload the built image to some cloud service and send the link here so that i don't have to go through and build the image again
Thanks for testing it out and I'll join you soon so keep trying and I'll try to do everything i can to help you , Have a good day.
Click to expand...
Click to collapse
pmos-samsung-a7y18lte.zip
drive.google.com
I think that it's trying to install itself to /system partition which is very small, and the "data" partition is like 50GB. Maybe it's a problem with PBRP (I can't install twrp, it doesn't work for me).
Can you try installing this file and testing if it works for you, or is it the same problem?
Arm1nas said:
pmos-samsung-a7y18lte.zip
drive.google.com
I think that it's trying to install itself to /system partition which is very small, and the "data" partition is like 50GB. Maybe it's a problem with PBRP (I can't install twrp, it doesn't work for me).
Can you try installing this file and testing if it works for you, or is it the same problem?
Click to expand...
Click to collapse
I'd love to test it , but currently I'm not at my home and my A7 is at home (since It's not my daily driver) but I'll test it as soon as I can get back home
Until then
Keep figuring out things
Also I think you can use the TWRP terminal to Change the size of system partition using the resize2fs command i guess
I found this when I looked into it
First to clarify, Resize Partition is different than Resize File System, TWRP provides latter option. It resizes the ext2/3/4 filesystem to the size of partition it's created on. Filesystem size can be checked with df command when mounted, and partition size with blockdev. Just like HDDs or SSDs on PC, Android's eMMC storage is divided into partitions (can be 50+). Some of them have filesystem e.g. the larger ones userdata and system. In simple cases a filesystem occupies a complete physical partition, but it's not always the case, LVM makes it possible to have single filesystem on multiple partitions. Or the opposite what happened in your case as explained here: Sometimes the zip file of: a custom ROM does not have the correct size for the system partition and if the ROM flashes a raw system image, that image will not take up the full block device. Running resize2fs can fix the size Similarly: Sometimes flashing a factory image may flash userdata with an image with a file system that does not take up the full size of the block device So TWRP can expand the filesystem to reclaim wasted space. That's what happened in your case to the /system partition. The actual size of partition was 2.5 GB, but flashed image was of 1.5 GB. Coming to your query: I realized that the system partition is too big (~1.5GB). The current ROM uses only about 40% of the partition so I want to shrink it to make space for cache and data. You want to resize partition, not filesystem. So resize2fs (which TWRP uses at back end) isn't the right choice. As your partition table suggests, you need to delete and recreate partitions 9 to 12. IT'S DANGEROUS AND NOT RECOMMENDED, you may permanently brick your device. All data on these partitions will be lost, so do backup. Also, fdisk isn't proper tool for GPT, it's for MBR partition scheme. Use parted or gdisk instead, but with great care.
So now you can just resize the system partition in case it's size is smaller than the image (not likely in my opinion)
animegamer4422 said:
I'd love to test it , but currently I'm not at my home and my A7 is at home (since It's not my daily driver) but I'll test it as soon as I can get back home
Until then
Keep figuring out things
Also I think you can use the TWRP terminal to Change the size of system partition using the resize2fs command i guess
I found this when I looked into it
First to clarify, Resize Partition is different than Resize File System, TWRP provides latter option. It resizes the ext2/3/4 filesystem to the size of partition it's created on. Filesystem size can be checked with df command when mounted, and partition size with blockdev. Just like HDDs or SSDs on PC, Android's eMMC storage is divided into partitions (can be 50+). Some of them have filesystem e.g. the larger ones userdata and system. In simple cases a filesystem occupies a complete physical partition, but it's not always the case, LVM makes it possible to have single filesystem on multiple partitions. Or the opposite what happened in your case as explained here: Sometimes the zip file of: a custom ROM does not have the correct size for the system partition and if the ROM flashes a raw system image, that image will not take up the full block device. Running resize2fs can fix the size Similarly: Sometimes flashing a factory image may flash userdata with an image with a file system that does not take up the full size of the block device So TWRP can expand the filesystem to reclaim wasted space. That's what happened in your case to the /system partition. The actual size of partition was 2.5 GB, but flashed image was of 1.5 GB. Coming to your query: I realized that the system partition is too big (~1.5GB). The current ROM uses only about 40% of the partition so I want to shrink it to make space for cache and data. You want to resize partition, not filesystem. So resize2fs (which TWRP uses at back end) isn't the right choice. As your partition table suggests, you need to delete and recreate partitions 9 to 12. IT'S DANGEROUS AND NOT RECOMMENDED, you may permanently brick your device. All data on these partitions will be lost, so do backup. Also, fdisk isn't proper tool for GPT, it's for MBR partition scheme. Use parted or gdisk instead, but with great care.
So now you can just resize the system partition in case it's size is smaller than the image (not likely in my opinion)
Click to expand...
Click to collapse
The /system partition is 3.9G big.
This is everything:
https://imgur.com/MOKz0uR
Arm1nas said:
The /system partition is 3.9G big.
This is everything:
https://imgur.com/MOKz0uR
Click to expand...
Click to collapse
Sorry i was sick from past 2 days so couldn't reply earlier
Anyways could you like drop to a shell when you boot up postmarketOS
If yes then check the dmesg
I also think you'll have to flash a special kernel which could also be obtained from the pmbootstrap tool
Also it'd be great if you could record a video of the phone booting up into postmarketOS as that'd help us understand until how far it can reach and where it gets stuck
Thanks alot and Take care
animegamer4422 said:
Sorry i was sick from past 2 days so couldn't reply earlier
Anyways could you like drop to a shell when you boot up postmarketOS
If yes then check the dmesg
I also think you'll have to flash a special kernel which could also be obtained from the pmbootstrap tool
Also it'd be great if you could record a video of the phone booting up into postmarketOS as that'd help us understand until how far it can reach and where it gets stuck
Thanks alot and Take care
Click to expand...
Click to collapse
Hello, did you make any progress with it? I will try installing pmOS again and recording everything.
This is my installation procedure:
On a Ubuntu 20.04 VM I run:
$ pmbootstrap init
I select my device, DE, go through the setup.
Then I type:
$ pmbootstrap install --android-recovery-zip
$ pmbootstrap export
Then on the phone I unmount everything:
https://imgur.com/PlQZ1oB
Go to ADB sideload:
https://imgur.com/xf1FBzQ
https://imgur.com/H9AbkXY
I connect the phone to my computer and use this command to install pmOS:
$ adb sideload pmos.zip
I recorded the installation procedure:
As you can see it boots up the first time, the file system only has 2.6GB free, when it reboots again, it just boots into busybox terminal. When trying to boot up it gives me these errors:
https://imgur.com/qEtwRlx
I logged in and typed:
$ df -H
This is the output:
https://imgur.com/7n61Vm3
If I try to start the desktop environment with $ startx command I get these errors:
https://imgur.com/8xOA1kc
dmesg output:
https://imgur.com/eizBP3m
https://imgur.com/nP8aAaB
This is the phone's partition layout:
https://imgur.com/9xNmaAV
https://i.imgur.com/M0m3GjW.png
D
Arm1nas said:
This is my installation procedure:
On a Ubuntu 20.04 VM I run:
$ pmbootstrap init
I select my device, DE, go through the setup.
Then I type:
$ pmbootstrap install --android-recovery-zip
$ pmbootstrap export
Then on the phone I unmount everything:
https://imgur.com/PlQZ1oB
Go to ADB sideload:
https://imgur.com/xf1FBzQ
https://imgur.com/H9AbkXY
I connect the phone to my computer and use this command to install pmOS:
$ adb sideload pmos.zip
I recorded the installation procedure:
As you can see it boots up the first time, the file system only has 2.6GB free, when it reboots again, it just boots into busybox terminal. When trying to boot up it gives me these errors:
https://imgur.com/qEtwRlx
Click to expand...
Click to collapse
Sorry for the late reply
Anyways i just got home and have the smartphone I'm my hands
So i can too test it out
Also I think we should try switching to Wayland as X seems to be crashing
By using Wayland if it works we'll know that it's not a Xorg issue but if Wayland too fails we'll know that it's a big in the Kernel and the way it handles hardware
Also could you create a Telegram group for us to chat instantly I think that way we can help each other better and then we'll just create a general guide on fixing things ok XDA
(I cannot post links since I didn't started the thread)[/url]
Arm1nas said:
This is my installation procedure:
On a Ubuntu 20.04 VM I run:
$ pmbootstrap init
I select my device, DE, go through the setup.
Then I type:
$ pmbootstrap install --android-recovery-zip
$ pmbootstrap export
Then on the phone I unmount everything:
https://imgur.com/PlQZ1oB
Go to ADB sideload:
https://imgur.com/xf1FBzQ
https://imgur.com/H9AbkXY
I connect the phone to my computer and use this command to install pmOS:
$ adb sideload pmos.zip
I recorded the installation procedure:
As you can see it boots up the first time, the file system only has 2.6GB free, when it reboots again, it just boots into busybox terminal. When trying to boot up it gives me these errors:
https://imgur.com/qEtwRlx
I logged in and typed:
$ df -H
This is the output:
https://imgur.com/7n61Vm3
If I try to start the desktop environment with $ startx command I get these errors:
https://imgur.com/8xOA1kc
dmesg output:
https://imgur.com/eizBP3m
https://imgur.com/nP8aAaB
This is the phone's partition layout:
https://imgur.com/9xNmaAV
https://i.imgur.com/M0m3GjW.png
Click to expand...
Click to collapse
Sorry for the late reply
Anyways ...post links since I didn't started the thread)
Arm1nas said:
This is my installation procedure:
On a Ubuntu 20.04 VM I run:
$ pmbootstrap init
I select my device, DE, go through the setup.
Then I type:
$ pmbootstrap install --android-recovery-zip
$ pmbootstrap export
Then on the phone I unmount everything:
https://imgur.com/PlQZ1oB
Go to ADB sideload:
https://imgur.com/xf1FBzQ
https://imgur.com/H9AbkXY
I connect the phone to my computer and use this command to install pmOS:
$ adb sideload pmos.zip
I recorded the installation procedure:
As you can see it boots up the first time, the file system only has 2.6GB free, when it reboots again, it just boots into busybox terminal. When trying to boot up it gives me these errors:
https://imgur.com/qEtwRlx
I logged in and typed:
$ df -H
This is the output:
https://imgur.com/7n61Vm3
If I try to start the desktop environment with $ startx command I get these errors:
https://imgur.com/8xOA1kc
dmesg output:
https://imgur.com/eizBP3m
https://imgur.com/nP8aAaB
This is the phone's partition layout:
https://imgur.com/9xNmaAV
https://i.imgur.com/M0m3GjW.png
Click to expand...
Click to collapse
I installed plasma desktop and it seems to be working great though there's no on screen keyboard so i had to use a USB OTG to connect a external keyboard and unlock the device and use it And also the performance is not very great it lags alot probably due to the lack of GPU acceleration
animegamer4422 said:
I installed plasma desktop and it seems to be working great though there's no on screen keyboard so i had to use a USB OTG to connect a external keyboard and unlock the device and use it And also the performance is not very great it lags alot probably due to the lack of GPU acceleration
Click to expand...
Click to collapse
What method did you use to flash pmOS? And what recovery do you have? Mind sharing the built pmOS files, so I can flash it myself?
Arm1nas said:
What method did you use to flash pmOS? And what recovery do you have? Mind sharing the built pmOS files, so I can flash it myself?
Click to expand...
Click to collapse
I created a recovery zip using Pmbootstrap and also I set the free space parameter (after running pmbootstrap init) to 2000mb (2gb)
And then i copied that zip file from the temp directory to a Pendrive and connected the pendrive to the phone in recovery mode (PBRP Recovery) and then flashed it
I'll upload the files in a bit
Also I tried using Phosh but it just gets to the Login TTY and then doesn't boots up and i think that's because the device lacks GPU acceleration
Also here's a Telegram group link which I'll delete once you join the group
~REMOVED~
M0Rf30 said:
Hi guys,
Here, for those who are interested, I'm maintaining the packages to use postmarketOS on bare-metal hardware.
I only tested the A750FN variant.
Check it out!
Feedbacks are welcome!
Many thanks:
@VDavid003 for kernel sources
Click to expand...
Click to collapse
hello, are this thread still active?