Database Develop

Problem when initially installing Android on HP Touchpad

Late last night I went to fix a touchpad that was handed to me, was told that the Android install was started, but had messed up. If I fixed it I could keep the touchpad.
So, i wandered over here and followed RolandDeschain79's how to install android thread, using the novacom,exe route with ACMEUninstaller2 and ACMEInstaller5. After running both of these (and placing the Cyanogen9 Mod on the tablet... i followed the instructions to the T). I got Android to run on it. BUT there was a problem! I got a bunch of notices @ initial startup, (Like 3). I don't remember what the other 2 were, but the biggest problem was the android keyboard would not function. Thinking that it would fix it, I went ahead and re-did what I had already done, running ACMEUninstaller2 and ACMEInstaller5. When I was in the middle of doing this the battery died (wish the stupid thing would just feed off power from my PC when it's plugged into it but apparently not). Now, I'm stuck in a bootloop (i think).
what does it do?:
The WEBOS boot screen, the little circle w/ HP in it? It just sits there. Sat there the entire time it was plugged in, didn't show me it was charging or anything. When I force it to shut off (hold power button and home key) it'll sit there 4 10 seconds or so, then turn itself right back on. I CAN GET INTO RECOVERY MODE however.
What I have done since then:
1. left it sit on the charger for about 7 hours... should be fully charged I hope.
2. Re-ran ACMEUninstaller2
3. Re-ran ACMEInstaller5
my thoughts were that if I can get an older ROM to work on it, I can upgrade to the most current from there.
HELP!!!!
Any ideas would be appreciated. This is the first tablet I've messed with, actually the first tablet I've owned and I'd really like to fix it...
Thanks in advance!

The easiest and most simple means of installing Android is with TP Toolbox. Follow the advice and instructions in the developers forum, you will have to do some reading to understand what you are doing.
I also am listing a link that I think is clear on the install:http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
As for the ROMS, there are a number to choose from. I have jcsullins installed on several TP's as well as pac-man ROM on another. Please take your time to read and decide.
Also, using toolbox will require that you use the naming convention for gapps as outlined in the toolbox thread.

Thank you. I followed the instructions on that site and the touchpad is working excellent.... Minus one glitch thus far: the camera works on boot, but as soon as you go to take a photo the whole screen digitizes and the touchpad loses connectivity with the camera. Is there an easy fix for this?

What ROM are you using? Also, which gapps did you install? Please be as specific as possible.

The ROM I am using is cyanogen 11 and I downloaded the gapps from the same page. The tablet upgraded itself last night and after that everything works great. It said something like upgrading apps, and reinstalled all the apps I had put on it. I'm playing with it as much as possible, making sure it acts like it should.
Thanks 4 all the help thus far

more issues
okay guys I am using invisiblek's cyanogen 11 and gapps... still have an issue with the camera I randomly acting up. it will work and then it won't. I have no clue where to even start with this. the build is from June of 2014. I do have an update available, I don't know if that will fix it but I do not have my laptop available at this current moment, so I cannot try it. Any ideas?

Are you reading the posts in the forum thread for that particular ROM? Other people using it may have encountered and fixed the issue.
I would invite you to read information about the various ROMS in the developer section as issues such as you are describing are
usually addressed and fixes or work arounds are presented.
I do not use the particular ROM you have installed but run other ROMS on several touchpads and do not have the problem you describe.

like an idiot I have not read the other threads regarding this particular CyanogenMod... I will look into them.
Thank you.

OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.

Greasemonkey50701 said:
OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.
Click to expand...
Click to collapse
You can't bypass moboot, and what you're proposing is going to ultimately cause you problems. But if you must, the easiest way to do what you want is to reduce the moboot timeout so that it goes directly to boot quickly. Create (if it's not already there) or edit (if it is) a file named moboot.timeout and put the number of seconds you want moboot to wait before booting CM. You can do that with a root browser like ROM ToolBox lite, or you can do a terminal session and type in:
Code:
su
mount -o remount,rw /boot
cd /boot
echo "1" >/boot/moboot.timeout # will set timeout to 1 sec (defaults to 5)
sync

What problems would this cause? Call me stupid (and I am sometimes) but i really don't forsee any problems caused by doing this...

I think Shumash already answered your question.
You need moboot to boot into Android.
Android is Linux based and Linux requires the use of a bootloader.
The best you can do is to shorten the time out before it boots.
In spite of the best advice given to you...it is your touchpad and you are free to do what you choose.
Even if that means borking it for good.

OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.

Greasemonkey50701 said:
OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.
Click to expand...
Click to collapse
You were clear enough, but seem to have some misunderstanding of what the sequence is. On boot, moboot times for a default 5 seconds and then automatically boots into Android, unless you screw with it by touching buttons or making selections. If you want it to do that faster, change the timeout as I suggested. You do not need to take anything off of it, and in fact, doing so will cause you grief eventually. If you take CWM off, and want to update your ROM, create a nandroid backup, clear the caches, or do any other low level stuff, you won't be able to. If it's booting into CWM (which you haven't said it does yet), then the moboot.default file has been changed. It should contain the word "CyanogenMod" (w/o the quotes) to boot directly to CM/Android. Use a root browser to edit or recreate it.

[Q] Constant Rebooting

I recently bought Kindle HD 7" (Tate) from Amazon used for $53. I went through the process off rooting/installing TWRP and then installing CM11. The tablet works fine when plugged in and charging, even works well unplugged until it gets to the mid 80% range and will just shut off. I can turn it back on and it will boot back to the OS and then as soon as I unlock it will shut off again. It only seems to have these issues once booted into CM, for example if I boot to TWRP and leave it on (and unplugged) it will not shut off. Just wondering if anyone else has run into similar issues?

b_rob32 said:
I recently bought Kindle HD 7" (Tate) from Amazon used for $53. I went through the process off rooting/installing TWRP and then installing CM11. The tablet works fine when plugged in and charging, even works well unplugged until it gets to the mid 80% range and will just shut off. I can turn it back on and it will boot back to the OS and then as soon as I unlock it will shut off again. It only seems to have these issues once booted into CM, for example if I boot to TWRP and leave it on (and unplugged) it will not shut off. Just wondering if anyone else has run into similar issues?
Click to expand...
Click to collapse
Try upgrading to a later version of CM. Did it do it on the stock ROM?

I've had issues with cm being finicky. Try the beanstalk build by @BuQQzz

Ph0enix_216 said:
Try upgrading to a later version of CM. Did it do it on the stock ROM?
Click to expand...
Click to collapse
I have tried various CM builds (M9, M10 and nightlies) with the same issue. I didn't have the issue on the stock ROM, however I did not use it on stock, as soon as I got it I went through the process of rooting and flashing CM.
Rushead said:
I've had issues with cm being finicky. Try the beanstalk build by @BuQQzz
Click to expand...
Click to collapse
I'll give that a try and see how it goes

Nexus 6 shows 4,000% battery life after root?

I got my Nexus 6P for Christmas, and I decided to root my Motorola Nexus 6 from last year. I've been waiting to do this for a few months, and was excited to finally enable several of the options I couldn't otherwise enable (such as double tap to wake and auto rotate on the lock screen and Google Now launcher). About an hour ago I got around to rooting and done so with little issues. It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. I rooted following the steps in a YouTube video by DroidModderX and the device is running perfectly fine. The device hasn't died yet, and I'll be interested to see when it will die. The battery life seems to fluctuate between 4,001% and 4,204% (Those two figures being the highest and lowest figures respectively). Rebooting does not fix this error.
I know it's not a massive problem, but I'd like to know what's causing this issue and how to resolve it. I haven't flashed any custom OS's on my phone, I'm still running stock Android 6.0.1 Marshmallow with the latest December security patches. The device is carrier unlocked also. How can I fix this?
Thanks,
Eamonn.

sonic2kk said:
It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. being the highest and lowest figures respectively). Rebooting does not fix this error.
Click to expand...
Click to collapse
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.

sansnil said:
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
Click to expand...
Click to collapse
Ah, thank goodness. I'll re-root tomorrow and post back if I have any problems. Thanks!

Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.

Why did you need root for the Google now launcher?

mikeprius said:
Why did you need root for the Google now launcher?
Click to expand...
Click to collapse
What do you mean? I can run the Google Now launcher perfectly fine. Root works fine as well. The problem isn't with the Google Now launcher but with the warning on boot. I didn't need to root, I chose to. Am I misunderstanding?

Your original post made it seem like you need root for double tap to wake and Google now launcher.

sonic2kk said:
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24269982087021512 gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: https://www.androidfilehost.com/?fid=24340319927534323 (flash this also after you flash the bootstack).

HueyT said:
(removed url) gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: (removed url) (flash this also after you flash the bootstack).
Click to expand...
Click to collapse
Worked perfect. That got rid of the corrupt message. One last question: (This is the last one, I swear! ) Are you saying that Android Pay won't work at all after rooting or that it wouldn't have worked if that screen had have appeared on boot? I hope to use the service if and when it comes to the UK.
mikeprius said:
Your original post made it seem like you need root for double tap to wake and Google now launcher.
Click to expand...
Click to collapse
Ah, sorry for the confusion my friend ?

I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...

orangekid said:
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
Click to expand...
Click to collapse
Haha if it wasn't a display error I might have (Though it would have only been like 3 days on the Nexus 6 )

Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6

Dalek Caan said:
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Click to expand...
Click to collapse
Sorry, I don't remember where I got the updated files now. I do remember sticking to looking on XDA and not just searching randomly online, maybe you could try searching the forums?

is it possible to root with chainfire root files. I did a clean install of the January security update, then flashed the latest boot.img from chainfire then flashed SuperSU 2.66.zip through TWRP, but im still getting this. I received this same issue with the last patch. Im at the point where it isnt worth rooting. Any help would be appreciated.

Downgrade back to marshmallow

So can't check "allow OEM quick" on N.
Already opted out of developer preview thru the site, and 4 days later, still no ota back to MM. Suggestions?
I thought to just fastboot twrp and try to flash a stock rom to allow unlock then start from the beginning but wanted opinions first.
Sent from my Robin using XDA-Developers mobile app

sookieball said:
So can't check "allow OEM quick" on N.
Already opted out of developer preview thru the site, and 4 days later, still no it's back to MM. Suggestions?
I thought to just fastboot twrp and try to flash a stock rom to allow unlock then start from the beginning but wanted opinions first.
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
well, to flash stock, you dont use twrp, you use fastboot while youre in the bootloader. and in N, allow oem unlock is automatically enabled.

It isn't tho
It i tried OEM unlock and it didn't work. :-/
Sent from my Robin using XDA-Developers mobile app

sookieball said:
It isn't tho
It i tried OEM unlock and it didn't work. :-/
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
how? did you do fastboot oem unlock?

Maybe you've already tried this, and I don't know if it will work, but have you tried re-enrolling and unenrolling in the hope that it will jog the revert mechanism into life?

I have tried enrolling and unenrolling a few times....
No dice.
Sims,
In fastboot... fastboot OEM unlock. Then error.
Sent from my Robin using XDA-Developers mobile app

sookieball said:
I have tried enrolling and unenrolling a few times....
No dice.
Sims,
In fastboot... fastboot OEM unlock. Then error.
Sent from my Robin using XDA-Developers mobile app
Click to expand...
Click to collapse
you pribably cant oem unlock while on N then. that probably why they made it unavailable. im not on N now, so cant test.

What about trying a sideload of the full OTA? I thought (I might be wrong) that it's independent of a locked bootloader.
https://developers.google.com/android/nexus/ota#instructions
It's worth a shot, especially as it doesn't overwrite your data.

On a related note, I'm on preview 3 - battery drain when idle is higher than what it was on stable M, so thinking about reverting back to M.
1. To avoid a factory wipe, can I just flash the img files from the stable M (skipping userdata) on top of the preview 3?
2. If so, to avoid getting the N preview update notification, I guess I will need to un-enroll from the beta program. Will that cause an OTA to be sent back to my phone (causing factory wipe as described on the beta page)? Or does it recognize that I'm already on 'M' and skip the OTA?
3. Before I do this, is it possible to flash the radio only from the latest "M" image on the "N" preview? (could that help with the drain when idle?)

Did you not like my previous answer...?
http://forum.xda-developers.com/showpost.php?p=66961421&postcount=104

dahawthorne said:
Did you not like my previous answer...?
http://forum.xda-developers.com/showpost.php?p=66961421&postcount=104
Click to expand...
Click to collapse
LOL! Yes, I did! And thank you for that as well - the part that I didn't understand (and unless I missed it in your response, I don't think we talked about in that post) was - since I'd still be enrolled in the preview/beta program, how do I get out of the program, without getting factory reset.
(I do have a nandroid backup as a last ditch option - trying to do this the 'clean' way first)
The preview is working well for me as well - skype is the only app giving me grief, but I can live with that. The battery drain on idle seems to be significantly higher than what I encountered with "M" stable. With barely any usage this morning (screen on for 11 minutes), my battery is at 77% (full charge and off the charger at 10 pm last night). Cell Standby is the the highest drain (6%). Phone idle and Android system tied for 2nd place at 3%.
With the latest M build, I'd be at over 90% battery remaining (with similar usage).

You're right on all counts...
I think the answer to your wipe question is that you'd have to agree to do it - if you unenrol and have already reverted manually to M, the downgrade OTA may be downloaded (though from my experience, as I said, I think the developers are smart enough to recognise that it's a waste of time and even that won't happen) but you would still have to push the button to accept it. They won't unceremoniously dump it on you without your permission.
And the battery drain... I was wondering if it was my imagination, or maybe just that my phone is a year old (I got a replacement last May) and the battery's a bit tired, but I've noticed that the percentage drops almost before my eyes. I have Battery Bot Pro showing my percentage figure on my status bar, and it seems to me that every time I unlock the phone another one or more percentage points have gone. It went from 97% this morning to 77% in a couple of hours, and I recharged it before I went out to work - it's now already down to 75% and falling. Like you, I'd expect it to be a clear 10% or more better than this over this period.
Looks like Google have a bit more work to do on their power management...
Edit: And in the 5 minutes since I wrote this, with the phone sitting beside me, screen off, nothing running, it's already down to 74%. Not at all impressive. Despite being relatively happy with it, I may have to renege on my previous comment that I can't see myself reverting to M.
And before you ask, I'll be reverting using my TWRP backup of M which I took immediately before I installed N...

Thank you
I'll wait for the June security update (factory image) and install that directly (skipping userdata). If that fails, I'll revert to the TWRP backup. (restoring TWRP on my old N5 has given me grief in the past, so going to avoid that if possible)
Edit: maybe I'll try flashing the radio from the May image onto "N" and see if that helps. The battery drain appears to be radio related.

Done. No problem at all. TWRP took about 12 minutes to restore 7GB of data, then a rather nerve-racking 5 minutes with the Google quad-icon swapping bits, and I'm back to MOB30I.
Seven updates waiting; BBC Radio, Skype, Google Drive, Sygic, all the broken apps working again, still have root.
Welcome back, old M world...
And if you're thinking of restoring M early next month, I'd give the OTA version a try. Just out of curiosity I sideloaded the MOB30H OTA on my Nexus 5 a few days ago, and it worked flawlessly without wiping any data. That's what I'll be doing on my N6 in June.
I've also just unenrolled from the Beta program, and checked for a system update. Exactly as I thought, "Your system is up to date" on MOB30I. I know that the OTAs have been slow for some people, but I don't expect to see the revert OTA - I'll post in this thread if I ever do.

dahawthorne said:
And if you're thinking of restoring M early next month, I'd give the OTA version a try. Just out of curiosity I sideloaded the MOB30H OTA on my Nexus 5 a few days ago, and it worked flawlessly without wiping any data. That's what I'll be doing on my N6 in June.
Click to expand...
Click to collapse
Would the fact that I'm rooted cause any issues with sideloading the OTA? (I realize the new OTA is essentially a full image, so it should just overwrite the system, and I'd have to reroot after that)

