Good afternoon everybody,
Need a bit of help with a Nexus 9 LTE and getting it reloaded with the factory image.
Initial Issue: Had a lady bring this to me, said it had gotten stuck in boot loop (google logo, black screen, repeat).
Steps taken:
So I've gotten platform tools, adb driver is installed and functioning. I've followed the steps in this guide drive.google.com/file/d/0Bz6x7k-VkpUJbGlQenRjM2hUMnM/viewto get into the Android Recovery menu and have wiped the system cache and attempted to apply the the update through ADB. This is where I get into a jam....
So at the top of the recovery screen is the following info google/volantisg/flouder_lte followed by 7.1.1/N4F26T/3687331. In the guide I had linked above, it states that the rescue OTA has to be either the same or newer then the one already installed.
I've been hunting around looking for a factory image to get this reloaded with and have tried a couple but I keep getting an error when I initiate the sideload.
First one I tried was one labelled volantisg-n4f26t-factory-ac2cfe5f.zip (obtained from .androidfilehost.com/?w=file-thanks&fid=457095661767144943&mid=71&download_id=1rrd6dg6fc8m7sj0ukedl8p4g1&tid=1496062844&hc=f297e8f2c668115670381bbe4553c77544435525e6d9647a3361e131dc576cff), which after starting the sideload spits back this error:
E: footer is wrong
update package verification took 1.0 s (result 1).
E: Signature verification failed
E: error: 21
Installation aborted
So as suggested on another forum, I verified the MD5 checksum, swapped usb cable and tried a new usb port. SAME. Tried on a new computer, SAME.
Decided that maybe that image just wasn't for this tablet and went looking for a different one. Found theseslimroms.org/#/device/flounder_lte, and downloaded the 7.1.1 build 0.19 zip and tried to apply it. Got a bit further but ended up getting this error about 26 seconds into the transfer:
E: Failed to verify the whole-file signature
Update package verification took 26.3 s (result 1)
E: Signature verification failed
E: error: 21
Checksum matches whats listed on the website, tried the 7.1.2 build 0.25 and again get the same result. So I'm not sure what is stopping me from loading these images on whether it's the wrong images, some hardware issue, or something else.
Any help would be appreciated
Related
So I'm trying to get my device back to stock so I can ship my device to someone I sold it too but somehow I'm running into issues.
I installed Terrasilent kernal and custom rom on my US 4.0 way back last spring and never had to connect my device to a computer since. Well now obviously I have to and am trying to do it off a new laptop I recently purchased.
My steps so have gone like this.
1. Downloaded and installed Samsung Drivers
2. Downloaded and installed C++ Redistrubiutable from: http://www.microsoft.com/en-au/download/details.aspx?id=30679
(I only got the bottom one. Did I need all 3?
3. Downloaded Latest Heimdall
4. Ran zadig and updated the one Samsung device that showed up
5. Ran Heimdall and loaded the pit and recovery files from this thread http://forum.xda-developers.com/showthread.php?t=1531850
But every time I get some sort of error.
The latest error being
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
After trying reinstalling drivers and such I've also ran into this error
error: failed to access device. libusb error: -12
Am I missing a very simple step? Somehow even though Heimdall won't flash anything I've also managed to get my device soft bricked.
Sadly I don't remember having such issues when I originally rooted my device and flashed it. Any ideas? I'd really love to get this device shipped out to the person it was sold to.
mewrius said:
So I'm trying to get my device back to stock so I can ship my device to someone I sold it too but somehow I'm running into issues.
I installed Terrasilent kernal and custom rom on my US 4.0 way back last spring and never had to connect my device to a computer since. Well now obviously I have to and am trying to do it off a new laptop I recently purchased.
My steps so have gone like this.
1. Downloaded and installed Samsung Drivers
2. Downloaded and installed C++ Redistrubiutable from: http://www.microsoft.com/en-au/download/details.aspx?id=30679
(I only got the bottom one. Did I need all 3?
3. Downloaded Latest Heimdall
4. Ran zadig and updated the one Samsung device that showed up
5. Ran Heimdall and loaded the pit and recovery files from this thread http://forum.xda-developers.com/showthread.php?t=1531850
But every time I get some sort of error.
The latest error being
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
After trying reinstalling drivers and such I've also ran into this error
error: failed to access device. libusb error: -12
Am I missing a very simple step? Somehow even though Heimdall won't flash anything I've also managed to get my device soft bricked.
Sadly I don't remember having such issues when I originally rooted my device and flashed it. Any ideas? I'd really love to get this device shipped out to the person it was sold to.
Click to expand...
Click to collapse
Did you installed the drivers while you were in download mode? Maybe this would solve your actual issues. Also if you used a different port, you need to reinstall the drivers once again AFAIK.
My Zenfone 5 received today an OTA update (3.24.40.78) and I authorized it, but it went into a bootloop, maybe because it was rooted (I had the 3.23.40.52 version until now).
I couldn't risk not backing up some of the data I had in the internal memory, so I decided to try TWRP and it really helped on that issue (doing a backup).
But now I am stuck with a (soft) bricked device, and I really (!!!) need help with it.
I also have tried factory resetting, of course, but all it does is enter the bootloop again.
For some reason, TWRP sideloading is not working on my computer: the device is properly recognized in all modes but sideloading, it just vanishes, then comes back as a USB-connected device again when I mount it or go into bootload/droidboot. I tried updating drivers, uninstalling and reinstalling drivers and devices, etc., but no good. So instead of sideloading I went for the "install" option in TWRP (after copying the files to the internal memory, of course). But here is the bad part, I have tried four different versions and none work:
2.22.40.54: it shows "Device image SKU:" and nothing comes after that, then states "OTA image SKU: WW" (my device is WW!), then gives the following error:
Code:
assert failed: getprop("ro.build.asus.sku") == "WW"
return code 8
5.3.3.3 [i.e., trying to downgrade from Lollipop to Kitkat]: approximately the same error. It also leaves blank after "Device image SKU:" and, after stating "OTA image SKU: WW", it says "Please use the right SKU for updating".
3.23.40.52 [i.e., trying to go back to the version that was installed until today]: it says "Only higher than Android 4.4.2 20150409 image version can upgrade to Android 5.0" (but I was already on 5.0!).
3.24.40.78 [i.e., trying to properly install the latest version, that bricked my phone]: the error is "Only Android 4.4.2/Android 5.0 20150522-20151001 image version could upgrade with this package".
On all four cases it ends saying there as an error executing the updater binary in the chosen zip file.
My device was always WW, but I even tried tried to "change from TW" to WW by flashing fastboot and recovery img files from one of the zips, but all I got was a dead android robot logo, so I installed TWRP back again.
Please help...
Hello, excuse my English but I'm Spanish and I used the translator, I hope someone can help me, it is that I have a fova orange and tinkering delete accidentally the launcher or something, the issue is that the battery alone carrying 50% and I made a reset from recovery and the result was catastrophic lol, to turn all black was seen and only the time and the battery appears, unfold the notification menu and just have no access to anything, I say I was root with kingroot but not There is no backup.
I tried everything:
1- from the factory recovery can not install an update that I found in the forum because I E: error in /tmp/sideload/package.zip (status 7), as original rom also gives me another error and this in CPB format.
2- from adb I can not because I have usb debugging enabled in fastboot mode and I did not recognize the PC and can not find anywhere drivers (ignition normal if recognized) plus I guess you also need the usb debugging.
3- I tried from the same phone but heard nothing but notifications can not be accessed.
Well that's all lol friends if anyone has any formulation would appreciate.
Cheers
sebas1979 said:
Hello, excuse my English but I'm Spanish and I used the translator, I hope someone can help me, it is that I have a fova orange and tinkering delete accidentally the launcher or something, the issue is that the battery alone carrying 50% and I made a reset from recovery and the result was catastrophic lol, to turn all black was seen and only the time and the battery appears, unfold the notification menu and just have no access to anything, I say I was root with kingroot but not There is no backup.
I tried everything:
1- from the factory recovery can not install an update that I found in the forum because I E: error in /tmp/sideload/package.zip (status 7), as original rom also gives me another error and this in CPB format.
2- from adb I can not because I have usb debugging enabled in fastboot mode and I did not recognize the PC and can not find anywhere drivers (ignition normal if recognized) plus I guess you also need the usb debugging.
3- I tried from the same phone but heard nothing but notifications can not be accessed.
Well that's all lol friends if anyone has any formulation would appreciate.
Cheers
Click to expand...
Click to collapse
Do you have a custom recovery ? If yes then making a flashable zip of a launcher and flashing it will solve your problem
sdeepb said:
Do you have a custom recovery ? If yes then making a flashable zip of a launcher and flashing it will solve your problem
Click to expand...
Click to collapse
The recovery is the original.
Thanks for your answer.
sebas1979 said:
The recovery is the original.
Thanks for your answer.
Click to expand...
Click to collapse
Is your stock recovery capable of flashing non OEM zips ?
I tried to install zip original and non-original and always gives me errors and similar errors signature except an update that gives the following error :
"/system/app/logkit.apk" has unexpected contents.
E:Error in /tmp/sideload/package.zip (status 7)
sdeepb said:
Is your stock recovery capable of flashing non OEM zips ?
Click to expand...
Click to collapse
I tried to install zip original and non-original and always gives me errors and similar errors signature except an update that gives the following error :
"/system/app/logkit.apk" has unexpected contents.
E:Error in /tmp/sideload/package.zip (status 7)
Guys,
Been struggling with my Vertu for a long time and thought of bringing it here.
Basically, im trying to reinstate the Firmware on my Vertu and looked at this link.
Rooted the phone successfully via KingoRoot
I am able to get to the point where I have the drivers and the flashtool ready.
1. Consistently I found an error while I tried to mount the "scatter file" but then I saw a video where someone opened it and added ## in the first line and mine loaded correctly.
2. Now when I try to run the update, it gives me a BROM error S_INVALID_BBCHIP_TYPE(0x3EB)
OR Failed to get PMT Info
Any idea how I can get the Firmware loaded ?
Can someone please try and help this guy get his very expensive phone working.
https://www.google.com/search?q=BRO...nt=ms-unknown&sourceid=chrome-mobile&ie=UTF-8
Hi
Unfortunately, I have forgotten the six-digit PIN number for my Amazon Fire 7 Tablet and ADB debugging is not enabled. I have some data on it that I do not want to lose so I don't want to do a factory reset. Does anyone here know how I can retrieve my data?
I have tried installing Aroma File Manager on it using "apply update from ADB" but it produced the following errors:
"E:footer is wrong
E:signature verification failed
Installation aborted."
Thank you very much.