I have really "screwed" up here. I erased everything on my TouchPad. So, how can I add the files I needed in order to get the rest of Android 9?
I have tried several files with TPToolbox (2015-01-08-v42) and did not get anywhere.
So, right now I could use some big help here. Without an OS, I cannot even get TWRP installed.
Thanks ahead for any help and support here.
BTW, I had Dirty Unicorn 8.1 before I erased everything. So I am really looking forward to this new version.
What does it show on the moboot menu when the TP is booted?
There was nothing, no software or moboot installed. I did finally manage to get TWRP installed (3.1.0.0) and during boot moboot version 0.3.8 shows up as well. So good for the great (really!) news.
But I now have a new problem, when I download load "du_tenderloin-v13.0-20190328-1316-RC.zip" the MD5 value does not match and it fails installation. I have tried 4-5 times on the downloads and still fails the MD5 value. I guess I'll wait till the next RC release or does someone knows where I can get a good release?
BTW- Thank you "HP_TOUCHPAD" for getting back to me. I really appreciate it. And to all the guys on this forum, especially a big thank you to Flintman for all that he has done .
How are you installing DU v13?
There is nothing wrong with the file from the site.
Using TWRP 3.1 0-0:
Select the flash zip file.
On the next screen in Options ( uncheck ) Zip signature verification.
The ROM will install with no issues.
HP_TOUCHPAD said:
How are you installing DU v13?
There is nothing wrong with the file from the site.
Using TWRP 3.1 0-0:
Select the flash zip file.
On the next screen in Options ( uncheck ) Zip signature verification.
The ROM will install with no issues.
Click to expand...
Click to collapse
_________________________________________________
I downloaded a "fresh" version of du_tenderloin-v13.0-20190328-1316-RC.zip (MD5 still did not match).
I made sure that "Zip signature verification" was unchecked and went ahead and installed it again.
During the installation I get the following error:
Flashing Dirty Unicorns System files...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file "/external_sd/ttinstall/du_tenderloin-v13.0-20190328-1316-RC.zip"
Updating partition details...
...done
I went ahead and re-boot the unit and it would only show the following:
moboot 0.3.8
boot TWRP
boot webOS Recovery
reboot
shutdown
For some reason I believe that the file is not coming down correctly (?) and because my MD5 does not match is the reason I'm thinking this.
Thanks for the support you are giving me.
The MD5 posted it for the 20190328 ROM is:
3fb70d72204ce4e8eef56fb4548930b6
I downloaded the 20190328 ROM and in Ubuntu did a md5sum on the file, the result:
89e32f1c6b5cf6792bf3ac6216c40a26
MD5 does not match.
Installed the ROM in TWRP 3.1. 0-0 after preparing the system for DU v13 as explain on this guide:
HP TOUCHPAD Optimize for Android with Swap Partition and SKZ Kernel_ Flash Files_
From the TWRP installation screen:
Installing zip file '/external_sd/du_tenderloin-v13.0-20190328-1316-RC.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Warning: No file_contexts
The ROM finished the installation property
Question:
How was the Android partitions created before installing the DU v13 ROM?
Was the /system partition created of a size of 1.4GB or larger?
How was the Android partitions created before installing the DU v13 ROM?
Using "Wipe_All_and_Create_Android_with_Swap_Partition"
Was the /system partition created of a size of 1.4GB or larger? Yes, 1.7GB I believe.
So, I have started over again -
I re-booted and from MOUNT I Selected (checked) Cache, Data, System and Micro SDCard (some were not checked before)
Then I went back to Install and tried again.
Great! This time I get;
Flashing boot image...
script succeeded: result was [1.000000}
Updating partition details...
According the web page - ..."installed the ROM as always, there is nothing else to do..."
I then rebooted - booting into Android - Optimizing app xx of 120
Upon finishing I get the following error "Weather Information Pro...keeps stopping.
Also, I am unable to connect to the Play Store to update the Play Service app,
Showed that Android Play Store was outdated.
Tried to installed "open-gapps-arm-9.0-pico-20190405.zip" but it failed with the following error:
Error Code: 40 - Unmounting /system
My new question is: How do I install open-gapp to get the latest? And does open-gapp also installs
the Play Service app?
Again, thanks for all the help.
_dave said:
How was the Android partitions created before installing the DU v13 ROM?
Using "Wipe_All_and_Create_Android_with_Swap_Partition"
Was the /system partition created of a size of 1.4GB or larger? Yes, 1.7GB I believe.
So, I have started over again -
I re-booted and from MOUNT I Selected (checked) Cache, Data, System and Micro SDCard (some were not checked before)
There is no need to mount anything, the ROM will mount everything that it needs when flashing.
Then I went back to Install and tried again.
Great! This time I get;
Flashing boot image...
script succeeded: result was [1.000000}
Updating partition details...
According the web page - ..."installed the ROM as always, there is nothing else to do..."
I then rebooted - booting into Android - Optimizing app xx of 120
The basic ROM needs to be install, the ROM does not provide any Apps.
Why is Android Optimizing app xx of 120?
Did you installed or restore any extra Apps?
Upon finishing I get the following error "Weather Information Pro...keeps stopping.
How was the Weather Information Pro installed?
Also, I am unable to connect to the Play Store to update the Play Service app,
Showed that Android Play Store was outdated.
Did you restore an old version onto DU v13?
Tried to installed "open-gapps-arm-9.0-pico-20190405.zip" but it failed with the following error:
Error Code: 40 - Unmounting /system
My new question is: How do I install open-gapp to get the latest? And does open-gapp also installs
the Play Service app?
The proper way to have a working Tablet:
1. Using the Wipe_ALL_Create_Android_With_Swap ( DU v13, Android Pie needs a swap partition)
2. Reboot
3. Flash the DUv13 ROM and the version of open-gapp and the same time.
The best is to use the Variant Pico, is the basic and allows Play Service to install any Apps.
Click here to download the latest open-gapp
Again, thanks for all the help.
Click to expand...
Click to collapse
You are very welcome !
Hi HP_TOUCHPAD, I repeated your last steps (again) and FINALLY FULL SUCCESS!!! OMG - THANK YOU!
_dave said:
Hi HP_TOUCHPAD, I repeated your last steps (again) and FINALLY FULL SUCCESS!!! OMG - THANK YOU!
Click to expand...
Click to collapse
Good to know you were able to get your Tablet working. Keep an eye on the DU v13 on here as more enhancement will be posted it. Enjoy your all new again HP TP !
Related
Hi,
this is my first post on xda and first Android device well actually it's a present for my daughter. First i'd like to say that you guys doing a great work here! Thank you!
Last couple of days (and nights) I spend reading and reading and reading.. http://forum.xda-developers.com/showthread.php?t=1905674 - now 101 pages! I am not in UK or US or any other country where nabi app shop is working, the only option for me is G play store. So rooting and installing gapps is the way for me. Unfortunately jmztaylor's method not working for me. Not only for me on page 26 (http://forum.xda-developers.com/showthread.php?t=1905674&page=26) mr_tris reported of having the same problem, but never got a solution for it and I see that MikeDVH (http://forum.xda-developers.com/showpost.php?p=35985909&postcount=1020) just reported the same issue:
failed to mount data (invalid argument)
-- Could not mount :/sdcard
-- Aborting
Backup failed!
I am getting the same error. There is plenty of free space (3+GB) and 2GB SD card. No apps on tablet, just configured Nabi mode.
The only explanation I can come up with that it's something different in UK model of Nabi2. The model reads: NABI2-NV7A-UK
My Nabi2 came with 1.9.29 and before attempting to root I upgraded to 1.9.37
I am thinking to trying http://forum.xda-developers.com/showthread.php?t=2041224 flash with his supplied stock version 1.9.37, but don't wanna mess something. I can supply any additional information or images needed, but to be honest will need some guidance in doing that as not very familiar with all this flashing thing, but not afraid of CLI
I can not post in that thread, but maybe it will be good to have thread dedicated to UK version of Nabi 2. Any other Nabi2-UK owners having problems/success?
regards
p.
petras_m said:
Hi,
this is my first post on xda and first Android device well actually it's a present for my daughter. First i'd like to say that you guys doing a great work here! Thank you!
Last couple of days (and nights) I spend reading and reading and reading.. http://forum.xda-developers.com/showthread.php?t=1905674 - now 101 pages! I am not in UK or US or any other country where nabi app shop is working, the only option for me is G play store. So rooting and installing gapps is the way for me. Unfortunately jmztaylor's method not working for me. Not only for me on page 26 (http://forum.xda-developers.com/showthread.php?t=1905674&page=26) mr_tris reported of having the same problem, but never got a solution for it and I see that MikeDVH (http://forum.xda-developers.com/showpost.php?p=35985909&postcount=1020) just reported the same issue:
failed to mount data (invalid argument)
-- Could not mount :/sdcard
-- Aborting
Backup failed!
I am getting the same error. There is plenty of free space (3+GB) and 2GB SD card. No apps on tablet, just configured Nabi mode.
The only explanation I can come up with that it's something different in UK model of Nabi2. The model reads: NABI2-NV7A-UK
My Nabi2 came with 1.9.29 and before attempting to root I upgraded to 1.9.37
I am thinking to trying http://forum.xda-developers.com/showthread.php?t=2041224 flash with his supplied stock version 1.9.37, but don't wanna mess something. I can supply any additional information or images needed, but to be honest will need some guidance in doing that as not very familiar with all this flashing thing, but not afraid of CLI
I can not post in that thread, but maybe it will be good to have thread dedicated to UK version of Nabi 2. Any other Nabi2-UK owners having problems/success?
regards
p.
Click to expand...
Click to collapse
i get the same error! any help would be great
Nabi 2 - UK Root and Gapps Install
After some more tries I finally rooted my nabi2-UK and successfully installed gapps!
Original files and credit go to jmztaylor from this thread: http://forum.xda-developers.com/showthread.php?t=1905674
New gapps and credit (no "Android Upgrading" message every reboot) go to t499user: http://forum.xda-developers.com/showthread.php?p=35888524 and manual recovery and flash http://forum.xda-developers.com/showthread.php?t=2016463
I’ve done “semi manual/automatic” if you can say that. So the steps were:
1. From http://junefabrics.com/android/ installed PdaNet for Android to have all proper drivers. My system win 7 64
2. set everything according http://forum.xda-developers.com/showthread.php?t=1590800
3. ran jmztaylor insatall.bat and selected option 2
4. in the background watching http://www.youtube.com/watch?v=HcAIsePNYVE – found some very useful notices – Thanks!
5. followed till the end, with the error: failed to mount data (invalid argument) and -- Could not mount :/sdcard
6. in TWRP selected Backup and done backup to external SD card
7. nabi being still in TWRP on pc opened command prompt and run:
Code:
adb push root.zip /sdcard/root.zip
and
Code:
adb push gapps.zip /sdcard/gapps.zip
8. In TWRP selected Install, navigated to /sdcard and selected root.zip after it was installed, the same done for gapps.zip
9. rebooted, run superSU, google play was installed, downloaded root checker – Congratulations! This device has root access!
Rebooted several times – everything ok.
I believe that this can be done in a better way, but this is just my experience and maybe it will help someone.
Sorry if some may sound in proper – English is not my native language
Happy New Year!
THANKYOU
petras_m said:
After some more tries I finally rooted my nabi2-UK and successfully installed gapps!
Original files and credit go to jmztaylor from this thread: http://forum.xda-developers.com/showthread.php?t=1905674
New gapps and credit (no "Android Upgrading" message every reboot) go to t499user: http://forum.xda-developers.com/showthread.php?p=35888524 and manual recovery and flash http://forum.xda-developers.com/showthread.php?t=2016463
I’ve done “semi manual/automatic” if you can say that. So the steps were:
1. From http://junefabrics.com/android/ installed PdaNet for Android to have all proper drivers. My system win 7 64
2. set everything according http://forum.xda-developers.com/showthread.php?t=1590800
3. ran jmztaylor insatall.bat and selected option 2
4. in the background watching http://www.youtube.com/watch?v=HcAIsePNYVE – found some very useful notices – Thanks!
5. followed till the end, with the error: failed to mount data (invalid argument) and -- Could not mount :/sdcard
6. in TWRP selected Backup and done backup to external SD card
7. nabi being still in TWRP on pc opened command prompt and run:
Code:
adb push root.zip /sdcard/root.zip
and
Code:
adb push gapps.zip /sdcard/gapps.zip
8. In TWRP selected Install, navigated to /sdcard and selected root.zip after it was installed, the same done for gapps.zip
9. rebooted, run superSU, google play was installed, downloaded root checker – Congratulations! This device has root access!
Rebooted several times – everything ok.
I believe that this can be done in a better way, but this is just my experience and maybe it will help someone.
Sorry if some may sound in proper – English is not my native language
Happy New Year!
Click to expand...
Click to collapse
Just wanted to say thanks to you and everyone on this site! i had a bit of trouble rooting my daughters nabi 2, but thanks to you i got it sorted!
Happy new year!!
:laugh::laugh:
easytiger1978 said:
Just wanted to say thanks to you and everyone on this site! i had a bit of trouble rooting my daughters nabi 2, but thanks to you i got it sorted!
Happy new year!!
:laugh::laugh:
Click to expand...
Click to collapse
Glad to hear that it worked for you. There is an updated recovery with various fixes so all that still have, in first post mentioned error, might wanna try http://forum.xda-developers.com/showthread.php?p=36083895#post36083895
Just replace recovery.img and gapps.zip in jmztaylor Files directory with new ones and try.
petras_m said:
Glad to hear that it worked for you. There is an updated recovery with various fixes so all that still have, in first post mentioned error, might wanna try http://forum.xda-developers.com/show....php?t=2074501
Just replace recovery.img and gapps.zip in jmztaylor Files directory with new ones and try.
Click to expand...
Click to collapse
I think that link is broken?
easytiger1978 said:
I think that link is broken?
Click to expand...
Click to collapse
updated link
failed to install / invalid argument whilst pushing root and Gapps on Nabi 2
A huge thank you for the 'how to' and files to help me root my nieces Nabi 2! ;0) I successfully rooted and installed Google apps, although I did it differently to the above methods.
(I'm using windows 8 and the Nabi 2 was already on 1.9.37. The device shows as NABI2-NV&A-UK under my computer)
I kept stalling at the point after the files were being pushed to the SD card. I also had the 'invalid argument / failed transfer' message flash up on the Nabi for a split second, and then hanging as the Nabi was disconnected from my laptop, until a reboot was done; but then it was not in developer mode. After going round in circles and reading for about an hour and a half (and watching the helpful video on youtube), and then coming here to see the above post, I tried the command prompt push method but still no joy! When I tried that method the files being pushed would show up on the Nabi screen but they would not install, there was also an error message after each attempt (I cannot remember exactly what it said now, sorry).
Two hours later and still no luck. Then I thought 'what if I did it this way' > ... I rebooted the Nabi 2, with a 2gb SD card in it. I opened 'my computer' and formatted the SD card. I dragged and dropped the Root.zip and Gapps.zip files to the root of SD card. I ran the adb driver app, via the command prompt (which in windows 8 can be accessed by pushing the windows key and X, then choosing 'command prompt' as there's no link for it in accessories) and then I ran the jmzrootpack 'install.bat' file to get the Nabi into developer mode. Then I entered install via the menu and the files were there! I installed the root and gapps files as in the youtube video, rebooted and everything was installed and worked as it should. Job done!
Once again thank you to the developers who made this possible ;0)
CyanogenMod is a free, community built, aftermarket firmware distribution of Android N (Nougat), which is designed to increase performance and reliability over stock Android for your device.
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 if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
This rom is for the Nook Tablet 1GB/16GB versions. The device code name is "acclaim".
Prerequisites:
A recovery. To install a recovery when coming from a stock device, you need to prepare a special SD card. Installation instructions can be found here on xda.
Installation:
Android N requires more space on the system partition. To load the Google Apps, it is necessary to repartition the device.
To repartition, flash the recovery partition that can be found here with fastboot:
https://basketbuild.com/filedl/devs...ery-repartition-acclaim-cm14.1-UNOFFICIAL.img
Boot into this recovery and select "Advanced->Repartion Nook Tablet for Android N".
The screen turns black for a minute or so and the repartitioning is happening.
Then select "Advanced->Reboot recovery" to reboot into recovery again.
NOTE: Repartioning will delete all data. BACKUP! It also deletes the legacy internal EMMC partition (which was 1GB big) in case this was not yet done.
NOTE2: If repartitioning fails, please adb into the device and post /tmp/repartition.log to the forum here.
Then you can flash the CM 14.1 images and gapps as usual (e.g. with adb sideload).
Once a version is installed (and all bugs fixed), you will be able to use CM Updater
Settings->About tablet->CyanogenMod updates->Refresh
Building:
The CM wiki explains that here: http://wiki.cyanogenmod.org/w/Build_for_acclaim
Returning to stock BN firmware:
If you have installed above rom and the recovery and you really hate it and want to go back to stock, you first have to repartition to come back to the original repartition layout. This is currently not documented.
You may wish to try to flash the original acclaim_update.zip from BN. You have to unzip that file and edit META-INF/com/google/android/updater-script. Drop the first two lines here:
assert(getprop("ro.product.device") == "blaze" ||
getprop("ro.build.product") == "blaze");
Zip the package again. Then go to recovery, flash the zip, wipe, and reboot.
Support:
For any issues encountered, please post into this forum, but add steps to reproduce and dmesg, logcat and audit.log information. If you don't know what this is or how to get them, try to find that out first before posting here.
Thanks:
hashcode, ntemis, kuzma30, fattire, mik_os, and many others that contribute to cyanogenmod and especially this version.
kuzma30 - great kernel job
hashcode - we have reused lots of your work and effort for the various omap devices (esp kindle fire). It is thanks to you mainly that we are now official CM device. Also many thanks for the L bringup help.
mik_os - great touchscreen firmware flasher and other efforts
fattire - for helping us everywhere he can
ntemis - thanks for giving so much energy to this - esp for 4.4 and L I have copied lots of things from you
CM community (stargo, david marble, etc.) - thanks for replying to all my questions!
DISCLAIMER:
- update the recovery (see above) if you come from older versions - otherwise you'll see funny error messages when installing zip
- It is possible that you need to wipe your device. I did not do that, but...
- You must flash your own gapps. It can be found somewhere....
Known issues:
- the touchscreen firmware flasher doesn't work on N. Use CM11 to flash it first.
- The system is altogether not really the fastest thing on earth
Get it soon from:
http://download.cyanogenmod.org/?device=acclaim
Get an UNOFFICIAL build now from here:
https://basketbuild.com/filedl/devs...ry/cm_acclaim_cm-14.1_13112016_UNOFFICIAL.zip
8GB model: I do not have such a device and can thus not test anything. The re-partitioning should also work, as I have created the last partition userdata with the "everything that's left in terms of size".
If you feel adventurous, please let me know if the 8GB model works as well, but it's currently not supported.
Oh my god, dude, you're still going
It's the tablet that won't die!
I flashed the recovery recovery-repartition-acclaim-cm14.1-UNOFFICIAL.img and I don't get any menu under advanced.
I ran repartition.sh in an adb shell under recovery. The partitions resized nicely.
I reflashed twrp 3.02 and failed to recover my backup. Data and cache were formatted as ext4. I fixed that in twrp and recovered my backup. I then failed to flash a rom. It errored immediately. I think the system was the wrong size. Testing with smaller (but increasing) system partition sizes shows that your defaults are correct. System is exactly 2G. I have no idea why I had troubles. I probably slipped a bit in my non-eec ram.
Very good work. I don't know why the repartition.sh script isn't run from the recovery. That is built from a slightly different device tree. I can post repartiton.log if you need it. It looked fine.
This is actually a useable tablet with this rom. Encore and, I assume the 8gb acclaim, just haven't worked well since cm-11 since they only have 512M ram. You have done a good job keeping this alive.
drmarble said:
I flashed the recovery recovery-repartition-acclaim-cm14.1-UNOFFICIAL.img and I don't get any menu under advanced.
I ran repartition.sh in an adb shell under recovery. The partitions resized nicely.
I reflashed twrp 3.02 and failed to recover my backup. Data and cache were formatted as ext4. I fixed that in twrp and recovered my backup. I then failed to flash a rom. It errored immediately. I think the system was the wrong size. Testing with smaller (but increasing) system partition sizes shows that your defaults are correct. System is exactly 2G. I have no idea why I had troubles. I probably slipped a bit in my non-eec ram.
Very good work. I don't know why the repartition.sh script isn't run from the recovery. That is built from a slightly different device tree. I can post repartiton.log if you need it. It looked fine.
This is actually a useable tablet with this rom. Encore and, I assume the 8gb acclaim, just haven't worked well since cm-11 since they only have 512M ram. You have done a good job keeping this alive.
Click to expand...
Click to collapse
I re-downloaded and flashed the recovery from here: https://basketbuild.com/filedl/devs...ery-repartition-acclaim-cm14.1-UNOFFICIAL.img
and I can see when I enter the Advanced menu, a new menu entry: Repartition Nook Tablet for Android N.
Strange.
Chris
Building CM14?
chrmhoffmann said:
...
Building:
The CM wiki explains that here: http://wiki.cyanogenmod.org/w/Build_for_acclaim
...
Click to expand...
Click to collapse
CM14 on this device!? Awesome!
Is there a special local manifest that I need to build this?
It has been a while, but for CM13, I did this:
rm -f $CROOT/.repo/local_manifest.xml
echo '<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_bn" path="vendor/bn" remote="github" revision="cm-13.0" />
</manifest>' > $CROOT/.repo/local_manifest.xml
repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0
repo sync -j1Can I just change cm-13.0 to cm-14.1?
Also, is this a resource pig like building CM14 for the NookHD+? I had to give my virtual machine 12GB RAM and 4 CPUs because of the new toolchain, notably Jack.
And thanks for the great work!!
== EDIT ==
I forked my CM13 script, made the changes above, and got a build! cm-14.1-20161119-UNOFFICIAL-acclaim.zip
Unfortunately, it wouldn't flash and gave an ERROR 7 error code. :crying:
I installed and flashed with TWRP 3.0.1, and was able to successfully re-flash CM13. I'll try building and installing CM14 again in a week or so.
Question, do I have to re-partition if I don't intend to install Gapps?
I flashed "recovery-repartition-acclaim-cm14.1-UNOFFICIAL.img" and then entered into it. After I did "Advanced->Reboot recovery". And when I had reboot into the recovery I got "No command" on the black screen. Help me.
AlexBreems said:
I flashed "recovery-repartition-acclaim-cm14.1-UNOFFICIAL.img" and then entered into it. After I did "Advanced->Reboot recovery". And when I had reboot into the recovery I got "No command" on the black screen. Help me.
Click to expand...
Click to collapse
I did the repartitioning on a 16GB also, and got the same result. rebooting into recovery and get the "no command"prompt only.
I rebooted to cyanoboot, started fastboot, and flashed a TWRP recovery
using the command "fastboot flash recovery twrp-3.0.2-0-acclaim.img" (no quotes)
partitons didn't appear formatted so I formatted /data f2fs , /cache ext4 and /system /ext4
haven't tried installing the rom yet, will do in a minute
partitions look like this after formatting
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 333.9M 20.0K 333.9M 0% /dev
tmpfs 333.9M 28.0K 333.9M 0% /tmp
/dev/block/platform/omap/omap_hsmmc.1/by-name/bootdata 47.2M 4.5K 47.2M 0% /bootdata
/dev/block/mmcblk0p9 1007.9M 17.3M 990.6M 2% /cache
/dev/block/mmcblk0p8 2.0G 35.0M 1.9G 2% /system
/dev/block/mmcblk0p10 11.1G 652.0M 10.4G 6% /data
/dev/block/mmcblk0p10 11.1G 652.0M 10.4G 6% /emmc
I'll try an 8GB tomorrow
!!! RENAME THE ATTACHED ZIP FILE TO IMG - its not a ZIP !!!
mikeataol said:
I did the repartitioning on a 16GB also, and got the same result. rebooting into recovery and get the "no command"prompt only.
I rebooted to cyanoboot, started fastboot, and flashed a TWRP recovery
using the command "fastboot flash recovery twrp-3.0.2-0-acclaim.img" (no quotes)
partitons didn't appear formatted so I formatted /data f2fs , /cache ext4 and /system /ext4
haven't tried installing the rom yet, will do in a minute
partitions look like this after formatting
Click to expand...
Click to collapse
You beat me to it. I flashed TWRP changed the partition format for /cache /data and /system to f2fs. I then changed the partition format for /cache /data and /system to ext4. I then flashed the ROM from within TWRP. I was able to boot successfully after that.
I have flashed "cm-13.0-20161113-NIGHTLY-acclaim-recovery.img" and then by the new recovery I have flashed "cm-14.1-20161119-NIGHTLY-acclaim.zip". Profit!
All files are located here https://download.cyanogenmod.org/?device=acclaim
Hi Chris,
after flashing the nightly, just providing feedback on things I noticed
Performance is very good.
Like many CM13 roms, if you've loaded GAPPS, initial setup doesn't like skipping through actually using WiFi and providing an account... It gets into a loop until you provide those things.
Screen artifacts seem pretty persistent, tried changing things like turning off LiveDisplay, developer settings for Disable HWoverlays and ForceGPUrendering didn't seem to have any effect.
CMBugreporter app gives random FC. MTPHost gives random FC (Ive seen this on other CM based recent roms as well...)
WiFi went into a "no Internet" randomly more than once, (no issues on other tablets and computers on the same LAN at the same time.)
I'm not wild about the partition sizes chosen with the repart script (1GB for cache , 2GB for system) , seems like they could be smaller, especially cache.
Didn't look at the whole rom in great detail, really... just noting what people might expect if they try this rom.
Thanks for keeping it alive and in the mainstream CM loop!
M
Working build!!
Great work @chrmhoffmann, @drmarble et al!
I reverted the partition sizes back to the CM13 sizes and built a working ROM without needing re-partitioning. My tablet only has two or three apps and is (importantly) used as my "clock radio".
I'll be back! ... for "O"
Thanks.
chrmhoffmann said:
8GB model: I do not have such a device and can thus not test anything. The re-partitioning should also work, as I have created the last partition userdata with the "everything that's left in terms of size".
If you feel adventurous, please let me know if the 8GB model works as well, but it's currently not supported.
Click to expand...
Click to collapse
Hi Chris,
It does install and run on the 8GB model, although it is very laggy and slow. I tried as much as one could to try to speed it up but its not nearly as usable as on the 16GB.
The repart script behaved the same way, got a "no command" on reboot to recovery and had to format the partitions before installing.
I did format /cache and /data f2fs on the 8GB install... I'll try ext4 and see if it behaves any better.
I did not notice the screen artifacts using the 2nd 1122 build that's on the CM download site....
Thanks again.
mikeataol said:
Hi Chris,
It does install and run on the 8GB model, although it is very laggy and slow. I tried as much as one could to try to speed it up but its not nearly as usable as on the 16GB.
The repart script behaved the same way, got a "no command" on reboot to recovery and had to format the partitions before installing.
I did format /cache and /data f2fs on the 8GB install... I'll try ext4 and see if it behaves any better.
I did not notice the screen artifacts using the 2nd 1122 build that's on the CM download site....
Thanks again.
Click to expand...
Click to collapse
I just ran into a similar issue but with the 16gb version. I fastboot flashed my recovery back to TWRP 2.8.7.0 and formatted /cache and /data to ext4 and it seems to be working now.
The link for the partitioning recovery seems to be down, does anybody have an alternate link? Will the official recovery get the partitioning function added?
Thanks!
lipps said:
The link for the partitioning recovery seems to be down, does anybody have an alternate link? Will the official recovery get the partitioning function added?
Thanks!
Click to expand...
Click to collapse
the download site is showing "unplanned maintenance, so here ya go...
rename this fie to .IMG... it's not a ZIP (renamed to allow uploading here)
mikeataol said:
the download site is showing "unplanned maintenance, so here ya go...
rename this fie to .IMG... it's not a ZIP (renamed to allow uploading here)
Click to expand...
Click to collapse
Thanks for the file! I changed the extension to .img, then flashed it to recovery using TWRP. When I reboot into recovery, I just get a message in very small text that says "No command"and every few seconds the screen flashes to a mottled white screen, then right back to "No command".
I also tried flashing the image with fastboot, same results. Any idea what I'm doing wrong?
lipps said:
Thanks for the file! I changed the extension to .img, then flashed it to recovery using TWRP. When I reboot into recovery, I just get a message in very small text that says "No command"and every few seconds the screen flashes to a mottled white screen, then right back to "No command".
I also tried flashing the image with fastboot, same results. Any idea what I'm doing wrong?
Click to expand...
Click to collapse
If you read the posts in this short thread , you will see others with the same result.
you need to flash TWRP now and format the partitions in TWRP . They have been resized, but not formatted
you should reboot to recovery after formatting , and before flashing the rom and gapps
mikeataol said:
If you read the posts in this short thread , you will see others with the same result.
you need to flash TWRP now and format the partitions in TWRP . They have been resized, but not formatted
you should reboot to recovery after formatting , and before flashing the rom and gapps
Click to expand...
Click to collapse
Thanks for continuing to help me out Mike. Do I need to re-partition using ADB, or does TWRP have that functionality? If it does, I don't see it.
I found this post about re-partitioning using ADB, is it something close to what I need to do?
http://forum.xda-developers.com/showpost.php?p=22157605&postcount=25
Thanks!
[Guide] Samsung Galaxy S2 i9100 Android 7.1 Nougat/Lineage OS 14.1
[Guide/Tutorial/Howto] Samsung Galaxy S2 i9100 Any version to Android 7.1 Nougat without PC
This detailed step-by-step guide helps you transform your Samsung Galaxy S2 i-9100/i-9100P to a powerful one with Android 7.1 Nougat.
Verify your phone is i9100 or i9100P before going further : when you Power on phone, it is written Galaxy SII i9100.
The flashing of recovery is a bit tricky but none of the S2 I had were recognised by the PC. So this tutorial is PC free.
If your S2 is recognised by PC, it's easier to flash directly TWRP recovery using Odin or Heimdall https://forum.xda-developers.com/showpost.php?p=75002977&postcount=343
CHANGELOG OF TUTORIAL
v10. Updated pack with TWRP 3.3.1-0
v9. Updated to Unofficial LOS 14.1
v8. Removed Dorimanx kernel (not maintained)
v7. Added Google Play certification (use instructions with my v5 pack below)
v6. Switched to Dorimanx kernel, swteaks, enhenced tutorial thx to feedback, introduced md5 signatures, Stweaks included
v5. Overclock and optimize
v4. Simpler repit, 2 profiles for repit included
v3.5. More custom partitions, kernel for Android N 1.3
v3. Moved to Lineage OS 14.1, Skyline custom kernel, TWRP 3.1 by the.gangster
v2. Added latest repit, added walkthrough for possible errors
v1. Initial release
1 ) DOWNLOAD ---------------------
- djibe Galaxy S2 i9100 pack (53 MB) v5 : http://bit.ly/GalaxyS2djibepackv5
(contains Philz Touch recovery + kernel Lanchon IsoRec CM13 + the.gangster IsoRec TWRP 3.3.1-0 recovery + lanchon repit djibe edit standard or prefered + Su for LOS 14.1 + Samsung drivers).
- ROM Unofficial Lineage OS 14.1 for GalaxyS2 i9100 : https://androidfilehost.com/?w=files&flid=302540&sort_by=date&sort_dir=DESC
Or AOKP : https://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-aokp-rom-t3606915
- OpenGApps ARM 7.1 pico (alternatives: Pico, Micro) : https://opengapps.org/?arch=arm&api=7.1&variant=pico
- a microSD card. Copy Philz Touch recovery + kernel Lanchon IsoRec CM13 + the.gangster IsoRec TWRP 3.3.1-0 recovery + lanchon repit djibe edit standard or prefered + Su for LOS 14.1 AND THEIR RESPECTIVE md5 files from my pack on microSD card and insert it in phone.
- Charge phone to 100 %
WARNING. Read carefully the sentences starting with ###.
### It will not work if your phone is encrypted. Uncrypt it before starting this tutorial.
### This tutorial works without a PC. So it will work if (like me) you get "Unknown USB device error" message when plugging phone in Windows.
### Warranty is now void.
### Later in this tutorial, if you get error : "Failed to mount */data* (No such device)", just reformat Data partition to Ext4 (Using lanchon-repit's script or TWRP recovery).
2 ) BACKUP DATA -------------------
Install Samsung drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use an app like Backupyourmobile to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
3 ) FLASH RECOVERY, KERNEL AND RE-PARTITION----------------
We gonna repartition phone to reduce an unused preload partition of 512 Mo (stored Samsung updates that no more exist).
We gonna increase system partition to 1 GB so Android 7.1 and Gapps have enough space.
We gonna increase data partition so you can have all the apps you like.
ALL YOUR DATA WILL BE LOST.
FLASH RECOVERY FROM STOCK RECOVERY ----
Shut down phone.
Power it back on in recovery mode : Use Volume+ + Home + Power buttons and release them when you see Galaxy S2 logo.
### Alternative and easier process if your S2 can be recognized by PC using Heimdall : https://forum.xda-developers.com/showpost.php?p=75002977&postcount=343
Then wait till the recovery launches.
### If you already have a custom recovery, go to the mark -!-!- below.
Using default recovery, use volume buttons to navigate and power to confirm,
install zip -> choose Philz_touch_6.48*.zip and install it.
When its done, shut down phone, restart in recovery mode. You are now in the Philz touch recovery.
### If it fails, you need to install CWM recovery using Odin software and SGS2 in Download mode.
### Use a good tutorial for Odin and SGS2 i9100 recovery flashing.
### Download CWM for Odin : https://www.androidfilehost.com/?fid=95916177934516900
### Once finished, continue operations below as if you had Philz recovery.
In Philz touch recovery (or your recovery -!-!-) : go to Wipe -> format /cache and format /system partitions.
Then back to install zip -> Flash kernel-lanchon*.zip (FLASH IT OR TWRP RECOVERY WON'T LAUNCH AND PHONE WILL BE BRICKED),
then flash recovery recovery-the.gangster-IsoRec-TWRP-3.1.0-0-i9100.zip.
Reboot phone to recovery again, it is now TWRP 3.1.0-0 Recovery !!!
Swipe to unlock filesystem.
Check never show this screen during boot again and swipe again.
In TWRP, go to Backup -> select Boot, System, Data,
Tap select Storage and select External storage,
then Swipe to Backup.
Backup is located on your microSD in the TWRP folder.
(To have latest TWRP recovery, go to Install > Select TWRP 3.1.1-0.img and swype to flash).
### Don't flash repit files if you don't have a TWRP recovery
### 2 MAIN CONFIGS TO REPARTITION :
- For standard config, just use the djibe-standard-repit*.zip included in my archive, you'll have :
1GB system, 6GB data (for apps), max internal storage (photos, temp files) and minimal preload (useless partition used for OTA offical updates).
- My PREFERED version is djibe-prefered-repit*.zip :
1GB system, 2GB Internal storage (limited size for photos and files because who takes photos with SGS2 ?), max data (about 11,5 GB for apps), minimal preload (useless partition).
### And a failproof repit one. If you get flash errors with repit files above, use this one.
- For more custom partitions, ask us in a post what partition sizes you want.
### Let the lanchon*.zip filename AS IS because the filename gives the instructions for the repit script. Lanchon is smart !
Go back to TWRP Home screen,
Plug phone to charger.
Tap go to Install, select lanchon-VERSIONYOUWANT-djibe-repit*.zip from your microSD (if file not seen, tap Select storage -> External-storage),
then Swipe to flash. There is an error, files have been copied to /tmp folder. It is normal !
Go back to Install -> Select Storage -> Internal Storage, OK.
Now tap on : (Up A Level),
scroll down and enter the "tmp" folder,
### If you use another PIT file to repartition (not mine -djibe-version), plug phone to Power source (not PC !) or you could hard brick your device.
tap on lanchon-VERSIONYOUWANT-djibe*.zip and Swipe to flash.
### never connect phone to PC during repit !!!
Let it process for 2 minutes.
4 ) Wipe partitions
INFO : F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and Ext4 is still faster.
Format has been done with repit. No need to manually format anymore.
Go to Wipe -> Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage then Swipe to Wipe, go back to TWRP Home.
5) INSTALL ROM, GAPPS AND ROOT
Still under TWRP Home screen -> go to Install zip and set Storage to External-Storage.
We need to install files 1 by 1.
Select lineage-14.1-*.zip and Swipe to flash,
Then select addonsu-*.zip (this is the Root) and Swipe to flash,
### You get this error : Updater process ended with signal: 4, Error installing zip file '/sdcard/Download/addonsu*.zip', don't care, root is correctly installed.
then open_gapps-arm-7.1*.zip, and Swipe to flash,
### If you are using ResurrectionRemix, don't flash any custom kernel at all !
Then wipe cache/dalvik,
then reboot system.
Wait for 15 minutes while Android starts for the first time.
6 ) ROOT ACCESS
Once in Android, open the Settings menu, select "About Phone".
Go to Settings -> About -> Hit 7 times on the build number, go back,
Go to the Developer options menu, root access -> activate ADB+apps
and Lower activate Local Terminal.
7) CALIBRATE BATTERY
In Google Play Store, download App Battery Calibration (from IMobS Ltd).
Launch the App.
Confirm root acces.
Plug tab and wait till charge hits 100%, then hit BATTERY CALIBRATION and unplug it.
8) You can use Backupyourmobile to restore data,
you can use GPS Status & Toolbox app to enhance GPS fix.
Enjoy,
djibe
THANKS --------------
Teams of : TWRP, Lineage OS, the.gangster, Lanchon, Resurrection remix, Philz, Skyline, MigoMujahid
Hi, i tried that, the repit file i isntalled was the one that has your name. The whole process went ok, except for the install. please check the image for more info.
I formated cache and data partition back to ext4 and everything went fine. Now I have ressurection remix 7.1 ROM.
hi octaviojss:
- Why did you flash my PIT, cause you got the WARNING. If you got "ERROR: 1 Fatal: file system errors in partition #11 'sdcard' (UMS) could not be fixed error" ?
- What happens if you go back to Wipe -> Advanced Wipe
And reformat every partition (F2FS for cache and data and ext4 for system and internal storage) ?
Keep in touch
Why did you have your PIT file there in first place, if it wasnt needed? I installed it because it was more recent. Anyway, as said, when i reformated the cache and data partitions back to ext4 file format i was able to install the rom smoothly and flawlessly.
Glad you did it !
For the PIT file it doesn't change much, but the original lanchon PIT moves data during partition resize, mine erases data.
Enjoy
I get an error "E: error in /tmp/sideload/package.zip" Please help me fix this
Aly Rezz said:
I get an error "E: error in /tmp/sideload/package.zip" Please help me fix this
Click to expand...
Click to collapse
Hi Aly, at which step are you ?
Did you try reflashing the PITs from the SDcard and moving back to Internal stroage main folder ?
Did you authorize TWRP to mount system partition ?
djibe89 said:
Hi Aly, at which step are you ?
Did you try reflashing the PITs from the SDcard and moving back to Internal stroage main folder ?
Did you authorize TWRP to mount system partition ?
Click to expand...
Click to collapse
I wiped my phone and flashed the Philz Touch Recovery Zip. I got this error while flashing it...
Aly Rezz said:
I wiped my phone and flashed the Philz Touch Recovery Zip. I got this error while flashing it...
Click to expand...
Click to collapse
So you've wiped everything under stock recovery ? It needs to be done later once Philz touch is working !
So, we'll try flashing recovery in Download Mode (Home + Power + Volume-), use Odin to flash Philz Touch recovery in .tar format (in AP/PDA section of Odin).
1 - Download Philz Touch recovery in .tar format :
https://mega.nz/#F!oZ1QDDbC!Ko20UNhowwIlXLVFjJsyKw (it doesn't load for me right now)
+ Odin 3.07 (my pack for i9300) : http://bit.ly/2hqiWsP
2 - From my tutorial here, execute the 3rd chapter with Odin :
https://forum.xda-developers.com/galaxy-s3/help/guide-tutorial-samsung-galaxy-s3-i9300-t3491788
(do not flash TWRP inside my i9300 Archive)
3 - Once flash of Philz touch recovery is done, reboot to recovery and continue further steps.
good to have a full tutorial
Glad it pleases you. Hope your S2 is now fully unleashed
Any constructive comment is welcome to enhence the tutorial.
djibe89 said:
So you've wiped everything under stock recovery ? It needs to be done later once Philz touch is working !
So, we'll try flashing recovery in Download Mode (Home + Power + Volume-), use Odin to flash Philz Touch recovery in .tar format (in AP/PDA section of Odin).
1 - Download Philz Touch recovery in .tar format :
https://mega.nz/#F!oZ1QDDbC!Ko20UNhowwIlXLVFjJsyKw (it doesn't load for me right now)
+ Odin 3.07 (my pack for i9300) : http://bit.ly/2hqiWsP
2 - From my tutorial here, execute the 3rd chapter with Odin :
https://forum.xda-developers.com/galaxy-s3/help/guide-tutorial-samsung-galaxy-s3-i9300-t3491788
(do not flash TWRP inside my i9300 Archive)
3 - Once flash of Philz touch recovery is done, reboot to recovery and continue further steps.
Click to expand...
Click to collapse
Still doesn't work. It's stuck at " Nand Write Start!!"
Try Odin 1.3
or this "Tried to do a rollback from official 4.4.2 to official 4.1.2 via Odin.
Since the new official bootloader doesn't allow rollback procedures, I got the missing magic string error and the NAND write fail at Odin.
The tablet bricked, not even showing Samsung Note 10.1 logo. I could only access to ODIN mode, not recovery even. *YIKES*
After a day and a half trying to recover it, I removed the SIM card, the SD card and I loaded the Samsung Stock recovery file via ODIN, then rebooted. I got as far as the Samsung logo which was an improvement compared to what I had. Then I proceeded to reload the 4.4.2 firmware (INU-N8000XXUDNE6) and rebooted the device. Went into recovery mode, restored factory defailts and, voilá!
It is working now on 4.4.2, though it is not the Spanish firmware it shoud be, at least the tablet is functional. "
Hi.
Oh boy I was happy when I found this complete package with all files in a zip. All other places the files are missing or you "can't find them".
And oh boy I was unhappy when I couldn't install the first file.
My phone is a SGS2 Modelnumber GT-I9100 bought in Sweden a few mounth after the model was released.
So I guess the instructions on this page should work for me?
I've rooted my phone with CWM-SuperSU-v0.97.zip and verified with a root checking app from the store. Otherwise it's only updated to the latest Andorid 4.1.2 from Samsung. The phone is working fine with the installed Android version.
So when I choose to install "Philz_touch_6.48*.zip" the following is printed out:
################
PhilZ Touch Recovery
Full Touch CWM Based
+
Advanced Features
Phone i9100
################
This package is for 'galaxys2.i9100.GT-I9100.GT-
I9100M.GT-I9100P,GT-I9100T,SC-02C devices; this
is a ''.
E:Error in /tmp/sideload/package.zip
(Status 7)
What am I doing wrong here? Have I missed doing something obvious? Do I need to install something more before I use your guide?
BR
Tobbe
Hello,
you are rooted.
So, in Android, what happens if you download the app ROM Manager : https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager ,
grant Root access for the app,
Flash latest ClockworkMod Recovery for i9100,
reboot to recovery, reflash Philz Touch ?
Hi.
I tried to do that you wrote. Didn't seem to work with:
GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9.tar
I downloaded Odin and flashed it instead. Now I got this yellow triangle with an exclamation mark in and phone didn't boot into Android.
Got very worried but I went into recovery mode and voila ClockworkMod was running
After that I followed your instruction. Up to "Format to F2FS". I got errors so I changed back to EXT4 and continued.
Installed CM13 with no problem and got very glad so I forgot step 6-8. Will do them in a few days.
Thank you very much for this guide and zip-archive.
It's actually my daughter who will get the updated phone. She is also very happy
BR
Tobbe
PS. One more thing, is it possible to get rid of the yellow triangle with an exclamation mark in? (only appears at atart up screen) DS.
Glad you did it.
It is strange how bugs can be different for everyone !
Triangle can be removed but it seems rather dangerous for a small benefit : https://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
I have no courage to do it after all these tricky steps we wen't by !
See you,
Thanks djibe. I wanted to flash to CM13 from stock rom, so your guide was really helpful.
I did run into two issues, and want to share how I got around them:
1. I got the "Status 7" problem when trying to flash Philz_touch_6.48*.zip. So instead I flashed the relevant ZIP file from "forum.xda-developers.com/galaxy-s2/development-derivatives/philz-cwm6-stock-kernel-cwm6-root-exfat-t1877270" from stock recovery first. This installed a custom recovery. Then I flashed Philz_touch_6.48 from the custom recovery.
2. After formatting /cache and /data to F2FS, installing CM13 failed. So instead I kept /cache and /data as EXT4 and completed the installation according to the rest of the guide. After rebooting and completing the CM13 Android setup, I redid the installation from step 4 of your guide onwards and F2FS worked this time. I should mention though that before formatting /cache and /data to F2FS, I also repartitioned with a newer repit file from lanchon's github (and increased data to 4G), so I don't know if this had an effect as well.
Hopefully this helps others facing the same problems. I should warn though that this is my first time attempting absolutely anything like this, so please take all this with caution. Your mileage may vary!
S2andCounting said:
Thanks djibe. I wanted to flash to CM13 from stock rom, so your guide was really helpful.
I did run into two issues, and want to share how I got around them:
1. I got the "Status 7" problem when trying to flash Philz_touch_6.48*.zip. So instead I flashed the relevant ZIP file from "forum.xda-developers.com/galaxy-s2/development-derivatives/philz-cwm6-stock-kernel-cwm6-root-exfat-t1877270" from stock recovery first. This installed a custom recovery. Then I flashed Philz_touch_6.48 from the custom recovery.
2. After formatting /cache and /data to F2FS, installing CM13 failed. So instead I kept /cache and /data as EXT4 and completed the installation according to the rest of the guide. After rebooting and completing the CM13 Android setup, I redid the installation from step 4 of your guide onwards and F2FS worked this time. I should mention though that before formatting /cache and /data to F2FS, I also repartitioned with a newer repit file from lanchon's github (and increased data to 4G), so I don't know if this had an effect as well.
Hopefully this helps others facing the same problems. I should warn though that this is my first time attempting absolutely anything like this, so please take all this with caution. Your mileage may vary!
Click to expand...
Click to collapse
Thank you very much for these tips that will surely help others.
Can you send me the direct link to the Philz recovery that was successful for you ?
I'm upgrading my tutorial with your stuff, and making it simpler with a new custom repit file.
Keep in touch
Hello, i am in need of your help
first off, yes, i have tried and am using the newest twrp and now also orangefox.
Im also using the mido rom for my mido phone, thats why its so puzzling to me.
I came from a Lineage 15.1 build of mid September and wanted to do a clean installation of the newest 15.1 nightly.
So i formatted clean via twrp and transferred the newest zip of 15.1. It failed and gave me an E1001 and Error 7
I also tried some older builds of this month to no avail , giving me the same errors.
Online answers told me to update my twrp, so i did that, but none of them worked so far.
At this point i have a working fastboot and recovery but i cant manage to install a rom anymore, which is very odd to me.
When trying to install any rom, i usually get this log:
Installing zip file `/sdcard/lineage-15.1-20190102-nightly-mido-signed.zip`
Checking for Digest file...
Skipping Digest check: no Digest file found
Detecting Current Package
- Detected Standard Package
Support MIUI Incremental package status: Disabled
Target: xiaomi/mido/mido:7.0/NRD90M/V8.5.4.0
NCFMIED:user/release-keys
detected filesystem ext4 for /dev/block
bootdevice/by-name/system
Patching system image unconditionally...
E1001: Failed to update system image
Updater process ended with ERROR: 7
Error installing zip file `/sdcard/lineage-15.1-20190102-nightly-mido-signed.zip`
Updating partition details...
Failed to mount `/system` (Invalid argument)
...done
Please help :crying:
shinzo_ningen said:
Hello, i am in need of your help
first off, yes, i have tried and am using the newest twrp and now also orangefox.
Im also using the mido rom for my mido phone, thats why its so puzzling to me.
I came from a Lineage 15.1 build of mid September and wanted to do a clean installation of the newest 15.1 nightly.
So i formatted clean via twrp and transferred the newest zip of 15.1. It failed and gave me an E1001 and Error 7
I also tried some older builds of this month to no avail , giving me the same errors.
Online answers told me to update my twrp, so i did that, but none of them worked so far.
At this point i have a working fastboot and recovery but i cant manage to install a rom anymore, which is very odd to me.
When trying to install any rom, i usually get this log:
Installing zip file `/sdcard/lineage-15.1-20190102-nightly-mido-signed.zip`
Checking for Digest file...
Skipping Digest check: no Digest file found
Detecting Current Package
- Detected Standard Package
Support MIUI Incremental package status: Disabled
Target: xiaomi/mido/mido:7.0/NRD90M/V8.5.4.0
NCFMIED:user/release-keys
detected filesystem ext4 for /dev/block
bootdevice/by-name/system
Patching system image unconditionally...
E1001: Failed to update system image
Updater process ended with ERROR: 7
Error installing zip file `/sdcard/lineage-15.1-20190102-nightly-mido-signed.zip`
Updating partition details...
Failed to mount `/system` (Invalid argument)
...done
Please help :crying:
Click to expand...
Click to collapse
Try this article, the problem number 2 in this article matches with yours
https://www.google.co.in/amp/s/www.yaabot.com/8206/4-problems-flashing-custom-roms-solutions/amp/
Bhanu_p_mishra said:
Try this article, the problem number 2 in this article matches with yours
Click to expand...
Click to collapse
I already did this and it didnt work.
The problem was a either a wonky window adb driver or the usb cable used. It worked on a different computer and cable.
Is your issue solved? ?
i tried to install lineage 19 and 18 but both trials end with error.
I used this....(https://raw.githubusercontent.com/RaghuVarma331/changelogs/master/crossdevelopment/abcrins.txt)
Installation procedure for the roms which doesn't comes with gapps
==============
1. Boot in to twrp
2. Click on wipe
3. Select format data
4. Type yes
5. Reboot to bootloader
6. Boot in to twrp
7. Select wipe
8. Select advance wipe
9. Select all except sdcard
10. Swipe to wipe
11. Copy rom.zip
so far so good
12. Flash ROM.zip ---> Errors applying update: 28 (Errror Code:: errors installing ZIP '/sdcard/lineage-18.1-20220203.zip
trying to install with ZIP signature verification: verifiction failed! Error installing.....zip.
happens with lineage 18 and 19.
i like to finish the other steps and need help.
I also tried to sideload the Rom without luck.
last steps to finish
13. Change slot , reboot to twrp again , flash opengapps.zip
14. Select wipe
15. Select advance wipe
16. Select all except system vendor SD card and swipe to wipe
17. Reboot system
today i tried this to get this phone running on lineage
adb reboot recovery
black lineage recovery screen shows
Version 19.0 (20211212)
active slot: b
(seems as an installation left did somethin right??)
I thought to try an update from ADB with the same versions cause my several installations before ended with the error shown above or did not boot into lineage after installation.
results:
1. E: emulated failed to bind mount /mt/staging/emulated/media/0 on /storage/emulated: No such file or directory
-> so i mounted /mnt/system (i am not sure what i am doing here...)
2 . updating again via adb sideload:
supported api: 3
finding update package...
verifying update package...
update package verification took 54 s (result 0)
Installing update....
E: package is for product CTL_sprout but expected Crystal
same result with
lineage-19.0-20211212-UNOFFICIAL-Crystal.zip
lineage-18.1-20210816-UNOFFICIAL-Crystal.zip
Anyone with a hint for me ?
thx
Nokiabilly said:
today i tried this to get this phone running on lineage
adb reboot recovery
black lineage recovery screen shows
Version 19.0 (20211212)
active slot: b
(seems as an installation left did somethin right??)
I thought to try an update from ADB with the same versions cause my several installations before ended with the error shown above or did not boot into lineage after installation.
results:
1. E: emulated failed to bind mount /mt/staging/emulated/media/0 on /storage/emulated: No such file or directory
-> so i mounted /mnt/system (i am not sure what i am doing here...)
2 . updating again via adb sideload:
supported api: 3
finding update package...
verifying update package...
update package verification took 54 s (result 0)
Installing update....
E: package is for product CTL_sprout but expected Crystal
same result with
lineage-19.0-20211212-UNOFFICIAL-Crystal.zip
lineage-18.1-20210816-UNOFFICIAL-Crystal.zip
Anyone with a hint for me ?
thx
Click to expand...
Click to collapse
You need to use the Nokia Repartition Tool. Set to 3.5GB.
Nokia Repartition Tool
[CLOSED][TOOL][8.1.0/9.0/10.0] Nokia Repartition Tool [DRG][2020/11/21]
Hello, if i use NokiaRestoreTool to go back to stock, is the partition size reset to initial 2.5gb or will it stays 3.5gb ? Yes. Will revert back to 2.5G/500MB after back to stock.
forum.xda-developers.com
kousuke5555 said:
You need to use the Nokia Repartition Tool. Set to 3.5GB.
Nokia Repartition Tool
[CLOSED][TOOL][8.1.0/9.0/10.0] Nokia Repartition Tool [DRG][2020/11/21]
Hello, if i use NokiaRestoreTool to go back to stock, is the partition size reset to initial 2.5gb or will it stays 3.5gb ? Yes. Will revert back to 2.5G/500MB after back to stock.
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks,
it works.
Nokiabilly said:
Thanks,
it works.
Click to expand...
Click to collapse
I know this thread is a bit old but how to use the tool? I do not fully understand it. I have a Nokia .7.1, always get the error 28 and can not do anything. And the Nokia Repair Tool hangs?! What exactly do I have to do to make it work?!