No problems at all, no. My N5 was rooted & encrypted, and the OTA slid in easily. As I said in another thread, it boots into TWRP but the OTA is designed to handle that. I installed TWRP again anyway, probably pointlessly but just to be on the safe side, and then used it to install SuperSU 2.74.
Easy as pie...

I unenrolled, got a prompt for system "update" back to MM, it downloaded, and now I am going on 30 minutes on the install part....been stuck on the reboot screen with 4 colorful circles....
How long does it take to re-install MM? TIA
EDIT: Decided to hold down power button for about 5 seconds and it rebooted to setup screen

dahawthorne said:
And the battery drain... I was wondering if it was my imagination, or maybe just that my phone is a year old (I got a replacement last May) and the battery's a bit tired, but I've noticed that the percentage drops almost before my eyes. I have Battery Bot Pro showing my percentage figure on my status bar, and it seems to me that every time I unlock the phone another one or more percentage points have gone. It went from 97% this morning to 77% in a couple of hours, and I recharged it before I went out to work - it's now already down to 75% and falling. Like you, I'd expect it to be a clear 10% or more better than this over this period.
Click to expand...
Click to collapse
I ended up flashing the radio (only) from MOB30I on to the N preview, and so far, the battery life on idle is back to how it was on M. I think I have a reason to stick on to the N preview a bit longer now
banditsw said:
How long does it take to re-install MM? TIA
Click to expand...
Click to collapse
Looks like you got it sorted out, but just for future reference, the reason it took long is because it essentially factory reset your phone - a factory reset with full wipe on the encrypted N6 cane take 20-30 minutes.

