First time poster, but thought I'd share how I managed to fix my problem, in hope that it helps someone else out.
I recently received the OTA Marshmallow update for my Stock Nexus 9 (unrooted and locked bootloader), but unfortunately it didn't work, and threw me into "bootloop" where it continually tried to apply the update but failed. First off I followed instructions to clear the Cache, which only made the problem worse, as all the tablet would do then was boot into the “swirling colour dots” and do nothing else until eventually the battery died.
After reading several forum posts I discovered that the usual solution is to flash via fastboot, however on a Nexus 9 you need to unlock the bootloader by activating "Enable OEM Unlock" from within Android. As I'm running a 100% Stock Nexus 9 I had never done this, so couldn't flash it.
Eventually though, after having an absolute nightmare trying to get it to work again, I found a working solution! Just use "Apply update from ADB" under Recovery, along with the correct update image!
A lot of what's in the steps below is likely to be known to most of the community, but I’ve tried to keep the steps extra simple so anyone can pick this up.
Steps:
1. Reboot into HBOOT (Hold down Volume Down + Power Button).
2. Press Volume Down to highlight Recovery, then press the Power Button to enter it.
3. Wait until the Google logo goes away, and you should see a picture of an Android laying on it’s back. Hold down the Power Button + Volume Up (very important to hold Power FIRST).
4. On the Recovery page it lists a few details about your version at the top. Note down the 6 character identifier for your device (which is in the format of 3 text characters, 2 numeric, and another text char). For me I was running 5.1.1 before the update, so my identifier was LMY48T.
5. Find the OTA update that upgrades from your current version to the next version. For me I was going from 5.1.1 to 6.0.0 on a Nexus 9, so I searched for LMY48T on Google and found that this was the OTA update needed: https://android.googleapis.com/pack...83199e.signed-volantis-MRA58K-from-LMY48T.zip
6. If you don’t have it already, download and install “Minimal ADB and Fastboot”: http://forum.xda-developers.com/showthread.php?t=2317790 – when it’s installed let it run straight away, and leave the command prompt open you’ll need it in a min.
7. If you don’t have it already, download and unzip the Google USB Driver: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
8. Copy the OTA update file you downloaded to the folder that Minimal ADB was installed in (usually C:\Program Files (x86)\Minimal ADB and Fastboot\).
9. Back on your device use Volume down to get to “Wipe Cache Partition”, and press the Power Button to activate it. If you want to be really sure this will work you should do a “Wipe data/factory reset” too, but be aware you will definitely lose your data.
10. Use Volume up to go to “Apply update from ADB”, and press the Power Button to enter it.
11. Plug your tablet into your PC (if it’s not already). You’ll need to go to your Device settings on your PC and you should see a new device named the same as your device or possibly just “Android”. Go to the Properties of the device and force the Driver to be the ADB Google driver from the Google USB Drivers that you downloaded earlier. (There’s plenty of other longer tutorials on how to do this if you’re having issues)
12. On your PC, in the Minimal ADB Command Prompt (that you should still have open from earlier) enter “adb sideload {NAMEOFOTAFILE}” e.g. for me this was “adb sideload ab835e17c874202049463ccd916f86fede83199e.signed-volantis-MRA58K-from-LMY48T.zip”.
13. Let it run. It took less than half hour for it to install for me, and I’m now the proud owner of a working Stock Nexus 9 with Marshmallow!
So why does this work but applying the stock images via fastboot doesn’t? As far as I can see it must be due to the “signing” of the files. The regular stock Google fastboot flash images don’t include signature information (as far as I’m aware) so they’re rejected as unsafe by the locked bootloader, whereas when you run the OTA update files through ADB sideloading signatures are on the OTA update files, and your device determines that these are safe to install.
Yeah, as long as your system partition is intact, "adb sideload" is a good option. I'm not so lucky...
nothint to do with mine, it doesn't show any OS versione unfortunately.
works well
Hi,
I had exactly the same upgrade failure, despite of a clean stock Nexus 9.
I followed the procedure and it works great for me.
Thank you for this post !
FYI - You don't need to go searching for OTA files on Google. They're all conveniently posted here:
http://forum.xda-developers.com/showthread.php?t=2906492
Ok, so I found where mine said lmy48i. I downloaded the upgrade file a8f87fa059f17f2fd4cd773921e888366b1dfa0e.signed-volantis-LMY48M-from-LMY48I.a8f87fa0.zip. When adb starts sending it, it gets to about 48% and the tablet starts verifying already. It winds up erroring out with the following information:
************
system partition has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
************
Any thoughts?
Josh
gijosh28 said:
Ok, so I found where mine said lmy48i. I downloaded the upgrade file a8f87fa059f17f2fd4cd773921e888366b1dfa0e.signed-volantis-LMY48M-from-LMY48I.a8f87fa0.zip. When adb starts sending it, it gets to about 48% and the tablet starts verifying already. It winds up erroring out with the following information:
************
system partition has unexpected contents
E:Error in /sideload/package.zip
(Status 7)
Installation aborted.
************
Any thoughts?
Josh
Click to expand...
Click to collapse
The same situation, maybe have any other solutions?
I wound up calling HTC and getting an return authorization. I have to pay shipping to them. They cover shipping back to me. But the whole thing is going to wind up taking about 2 weeks. Couple days to get there, 7-10 days to fix, couple back. I haven't sent it out yet. I bought mine at BestBuy, so I was going to see if I could swap it out there first.
Josh
it doesnt show any OS version either, what can i do?
Guide works perfectly. Massive thanks.
The trick is finding the latest OTA zip. Here for the moment.
http://apk-bro.blogspot.com/2015/12/download-android-601-marshmallow-ota.html
I got it to work but I'm never buying another HTC product again. I called warranty service in the first guy refused to help me out unless I had the tablet in front of me. The second guy did help me but I'm still waiting for the RMA ticket, it still has not showed up. So when I got these instructions I managed to resurrect for my Nexus 9 which is good. Now I have a working tablet to which I'm talking to the right now, but other than that HTC still sucks ass and I'm never going to buy anything from them again. Done.
I am on MRA58N currently facing the same issue. I downloaded the MMB29K update. But on running the sideload, I am getting the message
"E: Footer is wrong
E: Signature Verification Failed
Installation Aborted"
Pls tell how to proceed
harishvr9 said:
I am on MRA58N currently facing the same issue. I downloaded the MMB29K update. But on running the sideload, I am getting the message
"E: Footer is wrong
E: Signature Verification Failed
Installation Aborted"
Pls tell how to proceed
Click to expand...
Click to collapse
By some miracle or so, my device has come out of the bootloop and is working fine now. But it is giving me this error (link below), before the boot up begins.
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
harishvr9 said:
By some miracle or so, my device has come out of the bootloop and is working fine now. But it is giving me this error (link below), before the boot up begins.
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
Click to expand...
Click to collapse
Looks like the OTA corrupted something.
Note: OTA updates only work on completely stock devices.
Backup your devices important data.
If you where completely stock without unlocked bootloader, you will need to flash stock images to get rid of that message (OEM Unlock Command will wipe your device)
corkiejp said:
Looks like the OTA corrupted something.
Note: OTA updates only work on completely stock devices.
Backup your devices important data.
If you where completely stock without unlocked bootloader, you will need to flash stock images to get rid of that message (OEM Unlock Command will wipe your device)
Click to expand...
Click to collapse
I did a stock image flash using the Nexus Root Toolkit. But the message is still appearing whenever I restart the device. Otherwise the device is working perfectly.
When I get to step 4, I don't see device identifier text. I got text in pink saying
Code:
" *** Device state - LOCKED *** "
What do I do now
Just got it back from 'repair' via HTC, if anything it's got worse, with random freezes, lock screen freeze and bootloop.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Marshmallow OTA hose your Nexus device? Just flash the N dev preview.
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.
Many Thanks!!!!
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.[/QUOTE]
Posting the above for anyone with a Bricked device from a previous Marshmallow OTA and where not able to resolve it by sideloading a Marshmallow OTA.[/QUOTE]
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
dweissinger said:
I wanted to thank you for posting this solution!! I was able to flash N onto my nexus 9 and it is working once again. I was going to post this onto a main thread so that more people can see this but i did not want to seem as if i was taking credit for finding this. You should post this there so that you can help others. Once again, I would like to thank you. I am now trying to get into the usb debugging menu to unlock the bootloader so this does not happen again but i cannot find it in this version of android.
MANY THANKS!!!
Click to expand...
Click to collapse
1. Share the link where you like, the Original Finder of this is mentioned in the link
Posted here
2. Have you enabled developer options? Or does Android N not have that feature.
Found the developer options!!
Thanks and yes I found it. I had to reboot my tablet to see the Android version. It must be a bug but I will be happy to deal with a small bug like that. Much better than a bricked tablet. The first thing I did was to enable unlocking of the bootloader in case this happens again. Fool me once but not twice..lol
Related
Hello.
Yesterday ATT finally rolled out the new update, but for me it freezes with screen where android with explanation mark in triangle.
A day before I did successfully install [PUDDING] International House of Pudding! (Unlock/root thread) Updated July 23 2011 v2.3.4 and also [Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!
After that I reverted to stock v1.2.6 and gradually upgraded to v1.8.3
On top of that the android recovery doesn't work either with vol down on reboot, same explanation mark in a triangle...
Any ideas what could be wrong?
Thank you.
PS. sorry
[email protected] said:
Hello.
Yesterday ATT finally rolled out the new update, but for me it freezes with screen where android with explanation mark in triangle.
A day before I did successfully install [PUDDING] International House of Pudding! (Unlock/root thread) Updated July 23 2011 v2.3.4 and also [Unlocked Only][Release]CWM Recovery Mod for Atrix 4G 2011-06-30 updated again!
After that I reverted to stock v1.2.6 and gradually upgraded to v1.8.3
On top of that the android recovery doesn't work either with vol down on reboot, same explanation mark in a triangle...
Any ideas what could be wrong?
Thank you.
PS. sorry
Click to expand...
Click to collapse
Hey [email protected],
There is no problem with your recovery menu. When you see the Android with the exclamation mark, you are in recovery mode. just touch the screen right above the Search button, which turns out to be the "Hide" function, and you'll see everything show up! Neat-o, right? =] Too bad CWM isn't touchscreen-capable =[
What probably happened for you is that you failed the pre-test. When they install an OTA update, it looks to make sure that certain apps are still there and makes sure no illegal mods are added to your Atrix. If you remove bloatware using Titanium or have root or you modded system files, you'll run into an error trying to update because you failed the pre-test. The best way around that problem AND the solution to upgrading without deleting anything is here. Use the Automated Update for PC Users, which will bypass this check. This was made for the sole purpose of those who don't want to lose their data, however, you'll be more likely to encounter strange bugs if you do upgrade this way. I suggest backing up your SD card before you do anything, perform this update, and then do a factory wipe. I know it's annoying because you have to re-input all of your info and stuff, but this is pretty much the only guaranteed way that about 95% of it will function as it should.
Hope that helped =D
~jojojohnson7410~
jojojohnson7410 said:
Hey [email protected],
There is no problem with your recovery menu. When you see the Android with the exclamation mark, you are in recovery mode. just touch the screen right above the Search button, which turns out to be the "Hide" function, and you'll see everything show up! Neat-o, right? =] Too bad CWM isn't touchscreen-capable =[
What probably happened for you is that you failed the pre-test. When they install an OTA update, it looks to make sure that certain apps are still there and makes sure no illegal mods are added to your Atrix. If you remove bloatware using Titanium or have root or you modded system files, you'll run into an error trying to update because you failed the pre-test. The best way around that problem AND the solution to upgrading without deleting anything is Use the Automated Update for PC Users, which will bypass this check. This was made for the sole purpose of those who don't want to lose their data, however, you'll be more likely to encounter strange bugs if you do upgrade this way. I suggest backing up your SD card before you do anything, perform this update, and then do a factory wipe. I know it's annoying because you have to re-input all of your info and stuff, but this is pretty much the only guaranteed way that about 95% of it will function as it should.
Hope that helped =D
~jojojohnson7410~
Click to expand...
Click to collapse
When I touched the screen above the search button, I see the source of the error is "/system/app/swype.apk
so I imagine it is due to updating swype cuple of times and as far as I remember, in the first update i had to remove 2 system files to make it work.
This will help fix your issue.
1. Download the Motorola Drivers HERE if you haven't already, and install. (Link is to the 4.9.0 version, there is a newer one, but someone has said it has issues) If you would like to try the latest version, you can obtain them directly from Motorola Here.
2. Download RSDlite 5.3.1 HERE and install
3. Download the AT&T/Motorola 4.1.83 FULL SBF from this thread, unzip it and place it in a folder at C:\AtrixSBF\ (or something similar, short folder name, in the C:\ directory)
4. Plug your phone into a Rear USB port on your PC, using the OEM supplied USB cable. Set your USB option from the pull down Notification bar to None. ***For those that can't boot, power down, hold Volume Up while powering on. You should end up in Starting RSD protocol. Then continue. ***
5. Open RSDlite, wait until it recognizes you phone is attached.
6. Click on the "..." button and navigate to the SBF file you downloaded and select it.
7. Click the Start button and wait. It's good to stick around to make sure there are no errors, but it's going to take a good 20-40 minutes. DO NOT DISCONNECT anything until you see PASS next to the process you're running in the far right hand column.
Eddie Bombay said:
This will help fix your issue.
1. Download the Motorola Drivers HERE if you haven't already, and install. (Link is to the 4.9.0 version, there is a newer one, but someone has said it has issues) If you would like to try the latest version, you can obtain them directly from Motorola Here.
2. Download RSDlite 5.3.1 HERE and install
3. Download the AT&T/Motorola 4.1.83 FULL SBF from this thread, unzip it and place it in a folder at C:\AtrixSBF\ (or something similar, short folder name, in the C:\ directory)
4. Plug your phone into a Rear USB port on your PC, using the OEM supplied USB cable. Set your USB option from the pull down Notification bar to None. ***For those that can't boot, power down, hold Volume Up while powering on. You should end up in Starting RSD protocol. Then continue. ***
5. Open RSDlite, wait until it recognizes you phone is attached.
6. Click on the "..." button and navigate to the SBF file you downloaded and select it.
7. Click the Start button and wait. It's good to stick around to make sure there are no errors, but it's going to take a good 20-40 minutes. DO NOT DISCONNECT anything until you see PASS next to the process you're running in the far right hand column.
Click to expand...
Click to collapse
This did it for me. Left the SD card update on my SD card and as soon as it rebooted to clean 183 it found the update and installed it!
Thanks
Hey guys I desperately need help here. I got this Kindle Fire 8.9" years ago, and got abandoned by my Dad because we live in SEA, can't do much with it, I cannot even get the free apps through Amazon Appstore. I can use fake US CC in this matter to get the free apps but Is that even legit? I have real CC and a legit Amazon account I bought real stuffs from Amazon too back then (books, some shirts and some gadgets) but that doesn't seem to help much.
Anyway sideloading apps from Google Play don't help much since the compatibility are horrible, and sideloading the Google Playstore itself just don't work. I've attempted to install all the Playstore requirements, some installed and some spit out "Parse error - There was a problem parsing the package".
I figure I needed to convert it to a full Android. So searching around I found about "fastboot" but I'm not familiar with it. I only got my hands dirty on Odin and SP Flash Tool.
I followed the instruction here :
http://forum.xda-developers.com/kin...t-install-twrp-android-fire-os-8-5-1-t3278286
Works very well, rooted with KingRoot (which I already have offline), installed FireFlash, flashed the bootloader and recovery (100% like the instruction told me), got into TWRP, did a full backup of the current ROM and reboot. I can get it to the Carousel just fine. I attempted to flash Gapps package for ICS (gapps-ics-20120429-signed.zip) from here (found from googling around, checked the content too) :
https://docs.google.com/file/d/0B6zwjGaKK0GVUll5Sm95LWpNaDg/edit
The installation went quite well, after running Play Store, it crashes constantly. Found another tutorial on installing Google Apps on another forum, which I lost the link, so I want to attempt another Google Play install before went to CyanogenMod.
I noticed something, after each reboot, I need to re-flash TWRP and reboot. When I attempt to reflash TWRP I notice that kfhd8freedom-boot-8.4.6.img didn't have any warning anymore.
The tablet was a gift from my brother in law to my Dad. It was never been reset ever since. In fact after I installed Google Play, it still got my brother in law login in it, even though it doesn't have the Google Play store. So I figure I need to do a factory reset and start 100% fresh, just to be sure.
And this is where it went wrong. After the factory reset the device rebooted into fastboot mode. I don't know why. I see the orange Kindle Fire logo, then the screen went red then "fast boot mode" appear on screen. At this point I cannot do anything to it. Followed every power button tutorials out there, like pressing the power for 20 seconds then release then hold it for 2 seconds, or power plus volume up/volume down, no luck.
I plugged it into my PC, it shows as "Android", and below it "Android ADB". So I tried to use ADB console for it, it didn't respond. However it responds to "fastboot" commands, tried some commands from here :
http://forum.xda-developers.com/showthread.php?t=1474566&page=2
These commands works :
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
But it went straight back to fastboot mode. My guess is that the culprit is kfhd8freedom-boot-8.4.6.img.
Looking around in the forum there're so many obsolete solutions, like Kindle Fire HD First Aide download link are dead and it was intended for Fire 7.
So the questions are :
How would you recommend me to fix this? Fastboot command definitely still working from PC to my Kindle, if that is any help for this case. I really have no clue on what to do next. I only experienced with Odin and SP Flash Tool. I have no experience with fastboot.
I don't have any stock rom at hands, neither can find any googling around. Can anyone provide me with one? Just in case anything bad happen again after I fix this.
Will this work for 8.9"? Since he posted it in Fire 7 forum : http://forum.xda-developers.com/showthread.php?t=1951254
Info on my devices :
Kindle Fire Jem 8.9"
Latest stock (8.5.1_user_5159720) was installed
Rooted with KingRoot before went brick
I have no fastboot cable, but the fastboot command mentioned earlier works on regular USB (OnePlus One's stock cable)
Gapps for ICS was installed within too
I got both Windows 10 and Windows XP PCs at my hand. XP seems to recognize it better as ADB something under "android" in device manager.
I also got Ubuntu 16.04 installation, if needed.
Please help.
Thank you in advance!
Managed to boot into Fire OS
I just use fastboot to flash both kfhd8-twrp-2.8.7.0-recovery.img and kfhd8-u-boot-prod-8.1.4.bin.
After a reboot I went into TWRP, it does a few stuffs then rebooted again automatically.
Blue logo came up, then the orange logo, but it took longer than usual, I was a bit panicking. Forgot that on each first boot Android would take longer than usual.
But then kindle fire up the first time setup *phew*
First I want to get Gapps working on this device. If that working well, I'll stick with stock + GAPPS and custom launcher.
Only after that I will try CM12 on it.
I'll update on this thread later on how it goes.
Did anyone still have the stock recovery.img and boot.img?
Also after completing the initial setup my navigation and status bar went missing
The navigation bar blinks for a second then went black. While the status bar which displays wifi icons and hide the settings are missing. I cannot swipe from above at all.
With the status bar and navigation bar missing I can't do anything in it.
I still have APKs (es file explorer, kingroot, fireflash, all the ROMS like Cyanogen & TWRP) within the internal storage, but I cannot reach them.
Using silk tried to open file:/// it said "Webpage not available". I did this previously to sideload ES file explorer.
I went into recovery (power + volume up) but it went into fastboot mode instead of TWRP. And this time in "fastboot mode" it doesn't recognize either adb or fastboot commands from my PC.
I cannot even factory reset it.
What to do next?
My god, overall my impression so far? The hardware itself are near Apple premium quality.
But it looks like Amazon tried to follow Apple's footstep in term of software too.
Also this got me thinking of not having an android without any dedicated navigation buttons.
Finally SOLVED.
I forgot I can download ES file explorer from Silk. But turn out my Amazon appstore account allowed me to download it instead. Probably because my dad and brother's credentials was wiped clean from it.
I went to find flashfire.apk in my internal storage. Install it, then the unknown source popup warning appeared. Luckily it got the settings button which lead me to that particular option. After I tick it, I need to shut my kindle down, reboot then went to install it again, because there's no navigation bar available.
After it installed, turn out Kingroot's root are still intact. Kingroot's root permission pop up appeared.
Reflashed TWRP and Freedom boot. Shut my Kindle down, volume up + power and I'm in TWRP!!!
I decide I'll just go full CM this time. So, continued this :
http://forum.xda-developers.com/kind...8-5-1-t3278286
Now I'm currently updating the default Google apps from Google Play within CM 12. A little laggy but most definitely far better than FireOS.
I'll be using this Kindle for a week, I'll report here and hopefully can contribute to CM's bug report.
So far : camera, bluetooth, WIFI, GPS works out of the box. Brightness settings don't work.
Just one question, does this fastboot cable thingy "standard"? I saw one seller in my local online shop but it's for Xiaomi. Can I use it for OnePlus One and Kindle?
Oh yeah I got TWRP backup of the stock kindle, but I would still need both stock boot and recovery image. If someone kindly enough to provide me I'll be very thankful.
Checking in
Root are enabled by default, just found out about this. It got build in, barebone SU management, on which you can allow an app to have root access or not, but didn't see any comprehensive root access management like those found in SuperSU.
So installed SuperSU, told SuperSU to just update through TWRP, update binary was a breeze, all done automatically.
Watching YouTube on it was quite convenient. The screen obviously have near-retina display. Much better than viewing it on my Note 10.1 2012 obviously.
No problem browsing on Chrome.
Installed couple of other root apps, transfered it from my cheap chinese phone (Mito) using Bluetooth. All works well.
Tried to play Shooty Skies on it but it stuck on the intro screen. However on my OPO Shooty Skies refuses to run too and stuck on the intro screen. I've unlocked all characters on it I'll just wait for an update then.
Did some theming, custom boot animations works, styles applied, icons and everything applied without any problem at all.
One complain, the sound are too low, even when maxed out. Perhaps because the Dolby isn't supported by this CM yet?
My dad complained that there're too many updates after the initial setup so I use System Cleaner 2 to merge the updates into the system. The app did wonderful job on my Mito :
https://play.google.com/store/apps/details?id=com.flaki.systemcleaner2
Merged all updates into the system. If I don't do this everytime I wipe the device, the device will keep asking for updates. At least on the Gapps. It stuck at the middle, so I restart the System Cleaner 2 and it continue to do its job.
Then when I install Link2SD, which often do better job and more comprehensive apk management, weird things started to happen. It's said SuperSU are not installed. That and also couple of Google Apps. When I run Link2SD, their size is 0.
I think it's most likely caused by System Cleaner 2, couple of apps got interrupted when I merge the updated apk into the system?
So I reboot, then after I got into trebuchet, all the supposedly installed apps are gone. I don't know why. Thus I wipe everything clean again, reflash CM12, and just go into unrooted mode, update the gapps, remove my account and let my dad login using his and do whatever he want with this kindle.
Another minor update.
Since I've downloaded ICS (CM11), I figure I might just try it anyway. Since on whatever softwares I use I prefer older, stable version than bleeding edge and feature-rich but unstable ones.
Take a note I'm not saying CM12 is unstable, no problem so far, only those I pointed out in the previous post. But mostly because CM11 was marked "stable" on CyanogenMod download site.
First impression? It's snappier than CM12, and much more familiar than Lollipop. (since most devices I own still using JellyBean, with the exception of my OPO which already running Marshmellow).
My dad should be familiar with it too. Quite happy with it. But unfortunately the gapps are too outdated. It throws me server errors, and I cannot reach anything within Google Play. I can browse google websites without problem, even google play itself inside the default browser, so it's not connection problem definitely.
Updating the google play manually doesn't fix this. So any solution for this? Perhaps updated gapps for CM11/4.0.4?
Edit : eh nevermind, the Gapps provided for CM12 works with CM11. And very stable too.
Edit : CM11 for Kindle 8.9 is JellyBean 4.4, not ICS.
I guess I'll stick to CM11 for awhile then.
One more question, what does the CM12 recovery do? Can I install it alongside CM11? Is it better than TWRP?
stubbe said:
One more question, what does the CM12 recovery do? Can I install it alongside CM11? Is it better than TWRP?
Click to expand...
Click to collapse
Appears you have gone your own way completely independent of general guidance/solutions offered in the HDX forums. Seemed to work too based on your copious self-reporting. Hope all remains well; you are on an island which isn't necessarily a bad thing.
Hey Davey. Thanks for the response.
Davey126 said:
Appears you have gone your own way completely independent of general guidance/solutions offered in the HDX forums. Seemed to work too based on your copious self-reporting. Hope all remains well; you are on an island which isn't necessarily a bad thing.
Click to expand...
Click to collapse
Lol. Xda isn't my first English speaking forum so I did a search or two before I ask anything. And I've been around here quite awhile just rarely post but xda is my primary resource on mobile customizations.
I do still have couple of unanswered questions tho :
1. I still need the stock FireOS and recovery. I'm very sure I've backed it up but I probably accidentally wiped them in the process because I saved them in the internal storage.
2. Are the fastboot cables universal? This thing is hard to look for in my local stores and I can only find Xiaomi's. Will this work for every fastboot devices out there? I just found out about fastboot from flashing this kindle and I also recently find out my OPO uses fastboot as well so kinda thought it would be handy to keep one around.
3. How does CM12's recovery compares to TWRP? And will it runs fine along CM11 rom? I can try it myself but having late sleeps for days just because I bricked my kindle again isn't cool lol. TWRP does its job well. If it ain't broken I don't want to fix it. But I just want to know why @Hashcode included it in Cm12. If it's worth it I'll go ahead and install it and probably give further reports about it.
So far my dad is enjoying his CM11 powered kindle. Not sure if he finds any new bugs or not but seems that he's not complaining.
Cheers and thanks in advance.
stubbe said:
Hey Davey. Thanks for the response.
Lol. Xda isn't my first English speaking forum so I did a search or two before I ask anything. And I've been around here quite awhile just rarely post but xda is my primary resource on mobile customizations.
I do still have couple of unanswered questions tho :
1. I still need the stock FireOS and recovery. I'm very sure I've backed it up but I probably accidentally wiped them in the process because I saved them in the internal storage.
2. Are the fastboot cables universal? This thing is hard to look for in my local stores and I can only find Xiaomi's. Will this work for every fastboot devices out there? I just found out about fastboot from flashing this kindle and I also recently find out my OPO uses fastboot as well so kinda thought it would be handy to keep one around.
3. How does CM12's recovery compares to TWRP? And will it runs fine along CM11 rom? I can try it myself but having late sleeps for days just because I bricked my kindle again isn't cool lol. TWRP does its job well. If it ain't broken I don't want to fix it. But I just want to know why @Hashcode included it in Cm12. If it's worth it I'll go ahead and install it and probably give further reports about it.
So far my dad is enjoying his CM11 powered kindle. Not sure if he finds any new bugs or not but seems that he's not complaining.
Cheers and thanks in advance.
Click to expand...
Click to collapse
As noted you have gone you own way so the standard responses don't necessarily apply. Quick notes:
- there are several ways of restoring stock FireOS on this device, none clean, all with ramifications. Unless you need FireOS I would stear clear
- no standard way of restoring stock recovery; obtaining a compatible recovery image will be a challenge. TWRP is far superior
- fastboot cables do not work with this device
- I have no knowledge of CM12's recovery. TWRP gets the job done and is universal.
Davey126 said:
As noted you have gone you own way so the standard responses don't necessarily apply. Quick notes:
- there are several ways of restoring stock FireOS on this device, none clean, all with ramifications. Unless you need FireOS I would stear clear
- no standard way of restoring stock recovery; obtaining a compatible recovery image will be a challenge. TWRP is far superior
Click to expand...
Click to collapse
Ah dang. Not that much of a problem though. I just like to keep stocks ROMs around just to be safe. I won't be returning this thing to Amazon anytime soon, and I guess judging by my brief experience with the FireOS it won't be much of a use for our locals using the stock ROM if I or my dad actually decide to sell it.
- fastboot cables do not work with this device
Click to expand...
Click to collapse
Mmm... okay.
- I have no knowledge of CM12's recovery. TWRP gets the job done and is universal.
Click to expand...
Click to collapse
Ok fair enough and besides I don't go to the recovery much other than doing a backup.
Thanks Davey.
stubbe said:
With the status bar and navigation bar missing I can't do anything in it.
I still have APKs (es file explorer, kingroot, fireflash, all the ROMS like Cyanogen & TWRP) within the internal storage, but I cannot reach them.
Using silk tried to open file:/// it said "Webpage not available". I did this previously to sideload ES file explorer.
I went into recovery (power + volume up) but it went into fastboot mode instead of TWRP. And this time in "fastboot mode" it doesn't recognize either adb or fastboot commands from my PC.
I cannot even factory reset it.
What to do next?
My god, overall my impression so far? The hardware itself are near Apple premium quality.
But it looks like Amazon tried to follow Apple's footstep in term of software too.
Also this got me thinking of not having an android without any dedicated navigation buttons.
Click to expand...
Click to collapse
My Kindle Fire HDX (3rd Gen) is stuck in fastboot. After reading some forums, people don't recommend sending attempting to "recover" from the fastboot for the likelihood of bricking the device. Would you mind sharing the vulnerable bootloader + the twrp and the CM file you used? Along with the commands you used to flash. For some reason, the device isn't flashing the twrp image I have. I receive a "unknown partition" error when I try to flash twrp.
Thank you in advance.
Praxxer1 said:
My Kindle Fire HDX (3rd Gen) is stuck in fastboot. After reading some forums, people don't recommend sending attempting to "recover" from the fastboot for the likelihood of bricking the device. Would you mind sharing the vulnerable bootloader + the twrp and the CM file you used? Along with the commands you used to flash. For some reason, the device isn't flashing the twrp image I have. I receive a "unknown partition" error when I try to flash twrp.
Thank you in advance.
Click to expand...
Click to collapse
Answered elsewhere (one 48 other threads you posted to with the same question)
Stuck in Fastboot. I can flash and write and reboot, but 100% of the time it returns to FB. I had flashed freedom boot 8.46 2x. I most recently had lineage 14.1 and twrp 2.78.
Tried every tool in the book zero have worked.
UPDATE 6-9, out of fastboot, now stuck on kindle logo.
tia
KF 8.9hd jem
Here's how it started:
I was happily using the tablet (pollux_windy), when something prompted me to upgrade to 7.11 Lineage OS images. One of the things noteworthy here is that I was never able to go to recovery by pressing VOLUME_UP. I was always using adb to reboot to recovery
I installed it and used OpenGapps aroma installer to install what I wanted. I removed a few CM account related stuff
The tablet booted but was being stuck on the first screen on initial setup that displays a big LineageOS logo in green and there was no other option on it. I thought maybe the tablet is being slow and left it overnight to see if anything appears. Nope.. nothing did.
I tried a lot to go to recovery to reflash or flash something good. But as I mentioned before, I wasn't able to get into recovery by key combinations.
I tried to use Sony Companion to do a Software Repair. It kept complaining that bootloader was unlocked
I tried to use flashtool on mac to flash a stock FTF. It kept giving error (ERROR - null, ERROR - Error flashing. Aborted)
Since it looked like the only problem with using Sony Companion was that bootloader was unlocked. So I proceeded to lock the bootloader from flashtool. I believe this was where I messed up. I locked it successfully
I then proceeded to use software companion but it keeps giving me error with a small message about UEGetPhoneInfoFailure. I searched a few forum and posts but it seems that there's no solution for this (?)
I tried to unlock my bootloader again. I did it through the official method the first time and repeated it but fastboot write failed and it wasn't unlocked. Flashtool is not able to unlock it as well. Flashtool error is (Your phone bootloader cannot be officially unlocked)
I tried various versions of flashtool in MacOS and in Windows, trying to flash any FTF. I get a new error along with the one I mentioned above (-: Processing of loader.sin finished with errors)
I'm now typing this post
I'll appreciate if someone can help here.
I got this device when it first came out. I've loved it since now. It was an ace. It's not waterproof anymore because I did a few repairs on my own. But it worked flawlessly and battery life was great. I wouldn't mind saying goodbye to it as it's pretty old, but trying to revive it and have it living as it's cooler than a dead tablet
kishu27 said:
I'll appreciate if someone can help here.
Click to expand...
Click to collapse
Don't panic!
7.1.1 ROMs have some issues when reverting back to stock ROM.
Switch off device by holding VOL+Power for 5-7 sec, then read -> https://forum.xda-developers.com/xperia-tablet-z/help/flash-stock-rom-t3564623.
Rootk1t said:
Don't panic!
7.1.1 ROMs have some issues when reverting back to stock ROM.
Switch off device by holding VOL+Power for 5-7 sec, then read -> https://forum.xda-developers.com/xperia-tablet-z/help/flash-stock-rom-t3564623.
Click to expand...
Click to collapse
One thing I always practice and preach about Sony devices is not to panic .. Flash mode and Flashtool has saved my a** so many times.
So, thanks to you, I resolved the issue. I was doing the same thing but had a couple of pieces in the process that needed correction.
I let go of my Windows VM on Mac and prepped my old laptop fresh on Windows 10. Driver installation kept failing because of unsigned driver issue and bcdedit didn't do anything despite returning a success. Advanced startup worked. The second thing that might be wrong with my original attempt was the stock FTF version. 5.1.1 didn't work. I got hold of a german unbranded version on 4.1.2 and used it instead. Then reflashed to 5.1.1 and everything is golden.
Thanks again :good:
Hi all, attempted to root my phone today following this guide.
I got right up to step 9 but upon trying to reboot and launch from TWRP I began to have trouble. I've been able to access TWRP once, but after confirming install of SuperSU (step 11 here, my phone booted to the LG splash and I got the boot loop saying 'Your phone is unsecure, bootloader is unlocked' or words to that effect. Orange ! triangle.
I can launch to fastboot, or download mode. Turning on to a factory reset sends me back to a boot loop after confirming I would like to reset (leading me to believe I've not got a stock ROM in there at all).
Now when I try to flash any version of TWRP from command prompt in my ADB folder, I'm told my phone is corrupt and it won't allow me to flash.
Alternatively, trying to flash a stock ROM doesn't work either. LGUP does not recognise my model, it only shows COM Ports: [COM4, H85020s]. I've also tried using UPPERCUT but I get the following error: "Error reading from file: C:\Users\...\Roaming\Temp\F9FB5BD\TempFolder\UPPERCUT.exe. Verify the file exists and that you can access it." I've attempted running UPPERCUT from various locations, extracted.
I'm on Windows 10 and I've been trying desperately for the last 12 hours crawling through this site/ other articles for some kind of solution to give my phone SOME kind of functionality. Ultimate goal was LineageOS but now I'd be more than happy getting back to stock. I'd really appreciate any help, hope I've given enough information.
Hello, I am new here and I made a huge mistake!
I purchased Samsung Galaxy Tab S6 Lite (LTE) literarally 1-2 days ago and I wanted to root it, I had my smart phone rooted which did not have Knox protections, it was as straight forward as flashing TWRP and use Magisk via instructions I followed.
I make use of "Root" privileges a lot when using my device, I find it very important to my daily life so I decided to risk rooting it, after doing so my tablet was showing 2 errors, that its not using official samsung software and that the boot loader is unlocked, when I unlocked the boot loader using OEM Unlock everything went fine, the option was greyed out and checked afterwards.
During the boot process, it reboots 2 times and it shows a integrity error, integrity and some very long number, I am assuming its a integrity check? I have the exact matching firmware, so I flashed back the stock firmware and... the "not using official samsung software" warning disappeared, it boots me into recovery mode, I choose "reboot" and the device goes to boot looping with the same error.
I was following this tutorial: https://forum.xda-developers.com/galaxy-tab-s6-lite/how-to/howto-unlock-root-galaxy-tab-s6-lite-t4132289
But there are some things I skipped, here the exact steps I took:
Unlocking Boot Loader:
Followed all the steps from 1 to 4 but I skipped the 5th step entirely, the step where it asks you to mess with firmware date and twrp, I did none of that, I will mention that when I was looking for stock firmware to download before doing anything, I was not able to understand the CSC so I didn't know which firmware to exactly use until a software update came up which told me the exact firmware, I accepted the update and download that stock firmware, because my firmware was updated I didn't think that following the few steps of the step 5 would've done everything as I was already off the path.
I didn't do the 6th step as I just checked of the OEM Unlock is greyed out and still checked in the "developer options" section, I assumed that it was a success, not to mention the boot loader unlocked warning that was showing up and yes, all the data was erased and was forced to go through the setup process again as expected.
Root the tablet:
1. I have downloaded the firmware as it says not just for the purpose of rooting, the firmware that the software update told me about, this is the firmware I downloaded, the firmware is a exact match, everything is matching: https://samfrew.com/download/Galaxy__Tab__S6__Lite__-LTE-__/xs5l/SEB/P615XXU3BTI3/P615OXM3BTI3/
2. I follow all the steps from 2 to 11 from here.
3. When I reached step 12, I went to download mode and I look for any messages regarding it only allowing for official samsung images, but I saw no such message, didn't really pay attention to anything else, I just glossed over things, considering there was no such message I assumed that KG/RMM state was good, don't know what it was but it might not have been "prenormal" because there was no message regarding official samsung images, from here I falshed the boot.tar file like in the instructions, that lead me to my current problem I mentioned at the very start of this post.
4. There was no step 13 as I can't boot into android due to "integrity" error I have, right now I have my tablet turned off (thank god I can do that) via the recovery that shows up after flashing stock firmware.
Addition Info:
1. I don't have any data to lose, if I need to do a factory reset or something of that sort, I have no problems doing that.
2. As I mentioned at top, I do have a stock firmware downloaded from this link here: https://samfrew.com/download/Galaxy__Tab__S6__Lite__-LTE-__/xs5l/SEB/P615XXU3BTI3/P615OXM3BTI3/
3. The tablet is: SM-P615 (Samsung Galaxy Tab S6 Lite (LTE), I bought the LTE so I could use it as my phone)
4. At the download mode, the OEM (Boot Loader) state is set to NO and the FFS (I don't remember if its FFS exactly at the moment, something FF I believe, I don't want to turn on my tablet at the moment) was set to NO.
5. The KG (No RMM mention that I could see anywhere) state is showing up as "Checking..."
What do I need to do to fix my tablet? do I need to wait for 7 days? if so how do I do so, like does leaving my tablet off count or not?
PS: I am a self-thought experienced low-level windows programmer, I've been doing programming for over 10 years now, never have worked with Android development but I can attempt to build something from source if necesarry, I know very little about Linux OS as I purely work with Windows and use Windows for everything including servers.
I have done some research regarding that "integrity" error and I can't find any screenshot in google images that matches how it looks on my screen, but there are a lot of them quite similar to it, which basically says "verification failed, factory data reset your phone", in my case I don't have that message, it just says "integrity", but when the boot looping stops and shows that failure I do have 3 options, "try again" and "Factory data reset" and the 3th one I don't remember, I am suspecting that this could be my problem! I believe the samsung just changed the way that particular message is shown (visual change), so I just need a factory data reset and it will work, most likely with the rooted boot.img file! I will attempt this after a few hours of this reply, I may have panicked too early.
The issue has been fixed
Well this is surprising, I was about to do the factory reset but before doing so I decided to flash the same magisk patched boot.img file, when I flashed I saw seeing those 2 warning messages as expected, I was expecting for it to fail after 2 boot loops so I can do the factory reset as intended but on the 3th boot loop the tablet booted up! I was brought at the android setup screen, once I was done with that I checked the OEM Unlock, it was still checked and greyed out, downloaded Magisk Manager and to my surprised it worked! Magisk Root latest version is installed and working, it asked me to allow magisk do some "additional setup", the tablet booted up perfectly fine after that "additional setup", I check root privileges using "Root Checker" and it worked, I have root privileges! I most likely have panicked too soon, sorry for wasting your time! Hopefully this post will be useful to someone in the future looking to root their tablet.
My assumption of what happened: When I flashed the stock firmware AP a second time so I can turn off my tablet, it most likely did a factory reset without me knowing, so when I flashed magisk again before letting it try boot up again, the tablet booted perfectly fine because factory reset has already occured, which brought me to the android setup screen.