After flashing the newest build of LineageOS and rebooting into the Bootloader I am stuck on the "Firmware Update" screen. Please help.
A year ago I successfully installed LineageOS 14.1 on my LG G2 Mini. Today I flashed the most recent build of LineageOS onto my phone. I followed the steps as mentioned on https://forum.xda-developers.com/g2-mini/development/unofficial-lineageos-14-1-t3529585:
1. Download the ROM zip and move it to your sd-card
2. Reboot into recovery
3. Make a backup
4. Wipe System, Data and Cache
5. Flash the ROM zip
6. Optional: Install Google appsAfter rebooting I arrive in TWRP again and I select "Reboot - Bootloader". The phone reboots but enters a screen with the following text:
Firmware Update
Do not unplug the USB connection until the process is complete.
Progress bar at 0%.
I still can reboot into TWRP by selecting "Reboot - System", but selecting "Reboot" - "Bootloader" brings me to the "Firmware Update" screen again.
So now I am stuck. Please help.
[SOLUTION]
I found the solution!!!!! Searching the forums finally brought me to https://forum.xda-developers.com/tmo...puter-t2873386
Thanks @inshadesofgrey
Ok, so...
Why are you trying to reboot to the bootloader?
Why not just do a normal reboot?
TWRP Reboot
The TWRP Reboot screen has four options:
System
Power Off
Recovery
Bootloader
When I click "System" the phone reboots into TWRP. "Power Off" is not what I want. "Recovery" I do not want either. So "Bootloader" is the only obvious choice. But this sends me to the "Firmware Update" screen after reboot.
When I remove the battery and put it back in the phone boots into TWRP.
bjk268 said:
The TWRP Reboot screen has four options:
System
Power Off
Recovery
Bootloader
When I click "System" the phone reboots into TWRP. "Power Off" is not what I want. "Recovery" I do not want either. So "Bootloader" is the only obvious choice. But this sends me to the "Firmware Update" screen after reboot.
Click to expand...
Click to collapse
Reflash the ROM.
'System' is supposed to boot into the ROM.
Redownload rom, be sure to check control sum. Copy new file trough USB, your phone needs to be in TWRP for pc to recognize it.
Still no luck
Redownloading the ROM and reflashing it did not help. When rebooting into "System" the phone returns to TWRP again.
I checked the downloaded ROM using the keytool and the signature matches.
C:\Program Files\Java\jdk1.8.0_151\bin>keytool -list -printcert -jarfile "D:\Custom ROM\LineageOS\lineage-14.1-20171017-nightly-g2m-signed.zip"
Signer #1:
Signature:
Owner: CN=LineageOS, OU=LineageOS, O=LineageOS, L=Seattle, ST=Washington, C=US
Issuer: CN=LineageOS, OU=LineageOS, O=LineageOS, L=Seattle, ST=Washington, C=US
Serial number: e10413c773c3c54f
Valid from: Sat Jan 07 05:21:25 CET 2017 until: Wed May 25 06:21:25 CEST 2044
Certificate fingerprints:
MD5: F2:CA:AA:A7:2F6:34:FE:707:5C:41:43:6C:5E:14
SHA1: 9B:6D:F9:06:2A:1A:76:E6:E0:07:B1:1F:C2:EF:CB:EF:4B:32:F2:23
SHA256: 51:83:25:EF:7F:96:C01:19:4C:2E:85:6B:04:0D:63:61:66:FF:B8:46:71:7D:72:FA:87:F4:FA:E5:BE:7B:BB
Signature algorithm name: SHA1withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3
There may be an issue with the kernel.
Try flashing mine (-V- Kernel X)
The thread is at the G2 Mini Dev section.
No luck with the new kernel
Updating the kernel did not help either.
There is one red line during installation of the custom ROM: unable to recreate and-sec folder
Maybe this has something to do with my problem?
I cannot find a solution for the recreation of the and-sec folder.
bjk268 said:
Updating the kernel did not help either.
There is one red line during installation of the custom ROM: unable to recreate and-sec folder
Maybe this has something to do with my problem?
I cannot find a solution for the recreation of the and-sec folder.
Click to expand...
Click to collapse
That error has nothing to do with the problem. Please make sure you are using the latest twrp recovery.
Latest TWRP
I am using TWRP 3.0.2-0 and I cannot find a higher version for the LG G2 Mini. So still out of luck
I have tried installing the MOKEE ROM but in the end this had the same result of returning to TWRP after reboot:
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Device or resource busy
script succeeded: result was [1.000000]I don't know what caused the "Device or resource busy" error. Googling for suggestions did not help. The USB cable was disconnected so that could not be the problem.
After reboot again TWRP showed. I had hoped the custom ROM would appear but it did not.
[Solved]
I found the solution!!!!! Searching the forums finally brought me to https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
Thanks @inshadesofgrey
If you get into a recovery boot loop (where the phone keeps booting into the recovery, and not the OS), this will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.
Click to expand...
Click to collapse
bjk268 said:
I found the solution!!!!! Searching the forums finally brought me to https://forum.xda-developers.com/tmobile-lg-g3/general/fix-recovery-loop-twrp-computer-t2873386
Thanks inshadesofgrey
Click to expand...
Click to collapse
That means that there is an update file stuck in /cache
You should delete it.
Or, even better, wipe the /cache partition (as you should always do when flashing a ROM)
The cache was cleared as instructed
I cleared system, data and cache before every time I flashed the ROM so that could not have caused the TWRP loop.
I don't know what else could have caused this TWRP loop but the problem is solved now.
https://forum.xda-developers.com/g2...wrp-recovery-3-0-0-lg-g2-mini-t3311316/page10
Update recovery.
Related
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be a problem of ROM signing.
3. I installed "Minimal ADB and Fastboot" and "ZTE_Android_Driver", and run "adb devices" command.
Result: There is nothing under " List of devices attached", so I assume adb cannot see my phone. In Windows' Device Manager, it shows "Portable Devices" and lists drive I:\ and K:\ under it.
In summary, My phone is rooted. I might have damaged partition /data and /cache which causes the bootloop. I can still enter stock recovery mode. I have a stock ROM, but may not be properly signed.
Please suggest me on what I can do next.
Thanks.
sasawatd said:
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be a problem of ROM signing.
3. I installed "Minimal ADB and Fastboot" and "ZTE_Android_Driver", and run "adb devices" command.
Result: There is nothing under " List of devices attached", so I assume adb cannot see my phone. In Windows' Device Manager, it shows "Portable Devices" and lists drive I:\ and K:\ under it.
In summary, My phone is rooted. I might have damaged partition /data and /cache which causes the bootloop. I can still enter stock recovery mode. I have a stock ROM, but may not be properly signed.
Please suggest me on what I can do next.
Thanks.
Click to expand...
Click to collapse
can you return to stock using the mediatek flash tool and your stock firmware?(I'm not knowledgeable with MTK)
Lgrootnoob said:
can you return to stock using the mediatek flash tool and your stock firmware?(I'm not knowledgeable with MTK)
Click to expand...
Click to collapse
mediatek flash tool cannot see the phone either.
May be, if I can install CWM or TWRP, I might be able to update the stock rom with it. I've read elsewhere that If a phone can enter recovery mode, we can use fastboot in download mode. But I don't know how to install CWM or TWRP with fastboot.
sasawatd said:
mediatek flash tool cannot see the phone either.
May be, if I can install CWM or TWRP, I might be able to update the stock rom with it. I've read elsewhere that If a phone can enter recovery mode, we can use fastboot in download mode. But I don't know how to install CWM or TWRP with fastboot.
Click to expand...
Click to collapse
Driver issue?
Syntax for fastboot stuffz
try flashing:
Code:
fastboot flash recovery recovery.img
If flashing isn't working then try booting it directly
Code:
fastboot boot recovery.img
Hi,
I'm currently trying to install CyanogenMod onto my HTC One X+, but keep running into problems.
I unlocked the bootloader, and installed TWRP v2.8.7.0.
I went into recovery fine, and used "adb push" to push cm-11-20150906-NIGHTLY-enrc2b.zip onto the device and install it through TWRP.
I then tap "reboot" but it always tells me that "No OS Installed", and rebooting into the bootloader to flash the boot.img and erase the cache doesn't seem to fix this issue.
I've tried a few different versions of recoveries, like CyanogenMod's recovery, but still can't seem to get it to install any OS. Always just get stuck on the HTC logo.
Am I missing an important step, or something? Thanks for your time.
hmm...sounds correct. just try it again.
1. boot into bootloader
2. flash the boot.img from the zip you want to install (for cm11 i recommend to flash nik3rs kernel http://forum.xda-developers.com/showthread.php?t=2012320)
3. reboot into recovery
4. select wipe from twrp menu
5. install the zip
6. reboot
why dont you try cm12? much better performance!
.
el-Loko said:
hmm...sounds correct. just try it again.
1. boot into bootloader
2. flash the boot.img from the zip you want to install (for cm11 i recommend to flash nik3rs kernel http://forum.xda-developers.com/showthread.php?t=2012320)
3. reboot into recovery
4. select wipe from twrp menu
5. install the zip
6. reboot
Click to expand...
Click to collapse
Ok, I tried again.
I went into the bootloader and flashed boot.img.
Then went into recovery, and did a factory reset via the wipe menu.
Then used "adb push" to push cm-11.zip to my /sdcard/.
Then I installed the zip without any issues.
But then when restarting, it still warned me no OS was installed.
Booting anyways just got me stuck at the HTC logo.
I then tried again, this time flashing the kernel with Nik3r's file.
And then doing all the same stuff as before, but still getting the no OS was installed message and stuck on the HTC logo.
Perhaps it's the ROM I'm using? I'm not sure why it's telling me "no OS is installed" right after installing one.
el-Loko said:
why dont you try cm12? much better performance!
Click to expand...
Click to collapse
I actually can't find a ROM for CM12. I just grabbed the latest from http://download.cyanogenmod.org/?device=enrc2b.
KindDino said:
Ok, I tried again.
I went into the bootloader and flashed boot.img.
Then went into recovery, and did a factory reset via the wipe menu.
Then used "adb push" to push cm-11.zip to my /sdcard/.
Then I installed the zip without any issues.
But then when restarting, it still warned me no OS was installed.
Booting anyways just got me stuck at the HTC logo.
Click to expand...
Click to collapse
I never used "adb push" to push the ROM installation .zip onto my phone.
If you've made a nandroid backup, then go back to stock and give it a try to transfer the .zip in normal USB/Phone mode.
Afterwards repeat the process as described above.
When I flashed my last CM11 ROM, I used CWM as recovery and I flashed the boot.img after full wipe and rom/gapps installation.
After flash process I restarted the phone into bootloader and flashed the boot.img via adb. Then first normal reboot of the phone.
Worked without any issues...
KindDino said:
I actually can't find a ROM for CM12. I just grabbed the latest from http://download.cyanogenmod.org/?device=enrc2b.
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc...ent/rom-cyanogenmod-12-international-t2948462
Njoatun said:
I never used "adb push" to push the ROM installation .zip onto my phone.
If you've made a nandroid backup, then go back to stock and give it a try to transfer the .zip in normal USB/Phone mode.
Afterwards repeat the process as described above.
Click to expand...
Click to collapse
Sadly, I didn't know to make a backup when I started, so I cannot go back to stock at this time.
Njoatun said:
When I flashed my last CM11 ROM, I used CWM as recovery and I flashed the boot.img after full wipe and rom/gapps installation.
After flash process I restarted the phone into bootloader and flashed the boot.img via adb. Then first normal reboot of the phone.
Worked without any issues...
http://forum.xda-developers.com/htc...ent/rom-cyanogenmod-12-international-t2948462
Click to expand...
Click to collapse
I tried with TWRP again and actually decided to write down the entire log for installing the zip, maybe that'll help. It does say some things about errors, unsure if they're actual bad, or not, as it does succeed.
Of course after installing the zip, I selected 'Reboot' then 'Reboot into Bootloader', then used 'fastboot flash' to flash the boot.img with the boot.img from within the cm-12.zip.
Code:
Installing '/sdcard/cm-12.zip'..
Check for MD5 file..
Skipping MD5 check: no MD5 file found
could not detect filesystem for /dev/block/platform/sdhci-tegra.3/by-name/APP, assuming ext4
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at /system: Invalid argument
unmount of /system failed; no such volume
Patching system image unconditionally...
could not detect filesystem for /dev/block/platform/sdhci-tegra.3/by-name/APP, assuming ext4
mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/APP at /system: Invalid argument
unmount of /system failed: no such volume
script succeeded: result was [0.200000]
Updating partition details...
E:unable to mount '/system'
E:unable to mount '/cache'
...done
I tried CWM a few days ago while attempting this ( as it's linked in the CyanogenMod wiki ), and I just attempted it again with it and still cannot get past the logo.
Here is the log from CWM.
Code:
-- Installing: /sdcard/cm-12.zip
Finding update package...
OPening update package...
Installing update...
detected filesysystem extr4 for /dev/block/platform/sdhci-tegra.3/by-name/APP
Patching system image unconditionally...
detected filesysystem extr4 for /dev/block/platform/sdhci-tegra.3/by-name/APP
script succeeded: result was [0.200000]
Install from sdcard complete.
When rebooting back into the bootloader, I got an error about lost root access. I selected yes.
Code:
Root access possibly lost. Fix? THIS CAN NOT BE UNDONE.
- No
- Yes - Fix root (/system/xbin/su)
Seems like you've wiped your internal SD card partition, if it's unable to detect the ext4 format.
It's mentioned under Post 2 http://forum.xda-developers.com/showthread.php?t=2066390
If so... Search the forum for a solution. Never had this issue. Good luck
Njoatun said:
Seems like you've wiped your internal SD card partition, if it's unable to detect the ext4 format.
It's mentioned under Post 2 http://forum.xda-developers.com/showthread.php?t=2066390
If so... Search the forum for a solution. Never had this issue. Good luck
Click to expand...
Click to collapse
I read the post, and maybe I did wipe my SD Card. I have no idea on how to fix that, and I'll have to research more.
I would like to just use Hasoon2000's toolkit but sadly can't find a working download for it.
Same problem here! Nothing is working. It is saying no OS. Always booting into fastboot mode. Someone help. I have a Moto G3 1540
---------- Post added at 11:27 AM ---------- Previous post was at 11:18 AM ----------
Follow these steps and recover your device.
1. Unlock your bootloader if you have it locked
2. Boot into TWRP
3. Go to Wipe
4. Go to Advanced
5. Select everything except USB - OTG and SD Card
6. Boot into fastboot
7. Download the stock image of your phone
8. Flash it to your phone ( Please find it online)
9. After flashing do not reboot!!!
10. Download Cyanogenmod recovery and flash it to your device.
11. Boot into the newly installed recovery.
12. Go into Apply Update
13. Go into Apply Update from ADB
14. Sideload the Cyanogenmod using the command adb sideload filename.zip ( Replace filename with the name of your zip)
15. After Sideloading, boot into fastboot mode.
16. In fastboot mode, Select BP Tools.
17. Boom! Your device will start booting
Hope this helps you:good::good:
I had the same issue - here's how I went about this...
KindDino said:
Hi,
I'm currently trying to install CyanogenMod onto my HTC One X+, but keep running into problems.
I unlocked the bootloader, and installed TWRP v2.8.7.0.
I went into recovery fine, and used "adb push" to push cm-11-20150906-NIGHTLY-enrc2b.zip onto the device and install it through TWRP.
I then tap "reboot" but it always tells me that "No OS Installed", and rebooting into the bootloader to flash the boot.img and erase the cache doesn't seem to fix this issue.
I've tried a few different versions of recoveries, like CyanogenMod's recovery, but still can't seem to get it to install any OS. Always just get stuck on the HTC logo.
Am I missing an important step, or something? Thanks for your time.
Click to expand...
Click to collapse
I have a Nexus 7 2013 that I commonly use as both my daily driver (tablet-only) and as my ROM-testing guinea-pig. I had AOSP Android 7 installed before I wiped everything, due to an issue with Google Play (which I just couldn't fix for the life of me). When I went to flash a new ROM (AOSP Android 7.1.1), TWRP claimed that there was 'No OS'. This would mean that you definitely wiped everything - possibly including the partitions. My guess is:
If there are no partitions (esp. System, Recovery, Boot, Cache, etc.), the data meant for them may still get written to the device's storage. But the bootloader/kernel won't recognize where to pass the torch to when it's time for the system/userspace to come in.
In order to get this back , you may need either:
A) a ROM that has images for at least the System, Cache, and Boot partitions (add your own recovery if need-be).
B) a Stock ROM from the manufacturer's website, which tends to come with all of these images ready in the .zip
Once you flash one of those, you should confirm that your bootloader is unlocked. Once that is done, flash the ROM of your dreams
I hope this helped...
TWRP bootloop
el-Loko said:
hmm...sounds correct. just try it again.
1. boot into bootloader
2. flash the boot.img from the zip you want to install (for cm11 i recommend to flash nik3rs kernel http://forum.xda-developers.com/showthread.php?t=2012320)
3. reboot into recovery
4. select wipe from twrp menu
5. install the zip
6. reboot
why dont you try cm12? much better performance!
.
Click to expand...
Click to collapse
I have quite same issue.
I have TWRP 3.0.3 (that's the only version that i found and works) on my Doogee X9 Pro (MTK chip inside).
But after flashing successfully a ROM it still reboots to the recovery. (I tried it with 3 different ROMs.)
Any idea what else should/could try?
Hello
I wanted to speed up the TF201 with the help of the Kernel Adjutor. Something went wrong and after a series of frustrated attempts the only thing I get after starting the TF 201 are
- the ASUS /nvidia screen with the message "the device is unlocked"
- 4 penguins with a text "3.xxxxx message length: 9" (xxxxx being random numbers)
- the blue "teamwin" screen.
I cannot get into any other screen by pressing the volume up or down.
In June 2017 I have installed KatKiss 7.1 v023 following your tutorial. I have also made the backup recommended there.
How do I have to proceed to get the TF201 back to normal ?
Thank you very much for your help.
SwissJames
You might have to bring it back using a PC/Laptop along with Minimal ADB and Fastboot, you would have to wipe it and in the process loss everything.
Is your back-up on an external media like the micro SD or SD card?
NP
Hello Nektopoli
Thanks for your support.
backup files "bricksafe.img", "factory-config.img" and "unlock-token.img" are on the PC.
I still have the original files on micro SD from the upgrade to Android 7.1 Nougat as described in the tutorial.
After much research and many unsuccessful tries, it seems that I get lucky with lj50036's post: https://forum.xda-developers.com/showthread.php?t=2538028. After following his instructions it I was able to boot into fastboot.
At the step "fastboot -w" I got stuck: erasing cache "Command write failed <unknown error>"
So I closed the terminal and opened a new one (as described).
"fastboot erase boot" failed again "Command write failed <unknown error>"
Restarting the PC fixed the issue.
I managed to get the other steps done as well.
Now the tablet is working again with Android 4.1.1.
Next I'll upgrade it back to 7.1
Regards
SwissJames
swissjames said:
Hello Nektopoli
Thanks for your support.
backup files "bricksafe.img", "factory-config.img" and "unlock-token.img" are on the PC.
I still have the original files on micro SD from the upgrade to Android 7.1 Nougat as described in the tutorial.
After much research and many unsuccessful tries, it seems that I get lucky with lj50036's post: https://forum.xda-developers.com/showthread.php?t=2538028. After following his instructions it I was able to boot into fastboot.
At the step "fastboot -w" I got stuck: erasing cache "Command write failed <unknown error>"
So I closed the terminal and opened a new one (as described).
"fastboot erase boot" failed again "Command write failed <unknown error>"
Restarting the PC fixed the issue.
I managed to get the other steps done as well.
Now the tablet is working again with Android 4.1.1.
Next I'll upgrade it back to 7.1
Regards
SwissJames
Click to expand...
Click to collapse
Have you updated the bootloader to 10.6.1.27.1 and installed the TWRP recovery console?
NP
No, not yet. As I flashed the tab with the official ASUS firmware, everything has gone. Bootloader is 10.4.2.18 and the TWRP recovery console is gone. (RCK ends up with a "dead" android...). I'll follow the latest version of the tutorial https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237 to upgrade the tab.
Can you access the tablet via a computer/laptop using and ADB fastboot program like "Minimal ADB and Fastboot" https://forum.xda-developers.com/showthread.php?t=2317790
If you can, you could manually wipe the tablet, and flash JB Bootloader 10.6.1.27.1 and TWRP 2.5, then update the TWRP and install 7.1
NP
I almost got through the guide till chapter 8. Trying to install the open_gaaps-arm 7.1 pico I got the error msg "insufficient storage space available in System partition". The error log is attached.
Maybe you have an idea what I could delete on the System partition (and how). I have tried e.g. to get rid of the gmail account, but without success.
You should wipe the system partition before flashing the ROM, SuperSU and GAPPs using TWRP when you flash a new ROM
Alternatively, if you're using a PC and Fastboot to install the ROM
the: [fastboot erase system] command will wipe the system, but I don't think it will change the System partition to F2FS
NP
I have wiped all partitions before proceeding.
The size of my "system" partition after wiping is 503 MB (8 MB used) with ext4 (510 / 116 MB used with f2f). So I opted for the ext4-variant as described in the guide.
After installing KatKiss-7.1_TF201_026.zip, 433 MB are used in "system"
After installing SuperSU-v2.82.zip, 440 MB are used in "system".
So there is not enough space left for open_gaaps-arm-7.1_pico.zip with about 125 MB unzipped.
Is there a way to increase the size of the "system" partition ? (there is enough space left in the "data" partition where I could take some...)
Or do you see other options ?
Can you get back into the recovery console?
NP
yes I think so.
By pressing power and volume - I got to the selection screen and chose RCK. Now I am in TWRP again.
When you boot into the fastboot screen, the one with the RCK icon you should see the bootloader version at the top of the screen, what version is your tablet on?
this is what mine looks like
NP
it says
<1.00 e> released by "ww_epad-10.4.2.15-20120917" A03
sj
I checked the configuration of the bootloader before I began with the upgrade from 4.1. It said 10.4.2.18-20112122...
sj
What version TWRP do you have working now?
Ok, with the working TWRP you can flash the new Bootloader v10.6.1.21.1 found here;
https://androidfilehost.com/?fid=23060877490002899
This will also install TWRP 2.5 at this point we don't want to install any thing else. Once you are on the correct bootloader and TWRP 2.5 you will need to update TWRP in two steps. First to TWRP 2.8.5.1 and then to TWRP 3.1.0-1 once you have a working TWRP you can wipe the TF and flash the 7.1.2 ROM.
NP
As you suggested I downloaded the zipped file and put it on the pc and on the sd-card.
Swiped it with the twrp 3.1.0-1 from the sd-card
looked ok. Requested reboot.
The blue line appeared. It took no time at all to complete.
Now the I am on the asus-screen
reboot to get to see the version. still 10.4.2.15 with twrp 3.1.0-1
next try: installing the bootloader with cmd.exe
typed on pc: "adb devices"
response:
"list of devices attached"
"015d0787774bf603 recovery"
typed: "adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard" (the one I got from the site you indicated)
response: "1325 KB/s" etc -> looks as transferred to sdcard
on tab: "installing files.."
"done..."
"now please restart..."
"updating partition details..."
"...done"
reboot to get to see the version.
screen says
"OS will cold boot in 10 seconds if no input is detected"
"booting recovery kernel image"
Version is still 10.4.2.15 with twrp 3.1.0-1
That is so bizarre that it wont update the bootloader or downgrade the TWRP.
One way to fix this is to do a FULL "adb wipe"
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
This will wipe the complete table back to nothing.
Then:> adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard
This should get you on the correct bootloader and TWRP, after this boot into fastboot to confirm you're on the correct bootloader then flash 3.1.0-1
NP
I did what you suggested and erased all the files ->worked well.
Then "adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard" -> got an error: "device not found"
I restarted the tab and then clicked on the USB-symbol.
"adb devices" showed an empty list of devices attached.
"fastboot -i 0x0b05 flash recovery flatline_TF201.img" gave "OKAY" and "writing recovery"
Bootloader is still 10.4.2.15
On the tab I am now on Flatline CWM Recovery v1.0RC1
TWRP is gone.
"adb devices" shows "0123456789ABCDEF recovery"
again "adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard" success ! Data were copied.
reboot. Bootloader is still on 10.4.2.15
nBootloader should now be in the /sdcard
next intent:
"fastboot -i 0x0b05 flash recovery flatline_TF201.img" gave "OKAY" and "writing recovery"
restart, then to RCK - flatline CWM recovery
install zip from sdcard -> no files found
got in advanced - wheelie - I accept the above statement - flash androidRoot BL power off
-> blue progress line is almost empty. then progress line disappears, ASUS screen shows up.
In Flatline recovery tried "install zip from sdcard" - "choose zip from sdcard".
only "- AndroidRoot/" is shown. (no nHairyBean_Bootloader_TWRP2.5.zip). So no way of installing the nHairyBean_Bootloader-
On one hand, it seems that I am able to establish a connection between the PC and the tab when in RCK, but when in USB, the connection seems not possible.
Hmmm...
Maybe I am missing something basic in this whole thing that keeps me from progressing.
What if I use the backup-files and try to go back to the initial configuration of the TF201 ? Or are there other options with the CWM-Recovery ?
Regards sj
That sounds like the best idea, going back to the stock ROM, they can be found here; https://www.asus.com/Tablets/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/
Download the version for you region install and see if you can get back to stock.
NP
I downloaded the file you indicated. Now how do I get it into use ?
I cannot get into APX-mode
the only program working in the tab seems to be the flatline CWM Recovery v1.0RC1.
I tried to send the zip-file with "adb sideload <filename>" Error: failed to write data 'protocol fault <no status>'
I copied the zip-file to the external sd-card, but do not see how I can access it. The sd-card mentioned on screen ("Apply update from .zip file on SD card")seems to be an internal storage.
I've unlocked the bootloader to my Wileyfox Spark X using "fastboot flashing unlock" from my Ubuntu PC. I've flashed twrp recovery image (twrp-3.2.1-0-porridgek3.img
from https://dl.twrp.me/porridgek3/) having renamed it to twrp.img:
[email protected]:/home/john/Software/WileyfoxSparkX# fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13154 KB)...
OKAY [ 0.378s]
writing 'recovery'...
OKAY [ 0.347s]
finished. total time: 0.726s
But I can't get into SuperSU 2.82 (using SuperSU-v2.82-201705271822.zip) even though I've put it into the root directory of the internal SD card. There's no obvious option from the Android Recovery menu (i.e. Reboot system now, Reboot to bootloader, Apply update from ADB, Apply update from SD card,....). I've tried Apply update from SD Card and selected the SuperSU .zip file but it comes up with ""installation aborted" after "Update verification took 0.2 s (result 1)" with no other help. Any ideas?
I've tried TWRP 3.0.2-0. It gets into TWRP menu. I selected Install but "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. BTW I've emailed TWRP Support (from their web page) asking if they have a working version.
johnaaronrose said:
I've tried TWRP 3.0.2-0. It gets into TWRP menu. I selected Install but "it seems /system cannot be mounted anymore and TWRP thinks no system is installed)". After letting it finish, Root Checker (not unsurprisingly) says that device is not rooted. BTW I've emailed TWRP Support (from their web page) asking if they have a working version.
Click to expand...
Click to collapse
Don't bug the TWRP developers for a specific version of TWRP which isn't even maintained by them.
Can you mount /system at all? Try pressing the "Mount" button in the main menu and let me know. You aren't supposed to install anything from the Android Recovery menu, you can only install OTA updates through that menu and its functionality is pretty much limited.
Where did you get that version of TWRP from? (I'd appreciate it if you linked me the thread)
AlwaysLivid said:
Don't bug the TWRP developers for a specific version of TWRP which isn't even maintained by them.
Can you mount /system at all? Try pressing the "Mount" button in the main menu and let me know. You aren't supposed to install anything from the Android Recovery menu, you can only install OTA updates through that menu and its functionality is pretty much limited.
Where did you get that version of TWRP from? (I'd appreciate it if you linked me the thread)
Click to expand...
Click to collapse
I assumed that the Wileyfox Spark X (i.e. porridgek3) version is maintained by the TWRP developers because the various versions come from:
https://dl.twrp.me/porridgek3/
Currently, I can't get into TWRP again. It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. sill in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu. Could that be due to needing e.g. 70% battery charged?
At the moment the battery is 50% charged. So I'll fully charge it and post about the mount of /system using TWRP, assuming that I can get into TWRP.
BTW I did find a thread on https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung The interesting comment is #5. It says:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Is this the solution to rooting on the Spark X?
johnaaronrose said:
I assumed that the Wileyfox Spark X (i.e. porridgek3) version is maintained by the TWRP developers because the various versions come from:
https://dl.twrp.me/porridgek3/
Currently, I can't get into TWRP again. It's all hit & miss getting into TWRP:
1. If I do anything after flashing (e.g. booting as normal), I have to go into fastboot & flash TWRP again.
2. Once I have flashed TWRP (i.e. sill in fastboot mode), I can't leave fastboot mode. Also, the phone will not switch off unless I remove the battery and put it back in after approx 10 seconds.
3. Even then it often refuses to load TWRP i.e. it goes into the Android Boot menu. Could that be due to needing e.g. 70% battery charged?
At the moment the battery is 50% charged. So I'll fully charge it and post about the mount of /system using TWRP, assuming that I can get into TWRP.
BTW I did find a thread on https://android.stackexchange.com/questions/160130/how-do-i-install-systemless-supersu-in-samsung The interesting comment is #5. It says:
Sometimes the need for a systemless installation of SuperSU is not detected by the installation script, to force this to occur follow the following steps.
Start TWRP 3.0 or higher on the device
Go to Advanced - Terminal
In the terminal, enter echo SYSTEMLESS=true>>/data/.supersu
Press Enter
Exit to the TWRP main menu
Flash the current SuperSU as per normal
When flashing SuperSU, you should see in the TWRP recovery log screen mentions of system-less installation and patching of the boot image.
Is this the solution to rooting on the Spark X?
Click to expand...
Click to collapse
Yeah, that's normal. The battery percentage here doesn't really matter, but you could try to boot to TWRP using fastboot. You can also boot to TWRP by executing "fastboot boot recovery.img". You can also flash TWRP *through* TWRP.
I wanted to get rid of the Chinese bloatware that came with the phone and decided to install the xiaomi.eu rom.
This is what I did;
unlock the bootloader
downloaded TWRP from official website (3.2.1-0)
installed TWRP with adb, reboot into TWRP with VolUp+Power buttons combination
factory reset and clean data partition
reboot
PROBLEM 1: stuck at MI logo... I said "whataver" and reboot into TWRP
plugged into PC, and transferred rom into internal memory manually
PROBLEM 2: I couldn't push with adb because the device is not recognised in fastboot
in TWRP press install, try to install rom zip
PROBLEM 3: get error 7 message "This package is for device gemini.."
I say "whatever" and download global stable rom from MIUI
did another system data cache clean, tried to install rom
PROBLEM 4: "unmount of /firmware failed: no such volume" "mount:failed to mount /dev/block/bootdevice/by-name/sec at /firmware: invalid argument"
It says "scripting succeeded: result was [1.000000] Updating partition details...done", but when I reboot I'm stuck at the MI logo again!
Any help is very appreciated!
tryhardernow said:
I wanted to get rid of the Chinese bloatware that came with the phone and decided to install the xiaomi.eu rom.
This is what I did;
unlock the bootloader
downloaded TWRP from official website (3.2.1-0)
installed TWRP with adb, reboot into TWRP with VolUp+Power buttons combination
factory reset and clean data partition
reboot
PROBLEM 1: stuck at MI logo... I said "whataver" and reboot into TWRP
plugged into PC, and transferred rom into internal memory manually
PROBLEM 2: I couldn't push with adb because the device is not recognised in fastboot
in TWRP press install, try to install rom zip
PROBLEM 3: get error 7 message "This package is for device gemini.."
I say "whatever" and download global stable rom from MIUI
did another system data cache clean, tried to install rom
PROBLEM 4: "unmount of /firmware failed: no such volume" "mount:failed to mount /dev/block/bootdevice/by-name/sec at /firmware: invalid argument"
It says "scripting succeeded: result was [1.000000] Updating partition details...done", but when I reboot I'm stuck at the MI logo again!
Any help is very appreciated!
Click to expand...
Click to collapse
Well, you need here some corrections to do things in the right way.
In the 3rd step you say that installed twrp through adb but twrp can´t be installed through adb; maybe you wanted to mean fastboot that is other thing.
In the 4th step most important is at first reboot to twrp swipe to allow modifications and then you have to perform "format data" to can reboot normally to system although some times is required no-verity zip for R5P vince (just Google) some users refer that is needed despite I never did.
In the 8th step; fastboot mode can´t work simultaneously meanwhile are you using adb so you don´t need it when you are using adb although this you can´t transfer a file from pc to your device using simply adb; you need to enable first in advanced options from twrp the feature adb sideload then placing the file that you want to transfer from pc to device in the same adb folder you have to type in a terminal with admin rights adb sideload nameoffile.zip but this is not to transfer a file only but to transfer it and flash it onto device.
In the 10th step first open the zip file of the rom with notepad++, go to META-INF/com/google/android/updater-script and check what device is it made for and additional you can browse to system/build.prop and similarly open it and check ro.product/model cause gemini is other variant.
So I think that you flashed firstly a rom for other device and maybe you need to restore some partitions to correct this using MiFlash tool.
But first to this if most of all partitions are working and not damaged you can flash almost any partition through fastboot mode, unzip the rom in the same adb folder and type every file for every partition one by one but maybe you need only system, boot and userdata partitions so try first these three, I hope that you know syntax of fastboot commands.