I'm impatient, me, so by the time I read this I was already back on MOB30I, but in any case I'm happier to have all working apps without the rash of library errors and force-closures. Interesting thread...
But we never heard back from sookieball after I suggested a sideload: http://forum.xda-developers.com/showpost.php?p=67013821&postcount=8

dahawthorne said:
But we never heard back from sookieball after I suggested a sideload: http://forum.xda-developers.com/showpost.php?p=67013821&postcount=8
Click to expand...
Click to collapse
I ended up reverting back to the "M" stable image yesterday (was waiting for the June image to be available). No issues with the "N" to report, except one custom app that I use was giving me some issues.
Anyway, thought I'd share my "downgrade" story
If you do the downgrade the right way (un-enroll from the Beta program), and get the OTA back to the latest "M", it will likely go well - because it performs a factory reset on your phone.
I however, didn't wait to set my phone up from scratch (lazy), so I flashed the factory image for the latest "M" (and skipped userdata.img). Bad idea. Flash went thru' successfully, but I ended up with pretty much an unusable phone because two system processes kept crashing in a loop after booting up. I then tried ADB sideload for the new OTA image file - same results. Wiped cache partition - no difference.
I then remembered that some apps (like Google Maps) had different versions for "N", and realized that the issue must be because of apps like that not being compatible with "M". Thankfully, I had a nandroid backup of the "M" (May security release) from before I installed "N", and I installed that - and then, updated to the June security release of "M".
Whew!
So, in summary, If you are rooted, take a nandroid backup in TWRP before you install "N" preview. If not, plan to factory reset your device after going back (or while going back) to "M" - no shortcuts.

