Related
Last night I got the notification for 4.4 update. I'm on a rooted stock device, Build JSS15R Kernel 3.4.0-ge52a21
I hit ok to reboot and install. It booted and I saw the green android. I then left the room (mistake), and when I came back it was on the main screen.
I checked and I was on 4.3 still. Is there anyway to check to see why it failed? Any log files? Will I get the OTA again?
I don't really want to sideload but if last resort I will.
Any ideas?
Check the cache folder whether the downloaded files are there,,
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 07:04 PM ---------- Previous post was at 07:03 PM ----------
Also it's not safe to do an OTA on a rooted device...
Sent from my Nexus 7 using xda app-developers app
this is exactly happened to me too,
so if my device rooted, i have to do safeload instead of OTA ?
That's stange, as every previous update i've had on both my Nexus 7's have been done on a rooted device.
Obviously you lose the root by doing the update, but just re-root afterwards.
In the cache folder there is a .zip file called. 'Longrandonstringofchars'+.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
???
filking said:
I checked and I was on 4.3 still. Is there anyway to check to see why it failed? Any log files? Will I get the OTA again?
I don't really want to sideload but if last resort I will.
Click to expand...
Click to collapse
Somewhere in /cache there is a recovery.log file
If you are not on the latest version you'll get the OTA again eventually.
Sideloading is really the same type of install as OTA. The difference mainly being whether it is automatically downloaded or you download by hand and send over a USB connection. The actually install file is the same in either case.
Thanks... I knew it was the same but I had a problem doing the same with an old nexus 2012 and the cable 'slipped' and bricked it.
So, to save risks, i'll wait for the OTA.... Not in a hurry, just curious why it didn't install 1st time.
I'll look at the recovery.log file and see what I find.
Ok, Below is the end of the recovery.log.
Seems like an error in the downloaded file, but I may be wrong.
Finding update package...
I:Update location: /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
Opening update package...
I:read key e=65537
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1370 bytes; signature 1352 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Verifying current system...
file "/system/bin/debuggerd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/debuggerd" has unexpected contents.
"/system/bin/debuggerd" has unexpected contents.
E:Error in /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
(Status 7)
Installation aborted.
I:Saving locale "en_GB"
I:timed out waiting for key input; rebooting.
I:Saving locale "en_GB"
Any ideas?
filking said:
Ok, Below is the end of the recovery.log.
Seems like an error in the downloaded file, but I may be wrong.
Finding update package...
I:Update location: /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
Opening update package...
I:read key e=65537
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1370 bytes; signature 1352 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Verifying current system...
file "/system/bin/debuggerd" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/bin/debuggerd" has unexpected contents.
"/system/bin/debuggerd" has unexpected contents.
E:Error in /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
(Status 7)
Installation aborted.
I:Saving locale "en_GB"
I:timed out waiting for key input; rebooting.
I:Saving locale "en_GB"
Any ideas?
Click to expand...
Click to collapse
To me, it looks like a corrupted download. Maybe you can try deleting the file and reboot?
Sent from my Nexus 4 using Tapatalk
I thought that as well.. So I copied the .zip file and deleted it.
Rebooting..... I will report back..
filking said:
Ok, Below is the end of the recovery.log.
Seems like an error in the downloaded file, but I may be wrong.
...
Any ideas?
Click to expand...
Click to collapse
The downloaded file is fine.
Your /system/bin/debuggerd is modified.
You most likely are rooted and using stickmount.
You can grab the appropriate debuggerd from this thread in the download section:
http://forum.xda-developers.com/showthread.php?t=2534698
look for update-KRT16S-debuggerd.zip
You can run it in TWRP or unzip and place debuggerd in /system/bin
Cheers for that.
I've now copied the downloaded 'buggerd' file (appropriate name btw) over and put the OTA .zip file back into cache.
Is there anyway I can execute that now, or do I have to wait for a new download.
filking said:
Cheers for that.
I've now copied the downloaded 'buggerd' file (appropriate name btw) over and put the OTA .zip file back into cache.
Is there anyway I can execute that now, or do I have to wait for a new download.
Click to expand...
Click to collapse
I assume you are unlocked?
Download latest twrp 2.6.3.1, unzip, rename as twrp.img, place in platform-tools
Boot into boot loader
In command prompt in your platform-tools directory type
fast boot boot twrp.img
Choose install and select the ota update.zip in the file browser
Or you can skip all that and wait for it to naturally happen.
Question for you. Downloaded the TWRP 2.6.3.1 which arrived as openrecovery-twrp-2.6.3.1-flo.img
You then say unzip. Confused at that point. Using all zip programs says no files. Was that put in to test me?
I had the exact same issue, please update with what you find out.
filking said:
Question for you. Downloaded the TWRP 2.6.3.1 which arrived as openrecovery-twrp-2.6.3.1-flo.img
You then say unzip. Confused at that point. Using all zip programs says no files. Was that put in to test me?
Click to expand...
Click to collapse
Sorry, I usually zip it up. Just rename it twrp.img so it is easier to type.
Ok, So I followed the directions..
Selected Install, then selected the downloaded .zip OTA file.
Messages on screen as follows :-
Skipping MD5 check
Verifying current System...
"/system/framework/core.odex" had unexpected content.
E:Error executing updater binary in zip ".... (ota file)"
updating partition details.
Then I reboot and tablet back to normal..
Help please
*UPDATE*
As I rebooted, I got a system message saying a new OTA is available. (spooky)
I selected install.
Got the green android and then he fell over error.
Checked the cache log and got same error really.
failed to stat "/cache/saved.file"
failed to load cache file
script aborted:" /system/framework/core.odex" has unexpected contents
E:Error in /cache/"otafile.zip"
(status 7)
installation aborted.
:crying:
sfhub said:
Sorry, I usually zip it up. Just rename it twrp.img so it is easier to type.
Click to expand...
Click to collapse
No worries, I guessed as much.
The update for 4.4 finally popped up on my notification bar as well and I went straight ahead to install it, hit reboot and install, it started the installation. I'm on stock with unlocked bootloader&rooted
Suddenly a sad looking dead android pops up with an "Error!" message. Waited a while and the device rebooted and it's still on 4.3, and I've lost the system update notification & in the settings it says I'm up to date :L
And I had this at the end of my recovery log file...
Finding update package...
I:Update location: /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
Opening update package...
I:read key e=65537
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1370 bytes; signature 1352 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Verifying current system...
failed to stat "/system/app/Chrome.apk": No such file or directory
file "/system/app/Chrome.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/app/Chrome.apk" has unexpected contents.
"/system/app/Chrome.apk" has unexpected contents.
E:Error in /cache/7d9b309e11da82edb5373a1f59965bca89f6041f.signed-razor-KRT16S-from-JSS15R.7d9b309e.zip
(Status 7)
Installation aborted.
I:Saving locale "en_US"
I:timed out waiting for key input; rebooting.
I:Saving locale "en_US"
..does this mean I need to get all the crappy system apps I've deleted back in there in order to make the update succeed? Also any idea how to get the update notification back so it could even try running it again? Thanks in advance!
filking said:
Ok, So I followed the directions..
Selected Install, then selected the downloaded .zip OTA file.
Messages on screen as follows :-
Skipping MD5 check
Verifying current System...
"/system/framework/core.odex" had unexpected content.
E:Error executing updater binary in zip ".... (ota file)"
updating partition details.
Then I reboot and tablet back to normal..
Help please
*UPDATE*
As I rebooted, I got a system message saying a new OTA is available. (spooky)
I selected install.
Got the green android and then he fell over error.
Checked the cache log and got same error really.
failed to stat "/cache/saved.file"
failed to load cache file
script aborted:" /system/framework/core.odex" has unexpected contents
E:Error in /cache/"otafile.zip"
(status 7)
installation aborted.
:crying:
Click to expand...
Click to collapse
So you've fixed one problem file (debuggerd) only to notice another file has been modified core.odex.
At this point I would suggest you just flash the factory image. We can go on replacing files one by one, but chances are you modified more than one file either directly or indirectly by flashing something on top for some tweak.
There are instructions and download link for the KRT16S factory image here (choose the nowipe option to keep your data):
http://forum.xda-developers.com/showthread.php?p=47640458#post47640458
---------- Post added at 06:53 PM ---------- Previous post was at 06:51 PM ----------
Zamuzzzz said:
..does this mean I need to get all the crappy system apps I've deleted back in there in order to make the update succeed? Also any idea how to get the update notification back so it could even try running it again? Thanks in advance!
Click to expand...
Click to collapse
If you've deleted a bunch of system apps, best you just flash the factory image, instructions and download here (choose the nowipe option to keep your data):
http://forum.xda-developers.com/showthread.php?p=47640458#post47640458
In the future, instead of deleting system apps, it is better to freeze the system apps if you want to receive future OTAs.
Thanks for reply. It's totally weird tho, as the only thing I've done is use the nexus root toolkit to unlock and root my device.
Apart from that, only added a few other apps like stickmount that may affect things.
The 4.3 update went fine. So it doesn't make sense, but I will now follow the instructions to do it manually.
Cheers for the help.
I am not responsible for whatever may happen to you or your device when using this, Run this at your own risk!!
Requires unlocked bootloader!
Based on SuperSU - v4.46 (the binary updates from within the app later on)
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LMY47D - root-boot
For past firmware:
LRX21V - root-boot
For past firmware:
LRX21M - root-boot
crappy video but simple demonstration :good:How to install:
Download the zip depending on your Nexus Player's firmware than extract & run root-boot.bat (Other operating system support coming soon for the installer script) Made on windows 7
Follow and read the on screen instruction carefully
Click to expand...
Click to collapse
SU app and binarys gets installed to /system/* directory's, The insecure boot.img gets installed to be able to access root adb shell and install those binarys
The root-boot boot.img is temporarily booted once during this process on the first boot of installation, it does not flash the boot.img
The previous boot.img before the installation is restored after SU is installed
Click to expand...
Click to collapse
Thanks @Chainfire for Superuser
My Donation Box
Troubleshooting:
Check to make sure your device gets picked up in adb before running the script - - - ADB Drivers
This tool uses an unlocked bootloader and i have not unlocked mine yet, does unlocking the bootloader wipe the device? - - - Yes unlocking the bootloader will wipe the device
After fastboot flashed the boot.img than rebooted to the home screen i continued the the script like the installation steps said but it returned "device not found" - - - As long as it shows transferring files a few seconds after than its fine, adb restarts at that moment which will than return "device not found" than it reconnects and transfers. if fastboot flashed than rebooted fine than adb shouldn't have an issue
Help! Something went wrong and im bootlooping but i dont want to loose all my saved data - - - Everything is fine, Download the factory zip from here for your android version than extract the zip and retrieve the system.img and copy it into a folder that contains adb/fastboot and boot your device into fastboot mode and do "fastboot flash system system.img" doing it this way wont wipe your "/data" partition leaving everything intact but will restore the system back to its defaults
(If you were to run the factory zip as an update than it would format everything)
I installed SU with this method but cant use adb commands on my device - - - Go into "Settings>About" and click on "Build" 7 times very fast and it will enable "Developer options" in the settings menu, Go back to the settings menu and open developer options (You may need to reboot if it doesnt show up immediately) and enable the "USB debugging" option
Ill be updating this as new version of lollipop get released
support for both firmwares are up, any issues let me know i tested them both though and everything looked okay
Reuploading, had a minor issue
Edit: LRX21M link back up, let me know if there's any issues
Whoa...
Let the games begin....
ftarules said:
Whoa...
Let the games begin....
Click to expand...
Click to collapse
yeup, after recovery i have a few system modification ideas for the settings apk i was considering
i do have other devices to worry about though so it may take some time
bunchies said:
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM
For current firmware:
LRX21V - root-boot
Click to expand...
Click to collapse
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
mikereidis said:
Working well, Thank you, after semi-manually adapting for working from Linux Mint.
I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
Click to expand...
Click to collapse
Use adb shell
than type su to use root adb shell
Since running the script everything seems all good except for using voice search. Anybody else having issues where voice search just closes?
Update: Erased and manually flashed the V firmware as I was on M and now it appears to be working correctly, not sure if this is going to be a problem with people stuck on M for now but you may want to think of upgrading your fimware.
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
xReaper7x said:
Getting ADB device not found.. Anywhere I can download drivers from? I have the latest android-sdk
Click to expand...
Click to collapse
http://developer.android.com/sdk/win-usb.html
at what point, adb will restart about half way through and it shows it cant connect to device but it really is
but if your in fastboot and it cant connect to the device than thats an issue
i should note this in the OP
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Snuzzo said:
Subscribed for later. Awaiting someone else to port a recovery for this, I am lazy.
Click to expand...
Click to collapse
lol Snuzzo :good: recovery coming soon
Links are down. Does anyone have a mirror of 21V?
prsterero said:
Links are down. Does anyone have a mirror of 21V?
Click to expand...
Click to collapse
Links are up, hosted on android file host
Can mirror in a bit if needed
bunchies said:
Links are up, hosted on android file host
Can mirror in a bit if needed
Click to expand...
Click to collapse
Looks like it's working now. Before I was getting that the file couldn't be found. Thanks I appreciate you releasing this I just got it unlocked so time to root and have some fun expanding the storage to 128gb
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
________________________________________________________
root-boot: By Bunchies @xda
________________________________________________________
________________________________________________________
Power off/unplug the device, hold the power button while
plugging in the device until you see the google logo and
than let go to enter fastboot mode
________________________________________________________
________________________________________________________
Plugin the device to a PC using a usb cable
________________________________________________________
Press any key to continue . . .
waiting for ADB
target reported max download size of 536870912 bytes
sending 'boot' (5424 KB)...
OKAY [ 1.357s]
writing 'boot'...
OKAY [ 1.515s]
finished. total time: 2.876s
rebooting...
finished. total time: 0.602s
When boot completes
and you see the launcher
Press any key to continue . . .
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
rm: /system/bin/install-recovery.sh: Read-only file system
mkdir failed for /system/app/SuperSU, Read-only file system
mkdir failed for /system/bin/.ext, Read-only file system
failed to copy 'SuperSU/SuperSU.apk' to '/system/app/SuperSU/': Is a directory
failed to copy 'x86/su' to '/system/xbin/su': Read-only file system
failed to copy 'x86/supolicy' to '/system/xbin/supolicy': Read-only file system
failed to copy 'x86/libsupol.so' to '/system/lib/libsupol.so': Read-only file sy
stem
failed to copy 'x86/99SuperSUDaemon' to '/system/etc/init.d/99SuperSUDaemon': Re
ad-only file system
failed to copy 'x86/install-recovery.sh' to '/system/etc/install-recovery.sh': R
ead-only file system
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: /system/xbin/sugote-mksh: Read-only file system
ln: /system/bin/su: Read-only file system
ln: /system/bin/install-recovery.sh: File exists
rm: /system/bin/app_process: Read-only file system
ln: /system/bin/app_process: File exists
mv: rename /system/bin/app_process32 to /system/bin/app_process32_original: Read
-only file system
ln: /system/bin/app_process32: File exists
cp: /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/app/SuperSU: No such file or directory
Unable to chmod /system/app/SuperSU/SuperSU.apk: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/lib/libsupol.so: No such file or directory
Unable to chmod /system/bin/.ext: No such file or directory
Unable to chmod /system/bin/.ext/.su: No such file or directory
Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chmod /system/xbin/daemonsu: No such file or directory
Unable to chmod /system/xbin/sugote: No such file or directory
Unable to chmod /system/xbin/sugote-mksh: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/xbin/supolicy: No such file or directory
Unable to chmod /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/bin/app_process_init: No such file or directory
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: No such
file or directory
chcon: Could not label /system/bin/.ext/.su with ubject_r:system_file:s0: No
such file or directory
chcon: Could not label /system/lib/libsupol.so with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/etc/init.d/99SuperSUDaemon with ubject_r:syste
m_file:s0: No such file or directory
chcon: Could not label /system/bin/sh with ubject_r:system_file:s0: Read-onl
y file system
chcon: Could not label /system/xbin/sugote with ubject_r:zygote_exec:s0: No
such file or directory
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: N
o such file or directory
chcon: Could not label /system/xbin/sugote-mksh with ubject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/bin/app_process32_original with ubject_r:zygot
e_exec:s0: No such file or directory
chcon: Could not label /system/bin/app_process_init with ubject_r:system_file
:s0: No such file or directory
Finished, you can now exit the installer
Press any key to continue . . .
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
prsterero said:
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.
Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
Click to expand...
Click to collapse
Glad to hear that!
bunchies said:
Glad to hear that!
Click to expand...
Click to collapse
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
prsterero said:
The first time around I got into the bootloop so I had to start over. Second time and it worked now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.
Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently
Click to expand...
Click to collapse
Weird, windows 8?
HI
I have a HTC one M9 hima. Lastly, it has suddenly rebooted. I have not use it.
But it have not stuck in boot. It has boot to the withe Logo screen then go off and boot again, again and again.
If i push power + vol down, the Black screen with e HTC logo comes and the loop go faster.
The only way to come to the bootloader ist to push power + vol down + vol up.
From there i come to the recovery or download Mode. I have twrp installed.
In twrp i discovered that some Partitions can not mount:
mount: mounting /dev/block/mmcblk0p65 on /cache failed: Invalid argument
mount: mounting /dev/block/mmcblk0p67 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p36 on /devlog failed: Invalid argument
mount: mounting /dev/block/mmcblk0p50 on /carrier failed: Invalid argument
mount: mounting /dev/block/mmcblk0p69 on /cota failed: Invalid argument
mount: mounting /dev/block/mmcblk0p68 on /preload failed: Invalid argument
mount: mounting /usb_otg on vfat failed: No such file or directory
mount: mounting /sd-ext on ext4 failed: No such file or directory
I tried:
- wipe Data --> mount error
- formate Data --> mount error
- flash new rom --> mount error
- install new Firmware --> requiret new start then loop
- mount manuel over adb --> invalied argument
- e2fsck /dev/block/mmcblk0p* --> bad magic number in super-block
- flash rom with fastboot --> invalid zip file
- new recovery --> after flash and boot to recover: exist old recovery <-- with dd, twrp and with fastboot
- twrp repair or change File System --> mount error
- twrp resize File System --> end with ERROR: 8
- twrp Change File System --> ERROR: 8
pls help me!!
sorry for my bad English
anyone here who knows the solution for above errors please? coz it did happen to me also. Thanks XDA for your help.
my has expanded. after After my m9 has lain a long time to empty the battery. I can only boot to the bootloader. If i try to boot to recovery or DownloadMode(Fastboot) comes a message "Fail to boot to *".
Radianer said:
my has expanded. after After my m9 has lain a long time to empty the battery. I can only boot to the bootloader. If i try to boot to recovery or DownloadMode(Fastboot) comes a message "Fail to boot to *".
Click to expand...
Click to collapse
On my htc m9, I could still boot to TWRP Recovery but in the Download Mode, it says "Failed to boot to Download"
kmx0101 said:
On my htc m9, I could still boot to TWRP Recovery but in the Download Mode, it says "Failed to boot to Download"
Click to expand...
Click to collapse
As I allready said... maybe flashing signed hosd file fix it...but it isn't sure...
some devices work after... some don't.
shivasrage said:
As I allready said... maybe flashing signed hosd file fix it...but it isn't sure...
some devices work after... some don't.
Click to expand...
Click to collapse
Thanks shivasrage. Let me try ur suggestion but where I could find a signed hosd file?
kmx0101 said:
Thanks shivasrage. Let me try ur suggestion but where I could find a signed hosd file?
Click to expand...
Click to collapse
https://forum.xda-developers.com/one-m9/help/download-modepossible-fix-t3555678
Hello,
My tablet had a battery drain problem so I changed the motherboard and tried to install lineageos 14.1 again.
After replacing the motherboard, I turned on the tablet to activate usb debugging. The rom installed wasn't "complete", it looked like an interface for professionals to copy data from the old motherboard to the new... Maybe one of you knows what I'm talking about.
I flashed twrp and booted in recovery mode. Then I tried to wipe data but got errors (for instance "cache partition not found" or "hidden partition not found" or something like this. I'm sorry I didn't copy the error message :/
I tried to reboot anyway but I'm now unable to boot on the rom nor on recovery mode. I have a message : "POWER RESET or UNKNOWN UPLOAD MODE" and "ATconsole=ram loglevel=4 sec_debug. Level=1 cluster_power=1 androidboot. debug_level=0x494d sec_"
Only download mode is working.
So I'm trying to install the stock rom, downloaded from sammobile. On linux via Heimdall I got this error when flashing system.img and hidden.img :
Code:
Uploading SYSTEM
0%
1%
ERROR: Failed to unpack received packet.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send end session packet!
Releasing device interface...
On windows via Odin, I cannot flash the tar.md5 file either, it fails.
Someone could help ?
Or at least explain why I got these errors in twrp?
Thank you very much !!!!!!
Update :
I found a way to boot in recovery mode (twrp 3.3.1-klimtwifi) : unplug the battery, replug it and home + vol up + power.
So here is the error when I try to wipe data : "Failed to mound '/hidden' (Invalid argument)"
I installed the old motherboard and I'm doing a full backup on my sd card on TWRP, including EFS partition.
On the new motherboard I can't restore the backup because in twrp > restore > sd card : "No partitions selected to restore".
So here's where I am now :
I can boot into twrp but have an error message when trying to wipe data.
I have a full backup of the old motherboard with lineageos installed and working but i'm not able to restore it
Any help appreciated
And also, when I try to sideload the lineageos zip file I get this :
Code:
Starting ADB sideload feature ...
Installing zip file '/sideload/package.zip'
Target: samsung/klimtwifixx/klimtwifi:6.0.1/MMB29K/T700XXU1CRF1:user/release-keys
detected filesystem ext4 for /dev/block/platform/dw_mmc.0/by-name/SYSTEM
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Ok, I fixed the restore issue by moving the backup files to : sd_external/twrp/BACKUP/[myserialnumber]
So now I can restore all partition except System, System Image and Hidden.
Error : extractTarFork() process ended with ERROR: 255
I still can't sideload the custom rom. But the error message "Failed to mound '/hidden' (Invalid argument)" disapeared
I fixed/unbricked the tablet by using SamFirm to download a 3 files stock firmware.
I installed it with Odin and it worked like a charm.
Then I could install a custom rom
How the title says i have this error in twrp,
Error opening: '/data/....' (Structure needs cleaning)
twrp can't see my storage, some help?
Solved: Format data and restart recovery.