Repeated shutdowns.

Hi folks,
I'm using a Fire 7 5th Gen rooted and with the excellent Nexus Rom (02/12/2017 version). Following the upgrade I've had an issue whereby as soon as the screen goes to sleep the device appears to power off. It takes several presses of the power button to turn on again and booting into fastboot doesn't seem to work. The battery monitor shows approx 52% power (which seems about correct to me, based on how I've used it since last charge) so I didn't think it would be a battery issue. Does anyone have any idea what might be going on here and what I might do to fix it? Any help would be massively appreciated.
Thanks,
Jonathan

jonathanmoneill said:
Hi folks,
I'm using a Fire 7 5th Gen rooted and with the excellent Nexus Rom (02/12/2017 version). Following the upgrade I've had an issue whereby as soon as the screen goes to sleep the device appears to power off. It takes several presses of the power button to turn on again and booting into fastboot doesn't seem to work. The battery monitor shows approx 52% power (which seems about correct to me, based on how I've used it since last charge) so I didn't think it would be a battery issue. Does anyone have any idea what might be going on here and what I might do to fix it? Any help would be massively appreciated.
Thanks,
Jonathan
Click to expand...
Click to collapse
Symptoms are similar to a recently reported issue in the Lineage 12.1 thread if you applied the latest Nexus update. If that's the case simply roll back to the prior build.

Hi Davey,
Thanks for the update, I saw that thread after my OP and did wonder. I'm going to either roll back to an earlier version of the Nexus ROM or try a stable version of the Lineage ROM. As I can't get the device to stay on long enough to use FlashFire, I'm assuming an ADB sideload will be my best bet. Slightly off topic but is there one of those ROMs you'd recommend over the other?

jonathanmoneill said:
Hi Davey,
Thanks for the update, I saw that thread after my OP and did wonder. I'm going to either roll back to an earlier version of the Nexus ROM or try a stable version of the Lineage ROM. As I can't get the device to stay on long enough to use FlashFire, I'm assuming an ADB sideload will be my best bet. Slightly off topic but is there one of those ROMs you'd recommend over the other?
Click to expand...
Click to collapse
If the device shuts down while the Amazon logo is being displayed then it may be hardware related. ADB sideload of FireOS (be sure to get the build right) is your best option, preferably starting from stock recovery.
At present only two Custom ROMs are under active maintenance: Fire Nexus and LineageOS 12.1. Both are stable and feature complete. While I generally prefer pure AOSP (favoring Nexus) Lineage works well with this device and requires less customization to get the UX I prefer. Note: This device is not my daily driver so keeping things simple takes priority. Nexus is akin to a blank sheet of paper just waiting for some love while Lineage already has a few lines drawn in.

Davey126 said:
If the device shuts down while the Amazon logo is being displayed then it may be hardware related. ADB sideload of FireOS (be sure to get the build right) is your best option, preferably starting from stock recovery.
At present only two Custom ROMs are under active maintenance: Fire Nexus and LineageOS 12.1. Both are stable and feature complete. While I generally prefer pure AOSP (favoring Nexus) Lineage works well with this device and requires less customization to get the UX I prefer. Note: This device is not my daily driver so keeping things simple takes priority. Nexus is akin to a blank sheet of paper just waiting for some love while Lineage already has a few lines drawn in.
Click to expand...
Click to collapse
Thanks for the ROM advice. I love the Nexus ROm but I've been tempted by lineage for a while so I might take this opportunity to give it a go
In relation to sorting my current issues, the device doesn't shut down while the grey logo is being displayed, the OS loads and I usually get about 30-90 seconds of functioning before it dies again. Sorry if this seems like a NOOB question but is there any reason not to ADB sideload my chosen Lineage or Nexus ROM directly? Or if I'm going to reinstall fireOS just choose the factory reset option from fastboot (on those rare occasions I can get fastboot to work).

jonathanmoneill said:
Sorry if this seems like a NOOB question but is there any reason not to ADB sideload my chosen Lineage or Nexus ROM directly? Or if I'm going to reinstall fireOS just choose the factory reset option from fastboot (on those rare occasions I can get fastboot to work).
Click to expand...
Click to collapse
Amazon's crippled bootloader disables most commands and (obviously) ADB isn't an option from native fastboot. I doubt sideload will permit installation of a custom ROM from stock recovery. However, if you have done it before (and it works) great!

Davey126 said:
Amazon's crippled bootloader disables most commands and (obviously) ADB isn't an option from native fastboot. I doubt sideload will permit installation of a custom ROM from stock recovery. However, if you have done it before (and it works) great!
Click to expand...
Click to collapse
I hadn't tried this before and just as you predicted it didn't work. I was wondering how can I find out which version of the stock fireOS I need? Or will a factory reset from recovery still permit me to root again from scratch....

jonathanmoneill said:
I hadn't tried this before and just as you predicted it didn't work. I was wondering how can I find out which version of the stock fireOS I need? Or will a factory reset from recovery still permit me to root again from scratch....
Click to expand...
Click to collapse
You can try a factory reset. Failing that and w/o knowledge of the FireOS build that was previously installed go with 5.3.1 which is the last rootable version and will avoid a potential (recoverable) brick scenario if you inadvertently attempt to downgrade the bootloader.

Davey126 said:
You can try a factory reset. Failing that and w/o knowledge of the FireOS build that was previously installed go with 5.3.1 which is the last rootable version and will avoid a potential (recoverable) brick scenario if you inadvertently attempt to downgrade the bootloader.
Click to expand...
Click to collapse
Factory reset from the recovery screen seems to have solved my issues, tablet is purring like a kitten. Also saved myself the .bin for 5.3.1 in case of emergency. Thanks again for the advice on this

jonathanmoneill said:
Factory reset from the recovery screen seems to have solved my issues, tablet is purring like a kitten. Also saved myself the .bin for 5.3.1 in case of emergency. Thanks again for the advice on this
Click to expand...
Click to collapse
I was the one having the update issues, but it was on the Lineage ROM! Looks like whatever ggow did, it's affecting both Nexus and Lineage. I think I'll just roll back to the previous build then restore apps.